[Pce] Fw: I-D Action:draft-yasukawa-pce-p2mp-req-04.txt

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 14 November 2007 22:23 UTC

Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsQe7-0005N4-W5; Wed, 14 Nov 2007 17:23:44 -0500
Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1IsQe6-0005JV-Uf for pce-confirm+ok@megatron.ietf.org; Wed, 14 Nov 2007 17:23:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsQe6-0005I8-Iu for pce@ietf.org; Wed, 14 Nov 2007 17:23:42 -0500
Received: from asmtp2.iomartmail.com ([62.128.201.249]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IsQe5-0005iA-TO for pce@ietf.org; Wed, 14 Nov 2007 17:23:42 -0500
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id lAEMNdAF011359 for <pce@ietf.org>; Wed, 14 Nov 2007 22:23:39 GMT
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id lAEMNbIk011349 for <pce@ietf.org>; Wed, 14 Nov 2007 22:23:39 GMT
Message-ID: <066701c8270c$fe2f1b50$0200a8c0@your029b8cecfe>
From: Adrian Farrel <adrian@olddog.co.uk>
To: pce@ietf.org
Date: Wed, 14 Nov 2007 22:23:31 -0000
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc:
Subject: [Pce] Fw: I-D Action:draft-yasukawa-pce-p2mp-req-04.txt
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Path Computation Element <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org

For your information.

Only a small change. Section 2.1.6 re-written.

Adrian
----- Original Message ----- 
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Sent: Wednesday, November 14, 2007 8:50 PM
Subject: I-D Action:draft-yasukawa-pce-p2mp-req-04.txt


>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
> Title           : PCC-PCE Communication Requirements for Point to 
> Multipoint Multiprotocol Label Switching Traffic Engineering (MPLS-TE)
> Author(s)       : S. Yasukawa, A. Farrel
> Filename        : draft-yasukawa-pce-p2mp-req-04.txt
> Pages           : 10
> Date            : 2007-11-14
>
> The Path Computation Element (PCE) provides path computation
> functions in support of traffic engineering in Multi-Protocol Label
> Switching (MPLS) and Generalized MPLS (GMPLS) networks.
>
> Extensions to the MPLS and GMPLS signaling and routing protocols have
> been made in support of point-to-multipoint (P2MP) Traffic Engineered
> (TE) Label Switched Paths (LSPs). Since P2MP TE LSP routes are
> sometimes complex to compute, and given the use of PCE in MPLS
> networks it is likely that PCE will be used in P2MP MPLS-TE networks.
>
> Generic requirements for a communication protocol between Path
> Computation Clients (PCCs) and PCEs are presented in "Path
> Computation Element (PCE) Communication Protocol Generic
> Requirements". This document complements the generic requirements and
> presents a detailed set of PCC-PCE communication protocol
> requirements for point-to-multipoint MPLS traffic engineering.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-yasukawa-pce-p2mp-req-04.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> 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-yasukawa-pce-p2mp-req-04.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-yasukawa-pce-p2mp-req-04.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.
>


--------------------------------------------------------------------------------


> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce
> 




_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce