[Pce] Fw: I-D Action:draft-yasukawa-pce-p2mp-req-05.txt
"Adrian Farrel" <adrian@olddog.co.uk> Mon, 12 May 2008 10:48 UTC
Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DCB03A680D; Mon, 12 May 2008 03:48:14 -0700 (PDT)
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 58C4A3A680D for <pce@core3.amsl.com>; Mon, 12 May 2008 03:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.373
X-Spam-Level:
X-Spam-Status: No, score=-2.373 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zqJ0U8NOMuCJ for <pce@core3.amsl.com>; Mon, 12 May 2008 03:48:11 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by core3.amsl.com (Postfix) with ESMTP id 480643A67F9 for <pce@ietf.org>; Mon, 12 May 2008 03:48:11 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id m4CAlLpl029355 for <pce@ietf.org>; Mon, 12 May 2008 11:47:21 +0100
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id m4CAlIDr029267 for <pce@ietf.org>; Mon, 12 May 2008 11:47:20 +0100
Message-ID: <037d01c8b41d$85124f00$0200a8c0@your029b8cecfe>
From: Adrian Farrel <adrian@olddog.co.uk>
To: pce@ietf.org
Date: Mon, 12 May 2008 11:46:38 +0100
MIME-Version: 1.0
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
Subject: [Pce] Fw: I-D Action:draft-yasukawa-pce-p2mp-req-05.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org
Hi PCE, We are keeping this I-D alive pending the update to the charter to include P2MP. In this version, we have just made a few small changes to the text for clarity. Thanks, Adrian ----- Original Message ----- From: <Internet-Drafts@ietf.org> To: <i-d-announce@ietf.org> Sent: Monday, May 12, 2008 11:15 AM Subject: I-D Action:draft-yasukawa-pce-p2mp-req-05.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-05.txt > Pages : 10 > Date : 2008-05-12 > > 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). The use of PCE in MPLS networks is > already established, and since P2MP TE LSP routes are sometimes > complex to compute, it is likely that PCE will be used for P2MP LSPs. > > 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/GMPLS traffic engineering. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-yasukawa-pce-p2mp-req-05.txt _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce
- [Pce] Fw: I-D Action:draft-yasukawa-pce-p2mp-req-… Adrian Farrel