The MPLS WG Archive

[Seisho Yasukawa <yasukawa.seisho@lab.ntt.co.jp>]

Hi,

As discussed in Seoul, the P2MP requirements draft needed a few
minor changes before it was ready for working group last call.

We have now published a new version
(http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-requirement-02.txt)

In the view of the authors this draft is now complete and we would
like to ask the chairs to consider a working group last call.

Cheers,

Seisho


>To: IETF-Announce:;
>Cc: mpls@UU.NET
>From: Internet-Drafts@ietf.org
>Reply-to: Internet-Drafts@ietf.org
>Subject: I-D ACTION:draft-ietf-mpls-p2mp-requirement-02.txt
>Date: Fri, 26 Mar 2004 15:56:45 -0500
>Sender: owner-mpls@UU.NET
>
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>This draft is a work item of the Multiprotocol Label Switching Working 
>Group of the IETF.
>
>         Title           : Requirements for Point to Multipoint extension 
> to RSVP-TE
>         Author(s)       : S. Yasukawa
>         Filename        : draft-ietf-mpls-p2mp-requirement-02.txt
>         Pages           : 28
>         Date            : 2004-3-26
>
>This document presents a basic set of requirements for Point-to-
>    Multipoint(P2MP) Traffic Engineering (TE) extensions to Multiprotocol
>    Label Switching (MPLS). It specifies functional requirements for
>    RSVP-TE in order to deliver P2MP applications over a MPLS TE
>    infrastructure. It is intended that solutions that specify RSVP-TE
>    procedures for P2MP TE LSP setup satisfy these requirements. There is
>    no intent to specify solution specific details in this document.
>
>    It is intended that the requirements presented in this document are
>    not limited to the requirements of packet switched networks, but also
>    encompass the requirements of L2SC, TDM, lambda and port switching
>    networks managed by Generalized MPLS (GMPLS) protocols. Protocol
>    solutions developed to meet the requirements set out in this document
>    must be equally applicable to MPLS and GMPLS.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-requirement-02.txt
>
>To remove yourself from the IETF Announcement list, send a message to
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>         "get draft-ietf-mpls-p2mp-requirement-02.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>         mailserv@ietf.org.
>In the body type:
>         "FILE /internet-drafts/draft-ietf-mpls-p2mp-requirement-02.txt".
>
>NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <2004-3-26161416.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-mpls-p2mp-requirement-02.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-requirement-02.txt>