Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture
RFC 3985

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    pwe3 mailing list <pwe3@ietf.org>, 
    pwe3 chair <pwe3-chairs@tools.ietf.org>
Subject: Document Action: 'PWE3 Architecture' to Informational 
         RFC 

The IESG has approved the following document:

- 'PWE3 Architecture '
   <draft-ietf-pwe3-arch-08.txt> as an Informational RFC

This document is the product of the Pseudowire Emulation Edge to Edge 
Working Group. 

The IESG contact persons are Jon Peterson and Mark Townsley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-arch-08.txt

RFC Editor Note:

3rd paragraph of Section 10:

      OLD:

       Protection mechanisms must also address the spoofing of tunneled PW
       data. The validation of traffic addressed to the PW Demultiplexer
       end-point is paramount in ensuring integrity of PW encapsulation.
       Security protocols such as IPSec [RFC2401] may be used by the PW
       Demultiplexer Layer in order to maintain the integrity of the PW by
       authenticating data between the PW Demultiplexer End-points.

      NEW:

       Protection mechanisms must also address the spoofing of tunneled PW
       data. The validation of traffic addressed to the PW Demultiplexer
       end-point is paramount in ensuring integrity of PW encapsulation.
       Security protocols such as IPSec [RFC2401] may be used by the PW
       Demultiplexer Layer in order to provide authentication and data
       integrity of data between the PW Demultiplexer End-points.