MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements
RFC 4216

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>, 
    tewg mailing list <te-wg@ops.ietf.org>, 
    tewg chair <tewg-chairs@tools.ietf.org>
Subject: Document Action: 'MPLS Inter-AS Traffic Engineering 
         requirements' to Informational RFC 

The IESG has approved the following document:

- 'MPLS Inter-AS Traffic Engineering requirements '
   <draft-ietf-tewg-interas-mpls-te-req-10.txt> as an Informational RFC

This document is the product of the Internet Traffic Engineering Working 
Group. 

The IESG contact persons are Bert Wijnen and Alex Zinin.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-10.txt

Technical Summary
 
  This document discusses requirements for the support of inter-AS
  MPLS Traffic Engineering (MPLS TE).  Its main objective is to
  present a set of requirements which would result in general
  guidelines for the definition, selection and specification
  development for any technical solution(s) meeting these
  requirements.

Working Group Summary
 
  The working group has consensus to publish this document as an
  Informational RFC. It serves as input for further work in the 
  CCAMP WG.
 
Protocol Quality
 
  Bert Wijnen has reviewed this document for the IESG.
  The document has also been reviewed by Adrian Farrel (CCAMP WG
  co-chair).

RFC-Editor note:

Please change in section 5.2.2.1
OLD:
  The following provides a set of TE-LSP parameters in the inter-AS TE
  Requests (RSVP Path Message) that SHOULD be enforced at the AS
  boundaries: 

NEW:
  The following provides a set of TE-LSP parameters in the inter-AS TE 
  Requests (RSVP Path Message) that could be enforced at the AS 
  boundaries: