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

--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 4216

        Title:      MPLS Inter-Autonomous System (AS)
                    Traffic Engineering (TE) Requirements
        Author(s):  R. Zhang, Ed., J.-P. Vasseur, Ed.
        Status:     Informational
        Date:       November 2005
        Mailbox:    [email protected], [email protected]
        Pages:      29
        Characters: 64640
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-tewg-interas-mpls-te-req-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4216.txt


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 and scenarios which would result in
general guidelines for the definition, selection, and specification
development for any technical solution(s) meeting these requirements
and supporting the scenarios.

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

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [email protected]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="[email protected]"

Content-Type: text/plain
Content-ID: <[email protected]>

RETRIEVE: rfc
DOC-ID: rfc4216

--OtherAccess
Content-Type: Message/External-body; name="rfc4216.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <[email protected]>


--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IETF-Announce mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ietf-announce

--NextPart--