From pce-bounces@ietf.org  Sun Mar  2 02:37:03 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 66CF228C333;
	Sun,  2 Mar 2008 02:37:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.44
X-Spam-Level: 
X-Spam-Status: No, score=-0.44 tagged_above=-999 required=5 tests=[AWL=-0.003,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	RDNS_NONE=0.1]
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 51bIRaC74MM5; Sun,  2 Mar 2008 02:36:57 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B50873A6A60;
	Sun,  2 Mar 2008 02:36:57 -0800 (PST)
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 6355F3A6A60
	for <pce@core3.amsl.com>; Sun,  2 Mar 2008 02:36:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 tejRCR8Ftxf4 for <pce@core3.amsl.com>;
	Sun,  2 Mar 2008 02:36:51 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id 6C07C3A69D2
	for <pce@ietf.org>; Sun,  2 Mar 2008 02:36:49 -0800 (PST)
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
	m22AadvP010033 for <pce@ietf.org>; Sun, 2 Mar 2008 10:36:39 GMT
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
	m22Aaalv010018 for <pce@ietf.org>; Sun, 2 Mar 2008 10:36:39 GMT
Message-ID: <045501c87c51$47e2f2f0$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Sun, 2 Mar 2008 10:33:29 -0000
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] Liaison Statement received from ITU-T SG15
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,

We have received the following liaison statement from the ITU-T Study Group 
15.

There is no request for action, but we should consider these comments when 
revising the PCE inter-layer drafts.

Thanks,
Adrian

===

Title: Liaison Reply to IETF PCE WG on Application of PCE to Inter-Layer 
Networks
Submission Date: 2008-02-29
From: Greg Jones(ITU-T SG 15) <tsbsg15@itu.int>
To: IETF PCE WG(jpv@cisco.com,adrian@olddog.co.uk)
Cc: sob@harvard.edu, rcallon@juniper.net, dward@cisco.com
    pce@ietf.org, yoichi.maeda@ntt-at.co.jp, sjtrowbridge@alcatel-lucent.com
Reponse Contact: tsbsg15@itu.int
Technical Contact: betts01@nortel.com, hklam@alcatel-lucent.com

Purpose: For information

Thank you for bring the PCE drafts to our attention.  There has been recent 
work in SG15 on layer architecture and control plane discussion on 
interlayer aspects.

A recent Recommendation G.800 "Unified Functional Architecture of Transport 
Networks" describes the architecture of transport networks that encompasses 
G.805, which is applicable to connection-oriented technologies, and G.809, 
which is applicable to connectionless technologies.  All three 
Recommendations use the term "layer" which refers to the generation, 
transport and termination of a particular type of information (or 
"characteristic information").  While the use of the term has identical 
meaning in many cases between SG15 documents and the PCE drafts, reading the 
I-Ds with the G.800 definition of layer suggests that clarification of the 
terms "higher layer" and "lower layer" would be helpful.  We assume that 
this is the same as the client-server relationship in G.800.  One 
implication of this is that a lower (server) layer does not necessarily 
imply that the characteristic information transferred is larger (more bits) 
than the higher (client) layer.  Examples of this would be an inverse mux 
layer (e.g., a VCAT layer such as VC-3-3v) to its constituent layer, or a 
packet in packet case.  Another implication is that the technology of the 
higher and lower layer could even be the same (packet in packet).

Regarding draft-ietf-pce-inter-layer-frwk-05.txt, Q12/15 has been discussing 
topology representations for multi-layer networks and two models have 
emerged.  The first represents a layer network with resources strictly in 
that layer.  If server layers can be used to connect portions of the layer 
network of interest, then this can be represented as a link or node, 
sometime called pseudo links or pseudo nodes.  This appears to be similar to 
the representation of the dotted link in the various figures of the I-D.

PCEs can have visibility of individual layers with the potential 
connectivity.  Multiple layer visibility would be accomplished by putting 
several layers into scope of one PCE.

Another representation of the topology is one in which links from all layers 
are in the graph and adaptations supported at each link end are represented. 
Path computations on this model would be allowed to follow pairs of 
adaptations that exist on links such that the ingress and egress layers end 
up being the same.  Pruning of the graph prior to, or during, the path 
calculation by removing links whose ingress/egress layers are not desired, 
can improve the efficiency of the calculation.

Restricting PCE visibility to one or subset of the available layers of this 
second model is needed for the multiple PCE inter-layer path computation of 
section 3.2.  It could be done with some type of VNT manager.

 Comments by section on draft-ietf-pce-inter-layer-req-06.txt are:

1. Introduction.  Current text (in paragraph 3) suggests that the 
optimization is required.  We suggest that the requirement be phrased as "It 
is important to be able to optimize network resource utilization globally" 
"since there may be non-technical reasons that prevent global optimization." 
Similarly, it is suggested that some brief discussion of resource ownership 
be included as administrative/ownership boundaries between layers can affect 
the ability to optimize.  For example, if a server layer only uses the 
management plane for connection establishment (no control plane).

2. Section 3.1.2. It should be clarified that when a PCC makes a request, it 
should specify the layer for which it is requesting a path.  If there are 
several "mono" layers that could satisfy a path request, what indication is 
given to the PCE about which to select?

3. Section 3.1.3.  It may be helpful to have a depth indicator in the 
original PCC request that limits the maximum number of adaptations allowed 
in the returned path.  Similarly some indicator of how many administrative 
boundaries to cross could be useful to contain the cost of a potential path.

An electronic copy of this liaison statement is available at: 
ftp://ftp.itu.int/tsg15opticaltransport/COMMUNICATIONS/index.html

====

You can see this liaison statement in the IETF repository at URL of the IETF 
Web page: 
https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=426
body text in pdf 
(https://datatracker.ietf.org/documents/LIAISON/file533.pdf)



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


From pce-bounces@ietf.org  Tue Mar  4 07:29:58 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 13A923A68F9;
	Tue,  4 Mar 2008 07:29:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.753
X-Spam-Level: 
X-Spam-Status: No, score=-1.753 tagged_above=-999 required=5
	tests=[AWL=-1.316, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
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 DX9+gJggOuEJ; Tue,  4 Mar 2008 07:29:52 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E466D3A6D2E;
	Tue,  4 Mar 2008 07:29:46 -0800 (PST)
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 7EC1228C625
	for <pce@core3.amsl.com>; Tue,  4 Mar 2008 07:29:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 zupySo5wYV7e for <pce@core3.amsl.com>;
	Tue,  4 Mar 2008 07:29:40 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id CD3B928C65D
	for <pce@ietf.org>; Tue,  4 Mar 2008 07:28:57 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.25,444,1199682000"; 
   d="scan'208";a="384167"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 04 Mar 2008 10:28:48 -0500
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m24FSm9T022758
	for <pce@ietf.org>; Tue, 4 Mar 2008 10:28:48 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m24FSYal027536
	for <pce@ietf.org>; Tue, 4 Mar 2008 15:28:47 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 4 Mar 2008 10:28:43 -0500
Received: from 10.86.104.184 ([10.86.104.184]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue,  4 Mar 2008 15:28:43 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Tue, 04 Mar 2008 10:28:45 -0500
From: JP Vasseur <jvasseur@cisco.com>
To: <pce@ietf.org>
Message-ID: <C3F2D4DD.2BD8E%jvasseur@cisco.com>
Thread-Topic: Slides
Thread-Index: Ach+DG8trYT3cun/EdyVFgANk8WjQA==
Mime-version: 1.0
X-OriginalArrivalTime: 04 Mar 2008 15:28:44.0179 (UTC)
	FILETIME=[6EAFEE30:01C87E0C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=81; t=1204644528; x=1205508528;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20Slides |Sender:=20 |To:=20<pce@ietf.org>;
	bh=loG6ArhJg+73D3iY3cGFEHt4/+veB+w/EU3oewM03QY=;
	b=P0VIkchsmZ+Qx6mzbVoK9v3lcI/oD9geH3Vn2gicGA2ehQp92jAp0JgXQJ
	CZCWpSDfLXoYEDOkrjvDaq9jX8NxyAtRg1trwtVhgl9Ggx8VqpBrk4uG19DC
	RjcufH6MWk;
Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: [Pce] Slides
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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,

"Presenters" thanks to send us your slides by March 7?

Thanks.

JP.

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


From pce-bounces@ietf.org  Wed Mar  5 10:51:08 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3F93C3A6F29;
	Wed,  5 Mar 2008 10:51:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.631
X-Spam-Level: 
X-Spam-Status: No, score=0.631 tagged_above=-999 required=5 tests=[AWL=0.718,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_FR=0.35,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
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 ORQ2tdq9nf5C; Wed,  5 Mar 2008 10:51:07 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F1D413A6F38;
	Wed,  5 Mar 2008 10:51:06 -0800 (PST)
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 05D383A6F38
	for <pce@core3.amsl.com>; Wed,  5 Mar 2008 10:51:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 2Z3jNewgw8zE for <pce@core3.amsl.com>;
	Wed,  5 Mar 2008 10:51:05 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com
	[195.101.245.15])
	by core3.amsl.com (Postfix) with ESMTP id 7B1713A6915
	for <pce@ietf.org>; Wed,  5 Mar 2008 10:51:04 -0800 (PST)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 5 Mar 2008 19:50:11 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 5 Mar 2008 19:50:10 +0100
Message-ID: <D109C8C97C15294495117745780657AE09695E1E@ftrdmel1>
In-Reply-To: <20080227194501.A439D28C9DD@core3.amsl.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pce] I-D ACTION:draft-ietf-pce-of-02.txt
thread-index: Ach5elI+PAV/FaTaSQe5312jxORtxwFdwIDg
References: <20080227194501.A439D28C9DD@core3.amsl.com>
From: <jeanlouis.leroux@orange-ftgroup.com>
To: <pce@ietf.org>
X-OriginalArrivalTime: 05 Mar 2008 18:50:11.0821 (UTC)
	FILETIME=[BDE579D0:01C87EF1]
Subject: Re: [Pce] I-D ACTION:draft-ietf-pce-of-02.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi all,

This version accounts for comments received on the list.
There is only one minor update: We added a text to indicate that the OF can=
not be associated with a NO-PATH object.
We consider that this version is cooked and ready for WG last call.

Regards,

JL

-----Message d'origine-----
De : pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] De la part de Inter=
net-Drafts@ietf.org
Envoy=E9 : mercredi 27 f=E9vrier 2008 20:45
=C0 : i-d-announce@ietf.org
Cc : pce@ietf.org
Objet : [Pce] I-D ACTION:draft-ietf-pce-of-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
This draft is a work item of the Path Computation Element Working Group of =
the IETF.

	Title		: Encoding of Objective Functions in Path Computation Element commu=
nication Protocol (PCEP)
	Author(s)	: J. Le Roux
	Filename	: draft-ietf-pce-of-02.txt
	Pages		: 17
	Date		: 2008-2-27
	=

The computation of one or a series of Traffic Engineering Label =

   Switched Paths (TE LSPs) in MultiProtocol Label Switching (MPLS) and =

   Generalized MPLS (GMPLS) networks, is subject to a set of one or more =

   specific optimization criteria(s), referred to as an objective =

   function (e.g. minimum cost path, widest path, etc.). A Path =

   Computation Element (PCE) may support one or multiple objective =

   functions, and it is desired for a Path Computation Client (PCC) to =

   automatically discover the set of objective functions supported by a =

   PCE. Furthermore, it may be useful for a PCC to specify in a path =

   computation request the required objective function to be used by the =

   PCE to compute a TE LSP or a set of TE LSPs. Thus the aim of this =

   document is to define extensions to the PCE communication Protocol =

   (PCEP) in order to allow a PCC to discover the set of objective =

   functions supported by a PCE as well as to allow a PCC to indicate in =

   a path computation request the required objective function and a PCE =

   to indicate in a path computation reply the objective function that =

   was used for path computation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-of-02.txt

To remove yourself from the I-D Announcement list, send a message to i-d-an=
nounce-request@ietf.org with the word unsubscribe in the body of the messag=
e. =

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 usernam=
e "anonymous" and a password of your e-mail address. After logging in, type=
 "cd internet-drafts" and then "get draft-ietf-pce-of-02.txt".

A list of Internet-Drafts directories can be found in http://www.ietf.org/s=
hadow.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-pce-of-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 implementa=
tion to automatically retrieve the ASCII version of the Internet-Draft.
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


From pce-bounces@ietf.org  Sun Mar  9 11:42:35 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E05CD28C144;
	Sun,  9 Mar 2008 11:42:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.513
X-Spam-Level: 
X-Spam-Status: No, score=-100.513 tagged_above=-999 required=5
	tests=[AWL=-0.075, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 GpM1cDPiibOa; Sun,  9 Mar 2008 11:42:35 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 06DAE3A6AB5;
	Sun,  9 Mar 2008 11:42:35 -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 EC0FD3A6B0E
	for <pce@core3.amsl.com>; Sun,  9 Mar 2008 11:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 Afh8bHQBg4bR for <pce@core3.amsl.com>;
	Sun,  9 Mar 2008 11:42:33 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id E7A0B3A682B
	for <pce@ietf.org>; Sun,  9 Mar 2008 11:42:32 -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
	m29Ie95e001085 for <pce@ietf.org>; Sun, 9 Mar 2008 18:40:10 GMT
Received: from your029b8cecfe ([130.129.83.239]) (authenticated bits=0)
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m29Ie7TK001064 for <pce@ietf.org>; Sun, 9 Mar 2008 18:40:09 GMT
Message-ID: <00c801c88214$fff481b0$3a87960a@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Sun, 9 Mar 2008 18:40:04 -0000
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] Last call complete on PCEP
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,

Thanks to those who reviewed and commented during last call.

I saw a bunch of emails, and it is my reading that they mainly completed 
without any requirement for updates to the I-D.

*** If you disagree with this view, please speak up.


The issue that was left open was raised in the context of the XRO draft. The 
question was about harmonising the subobjects used to carry AS numbers. PCEP 
(as RSVP-TE) assumes 2 byte AS numbers. XRO allows 2 or 4 byte AS numbers. 
Should we converge, and if so, which way?

It is my (personal - not WG chair) opinion that it would be good to 
converge, so one of the I-Ds needs to change.
It is the opinion of the PCEP editors that it is convenient to restrict PCEP 
to 2 byte AS numbers on the grounds that we do not yet know how/if RSVP-TE 
will handle 4 byte AS numbers. New subobjects can be introduced for 4 byte 
AS numbers as and when needed.

That means that PCEP remains unchanged, and the XRO authors should update 
their I-D.

*** If you disagree with this view, please speak up.


Lastly, there were a couple of open questions from my review of the security 
section of the I-D. These related to key management and distribution. The 
editors and I don't know the answers to the questions. Since the IESG review 
will include a review by the Security Directorate, we can expect them to 
pick up on any issues (if they exist), and we have decided to pass the I-D 
to the IESG without delay and with no further attempt to resolve the 
questions.

*** If you think this is unreasonable, please speak up.


I will be writing the protocol shepherd documentation during the IETF week, 
with a view to submitting it to the ADs by the end of the week. So shout 
soon if you have any concerns.

Cheers,
Adrian



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


From pce-bounces@ietf.org  Mon Mar 10 08:30:38 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 89C4B28C9BC;
	Mon, 10 Mar 2008 08:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.518
X-Spam-Level: 
X-Spam-Status: No, score=-103.518 tagged_above=-999 required=5
	tests=[AWL=-3.081, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 1mVJLdID3dSB; Mon, 10 Mar 2008 08:30:38 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BCF9928DCB6;
	Mon, 10 Mar 2008 08:05:44 -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 534FF28D7A6
	for <pce@core3.amsl.com>; Mon, 10 Mar 2008 08:05:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 2xBZXQ8VEHME for <pce@core3.amsl.com>;
	Mon, 10 Mar 2008 08:05:41 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id A3AB828CFF5
	for <pce@ietf.org>; Mon, 10 Mar 2008 07:36:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,474,1199682000"; 
   d="scan'208";a="1166236"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 10 Mar 2008 10:34:30 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m2AEYUPi001748
	for <pce@ietf.org>; Mon, 10 Mar 2008 10:34:30 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m2AEYMap029060
	for <pce@ietf.org>; Mon, 10 Mar 2008 14:34:28 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 10 Mar 2008 10:34:12 -0400
Received: from 10.86.104.184 ([10.86.104.184]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 10 Mar 2008 14:34:12 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Mon, 10 Mar 2008 10:34:11 -0500
From: JP Vasseur <jvasseur@cisco.com>
To: <pce@ietf.org>
Message-ID: <C3FABF23.2D159%jvasseur@cisco.com>
Thread-Topic: Missing Slides
Thread-Index: AciCu84yDQCUvu6vEdyVFgANk8WjQA==
Mime-version: 1.0
X-OriginalArrivalTime: 10 Mar 2008 14:34:12.0863 (UTC)
	FILETIME=[CF4F38F0:01C882BB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=274; t=1205159670; x=1206023670;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20Missing=20Slides |Sender:=20 |To:=20<pce@ietf.org>;
	bh=yNj5hq0r1z0FsohoKcyCuFkDT2ftuODcH23FM7RBqB0=;
	b=nhojpZyNC/w7z82GB74x7swDWldDuNSN6Zon0iyO8J4iuVA4vNCjha4vGh
	N9218Xcw2DlXKvBPmdHVPTXqY8l2UmJXr1UN7JGNPwYtBSIfnplIQMlk5SSw
	NrUxD5mXTf;
Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: [Pce] Missing Slides
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Missing slides:

3) Inter-AS Requirements for the Path Computation Element Communication
Protocol (PCECP) - draft-ietf-pce-interas-pcecp-reqs-04.txt
(Kenji/Raymond/Nabil - 10mn) [25]

10) Update on draft-ietf-pce-disc-mib-02.txt (Emile - 10mn) [80]

Thanks.

JP.

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


From pce-bounces@ietf.org  Tue Mar 11 08:00:20 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2058528C5D1;
	Tue, 11 Mar 2008 08:00:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.518
X-Spam-Level: 
X-Spam-Status: No, score=-103.518 tagged_above=-999 required=5
	tests=[AWL=-3.081, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 qLjmsUkVXu4R; Tue, 11 Mar 2008 08:00:19 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9282F3A6E37;
	Tue, 11 Mar 2008 08:00:08 -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 1AC8228C496
	for <pce@core3.amsl.com>; Tue, 11 Mar 2008 08:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 MEA7x8yBwZGI for <pce@core3.amsl.com>;
	Tue, 11 Mar 2008 08:00:06 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 625FE3A6E37
	for <pce@ietf.org>; Tue, 11 Mar 2008 08:00:05 -0700 (PDT)
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 11 Mar 2008 07:57:46 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m2BEvj7E000495
	for <pce@ietf.org>; Tue, 11 Mar 2008 07:57:45 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id m2BEvPs1011005
	for <pce@ietf.org>; Tue, 11 Mar 2008 14:57:45 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 11 Mar 2008 10:57:14 -0400
Received: from [161.44.212.67] ([161.44.212.67]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 11 Mar 2008 10:57:14 -0400
Message-ID: <47D69DC8.5080701@cisco.com>
Date: Tue, 11 Mar 2008 10:57:12 -0400
From: Jon Parker <jdparker@cisco.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: pce@ietf.org
X-OriginalArrivalTime: 11 Mar 2008 14:57:14.0692 (UTC)
	FILETIME=[315B5840:01C88388]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=191; t=1205247465; x=1206111465;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdparker@cisco.com;
	z=From:=20Jon=20Parker=20<jdparker@cisco.com>
	|Subject:=20[Pce]=20PCE=20DSTE=20-=20draft-ietf-pce-dste-00
	.txt |Sender:=20;
	bh=u323q0zO+ZyObxHGA2bRIzLobaGJq6kQcmROGn18QjI=;
	b=k2wU5/L6VOG9gZtQ0M9xWfhohHb+eOQ8iiu6WKzTrqWDjVzSlINCSa5MG+
	9SdMrOb1pDsmuTT47ZX8e3OU8Kpr29OlVBqghjaTqDFcB+vtudz1GviM7AEk
	ki5BN+G74v;
Authentication-Results: sj-dkim-3; header.From=jdparker@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: [Pce]  PCE DSTE - draft-ietf-pce-dste-00.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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 WG,

The PCE DSTE draft 
(http://www.ietf.org/internet-drafts/draft-ietf-pce-dste-00.txt) seems 
stable.

Please go through the document and send your feedback.

Cheers,
Jon
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


From pce-bounces@ietf.org  Tue Mar 11 08:49:11 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 663263A6DCE;
	Tue, 11 Mar 2008 08:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.106
X-Spam-Level: 
X-Spam-Status: No, score=-100.106 tagged_above=-999 required=5
	tests=[AWL=-0.270, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6,
	RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 syeKq13gxgO7; Tue, 11 Mar 2008 08:49:10 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 16F803A6987;
	Tue, 11 Mar 2008 08:49:10 -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 3ECAE3A6987
	for <pce@core3.amsl.com>; Tue, 11 Mar 2008 08:49:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 Hkincjr9RD1w for <pce@core3.amsl.com>;
	Tue, 11 Mar 2008 08:49:08 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211])
	by core3.amsl.com (Postfix) with ESMTP id 4B7263A67B1
	for <pce@ietf.org>; Tue, 11 Mar 2008 08:49:08 -0700 (PDT)
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JXK00BT5P601T@usaga01-in.huawei.com> for
	pce@ietf.org; Tue, 11 Mar 2008 08:46:48 -0700 (PDT)
Received: from Lee736821 (dhcp-16d6.ietf71.ietf.org [130.129.22.214])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0JXK002QTP5V27@usaga01-in.huawei.com> for pce@ietf.org;
	Tue, 11 Mar 2008 08:46:48 -0700 (PDT)
Date: Tue, 11 Mar 2008 09:46:43 -0600
From: Young Lee <ylee@huawei.com>
To: pce@ietf.org
Message-id: <000001c8838f$1b1a0070$d6168182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Thread-index: AciDjxqZB2bWMAXFSkOP36kfwafMaQ==
Subject: [Pce] PCE WG rechater discussion
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: multipart/mixed; boundary="===============0669988587=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0669988587==
Content-type: multipart/alternative;
 boundary="Boundary_(ID_Hb4kUSBAjA/4aujSRH4Yeg)"

This is a multi-part message in MIME format.

--Boundary_(ID_Hb4kUSBAjA/4aujSRH4Yeg)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Enhancing PCE interoperability and Scalability for WSON and beyond
 
Hi PCE'rs, at the upcomming meeting in Philadelphia we noticed some time for
PCE
charter discussion. One area that has come up in the application of PCE to
wavelength switched optical networks (WSON) is the additional amount of
information needed to specify the constraints on the path.  In addition,
there
has been concerns about the scalability of distributing this information and
precise link lambda utilization information via an IGP.
 
In section 6.7 of RFC4655 (PCE Architecture) on PCE TED synchronization a
description of "Out-of-band TED synchronization" (non-IGP based) is given
and 
some considerations of mechanisms are discussed. For the WSON case we have
discussed in our various drafts such a mechanism could prove very
beneficial.
 
We think that the PCE charter should be extended to include a mechanism for
out
of band TED distribution and synchronization. This communication of TED
information can be partial or complete and could flow from network elements,
management systems, and PCEs to other PCEs.
 
The use of management protocols for "Out-of-band TED synchronization"
present a 
number of difficulties. First, the information models are by necessity much
larger and complex than required for constrained path computation since
those
models are used to support general network management (Fault, Configuration,
Accounting, Performance). Second, as seen in the WSON case, efficient
transport
of incremental updates of resource state is key to scalability in a dynamic
networking environment. While IGPs have generally been strong in this area
the
requirement of flooding the dynamic resource status information among all
network elements leads to scalability concerns. We envision that such a
capability could be acheived via an extendable path computation information
model roughly based on todays GMPLS routing models combined with a protocol
suitable for NE/NMS to PCE communications such as PCEP.
 
Regards
 
Greg B. and Young L.  

--Boundary_(ID_Hb4kUSBAjA/4aujSRH4Yeg)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3243" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial>Enhancing PCE interoperability and Scalability for WSON 
and beyond</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial>Hi PCE'rs, at the upcomming meeting in Philadelphia we 
noticed some time for PCE<BR>charter discussion. One area that has come up in 
the application of PCE to<BR>wavelength switched optical networks (WSON) is the 
additional amount of<BR>information needed to specify the constraints on the 
path.&nbsp; In addition, there<BR>has been concerns about the scalability of 
distributing this information and<BR>precise link lambda utilization information 
via an IGP.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial>In section 6.7 of RFC4655 (PCE Architecture) on PCE TED 
synchronization a<BR>description of "Out-of-band TED synchronization" (non-IGP 
based) is given and <BR>some considerations of mechanisms are discussed. For the 
WSON case we have<BR>discussed in our various drafts such a mechanism could 
prove very beneficial.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial>We think that the PCE charter should be extended to 
include a mechanism for out<BR>of band TED distribution and synchronization. 
This communication of TED<BR>information can be partial or complete and could 
flow from network elements,<BR>management systems, and PCEs to other 
PCEs.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial>The use of management protocols for "Out-of-band TED 
synchronization" present a <BR>number of difficulties. First, the information 
models are by necessity much<BR>larger and complex than required for constrained 
path computation since those<BR>models are used to support general network 
management (Fault, Configuration,<BR>Accounting, Performance). Second, as seen 
in the WSON case, efficient transport<BR>of incremental updates of resource 
state is key to scalability in a dynamic<BR>networking environment. While IGPs 
have generally been strong in this area the<BR>requirement of flooding the 
dynamic resource status information among all<BR>network elements leads to 
scalability concerns. We envision that such a<BR>capability could be acheived 
via an extendable path computation information<BR>model roughly based on todays 
GMPLS routing models combined with a protocol<BR>suitable for NE/NMS to PCE 
communications such as PCEP.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial>Regards</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial>Greg B. and Young L.&nbsp; </FONT></DIV></BODY></HTML>

--Boundary_(ID_Hb4kUSBAjA/4aujSRH4Yeg)--

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

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

--===============0669988587==--


From pce-bounces@ietf.org  Tue Mar 11 12:43:51 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2967628C472;
	Tue, 11 Mar 2008 12:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.038
X-Spam-Level: 
X-Spam-Status: No, score=-100.038 tagged_above=-999 required=5
	tests=[AWL=0.399, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 Y37qHwnS0Qn8; Tue, 11 Mar 2008 12:43:45 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A82E028C376;
	Tue, 11 Mar 2008 12:43:45 -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 D178228C40A
	for <pce@core3.amsl.com>; Tue, 11 Mar 2008 12:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 iKFtAG-HY8qL for <pce@core3.amsl.com>;
	Tue, 11 Mar 2008 12:43:42 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 333253A6C39
	for <pce@ietf.org>; Tue, 11 Mar 2008 12:43:42 -0700 (PDT)
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
	m2BJfKQj032065 for <pce@ietf.org>; Tue, 11 Mar 2008 19:41:21 GMT
Received: from your029b8cecfe (dhcp-148c.ietf71.ietf.org [130.129.20.140])
	(authenticated bits=0)
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m2BJfIQ2032056 for <pce@ietf.org>; Tue, 11 Mar 2008 19:41:20 GMT
Message-ID: <016a01c883af$dfa977c0$8c148182@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Tue, 11 Mar 2008 19:41:11 -0000
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] Temporary PCEP codepoint registry
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

As JP just reminded us about the temporary codepoint registry for PCEP.

This exists until IANA gets control of the registries and should help you 
with protocol extensions and implementations.

It can be found at www.olddog.co.uk/pce.htm

Currently, it is a little out of date, but JP and I will work to get it in 
synch with the current PCEP I-D.

Cheers,
Adrian 


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


From pce-bounces@ietf.org  Tue Mar 11 12:47:53 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 099AD28C4C9;
	Tue, 11 Mar 2008 12:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.196
X-Spam-Level: 
X-Spam-Status: No, score=-100.196 tagged_above=-999 required=5
	tests=[AWL=0.241, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 AWn6DXeR9VRP; Tue, 11 Mar 2008 12:47:52 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A62D28C4AD;
	Tue, 11 Mar 2008 12:47:52 -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 228193A68AD
	for <pce@core3.amsl.com>; Tue, 11 Mar 2008 12:47:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 mhcVaYuheHPd for <pce@core3.amsl.com>;
	Tue, 11 Mar 2008 12:47:50 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id B9FF628C4B6
	for <pce@ietf.org>; Tue, 11 Mar 2008 12:47:23 -0700 (PDT)
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
	m2BJj3O8000931 for <pce@ietf.org>; Tue, 11 Mar 2008 19:45:03 GMT
Received: from your029b8cecfe (dhcp-148c.ietf71.ietf.org [130.129.20.140])
	(authenticated bits=0)
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m2BJj0OS000917 for <pce@ietf.org>; Tue, 11 Mar 2008 19:45:02 GMT
Message-ID: <016f01c883b0$645da2c0$8c148182@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Tue, 11 Mar 2008 19:44:30 -0000
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] Two working group last calls
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,

As discussed in the PCE WG meeting, this email commences a two week working 
group last call on the following two drafts.

BRPC
http://www.ietf.org/internet-drafts/draft-ietf-pce-brpc-07.txt

Inter-AS PCEP requirements
http://www.ietf.org/internet-drafts/draft-ietf-pce-interas-pcecp-reqs-04.txt

Please send comments to the list.

The last call will end on Monday March 31st at 12 noon GMT. That is almost 
three weeks (because it overlaps with the IETF meeting) but please review 
early and often.

Thanks,
Adrian 


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


From pce-bounces@ietf.org  Tue Mar 11 19:08:02 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F29AA28C3AA;
	Tue, 11 Mar 2008 19:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.699
X-Spam-Level: 
X-Spam-Status: No, score=-98.699 tagged_above=-999 required=5
	tests=[AWL=-0.015, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MIME_BASE64_TEXT=1.753, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 4UIUpY6qDKOw; Tue, 11 Mar 2008 19:08:01 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 232C73A6AE8;
	Tue, 11 Mar 2008 19:08:01 -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 EB4FC28C3A3
	for <pce@core3.amsl.com>; Tue, 11 Mar 2008 19:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 gXC7GixLaQbo for <pce@core3.amsl.com>;
	Tue, 11 Mar 2008 19:07:59 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [61.144.161.53])
	by core3.amsl.com (Postfix) with ESMTP id 0BA2028C2E3
	for <pce@ietf.org>; Tue, 11 Mar 2008 19:07:59 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JXL00G91HT4AW@szxga01-in.huawei.com> for
	pce@ietf.org; Wed, 12 Mar 2008 10:05:28 +0800 (CST)
Received: from M55527 ([10.111.12.186])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JXL008JOHT1XP@szxga01-in.huawei.com> for
	pce@ietf.org; Wed, 12 Mar 2008 10:05:28 +0800 (CST)
Date: Wed, 12 Mar 2008 10:05:26 +0800
From: Mach Chen <mach@huawei.com>
To: Adrian Farrel <adrian@olddog.co.uk>, "pce@ietf.org" <pce@ietf.org>
Message-id: <200803121005245480719@huawei.com>
Organization: Huawei
MIME-version: 1.0
X-Mailer: Foxmail 6, 10, 201, 20 [cn]
References: <016f01c883b0$645da2c0$8c148182@your029b8cecfe>
Subject: Re: [Pce] Two working group last calls
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="gb2312"
Content-Transfer-Encoding: base64
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

SGksDQoNCkhlcmUgYXJlIHNvbWUgY29tbWVudHMgYWJvdXQgdGhlIEJSUEMgZHJhZnQ6DQogDQog
ICAxoaJJbiB0aGUgbWlkZGxlIG9mIFNlY3Rpb24gNC4yDQogDQogICAiTm90ZSB0aGF0IFBDRShp
KSBvbmx5IGNvbnNpZGVycyB0aGUgZW50cnkgQk5zIHRoYXQgcHJvdmlkZQ0KICAgY29ubmVjdGl2
aXR5IGZyb20gZG9tYWluKGktMSkuICBUaGF0IGlzLCB0aGUgc2V0IEJOLWVuKGssaS0xKSBpcyBv
bmx5DQogICBtYWRlIG9mIHRob3NlIEJOcyB0aGF0IHByb3ZpZGUgY29ubmVjdGl2aXR5IGZyb20g
ZG9tYWluIChpLTEpIHRvDQogICBkb21haW4oaSkuICBGdXJ0aGVybW9yZSwgc29tZSBCTnMgbWF5
IGJlIGV4Y2x1ZGVkIGFjY29yZGluZyB0byBwb2xpY3kNCiAgIGNvbnN0cmFpbnRzIChlaXRoZXIg
ZHVlIHRvIGxvY2FsIHBvbGljeSBvciBwb2xpY2llcyBzaWduYWxlZCBpbiB0aGUNCiAgIHBhdGgg
Y29tcHV0YXRpb24gcmVxdWVzdCkuIg0KIA0KICAgQXMgdGhlIGRlZmluaXRpb24gb2YgVlNQVChp
KSwgaXMgdGhlICJCTi1lbihrLGktMSkiIHNob3VsZCBiZSAiQk4tZW4oayxpKSIgPw0KIA0KICAg
DQogICAyoaJJbiB0aGUgZHJhZnQsIHRoZXJlIGFyZSBzZXZlcnZhbCBwbGFjZXMgdXNpbmcgIkJS
IiwgIkJSLWVuIiwgIkJSLWV4IiwgYnV0IHRoZXJlIGlzIG5vIHN1Y2ggZGVmaW5pdGlvbiBhYm91
dCAiQlIiLCBpZiBJIGFtIGNvcnJlY3QsIEkgZ3Vlc3MgaXQgc2hvdWxkIGJlICJCTiIsICJCTi1l
biIsICJCTi1leCIuIFBsZWFzZSBjaGVjay4NCg0KDQpCZXN0IHJlZ2FyZHMsDQpNYWNoDQoNCiAg
DQpPbiAyMDA4LTAzLTEyLCBhdCAwMzo0NTo0OSBBZHJpYW4gRmFycmVsIHdyb3RlOg0KDQo+SGks
DQo+DQo+QXMgZGlzY3Vzc2VkIGluIHRoZSBQQ0UgV0cgbWVldGluZywgdGhpcyBlbWFpbCBjb21t
ZW5jZXMgYSB0d28gd2VlayB3b3JraW5nIA0KPmdyb3VwIGxhc3QgY2FsbCBvbiB0aGUgZm9sbG93
aW5nIHR3byBkcmFmdHMuDQo+DQo+QlJQQw0KPmh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQt
ZHJhZnRzL2RyYWZ0LWlldGYtcGNlLWJycGMtMDcudHh0DQo+DQo+SW50ZXItQVMgUENFUCByZXF1
aXJlbWVudHMNCj5odHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRm
LXBjZS1pbnRlcmFzLXBjZWNwLXJlcXMtMDQudHh0DQo+DQo+UGxlYXNlIHNlbmQgY29tbWVudHMg
dG8gdGhlIGxpc3QuDQo+DQo+VGhlIGxhc3QgY2FsbCB3aWxsIGVuZCBvbiBNb25kYXkgTWFyY2gg
MzFzdCBhdCAxMiBub29uIEdNVC4gVGhhdCBpcyBhbG1vc3QgDQo+dGhyZWUgd2Vla3MgKGJlY2F1
c2UgaXQgb3ZlcmxhcHMgd2l0aCB0aGUgSUVURiBtZWV0aW5nKSBidXQgcGxlYXNlIHJldmlldyAN
Cj5lYXJseSBhbmQgb2Z0ZW4uDQo+DQo+VGhhbmtzLA0KPkFkcmlhbiANCj4NCj4NCj5fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPlBjZSBtYWlsaW5nIGxp
c3QNCj5QY2VAaWV0Zi5vcmcNCj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L3BjZQ0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
ClBjZSBtYWlsaW5nIGxpc3QKUGNlQGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vcGNlCg==


From pce-bounces@ietf.org  Wed Mar 12 02:42:24 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B86228C5F0;
	Wed, 12 Mar 2008 02:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.122
X-Spam-Level: 
X-Spam-Status: No, score=-101.122 tagged_above=-999 required=5
	tests=[AWL=-0.685, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 0RozzcgFxjly; Wed, 12 Mar 2008 02:42:23 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F1E528C5DE;
	Wed, 12 Mar 2008 02:42:23 -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 A879E28C5E5
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 02:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 HAwhsY0R6lEx for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 02:42:19 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 1A3C528C583
	for <pce@ietf.org>; Wed, 12 Mar 2008 02:42:01 -0700 (PDT)
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 12 Mar 2008 02:39:42 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m2C9dgtr021045; 
	Wed, 12 Mar 2008 02:39:42 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m2C9dgBD022533;
	Wed, 12 Mar 2008 09:39:42 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Mar 2008 05:39:41 -0400
Received: from 10.21.69.188 ([10.21.69.188]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Wed, 12 Mar 2008 09:39:40 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Wed, 12 Mar 2008 05:39:39 -0400
From: JP Vasseur <jvasseur@cisco.com>
To: Mach Chen <mach@huawei.com>, Adrian Farrel <adrian@olddog.co.uk>,
	"pce@ietf.org" <pce@ietf.org>
Message-ID: <C3FD1D1B.2DB33%jvasseur@cisco.com>
Thread-Topic: [Pce] Two working group last calls
Thread-Index: AciEJP2xPGOne/AYEdy5UAANk8WjQA==
In-Reply-To: <200803121005245480719@huawei.com>
Mime-version: 1.0
X-OriginalArrivalTime: 12 Mar 2008 09:39:41.0162 (UTC)
	FILETIME=[FEFB24A0:01C88424]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2121; t=1205314782;
	x=1206178782; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20Re=3A=20[Pce]=20Two=20working=20group=20last=20
	calls |Sender:=20;
	bh=jajn4YqtgJkqByP2gx4uKwJPS9BlGBiswvyXmsjLanU=;
	b=DNTAHjbTYSNkigHmsRlKXZkbdcaFOnrPYmi2pojR9lqf3nJxiGq8weunLR
	3kr5BylW4IlqINaIa/d7pJk/C9MMn31bhTnlv1I28dcAY+fCuub5FGpOxBh9
	gRWguBZYp5;
Authentication-Results: sj-dkim-3; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: Re: [Pce] Two working group last calls
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi Mach,


> From: Mach Chen <mach@huawei.com>
> Organization: Huawei
> Date: Wed, 12 Mar 2008 10:05:26 +0800
> To: Adrian Farrel <adrian@olddog.co.uk>, "pce@ietf.org" <pce@ietf.org>
> Cc: JP Vasseur <jvasseur@cisco.com>
> Subject: Re: [Pce] Two working group last calls
> 
> Hi,
> 
> Here are some comments about the BRPC draft:
>  
>    1$B!"(BIn the middle of Section 4.2
>  
>    "Note that PCE(i) only considers the entry BNs that provide
>    connectivity from domain(i-1).  That is, the set BN-en(k,i-1) is only
>    made of those BNs that provide connectivity from domain (i-1) to
>    domain(i).  Furthermore, some BNs may be excluded according to policy
>    constraints (either due to local policy or policies signaled in the
>    path computation request)."
>  
>    As the definition of VSPT(i), is the "BN-en(k,i-1)" should be "BN-en(k,i)"
> ?

Indeed, it should read "i" and not "i-1", thanks for catching the typo.

>  
>    
>    2$B!"(BIn the draft, there are severval places using "BR", "BR-en", "BR-ex", but
> there is no such definition about "BR", if I am correct, I guess it should be
> "BN", "BN-en", "BN-ex". Please check.

Fixed to consistently use the same terminology.

Thanks for your comments.

JP.

> 
> 
> Best regards,
> Mach
> 
>   
> On 2008-03-12, at 03:45:49 Adrian Farrel wrote:
> 
>> Hi,
>> 
>> As discussed in the PCE WG meeting, this email commences a two week working
>> group last call on the following two drafts.
>> 
>> BRPC
>> http://www.ietf.org/internet-drafts/draft-ietf-pce-brpc-07.txt
>> 
>> Inter-AS PCEP requirements
>> http://www.ietf.org/internet-drafts/draft-ietf-pce-interas-pcecp-reqs-04.txt
>> 
>> Please send comments to the list.
>> 
>> The last call will end on Monday March 31st at 12 noon GMT. That is almost
>> three weeks (because it overlaps with the IETF meeting) but please review
>> early and often.
>> 
>> Thanks,
>> Adrian 
>> 
>> 
>> _______________________________________________
>> Pce mailing list
>> Pce@ietf.org
>> https://www.ietf.org/mailman/listinfo/pce
> 
> 

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


From pce-bounces@ietf.org  Wed Mar 12 03:35:36 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3BF8228C620;
	Wed, 12 Mar 2008 03:35:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.881
X-Spam-Level: 
X-Spam-Status: No, score=-99.881 tagged_above=-999 required=5
	tests=[AWL=-1.744, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 YNzIMEnj1Dhh; Wed, 12 Mar 2008 03:35:35 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4CACE28C60C;
	Wed, 12 Mar 2008 03:35:35 -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 20C4928C60C
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 03:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 Be4IR3voHXOD for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 03:35:33 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 2CFB928C601
	for <pce@ietf.org>; Wed, 12 Mar 2008 03:35:33 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,487,1199682000"; 
   d="scan'208";a="1426591"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 12 Mar 2008 06:33:13 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m2CAXDbC030666; 
	Wed, 12 Mar 2008 06:33:13 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m2CAXDu8014654; 
	Wed, 12 Mar 2008 10:33:13 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Mar 2008 06:33:13 -0400
Received: from 10.21.69.188 ([10.21.69.188]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Wed, 12 Mar 2008 10:33:13 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Wed, 12 Mar 2008 06:33:11 -0400
From: JP Vasseur <jvasseur@cisco.com>
To: <pce@ietf.org>
Message-ID: <C3FD29A7.2DB58%jvasseur@cisco.com>
Thread-Topic: Quick Poll on PCE Rechartering
Thread-Index: AciELHgxtwDFHvAfEdy5UAANk8WjQA==
Mime-version: 1.0
X-OriginalArrivalTime: 12 Mar 2008 10:33:13.0407 (UTC)
	FILETIME=[79A0D4F0:01C8842C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=422; t=1205317993; x=1206181993;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20Quick=20Poll=20on=20PCE=20Rechartering |Sender:=20
	|To:=20<pce@ietf.org>;
	bh=1+18BVuoepXBNkr5wlE9A9FEyiwb0HUUmWLjNpgrEUg=;
	b=amMm7DsFEdOOTqavC0undgKAhFS70oMOH701Pr62jf1bhFdtFiagWXumoR
	lzlk7imUZIITMU7KvDIqGxkPnEDnxiVAjikzJ8Lr0B0WrBNlz2xZwoAkJs/G
	qfNS3y8Ihf;
Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: rcallon@juniper.net
Subject: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Dear WG,

We discussed about our rechartering during the PCE WG yesterday and there
was a large consensus for including P2MP (requirements and PCEP protocol
extensions). It is at this point pre-mature to include further items but the
discussion should continue on the ML.

Before finalizing the new proposed charter, we wanted to first confirm the
consensus on the mailing list.

In support ?

Thanks.

JP.

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


From pce-bounces@ietf.org  Wed Mar 12 04:45:42 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7659628C653;
	Wed, 12 Mar 2008 04:45:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.678
X-Spam-Level: 
X-Spam-Status: No, score=-98.678 tagged_above=-999 required=5
	tests=[AWL=-0.540, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 vpE2KsDlgcDg; Wed, 12 Mar 2008 04:45:41 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8E3F528C649;
	Wed, 12 Mar 2008 04:45:41 -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 6541828C649
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 04:45:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 Mg4PfzanSrvV for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 04:45:39 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159])
	by core3.amsl.com (Postfix) with ESMTP id E2F1028C64A
	for <pce@ietf.org>; Wed, 12 Mar 2008 04:45:38 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id 16so2348491fgg.41
	for <pce@ietf.org>; Wed, 12 Mar 2008 04:43:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=01QUr4qXlPMTz3CpM3F1NX5jUsgjcgLFmUZKfiAfOcc=;
	b=liLUjHVyis10DxhyaL7yfOlEAqmCvRMEp/P+3av2Bi3qjuCzJwzsKwMrOBb7InneYAGkUmbWNjSulmOynG9BkLT2wTB2v5NOhE8XsNt6IGE2GtwoPBvI7VBaOHVU1PyXpi+IQv6txAukCw084ljU90sjlLUHcPJM8HXvCrTsGO4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=A0z0EvTGryGIv+jQTN1muZ8iKdG6E+t6hSukqNGHTNkkxfgcZpfgNpO02DN15OodiF6hXljuQyd19LzOLGwWJGCvWYdk05TEcaN6DiHii/TeaEGB+gCXEDb3m9IaDk7P+Sn4U+7yYqbDhaFdj5QpgJKJFQKSnkQ919Syu/rqvU0=
Received: by 10.86.84.5 with SMTP id h5mr750156fgb.27.1205322199403;
	Wed, 12 Mar 2008 04:43:19 -0700 (PDT)
Received: by 10.86.2.3 with HTTP; Wed, 12 Mar 2008 04:43:19 -0700 (PDT)
Message-ID: <406e32c00803120443id9b503dt376676e0979eee4@mail.gmail.com>
Date: Wed, 12 Mar 2008 07:43:19 -0400
From: "Peng He" <peng.he.2000@gmail.com>
To: "JP Vasseur" <jvasseur@cisco.com>
In-Reply-To: <C3FD29A7.2DB58%jvasseur@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <C3FD29A7.2DB58%jvasseur@cisco.com>
Cc: rcallon@juniper.net, pce@ietf.org
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Support.

Regards,
Peng

On Wed, Mar 12, 2008 at 6:33 AM, JP Vasseur <jvasseur@cisco.com> wrote:
> Dear WG,
>
>  We discussed about our rechartering during the PCE WG yesterday and there
>  was a large consensus for including P2MP (requirements and PCEP protocol
>  extensions). It is at this point pre-mature to include further items but the
>  discussion should continue on the ML.
>
>  Before finalizing the new proposed charter, we wanted to first confirm the
>  consensus on the mailing list.
>
>  In support ?
>
>  Thanks.
>
>  JP.
>
>  _______________________________________________
>  Pce mailing list
>  Pce@ietf.org
>  https://www.ietf.org/mailman/listinfo/pce
>
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


From pce-bounces@ietf.org  Wed Mar 12 05:25:43 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6DC3C28C6C6;
	Wed, 12 Mar 2008 05:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.164
X-Spam-Level: 
X-Spam-Status: No, score=-99.164 tagged_above=-999 required=5
	tests=[AWL=-1.027, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 chSVu65d1uDK; Wed, 12 Mar 2008 05:25:42 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 07B1E28C6A6;
	Wed, 12 Mar 2008 05:25:42 -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 21D3428C6A6
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 05:25:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 MZUq-CGFzxLr for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 05:25:40 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 3123928C68D
	for <pce@ietf.org>; Wed, 12 Mar 2008 05:25:40 -0700 (PDT)
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 12 Mar 2008 05:23:21 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m2CCNLSx023160; 
	Wed, 12 Mar 2008 05:23:21 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m2CCNGgi012823;
	Wed, 12 Mar 2008 12:23:16 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Mar 2008 05:23:16 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 12 Mar 2008 05:23:14 -0700
Message-ID: <70BC84B185C3EE448EDB7AB8956D3B0E0532D71F@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <C3FD29A7.2DB58%jvasseur@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pce] Quick Poll on PCE Rechartering
Thread-Index: AciELHgxtwDFHvAfEdy5UAANk8WjQAAD1aEg
References: <C3FD29A7.2DB58%jvasseur@cisco.com>
From: "Dean Cheng (dcheng)" <dcheng@cisco.com>
To: "Jean Philippe Vasseur (jvasseur)" <jvasseur@cisco.com>, <pce@ietf.org>
X-OriginalArrivalTime: 12 Mar 2008 12:23:16.0549 (UTC)
	FILETIME=[D9685750:01C8843B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=922; t=1205324601; x=1206188601;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dcheng@cisco.com;
	z=From:=20=22Dean=20Cheng=20(dcheng)=22=20<dcheng@cisco.com>
	|Subject:=20RE=3A=20[Pce]=20Quick=20Poll=20on=20PCE=20Recha
	rtering |Sender:=20;
	bh=neqL1k5QU4ua18gtc4ttBmfbumFP6HXKkGgsQw20Wkw=;
	b=qwraIntP6VoUxlcKp/dTAes7O2/HWkAE/JZB5WIdzlBRoD8LWW8w+5HPbJ
	ZKj55y/mHjwh496xGtleepuuVtpe5mOZmzidQBSBC8lw9b2z73hTT0smigZr
	f8Xjw4vqj3;
Authentication-Results: sj-dkim-4; header.From=dcheng@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: rcallon@juniper.net
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Yes. 

> -----Original Message-----
> From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On 
> Behalf Of Jean Philippe Vasseur (jvasseur)
> Sent: Wednesday, March 12, 2008 3:33 AM
> To: pce@ietf.org
> Cc: rcallon@juniper.net
> Subject: [Pce] Quick Poll on PCE Rechartering
> 
> Dear WG,
> 
> We discussed about our rechartering during the PCE WG 
> yesterday and there was a large consensus for including P2MP 
> (requirements and PCEP protocol extensions). It is at this 
> point pre-mature to include further items but the discussion 
> should continue on the ML.
> 
> Before finalizing the new proposed charter, we wanted to 
> first confirm the consensus on the mailing list.
> 
> In support ?
> 
> Thanks.
> 
> JP.
> 
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
> 
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


From pce-bounces@ietf.org  Wed Mar 12 05:34:56 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 58A7F28C6F5;
	Wed, 12 Mar 2008 05:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.953
X-Spam-Level: 
X-Spam-Status: No, score=-97.953 tagged_above=-999 required=5
	tests=[AWL=0.184, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 UxYfZNafCFtj; Wed, 12 Mar 2008 05:34:54 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D9E7628C6DC;
	Wed, 12 Mar 2008 05:34:54 -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 0F04828C62C
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 05:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 krRBjRSdaKQp for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 05:34:50 -0700 (PDT)
Received: from tama50.ecl.ntt.co.jp (tama50.ecl.ntt.co.jp [129.60.39.147])
	by core3.amsl.com (Postfix) with ESMTP id 3473D28C67A
	for <pce@ietf.org>; Wed, 12 Mar 2008 05:34:49 -0700 (PDT)
Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149])
	by tama50.ecl.ntt.co.jp (8.14.2/8.14.2) with ESMTP id m2CCVOtF007560;
	Wed, 12 Mar 2008 21:31:24 +0900 (JST)
Received: from mfs6.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 581F46BFB;
	Wed, 12 Mar 2008 21:31:24 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (eclscan2.m.ecl.ntt.co.jp
	[129.60.5.68])
	by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 52B186B9E;
	Wed, 12 Mar 2008 21:31:24 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2CCVNrv027468; Wed, 12 Mar 2008 21:31:23 +0900 (JST)
Received: from imf.m.ecl.ntt.co.jp (imf0.m.ecl.ntt.co.jp [129.60.5.144])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2CCVNif027459; Wed, 12 Mar 2008 21:31:23 +0900 (JST)
Received: from imf.m.ecl.ntt.co.jp (webmail.ecl.ntt.co.jp [129.60.39.130])
	by imf.m.ecl.ntt.co.jp (8.13.8/8.13.8) with SMTP id m2CCVMBe005748;
	Wed, 12 Mar 2008 21:31:22 +0900 (JST)
Message-Id: <200803121231.m2CCVMBe005748@imf.m.ecl.ntt.co.jp>
To: jvasseur@cisco.com, pce@ietf.org
From: Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp>
Date: Wed, 12 Mar 2008 21:31:22 +0900
In-Reply-To: <C3FD29A7.2DB58%jvasseur@cisco.com>
X-Mailer: WebMail V3.5.2 PL1
Mime-Version: 1.0
Cc: rcallon@juniper.net
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Yes

Tomonori

> Dear WG,
> 
> We discussed about our rechartering during the PCE WG yesterday and there
> was a large consensus for including P2MP (requirements and PCEP protocol
> extensions). It is at this point pre-mature to include further items but the
> discussion should continue on the ML.
> 
> Before finalizing the new proposed charter, we wanted to first confirm the
> consensus on the mailing list.
> 
> In support ?
> 
> Thanks.
> 
> JP.
> 
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce

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


From pce-bounces@ietf.org  Wed Mar 12 06:06:41 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CAC9428C788;
	Wed, 12 Mar 2008 06:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.218
X-Spam-Level: 
X-Spam-Status: No, score=-99.218 tagged_above=-999 required=5
	tests=[AWL=-1.081, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 FvPiuqSlDdIU; Wed, 12 Mar 2008 06:06:41 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA1C428C798;
	Wed, 12 Mar 2008 06:05:39 -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 3BBDB28C697
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 06:05:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 LtBYeUeA2Uh7 for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 06:05:34 -0700 (PDT)
Received: from pro.abac.com (pro.abac.com [66.226.64.2])
	by core3.amsl.com (Postfix) with ESMTP id 0DD7428C73B
	for <pce@ietf.org>; Wed, 12 Mar 2008 06:04:51 -0700 (PDT)
Received: from [130.129.23.74] (dhcp-174a.ietf71.ietf.org [130.129.23.74])
	(authenticated bits=0)
	by pro.abac.com (8.14.1/8.14.1) with ESMTP id m2CD2IR3070122
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 12 Mar 2008 06:02:23 -0700 (PDT)
	(envelope-from gregb@grotto-networking.com)
Message-ID: <47D7D45D.3000400@grotto-networking.com>
Date: Wed, 12 Mar 2008 06:02:21 -0700
From: Greg Bernstein <gregb@grotto-networking.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: JP Vasseur <jvasseur@cisco.com>
References: <C3FD29A7.2DB58%jvasseur@cisco.com>
In-Reply-To: <C3FD29A7.2DB58%jvasseur@cisco.com>
Cc: rcallon@juniper.net, pce@ietf.org
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Yes.

Greg B.

JP Vasseur wrote:
> Dear WG,
>
> We discussed about our rechartering during the PCE WG yesterday and there
> was a large consensus for including P2MP (requirements and PCEP protocol
> extensions). It is at this point pre-mature to include further items but the
> discussion should continue on the ML.
>
> Before finalizing the new proposed charter, we wanted to first confirm the
> consensus on the mailing list.
>
> In support ?
>
> Thanks.
>
> JP.
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>
>   

-- 
===================================================
Dr Greg Bernstein, Grotto Networking (510) 573-2237



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


From pce-bounces@ietf.org  Wed Mar 12 06:52:46 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9564128C1B5;
	Wed, 12 Mar 2008 06:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.964
X-Spam-Level: 
X-Spam-Status: No, score=-97.964 tagged_above=-999 required=5
	tests=[AWL=0.173, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 yMiO6gd8FzXb; Wed, 12 Mar 2008 06:52:45 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B4E923A6E3D;
	Wed, 12 Mar 2008 06:52:42 -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 50CB53A6CBA
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 06:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 o3oENOqB0CI2 for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 06:52:40 -0700 (PDT)
Received: from tama500.ecl.ntt.co.jp (tama500.ecl.ntt.co.jp [129.60.39.148])
	by core3.amsl.com (Postfix) with ESMTP id 8F09928C696
	for <pce@ietf.org>; Wed, 12 Mar 2008 06:52:01 -0700 (PDT)
Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149])
	by tama500.ecl.ntt.co.jp (8.14.2/8.14.2) with ESMTP id
	m2CDnexh002475; Wed, 12 Mar 2008 22:49:40 +0900 (JST)
Received: from mfs6.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id BA8916BFB;
	Wed, 12 Mar 2008 22:49:40 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (eclscan2.m.ecl.ntt.co.jp
	[129.60.5.68])
	by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id B0B876B9E;
	Wed, 12 Mar 2008 22:49:40 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2CDne7j017843; Wed, 12 Mar 2008 22:49:40 +0900 (JST)
Received: from imb.m.ecl.ntt.co.jp (imb0.m.ecl.ntt.co.jp [129.60.5.140])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2CDndwi017836; Wed, 12 Mar 2008 22:49:39 +0900 (JST)
Received: from [129.60.80.54] ([129.60.80.54])
	by imb.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id m2CDndKg005940;
	Wed, 12 Mar 2008 22:49:39 +0900 (JST)
Date: Wed, 12 Mar 2008 22:49:16 +0900
From: Eiji Oki <oki.eiji@lab.ntt.co.jp>
To: JP Vasseur <jvasseur@cisco.com>
In-Reply-To: <C3FD29A7.2DB58%jvasseur@cisco.com>
References: <C3FD29A7.2DB58%jvasseur@cisco.com>
Message-Id: <20080312224852.07F0.OKI.EIJI@lab.ntt.co.jp>
MIME-Version: 1.0
X-Mailer: Becky! ver. 2.30.04 [ja]
Cc: rcallon@juniper.net, pce@ietf.org
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Yes.

Eiji

On Wed, 12 Mar 2008 06:33:11 -0400
JP Vasseur <jvasseur@cisco.com> wrote:

> Dear WG,
> 
> We discussed about our rechartering during the PCE WG yesterday and there
> was a large consensus for including P2MP (requirements and PCEP protocol
> extensions). It is at this point pre-mature to include further items but the
> discussion should continue on the ML.
> 
> Before finalizing the new proposed charter, we wanted to first confirm the
> consensus on the mailing list.
> 
> In support ?
> 
> Thanks.
> 
> JP.
> 
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce

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


From pce-bounces@ietf.org  Wed Mar 12 07:24:15 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9B1D63A6E63;
	Wed, 12 Mar 2008 07:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.702
X-Spam-Level: 
X-Spam-Status: No, score=-99.702 tagged_above=-999 required=5
	tests=[AWL=-1.565, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 QE1M78s3oydP; Wed, 12 Mar 2008 07:24:11 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B0BF13A6C15;
	Wed, 12 Mar 2008 07:24:11 -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 4201C3A6C15
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 07:24:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 LzrveZzyxZ+Q for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 07:24:10 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id B7E0C3A6BE4
	for <pce@ietf.org>; Wed, 12 Mar 2008 07:24:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,488,1199682000"; 
   d="scan'208";a="1542957"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 12 Mar 2008 10:21:48 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m2CELonC020481; 
	Wed, 12 Mar 2008 10:21:50 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m2CELZuU017882; 
	Wed, 12 Mar 2008 14:21:46 GMT
Received: from xmb-rtp-203.amer.cisco.com ([64.102.31.20]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Mar 2008 10:21:39 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 12 Mar 2008 10:21:51 -0400
Message-ID: <BABC859E6D0B9A4D8448CC7F41CD2B0706180B7E@xmb-rtp-203.amer.cisco.com>
In-Reply-To: <C3FD29A7.2DB58%jvasseur@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pce] Quick Poll on PCE Rechartering
Thread-Index: AciELHgxtwDFHvAfEdy5UAANk8WjQAAH+TmQ
References: <C3FD29A7.2DB58%jvasseur@cisco.com>
From: "Zafar Ali (zali)" <zali@cisco.com>
To: "Jean Philippe Vasseur (jvasseur)" <jvasseur@cisco.com>, <pce@ietf.org>
X-OriginalArrivalTime: 12 Mar 2008 14:21:39.0922 (UTC)
	FILETIME=[63590B20:01C8844C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=957; t=1205331710; x=1206195710;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=zali@cisco.com;
	z=From:=20=22Zafar=20Ali=20(zali)=22=20<zali@cisco.com>
	|Subject:=20RE=3A=20[Pce]=20Quick=20Poll=20on=20PCE=20Recha
	rtering |Sender:=20
	|To:=20=22Jean=20Philippe=20Vasseur=20(jvasseur)=22=20<jvas
	seur@cisco.com>,=20<pce@ietf.org>;
	bh=DwZ2w70yl5THHy1rnbAxf+i2Lur+0TAwL8HfoJpzsgI=;
	b=HroRBi3RcaEJJO3+5vuEl4XjnQ/04pTxGDvCHDb29jeo1lQONYnDrLgl1/
	97Euvjevx+RSZiutxnYRnUe2r7haAeJU4tQDsMld8zb5znat7HvcMlDWYDkz
	My1pStt99k;
Authentication-Results: rtp-dkim-1; header.From=zali@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: rcallon@juniper.net
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

> -----Original Message-----
> From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On 
> Behalf Of Jean Philippe Vasseur (jvasseur)
> Sent: Wednesday, March 12, 2008 6:33 AM
> To: pce@ietf.org
> Cc: rcallon@juniper.net
> Subject: [Pce] Quick Poll on PCE Rechartering
> 
> Dear WG,
> 
> We discussed about our rechartering during the PCE WG 
> yesterday and there was a large consensus for including P2MP 
> (requirements and PCEP protocol extensions). It is at this 
> point pre-mature to include further items but the discussion 
> should continue on the ML.
> 
> Before finalizing the new proposed charter, we wanted to 
> first confirm the consensus on the mailing list.
> 
> In support ?
> 

Yes, 

Thanks

Regards... Zafar 

> Thanks.
> 
> JP.
> 
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
> 
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


From pce-bounces@ietf.org  Wed Mar 12 07:25:22 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A08FF28C30D;
	Wed, 12 Mar 2008 07:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.678
X-Spam-Level: 
X-Spam-Status: No, score=-97.678 tagged_above=-999 required=5
	tests=[AWL=0.459, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 FdjUmzfkWGi6; Wed, 12 Mar 2008 07:25:21 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2DB1B3A6E8B;
	Wed, 12 Mar 2008 07:25:21 -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 601093A6BE4
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 07:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 83YPLZWI8vrq for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 07:25:15 -0700 (PDT)
Received: from tama500.ecl.ntt.co.jp (tama500.ecl.ntt.co.jp [129.60.39.148])
	by core3.amsl.com (Postfix) with ESMTP id 636C928C672
	for <pce@ietf.org>; Wed, 12 Mar 2008 07:25:14 -0700 (PDT)
Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149])
	by tama500.ecl.ntt.co.jp (8.14.2/8.14.2) with ESMTP id
	m2CEMt9b003581; Wed, 12 Mar 2008 23:22:55 +0900 (JST)
Received: from mfs6.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id F249A6BFB;
	Wed, 12 Mar 2008 23:22:54 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (eclscan2.m.ecl.ntt.co.jp
	[129.60.5.68])
	by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id E99886B9E;
	Wed, 12 Mar 2008 23:22:54 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2CEMsD5009036; Wed, 12 Mar 2008 23:22:54 +0900 (JST)
Received: from imb.m.ecl.ntt.co.jp (imb0.m.ecl.ntt.co.jp [129.60.5.140])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2CEMsVb009033; Wed, 12 Mar 2008 23:22:54 +0900 (JST)
Received: from imb.m.ecl.ntt.co.jp (webmail.ecl.ntt.co.jp [129.60.39.130])
	by imb.m.ecl.ntt.co.jp (8.13.8/8.13.8) with SMTP id m2CEMrFE007810;
	Wed, 12 Mar 2008 23:22:53 +0900 (JST)
Message-Id: <200803121422.m2CEMrFE007810@imb.m.ecl.ntt.co.jp>
To: pce@ietf.org
From: "inoue.ichiro@lab.ntt.co.jp" <inoue.ichiro@lab.ntt.co.jp>
Date: Wed, 12 Mar 2008 23:22:53 +0900
In-Reply-To: <47D7D45D.3000400@grotto-networking.com>
X-Mailer: WebMail V3.5.2 PL1
Mime-Version: 1.0
Cc: rcallon@juniper.net
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Yes.

Ichiro

> JP Vasseur wrote:
> > Dear WG,
> >
> > We discussed about our rechartering during the PCE WG yesterday and there
> > was a large consensus for including P2MP (requirements and PCEP protocol
> > extensions). It is at this point pre-mature to include further items but the
> > discussion should continue on the ML.
> >
> > Before finalizing the new proposed charter, we wanted to first confirm the
> > consensus on the mailing list.
> >
> > In support ?
> >
> > Thanks.
> >
> > JP.
> >
> > _______________________________________________
> > Pce mailing list
> > Pce@ietf.org
> > https://www.ietf.org/mailman/listinfo/pce
> >
> > 

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


From pce-bounces@ietf.org  Wed Mar 12 07:40:30 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D998828C3E8;
	Wed, 12 Mar 2008 07:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.218
X-Spam-Level: 
X-Spam-Status: No, score=-99.218 tagged_above=-999 required=5
	tests=[AWL=-1.081, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 Fgc+9c8QdMwa; Wed, 12 Mar 2008 07:40:30 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 319C828C439;
	Wed, 12 Mar 2008 07:40:28 -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 765D13A6E5A
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 07:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 aj1POYixZf6K for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 07:40:25 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211])
	by core3.amsl.com (Postfix) with ESMTP id 12AC928C6E8
	for <pce@ietf.org>; Wed, 12 Mar 2008 07:40:24 -0700 (PDT)
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JXM000ATGNGQ6@usaga01-in.huawei.com> for
	pce@ietf.org; Wed, 12 Mar 2008 07:38:05 -0700 (PDT)
Received: from dan (dhcp-10d3.ietf71.ietf.org [130.129.16.211])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0JXM007CXGNFQ5@usaga01-in.huawei.com> for pce@ietf.org;
	Wed, 12 Mar 2008 07:38:04 -0700 (PDT)
Date: Wed, 12 Mar 2008 22:38:12 +0800
From: Dan Li <danli@huawei.com>
To: JP Vasseur <jvasseur@cisco.com>, pce@ietf.org
Message-id: <00a701c8844e$b32fa9e0$d3108182@dan>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-Priority: 3
X-MSMail-priority: Normal
References: <C3FD29A7.2DB58%jvasseur@cisco.com>
Cc: rcallon@juniper.net
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Yes.

Dan

----- Original Message ----- 
From: "JP Vasseur" <jvasseur@cisco.com>
To: <pce@ietf.org>
Cc: <rcallon@juniper.net>
Sent: Wednesday, March 12, 2008 6:33 PM
Subject: [Pce] Quick Poll on PCE Rechartering


> Dear WG,
>
> We discussed about our rechartering during the PCE WG yesterday and there
> was a large consensus for including P2MP (requirements and PCEP protocol
> extensions). It is at this point pre-mature to include further items but 
> the
> discussion should continue on the ML.
>
> Before finalizing the new proposed charter, we wanted to first confirm the
> consensus on the mailing list.
>
> In support ?
>
> Thanks.
>
> JP.
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce 

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


From pce-bounces@ietf.org  Wed Mar 12 07:48:03 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3854D3A6E6B;
	Wed, 12 Mar 2008 07:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.208
X-Spam-Level: 
X-Spam-Status: No, score=-98.208 tagged_above=-999 required=5
	tests=[AWL=-0.071, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 7Wq67G1uGOQM; Wed, 12 Mar 2008 07:48:01 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12DD428C6EE;
	Wed, 12 Mar 2008 07:47:55 -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 2FEEF3A6E75
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 07:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 sJtc4stXy+xZ for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 07:47:53 -0700 (PDT)
Received: from maild.telecomitalia.it (maild.telecomitalia.it [156.54.233.30])
	by core3.amsl.com (Postfix) with ESMTP id 941FE28C759
	for <pce@ietf.org>; Wed, 12 Mar 2008 07:47:03 -0700 (PDT)
Received: from ptpxch010ba020.idc.cww.telecomitalia.it ([156.54.240.53]) by
	maild.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Wed, 12 Mar 2008 15:44:44 +0100
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.227]) by
	ptpxch010ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 12 Mar 2008 15:44:43 +0100
x-mimeole: Produced By Microsoft MimeOLE V6.00.3790.2992
Importance: normal
Priority: normal
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 12 Mar 2008 15:43:33 +0100
Message-ID: <9E577E61D0108D4F8CD482029B613F5C025DFFB5@PTPEVS108BA020.idc.cww.telecomitalia.it>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Quick Poll on PCE Rechartering
thread-index: AciELHgxtwDFHvAfEdy5UAANk8WjQAAIvpXg
References: <C3FD29A7.2DB58%jvasseur@cisco.com>
From: "Tempia Bonda Alberto" <alberto.tempiabonda@telecomitalia.it>
To: "JP Vasseur" <jvasseur@cisco.com>,
	<pce@ietf.org>
X-OriginalArrivalTime: 12 Mar 2008 14:44:43.0910 (UTC)
	FILETIME=[9C44DA60:01C8844F]
Cc: rcallon@juniper.net
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Yes.
Alberto

________________________________

From: pce-bounces@ietf.org on behalf of JP Vasseur
Sent: Wed 3/12/2008 11:33 AM
To: pce@ietf.org
Cc: rcallon@juniper.net
Subject: [Pce] Quick Poll on PCE Rechartering



Dear WG,

We discussed about our rechartering during the PCE WG yesterday and there
was a large consensus for including P2MP (requirements and PCEP protocol
extensions). It is at this point pre-mature to include further items but the
discussion should continue on the ML.

Before finalizing the new proposed charter, we wanted to first confirm the
consensus on the mailing list.

In support ?

Thanks.

JP.

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


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

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons above and may contain confidential information. If you have received the message in error, be informed that any use of the content hereof is prohibited. Please return it immediately to the sender and delete the message. Should you have any questions, please contact us by replying to webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                        
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


From pce-bounces@ietf.org  Wed Mar 12 07:53:44 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B67BB28C766;
	Wed, 12 Mar 2008 07:53:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.678
X-Spam-Level: 
X-Spam-Status: No, score=-98.678 tagged_above=-999 required=5
	tests=[AWL=-0.540, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 NQfWqXb0EjIB; Wed, 12 Mar 2008 07:53:44 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 592AA3A6E88;
	Wed, 12 Mar 2008 07:53:37 -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 92D6528C790
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 07:53:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 VKqw2vPj8PoQ for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 07:53:34 -0700 (PDT)
Received: from gfi-gw.seabridge.co.il (gfi-gw.seabridge.co.il [212.25.127.231])
	by core3.amsl.com (Postfix) with ESMTP id C35A128C74C
	for <pce@ietf.org>; Wed, 12 Mar 2008 07:52:32 -0700 (PDT)
Received: from dove.seabridge.co.il ([172.30.10.115]) by
	gfi-gw.seabridge.co.il with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Mar 2008 16:50:11 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 12 Mar 2008 16:50:11 +0200
Message-ID: <D3C85156A12AAB4DB23F598007E9826D05B16C65@dove.seabridge.co.il>
In-Reply-To: <406e32c00803120443id9b503dt376676e0979eee4@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pce] Quick Poll on PCE Rechartering
Thread-Index: AciEPejnVSnWlzQrRyqjIMbzLAVASQAAjmCA
From: "Nurit Sprecher" <nurit.sprecher@nsn.com>
To: <pce@ietf.org>
X-OriginalArrivalTime: 12 Mar 2008 14:50:11.0371 (UTC)
	FILETIME=[5F736FB0:01C88450]
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Support,
Nurit

On Wed, Mar 12, 2008 at 6:33 AM, JP Vasseur <jvasseur@cisco.com> wrote:
> Dear WG,
>
>  We discussed about our rechartering during the PCE WG yesterday and
there
>  was a large consensus for including P2MP (requirements and PCEP
protocol
>  extensions). It is at this point pre-mature to include further items
but the
>  discussion should continue on the ML.
>
>  Before finalizing the new proposed charter, we wanted to first
confirm the
>  consensus on the mailing list.
>
>  In support ?
>
>  Thanks.
>
>  JP.
>
>  _______________________________________________
>  Pce mailing list
>  Pce@ietf.org
>  https://www.ietf.org/mailman/listinfo/pce
>
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


From pce-bounces@ietf.org  Wed Mar 12 12:11:33 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 461D228C7C2;
	Wed, 12 Mar 2008 12:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.964
X-Spam-Level: 
X-Spam-Status: No, score=-97.964 tagged_above=-999 required=5
	tests=[AWL=0.173, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 8txORig0DzEQ; Wed, 12 Mar 2008 12:11:33 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE3AE28C7BE;
	Wed, 12 Mar 2008 12:10:40 -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 AAD0428C7BE
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 12:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 0MEOa0CPXOSN for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 12:10:33 -0700 (PDT)
Received: from tama50.ecl.ntt.co.jp (tama50.ecl.ntt.co.jp [129.60.39.147])
	by core3.amsl.com (Postfix) with ESMTP id E2E7128C85F
	for <pce@ietf.org>; Wed, 12 Mar 2008 12:09:22 -0700 (PDT)
Received: from mfs5.rdh.ecl.ntt.co.jp (mfs5.rdh.ecl.ntt.co.jp [129.60.39.144])
	by tama50.ecl.ntt.co.jp (8.14.2/8.14.2) with ESMTP id m2CJ72gh017824;
	Thu, 13 Mar 2008 04:07:02 +0900 (JST)
Received: from mfs5.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs5.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 9916463EE;
	Thu, 13 Mar 2008 04:07:02 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (eclscan2.m.ecl.ntt.co.jp
	[129.60.5.68])
	by mfs5.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 92E0363ED;
	Thu, 13 Mar 2008 04:07:02 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2CJ71Yr029047; Thu, 13 Mar 2008 04:07:02 +0900 (JST)
Received: from imc.m.ecl.ntt.co.jp (imc0.m.ecl.ntt.co.jp [129.60.5.141])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2CJ71JO029042; Thu, 13 Mar 2008 04:07:01 +0900 (JST)
Received: from [127.0.0.1] (neba-hp-shiomoto.nslab.ecl.ntt.co.jp
	[129.60.80.23])
	by imc.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id m2CJ6sw2008680;
	Thu, 13 Mar 2008 04:07:01 +0900 (JST)
Message-ID: <47D82989.6010102@lab.ntt.co.jp>
Date: Thu, 13 Mar 2008 04:05:45 +0900
From: Kohei Shiomoto <shiomoto.kohei@lab.ntt.co.jp>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: JP Vasseur <jvasseur@cisco.com>
References: <C3FD29A7.2DB58%jvasseur@cisco.com>
In-Reply-To: <C3FD29A7.2DB58%jvasseur@cisco.com>
Cc: rcallon@juniper.net, pce@ietf.org
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="utf-8"
Content-Transfer-Encoding: base64
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

WWVzLgoKS29oZWkKCgpKUCBWYXNzZXVyIOOBleOCk+OBr+abuOOBjeOBvuOBl+OBnzoKPiBEZWFy
IFdHLAo+Cj4gV2UgZGlzY3Vzc2VkIGFib3V0IG91ciByZWNoYXJ0ZXJpbmcgZHVyaW5nIHRoZSBQ
Q0UgV0cgeWVzdGVyZGF5IGFuZCB0aGVyZQo+IHdhcyBhIGxhcmdlIGNvbnNlbnN1cyBmb3IgaW5j
bHVkaW5nIFAyTVAgKHJlcXVpcmVtZW50cyBhbmQgUENFUCBwcm90b2NvbAo+IGV4dGVuc2lvbnMp
LiBJdCBpcyBhdCB0aGlzIHBvaW50IHByZS1tYXR1cmUgdG8gaW5jbHVkZSBmdXJ0aGVyIGl0ZW1z
IGJ1dCB0aGUKPiBkaXNjdXNzaW9uIHNob3VsZCBjb250aW51ZSBvbiB0aGUgTUwuCj4KPiBCZWZv
cmUgZmluYWxpemluZyB0aGUgbmV3IHByb3Bvc2VkIGNoYXJ0ZXIsIHdlIHdhbnRlZCB0byBmaXJz
dCBjb25maXJtIHRoZQo+IGNvbnNlbnN1cyBvbiB0aGUgbWFpbGluZyBsaXN0Lgo+Cj4gSW4gc3Vw
cG9ydCA/Cj4KPiBUaGFua3MuCj4KPiBKUC4KPgo+IF9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fCj4gUGNlIG1haWxpbmcgbGlzdAo+IFBjZUBpZXRmLm9yZwo+
IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGNlCj4KPgo+ICAgCi0tIApL
b2hlaSBTaGlvbW90bwpOVFQgTmV0d29yayBTZXJ2aWNlIFN5c3RlbXMgTGFib3JhdG9yaWVzCjMt
OS0xMSBNaWRvcmksIE11c2FzaGlubywgVG9reW8gMTgwLTg1ODUsIEphcGFuClBob25lICs4MSA0
MjIgNTkgNDQwMiBGYXggKzgxIDQyMiA1OSAzNzg3CkZyZWUgb25saW5lIGNvbnRlbnRzIG9mICJO
VFQgVGVjaG5pY2FsIFJldmlldyIgYXZhaWxhYmxlIGF0Cmh0dHBzOi8vd3d3Lm50dC1yZXZpZXcu
anAvCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KUGNl
IG1haWxpbmcgbGlzdApQY2VAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9wY2UK


From pce-bounces@ietf.org  Wed Mar 12 13:03:03 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 74A733A6B54;
	Wed, 12 Mar 2008 13:03:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.72
X-Spam-Level: 
X-Spam-Status: No, score=-97.72 tagged_above=-999 required=5 tests=[AWL=0.417,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	MANGLED_PREMTR=2.3, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 XIZJAm+r61OY; Wed, 12 Mar 2008 13:02:58 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ABA213A6B1E;
	Wed, 12 Mar 2008 13:02:57 -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 0FDCA3A69F8
	for <pce@core3.amsl.com>; Wed, 12 Mar 2008 13:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 hUI9t-Ud+sUS for <pce@core3.amsl.com>;
	Wed, 12 Mar 2008 13:02:55 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [61.144.161.55])
	by core3.amsl.com (Postfix) with ESMTP id 000313A68A3
	for <pce@ietf.org>; Wed, 12 Mar 2008 13:02:54 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JXM00H8UVKQ89@szxga03-in.huawei.com> for
	pce@ietf.org; Thu, 13 Mar 2008 04:00:26 +0800 (CST)
Received: from huawei.com ([172.24.1.3])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JXM00K6RVKPRE@szxga03-in.huawei.com> for
	pce@ietf.org; Thu, 13 Mar 2008 04:00:26 +0800 (CST)
Received: from HuaLiuSC (dhcp-10ee.ietf71.ietf.org [130.129.16.238])
	by szxml01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0JXM002ENVKHR2@szxml01-in.huawei.com> for pce@ietf.org;
	Thu, 13 Mar 2008 04:00:25 +0800 (CST)
Date: Wed, 12 Mar 2008 16:00:41 -0400
From: Autumn Liu <aliu@huawei.com>
In-reply-to: <mailman.5127.1205325294.4957.pce@ietf.org>
To: pce@ietf.org
Message-id: <000501c8847b$c1c842f0$ee108182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Thread-index: AciEPTi/iG/gpM7GSSakSNrFIbumigAPiz0g
References: <mailman.5127.1205325294.4957.pce@ietf.org>
Subject: Re: [Pce] Pce Digest, Vol 43, Issue 7
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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


Yes, support.

Autumn


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

Message: 5
Date: Wed, 12 Mar 2008 06:33:11 -0400
From: JP Vasseur <jvasseur@cisco.com>
Subject: [Pce] Quick Poll on PCE Rechartering
To: <pce@ietf.org>
Cc: rcallon@juniper.net
Message-ID: <C3FD29A7.2DB58%jvasseur@cisco.com>
Content-Type: text/plain;	charset="US-ASCII"

Dear WG,

We discussed about our rechartering during the PCE WG yesterday and there
was a large consensus for including P2MP (requirements and PCEP protocol
extensions). It is at this point pre-mature to include further items but the
discussion should continue on the ML.

Before finalizing the new proposed charter, we wanted to first confirm the
consensus on the mailing list.

In support ?

Thanks.

JP.



****************************


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


From pce-bounces@ietf.org  Thu Mar 13 00:02:38 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EFADF28C717;
	Thu, 13 Mar 2008 00:02:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.328
X-Spam-Level: 
X-Spam-Status: No, score=-98.328 tagged_above=-999 required=5
	tests=[AWL=-0.541, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_EQ_FR=0.35, HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3,
	RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 zWadcSO809v2; Thu, 13 Mar 2008 00:02:33 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 914A928C631;
	Thu, 13 Mar 2008 00:02:32 -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 CB7F43A6BBC
	for <pce@core3.amsl.com>; Thu, 13 Mar 2008 00:02:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 3JwpAr5KHu3M for <pce@core3.amsl.com>;
	Thu, 13 Mar 2008 00:02:27 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com
	[195.101.245.15])
	by core3.amsl.com (Postfix) with ESMTP id 5BC4728C6E8
	for <pce@ietf.org>; Thu, 13 Mar 2008 00:02:10 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 13 Mar 2008 07:59:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 13 Mar 2008 07:59:42 +0100
Message-ID: <D109C8C97C15294495117745780657AE0973DB50@ftrdmel1>
In-Reply-To: <406e32c00803120443id9b503dt376676e0979eee4@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pce] Quick Poll on PCE Rechartering
thread-index: AciENklaIAOQrnmLTm63zcrOZc6qjgAoW8Fw
References: <C3FD29A7.2DB58%jvasseur@cisco.com>
	<406e32c00803120443id9b503dt376676e0979eee4@mail.gmail.com>
From: <jeanlouis.leroux@orange-ftgroup.com>
To: <jvasseur@cisco.com>,
	<rcallon@juniper.net>,
	<pce@ietf.org>
X-OriginalArrivalTime: 13 Mar 2008 06:59:44.0589 (UTC)
	FILETIME=[D1640FD0:01C884D7]
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

In favor

JL =


-----Message d'origine-----
De : pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] De la part de Peng =
He
Envoy=E9 : mercredi 12 mars 2008 12:43
=C0 : JP Vasseur
Cc : rcallon@juniper.net; pce@ietf.org
Objet : Re: [Pce] Quick Poll on PCE Rechartering

Support.

Regards,
Peng

On Wed, Mar 12, 2008 at 6:33 AM, JP Vasseur <jvasseur@cisco.com> wrote:
> Dear WG,
>
>  We discussed about our rechartering during the PCE WG yesterday and =

> there  was a large consensus for including P2MP (requirements and PCEP =

> protocol  extensions). It is at this point pre-mature to include =

> further items but the  discussion should continue on the ML.
>
>  Before finalizing the new proposed charter, we wanted to first =

> confirm the  consensus on the mailing list.
>
>  In support ?
>
>  Thanks.
>
>  JP.
>
>  _______________________________________________
>  Pce mailing list
>  Pce@ietf.org
>  https://www.ietf.org/mailman/listinfo/pce
>
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


From pce-bounces@ietf.org  Fri Mar 14 06:33:28 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 502F328C8EC;
	Fri, 14 Mar 2008 06:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.272
X-Spam-Level: 
X-Spam-Status: No, score=-98.272 tagged_above=-999 required=5
	tests=[AWL=-0.135, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 5tcNz2MazsGk; Fri, 14 Mar 2008 06:33:22 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D3F0B3A6AB5;
	Fri, 14 Mar 2008 06:33:22 -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 5FD973A6F35
	for <pce@core3.amsl.com>; Fri, 14 Mar 2008 06:33:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 GXB0dHDOCSRB for <pce@core3.amsl.com>;
	Fri, 14 Mar 2008 06:33:20 -0700 (PDT)
Received: from pythagoras.zen.co.uk (pythagoras.zen.co.uk [212.23.3.140])
	by core3.amsl.com (Postfix) with ESMTP id 7CFCE3A6AB5
	for <pce@ietf.org>; Fri, 14 Mar 2008 06:33:20 -0700 (PDT)
Received: from [88.96.235.142] (helo=aria-networks.com)
	by pythagoras.zen.co.uk with esmtp (Exim 4.63)
	(envelope-from <daniel.king@aria-networks.com>)
	id 1Ja9zy-0002ra-1j; Fri, 14 Mar 2008 13:31:02 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 14 Mar 2008 13:31:00 -0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <C4C61D8AE3C3E649BE97022FEBE05A881D7C97@hub.aria-networks.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pce] Quick Poll on PCE Rechartering
Thread-Index: AciELHgxtwDFHvAfEdy5UAANk8WjQABqkk5A
References: <C3FD29A7.2DB58%jvasseur@cisco.com>
From: "Daniel King" <daniel.king@aria-networks.com>
To: "JP Vasseur" <jvasseur@cisco.com>,
	<pce@ietf.org>
X-Originating-Pythagoras-IP: [88.96.235.142]
Cc: rcallon@juniper.net
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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 JP et al. 

Yes, I would also support the recharter to include P2MP. 

Thanks, Dan. 

-----Original Message-----
From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of JP
Vasseur
Sent: 12 March 2008 10:33
To: pce@ietf.org
Cc: rcallon@juniper.net
Subject: [Pce] Quick Poll on PCE Rechartering

Dear WG,

We discussed about our rechartering during the PCE WG yesterday and
there
was a large consensus for including P2MP (requirements and PCEP protocol
extensions). It is at this point pre-mature to include further items but
the
discussion should continue on the ML.

Before finalizing the new proposed charter, we wanted to first confirm
the
consensus on the mailing list.

In support ?

Thanks.

JP.

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


From pce-bounces@ietf.org  Fri Mar 14 08:28:15 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 73E8328C432;
	Fri, 14 Mar 2008 08:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.451
X-Spam-Level: 
X-Spam-Status: No, score=-101.451 tagged_above=-999 required=5
	tests=[AWL=-3.081, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RCVD_NUMERIC_HELO=2.067, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 QQ1-oRtMeizn; Fri, 14 Mar 2008 08:28:14 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7166828C155;
	Fri, 14 Mar 2008 08:28: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 0225E3A6999
	for <pce@core3.amsl.com>; Fri, 14 Mar 2008 08:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 527iQM46yKJg for <pce@core3.amsl.com>;
	Fri, 14 Mar 2008 08:28:07 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 4053B3A68A2
	for <pce@ietf.org>; Fri, 14 Mar 2008 08:28:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,501,1199682000"; 
   d="scan'208";a="1787709"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 14 Mar 2008 11:25:49 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m2EFPnK2028393; 
	Fri, 14 Mar 2008 11:25:49 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m2EFPQ0t004477; 
	Fri, 14 Mar 2008 15:25:45 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 14 Mar 2008 11:25:42 -0400
Received: from 161.44.71.244 ([161.44.71.244]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri, 14 Mar 2008 15:25:42 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Fri, 14 Mar 2008 11:25:42 -0400
From: JP Vasseur <jvasseur@cisco.com>
To: <pce@ietf.org>
Message-ID: <C4001136.2E44C%jvasseur@cisco.com>
Thread-Topic: draft-dasgupta-ccamp-path-comp-analysis
Thread-Index: AciF56o76OD/6fHaEdyNXAANk8WjQA==
Mime-version: 1.0
X-OriginalArrivalTime: 14 Mar 2008 15:25:43.0080 (UTC)
	FILETIME=[AADFEA80:01C885E7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=551; t=1205508349; x=1206372349;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20draft-dasgupta-ccamp-path-comp-analysis |Sender:=20
	|To:=20<pce@ietf.org>;
	bh=qYx7bFKmp20wjHrYffYbmMJM2Yw/IRDIDWUZKwNpNhk=;
	b=HxT0ItcvjQ72LJKJeKUpIeRCnRL5Mm3E1iikBnypvO/aNwbpVTv4nniE6Z
	JBXfVRUk0JBznmH8cmhW/VYS8GxKikKbZMkZlrrO4Xt/MSQe9+JyCkVIIWR5
	MOzVQ3Vhti;
Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: rcallon@juniper.net
Subject: [Pce] draft-dasgupta-ccamp-path-comp-analysis
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Dear WG,

Please review and comment draft-dasgupta-ccamp-path-comp-analysis. It has
already be presented in CCAMP with comments and has been updated accordingly
(Adrian and Deborah may poll CCAMP) but because the aim of this document is
to provide some performance analysis comparing the per-domain and PCE-based,
this is of interest for the PCE WG.

Note that, as advised by Ross, this document would follow the individual
submission track with AD sponsorship since it neither in our charter nor in
the charter of CCAMP.

Thanks.

JP.

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


From pce-bounces@ietf.org  Sun Mar 16 13:45:08 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7465928C203;
	Sun, 16 Mar 2008 13:45:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5
	tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ybTDihu2fjBk; Sun, 16 Mar 2008 13:45:04 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B2F403A6DE2;
	Sun, 16 Mar 2008 13:45:04 -0700 (PDT)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 279B73A6DE5; Sun, 16 Mar 2008 13:45:01 -0700 (PDT)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080316204502.279B73A6DE5@core3.amsl.com>
Date: Sun, 16 Mar 2008 13:45:02 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-pcep-11.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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>
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element Working Group of the IETF.


	Title           : Path Computation Element (PCE) Communication Protocol (PCEP)
	Author(s)       : A. Ayyangar, et al.
	Filename        : draft-ietf-pce-pcep-11.txt
	Pages           : 76
	Date            : 2008-03-16

This document specifies the Path Computation Element Communication
Protocol (PCEP) for communications between a Path Computation Client
(PCC) and a Path Computation Element (PCE), or between two PCEs.
Such interactions include path computation requests and path
computation replies as well as notifications of specific states
related to the use of a PCE in the context of Multiprotocol Label
Switching (MPLS) and Generalized (GMPLS) Traffic Engineering.  PCEP
is designed to be flexible and extensible so as to easily allow for
the addition of further messages and objects, should further
requirements be expressed in the future.Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-11.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pce-pcep-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-03-16133450.I-D@ietf.org>


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

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

--NextPart--


From pce-bounces@ietf.org  Sun Mar 16 14:12:46 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A02433A6B91;
	Sun, 16 Mar 2008 14:12:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.605
X-Spam-Level: 
X-Spam-Status: No, score=-100.605 tagged_above=-999 required=5
	tests=[AWL=-0.168, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 zUe2QyNpXirZ; Sun, 16 Mar 2008 14:12:45 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C42383A6A61;
	Sun, 16 Mar 2008 14:12:45 -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 C775F3A6A61
	for <pce@core3.amsl.com>; Sun, 16 Mar 2008 14:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 ajgN0JOLZxW6 for <pce@core3.amsl.com>;
	Sun, 16 Mar 2008 14:12:44 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id A9D0A3A68BE
	for <pce@ietf.org>; Sun, 16 Mar 2008 14:12:43 -0700 (PDT)
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
	m2GLAPBE023185 for <pce@ietf.org>; Sun, 16 Mar 2008 21:10:25 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
	m2GLALVk023152 for <pce@ietf.org>; Sun, 16 Mar 2008 21:10:22 GMT
Message-ID: <00c301c887aa$23bba7f0$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
References: <20080316204502.279B73A6DE5@core3.amsl.com>
Date: Sun, 16 Mar 2008 21:10:13 -0000
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: Re: [Pce] I-D Action:draft-ietf-pce-pcep-11.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

Minor revision to pass idnits and clarify the IANA sections prior to 
publication request.

Diffs at http://www.olddog.co.uk/pcep-diff.htm

Adrian
----- Original Message ----- 
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Cc: <pce@ietf.org>
Sent: Sunday, March 16, 2008 8:45 PM
Subject: [Pce] I-D Action:draft-ietf-pce-pcep-11.txt


>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
> This draft is a work item of the Path Computation Element Working Group of 
> the IETF.
>
>
> Title           : Path Computation Element (PCE) Communication Protocol 
> (PCEP)
> Author(s)       : A. Ayyangar, et al.
> Filename        : draft-ietf-pce-pcep-11.txt
> Pages           : 76
> Date            : 2008-03-16
>
> This document specifies the Path Computation Element Communication
> Protocol (PCEP) for communications between a Path Computation Client
> (PCC) and a Path Computation Element (PCE), or between two PCEs.
> Such interactions include path computation requests and path
> computation replies as well as notifications of specific states
> related to the use of a PCE in the context of Multiprotocol Label
> Switching (MPLS) and Generalized (GMPLS) Traffic Engineering.  PCEP
> is designed to be flexible and extensible so as to easily allow for
> the addition of further messages and objects, should further
> requirements be expressed in the future.Requirements Language
>
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> document are to be interpreted as described in RFC 2119 [RFC2119].
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-11.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>


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


> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
> 


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


From pce-bounces@ietf.org  Sun Mar 16 14:14:44 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4F17F3A69A0;
	Sun, 16 Mar 2008 14:14:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.449
X-Spam-Level: 
X-Spam-Status: No, score=-100.449 tagged_above=-999 required=5
	tests=[AWL=-0.012, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 4js9XXaDYpoh; Sun, 16 Mar 2008 14:14:42 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF8CE3A6DE4;
	Sun, 16 Mar 2008 14:14:42 -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 F2FD83A6DD8;
	Sun, 16 Mar 2008 14:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 wSo3g4l4cpFB; Sun, 16 Mar 2008 14:14:40 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id 0EB143A6B21;
	Sun, 16 Mar 2008 14:14:35 -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
	m2GLCABr001379; Sun, 16 Mar 2008 21:12:10 GMT
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
	m2GLC7lL001367; Sun, 16 Mar 2008 21:12:09 GMT
Message-ID: <00ce01c887aa$6365dfb0$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Ross Callon" <rcallon@juniper.net>
Date: Sun, 16 Mar 2008 21:12:02 -0000
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
Cc: iesg-secretary@iesg.org, pce@ietf.org, dward@cisco.com
Subject: [Pce] Please publish draft-ietf-pce-pcep-11.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

Proto-write-up for draft-ietf-pcep-pcep-11.txt

Intended status : Standards Track

> (1.a)  Who is the Document Shepherd for this document?  Has the
>        Document Shepherd personally reviewed this version of the
>        document and, in particular, does he or she believe this
>        version is ready for forwarding to the IESG for publication?

Adrian Farrel is the document shepherd.
He has personally reviewed the I-D and believes it is ready for forwarding
to the IESG for publication.

> (1.b)  Has the document had adequate review both from key WG members
>        and from key non-WG members?  Does the Document Shepherd have
>        any concerns about the depth or breadth of the reviews that
>        have been performed?

I-D has had very good level of discussions and review. The high version
number is indicative of many small deltas over the last year as reviews and
implementations have discovered nits to be fixed.

> (1.c)  Does the Document Shepherd have concerns that the document
>        needs more review from a particular or broader perspective,
>        e.g., security, operational complexity, someone familiar with
>        AAA, internationalization or XML?

We are aware that the security considerations for a new protocol need
special attention. The I-D has been the subject of several informal security
discussions, and the authors and chairs have attempted to get the security
section right. But the WG feels that a review by the Security Directorate at
the same time as IESG review would be useful to close out any issues.

> (1.d)  Does the Document Shepherd have any specific concerns or
>        issues with this document that the Responsible Area Director
>        and/or the IESG should be aware of?  For example, perhaps he
>        or she is uncomfortable with certain parts of the document, or
>        has concerns whether there really is a need for it.  In any
>        event, if the WG has discussed those issues and has indicated
>        that it still wishes to advance the document, detail those
>        concerns here.  Has an IPR disclosure related to this document
>        been filed?  If so, please include a reference to the
>        disclosure and summarize the WG discussion and conclusion on
>        this issue.

The document is sound.
No IPR disclosure has been filed.

> (1.e)  How solid is the WG consensus behind this document?  Does it
>        represent the strong concurrence of a few individuals, with
>        others being silent, or does the WG as a whole understand and
>        agree with it?

Consensus is comprehensive to the point of unanimity!

> (1.f)  Has anyone threatened an appeal or otherwise indicated extreme
>        discontent?  If so, please summarise the areas of conflict in
>        separate email messages to the Responsible Area Director.  (It
>        should be in a separate email because this questionnaire is
>        entered into the ID Tracker.)

No threats. No discontent.

> (1.g)  Has the Document Shepherd personally verified that the
>        document satisfies all ID nits?  (See
>        http://www.ietf.org/ID-Checklist.html and
>        http://tools.ietf.org/tools/idnits/).  Boilerplate checks are
>        not enough; this check needs to be thorough.  Has the document
>        met all formal review criteria it needs to, such as the MIB
>        Doctor, media type and URI type reviews?

All checks made.

> (1.h)  Has the document split its references into normative and
>        informative?  Are there normative references to documents that
>        are not ready for advancement or are otherwise in an unclear
>        state?  If such normative references exist, what is the
>        strategy for their completion?  Are there normative references
>        that are downward references, as described in [RFC3967]?  If
>        so, list these downward references to support the Area
>        Director in the Last Call procedure for them [RFC3967].

References split.
No downrefs.

> (1.i)  Has the Document Shepherd verified that the document IANA
>        consideration section exists and is consistent with the body
>        of the document?  If the document specifies protocol
>        extensions, are reservations requested in appropriate IANA
>        registries?  Are the IANA registries clearly identified?  If
>        the document creates a new registry, does it define the
>        proposed initial contents of the registry and an allocation
>        procedure for future registrations?  Does it suggest a
>        reasonable name for the new registry?  See [RFC2434].  If the
>        document describes an Expert Review process has Shepherd
>        conferred with the Responsible Area Director so that the IESG
>        can appoint the needed Expert during the IESG Evaluation?

The document defines a new protocol and requests a registry with multiple 
sub-registries. The registries are well documented and named.

> (1.j)  Has the Document Shepherd verified that sections of the
>        document that are written in a formal language, such as XML
>        code, BNF rules, MIB definitions, etc., validate correctly in
>        an automated checker?

The message formats are described in relatively simple BNF. No automated 
checker has been used.

Note that the symbol "|" is used to denote an alternative whereas RFC 5234 
specifies the use of "/". This choice was made deliberately as the "|" 
symbol is found in related RFCs (e.g. RFCs 2205, 3209, 3473).

> (1.k)  The IESG approval announcement includes a Document
>        Announcement Write-Up.  Please provide such a Document
>        Announcement Write-Up.  Recent examples can be found in the
>        "Action" announcements for approved documents.  The approval
>        announcement contains the following sections:
>
>        Technical Summary
>           Relevant content can frequently be found in the abstract
>           and/or introduction of the document.  If not, this may be
>           an indication that there are deficiencies in the abstract
>           or introduction.

RFC4655 describes the motivations and architecture for a Path Computation 
Element (PCE) based model for the computation of Multiprotocol Label 
Switching (MPLS) and Generalized (GMPLS) Traffic Engineering Label Switch 
Paths (TE LSPs).  The model allows for the separation of PCE from Path 
Computation Client (PCC), and allows for the cooperation between PCEs.  This 
necessitates a communication protocol between PCC and PCE, and between PCEs.

RFC4657 states the generic requirements for such a protocol including the 
requirement for using the same protocol between PCC and PCE, and between 
PCEs.

This document specifies the Path Computation Element Communication Protocol 
(PCEP) for communications between a Path Computation Client (PCC) and a Path 
Computation Element (PCE), or between two PCEs. Such interactions include 
path computation requests and path computation replies as well as 
notifications of specific states related to the use of a PCE in the context 
of Multiprotocol Label Switching (MPLS) and Generalized (GMPLS) Traffic 
Engineering. PCEP is designed to be flexible and extensible so as to easily 
allow for the addition of further messages and objects, should further 
requirements be expressed in the future.

>        Working Group Summary
>           Was there anything in WG process that is worth noting?  For
>           example, was there controversy about particular points or
>           were there decisions where the consensus was particularly
>           rough?

WG has thorough consensus with no disputes or disagreements.
At the start of the development of the protocol, a thorough survey was 
conducted into the possible use or re-use of existing protocols. The 
Applications Area was engaged, and several prototypes were produced. But in 
the end it was determined that a new protocol was expeditious.

>        Document Quality
>           Are there existing implementations of the protocol?  Have a
>           significant number of vendors indicated their plan to
>           implement the specification?  Are there any reviewers that
>           merit special mention as having done a thorough review,
>           e.g., one that resulted in important changes or a
>           conclusion that the document had no substantive issues?  If
>           there was a MIB Doctor, Media Type or other expert review,
>           what was its course (briefly)?  In the case of a Media Type
>           review, on what date was the request posted?

There are a substantial number of implementations (around 10 were recorded 
in an informal survey). Some of these are experimental implementations in 
service provider labs, while some are academic projects. Other 
implementations are for hardware and software products and are commercially 
available.

Private interoperability testing has been conducted between at least four of 
these implementations. Initial testing raised important defects in the 
specification (that were fixed). 


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


From pce-bounces@ietf.org  Wed Mar 19 10:30:05 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF3593A6F74;
	Wed, 19 Mar 2008 10:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.594
X-Spam-Level: 
X-Spam-Status: No, score=-102.594 tagged_above=-999 required=5
	tests=[AWL=0.005, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 DrH87TM0kLbr; Wed, 19 Mar 2008 10:30:02 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 05F6B3A6F5A;
	Wed, 19 Mar 2008 10:30:02 -0700 (PDT)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 2C0143A6F5A; Wed, 19 Mar 2008 10:30:00 -0700 (PDT)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080319173001.2C0143A6F5A@core3.amsl.com>
Date: Wed, 19 Mar 2008 10:30:01 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] I-D ACTION:draft-ietf-pce-pcep-xro-04.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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>
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Path Computation Element Working Group of the IETF.

	Title		: Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions
	Author(s)	: E. Oki, A. Farrel
	Filename	: draft-ietf-pce-pcep-xro-04.txt
	Pages		: 16
	Date		: 2008-3-19
	
The Path Computation Element (PCE) provides functions of path 
   computation in support of traffic engineering in Multi-Protocol 
   Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. 
    
   When a Path Computation Client (PCC) requests a PCE for a route, it 
   may be useful for the PCC to specify, as constraints to the path 
   computation, abstract nodes, resources, and Shared Risk Link Groups 
   (SRLGs) that are to be explicitly excluded from the computed route. 
   Such constraints are termed route exclusions. 
   
   The PCE Communication Protocol (PCEP) is designed as a communication 
   protocol between PCCs and PCEs. This document presents PCEP 
   extensions for route exclusions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-xro-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pce-pcep-xro-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-3-19102630.I-D@ietf.org>


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

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

--NextPart--



From pce-bounces@ietf.org  Wed Mar 19 11:19:31 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8991D3A6D11;
	Wed, 19 Mar 2008 11:19:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.239
X-Spam-Level: 
X-Spam-Status: No, score=-98.239 tagged_above=-999 required=5
	tests=[AWL=-0.452, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_EQ_FR=0.35, HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3,
	RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 a4jqxpFBn-GD; Wed, 19 Mar 2008 11:19:27 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C52A43A68FA;
	Wed, 19 Mar 2008 11:19:27 -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 149233A68AC
	for <pce@core3.amsl.com>; Wed, 19 Mar 2008 11:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 2QcFzp12M2X9 for <pce@core3.amsl.com>;
	Wed, 19 Mar 2008 11:19:25 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com
	[195.101.245.15])
	by core3.amsl.com (Postfix) with ESMTP id E80D93A67A3
	for <pce@ietf.org>; Wed, 19 Mar 2008 11:19:23 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Mar 2008 19:15:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 19 Mar 2008 19:15:41 +0100
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB0260568943B@ftrdmel2>
In-Reply-To: <C3FD29A7.2DB58%jvasseur@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pce] Quick Poll on PCE Rechartering
Thread-Index: AciELHgxtwDFHvAfEdy5UAANk8WjQAFvwjOw
References: <C3FD29A7.2DB58%jvasseur@cisco.com>
From: <julien.meuric@orange-ftgroup.com>
To: <jvasseur@cisco.com>,
	<pce@ietf.org>
X-OriginalArrivalTime: 19 Mar 2008 18:15:45.0132 (UTC)
	FILETIME=[3FD642C0:01C889ED]
Cc: rcallon@juniper.net
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Let's echo the rough consensus of the meeting: support.

Julien

-----Original Message-----
From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of JP
Vasseur

Dear WG,

We discussed about our rechartering during the PCE WG yesterday and
there
was a large consensus for including P2MP (requirements and PCEP protocol
extensions). It is at this point pre-mature to include further items but
the
discussion should continue on the ML.

Before finalizing the new proposed charter, we wanted to first confirm
the
consensus on the mailing list.

In support ?

Thanks.

JP.
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


From pce-bounces@ietf.org  Wed Mar 19 12:30:22 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B1AA528C637;
	Wed, 19 Mar 2008 12:30:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.218
X-Spam-Level: 
X-Spam-Status: No, score=-99.218 tagged_above=-999 required=5
	tests=[AWL=-1.081, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 4FvFUXiqCXxp; Wed, 19 Mar 2008 12:30:22 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A065D28C46F;
	Wed, 19 Mar 2008 12:30:17 -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 4F82C28C46F
	for <pce@core3.amsl.com>; Wed, 19 Mar 2008 12:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 mmSkMr8U45-G for <pce@core3.amsl.com>;
	Wed, 19 Mar 2008 12:30:15 -0700 (PDT)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180])
	by core3.amsl.com (Postfix) with ESMTP id 8D5CD3A6F1A
	for <pce@ietf.org>; Wed, 19 Mar 2008 12:30:13 -0700 (PDT)
Received: from huawei.com (usaga04-in [172.18.9.16])
	by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JXZ0066LSQEQD@usaga04-in.huawei.com> for
	pce@ietf.org; Wed, 19 Mar 2008 14:27:50 -0500 (CDT)
Received: from huaweicf6146f5 ([10.192.21.51])
	by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JXZ00FHWSQC2N@usaga04-in.huawei.com> for
	pce@ietf.org; Wed, 19 Mar 2008 14:27:50 -0500 (CDT)
Date: Wed, 19 Mar 2008 14:27:47 -0500
From: Quintin Zhao <qzhao@huawei.com>
In-reply-to: <mailman.37.1205953205.4901.pce@ietf.org>
To: pce@ietf.org
Message-id: <002901c889f7$51102880$3815c00a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Thread-index: AciJ8y58U5c5j19yRi+jKbvLtT+tbwAAzydw
References: <mailman.37.1205953205.4901.pce@ietf.org>
Cc: rcallon@juniper.net
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Yes.

Quintin

-----Original Message-----
From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of JP
Vasseur

Dear WG,

We discussed about our rechartering during the PCE WG yesterday and
there
was a large consensus for including P2MP (requirements and PCEP protocol
extensions). It is at this point pre-mature to include further items but
the
discussion should continue on the ML.

Before finalizing the new proposed charter, we wanted to first confirm
the
consensus on the mailing list.

In support ?

Thanks.

JP.


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

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

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


From pce-bounces@ietf.org  Thu Mar 20 00:30:51 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A13CE28C104;
	Thu, 20 Mar 2008 00:30:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.678
X-Spam-Level: 
X-Spam-Status: No, score=-98.678 tagged_above=-999 required=5
	tests=[AWL=-0.540, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MANGLED_PREMTR=2.3, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 Apva-F0XG-Jz; Thu, 20 Mar 2008 00:30:50 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CFF913A6D38;
	Thu, 20 Mar 2008 00:30:50 -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 EC94A28C104
	for <pce@core3.amsl.com>; Thu, 20 Mar 2008 00:30:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 A5579tKxRym2 for <pce@core3.amsl.com>;
	Thu, 20 Mar 2008 00:30:49 -0700 (PDT)
Received: from bizpsie4.9services.com (bizpsie4.9services.com [84.96.93.162])
	by core3.amsl.com (Postfix) with ESMTP id D12323A6892
	for <pce@ietf.org>; Thu, 20 Mar 2008 00:30:48 -0700 (PDT)
Received: from pooky.marben-products.com ([86.65.15.130])
	by bizpsie4.9services.com with 9services
	id 3KUV1Z0022oN1dS0400000; Thu, 20 Mar 2008 08:28:29 +0100
X-Biz3: ??
X-VRSPAM-SCORE: -200.00
Received: from AOFR11476 (aofr11476.marben-products.com [192.168.7.180])
	by pooky.marben-products.com (8.14.0/8.14.0) with ESMTP id
	m2K7SSH3007273; Thu, 20 Mar 2008 08:28:28 +0100
From: "Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com>
To: "'JP Vasseur'" <jvasseur@cisco.com>, <pce@ietf.org>
Date: Thu, 20 Mar 2008 08:27:19 +0100
Message-ID: <000b01c88a5b$d7d02aa0$b407a8c0@marbenproducts.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <C3FD29A7.2DB58%jvasseur@cisco.com>
Thread-Index: AciELHgxtwDFHvAfEdy5UAANk8WjQAGL1C6Q
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Cc: rcallon@juniper.net
Subject: Re: [Pce] Quick Poll on PCE Rechartering
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Yes

Fabien

> -----Message d'origine-----
> De=A0: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] De la part de JP
> Vasseur
> Envoy=E9=A0: mercredi 12 mars 2008 11:33
> =C0=A0: pce@ietf.org
> Cc=A0: rcallon@juniper.net
> Objet=A0: [Pce] Quick Poll on PCE Rechartering
> =

> Dear WG,
> =

> We discussed about our rechartering during the PCE WG yesterday and there
> was a large consensus for including P2MP (requirements and PCEP protocol
> extensions). It is at this point pre-mature to include further items but
> the
> discussion should continue on the ML.
> =

> Before finalizing the new proposed charter, we wanted to first confirm the
> consensus on the mailing list.
> =

> In support ?
> =

> Thanks.
> =

> JP.
> =

> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce

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


From pce-bounces@ietf.org  Thu Mar 20 00:52:56 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5F3793A6C2A;
	Thu, 20 Mar 2008 00:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.924
X-Spam-Level: 
X-Spam-Status: No, score=-99.924 tagged_above=-999 required=5
	tests=[AWL=0.513, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 k3vEAi23rz6F; Thu, 20 Mar 2008 00:52:55 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 865EC3A6B03;
	Thu, 20 Mar 2008 00:52:55 -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 689A03A6A12
	for <pce@core3.amsl.com>; Thu, 20 Mar 2008 00:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 XGcsA14Lso0c for <pce@core3.amsl.com>;
	Thu, 20 Mar 2008 00:52:51 -0700 (PDT)
Received: from bizpsie3.9services.com (bizpsie3.9services.com [84.96.93.161])
	by core3.amsl.com (Postfix) with ESMTP id A0A653A6821
	for <pce@ietf.org>; Thu, 20 Mar 2008 00:52:50 -0700 (PDT)
Received: from pooky.marben-products.com ([86.65.15.130])
	by bizpsie3.9services.com with 9services
	id 3KqX1Z0072oN1dS0300000; Thu, 20 Mar 2008 08:50:32 +0100
X-Biz3: ??
X-VRSPAM-SCORE: -80.00
Received: from AOFR11476 (aofr11476.marben-products.com [192.168.7.180])
	by pooky.marben-products.com (8.14.0/8.14.0) with ESMTP id
	m2K7oVmh007406 for <pce@ietf.org>; Thu, 20 Mar 2008 08:50:31 +0100
From: "Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com>
To: <pce@ietf.org>
Date: Thu, 20 Mar 2008 08:49:21 +0100
Message-ID: <000c01c88a5e$ebcae240$b407a8c0@marbenproducts.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <20080319173001.2C0143A6F5A@core3.amsl.com>
Thread-Index: AciJ5o4fH6QB1Y0tQCKIb3QmDd3vGAAd037Q
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: Re: [Pce] I-D ACTION:draft-ietf-pce-pcep-xro-04.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org


Hi,

Sorry to come back on this subject but it is still not clear to me why we
are using different subobject types between XRO and ERO/RRO/IRO in PCEP.

Is there any particular reason?

In http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-11.txt
     Type   Subobject
        1   IPv4 prefix
        2   IPv6 prefix
        4   Unnumbered Interface ID
       32   Autonomous system number

In http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-xro-04.txt

        Type           Subobject =

        -------------+------------------------------- =

        1              IPv4 prefix =

        2              IPv6 prefix =

        3              Unnumbered Interface ID =

        4              Autonomous system number =

        5              SRLG


Thanks
Fabien


> -----Message d'origine-----
> De=A0: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] De la part de
> Internet-Drafts@ietf.org
> Envoy=E9=A0: mercredi 19 mars 2008 18:30
> =C0=A0: i-d-announce@ietf.org
> Cc=A0: pce@ietf.org
> Objet=A0: [Pce] I-D ACTION:draft-ietf-pce-pcep-xro-04.txt
> =

> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Path Computation Element Working Group of
> the IETF.
> =

> 	Title		: Extensions to the Path Computation Element
> Communication Protocol (PCEP) for Route Exclusions
> 	Author(s)	: E. Oki, A. Farrel
> 	Filename	: draft-ietf-pce-pcep-xro-04.txt
> 	Pages		: 16
> 	Date		: 2008-3-19
> =

> The Path Computation Element (PCE) provides functions of path
>    computation in support of traffic engineering in Multi-Protocol
>    Label Switching (MPLS) and Generalized MPLS (GMPLS) networks.
> =

>    When a Path Computation Client (PCC) requests a PCE for a route, it
>    may be useful for the PCC to specify, as constraints to the path
>    computation, abstract nodes, resources, and Shared Risk Link Groups
>    (SRLGs) that are to be explicitly excluded from the computed route.
>    Such constraints are termed route exclusions.
> =

>    The PCE Communication Protocol (PCEP) is designed as a communication
>    protocol between PCCs and PCEs. This document presents PCEP
>    extensions for route exclusions.
> =

> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-xro-04.txt
> =

> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> =

> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.

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


From pce-bounces@ietf.org  Thu Mar 20 09:25:40 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC47D28C165;
	Thu, 20 Mar 2008 09:25:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.324
X-Spam-Level: 
X-Spam-Status: No, score=-100.324 tagged_above=-999 required=5
	tests=[AWL=0.113, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 djyrI3TmasHO; Thu, 20 Mar 2008 09:25:36 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 257C328C5AD;
	Thu, 20 Mar 2008 09:25:36 -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 75CC128C21C
	for <pce@core3.amsl.com>; Thu, 20 Mar 2008 09:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 nD7kcAqmBZz1 for <pce@core3.amsl.com>;
	Thu, 20 Mar 2008 09:25:33 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id 060C53A6CA9
	for <pce@ietf.org>; Thu, 20 Mar 2008 09:25:12 -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
	m2KGMlet028281 for <pce@ietf.org>; Thu, 20 Mar 2008 16:22:51 GMT
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
	m2KGMjlY028271 for <pce@ietf.org>; Thu, 20 Mar 2008 16:22:46 GMT
Message-ID: <096201c88aa6$a06ad7e0$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Thu, 20 Mar 2008 16:21:18 -0000
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] PCEP Codepoints
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,

ATTENTION!
Authors of PCEP, XRO, BRPC and Path-Key.

I updated the temporary registry at http://www.olddog.co.uk/pce.htm

This is based on pcep-11 xro-04, brpc-05, and path-key-02

What I found was...

PCEP is a bit of a mess, sometimes numbering bits from most-significant and 
sometimes numbering from least-significant. Sometimes the count starts at 
zero, sometimes at one. I believe I have reproduced what the PCEP draft 
says, but do we want to fix it? It's probable that IANA will get confused 
unless we get some consistency.

Maybe best to count all bits left-to-right (most to least significant) 
starting at zero. This seems to be the usual IETF way.

Maybe good to also show the hex for each bit.

That would be a revision of PCEP, but it would fit in the review cycle if it 
was done quickly.


I believe I also found two points of confusion in BRPC...

14.1 defines the VSPT (V-bit) as
"Bit Number: 10
 Value: 0x60"
I may be old, but I am not aware of a way to encode 0x60 as a single bit.
Note also, however, that the registry for "Request Parameters Bit Flags" has 
a couple of unassigned bits. Maybe you'd like to close the gap?

14.2 assigns a new bit as
"Bit number (suggested value): 0x04"
If this is supposed to be the bit number (i.e. it number 4) this fits with 
the PCEP registry. But if it is supposed to be the hex representation of the 
bit-field note that PCEP says that the count starts at zero and assigns bits 
1, 2, and 3. So 0x04 is already assigned.


In Path-Key section 7.3, I found the RP object bits numbered from the other 
end.
In section 7.4, there is an allocaiton from the No-Path Vector TLV bit 
flags, and an attempt is made to allocate bit 1. This is already in use for 
PCEP.


Please fix drafts and let me know the updates.

Thanks,
Adrian 


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


From pce-bounces@ietf.org  Thu Mar 20 17:30:27 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4C09928C3ED;
	Thu, 20 Mar 2008 17:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.919
X-Spam-Level: 
X-Spam-Status: No, score=-99.919 tagged_above=-999 required=5
	tests=[AWL=0.518, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 YqUuQrcNPELV; Thu, 20 Mar 2008 17:30:26 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 659D03A6B87;
	Thu, 20 Mar 2008 17:30:26 -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 9A79B3A6BB6
	for <pce@core3.amsl.com>; Thu, 20 Mar 2008 17:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 vInX76Jx24oX for <pce@core3.amsl.com>;
	Thu, 20 Mar 2008 17:30:24 -0700 (PDT)
Received: from tama50.ecl.ntt.co.jp (tama50.ecl.ntt.co.jp [129.60.39.147])
	by core3.amsl.com (Postfix) with ESMTP id 9A0F73A6AC8
	for <pce@ietf.org>; Thu, 20 Mar 2008 17:30:24 -0700 (PDT)
Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149])
	by tama50.ecl.ntt.co.jp (8.14.2/8.14.2) with ESMTP id m2L0S5Ua012096;
	Fri, 21 Mar 2008 09:28:05 +0900 (JST)
Received: from mfs6.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id DDD226BFF;
	Fri, 21 Mar 2008 09:28:05 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (eclscan2.m.ecl.ntt.co.jp
	[129.60.5.68])
	by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id BCCDC6BFB;
	Fri, 21 Mar 2008 09:28:05 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2L0S5D2026862; Fri, 21 Mar 2008 09:28:05 +0900 (JST)
Received: from ipb0.m.ecl.ntt.co.jp (ipb0.m.ecl.ntt.co.jp [129.60.5.155])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2L0S4At026853; Fri, 21 Mar 2008 09:28:05 +0900 (JST)
Received: from [129.60.80.54] ([129.60.80.54])
	by ipb0.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id m2L0S4jr013744;
	Fri, 21 Mar 2008 09:28:04 +0900 (JST)
Date: Fri, 21 Mar 2008 09:27:24 +0900
From: Eiji Oki <oki.eiji@lab.ntt.co.jp>
To: "Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com>
In-Reply-To: <000c01c88a5e$ebcae240$b407a8c0@marbenproducts.com>
References: <20080319173001.2C0143A6F5A@core3.amsl.com>
	<000c01c88a5e$ebcae240$b407a8c0@marbenproducts.com>
Message-Id: <20080321092603.D61E.OKI.EIJI@lab.ntt.co.jp>
MIME-Version: 1.0
X-Mailer: Becky! ver. 2.30.04 [ja]
Cc: pce@ietf.org
Subject: Re: [Pce] I-D ACTION:draft-ietf-pce-pcep-xro-04.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Fabien, 

Yes, you are right. We should match the base PCEP spec.
We will change 3 to 4, 4 to 32, and 5 to 34.
Is it OK to make this change during working group last call?

Thank you.
Eiji

On Thu, 20 Mar 2008 08:49:21 +0100
"Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com> wrote:

> 
> Hi,
> 
> Sorry to come back on this subject but it is still not clear to me why we
> are using different subobject types between XRO and ERO/RRO/IRO in PCEP.
> 
> Is there any particular reason?
> 
> In http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-11.txt
>      Type   Subobject
>         1   IPv4 prefix
>         2   IPv6 prefix
>         4   Unnumbered Interface ID
>        32   Autonomous system number
> 
> In http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-xro-04.txt
> 
>         Type           Subobject 
>         -------------+------------------------------- 
>         1              IPv4 prefix 
>         2              IPv6 prefix 
>         3              Unnumbered Interface ID 
>         4              Autonomous system number 
>         5              SRLG
> 
> 
> Thanks
> Fabien
> 
> 
> > -----Message d'origine-----
> > De?: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] De la part de
> > Internet-Drafts@ietf.org
> > Envoy$Br"(B: mercredi 19 mars 2008 18:30
> > $B%?(B?: i-d-announce@ietf.org
> > Cc?: pce@ietf.org
> > Objet?: [Pce] I-D ACTION:draft-ietf-pce-pcep-xro-04.txt
> > 
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > This draft is a work item of the Path Computation Element Working Group of
> > the IETF.
> > 
> > 	Title		: Extensions to the Path Computation Element
> > Communication Protocol (PCEP) for Route Exclusions
> > 	Author(s)	: E. Oki, A. Farrel
> > 	Filename	: draft-ietf-pce-pcep-xro-04.txt
> > 	Pages		: 16
> > 	Date		: 2008-3-19
> > 
> > The Path Computation Element (PCE) provides functions of path
> >    computation in support of traffic engineering in Multi-Protocol
> >    Label Switching (MPLS) and Generalized MPLS (GMPLS) networks.
> > 
> >    When a Path Computation Client (PCC) requests a PCE for a route, it
> >    may be useful for the PCC to specify, as constraints to the path
> >    computation, abstract nodes, resources, and Shared Risk Link Groups
> >    (SRLGs) that are to be explicitly excluded from the computed route.
> >    Such constraints are termed route exclusions.
> > 
> >    The PCE Communication Protocol (PCEP) is designed as a communication
> >    protocol between PCCs and PCEs. This document presents PCEP
> >    extensions for route exclusions.
> > 
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-xro-04.txt
> > 
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> > 
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> 
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce

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


From pce-bounces@ietf.org  Fri Mar 21 12:11:29 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B5A6828C149;
	Fri, 21 Mar 2008 12:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.452
X-Spam-Level: 
X-Spam-Status: No, score=-102.452 tagged_above=-999 required=5
	tests=[AWL=-2.059, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044,
	FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 pcXMnYGnelMF; Fri, 21 Mar 2008 12:11:27 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 742C83A694B;
	Fri, 21 Mar 2008 12:11:27 -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 90F483A6A05
	for <pce@core3.amsl.com>; Fri, 21 Mar 2008 12:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 7JXDRxjBwwOm for <pce@core3.amsl.com>;
	Fri, 21 Mar 2008 12:11:23 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 924CF3A694B
	for <pce@ietf.org>; Fri, 21 Mar 2008 12:11:23 -0700 (PDT)
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 21 Mar 2008 12:09:06 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m2LJ964s030003; 
	Fri, 21 Mar 2008 12:09:06 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m2LJ95sH022993;
	Fri, 21 Mar 2008 19:09:05 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 21 Mar 2008 15:09:05 -0400
Received: from 10.86.104.186 ([10.86.104.186]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri, 21 Mar 2008 19:09:04 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Fri, 21 Mar 2008 10:28:31 -0400
From: JP Vasseur <jvasseur@cisco.com>
To: Adrian Farrel <adrian@olddog.co.uk>, <rbradfor@cisco.com>
Message-ID: <C4093E4F.2F9B3%jvasseur@cisco.com>
Thread-Topic: [Pce] PCEP Codepoints
Thread-Index: AciLX9YWFGnXt/dTEdyNXAANk8WjQA==
In-Reply-To: <096201c88aa6$a06ad7e0$0200a8c0@your029b8cecfe>
Mime-version: 1.0
X-OriginalArrivalTime: 21 Mar 2008 19:09:05.0372 (UTC)
	FILETIME=[0827A1C0:01C88B87]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3049; t=1206126546;
	x=1206990546; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20Re=3A=20[Pce]=20PCEP=20Codepoints |Sender:=20;
	bh=0o2rvPvMnlUmMkxsJZxFICniTX/KbsImooEiAdut/Rc=;
	b=sMxyC2p7mtNBwJuo+TC4B9f1wMv0zQZMfvm2j1NMJ9eFE2Fyk4NT4eupQO
	510Rak8KgPHzgpBZ6z7bfssGSvKuMLjSv8KP5TgpZLIQR0Z/2SUXeDP28Iuu
	RG4lpWEY/e;
Authentication-Results: sj-dkim-4; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: pce@ietf.org
Subject: Re: [Pce] PCEP Codepoints
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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 Adrian,


> From: Adrian Farrel <adrian@olddog.co.uk>
> Reply-To: Adrian Farrel <adrian@olddog.co.uk>
> Date: Thu, 20 Mar 2008 16:21:18 -0000
> To: <pce@ietf.org>
> Subject: [Pce] PCEP Codepoints
> 
> Hi,
> 
> ATTENTION!
> Authors of PCEP, XRO, BRPC and Path-Key.
> 
> I updated the temporary registry at http://www.olddog.co.uk/pce.htm
> 
> This is based on pcep-11 xro-04, brpc-05, and path-key-02
> 
> What I found was...
> 
> PCEP is a bit of a mess, sometimes numbering bits from most-significant and
> sometimes numbering from least-significant. Sometimes the count starts at
> zero, sometimes at one. I believe I have reproduced what the PCEP draft
> says, but do we want to fix it? It's probable that IANA will get confused
> unless we get some consistency.

Let me look at it, not sure that we need any change though.

> 
> Maybe best to count all bits left-to-right (most to least significant)
> starting at zero. This seems to be the usual IETF way.
> 
> Maybe good to also show the hex for each bit.
> 
> That would be a revision of PCEP, but it would fit in the review cycle if it
> was done quickly.
> 
> 
> I believe I also found two points of confusion in BRPC...
> 
> 14.1 defines the VSPT (V-bit) as
> "Bit Number: 10
>  Value: 0x60"
> I may be old, but I am not aware of a way to encode 0x60 as a single bit.
> Note also, however, that the registry for "Request Parameters Bit Flags" has
> a couple of unassigned bits. Maybe you'd like to close the gap?
> 
> 14.2 assigns a new bit as
> "Bit number (suggested value): 0x04"
> If this is supposed to be the bit number (i.e. it number 4) this fits with
> the PCEP registry. But if it is supposed to be the hex representation of the
> bit-field note that PCEP says that the count starts at zero and assigns bits
> 1, 2, and 3. So 0x04 is already assigned.
> 

We fixed those issues in version -07 (February 8, 2008).

15.1.  New flag of the RP object

   A new flag of the RP object (specified in [I-D.ietf-pce-pcep]) is
   defined in this document.

   VSPT Flag
   Bit Number      Name Flag    Reference
     7                VSPT      This document


15.3.  New flag of the NO-PATH-VECTOR TLV

   A new flag of the NO-PATH-VECTOR TLV defined in [I-D.ietf-pce-pcep])
   is specified in this document.

    Bit number  Meaning                  Reference

       4        BRPC Path computation   This document
                chain unavailable

> 
> In Path-Key section 7.3, I found the RP object bits numbered from the other
> end.
> In section 7.4, there is an allocaiton from the No-Path Vector TLV bit
> flags, and an attempt is made to allocate bit 1. This is already in use for
> PCEP.

Richard, could you fix it in the next revision (thanks) ?

Cheers,

JP.

> 
> 
> Please fix drafts and let me know the updates.
> 
> Thanks,
> Adrian 
> 
> 
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce

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


From pce-bounces@ietf.org  Fri Mar 21 12:26:46 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D672F28C22F;
	Fri, 21 Mar 2008 12:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.677
X-Spam-Level: 
X-Spam-Status: No, score=-101.677 tagged_above=-999 required=5
	tests=[AWL=-1.240, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 tXS+w+xJZTRI; Fri, 21 Mar 2008 12:26:45 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C35713A6C1C;
	Fri, 21 Mar 2008 12:26:45 -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 72E873A681F
	for <pce@core3.amsl.com>; Fri, 21 Mar 2008 12:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 ApADslzQCjaV for <pce@core3.amsl.com>;
	Fri, 21 Mar 2008 12:26:41 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 56F8428C164
	for <pce@ietf.org>; Fri, 21 Mar 2008 12:26:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,536,1199692800"; d="scan'208";a="18222974"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 21 Mar 2008 12:24:23 -0700
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m2LJONZA014416; 
	Fri, 21 Mar 2008 12:24:23 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m2LJONAj020748;
	Fri, 21 Mar 2008 19:24:23 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 21 Mar 2008 15:24:22 -0400
Received: from 10.86.104.186 ([10.86.104.186]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri, 21 Mar 2008 19:24:22 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Fri, 21 Mar 2008 15:24:18 -0400
From: JP Vasseur <jvasseur@cisco.com>
To: Eiji Oki <oki.eiji@lab.ntt.co.jp>,
	Fabien Verhaeghe <fabien.verhaeghe@marben-products.com>
Message-ID: <C40983A2.2FBB0%jvasseur@cisco.com>
Thread-Topic: [Pce] I-D ACTION:draft-ietf-pce-pcep-xro-04.txt
Thread-Index: AciLiSgfZryK0fd8EdyNXAANk8WjQA==
In-Reply-To: <20080321092603.D61E.OKI.EIJI@lab.ntt.co.jp>
Mime-version: 1.0
X-OriginalArrivalTime: 21 Mar 2008 19:24:22.0927 (UTC)
	FILETIME=[2B0F69F0:01C88B89]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3762; t=1206127463;
	x=1206991463; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20Re=3A=20[Pce]=20I-D=20ACTION=3Adraft-ietf-pce-p
	cep-xro-04.txt |Sender:=20;
	bh=D7Sp9T+7IaVohC6RfegXcz9Z73OaED5VzVB8K5y/qFE=;
	b=LWPOu4FaRIKaXazK4xdP/uwWwqzKUdWF6O9jCTAnpHenDKy+rgn61LeeKR
	9Mhusw587htw3IlR6UBvxz+sdCwjh5lMj4vFe3TQJebD2rV/UXj6rn/7aKAW
	JI+6UYeFra;
Authentication-Results: sj-dkim-2; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: pce@ietf.org
Subject: Re: [Pce] I-D ACTION:draft-ietf-pce-pcep-xro-04.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi Eiji,


> From: Eiji Oki <oki.eiji@lab.ntt.co.jp>
> Date: Fri, 21 Mar 2008 09:27:24 +0900
> To: Fabien Verhaeghe <fabien.verhaeghe@marben-products.com>
> Cc: <pce@ietf.org>
> Subject: Re: [Pce] I-D ACTION:draft-ietf-pce-pcep-xro-04.txt
> 
> Fabien, 
> 
> Yes, you are right. We should match the base PCEP spec.
> We will change 3 to 4, 4 to 32, and 5 to 34.
> Is it OK to make this change during working group last call?

If OK with you I would suggest to make the change now, and we will then Last
Call the document.

Thanks.

JP.

> 
> Thank you.
> Eiji
> 
> On Thu, 20 Mar 2008 08:49:21 +0100
> "Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com> wrote:
> 
>> 
>> Hi,
>> 
>> Sorry to come back on this subject but it is still not clear to me why we
>> are using different subobject types between XRO and ERO/RRO/IRO in PCEP.
>> 
>> Is there any particular reason?
>> 
>> In http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-11.txt
>>      Type   Subobject
>>         1   IPv4 prefix
>>         2   IPv6 prefix
>>         4   Unnumbered Interface ID
>>        32   Autonomous system number
>> 
>> In http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-xro-04.txt
>> 
>>         Type           Subobject
>>         -------------+-------------------------------
>>         1              IPv4 prefix
>>         2              IPv6 prefix
>>         3              Unnumbered Interface ID
>>         4              Autonomous system number
>>         5              SRLG
>> 
>> 
>> Thanks
>> Fabien
>> 
>> 
>>> -----Message d'origine-----
>>> De?: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] De la part de
>>> Internet-Drafts@ietf.org
>>> Envoy$Br"(B: mercredi 19 mars 2008 18:30
>>> $B%?(B?: i-d-announce@ietf.org
>>> Cc?: pce@ietf.org
>>> Objet?: [Pce] I-D ACTION:draft-ietf-pce-pcep-xro-04.txt
>>> 
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>> This draft is a work item of the Path Computation Element Working Group of
>>> the IETF.
>>> 
>>> Title  : Extensions to the Path Computation Element
>>> Communication Protocol (PCEP) for Route Exclusions
>>> Author(s) : E. Oki, A. Farrel
>>> Filename : draft-ietf-pce-pcep-xro-04.txt
>>> Pages  : 16
>>> Date  : 2008-3-19
>>> 
>>> The Path Computation Element (PCE) provides functions of path
>>>    computation in support of traffic engineering in Multi-Protocol
>>>    Label Switching (MPLS) and Generalized MPLS (GMPLS) networks.
>>> 
>>>    When a Path Computation Client (PCC) requests a PCE for a route, it
>>>    may be useful for the PCC to specify, as constraints to the path
>>>    computation, abstract nodes, resources, and Shared Risk Link Groups
>>>    (SRLGs) that are to be explicitly excluded from the computed route.
>>>    Such constraints are termed route exclusions.
>>> 
>>>    The PCE Communication Protocol (PCEP) is designed as a communication
>>>    protocol between PCCs and PCEs. This document presents PCEP
>>>    extensions for route exclusions.
>>> 
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-xro-04.txt
>>> 
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>> 
>>> Below is the data which will enable a MIME compliant mail reader
>>> implementation to automatically retrieve the ASCII version of the
>>> Internet-Draft.
>> 
>> _______________________________________________
>> Pce mailing list
>> Pce@ietf.org
>> https://www.ietf.org/mailman/listinfo/pce
> 
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce

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


From pce-bounces@ietf.org  Fri Mar 21 13:21:37 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AEDA628C423;
	Fri, 21 Mar 2008 13:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.38
X-Spam-Level: 
X-Spam-Status: No, score=-100.38 tagged_above=-999 required=5
	tests=[AWL=0.057, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 6U6MeZY0k6Nk; Fri, 21 Mar 2008 13:21:36 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0631328C22B;
	Fri, 21 Mar 2008 13:21:36 -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 D172128C22B
	for <pce@core3.amsl.com>; Fri, 21 Mar 2008 13:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 xcurOJULsjoy for <pce@core3.amsl.com>;
	Fri, 21 Mar 2008 13:21:34 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id CF5CA28C1A4
	for <pce@ietf.org>; Fri, 21 Mar 2008 13:21:33 -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
	m2LKIrQ1025231; Fri, 21 Mar 2008 20:18:57 GMT
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
	m2LKIpQx025224; Fri, 21 Mar 2008 20:18:53 GMT
Message-ID: <0be101c88b90$c5830a30$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "JP Vasseur" <jvasseur@cisco.com>
References: <C4093E4F.2F9B3%jvasseur@cisco.com>
Date: Fri, 21 Mar 2008 20:18:09 -0000
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
Cc: pce@ietf.org
Subject: Re: [Pce] PCEP Codepoints
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

>> I believe I also found two points of confusion in BRPC...
>
> We fixed those issues in version -07 (February 8, 2008).

Indeed!

If you are so clever, can you explain why I was looking at the wrong version 
of this I-D?

Temporary registry updated.

Adrian 


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


From pce-bounces@ietf.org  Fri Mar 21 13:25:01 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 90C083A6DE6;
	Fri, 21 Mar 2008 13:25:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.228
X-Spam-Level: 
X-Spam-Status: No, score=-101.228 tagged_above=-999 required=5
	tests=[AWL=-0.791, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 2KN137CXy1Q9; Fri, 21 Mar 2008 13:25:00 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BBFB23A6DE2;
	Fri, 21 Mar 2008 13:25:00 -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 9D1003A6C2F
	for <pce@core3.amsl.com>; Fri, 21 Mar 2008 13:24:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 q-dW6jZdrmzh for <pce@core3.amsl.com>;
	Fri, 21 Mar 2008 13:24:59 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id AD2B73A67D7
	for <pce@ietf.org>; Fri, 21 Mar 2008 13:24:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,537,1199682000"; 
   d="scan'208";a="2710180"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 21 Mar 2008 16:22:40 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m2LKMeSI023005; 
	Fri, 21 Mar 2008 16:22:40 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m2LKMeSe015169;
	Fri, 21 Mar 2008 20:22:40 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 21 Mar 2008 16:22:40 -0400
Received: from 10.86.104.186 ([10.86.104.186]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri, 21 Mar 2008 20:22:40 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Fri, 21 Mar 2008 16:22:39 -0400
From: JP Vasseur <jvasseur@cisco.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Message-ID: <C409914F.2FBE9%jvasseur@cisco.com>
Thread-Topic: [Pce] PCEP Codepoints
Thread-Index: AciLkU7hjVgbGPeEEdyNXAANk8WjQA==
In-Reply-To: <0be101c88b90$c5830a30$0200a8c0@your029b8cecfe>
Mime-version: 1.0
X-OriginalArrivalTime: 21 Mar 2008 20:22:40.0235 (UTC)
	FILETIME=[4F9E43B0:01C88B91]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=571; t=1206130960; x=1206994960;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20Re=3A=20[Pce]=20PCEP=20Codepoints |Sender:=20
	|To:=20Adrian=20Farrel=20<adrian@olddog.co.uk>;
	bh=5XFsI0pf1EU360Kt4JhtuHHzsJZJr7LN5qsWl1zkZjs=;
	b=cvb7l6FesuNDyAszwReFz1c5jMS//wPKVVCx4JMyYikKOs7p4UbTPVcswf
	eTnrtJkmF1XcQPhscH/0AAHpymgp6BHq3THcfEFNSgZLeLyQ8BnehWaUIx6p
	XIN4WVImOx;
Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: pce@ietf.org
Subject: Re: [Pce] PCEP Codepoints
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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

Thanks.

Cheers,

JP.


> From: Adrian Farrel <adrian@olddog.co.uk>
> Reply-To: Adrian Farrel <adrian@olddog.co.uk>
> Date: Fri, 21 Mar 2008 20:18:09 -0000
> To: JP Vasseur <jvasseur@cisco.com>
> Cc: <pce@ietf.org>
> Subject: Re: [Pce] PCEP Codepoints
> 
>>> I believe I also found two points of confusion in BRPC...
>> 
>> We fixed those issues in version -07 (February 8, 2008).
> 
> Indeed!
> 
> If you are so clever, can you explain why I was looking at the wrong version
> of this I-D?
> 
> Temporary registry updated.
> 
> Adrian 
> 
> 

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


From pce-bounces@ietf.org  Fri Mar 21 13:40:57 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7F0EB28C59C;
	Fri, 21 Mar 2008 13:40:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.384
X-Spam-Level: 
X-Spam-Status: No, score=-100.384 tagged_above=-999 required=5
	tests=[AWL=0.053, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 5ZETwkGq7zuj; Fri, 21 Mar 2008 13:40:55 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9FB173A6DCE;
	Fri, 21 Mar 2008 13:40:55 -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 DF2EF28C285
	for <pce@core3.amsl.com>; Fri, 21 Mar 2008 13:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 wwNW1OnyIR0U for <pce@core3.amsl.com>;
	Fri, 21 Mar 2008 13:40:53 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 12ADB3A6A22
	for <pce@ietf.org>; Fri, 21 Mar 2008 13:40:52 -0700 (PDT)
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
	m2LKcXI0009159 for <pce@ietf.org>; Fri, 21 Mar 2008 20:38:33 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
	m2LKcUFg009149 for <pce@ietf.org>; Fri, 21 Mar 2008 20:38:31 GMT
Message-ID: <0bee01c88b93$84106720$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Fri, 21 Mar 2008 20:38:25 -0000
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] BRPC last call comments
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,

Here are some last call comments on draft-ietf-pce-brpc-07.txt

Running idnits (http://tools.ietf.org/tools/idnits/) yields...
  ** There is 1 instance of too long lines in the document, the longest one
     being 5 characters in excess of 72.

  == Unused Reference: 'I-D.ietf-ccamp-inter-domain-rsvp-te' is defined on
     line 675, but no explicit reference was found in the text

  == Outdated reference: A later version (-11) exists of
     draft-ietf-pce-pcep-09

  ** Downref: Normative reference to an Informational RFC: RFC 4655

  == Outdated reference: draft-ietf-ccamp-inter-domain-pd-path-comp has been
     published as RFC 5152

  == Outdated reference: draft-ietf-ccamp-inter-domain-rsvp-te has been
     published as RFC 5151

  == Outdated reference: A later version (-03) exists of
     draft-ietf-pce-manageability-requirements-02

  == Outdated reference: A later version (-02) exists of
     draft-ietf-pce-path-key-01

====
General
Replace optional plurals "(s)" with normal plural "s" for correct grammar
Please fix indentation for bullets in sections 3, 4, and 7
Please ensure that all section headings use capitals
====
Document title
Please use capitalisation as...
 A Backward Recursive PCE-based Computation (BRPC) Procedure to Compute
     Shortest Inter-Domain Traffic Engineering Label Switched Paths
====
Document title
Should the title say "Shortest Constrained" rather than "Shortest"? The 
Abstract and the body of the text refered to "constrained".
====
Abstract
s/domain is referred to as a/domain is a/
s/as IGP areas and Autonomous Systems/as an IGP area or an Autonomous 
System/
s/in order to compute/to compute/
s/paths along a/paths across a/
s/determined sequence/predetermined sequence/
s/technique while preserving/technique. This technique preserves/
====
Section 1.
The RFC Editor requires that the first section is the Introduction.
Therefore...
- Swap section 1 and section 2
- Expand all acronyms on their first use in the Introduction
  This includes "(G)MPLS"
====
Terminology section
If you choose to include terms like ABR, can you also please include the 
acronym expansion.
====
Introduction
s/establishing inter-domain/establishing an inter-domain/
====
Introduction
You say...
   the entry
   boundary node of each domain (each node in charge of computing a
   section of an inter-domain TE LSP path is always along the path of
   such TE LSP).
This implies that the BN is not able to be a PCC and use a remote PCE. I 
don't think this limit applies.
Perhaps you mean to say "each node responsible for triggering the 
computation of a section...."
====
Introduction
s/Such path computation technique/This computation technique/
====
Introduction
I think you should add to the final paragraph the usual note about common 
understanding or metrics and objective functions (or the ability to provide 
suitable mappings) between the domains.
(This is exapnded on in section 3 bullet 3, but it is fundamental to the 
brpc paradigm.
====
Section 3, bullet 1
Why do you assume that OSPF-TE or ISIS-TE are being run.
I think your assumption is that each PCE has access to an up-to-date TED, 
and you might note that the normal way to achieve this would be by running 
OSPF-TE or ISIS-TE.
====
Section 3, final bullet
s/means that are/means that is/
====
Section 4
s/solve multi-constraints/solve multi-constraint/
====
Section 4.1
In section 3, final bullet, we see...
   - The domain path (set of domains traversed to reach the destination
   domain) is either administratively pre-determined or discovered by
   some means that are outside of the scope of this document.
But here in section 4.1...
   The sequence of domains to be
   traversed can either be determined a priori or during the path
   computation procedure.
I wonder if section 4.1 is trying to provide hints of how to do domain 
selection. Perhaps you could replace 4.1 with a simple statement that BRPC 
mechanisms might also be used to determine the sequence of domains, but that 
such procedures are out of scope of this document.
====
Section 4.2
Is "Definition of VSPT(i)" intended to be a subsection?
I find that the section leaps to rapidly into the definition of the VSPT. 
Shouldn't there be some discussion first (somewhere) about the sequence of 
exchange of information between PCC and PCEs? This isn't much information, 
but seeing the VSPT(i) described as "tree returned by PCE(i) to PCE(i-1)" 
makes me wonder how the PCEs are joined together.
====
Figure 1
s/BN-en((j), i)/BN-en(j,i)/
====
Section 4.2, paragraph after Figure 1
s/the number of entry BN/the number of entry BNs/
Delete "(identified by its TE Router-ID)"? This has nothing to do with the 
definition of the abstract VSPT.
====
Section 4.2
   Note that PCE(i) only considers the entry BNs that provide
   connectivity from domain(i-1).
According to the definition of "Entry BN of domain(n)" in the terminology 
section, this text is redundant.
Perhaps you mean to say...
   Note that PCE(i) only considers the entry BNs of domain(i). That is,
   only the BNs that provide connectivity from domain (i-1).
This, however, jars with the note in Figure 1 that "j <= [X-en(i)]" since 
the implication of that note and the subsequent text in 4.2 is that the set 
of entry nodes to domain(i) (X-en(i)) is actually considered to be the set 
of all BNs to domain(i).
You need to select a some terminology and then fix the text to be 
consistent.
Note, it is fine when you say:
   Furthermore, some BNs may be excluded according to policy
   constraints (either due to local policy or policies signaled in the
   path computation request).
This does allow j <= [X-en(i)]
====
Section 4.2
   The path computation request is then relayed until reaching a PCE(n)
   such that the TE LSP destination resides in the domain(n).  At each
   step of the process, the next PCE can either be statically configured
   or dynamically discovered via IGP/BGP extensions.
You need to be clear. Is it required that the PCEP request is forwarded in 
strict sequence PCE(i-1)-->PCE(i) for all i = 2 to n, or is it OK for the 
request to simply be forwarded direct to PCE(n)?
This leads to...
   If
   multiple PCEs are discovered, the PCE may select a subset of these
   PCEs based on some local policies or heuristics.
...should be clarified as...
   If PCE(i-1)
   discovers multiple PCEs for the adjacent domain(i), PCE(i) may
   select a subset of these PCEs based on some local policies or
   heuristics.
And hidden in here is the fact that PCE(i-1) may consult multiple PCE(i)s. 
This is fine, but is not exposed anywhere else in the document. In 
particular, the process does not say "PCE(i-1) MUST/SHOULD/MAY wait until it 
has heard responses from each PCE(i) that it has consulted."
====
Section 4.2
   Step i:

   - For i=n-1 to 2: PCE(i) concatenates the topology of domain(i)
   (using its TED) with the received VSPT(i+1).

I don't like "concatenates the topology". Don't you mean...
   Step i:

   - For i=n-1 to 2: PCE(i) computes the shortest constrained paths from
     each BN-en(i) to each BN-ex(i) that is identified in VSPT(i+1). It
     then concatenates the shortest of those paths to the paths in
     VSPT(i+1) to construct VSPT(i).

Then you can delete the following...
   Then PCE(i) computes VSPT(i) (MP2P (Multi-Point to Point) tree made
   of the shortest constrained paths between each BN-en(j,i) and the TE
   LSP destination).

====
Section 4.2
Replace...
   End
...with...
   Step n
====
Section 5
Is it assumed that PCE(i) knows which domain the requesting PCE(i-1) 
represents?
The reverse is obviously true because PCE(i-1) must select PCE(i) on this 
basis, but it seems to me that the PCReq could useful identify the 
neighboring (upstream) domain. This would be particularly useful in the case 
of a requesting PCE that represents multiple domains since it will allow 
PCE(i) to know which are the BN-en(i) nodes.
Conversely, if PCE(i) has computation capabilities for multiple domains, it 
will need to be told which for domain(i) it should act.
So we either need protocol extensions (requesting domain, computation 
domain) or we need to be told how to use existing protocol fields for this 
purpose.

Furthermore :-( how although the sequence of domains is known (a priori) by 
the PCC, we need some way to convey the sequence in the PCReq so that PCE(i) 
knows that the next domain in the sequence is domain(i+1).
If this can be achieved by existing protocol mechanism, you need to describe 
the procedures. If it can't be done, we need protocol extensions.
====
Section 6
s/from an ABR/from a BN/
s/PCERep/PCRep/
====
Section 9
Since the protocol extensions presented in this document are exactly that 
(protocol extensions) you must beware of backward compatibility issues. So 
when you have...
   If the BRPC procedure cannot be completed because a PCE along the
   domain path does not support the procedure, a PCErr message MUST be
   returned to the upstream PCE with a Error-Type "BRPC procedure
   completion failure".  The PCErr message MUST be relayed to the
   requesting PCC.
...you need to be aware that for PCE(i), not supporting BRPC (i.e. not 
recognising the VSPT bit) is going to be treated according to the main PCEP 
spec, and not according to any rules in this document.
But pcep-11 says...
   Unassigned bits are considered as reserved and MUST be set to zero on
   transmission.
...from which we assume that bits not understood are ignored and MAYBE 
forwarded in the next PCReq to PCE(i+1) or MAYBE dropped.

Ouch!
Not to late to fix the PCEP spec to say that an RP object carrying an 
unrecognised bit MUST be rejected with an Error Type of "Unknown Request 
Parameter" (or would you use "Capability Not Supported"?) and an Error Code 
to indicate the bit number. (You can't give names to the error codes because 
you don't know what the bits mean!)

That would leave you with the need to modify your document here as...
   If the BRPC procedure cannot be completed because a PCE along the
   domain path recognises but does not support the procedure, it MUST
   return a PCErr message to the upstream PCE with an Error-Type "BRPC
   procedure completion failure".

Note that if you do not fix the PCEP spec, you will have to handle the case 
where the PCE receives a PCRep from its downstream neighbor containing a 
VSPT that will be incomprehensible.

See also Section 14.1
====
Section 10.1
s/Such request MUST/Such requests MUST/
s/a set of diversely routed TE LSP/a set of diversely routed TE LSPs/
====
Section 13
s/meaningful, a metric normalization/meaningful, metric normalization/
s/thanks to the METRIC/using the METRIC/
====
Section 14.2
Not mandatory, but it would be useful to highlight what this MIB module 
actually needs to track.
Is it just the configuration widget in 14.1, or is there more stuff?
====
Section 14.4
Ha!
And how will you look at these TEDs?
Have a look at 8.4 of pcep-11
====
Appendix A
I think you can remove this now
====


Cheers,
Adrian 


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


From pce-bounces@ietf.org  Mon Mar 24 10:33:10 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 77DC13A6861;
	Mon, 24 Mar 2008 10:33:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.953
X-Spam-Level: 
X-Spam-Status: No, score=-98.953 tagged_above=-999 required=5
	tests=[AWL=-0.583, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RCVD_NUMERIC_HELO=2.067, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 ckPHpM6Evo2P; Mon, 24 Mar 2008 10:33:08 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C927328C48E;
	Mon, 24 Mar 2008 10:32:59 -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 4C4F428C46C
	for <pce@core3.amsl.com>; Mon, 24 Mar 2008 10:32:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 S8MlJSUNaUbf for <pce@core3.amsl.com>;
	Mon, 24 Mar 2008 10:32:57 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 460ED28C45D
	for <pce@ietf.org>; Mon, 24 Mar 2008 10:32:29 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,547,1199682000"; 
   d="scan'208";a="2916346"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 24 Mar 2008 13:30:09 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m2OHU9P2030461; 
	Mon, 24 Mar 2008 13:30:09 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m2OHU9Vb012848;
	Mon, 24 Mar 2008 17:30:09 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 24 Mar 2008 13:30:09 -0400
Received: from 161.44.71.244 ([161.44.71.244]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 24 Mar 2008 17:30:08 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Mon, 24 Mar 2008 13:30:07 -0400
From: JP Vasseur <jvasseur@cisco.com>
To: Adrian Farrel <adrian@olddog.co.uk>, <pce@ietf.org>
Message-ID: <C40D5D5F.30007%jvasseur@cisco.com>
Thread-Topic: [Pce] BRPC last call comments
Thread-Index: AciN1LPZ8ow2jPnHEdyylAANk8WjQA==
In-Reply-To: <0bee01c88b93$84106720$0200a8c0@your029b8cecfe>
Mime-version: 1.0
X-OriginalArrivalTime: 24 Mar 2008 17:30:09.0274 (UTC)
	FILETIME=[B53435A0:01C88DD4]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=11179; t=1206379809;
	x=1207243809; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20Re=3A=20[Pce]=20BRPC=20last=20call=20comments
	|Sender:=20
	|To:=20Adrian=20Farrel=20<adrian@olddog.co.uk>,=20<pce@ietf
	.org>; bh=O7lHgCMuXf+4M+RtsBHC5P75xkaK6rKjvcaVWwC5S4Y=;
	b=PK2PUmkS5eRJUJ8JkgmQcwZzow/rlHcho5oDEzkNf9YiVfUuW9oUBjv8P2
	+IobfGZb8BRHUDLevIzv9btw7DfQ+OFdc/zq0UMmjZSUvIHX4WdaD9R/y70a
	ac5Le0feDa;
Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: Re: [Pce] BRPC last call comments
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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 Adrian,

Thanks for the great review, as usual.

I skipped all editorial comments that have been addressed.

> Introduction
> You say...
>    the entry
>    boundary node of each domain (each node in charge of computing a
>    section of an inter-domain TE LSP path is always along the path of
>    such TE LSP).
> This implies that the BN is not able to be a PCC and use a remote PCE. I
> don't think this limit applies.
> Perhaps you mean to say "each node responsible for triggering the
> computation of a section...."

Absolutely. The case of the BN acting as a PCC is clarified in the document
but the wording here was not appropriate. Text fixed.

> Introduction
> I think you should add to the final paragraph the usual note about common
> understanding or metrics and objective functions (or the ability to provide
> suitable mappings) between the domains.
> (This is exapnded on in section 3 bullet 3, but it is fundamental to the
> brpc paradigm.

Yes, I added a sentence + a pointer to section 13.

> ====
> Section 3, bullet 1
> Why do you assume that OSPF-TE or ISIS-TE are being run.
> I think your assumption is that each PCE has access to an up-to-date TED,
> and you might note that the normal way to achieve this would be by running
> OSPF-TE or ISIS-TE.

Right. " i.e. running OSPF-TE or ISIS-TE and RSVP-TE" has simply be removed.

> ====
> Section 4.1
> In section 3, final bullet, we see...
>    - The domain path (set of domains traversed to reach the destination
>    domain) is either administratively pre-determined or discovered by
>    some means that are outside of the scope of this document.
> But here in section 4.1...
>    The sequence of domains to be
>    traversed can either be determined a priori or during the path
>    computation procedure.

Heu ... I do not see any contradiction here?

> I wonder if section 4.1 is trying to provide hints of how to do domain
> selection. Perhaps you could replace 4.1 with a simple statement that BRPC
> mechanisms might also be used to determine the sequence of domains, but that
> such procedures are out of scope of this document.

BRPC by itself is not itself used to determine the sequence of domains but
it can indeed perform the function. But we'd rather use the same wording
here. 

S/ The sequence of domains to be traversed can either be determined a priori
or during the path computation procedure/ The sequence of domains to be
traversed is either administratively pre-determined or discovered by
some means that is outside of the scope of this document.

> ====
> Section 4.2
> Is "Definition of VSPT(i)" intended to be a subsection?
> I find that the section leaps to rapidly into the definition of the VSPT.
> Shouldn't there be some discussion first (somewhere) about the sequence of
> exchange of information between PCC and PCEs? This isn't much information,
> but seeing the VSPT(i) described as "tree returned by PCE(i) to PCE(i-1)"
> makes me wonder how the PCEs are joined together.

This is explained in the text right after. Do you think that we need to add
even more text there?

> ====
> Section 4.2
>    Note that PCE(i) only considers the entry BNs that provide
>    connectivity from domain(i-1).
> According to the definition of "Entry BN of domain(n)" in the terminology
> section, this text is redundant.
> Perhaps you mean to say...
>    Note that PCE(i) only considers the entry BNs of domain(i). That is,
>    only the BNs that provide connectivity from domain (i-1).

> This, however, jars with the note in Figure 1 that "j <= [X-en(i)]" since
> the implication of that note and the subsequent text in 4.2 is that the set
> of entry nodes to domain(i) (X-en(i)) is actually considered to be the set
> of all BNs to domain(i).

I don't see an issue there since the note says "j<=[X-en(i)]", which does
not imply that the set is the set of all BNs to domain(i) ?

> You need to select a some terminology and then fix the text to be
> consistent.
> Note, it is fine when you say:
>    Furthermore, some BNs may be excluded according to policy
>    constraints (either due to local policy or policies signaled in the
>    path computation request).
> This does allow j <= [X-en(i)]

Right,

> ====
> Section 4.2
>    The path computation request is then relayed until reaching a PCE(n)
>    such that the TE LSP destination resides in the domain(n).  At each
>    step of the process, the next PCE can either be statically configured
>    or dynamically discovered via IGP/BGP extensions.
> You need to be clear. Is it required that the PCEP request is forwarded in
> strict sequence PCE(i-1)-->PCE(i) for all i = 2 to n, or is it OK for the
> request to simply be forwarded direct to PCE(n)?

It was intentional not to be specific here since both are possible.

> This leads to...
>    If
>    multiple PCEs are discovered, the PCE may select a subset of these
>    PCEs based on some local policies or heuristics.
> ...should be clarified as...
>    If PCE(i-1)
>    discovers multiple PCEs for the adjacent domain(i), PCE(i) may
>    select a subset of these PCEs based on some local policies or
>    heuristics.

OK

> And hidden in here is the fact that PCE(i-1) may consult multiple PCE(i)s.
> This is fine, but is not exposed anywhere else in the document. In
> particular, the process does not say "PCE(i-1) MUST/SHOULD/MAY wait until it
> has heard responses from each PCE(i) that it has consulted."

It is implementation specific.

> ====
> Section 4.2
>    Step i:
> 
>    - For i=n-1 to 2: PCE(i) concatenates the topology of domain(i)
>    (using its TED) with the received VSPT(i+1).
> 
> I don't like "concatenates the topology". Don't you mean...
>    Step i:
> 
>    - For i=n-1 to 2: PCE(i) computes the shortest constrained paths from
>      each BN-en(i) to each BN-ex(i) that is identified in VSPT(i+1). It
>      then concatenates the shortest of those paths to the paths in
>      VSPT(i+1) to construct VSPT(i).
> 
> Then you can delete the following...
>    Then PCE(i) computes VSPT(i) (MP2P (Multi-Point to Point) tree made
>    of the shortest constrained paths between each BN-en(j,i) and the TE
>    LSP destination).

Not really since this is a different way to compute the path. We used to
terminology "concatenates" since for example PCE1 may not compute the
shortest paths from BN-en(1) to each BN-ex(1). It could indeed concatenate
VPST(2) with its TED and compute the path in one pass in the case of an ABR.

> 
> ====
> Section 4.2
> Replace...
>    End
> ...with...
>    Step n
> ====


> Section 5
> Is it assumed that PCE(i) knows which domain the requesting PCE(i-1)
> represents?
> The reverse is obviously true because PCE(i-1) must select PCE(i) on this
> basis, but it seems to me that the PCReq could useful identify the
> neighboring (upstream) domain. This would be particularly useful in the case
> of a requesting PCE that represents multiple domains since it will allow
> PCE(i) to know which are the BN-en(i) nodes.
> Conversely, if PCE(i) has computation capabilities for multiple domains, it
> will need to be told which for domain(i) it should act.
> So we either need protocol extensions (requesting domain, computation
> domain) or we need to be told how to use existing protocol fields for this
> purpose.
> 
> Furthermore :-( how although the sequence of domains is known (a priori) by
> the PCC, we need some way to convey the sequence in the PCReq so that PCE(i)
> knows that the next domain in the sequence is domain(i+1).
> If this can be achieved by existing protocol mechanism, you need to describe
> the procedures. If it can't be done, we need protocol extensions.

We make the assumption that the sequence of domains is predetermined or
discovered by some means that is outside of the scope of this document.
You're right that we do not say that the sequence of PCE is also
predetermined or discovery by some means. Do you want us to explicitly add
this assumption?
Consider the two following cases:
1) Inter-area: obvious
2) Inter-AS: if the sequences of domain and related PCEs are known, there is
no need for protocol extensions except if we want to enforce the sequence of
PCEs, which can be done thanks to the PCE-ID object defined in
http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-01.txt. We
could include the PCE-ID object definition in BRPC and add some text here.
Thoughts?

> ====
> Section 9
> Since the protocol extensions presented in this document are exactly that
> (protocol extensions) you must beware of backward compatibility issues. So
> when you have...
>    If the BRPC procedure cannot be completed because a PCE along the
>    domain path does not support the procedure, a PCErr message MUST be
>    returned to the upstream PCE with a Error-Type "BRPC procedure
>    completion failure".  The PCErr message MUST be relayed to the
>    requesting PCC.
> ...you need to be aware that for PCE(i), not supporting BRPC (i.e. not
> recognising the VSPT bit) is going to be treated according to the main PCEP
> spec, and not according to any rules in this document.
> But pcep-11 says...
>    Unassigned bits are considered as reserved and MUST be set to zero on
>    transmission.
> ...from which we assume that bits not understood are ignored and MAYBE
> forwarded in the next PCReq to PCE(i+1) or MAYBE dropped.
> 
> Ouch!
> Not to late to fix the PCEP spec to say that an RP object carrying an
> unrecognised bit MUST be rejected with an Error Type of "Unknown Request
> Parameter" (or would you use "Capability Not Supported"?) and an Error Code
> to indicate the bit number. (You can't give names to the error codes because
> you don't know what the bits mean!)
> 
> That would leave you with the need to modify your document here as...
>    If the BRPC procedure cannot be completed because a PCE along the
>    domain path recognises but does not support the procedure, it MUST
>    return a PCErr message to the upstream PCE with an Error-Type "BRPC
>    procedure completion failure".
> 

Very good point. The proposed text has been added.

And indeed, we need to update the PCEP spec with:

Section 7.4: An RP object carrying an unrecognised bit MUST be rejected with
an Error Type of "Unknown Request Parameter.

Could be:
A new Error-Type
Or
10         Reception of an invalid object
               Error-value=1: reception of an object with P flag not set
               although the P-flag must be set according to this
               specification.

With a new Error-value.

> ====
> Section 14.4
> Ha!
> And how will you look at these TEDs?

It of course depends on how these TEDs are populated but this is in any case
the only way to verify correct operation.

> Have a look at 8.4 of pcep-11

Thanks.

JP.

> 
> 
> Cheers,
> Adrian 
> 
> 
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce

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


From pce-bounces@ietf.org  Mon Mar 24 12:45:27 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5DFCA28C3A3;
	Mon, 24 Mar 2008 12:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.462
X-Spam-Level: 
X-Spam-Status: No, score=-100.462 tagged_above=-999 required=5
	tests=[AWL=-0.026, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 Jb6d1dwS6dEG; Mon, 24 Mar 2008 12:45:25 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE09228C20A;
	Mon, 24 Mar 2008 12:44:51 -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 50AD928C20A
	for <pce@core3.amsl.com>; Mon, 24 Mar 2008 12:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 fcWwsZ-G4Bs0 for <pce@core3.amsl.com>;
	Mon, 24 Mar 2008 12:44:45 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 0B3203A6805
	for <pce@ietf.org>; Mon, 24 Mar 2008 12:44:44 -0700 (PDT)
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
	m2OJfVdB002464; Mon, 24 Mar 2008 19:41:36 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
	m2OJfUJC002454; Mon, 24 Mar 2008 19:41:31 GMT
Message-ID: <0de901c88de7$0b2d2950$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "JP Vasseur" <jvasseur@cisco.com>, <pce@ietf.org>
References: <C40D5D5F.30007%jvasseur@cisco.com>
Date: Mon, 24 Mar 2008 19:40:47 -0000
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: Re: [Pce] BRPC last call comments
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: multipart/mixed; boundary="===============1836957520=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1836957520==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0DE6_01C88DE6.F5706F00"

This is a multi-part message in MIME format.

------=_NextPart_000_0DE6_01C88DE6.F5706F00
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi JP,

Thanks for the quick progress.

Snipped everything where we have reached conclusion...

>> Section 4.2
>> Is "Definition of VSPT(i)" intended to be a subsection?
>> I find that the section leaps to rapidly into the definition of the =
VSPT.
>> Shouldn't there be some discussion first (somewhere) about the =
sequence of
>> exchange of information between PCC and PCEs? This isn't much =
information,
>> but seeing the VSPT(i) described as "tree returned by PCE(i) to =
PCE(i-1)"
>> makes me wonder how the PCEs are joined together.
>=20
> This is explained in the text right after. Do you think that we need =
to add
> even more text there?

Well, I don't think it is crystal clear. Or rather, it *is* crystal =
clear, but the crystal is smokey quartz =
(http://gwydir.demon.co.uk/jo/minerals/otherquartz.htm)

How about a simple paragraph about the basic operation of BRPC such =
as...

The BRPC procedure relies on communication between cooperating PCEs. In =
particular, the PCC sends a PCReq to a PCE in its domain. The request is =
forwarded between PCEs, domain-by-domain until the PCE responsible for =
the domain containing the LSP destination is reached. The PCE in the =
destination domain creates a tree of potential paths to the destination =
(the Virtual Shortest Path Tree - VSPT) and passes this back to the =
previous PCE in a PCRep. Each PCE in turn adds to the VSPT and passes it =
back until the PCE in the source domain uses the VSPT to select an =
end-to-end path that it sends to the PCC.

>> Section 4.2
>>    Step i:
>>=20
>>    - For i=3Dn-1 to 2: PCE(i) concatenates the topology of domain(i)
>>    (using its TED) with the received VSPT(i+1).
>>=20
>> I don't like "concatenates the topology". Don't you mean...
>>    Step i:
>>=20
>>    - For i=3Dn-1 to 2: PCE(i) computes the shortest constrained paths =
from
>>      each BN-en(i) to each BN-ex(i) that is identified in VSPT(i+1). =
It
>>      then concatenates the shortest of those paths to the paths in
>>      VSPT(i+1) to construct VSPT(i).
>>=20
>> Then you can delete the following...
>>    Then PCE(i) computes VSPT(i) (MP2P (Multi-Point to Point) tree =
made
>>    of the shortest constrained paths between each BN-en(j,i) and the =
TE
>>    LSP destination).
>=20
> Not really since this is a different way to compute the path. We used =
to
> terminology "concatenates" since for example PCE1 may not compute the
> shortest paths from BN-en(1) to each BN-ex(1). It could indeed =
concatenate
> VPST(2) with its TED and compute the path in one pass in the case of =
an ABR.

OK.
The problem is with the "concatenate."

How about...

    Step i:
=20
    - For i=3Dn-1 to 2: PCE(i) computes VSPT(i), the tree made
      of the shortest constrained paths between each BN-en(j,i)
      and the TE LSP destination. It does this by considering
      its own TED and the information in VSPT(i+1).

>> Section 5
>> Is it assumed that PCE(i) knows which domain the requesting PCE(i-1)
>> represents?
>> The reverse is obviously true because PCE(i-1) must select PCE(i) on =
this
>> basis, but it seems to me that the PCReq could useful identify the
>> neighboring (upstream) domain. This would be particularly useful in =
the case
>> of a requesting PCE that represents multiple domains since it will =
allow
>> PCE(i) to know which are the BN-en(i) nodes.
>> Conversely, if PCE(i) has computation capabilities for multiple =
domains, it
>> will need to be told which for domain(i) it should act.
>> So we either need protocol extensions (requesting domain, computation
>> domain) or we need to be told how to use existing protocol fields for =
this
>> purpose.
>>=20
>> Furthermore :-( how although the sequence of domains is known (a =
priori) by
>> the PCC, we need some way to convey the sequence in the PCReq so that =
PCE(i)
>> knows that the next domain in the sequence is domain(i+1).
>> If this can be achieved by existing protocol mechanism, you need to =
describe
>> the procedures. If it can't be done, we need protocol extensions.
>=20
> We make the assumption that the sequence of domains is predetermined =
or
> discovered by some means that is outside of the scope of this =
document.
> You're right that we do not say that the sequence of PCE is also
> predetermined or discovery by some means. Do you want us to explicitly =
add
> this assumption?
> Consider the two following cases:
> 1) Inter-area: obvious
> 2) Inter-AS: if the sequences of domain and related PCEs are known, =
there is
> no need for protocol extensions except if we want to enforce the =
sequence of
> PCEs, which can be done thanks to the PCE-ID object defined in
> http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-01.txt. =
We
> could include the PCE-ID object definition in BRPC and add some text =
here.
> Thoughts?

Well, I have no problems with "the sequence of domains is known a =
priori." In fact, I strongly support it.

However, to whom is this sequence known?

Yes, if the ingress PCC or PCE knows the PCEs responsible for each =
domain, then it could provide a list of such PCEs. But this is more =
information than is implied in "the sequence of domains". My assumption =
is that the default position is that PCE(i) will select PCE(i+1).

But how does PCE(i) know that the next domain is domain(i+1)? How is the =
a priori knowledge passed to PCE(i)?

This isimportant, because knowing the sequence of PCEs is not enough to =
know the sequence of domains. A PCE may serve more than one domain.

>> Section 14.4
>> Ha!
>> And how will you look at these TEDs?
>=20
> It of course depends on how these TEDs are populated but this is in =
any case
> the only way to verify correct operation.
=20
In section 8.4 of pcep-11 we took a completely different meaning of =
"correct operation" because we recognised that we are interested in the =
correct operation of the protocol, not the correct operation of the =
computation algorithm.

You should do the same here.

I think the only thing to add to the PCEP spec will be the trail of PCEs =
as discussed in the monitoring I-D.

A
------=_NextPart_000_0DE6_01C88DE6.F5706F00
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Hi JP,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks for the quick =
progress.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Snipped everything where we have =
reached=20
conclusion...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&gt;&gt; Section 4.2<BR>&gt;&gt; Is =
"Definition of=20
VSPT(i)" intended to be a subsection?<BR>&gt;&gt; I find that the =
section leaps=20
to rapidly into the definition of the VSPT.<BR>&gt;&gt; Shouldn't there =
be some=20
discussion first (somewhere) about the sequence of<BR>&gt;&gt; exchange =
of=20
information between PCC and PCEs? This isn't much =
information,<BR>&gt;&gt; but=20
seeing the VSPT(i) described as "tree returned by PCE(i) to=20
PCE(i-1)"<BR>&gt;&gt; makes me wonder how the PCEs are joined =
together.<BR>&gt;=20
<BR>&gt; This is explained in the text right after. Do you think that we =
need to=20
add<BR>&gt; even more text there?<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Well, I don't think it is crystal =
clear. Or rather,=20
it *is* crystal clear, but the crystal is smokey quartz (</FONT><A=20
href=3D"http://gwydir.demon.co.uk/jo/minerals/otherquartz.htm"><FONT =
face=3DArial=20
size=3D2>http://gwydir.demon.co.uk/jo/minerals/otherquartz.htm</FONT></A>=
<FONT=20
face=3DArial size=3D2>)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>How about a simple paragraph about the =
basic=20
operation of BRPC such as...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The BRPC procedure relies on =
communication between=20
cooperating PCEs. In particular, the PCC sends a PCReq to a PCE&nbsp;in =
its=20
domain.&nbsp;The request is forwarded between PCEs, domain-by-domain =
until the=20
PCE responsible for the domain containing the LSP destination is =
reached. The=20
PCE in the destination domain creates a tree of potential paths to the=20
destination (the Virtual Shortest Path Tree - VSPT) and passes this back =
to the=20
previous PCE in a PCRep. Each PCE in turn adds to the VSPT and passes it =
back=20
until the PCE in the source domain uses the VSPT to select an end-to-end =
path=20
that it sends to the PCC.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&gt;&gt; Section =
4.2<BR>&gt;&gt;&nbsp;&nbsp;&nbsp;=20
Step i:<BR>&gt;&gt; <BR>&gt;&gt;&nbsp;&nbsp;&nbsp; - For i=3Dn-1 to 2: =
PCE(i)=20
concatenates the topology of domain(i)<BR>&gt;&gt;&nbsp;&nbsp;&nbsp; =
(using its=20
TED) with the received VSPT(i+1).<BR>&gt;&gt; <BR>&gt;&gt; I don't like=20
"concatenates the topology". Don't you =
mean...<BR>&gt;&gt;&nbsp;&nbsp;&nbsp;=20
Step i:<BR>&gt;&gt; <BR>&gt;&gt;&nbsp;&nbsp;&nbsp; - For i=3Dn-1 to 2: =
PCE(i)=20
computes the shortest constrained paths=20
from<BR>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; each BN-en(i) to each =
BN-ex(i)=20
that is identified in VSPT(i+1). =
It<BR>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
then concatenates the shortest of those paths to the paths=20
in<BR>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; VSPT(i+1) to construct=20
VSPT(i).<BR>&gt;&gt; <BR>&gt;&gt; Then you can delete the=20
following...<BR>&gt;&gt;&nbsp;&nbsp;&nbsp; Then PCE(i) computes VSPT(i) =
(MP2P=20
(Multi-Point to Point) tree made<BR>&gt;&gt;&nbsp;&nbsp;&nbsp; of the =
shortest=20
constrained paths between each BN-en(j,i) and the=20
TE<BR>&gt;&gt;&nbsp;&nbsp;&nbsp; LSP destination).<BR>&gt; <BR>&gt; Not =
really=20
since this is a different way to compute the path. We used to<BR>&gt;=20
terminology "concatenates" since for example PCE1 may not compute =
the<BR>&gt;=20
shortest paths from BN-en(1) to each BN-ex(1). It could indeed=20
concatenate<BR>&gt; VPST(2) with its TED and compute the path in one =
pass in the=20
case of an ABR.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>OK.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The problem is with the =
"concatenate."</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>How about...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>&nbsp;&nbsp;&nbsp; Step=20
i:<BR>&nbsp;<BR>&nbsp;&nbsp;&nbsp; - For i=3Dn-1 to 2: PCE(i) computes =
VSPT(i),=20
the tree made<BR>&nbsp; &nbsp;&nbsp;&nbsp; of the shortest constrained =
paths=20
between each BN-en(j,i)</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;and the TE=20
LSP destination. It does this by&nbsp;</FONT><FONT face=3D"Courier New"=20
size=3D2>considering</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;its=20
own&nbsp;</FONT><FONT face=3DArial size=3D2><FONT face=3D"Courier =
New">TED and the=20
information in VSPT(i+1).</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;</DIV></FONT>
<DIV><FONT face=3DArial size=3D2>&gt;&gt; Section 5<BR>&gt;&gt; Is it =
assumed that=20
PCE(i) knows which domain the requesting PCE(i-1)<BR>&gt;&gt;=20
represents?<BR>&gt;&gt; The reverse is obviously true because PCE(i-1) =
must=20
select PCE(i) on this<BR>&gt;&gt; basis, but it seems to me that the =
PCReq could=20
useful identify the<BR>&gt;&gt; neighboring (upstream) domain. This =
would be=20
particularly useful in the case<BR>&gt;&gt; of a requesting PCE that =
represents=20
multiple domains since it will allow<BR>&gt;&gt; PCE(i) to know which =
are the=20
BN-en(i) nodes.<BR>&gt;&gt; Conversely, if PCE(i) has computation =
capabilities=20
for multiple domains, it<BR>&gt;&gt; will need to be told which for =
domain(i) it=20
should act.<BR>&gt;&gt; So we either need protocol extensions =
(requesting=20
domain, computation<BR>&gt;&gt; domain) or we need to be told how to use =

existing protocol fields for this<BR>&gt;&gt; purpose.<BR>&gt;&gt; =
<BR>&gt;&gt;=20
Furthermore :-( how although the sequence of domains is known (a priori) =

by<BR>&gt;&gt; the PCC, we need some way to convey the sequence in the =
PCReq so=20
that PCE(i)<BR>&gt;&gt; knows that the next domain in the sequence is=20
domain(i+1).<BR>&gt;&gt; If this can be achieved by existing protocol =
mechanism,=20
you need to describe<BR>&gt;&gt; the procedures. If it can't be done, we =
need=20
protocol extensions.<BR>&gt; <BR>&gt; We make the assumption that the =
sequence=20
of domains is predetermined or<BR>&gt; discovered by some means that is =
outside=20
of the scope of this document.<BR>&gt; You're right that we do not say =
that the=20
sequence of PCE is also<BR>&gt; predetermined or discovery by some =
means. Do you=20
want us to explicitly add<BR>&gt; this assumption?<BR>&gt; Consider the =
two=20
following cases:<BR>&gt; 1) Inter-area: obvious<BR>&gt; 2) Inter-AS: if =
the=20
sequences of domain and related PCEs are known, there is<BR>&gt; no need =
for=20
protocol extensions except if we want to enforce the sequence of<BR>&gt; =
PCEs,=20
which can be done thanks to the PCE-ID object defined in<BR>&gt; =
</FONT><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-01.=
txt"><FONT=20
face=3DArial=20
size=3D2>http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-01=
.txt</FONT></A><FONT=20
face=3DArial size=3D2>. We<BR>&gt; could include the PCE-ID object =
definition in=20
BRPC and add some text here.<BR>&gt; Thoughts?<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Well, I have no problems with "the =
sequence of=20
domains is known a priori." In fact, I strongly support it.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>However, to whom is this sequence=20
known?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Yes, if the ingress PCC or PCE knows =
the PCEs=20
responsible for each domain, then it could provide a list of such PCEs. =
But this=20
is more information than is implied in "the sequence of domains". My =
assumption=20
is that the default position is that PCE(i) will select =
PCE(i+1).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>But how does PCE(i) know that the next =
domain is=20
domain(i+1)? How is the a priori knowledge passed to =
PCE(i)?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>This isimportant, because knowing the =
sequence of=20
PCEs is not enough to know the sequence of domains. A PCE may serve more =
than=20
one domain.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&gt;&gt; Section 14.4<BR>&gt;&gt; =
Ha!<BR>&gt;&gt;=20
And how will you look at these TEDs?<BR>&gt; <BR>&gt; It of course =
depends on=20
how these TEDs are populated but this is in any case<BR>&gt; the only =
way to=20
verify correct operation.<BR>&nbsp;<BR>In&nbsp;section&nbsp;8.4 of =
pcep-11 we=20
took a completely different meaning of "correct operation" because we =
recognised=20
that we are interested in the correct operation of the protocol, not the =
correct=20
operation of the computation algorithm.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>You should do the same =
here.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I think the only thing to add to the =
PCEP spec will=20
be the trail of PCEs as discussed in the monitoring I-D.</DIV>
<DIV><BR>A</DIV></FONT></BODY></HTML>

------=_NextPart_000_0DE6_01C88DE6.F5706F00--



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

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

--===============1836957520==--




From pce-bounces@ietf.org  Mon Mar 24 16:39:15 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 572223A6B27;
	Mon, 24 Mar 2008 16:39:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.28
X-Spam-Level: 
X-Spam-Status: No, score=-100.28 tagged_above=-999 required=5
	tests=[AWL=0.157, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 XMsnuq31CJFB; Mon, 24 Mar 2008 16:39:14 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 681453A683B;
	Mon, 24 Mar 2008 16:39: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 C24463A6AF1
	for <pce@core3.amsl.com>; Mon, 24 Mar 2008 16:39:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 SWlTYRZlxvr4 for <pce@core3.amsl.com>;
	Mon, 24 Mar 2008 16:39:12 -0700 (PDT)
Received: from tama500.ecl.ntt.co.jp (tama500.ecl.ntt.co.jp [129.60.39.148])
	by core3.amsl.com (Postfix) with ESMTP id A16653A6A8A
	for <pce@ietf.org>; Mon, 24 Mar 2008 16:39:12 -0700 (PDT)
Received: from mfs5.rdh.ecl.ntt.co.jp (mfs5.rdh.ecl.ntt.co.jp [129.60.39.144])
	by tama500.ecl.ntt.co.jp (8.14.2/8.14.2) with ESMTP id
	m2ONakT3004185; Tue, 25 Mar 2008 08:36:46 +0900 (JST)
Received: from mfs5.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs5.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 143B96A55;
	Tue, 25 Mar 2008 08:36:46 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (eclscan2.m.ecl.ntt.co.jp
	[129.60.5.68])
	by mfs5.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 027946A40;
	Tue, 25 Mar 2008 08:36:45 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2ONajWE011529; Tue, 25 Mar 2008 08:36:45 +0900 (JST)
Received: from imb.m.ecl.ntt.co.jp (imb0.m.ecl.ntt.co.jp [129.60.5.140])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2ONajpe011525; Tue, 25 Mar 2008 08:36:45 +0900 (JST)
Received: from [129.60.80.54] ([129.60.80.54])
	by imb.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id m2ONaiiD008976;
	Tue, 25 Mar 2008 08:36:45 +0900 (JST)
Date: Tue, 25 Mar 2008 08:35:55 +0900
From: Eiji Oki <oki.eiji@lab.ntt.co.jp>
To: JP Vasseur <jvasseur@cisco.com>
In-Reply-To: <C40983A2.2FBB0%jvasseur@cisco.com>
References: <20080321092603.D61E.OKI.EIJI@lab.ntt.co.jp>
	<C40983A2.2FBB0%jvasseur@cisco.com>
Message-Id: <20080325083522.108D.OKI.EIJI@lab.ntt.co.jp>
MIME-Version: 1.0
X-Mailer: Becky! ver. 2.30.04 [ja]
Cc: pce@ietf.org
Subject: Re: [Pce] I-D ACTION:draft-ietf-pce-pcep-xro-04.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi JP, 

Yes. I will submit the revision soon.

Thank you.
Eiji

On Fri, 21 Mar 2008 15:24:18 -0400
JP Vasseur <jvasseur@cisco.com> wrote:

> Hi Eiji,
> 
> 
> > From: Eiji Oki <oki.eiji@lab.ntt.co.jp>
> > Date: Fri, 21 Mar 2008 09:27:24 +0900
> > To: Fabien Verhaeghe <fabien.verhaeghe@marben-products.com>
> > Cc: <pce@ietf.org>
> > Subject: Re: [Pce] I-D ACTION:draft-ietf-pce-pcep-xro-04.txt
> > 
> > Fabien, 
> > 
> > Yes, you are right. We should match the base PCEP spec.
> > We will change 3 to 4, 4 to 32, and 5 to 34.
> > Is it OK to make this change during working group last call?
> 
> If OK with you I would suggest to make the change now, and we will then Last
> Call the document.
> 
> Thanks.
> 
> JP.
> 
> > 
> > Thank you.
> > Eiji
> > 
> > On Thu, 20 Mar 2008 08:49:21 +0100
> > "Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com> wrote:
> > 
> >> 
> >> Hi,
> >> 
> >> Sorry to come back on this subject but it is still not clear to me why we
> >> are using different subobject types between XRO and ERO/RRO/IRO in PCEP.
> >> 
> >> Is there any particular reason?
> >> 
> >> In http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-11.txt
> >>      Type   Subobject
> >>         1   IPv4 prefix
> >>         2   IPv6 prefix
> >>         4   Unnumbered Interface ID
> >>        32   Autonomous system number
> >> 
> >> In http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-xro-04.txt
> >> 
> >>         Type           Subobject
> >>         -------------+-------------------------------
> >>         1              IPv4 prefix
> >>         2              IPv6 prefix
> >>         3              Unnumbered Interface ID
> >>         4              Autonomous system number
> >>         5              SRLG
> >> 
> >> 
> >> Thanks
> >> Fabien
> >> 
> >> 
> >>> -----Message d'origine-----
> >>> De?: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] De la part de
> >>> Internet-Drafts@ietf.org
> >>> Envoy$Br"(B: mercredi 19 mars 2008 18:30
> >>> $B%?(B?: i-d-announce@ietf.org
> >>> Cc?: pce@ietf.org
> >>> Objet?: [Pce] I-D ACTION:draft-ietf-pce-pcep-xro-04.txt
> >>> 
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> >>> directories.
> >>> This draft is a work item of the Path Computation Element Working Group of
> >>> the IETF.
> >>> 
> >>> Title  : Extensions to the Path Computation Element
> >>> Communication Protocol (PCEP) for Route Exclusions
> >>> Author(s) : E. Oki, A. Farrel
> >>> Filename : draft-ietf-pce-pcep-xro-04.txt
> >>> Pages  : 16
> >>> Date  : 2008-3-19
> >>> 
> >>> The Path Computation Element (PCE) provides functions of path
> >>>    computation in support of traffic engineering in Multi-Protocol
> >>>    Label Switching (MPLS) and Generalized MPLS (GMPLS) networks.
> >>> 
> >>>    When a Path Computation Client (PCC) requests a PCE for a route, it
> >>>    may be useful for the PCC to specify, as constraints to the path
> >>>    computation, abstract nodes, resources, and Shared Risk Link Groups
> >>>    (SRLGs) that are to be explicitly excluded from the computed route.
> >>>    Such constraints are termed route exclusions.
> >>> 
> >>>    The PCE Communication Protocol (PCEP) is designed as a communication
> >>>    protocol between PCCs and PCEs. This document presents PCEP
> >>>    extensions for route exclusions.
> >>> 
> >>> A URL for this Internet-Draft is:
> >>> http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-xro-04.txt
> >>> 
> >>> Internet-Drafts are also available by anonymous FTP at:
> >>> ftp://ftp.ietf.org/internet-drafts/
> >>> 
> >>> Below is the data which will enable a MIME compliant mail reader
> >>> implementation to automatically retrieve the ASCII version of the
> >>> Internet-Draft.
> >> 
> >> _______________________________________________
> >> Pce mailing list
> >> Pce@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pce
> > 
> > _______________________________________________
> > Pce mailing list
> > Pce@ietf.org
> > https://www.ietf.org/mailman/listinfo/pce

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


From pce-bounces@ietf.org  Tue Mar 25 11:00:24 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8A3BB3A6D3D;
	Tue, 25 Mar 2008 11:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.591
X-Spam-Level: 
X-Spam-Status: No, score=-102.591 tagged_above=-999 required=5
	tests=[AWL=0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 IZ+v+Z5-USry; Tue, 25 Mar 2008 11:00:20 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 89E7E28C3BB;
	Tue, 25 Mar 2008 11:00:03 -0700 (PDT)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id E70C528C363; Tue, 25 Mar 2008 11:00:01 -0700 (PDT)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080325180001.E70C528C363@core3.amsl.com>
Date: Tue, 25 Mar 2008 11:00:01 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] I-D ACTION:draft-ietf-pce-pcep-xro-05.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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>
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Path Computation Element Working Group of the IETF.

	Title		: Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions
	Author(s)	: E. Oki, A. Farrel
	Filename	: draft-ietf-pce-pcep-xro-05.txt
	Pages		: 17
	Date		: 2008-3-25
	
The Path Computation Element (PCE) provides functions of path
   computation in support of traffic engineering in Multi-Protocol
   Label Switching (MPLS) and Generalized MPLS (GMPLS) networks.

   When a Path Computation Client (PCC) requests a PCE for a route, it
   may be useful for the PCC to specify, as constraints to the path
   computation, abstract nodes, resources, and Shared Risk Link Groups
   (SRLGs) that are to be explicitly excluded from the computed route.
   Such constraints are termed route exclusions.

   The PCE Communication Protocol (PCEP) is designed as a communication
   protocol between PCCs and PCEs. This document presents PCEP
   extensions for route exclusions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-xro-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pce-pcep-xro-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-3-25104754.I-D@ietf.org>


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

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

--NextPart--



From pce-bounces@ietf.org  Tue Mar 25 11:00:30 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F080C28C59F;
	Tue, 25 Mar 2008 11:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level: 
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5
	tests=[AWL=0.007, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 MgGAB6Yqp1J2; Tue, 25 Mar 2008 11:00:28 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8CBE828C46A;
	Tue, 25 Mar 2008 11:00:05 -0700 (PDT)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 047A828C3BB; Tue, 25 Mar 2008 11:00:01 -0700 (PDT)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080325180002.047A828C3BB@core3.amsl.com>
Date: Tue, 25 Mar 2008 11:00:02 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] I-D ACTION:draft-ietf-pce-pcep-12.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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>
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Path Computation Element Working Group of the IETF.

	Title		: Path Computation Element (PCE) Communication Protocol (PCEP)
	Author(s)	: A. Ayyangar, E. Oki, A. Atlas, A. Dolganow, Y. Ikejiri, K. Kumaki, J. Vasseur, J. Le Roux
	Filename	: draft-ietf-pce-pcep-12.txt
	Pages		: 76
	Date		: 2008-3-25
	
This document specifies the Path Computation Element Communication
   Protocol (PCEP) for communications between a Path Computation Client
   (PCC) and a Path Computation Element (PCE), or between two PCEs.
   Such interactions include path computation requests and path
   computation replies as well as notifications of specific states
   related to the use of a PCE in the context of Multiprotocol Label
   Switching (MPLS) and Generalized (GMPLS) Traffic Engineering.  PCEP
   is designed to be flexible and extensible so as to easily allow for
   the addition of further messages and objects, should further
   requirements be expressed in the future.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-12.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pce-pcep-12.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-3-25105739.I-D@ietf.org>


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

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

--NextPart--



From pce-bounces@ietf.org  Tue Mar 25 13:57:16 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EC7E83A6F23;
	Tue, 25 Mar 2008 13:57:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.906
X-Spam-Level: 
X-Spam-Status: No, score=-98.906 tagged_above=-999 required=5
	tests=[AWL=-0.536, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RCVD_NUMERIC_HELO=2.067, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
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 NS5SQ62bupKp; Tue, 25 Mar 2008 13:57:15 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC58D3A6C37;
	Tue, 25 Mar 2008 13:57:15 -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 14EB23A6BC4
	for <pce@core3.amsl.com>; Tue, 25 Mar 2008 13:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 mhFwc2DWLixw for <pce@core3.amsl.com>;
	Tue, 25 Mar 2008 13:57:13 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id E4A6D3A69B8
	for <pce@ietf.org>; Tue, 25 Mar 2008 13:57:13 -0700 (PDT)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 25 Mar 2008 13:54:55 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m2PKsrHR019196; 
	Tue, 25 Mar 2008 13:54:53 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m2PKspmN021015;
	Tue, 25 Mar 2008 20:54:53 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 25 Mar 2008 16:54:48 -0400
Received: from 161.44.71.244 ([161.44.71.244]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 25 Mar 2008 20:54:47 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Tue, 25 Mar 2008 16:54:46 -0400
From: JP Vasseur <jvasseur@cisco.com>
To: <pce@ietf.org>
Message-ID: <C40EDED6.305FB%jvasseur@cisco.com>
Thread-Topic: I-D ACTION:draft-ietf-pce-pcep-12.txt 
Thread-Index: AciOunUds5ckFPqtEdygCAANk8WjQA==
In-Reply-To: <20080325180002.047A828C3BB@core3.amsl.com>
Mime-version: 1.0
X-OriginalArrivalTime: 25 Mar 2008 20:54:48.0302 (UTC)
	FILETIME=[767CF0E0:01C88EBA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6305; t=1206478493;
	x=1207342493; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20FW=3A=20I-D=20ACTION=3Adraft-ietf-pce-pcep-12.t
	xt=20 |Sender:=20;
	bh=qWoBCdA9sLujuVWP3iTZQEIqkImmt5YIIKzWgu5BY40=;
	b=LIvNK/XkOiOEN73bcfu0SB1NB96JhkX4mhv8aTD2Al/Lvea7WOdDJqhCJt
	nD6b6gSAM5+i7ekB0G+BEZGqBrlxI+OmVVvpfB88torRd/KD5fDL1ab0OgUo
	oWbphOK6M1;
Authentication-Results: sj-dkim-2; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: [Pce] FW: I-D ACTION:draft-ietf-pce-pcep-12.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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,

While discussing other IDs in LC (BRPC, XRO), we found a few very cosmetic
changes that we should better handle in PCEPs (in rev-12).

We just introduce two error subcodes that are needed now so that we are
forward compatible.

Section 7.15
OLD
   3          Unknown Object
               Error-value=1: Unrecognized object class
               Error-value=2: Unrecognized object Type
   4          Not supported object
               Error-value=1: Not supported object class
               Error-value=2: Not supported object Type
NEW
   3          Unknown Object
               Error-value=1: Unrecognized object class
               Error-value=2: Unrecognized object type
               Error-value=3: Unrecognized subobject type
               Error-value=4: Unrecognized parameter

   4          Not supported object
               Error-value=1: Not supported object class
               Error-value=2: Not supported object type
               Error-value=3: Unsupported subobject type
               Error-value=4: Unsupported parameter
===
Section 7.15
OLD
   Error-Type=3 or Error-Type=4: if a PCEP message is received that
   carries a PCEP object (with the P flag set) not recognized by the PCE
   or recognized but not supported, then the PCE MUST send a PCErr
   message with a PCEP-ERROR object (Error-Type=3 and 4 respectively).
   In addition, the PCE MAY include in the PCErr message the unknown or
   not supported object.  The corresponding path computation request
   MUST be cancelled by the PCE without further notification.
NEW
   Error-Type=3 or Error-Type=4: if a PCEP message is received that
   carries a PCEP object (with the P flag set) not recognized by the PCE
   or recognized but not supported, then the PCE MUST send a PCErr
   message with a PCEP-ERROR object (Error-Type=3 and 4 respectively).
   If the object type or object class is unknown or unsupported, the PCE
   MAY include in the PCErr message the unknown or not supported object.
   Furthermore, if a subobject or parameter is unknown or unsupported,
   the PCE MAY include the parent object up to and including (but no
   further than) the unknown or unsupported subobject or parameter. In
   the case where the unknown or unsupported parameter is a bit flag, the
   included object should contain the whole bit flag field with all bits
   after the parameter at issue set to zero. The corresponding path
   computation request MUST be cancelled by the PCE without further
   notification.
===
Section 9.2.5
OLD
   3    Unknown Object                                     This document
          Error-value=1:                                   This document
            Unrecognized object class
          Error-value=2:                                   This document
            Unrecognized object Type

   4    Not supported object                               This document
          Error-value=1:
            Unsupported object class.                      This document
          Error-value=2:
            Unsupported object Type.                       This document

NEW
   3    Unknown Object                                     This document
          Error-value=1:                                   This document
            Unrecognized object class
          Error-value=2:                                   This document
            Unrecognized object type
          Error-value=3:                                   This document
            Unrecognized subobject type
          Error-value=4:                                   This document
            Unrecognized parameter

   4    Not supported object                               This document
          Error-value=1:
            Unsupported object class.                      This document
          Error-value=2:
            Unsupported object type.                       This document
          Error-value=3:
            Unsupported subobject type.                    This document
          Error-value=4:
            Unsupported parameter.                         This document
===




------ Forwarded Message
> From: <Internet-Drafts@ietf.org>
> Reply-To: <internet-drafts@ietf.org>
> Date: Tue, 25 Mar 2008 11:00:02 -0700 (PDT)
> To: <i-d-announce@ietf.org>
> Cc: <pce@ietf.org>
> Subject: I-D ACTION:draft-ietf-pce-pcep-12.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Path Computation Element Working Group of the
> IETF.
> 
> Title  : Path Computation Element (PCE) Communication Protocol (PCEP)
> Author(s) : A. Ayyangar, E. Oki, A. Atlas, A. Dolganow, Y. Ikejiri, K. Kumaki,
> J. Vasseur, J. Le Roux
> Filename : draft-ietf-pce-pcep-12.txt
> Pages  : 76
> Date  : 2008-3-25
> 
> This document specifies the Path Computation Element Communication
>    Protocol (PCEP) for communications between a Path Computation Client
>    (PCC) and a Path Computation Element (PCE), or between two PCEs.
>    Such interactions include path computation requests and path
>    computation replies as well as notifications of specific states
>    related to the use of a PCE in the context of Multiprotocol Label
>    Switching (MPLS) and Generalized (GMPLS) Traffic Engineering.  PCEP
>    is designed to be flexible and extensible so as to easily allow for
>    the addition of further messages and objects, should further
>    requirements be expressed in the future.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-12.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 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: <2008-3-25105739.I-D@ietf.org>
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

------ End of Forwarded Message

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


From pce-bounces@ietf.org  Tue Mar 25 18:06:04 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D09E83A6AB2;
	Tue, 25 Mar 2008 18:06:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.28
X-Spam-Level: 
X-Spam-Status: No, score=-100.28 tagged_above=-999 required=5
	tests=[AWL=0.157, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 ZT-j6nbLDozN; Tue, 25 Mar 2008 18:06:03 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D502B3A6BAB;
	Tue, 25 Mar 2008 18:06:03 -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 E70533A69C1
	for <pce@core3.amsl.com>; Tue, 25 Mar 2008 18:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 kMWg5COe+YJq for <pce@core3.amsl.com>;
	Tue, 25 Mar 2008 18:05:56 -0700 (PDT)
Received: from tama500.ecl.ntt.co.jp (tama500.ecl.ntt.co.jp [129.60.39.148])
	by core3.amsl.com (Postfix) with ESMTP id C28DE3A6BAB
	for <pce@ietf.org>; Tue, 25 Mar 2008 18:05:55 -0700 (PDT)
Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149])
	by tama500.ecl.ntt.co.jp (8.14.2/8.14.2) with ESMTP id m2Q13ZBG013393
	for <pce@ietf.org>; Wed, 26 Mar 2008 10:03:35 +0900 (JST)
Received: from mfs6.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 311E16BFF
	for <pce@ietf.org>; Wed, 26 Mar 2008 10:03:35 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (eclscan2.m.ecl.ntt.co.jp
	[129.60.5.68])
	by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 2AAB16BFE
	for <pce@ietf.org>; Wed, 26 Mar 2008 10:03:35 +0900 (JST)
Received: from eclscan2.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2Q13YLV027254
	for <pce@ietf.org>; Wed, 26 Mar 2008 10:03:34 +0900 (JST)
Received: from imb.m.ecl.ntt.co.jp (imb0.m.ecl.ntt.co.jp [129.60.5.140])
	by eclscan2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id
	m2Q13YBG027240
	for <pce@ietf.org>; Wed, 26 Mar 2008 10:03:34 +0900 (JST)
Received: from [129.60.80.54] ([129.60.80.54])
	by imb.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id m2Q13XaV018514
	for <pce@ietf.org>; Wed, 26 Mar 2008 10:03:33 +0900 (JST)
Date: Wed, 26 Mar 2008 10:02:42 +0900
From: Eiji Oki <oki.eiji@lab.ntt.co.jp>
To: pce@ietf.org
Message-Id: <20080326094138.4BA5.OKI.EIJI@lab.ntt.co.jp>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="------_47E99BC24BA209B6E908_MULTIPART_MIXED_"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.30.04 [ja]
Subject: [Pce] Fw: I-D ACTION:draft-ietf-pce-pcep-xro-05.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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>
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

--------_47E99BC24BA209B6E908_MULTIPART_MIXED_
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit

Hi all, 

Major changes on XRO-05 from XRO-04 are as follows, by incorporating
Fabien's comments on subobject types and PCEP-12 updates.

2.2.2. Processing Rules
Second and third paragraphs.

4.IANA Considerations
sections 4.1-4.4 are revised on PCEP subobject, Error Object Field
Values and flags.

7.1. Normative References
[RFC3209] was added.

Thank you.
Eiji

Forwarded by Eiji Oki <oki.eiji@lab.ntt.co.jp>
----------------------- Original Message -----------------------
 From:    Internet-Drafts@ietf.org
 To:      i-d-announce@ietf.org
 Cc:      pce@ietf.org
 Date:    Tue, 25 Mar 2008 11:00:01 -0700 (PDT)
 Subject: I-D ACTION:draft-ietf-pce-pcep-xro-05.txt 
----

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Path Computation Element Working Group of the IETF.

	Title		: Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions
	Author(s)	: E. Oki, A. Farrel
	Filename	: draft-ietf-pce-pcep-xro-05.txt
	Pages		: 17
	Date		: 2008-3-25
	
The Path Computation Element (PCE) provides functions of path
   computation in support of traffic engineering in Multi-Protocol
   Label Switching (MPLS) and Generalized MPLS (GMPLS) networks.

   When a Path Computation Client (PCC) requests a PCE for a route, it
   may be useful for the PCC to specify, as constraints to the path
   computation, abstract nodes, resources, and Shared Risk Link Groups
   (SRLGs) that are to be explicitly excluded from the computed route.
   Such constraints are termed route exclusions.

   The PCE Communication Protocol (PCEP) is designed as a communication
   protocol between PCCs and PCEs. This document presents PCEP
   extensions for route exclusions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-xro-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--------------------- Original Message Ends --------------------

--
Eiji Oki, Ph. D.
Senior Research Engineer
NTT Network Service Systems Laboratories
3-9-11 Midori-cho Musashino-shi, Tokyo 180-8585 Japan
Tel: +81-422-59-3441, Fax: +81-422-59-3787
E-mail: oki.eiji@lab.ntt.co.jp

--
$BBgLZ1Q;J(B
NTT$B%M%C%H%o!<%/%5!<%S%9%7%9%F%`8&5f=j(B
$B")(B180-8585 $BEl5~ETIpB"Ln;TNPD.(B3-9-11
Tel: 0422-59-3441, Fax: 0422-59-3787
E-mail: oki.eiji@lab.ntt.co.jp

--------_47E99BC24BA209B6E908_MULTIPART_MIXED_
Content-Type: Message/External-body;
 name="draft-ietf-pce-pcep-xro-05.txt";
 site="ftp.ietf.org";
 access-type="anon-ftp";
 directory="internet-drafts"
Content-Disposition: attachment;
 filename="draft-ietf-pce-pcep-xro-05.txt"
Content-Transfer-Encoding: 7bit

Content-Type: text/plain
Content-ID: <2008-3-25104754.I-D@ietf.org>


--------_47E99BC24BA209B6E908_MULTIPART_MIXED_
MIME-Version: 1.0
Content-Type: text/plain;
 charset="us-ascii"
Content-Disposition: attachment;
 filename=forward.txt
Content-Transfer-Encoding: 7bit

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

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

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

--------_47E99BC24BA209B6E908_MULTIPART_MIXED_--



From pce-bounces@ietf.org  Sat Mar 29 07:49:54 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8716C3A6A0A;
	Sat, 29 Mar 2008 07:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.879
X-Spam-Level: 
X-Spam-Status: No, score=-100.879 tagged_above=-999 required=5
	tests=[AWL=-0.442, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 Utn2xswLJ8cy; Sat, 29 Mar 2008 07:49:53 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C8C633A6C73;
	Sat, 29 Mar 2008 07:49:53 -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 1D3403A6C73
	for <pce@core3.amsl.com>; Sat, 29 Mar 2008 07:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 b5llMGq6hpib for <pce@core3.amsl.com>;
	Sat, 29 Mar 2008 07:49:51 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 0960F3A6A0A
	for <pce@ietf.org>; Sat, 29 Mar 2008 07:49:49 -0700 (PDT)
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
	m2TEne1w019753 for <pce@ietf.org>; Sat, 29 Mar 2008 14:49:42 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
	m2TEnccJ019745 for <pce@ietf.org>; Sat, 29 Mar 2008 14:49:40 GMT
Message-ID: <060301c891ac$18abbdd0$0300a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Sat, 29 Mar 2008 14:49:28 -0000
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] Don't Forget: Two working group last calls
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

Don't forget to do you last minute review of these drafts.

We've had some comments on BRPC, but silence on the inter-AS ID. I'd at 
least like some evidence that people have read the draft.

Thanks,
Adrian
----- Original Message ----- 
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Sent: Tuesday, March 11, 2008 7:44 PM
Subject: [Pce] Two working group last calls


> Hi,
>
> As discussed in the PCE WG meeting, this email commences a two week 
> working
> group last call on the following two drafts.
>
> BRPC
> http://www.ietf.org/internet-drafts/draft-ietf-pce-brpc-07.txt
>
> Inter-AS PCEP requirements
> http://www.ietf.org/internet-drafts/draft-ietf-pce-interas-pcecp-reqs-04.txt
>
> Please send comments to the list.
>
> The last call will end on Monday March 31st at 12 noon GMT. That is almost
> three weeks (because it overlaps with the IETF meeting) but please review
> early and often.
>
> Thanks,
> Adrian
>
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
> 


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


From pce-bounces@ietf.org  Sat Mar 29 12:15:46 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6FDD528C274;
	Sat, 29 Mar 2008 12:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.966
X-Spam-Level: 
X-Spam-Status: No, score=-100.966 tagged_above=-999 required=5
	tests=[AWL=-0.756, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227,
	USER_IN_WHITELIST=-100]
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 tl-zGZLvB3Ax; Sat, 29 Mar 2008 12:15:45 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4C6F13A6BC4;
	Sat, 29 Mar 2008 12:15:45 -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 776573A6BC4
	for <pce@core3.amsl.com>; Sat, 29 Mar 2008 12:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 HUB8myvubMUV for <pce@core3.amsl.com>;
	Sat, 29 Mar 2008 12:15:40 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 692743A6BE0
	for <pce@ietf.org>; Sat, 29 Mar 2008 12:15:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,575,1199682000"; 
   d="scan'208";a="3416436"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 29 Mar 2008 15:15:39 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m2TJFdV4025228
	for <pce@ietf.org>; Sat, 29 Mar 2008 15:15:39 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m2TJFcUr019300
	for <pce@ietf.org>; Sat, 29 Mar 2008 19:15:38 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 29 Mar 2008 15:15:38 -0400
Received: from 10.86.104.186 ([10.86.104.186]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Sat, 29 Mar 2008 19:15:38 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Sat, 29 Mar 2008 15:15:37 -0400
From: JP Vasseur <jvasseur@cisco.com>
To: <pce@ietf.org>
Message-ID: <C4140D99.3149F%jvasseur@cisco.com>
Thread-Topic: LC comments on draft-ietf-pce-interas-pcecp-reqs-04.txt
Thread-Index: AciR0UTjg1Fibf3EEdym2wANk8WjQA==
Mime-version: 1.0
X-OriginalArrivalTime: 29 Mar 2008 19:15:38.0897 (UTC)
	FILETIME=[4604C810:01C891D1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7200; t=1206818139;
	x=1207682139; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20LC=20comments=20on=20draft-ietf-pce-interas-pce
	cp-reqs-04.txt |Sender:=20 |To:=20<pce@ietf.org>;
	bh=ZK41aBCc+v9ErY12v8WUPtKJQAF09nvyXGTlzFprEV8=;
	b=OR1wzwQe62oU2hvcnhTwi5Hf2fLZg+1MMP8QpeYqzMUFbjhPHaXXKqwkqQ
	kXkE4PdAaO5BzTsxU9dE03zNPKoZ67BaDSlQMwl+jMJy815JsdQ1KIp0IUwh
	mOYJW2CBmT;
Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: [Pce] LC comments on draft-ietf-pce-interas-pcecp-reqs-04.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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,

Here are some last call comments on draft-ietf-pce-brpc-07.txt

  Checking references for intended status: Informational
  
----------------------------------------------------------------------------

== Outdated reference: draft-ietf-ccamp-inter-domain-rsvp-te has been
   published as RFC 5151

== Outdated reference: draft-ietf-ccamp-lsp-stitching has been published as
   RFC 5150

== Outdated reference: draft-ietf-ccamp-inter-domain-pd-path-comp has been
   published as RFC 5152

Other comments
##############

* First page: All authors are editors so you can remove "Editors" after the
names.

* Please make sure that the title and all section headings use capitals

* Just to be consistent with several other documents: s/ MPLS-TE/ MPLS TE

* s/definition/Terminology for the title of section 2.

* There are several places in the document where it would be preferable to
replace "path" by "constrained path". Ex:
" The mechanisms in [INTERD-TE-PDPC]
do not guarantee an optimum path across multiple ASes where an
optimum path for an LSP is one that has the smallest cost"

*  s/ TE-constraints/TE constraints.

* You may want to use a consistent terminology throughout the document:
"inter-AS route", "inter-AS path", "inter-AS TE LSP".

* In the introduction please expand acronyms when first used: LSPs, (G)MPLS.

* Section 3

- s/ "R1 in AS1 wants to setup a MPLS-TE or a GMPLS path"/ "R1 in AS1 wants
   to setup (G)MPLS TE LSP"
- s/ "R1, as a PCC, sends a PCECP path request to PCE1"/ "R1, as a
   PCC, sends a PCECP path computation request to PCE1".
- s/ " PCE1 sends a PCECP path request to PCE2"/" PCE1 sends a PCECP path
computation request to PCE2"
- You wrote:  " R4 returns a PCECP path response to PCE2 with ASBR3 as
    the entry point to AS2 from AS1 and ASBR7 as the exit point to AS3.
   PCE2 then sends a PCECP path request to PCE3 to compute the path
   segment across AS3, starting at ASBR7 and terminating at R7."

You may want to indicate that the choice of ASBR7 is taken for the sake of
illustration.


* Section 4:

- " This section discusses detailed PCECP requirements for inter-AS
   MPLS-TE and GMPLS LSPs."
May be a bit confusion ... How about " This section discusses detailed PCECP
requirements for inter-AS (G)MPLS TE"

- " Specifically, some requirements are more applicable to inter-
   provider inter-AS MPLS-TE and GMPLS operations than to intra-
   provider operations. "

Is a bit ambiguous. How about:

 " Specifically, some requirements are more applicable to inter-
   provider inter-AS than to intra-provider inter-AS MPLS TE and GMPLS
operations. "

- " 1. [RFC4657] states the requirement for a priority level to be
   associated with each path computation request. This document does
   not change that requirement, but, in addition, it MUST be possible
   for an inter-AS PCE to apply local policy to vary the priority of
   path computation requests received across AS borders."

Since the policy is local, why is this a requirement for the PCECP?

- "4. A PCECP path request from one inter-AS PCE to another MUST
   include the previous AS number in the path of the LSP to enable the
   correct application of local policy at the second inter-AS PCE. "

Don't you mean ? :

"4. The PCECP MUST provide the ability to include the previous AS number in
the path of the LSP in a path computation request from one inter-AS PCE to
another. That to enable the correct application of local policy at the
second inter-AS PCE. "

- "6. PCECP MUST support the disjoint path requirements specified in
   [RFC4657] and MUST further allow the specification of AS-diversity
   for the computation of a set of two or more paths. "

The first MUST should be removed here since it is specified in RFC4657. It
should read:

"6. As specified in [RFC4657], PCECP must support the disjoint path
requirements. In addition to this requirement, PCECP MUST further allow the
specification of AS-diversity for the computation of a set of two or more
paths. "

Section 4.1.2

- " 6. A PCECP path computation response MUST be able to identify
diversified paths for the same (G)MPLS-TE LSP."

What did you mean by "same" here?

Section 4.3

- " The PCECP MIB module MUST provide objects to control the behavior of
   PCECP in inter-AS applications.  They include the ASes within the
   scope of an inter-AS PCE, Inter-AS PCEs in neighboring ASes to which
   the requesting PCE will or will not communicate, confidentiality and
   policies, etc.. "

Since you enumerate "objects", it is a bit awkward to terminate the sentence
by "etc ..." You may want to either provide the exhaustive list or remove
the "etc".

Section 4.4

- S/" Confidentiality rules may also apply among ASes under a single
Provider"/" Confidentiality rules may also apply among ASes under a single
SP"

- Just a terminology issue:

" Each SP will in most cases designate some PCEs for inter-AS
MPLS-TE or GMPLS path computation within its own administrative domain
and some other PCEs for inter-provider inter-AS MPLS-TE or GMPLS path
computation."

In several places you use the term "inter-AS MPLS-TE or GMPLS path
computation". You may want to replace it by "inter-AS (G)MPLS TE path
computation".

- s/" PCECP SHOULD allow an SP to hide from other SPs the set of hops
   within its own ASes that are traversed by an inter-AS inter-provider
   LSP (c.f., Section 5.2.1 of [RFC4216])."/" PCECP SHOULD allow an SP to
hide from other SPs the set of hops within its own ASes that are traversed
by an inter-AS inter-provider TE LSP (c.f., Section 5.2.1 of [RFC4216])."
                             ^^^^
Please make sure to consistently use "TE LSP": you are using LSP, TE LSP,
...

- In section 4.1.2:

" 2. A PCECP path computation response from one inter-AS PCE to the
requesting inter-AS PCE MUST be able to carry an identifier for a path
segment it computes to preserve path segment and topology
confidentiality. The objective of the identifier is to be included in
the LSP signaling, whose mechanism is out of scope of this document, to
be used for path expansion during LSP signaling."

Then in section 4.4, you write:

" PCECP SHOULD allow an SP to hide from other SPs the set of hops
   within its own ASes that are traversed by an inter-AS inter-provider
   LSP (c.f., Section 5.2.1 of [RFC4216]). "

And in section 5.3:

"5.3. Confidentiality
 
The PCECP SHOULD also provide mechanism to preserve the confidentiality
of path segments computed by a PCE in one AS and provided to a
computation response in another AS. "


Should the SHOULD be MUST here to be consistent?

Section 5.3

- "Not only is it necessary for such
mechanisms to be provided in PCECP responses, but signaling messages
MUST also provide mechanisms such that an ASBR receiving an incoming
signaling request can apply policy to reject signaling messages that do
not contain the computation responses produced by the local PCE."

The issue is that the MUST applies to signaling ... This document is about
PCECP.

Thanks.

JP.

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


From pce-bounces@ietf.org  Sat Mar 29 13:19:52 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: ietfarch-pce-archive@core3.amsl.com
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D74DF3A6CDB;
	Sat, 29 Mar 2008 13:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.908
X-Spam-Level: 
X-Spam-Status: No, score=-100.908 tagged_above=-999 required=5
	tests=[AWL=-0.698, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227,
	USER_IN_WHITELIST=-100]
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 SerPwgVvtO03; Sat, 29 Mar 2008 13:19:51 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 949363A6D0E;
	Sat, 29 Mar 2008 13:19:51 -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 0E68D3A6D0E
	for <pce@core3.amsl.com>; Sat, 29 Mar 2008 13:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 JPmBkp2zSnH3 for <pce@core3.amsl.com>;
	Sat, 29 Mar 2008 13:19:48 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 5CC493A6CDB
	for <pce@ietf.org>; Sat, 29 Mar 2008 13:19:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,576,1199682000"; 
   d="scan'208";a="3409966"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 29 Mar 2008 16:19:46 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m2TKJkIL014349
	for <pce@ietf.org>; Sat, 29 Mar 2008 16:19:46 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m2TKJkmO005884
	for <pce@ietf.org>; Sat, 29 Mar 2008 20:19:46 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 29 Mar 2008 16:19:45 -0400
Received: from 10.86.104.186 ([10.86.104.186]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Sat, 29 Mar 2008 20:19:45 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Sat, 29 Mar 2008 16:19:44 -0400
From: JP Vasseur <jvasseur@cisco.com>
To: <pce@ietf.org>
Message-ID: <C4141CA0.314AC%jvasseur@cisco.com>
Thread-Topic: LC comments on draft-ietf-pce-interas-pcecp-reqs-04.txt
Thread-Index: AciR0UTjg1Fibf3EEdym2wANk8WjQAACPT9O
In-Reply-To: <C4140D99.3149F%jvasseur@cisco.com>
Mime-version: 1.0
X-OriginalArrivalTime: 29 Mar 2008 20:19:45.0970 (UTC)
	FILETIME=[3B0D8920:01C891DA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7999; t=1206821986;
	x=1207685986; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20FW=3A=20LC=20comments=20on=20draft-ietf-pce-int
	eras-pcecp-reqs-04.txt |Sender:=20 |To:=20<pce@ietf.org>;
	bh=Ig/Zci9gWT6g+wronswc0broJ5viyvY4s6QVwbgm7k4=;
	b=iVwd2utIIAjvF3H5pUXqgQERwm9XWAR80KhzTZ61xRsOjE0vmf4K2DYGz2
	01AGEb8Eu6toNeMEwKpv9LnmEao315xQ/20SUICCWLVtpJNd2MpEdkiDa2f2
	1VApQPtX/0;
Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: [Pce] FW: LC comments on draft-ietf-pce-interas-pcecp-reqs-04.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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



------ Forwarded Message
> From: JP Vasseur <jvasseur@cisco.com>
> Date: Sat, 29 Mar 2008 15:15:37 -0400
> To: <pce@ietf.org>
> Conversation: LC comments on draft-ietf-pce-interas-pcecp-reqs-04.txt
> Subject: LC comments on draft-ietf-pce-interas-pcecp-reqs-04.txt
> 
> Hi,
> 
> Here are some last call comments on draft-ietf-pce-brpc-07.txt
> 

Of course it should read Here are some last call comments on
draft-ietf-pce-interas-pcecp-reqs-04.txt

>   Checking references for intended status: Informational
>   ----------------------------------------------------------------------------
> 
> == Outdated reference: draft-ietf-ccamp-inter-domain-rsvp-te has been
>    published as RFC 5151
> 
> == Outdated reference: draft-ietf-ccamp-lsp-stitching has been published as
>    RFC 5150
> 
> == Outdated reference: draft-ietf-ccamp-inter-domain-pd-path-comp has been
>    published as RFC 5152
> 
> Other comments
> ##############
> 
> * First page: All authors are editors so you can remove "Editors" after the
> names.
> 
> * Please make sure that the title and all section headings use capitals
> 
> * Just to be consistent with several other documents: s/ MPLS-TE/ MPLS TE
> 
> * s/definition/Terminology for the title of section 2.
> 
> * There are several places in the document where it would be preferable to
> replace "path" by "constrained path". Ex:
> " The mechanisms in [INTERD-TE-PDPC]
> do not guarantee an optimum path across multiple ASes where an
> optimum path for an LSP is one that has the smallest cost"
> 
> *  s/ TE-constraints/TE constraints.
> 
> * You may want to use a consistent terminology throughout the document:
> "inter-AS route", "inter-AS path", "inter-AS TE LSP".
> 
> * In the introduction please expand acronyms when first used: LSPs, (G)MPLS.
> 
> * Section 3
> 
> - s/ "R1 in AS1 wants to setup a MPLS-TE or a GMPLS path"/ "R1 in AS1 wants
>    to setup (G)MPLS TE LSP"
> - s/ "R1, as a PCC, sends a PCECP path request to PCE1"/ "R1, as a
>    PCC, sends a PCECP path computation request to PCE1".
> - s/ " PCE1 sends a PCECP path request to PCE2"/" PCE1 sends a PCECP path
> computation request to PCE2"
> - You wrote:  " R4 returns a PCECP path response to PCE2 with ASBR3 as
>     the entry point to AS2 from AS1 and ASBR7 as the exit point to AS3.
>    PCE2 then sends a PCECP path request to PCE3 to compute the path
>    segment across AS3, starting at ASBR7 and terminating at R7."
> 
> You may want to indicate that the choice of ASBR7 is taken for the sake of
> illustration.
> 
> 
> * Section 4:
> 
> - " This section discusses detailed PCECP requirements for inter-AS
>    MPLS-TE and GMPLS LSPs."
> May be a bit confusion ... How about " This section discusses detailed PCECP
> requirements for inter-AS (G)MPLS TE"
> 
> - " Specifically, some requirements are more applicable to inter-
>    provider inter-AS MPLS-TE and GMPLS operations than to intra-
>    provider operations. "
> 
> Is a bit ambiguous. How about:
> 
>  " Specifically, some requirements are more applicable to inter-
>    provider inter-AS than to intra-provider inter-AS MPLS TE and GMPLS
> operations. "
> 
> - " 1. [RFC4657] states the requirement for a priority level to be
>    associated with each path computation request. This document does
>    not change that requirement, but, in addition, it MUST be possible
>    for an inter-AS PCE to apply local policy to vary the priority of
>    path computation requests received across AS borders."
> 
> Since the policy is local, why is this a requirement for the PCECP?
> 
> - "4. A PCECP path request from one inter-AS PCE to another MUST
>    include the previous AS number in the path of the LSP to enable the
>    correct application of local policy at the second inter-AS PCE. "
> 
> Don't you mean ? :
> 
> "4. The PCECP MUST provide the ability to include the previous AS number in
> the path of the LSP in a path computation request from one inter-AS PCE to
> another. That to enable the correct application of local policy at the second
> inter-AS PCE. "
> 
> - "6. PCECP MUST support the disjoint path requirements specified in
>    [RFC4657] and MUST further allow the specification of AS-diversity
>    for the computation of a set of two or more paths. "
> 
> The first MUST should be removed here since it is specified in RFC4657. It
> should read:
> 
> "6. As specified in [RFC4657], PCECP must support the disjoint path
> requirements. In addition to this requirement, PCECP MUST further allow the
> specification of AS-diversity for the computation of a set of two or more
> paths. "
> 
> Section 4.1.2
> 
> - " 6. A PCECP path computation response MUST be able to identify
> diversified paths for the same (G)MPLS-TE LSP."
> 
> What did you mean by "same" here?
> 
> Section 4.3
> 
> - " The PCECP MIB module MUST provide objects to control the behavior of
>    PCECP in inter-AS applications.  They include the ASes within the
>    scope of an inter-AS PCE, Inter-AS PCEs in neighboring ASes to which
>    the requesting PCE will or will not communicate, confidentiality and
>    policies, etc.. "
> 
> Since you enumerate "objects", it is a bit awkward to terminate the sentence
> by "etc ..." You may want to either provide the exhaustive list or remove the
> "etc".
> 
> Section 4.4
> 
> - S/" Confidentiality rules may also apply among ASes under a single
> Provider"/" Confidentiality rules may also apply among ASes under a single
> SP"
> 
> - Just a terminology issue:
> 
> " Each SP will in most cases designate some PCEs for inter-AS
> MPLS-TE or GMPLS path computation within its own administrative domain
> and some other PCEs for inter-provider inter-AS MPLS-TE or GMPLS path
> computation."
> 
> In several places you use the term "inter-AS MPLS-TE or GMPLS path
> computation". You may want to replace it by "inter-AS (G)MPLS TE path
> computation".
> 
> - s/" PCECP SHOULD allow an SP to hide from other SPs the set of hops
>    within its own ASes that are traversed by an inter-AS inter-provider
>    LSP (c.f., Section 5.2.1 of [RFC4216])."/" PCECP SHOULD allow an SP to hide
> from other SPs the set of hops within its own ASes that are traversed by an
> inter-AS inter-provider TE LSP (c.f., Section 5.2.1 of [RFC4216])."
>                              ^^^^
> Please make sure to consistently use "TE LSP": you are using LSP, TE LSP, ...
> 
> - In section 4.1.2:
> 
> " 2. A PCECP path computation response from one inter-AS PCE to the
> requesting inter-AS PCE MUST be able to carry an identifier for a path
> segment it computes to preserve path segment and topology
> confidentiality. The objective of the identifier is to be included in
> the LSP signaling, whose mechanism is out of scope of this document, to
> be used for path expansion during LSP signaling."
> 
> Then in section 4.4, you write:
> 
> " PCECP SHOULD allow an SP to hide from other SPs the set of hops
>    within its own ASes that are traversed by an inter-AS inter-provider
>    LSP (c.f., Section 5.2.1 of [RFC4216]). "
> 
> And in section 5.3:
> 
> "5.3. Confidentiality
>  
> The PCECP SHOULD also provide mechanism to preserve the confidentiality
> of path segments computed by a PCE in one AS and provided to a
> computation response in another AS. "
> 
> 
> Should the SHOULD be MUST here to be consistent?
> 
> Section 5.3
> 
> - "Not only is it necessary for such
> mechanisms to be provided in PCECP responses, but signaling messages
> MUST also provide mechanisms such that an ASBR receiving an incoming
> signaling request can apply policy to reject signaling messages that do
> not contain the computation responses produced by the local PCE."
> 
> The issue is that the MUST applies to signaling ... This document is about
> PCECP.
> 
> Thanks.
> 
> JP.

------ End of Forwarded Message

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


From pce-bounces@ietf.org  Mon Mar 31 07:47:35 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 821663A6AC3;
	Mon, 31 Mar 2008 07:47:35 -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 89ADA3A6AC3
	for <pce@core3.amsl.com>; Mon, 31 Mar 2008 07:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396,
	RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067]
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 1BpOY9LhXvKa for <pce@core3.amsl.com>;
	Mon, 31 Mar 2008 07:47:24 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 019BA3A6930
	for <pce@ietf.org>; Mon, 31 Mar 2008 07:47:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,583,1199682000"; d="scan'208,217";a="3507453"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 31 Mar 2008 10:47:00 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m2VEl0h5004896; 
	Mon, 31 Mar 2008 10:47:00 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m2VEl0iM014986;
	Mon, 31 Mar 2008 14:47:00 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 31 Mar 2008 10:47:00 -0400
Received: from 161.44.71.244 ([161.44.71.244]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 31 Mar 2008 14:47:00 +0000
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Mon, 31 Mar 2008 10:46:59 -0400
From: JP Vasseur <jvasseur@cisco.com>
To: Adrian Farrel <adrian@olddog.co.uk>, <pce@ietf.org>
Message-ID: <C41671A3.3173B%jvasseur@cisco.com>
Thread-Topic: [Pce] BRPC last call comments
Thread-Index: AciTPhKjUPS3J/8xEdysSAANk8WjQA==
In-Reply-To: <0de901c88de7$0b2d2950$0200a8c0@your029b8cecfe>
Mime-version: 1.0
X-OriginalArrivalTime: 31 Mar 2008 14:47:00.0686 (UTC)
	FILETIME=[13A476E0:01C8933E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=20356; t=1206974820;
	x=1207838820; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:=20JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:=20Re=3A=20[Pce]=20BRPC=20last=20call=20comments
	|Sender:=20
	|To:=20Adrian=20Farrel=20<adrian@olddog.co.uk>,=20<pce@ietf
	.org>; bh=UywKSIQSFKdNYtMWcTAaA2wwJ7Rx1rw1w36IFLiFds8=;
	b=hogn1ml5yv1r9SZc6ET4LzOPM/G8aWOIkAKFr2lpP65axDFRNgIYBsUQ7g
	LABgabMOJ4g7WVNAj3kRznb7U8LTjcJL+19TyS+wLzUR7uVvZ8Ix+rAB8vaR
	d/wZQ73tOy;
Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: Re: [Pce] BRPC last call comments
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: multipart/mixed; boundary="===============2043892477=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============2043892477==
Content-type: multipart/alternative;
	boundary="B_3289805219_1583891"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3289805219_1583891
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Hi,

Sorry for the one week interruption in the thread ... Back to addressing th=
e
last comments, then I=B9ll post the new revision.

See in line.


From: Adrian Farrel <adrian@olddog.co.uk>
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
Date: Mon, 24 Mar 2008 19:40:47 -0000
To: JP Vasseur <jvasseur@cisco.com>, <pce@ietf.org>
Subject: Re: [Pce] BRPC last call comments

Hi JP,
=20
Thanks for the quick progress.
=20
Snipped everything where we have reached conclusion...
=20
>> Section 4.2
>> Is "Definition of VSPT(i)" intended to be a subsection?
>> I find that the section leaps to rapidly into the definition of the VSPT=
.
>> Shouldn't there be some discussion first (somewhere) about the sequence =
of
>> exchange of information between PCC and PCEs? This isn't much informatio=
n,
>> but seeing the VSPT(i) described as "tree returned by PCE(i) to PCE(i-1)=
"
>> makes me wonder how the PCEs are joined together.
>=20
> This is explained in the text right after. Do you think that we need to a=
dd
> even more text there?
Well, I don't think it is crystal clear. Or rather, it *is* crystal clear,
but the crystal is smokey quartz
(http://gwydir.demon.co.uk/jo/minerals/otherquartz.htm
<http://gwydir.demon.co.uk/jo/minerals/otherquartz.htm> )

JP> ;-)
=20
How about a simple paragraph about the basic operation of BRPC such as...
=20
The BRPC procedure relies on communication between cooperating PCEs. In
particular, the PCC sends a PCReq to a PCE in its domain. The request is
forwarded between PCEs, domain-by-domain until the PCE responsible for the
domain containing the LSP destination is reached. The PCE in the destinatio=
n
domain creates a tree of potential paths to the destination (the Virtual
Shortest Path Tree - VSPT) and passes this back to the previous PCE in a
PCRep. Each PCE in turn adds to the VSPT and passes it back until the PCE i=
n
the source domain uses the VSPT to select an end-to-end path that it sends
to the PCC.
=20
JP> Well does not hurt ;-) I added it, thanks.

>> Section 4.2
>>    Step i:
>>=20
>>    - For i=3Dn-1 to 2: PCE(i) concatenates the topology of domain(i)
>>    (using its TED) with the received VSPT(i+1).
>>=20
>> I don't like "concatenates the topology". Don't you mean...
>>    Step i:
>>=20
>>    - For i=3Dn-1 to 2: PCE(i) computes the shortest constrained paths from
>>      each BN-en(i) to each BN-ex(i) that is identified in VSPT(i+1). It
>>      then concatenates the shortest of those paths to the paths in
>>      VSPT(i+1) to construct VSPT(i).
>>=20
>> Then you can delete the following...
>>    Then PCE(i) computes VSPT(i) (MP2P (Multi-Point to Point) tree made
>>    of the shortest constrained paths between each BN-en(j,i) and the TE
>>    LSP destination).
>=20
> Not really since this is a different way to compute the path. We used to
> terminology "concatenates" since for example PCE1 may not compute the
> shortest paths from BN-en(1) to each BN-ex(1). It could indeed concatenat=
e
> VPST(2) with its TED and compute the path in one pass in the case of an A=
BR.
=20
OK.
The problem is with the "concatenate."
=20
How about...
=20
    Step i:
=20
    - For i=3Dn-1 to 2: PCE(i) computes VSPT(i), the tree made
      of the shortest constrained paths between each BN-en(j,i)
      and the TE LSP destination. It does this by considering
      its own TED and the information in VSPT(i+1).

JP> If you do not like =B3concatenate=B2 no big deal, this text works.
=20
>> Section 5
>> Is it assumed that PCE(i) knows which domain the requesting PCE(i-1)
>> represents?
>> The reverse is obviously true because PCE(i-1) must select PCE(i) on thi=
s
>> basis, but it seems to me that the PCReq could useful identify the
>> neighboring (upstream) domain. This would be particularly useful in the =
case
>> of a requesting PCE that represents multiple domains since it will allow
>> PCE(i) to know which are the BN-en(i) nodes.
>> Conversely, if PCE(i) has computation capabilities for multiple domains,=
 it
>> will need to be told which for domain(i) it should act.
>> So we either need protocol extensions (requesting domain, computation
>> domain) or we need to be told how to use existing protocol fields for th=
is
>> purpose.
>>=20
>> Furthermore :-( how although the sequence of domains is known (a priori)=
 by
>> the PCC, we need some way to convey the sequence in the PCReq so that PC=
E(i)
>> knows that the next domain in the sequence is domain(i+1).
>> If this can be achieved by existing protocol mechanism, you need to desc=
ribe
>> the procedures. If it can't be done, we need protocol extensions.
>=20
> We make the assumption that the sequence of domains is predetermined or
> discovered by some means that is outside of the scope of this document.
> You're right that we do not say that the sequence of PCE is also
> predetermined or discovery by some means. Do you want us to explicitly ad=
d
> this assumption?
> Consider the two following cases:
> 1) Inter-area: obvious
> 2) Inter-AS: if the sequences of domain and related PCEs are known, there=
 is
> no need for protocol extensions except if we want to enforce the sequence=
 of
> PCEs, which can be done thanks to the PCE-ID object defined in
> http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-01.txt
<http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-01.txt> . We
> could include the PCE-ID object definition in BRPC and add some text here=
.
> Thoughts?
Well, I have no problems with "the sequence of domains is known a priori."
In fact, I strongly support it.
=20
However, to whom is this sequence known?
=20
Yes, if the ingress PCC or PCE knows the PCEs responsible for each domain,
then it could provide a list of such PCEs. But this is more information tha=
n
is implied in "the sequence of domains". My assumption is that the default
position is that PCE(i) will select PCE(i+1).

JP> This is what we referred to as =B3discovered by some means=B2 indeed.
=20
But how does PCE(i) know that the next domain is domain(i+1)? How is the a
priori knowledge passed to PCE(i)?
=20
JP> By some means out of the scope of the document.
Example: inter-area + PCE on the ABR + PCE discovery (RFC 5088/5089)
There are other mechanisms available but out of the scope of this document.

This isimportant, because knowing the sequence of PCEs is not enough to kno=
w
the sequence of domains. A PCE may serve more than one domain.
=20
>> Section 14.4
>> Ha!
>> And how will you look at these TEDs?
>=20
> It of course depends on how these TEDs are populated but this is in any c=
ase
> the only way to verify correct operation.
=20
In section 8.4 of pcep-11 we took a completely different meaning of "correc=
t
operation" because we recognised that we are interested in the correct
operation of the protocol, not the correct operation of the computation
algorithm.
=20
You should do the same here.

JP> Ah I see what you mean now. Sure that makes sense.

OLD:
Verifying the correct operation of BRPC can be done by looking at the TEDs
related to the various domains traversed by a TE LSP at the time the BRPC
procedure was invoked and verify that the path computed by the BRPC
procedure is the expected optimal inter-domain constrained path (the path
that would be obtained in the absence of multiple domains).

NEW:
Verifying the correct operation of BRPC can be performed by monitoring a se=
t
of parameters. A BRPC implementation SHOULD provide the following
parameters:=20
o Number of successful BRPC Procedure completions on a per PCE peer basis,
o Number of BRPC procedure completion failures because the VSPT flag was no=
t
recognized (on a per PCE peer basis),
o Number of BRPC procedure completetion failures because the BRPC procedure
was not supported (on a per PCE peer basis),
=20
I think the only thing to add to the PCEP spec will be the trail of PCEs as
discussed in the monitoring I-D.

JP> I guess that it will come with the monitoring ID.

Cheers,

JP.


A



--B_3289805219_1583891
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Pce] BRPC last call comments</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'>Hi,<B=
R>
<BR>
Sorry for the one week interruption in the thread ... Back to addressing th=
e last comments, then I&#8217;ll post the new revision.<BR>
<BR>
See in line.<BR>
<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"><B>From: </B>Adrian Farrel &lt;adrian=
@olddog.co.uk&gt;<BR>
<B>Reply-To: </B>Adrian Farrel &lt;adrian@olddog.co.uk&gt;<BR>
<B>Date: </B>Mon, 24 Mar 2008 19:40:47 -0000<BR>
<B>To: </B>JP Vasseur &lt;jvasseur@cisco.com&gt;, &lt;pce@ietf.org&gt;<BR>
<B>Subject: </B>Re: [Pce] BRPC last call comments<BR>
<BR>
</SPAN></FONT><SPAN STYLE=3D'font-size:12.0px'><FONT FACE=3D"Arial">Hi JP,<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">Thanks for the quick progress.<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">Snipped everything where we have reached conclusi=
on...<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">&gt;&gt; Section 4.2<BR>
&gt;&gt; Is &quot;Definition of VSPT(i)&quot; intended to be a subsection?<=
BR>
&gt;&gt; I find that the section leaps to rapidly into the definition of th=
e VSPT.<BR>
&gt;&gt; Shouldn't there be some discussion first (somewhere) about the seq=
uence of<BR>
&gt;&gt; exchange of information between PCC and PCEs? This isn't much info=
rmation,<BR>
&gt;&gt; but seeing the VSPT(i) described as &quot;tree returned by PCE(i) =
to PCE(i-1)&quot;<BR>
&gt;&gt; makes me wonder how the PCEs are joined together.<BR>
&gt; <BR>
&gt; This is explained in the text right after. Do you think that we need t=
o add<BR>
&gt; even more text there?<BR>
Well, I don't think it is crystal clear. Or rather, it *is* crystal clear, =
but the crystal is smokey quartz (<a href=3D"http://gwydir.demon.co.uk/jo/mine=
rals/otherquartz.htm">http://gwydir.demon.co.uk/jo/minerals/otherquartz.htm<=
/a></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <a href=3D"http://gwydir.dem=
on.co.uk/jo/minerals/otherquartz.htm">&lt;http://gwydir.demon.co.uk/jo/miner=
als/otherquartz.htm&gt;</a> </FONT><FONT FACE=3D"Arial">)<BR>
<BR>
JP&gt; ;-)<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">How about a simple paragraph about the basic oper=
ation of BRPC such as...<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">The BRPC procedure relies on communication betwee=
n cooperating PCEs. In particular, the PCC sends a PCReq to a PCE in its dom=
ain. The request is forwarded between PCEs, domain-by-domain until the PCE r=
esponsible for the domain containing the LSP destination is reached. The PCE=
 in the destination domain creates a tree of potential paths to the destinat=
ion (the Virtual Shortest Path Tree - VSPT) and passes this back to the prev=
ious PCE in a PCRep. Each PCE in turn adds to the VSPT and passes it back un=
til the PCE in the source domain uses the VSPT to select an end-to-end path =
that it sends to the PCC.<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
JP&gt; Well does not hurt ;-) I added it, thanks.<BR>
<BR>
</FONT><FONT FACE=3D"Arial">&gt;&gt; Section 4.2<BR>
&gt;&gt; &nbsp;&nbsp;&nbsp;Step i:<BR>
&gt;&gt; <BR>
&gt;&gt; &nbsp;&nbsp;&nbsp;- For i=3Dn-1 to 2: PCE(i) concatenates the topolo=
gy of domain(i)<BR>
&gt;&gt; &nbsp;&nbsp;&nbsp;(using its TED) with the received VSPT(i+1).<BR>
&gt;&gt; <BR>
&gt;&gt; I don't like &quot;concatenates the topology&quot;. Don't you mean=
...<BR>
&gt;&gt; &nbsp;&nbsp;&nbsp;Step i:<BR>
&gt;&gt; <BR>
&gt;&gt; &nbsp;&nbsp;&nbsp;- For i=3Dn-1 to 2: PCE(i) computes the shortest c=
onstrained paths from<BR>
&gt;&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;each BN-en(i) to each BN-ex(i) that =
is identified in VSPT(i+1). It<BR>
&gt;&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;then concatenates the shortest of th=
ose paths to the paths in<BR>
&gt;&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;VSPT(i+1) to construct VSPT(i).<BR>
&gt;&gt; <BR>
&gt;&gt; Then you can delete the following...<BR>
&gt;&gt; &nbsp;&nbsp;&nbsp;Then PCE(i) computes VSPT(i) (MP2P (Multi-Point =
to Point) tree made<BR>
&gt;&gt; &nbsp;&nbsp;&nbsp;of the shortest constrained paths between each B=
N-en(j,i) and the TE<BR>
&gt;&gt; &nbsp;&nbsp;&nbsp;LSP destination).<BR>
&gt; <BR>
&gt; Not really since this is a different way to compute the path. We used =
to<BR>
&gt; terminology &quot;concatenates&quot; since for example PCE1 may not co=
mpute the<BR>
&gt; shortest paths from BN-en(1) to each BN-ex(1). It could indeed concate=
nate<BR>
&gt; VPST(2) with its TED and compute the path in one pass in the case of a=
n ABR.<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">OK.<BR>
The problem is with the &quot;concatenate.&quot;<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">How about...<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Courier New"> &nbsp;&nbsp;&nbsp;Step i:<BR>
&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;- For i=3Dn-1 to 2: PCE(i) computes VSPT(i), the tree=
 made<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;of the shortest constrained paths betwe=
en each BN-en(j,i)<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;and the TE LSP destination. It does thi=
s by considering<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;its own TED and the information in VSPT=
(i+1).<BR>
<BR>
JP&gt; If you do not like &#8220;concatenate&#8221; no big deal, this text =
works.<BR>
</FONT><FONT FACE=3D"Arial"> <BR>
&gt;&gt; Section 5<BR>
&gt;&gt; Is it assumed that PCE(i) knows which domain the requesting PCE(i-=
1)<BR>
&gt;&gt; represents?<BR>
&gt;&gt; The reverse is obviously true because PCE(i-1) must select PCE(i) =
on this<BR>
&gt;&gt; basis, but it seems to me that the PCReq could useful identify the=
<BR>
&gt;&gt; neighboring (upstream) domain. This would be particularly useful i=
n the case<BR>
&gt;&gt; of a requesting PCE that represents multiple domains since it will=
 allow<BR>
&gt;&gt; PCE(i) to know which are the BN-en(i) nodes.<BR>
&gt;&gt; Conversely, if PCE(i) has computation capabilities for multiple do=
mains, it<BR>
&gt;&gt; will need to be told which for domain(i) it should act.<BR>
&gt;&gt; So we either need protocol extensions (requesting domain, computat=
ion<BR>
&gt;&gt; domain) or we need to be told how to use existing protocol fields =
for this<BR>
&gt;&gt; purpose.<BR>
&gt;&gt; <BR>
&gt;&gt; Furthermore :-( how although the sequence of domains is known (a p=
riori) by<BR>
&gt;&gt; the PCC, we need some way to convey the sequence in the PCReq so t=
hat PCE(i)<BR>
&gt;&gt; knows that the next domain in the sequence is domain(i+1).<BR>
&gt;&gt; If this can be achieved by existing protocol mechanism, you need t=
o describe<BR>
&gt;&gt; the procedures. If it can't be done, we need protocol extensions.<=
BR>
&gt; <BR>
&gt; We make the assumption that the sequence of domains is predetermined o=
r<BR>
&gt; discovered by some means that is outside of the scope of this document=
.<BR>
&gt; You're right that we do not say that the sequence of PCE is also<BR>
&gt; predetermined or discovery by some means. Do you want us to explicitly=
 add<BR>
&gt; this assumption?<BR>
&gt; Consider the two following cases:<BR>
&gt; 1) Inter-area: obvious<BR>
&gt; 2) Inter-AS: if the sequences of domain and related PCEs are known, th=
ere is<BR>
&gt; no need for protocol extensions except if we want to enforce the seque=
nce of<BR>
&gt; PCEs, which can be done thanks to the PCE-ID object defined in<BR>
&gt; <a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring=
-01.txt">http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-01.tx=
t</a></FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <a href=3D"http://www.ietf=
.org/internet-drafts/draft-ietf-pce-monitoring-01.txt">&lt;http://www.ietf.o=
rg/internet-drafts/draft-ietf-pce-monitoring-01.txt&gt;</a> </FONT><FONT FAC=
E=3D"Arial">. We<BR>
&gt; could include the PCE-ID object definition in BRPC and add some text h=
ere.<BR>
&gt; Thoughts?<BR>
Well, I have no problems with &quot;the sequence of domains is known a prio=
ri.&quot; In fact, I strongly support it.<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">However, to whom is this sequence known?<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">Yes, if the ingress PCC or PCE knows the PCEs res=
ponsible for each domain, then it could provide a list of such PCEs. But thi=
s is more information than is implied in &quot;the sequence of domains&quot;=
. My assumption is that the default position is that PCE(i) will select PCE(=
i+1).<BR>
<BR>
JP&gt; This is what we referred to as &#8220;discovered by some means&#8221=
; indeed.<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">But how does PCE(i) know that the next domain is =
domain(i+1)? How is the a priori knowledge passed to PCE(i)?<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
JP&gt; By some means out of the scope of the document. <BR>
Example: inter-area + PCE on the ABR + PCE discovery (RFC 5088/5089) <BR>
There are other mechanisms available but out of the scope of this document.=
<BR>
<BR>
</FONT><FONT FACE=3D"Arial">This isimportant, because knowing the sequence of=
 PCEs is not enough to know the sequence of domains. A PCE may serve more th=
an one domain.<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">&gt;&gt; Section 14.4<BR>
&gt;&gt; Ha!<BR>
&gt;&gt; And how will you look at these TEDs?<BR>
&gt; <BR>
&gt; It of course depends on how these TEDs are populated but this is in an=
y case<BR>
&gt; the only way to verify correct operation.<BR>
&nbsp;<BR>
In section 8.4 of pcep-11 we took a completely different meaning of &quot;c=
orrect operation&quot; because we recognised that we are interested in the c=
orrect operation of the protocol, not the correct operation of the computati=
on algorithm.<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">You should do the same here.<BR>
<BR>
JP&gt; Ah I see what you mean now. Sure that makes sense.<BR>
<BR>
OLD:<BR>
Verifying the correct operation of BRPC can be done by looking at the TEDs =
related to the various domains traversed by a TE LSP at the time the BRPC pr=
ocedure was invoked and verify that the path computed by the BRPC procedure =
is the expected optimal inter-domain constrained path (the path that would b=
e obtained in the absence of multiple domains).<BR>
<BR>
NEW:<BR>
Verifying the correct operation of BRPC can be performed by monitoring a se=
t of parameters. A BRPC implementation SHOULD provide the following paramete=
rs: <BR>
o Number of successful BRPC Procedure completions on a per PCE peer basis,<=
BR>
o Number of BRPC procedure completion failures because the VSPT flag was no=
t recognized (on a per PCE peer basis),<BR>
o Number of BRPC procedure completetion failures because the BRPC procedure=
 was not supported (on a per PCE peer basis),<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"> <BR>
</FONT><FONT FACE=3D"Arial">I think the only thing to add to the PCEP spec wi=
ll be the trail of PCEs as discussed in the monitoring I-D.<BR>
<BR>
JP&gt; I guess that it will come with the monitoring ID.<BR>
<BR>
Cheers,<BR>
<BR>
JP.<BR>
<BR>
</FONT><FONT FACE=3D"Verdana, Helvetica, Arial"><BR>
A<BR>
<BR>
</FONT></SPAN>
</BODY>
</HTML>


--B_3289805219_1583891--


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

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

--===============2043892477==--



From pce-bounces@ietf.org  Mon Mar 31 08:49:56 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 38FD428C156;
	Mon, 31 Mar 2008 08:49:56 -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 DB3F428C156
	for <pce@core3.amsl.com>; Mon, 31 Mar 2008 08:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.523
X-Spam-Level: 
X-Spam-Status: No, score=-0.523 tagged_above=-999 required=5
	tests=[AWL=-0.525, BAYES_50=0.001, 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 4bYleJ7Zw92I for <pce@core3.amsl.com>;
	Mon, 31 Mar 2008 08:49:54 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id D98A928C449
	for <pce@ietf.org>; Mon, 31 Mar 2008 08:49:53 -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
	m2VFnjhX032407 for <pce@ietf.org>; Mon, 31 Mar 2008 16:49:50 +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
	m2VFnhBH032380 for <pce@ietf.org>; Mon, 31 Mar 2008 16:49:45 +0100
Message-ID: <01ac01c89346$d1cc2570$0300a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Mon, 31 Mar 2008 16:42:03 +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] Last calls complete (BRPC and inter-AS)
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,

The last calls completed with a few comments, but nothing too exciting.

We'll arrange for new revisions as appropriate and then pass them on to the 
ADs.

Thanks,
Adrian 


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


From pce-bounces@ietf.org  Mon Mar 31 14:10:37 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B736A28C455;
	Mon, 31 Mar 2008 14:10:36 -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 5191228C3D7
	for <pce@core3.amsl.com>; Mon, 31 Mar 2008 14:10:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.786
X-Spam-Level: 
X-Spam-Status: No, score=-1.786 tagged_above=-999 required=5 tests=[AWL=0.812, 
	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 S9IaqqBGsPWd for <pce@core3.amsl.com>;
	Mon, 31 Mar 2008 14:10:25 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 8D80228C43B
	for <pce@ietf.org>; Mon, 31 Mar 2008 14:10:19 -0700 (PDT)
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
	m2VL9dNc009629; Mon, 31 Mar 2008 22:09:44 +0100
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
	m2VL9agL009601; Mon, 31 Mar 2008 22:09:39 +0100
Message-ID: <023201c89373$818ca760$0300a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "JP Vasseur" <jvasseur@cisco.com>, <pce@ietf.org>
References: <C41671A3.3173B%jvasseur@cisco.com>
Date: Mon, 31 Mar 2008 21:56:13 +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] Remaining BRPC last call comment
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi JP,
Thanks for convergence.

There is just one remaining issue for discussion.
I've reproduced the thread here, but all the discussion is at the end.

Cheers,
Adrian

>>>> Section 5
>>>>
>>>> Is it assumed that PCE(i) knows which domain the requesting
>>>> PCE(i-1) represents?
>>>> The reverse is obviously true because PCE(i-1) must select
>>>> PCE(i) on this basis, but it seems to me that the PCReq could
>>>> useful identify the neighboring (upstream) domain. This would
>>>> be particularly useful in the case of a requesting PCE that
>>>> represents multiple domains since it will allow PCE(i) to know
>>>> which are the BN-en(i) nodes.
>>>>
>>>> Conversely, if PCE(i) has computation capabilities for multiple
>>>> domains, it will need to be told which for domain(i) it should act.
>>>> So we either need protocol extensions (requesting domain,
>>>> computation domain) or we need to be told how to use existing
>>>> protocol fields for this purpose.
>>>>
>>>> Furthermore :-( how although the sequence of domains is known
>>>> (a priori) by the PCC, we need some way to convey the sequence
>>>> in the PCReq so that PCE(i) knows that the next domain in the
>>>> sequence is domain(i+1).
>>>> If this can be achieved by existing protocol mechanism, you need
>>>> to describe the procedures. If it can't be done, we need protocol
>>>> extensions.
>>>
>>> We make the assumption that the sequence of domains is pre-
>>> determined or discovered by some means that is outside of the
>>> scope of this document.
>>> You're right that we do not say that the sequence of PCE is also
>>> predetermined or discovery by some means. Do you want us to
>>> explicitly add this assumption?
>>>
>>> Consider the two following cases:
>>> 1) Inter-area: obvious
>>> 2) Inter-AS: if the sequences of domain and related PCEs are known,
>>> there is no need for protocol extensions except if we want to enforce
>>> the sequence of PCEs, which can be done thanks to the PCE-ID
>>> object defined in
>>> http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-01.txt
>>> We could include the PCE-ID object definition in BRPC and add
>>> some text here.
>>> Thoughts?
>>
>> Well, I have no problems with "the sequence of domains is known a
>> priori." In fact, I strongly support it.
>>
>> However, to whom is this sequence known?
>>
>> Yes, if the ingress PCC or PCE knows the PCEs responsible for each
>> domain, then it could provide a list of such PCEs. But this is more
>> information than is implied in "the sequence of domains". My assumption
>> is that the default position is that PCE(i) will select PCE(i+1).
>
> This is what we referred to as =B3discovered by some means=B2 indeed.
>
>> But how does PCE(i) know that the next domain is domain(i+1)? How
>> is the a priori knowledge passed to PCE(i)?
>
> By some means out of the scope of the document.
> Example: inter-area + PCE on the ABR + PCE discovery
> (RFC 5088/5089).
> There are other mechanisms available but out of the scope of this
> document.
>
>> This is important, because knowing the sequence of PCEs is not enough
>> to know the sequence of domains. A PCE may serve more than one
>> domain.

OK
The difference in our view point is, I think, what we mean by "the series o=
f =

domains is known a priori." Let's use ASes as the example, because it is =

slightly more complex.
Here comes some ASCII Art (TM)

<ascii-art>
                --------- =

               | AS-B    |
 ---------     |         |     --------- =

| AS-A    |----|         |----| AS-D    |
|         |    |         |    |         |
|   PCC   |----|         |----|  Egress |
|         |     ---------     |         |
|         |       |   |       |         |
|         |     ---------     |         |
|         |----| AS-C    |----|         |
|         |    |         |    |         |
|         |----|         |----|         |
 ---------     |         |     --------- =

               |         |
                --------- =

</ascii-art>
Here we have 4 ASes and we want to get from the PCC to the Egress.
The ASes are interconnected as shown.
Let's assume that there are five PCEs. PCE-A, PCE-B, PCE-C and PCE-D have =

obvious scope.
PCE-E is special, it is capable of computing paths in AS-B and AS-C.

So, in my book, "the series of domains is known a priori" means that it is =

known before path computation starts. That means, either the PCC knows the =

series of ASes (say, ABD) or the sequence is known by PCE-A.

In the former case, we need a way for the PCC to pass that information to =

PCE-A. Note that this is not a sequence of PCEs. It is a sequence of =

domains.

Let's suppose that PCE-A now knows the series of domains, ABD. Let us assum=
e =

that it selects PCE-B as the next PCE in the series. How does it communicat=
e =

to PCE-B that the series of domains is ABD and not ABCD? One possible way t=
o =

do this, would be to signal the series of PCEs (PCE-A, PCE-B, PCE-D). But =

that has some implication of a one-to-one relationship between PCEs and =

domains.

So suppose PCE-A selects PCE-E as the next PCE in the series. How does PCE-=
E =

know the pre-determined series of domains? How does it know that it has bee=
n =

asked to find a path across AS-B and not AS-C? Do we suppose that this a =

priori knowledge permeates the ether? Or is it passed along with the =

request? Note that the sequence of PCEs PCE-A, PCE-E, PCE-D does not help =

because we could still select a path through domains ABCD.

So, I think that PCEP needs to be able to indicate the sequence of domains =

that should be traversed. The additional ability to indicate the sequence o=
f =

PCEs is a great supplement. =



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


From pce-bounces@ietf.org  Mon Mar 31 14:46:31 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D5CDE28C228;
	Mon, 31 Mar 2008 14:46:31 -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 4964828C211
	for <pce@core3.amsl.com>; Mon, 31 Mar 2008 14:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 xd7IfXwUFqiT for <pce@core3.amsl.com>;
	Mon, 31 Mar 2008 14:46:26 -0700 (PDT)
Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11])
	by core3.amsl.com (Postfix) with ESMTP id 684363A6B3F
	for <pce@ietf.org>; Mon, 31 Mar 2008 14:46:13 -0700 (PDT)
Received: from localhost (imp-4-1.polymtl.ca [132.207.4.76])
	by smtp.polymtl.ca (8.13.8/8.13.8) with ESMTP id m2VLjlVq012885;
	Mon, 31 Mar 2008 17:45:48 -0400
Received: from chaplin.larim.polymtl.ca (chaplin.larim.polymtl.ca
	[132.207.67.80]) by www.imp.polymtl.ca (IMP) with HTTP 
	for <meshi@132.207.4.132>; Mon, 31 Mar 2008 17:45:47 -0400
Message-ID: <1206999947.47f15b8b3331f@www.imp.polymtl.ca>
Date: Mon, 31 Mar 2008 17:45:47 -0400
From: Meral Shirazipour <meral.shirazipour@polymtl.ca>
To: Adrian Farrel <adrian@olddog.co.uk>
References: <C41671A3.3173B%jvasseur@cisco.com>
	<023201c89373$818ca760$0300a8c0@your029b8cecfe>
In-Reply-To: <023201c89373$818ca760$0300a8c0@your029b8cecfe>
MIME-Version: 1.0
User-Agent: Internet Messaging Program (IMP) 3.2.3
X-Originating-IP: 132.207.67.80
X-Poly-FromMTA: (imp-4-1.polymtl.ca [132.207.4.76]) at Mon,
	31 Mar 2008 21:45:48 +0000
Cc: "pce@ietf.org" <pce@ietf.org>
Subject: Re: [Pce] Remaining BRPC last call comment
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi Adrian,
  I do not disagree with you that it would be a plus to be able to =91somet=
imes=92
indicate the sequence of domains we want the path to go through; however I
understood that in most cases, each PCE along the path would decide of the
=93best next domain=94 to traverse next.

  On the other hand, I think it remains crucial to be able to indicate the
domain(s) to exclude in the sequence of domains (for diversity or political
reasons).

Regards,
Meral



Selon Adrian Farrel <adrian@olddog.co.uk>:

> Hi JP,
> Thanks for convergence.
>
> There is just one remaining issue for discussion.
> I've reproduced the thread here, but all the discussion is at the end.
>
> Cheers,
> Adrian
>
> >>>> Section 5
> >>>>
> >>>> Is it assumed that PCE(i) knows which domain the requesting
> >>>> PCE(i-1) represents?
> >>>> The reverse is obviously true because PCE(i-1) must select
> >>>> PCE(i) on this basis, but it seems to me that the PCReq could
> >>>> useful identify the neighboring (upstream) domain. This would
> >>>> be particularly useful in the case of a requesting PCE that
> >>>> represents multiple domains since it will allow PCE(i) to know
> >>>> which are the BN-en(i) nodes.
> >>>>
> >>>> Conversely, if PCE(i) has computation capabilities for multiple
> >>>> domains, it will need to be told which for domain(i) it should act.
> >>>> So we either need protocol extensions (requesting domain,
> >>>> computation domain) or we need to be told how to use existing
> >>>> protocol fields for this purpose.
> >>>>
> >>>> Furthermore :-( how although the sequence of domains is known
> >>>> (a priori) by the PCC, we need some way to convey the sequence
> >>>> in the PCReq so that PCE(i) knows that the next domain in the
> >>>> sequence is domain(i+1).
> >>>> If this can be achieved by existing protocol mechanism, you need
> >>>> to describe the procedures. If it can't be done, we need protocol
> >>>> extensions.
> >>>
> >>> We make the assumption that the sequence of domains is pre-
> >>> determined or discovered by some means that is outside of the
> >>> scope of this document.
> >>> You're right that we do not say that the sequence of PCE is also
> >>> predetermined or discovery by some means. Do you want us to
> >>> explicitly add this assumption?
> >>>
> >>> Consider the two following cases:
> >>> 1) Inter-area: obvious
> >>> 2) Inter-AS: if the sequences of domain and related PCEs are known,
> >>> there is no need for protocol extensions except if we want to enforce
> >>> the sequence of PCEs, which can be done thanks to the PCE-ID
> >>> object defined in
> >>> http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-01.txt
> >>> We could include the PCE-ID object definition in BRPC and add
> >>> some text here.
> >>> Thoughts?
> >>
> >> Well, I have no problems with "the sequence of domains is known a
> >> priori." In fact, I strongly support it.
> >>
> >> However, to whom is this sequence known?
> >>
> >> Yes, if the ingress PCC or PCE knows the PCEs responsible for each
> >> domain, then it could provide a list of such PCEs. But this is more
> >> information than is implied in "the sequence of domains". My assumption
> >> is that the default position is that PCE(i) will select PCE(i+1).
> >
> > This is what we referred to as =B3discovered by some means=B2 indeed.
> >
> >> But how does PCE(i) know that the next domain is domain(i+1)? How
> >> is the a priori knowledge passed to PCE(i)?
> >
> > By some means out of the scope of the document.
> > Example: inter-area + PCE on the ABR + PCE discovery
> > (RFC 5088/5089).
> > There are other mechanisms available but out of the scope of this
> > document.
> >
> >> This is important, because knowing the sequence of PCEs is not enough
> >> to know the sequence of domains. A PCE may serve more than one
> >> domain.
>
> OK
> The difference in our view point is, I think, what we mean by "the series=
 of
> domains is known a priori." Let's use ASes as the example, because it is
> slightly more complex.
> Here comes some ASCII Art (TM)
>
> <ascii-art>
>                 ---------
>                | AS-B    |
>  ---------     |         |     ---------
> | AS-A    |----|         |----| AS-D    |
> |         |    |         |    |         |
> |   PCC   |----|         |----|  Egress |
> |         |     ---------     |         |
> |         |       |   |       |         |
> |         |     ---------     |         |
> |         |----| AS-C    |----|         |
> |         |    |         |    |         |
> |         |----|         |----|         |
>  ---------     |         |     ---------
>                |         |
>                 ---------
> </ascii-art>
> Here we have 4 ASes and we want to get from the PCC to the Egress.
> The ASes are interconnected as shown.
> Let's assume that there are five PCEs. PCE-A, PCE-B, PCE-C and PCE-D have
> obvious scope.
> PCE-E is special, it is capable of computing paths in AS-B and AS-C.
>
> So, in my book, "the series of domains is known a priori" means that it is
> known before path computation starts. That means, either the PCC knows the
> series of ASes (say, ABD) or the sequence is known by PCE-A.
>
> In the former case, we need a way for the PCC to pass that information to
> PCE-A. Note that this is not a sequence of PCEs. It is a sequence of
> domains.
>
> Let's suppose that PCE-A now knows the series of domains, ABD. Let us ass=
ume
> that it selects PCE-B as the next PCE in the series. How does it communic=
ate
> to PCE-B that the series of domains is ABD and not ABCD? One possible way=
 to
> do this, would be to signal the series of PCEs (PCE-A, PCE-B, PCE-D). But
> that has some implication of a one-to-one relationship between PCEs and
> domains.
>
> So suppose PCE-A selects PCE-E as the next PCE in the series. How does PC=
E-E
> know the pre-determined series of domains? How does it know that it has b=
een
> asked to find a path across AS-B and not AS-C? Do we suppose that this a
> priori knowledge permeates the ether? Or is it passed along with the
> request? Note that the sequence of PCEs PCE-A, PCE-E, PCE-D does not help
> because we could still select a path through domains ABCD.
>
> So, I think that PCEP needs to be able to indicate the sequence of domains
> that should be traversed. The additional ability to indicate the sequence=
 of
> PCEs is a great supplement.
>
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>
>



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


From pce-bounces@ietf.org  Mon Mar 31 15:35:21 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E97E93A685C;
	Mon, 31 Mar 2008 15:35:21 -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 5E3DC3A685C
	for <pce@core3.amsl.com>; Mon, 31 Mar 2008 15:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 iHK2H6x1w9T3 for <pce@core3.amsl.com>;
	Mon, 31 Mar 2008 15:35:19 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154])
	by core3.amsl.com (Postfix) with ESMTP id 158D63A6817
	for <pce@ietf.org>; Mon, 31 Mar 2008 15:35:16 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id 16so1718378fgg.41
	for <pce@ietf.org>; Mon, 31 Mar 2008 15:35:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=s7j3xAGkF3TS+bH/XF+zDXO5IJnOJUSFEJgFdTam5ds=;
	b=Ve6VrJjphPKkXYJKB70IXybsBVqTPhhf9wdjFY2pQn+6mVNHj0ZWn+OpGkk6TeixL7lcznCmX9LVqMDsD0ZwrDgWHaCPgCPaAGOr9/Ta9K0Jgw4A/R8JWShDC4HdvfxgFNNLEaZUrGiSLpvGksd55kD68DSkFJVWPJF63kki5TI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=cI9xHDefDusi87uoGE3MusTtU76EAVDzo51gfctjS6yomsHhlAVjiE2eD5fqyqCotb9zmn8M0cr3Rd8kLCk4yBCIu5DUdBIJL7shqwJJGXAmPgCPjYRRzpfcY2cJ9dNL9SjljUfdFwWEFt6FgoHm1Ae2amdHkvixZpe/EQEYBHk=
Received: by 10.86.79.19 with SMTP id c19mr4855524fgb.16.1207002910421;
	Mon, 31 Mar 2008 15:35:10 -0700 (PDT)
Received: by 10.86.87.20 with HTTP; Mon, 31 Mar 2008 15:35:10 -0700 (PDT)
Message-ID: <406e32c00803311535y718ce934yf0eaa94496a945f4@mail.gmail.com>
Date: Mon, 31 Mar 2008 18:35:10 -0400
From: "Peng He" <peng.he.2000@gmail.com>
To: "Meral Shirazipour" <meral.shirazipour@polymtl.ca>
In-Reply-To: <1206999947.47f15b8b3331f@www.imp.polymtl.ca>
MIME-Version: 1.0
Content-Disposition: inline
References: <C41671A3.3173B%jvasseur@cisco.com>
	<023201c89373$818ca760$0300a8c0@your029b8cecfe>
	<1206999947.47f15b8b3331f@www.imp.polymtl.ca>
Cc: "pce@ietf.org" <pce@ietf.org>
Subject: Re: [Pce] Remaining BRPC last call comment
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

I agree with Adrian, the domain-sequence should be indicated
explicitly and kept consistency when passing through.

But I don't understand "each PCE along the path would decide of the
"best next domain" to traverse next" , I suppose the domain-sequence
is kind of 'global optimality' by all means; then how does a PCE
decide  the 'best next domain', how do you define the term 'best', and
it might be 'local optimality' in most times as Adrian's example
indicates.

>   On the other hand, I think it remains crucial to be able to indicate the
>  domain(s) to exclude in the sequence of domains (for diversity or politi=
cal
>  reasons).

If  the domain-sequence is decided by all means, then it might already
exclude the unwanted domain(s) I guess.


Regards,
Peng

On Mon, Mar 31, 2008 at 5:45 PM, Meral Shirazipour
<meral.shirazipour@polymtl.ca> wrote:
> Hi Adrian,
>   I do not disagree with you that it would be a plus to be able to 'somet=
imes'
>  indicate the sequence of domains we want the path to go through; however=
 I
>  understood that in most cases, each PCE along the path would decide of t=
he
>  "best next domain" to traverse next.
>
>   On the other hand, I think it remains crucial to be able to indicate the
>  domain(s) to exclude in the sequence of domains (for diversity or politi=
cal
>  reasons).
>
>  Regards,
>  Meral
>
>
>
>  Selon Adrian Farrel <adrian@olddog.co.uk>:
>
>
>
>  > Hi JP,
>  > Thanks for convergence.
>  >
>  > There is just one remaining issue for discussion.
>  > I've reproduced the thread here, but all the discussion is at the end.
>  >
>  > Cheers,
>  > Adrian
>  >
>  > >>>> Section 5
>  > >>>>
>  > >>>> Is it assumed that PCE(i) knows which domain the requesting
>  > >>>> PCE(i-1) represents?
>  > >>>> The reverse is obviously true because PCE(i-1) must select
>  > >>>> PCE(i) on this basis, but it seems to me that the PCReq could
>  > >>>> useful identify the neighboring (upstream) domain. This would
>  > >>>> be particularly useful in the case of a requesting PCE that
>  > >>>> represents multiple domains since it will allow PCE(i) to know
>  > >>>> which are the BN-en(i) nodes.
>  > >>>>
>  > >>>> Conversely, if PCE(i) has computation capabilities for multiple
>  > >>>> domains, it will need to be told which for domain(i) it should ac=
t.
>  > >>>> So we either need protocol extensions (requesting domain,
>  > >>>> computation domain) or we need to be told how to use existing
>  > >>>> protocol fields for this purpose.
>  > >>>>
>  > >>>> Furthermore :-( how although the sequence of domains is known
>  > >>>> (a priori) by the PCC, we need some way to convey the sequence
>  > >>>> in the PCReq so that PCE(i) knows that the next domain in the
>  > >>>> sequence is domain(i+1).
>  > >>>> If this can be achieved by existing protocol mechanism, you need
>  > >>>> to describe the procedures. If it can't be done, we need protocol
>  > >>>> extensions.
>  > >>>
>  > >>> We make the assumption that the sequence of domains is pre-
>  > >>> determined or discovered by some means that is outside of the
>  > >>> scope of this document.
>  > >>> You're right that we do not say that the sequence of PCE is also
>  > >>> predetermined or discovery by some means. Do you want us to
>  > >>> explicitly add this assumption?
>  > >>>
>  > >>> Consider the two following cases:
>  > >>> 1) Inter-area: obvious
>  > >>> 2) Inter-AS: if the sequences of domain and related PCEs are known,
>  > >>> there is no need for protocol extensions except if we want to enfo=
rce
>  > >>> the sequence of PCEs, which can be done thanks to the PCE-ID
>  > >>> object defined in
>  > >>> http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-01.t=
xt
>  > >>> We could include the PCE-ID object definition in BRPC and add
>  > >>> some text here.
>  > >>> Thoughts?
>  > >>
>  > >> Well, I have no problems with "the sequence of domains is known a
>  > >> priori." In fact, I strongly support it.
>  > >>
>  > >> However, to whom is this sequence known?
>  > >>
>  > >> Yes, if the ingress PCC or PCE knows the PCEs responsible for each
>  > >> domain, then it could provide a list of such PCEs. But this is more
>  > >> information than is implied in "the sequence of domains". My assump=
tion
>  > >> is that the default position is that PCE(i) will select PCE(i+1).
>  > >
>  > > This is what we referred to as =B3discovered by some means=B2 indeed.
>  > >
>  > >> But how does PCE(i) know that the next domain is domain(i+1)? How
>  > >> is the a priori knowledge passed to PCE(i)?
>  > >
>  > > By some means out of the scope of the document.
>  > > Example: inter-area + PCE on the ABR + PCE discovery
>  > > (RFC 5088/5089).
>  > > There are other mechanisms available but out of the scope of this
>  > > document.
>  > >
>  > >> This is important, because knowing the sequence of PCEs is not enou=
gh
>  > >> to know the sequence of domains. A PCE may serve more than one
>  > >> domain.
>  >
>  > OK
>  > The difference in our view point is, I think, what we mean by "the ser=
ies of
>  > domains is known a priori." Let's use ASes as the example, because it =
is
>  > slightly more complex.
>  > Here comes some ASCII Art (TM)
>  >
>  > <ascii-art>
>  >                 ---------
>  >                | AS-B    |
>  >  ---------     |         |     ---------
>  > | AS-A    |----|         |----| AS-D    |
>  > |         |    |         |    |         |
>  > |   PCC   |----|         |----|  Egress |
>  > |         |     ---------     |         |
>  > |         |       |   |       |         |
>  > |         |     ---------     |         |
>  > |         |----| AS-C    |----|         |
>  > |         |    |         |    |         |
>  > |         |----|         |----|         |
>  >  ---------     |         |     ---------
>  >                |         |
>  >                 ---------
>  > </ascii-art>
>  > Here we have 4 ASes and we want to get from the PCC to the Egress.
>  > The ASes are interconnected as shown.
>  > Let's assume that there are five PCEs. PCE-A, PCE-B, PCE-C and PCE-D h=
ave
>  > obvious scope.
>  > PCE-E is special, it is capable of computing paths in AS-B and AS-C.
>  >
>  > So, in my book, "the series of domains is known a priori" means that i=
t is
>  > known before path computation starts. That means, either the PCC knows=
 the
>  > series of ASes (say, ABD) or the sequence is known by PCE-A.
>  >
>  > In the former case, we need a way for the PCC to pass that information=
 to
>  > PCE-A. Note that this is not a sequence of PCEs. It is a sequence of
>  > domains.
>  >
>  > Let's suppose that PCE-A now knows the series of domains, ABD. Let us =
assume
>  > that it selects PCE-B as the next PCE in the series. How does it commu=
nicate
>  > to PCE-B that the series of domains is ABD and not ABCD? One possible =
way to
>  > do this, would be to signal the series of PCEs (PCE-A, PCE-B, PCE-D). =
But
>  > that has some implication of a one-to-one relationship between PCEs and
>  > domains.
>  >
>  > So suppose PCE-A selects PCE-E as the next PCE in the series. How does=
 PCE-E
>  > know the pre-determined series of domains? How does it know that it ha=
s been
>  > asked to find a path across AS-B and not AS-C? Do we suppose that this=
 a
>  > priori knowledge permeates the ether? Or is it passed along with the
>  > request? Note that the sequence of PCEs PCE-A, PCE-E, PCE-D does not h=
elp
>  > because we could still select a path through domains ABCD.
>  >
>  > So, I think that PCEP needs to be able to indicate the sequence of dom=
ains
>  > that should be traversed. The additional ability to indicate the seque=
nce of
>  > PCEs is a great supplement.
>  >
>  >
>  > _______________________________________________
>  > Pce mailing list
>  > Pce@ietf.org
>  > https://www.ietf.org/mailman/listinfo/pce
>  >
>  >
>
>
>
>  _______________________________________________
>  Pce mailing list
>  Pce@ietf.org
>  https://www.ietf.org/mailman/listinfo/pce
>
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


From pce-bounces@ietf.org  Mon Mar 31 20:56:57 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B34943A6A70;
	Mon, 31 Mar 2008 20:56:57 -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 A5B7A3A6A70
	for <pce@core3.amsl.com>; Mon, 31 Mar 2008 20:56:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 QttaV46OV8Ui for <pce@core3.amsl.com>;
	Mon, 31 Mar 2008 20:56:55 -0700 (PDT)
Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11])
	by core3.amsl.com (Postfix) with ESMTP id 2DCCF3A68AF
	for <pce@ietf.org>; Mon, 31 Mar 2008 20:56:55 -0700 (PDT)
Received: from localhost (imp-4-2.polymtl.ca [132.207.4.77])
	by smtp.polymtl.ca (8.13.8/8.13.8) with ESMTP id m313uoEZ000905;
	Mon, 31 Mar 2008 23:56:51 -0400
Received: from bas1-sthubert21-1279581895.dsl.bell.ca
	(bas1-sthubert21-1279581895.dsl.bell.ca [76.68.222.199]) 
	by www.imp.polymtl.ca (IMP) with HTTP 
	for <meshi@132.207.4.132>; Mon, 31 Mar 2008 23:56:50 -0400
Message-ID: <1207022210.47f1b28255332@www.imp.polymtl.ca>
Date: Mon, 31 Mar 2008 23:56:50 -0400
From: Meral Shirazipour <meral.shirazipour@polymtl.ca>
To: Peng He <peng.he.2000@gmail.com>
References: <C41671A3.3173B%jvasseur@cisco.com>
	<023201c89373$818ca760$0300a8c0@your029b8cecfe>
	<1206999947.47f15b8b3331f@www.imp.polymtl.ca>
	<406e32c00803311535y718ce934yf0eaa94496a945f4@mail.gmail.com>
In-Reply-To: <406e32c00803311535y718ce934yf0eaa94496a945f4@mail.gmail.com>
MIME-Version: 1.0
User-Agent: Internet Messaging Program (IMP) 3.2.3
X-Originating-IP: 76.68.222.199
X-Poly-FromMTA: (imp-4-2.polymtl.ca [132.207.4.77]) at Tue,
	1 Apr 2008 03:56:51 +0000
Cc: "pce@ietf.org" <pce@ietf.org>
Subject: Re: [Pce] Remaining BRPC last call comment
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi,
   Please see inline...

> I agree with Adrian, the domain-sequence should be indicated
> explicitly and kept consistency when passing through.

Again, I believe this is a plus but not a must.
Some PCCs might not even have the capability to come up with such a domain
sequence information.

> But I don't understand "each PCE along the path would decide of the
> "best next domain" to traverse next" , I suppose the domain-sequence
> is kind of 'global optimality' by all means; then how does a PCE
> decide  the 'best next domain', how do you define the term 'best', and
> it might be 'local optimality' in most times as Adrian's example
> indicates.
Of course the term "best" would be of local significance, if the PCE making=
 the
decision does not have a global end to end view.

> >   On the other hand, I think it remains crucial to be able to indicate =
the
> >  domain(s) to exclude in the sequence of domains (for diversity or
> political
> >  reasons).
>
> If  the domain-sequence is decided by all means, then it might already
> exclude the unwanted domain(s) I guess.

Again  I don't agree here. Not all PCCs will be able to come up with the do=
main
sequence information. However, and mostly for diversity reasons, they will =
know
the domains/PCEs they want to avoid.

> Regards,
> Peng
>

Regards,
Meral


> On Mon, Mar 31, 2008 at 5:45 PM, Meral Shirazipour
> <meral.shirazipour@polymtl.ca> wrote:
> > Hi Adrian,
> >   I do not disagree with you that it would be a plus to be able to
> 'sometimes'
> >  indicate the sequence of domains we want the path to go through; howev=
er I
> >  understood that in most cases, each PCE along the path would decide of=
 the
> >  "best next domain" to traverse next.
> >
> >   On the other hand, I think it remains crucial to be able to indicate =
the
> >  domain(s) to exclude in the sequence of domains (for diversity or
> political
> >  reasons).
> >
> >  Regards,
> >  Meral
> >
> >
> >
> >  Selon Adrian Farrel <adrian@olddog.co.uk>:
> >
> >
> >
> >  > Hi JP,
> >  > Thanks for convergence.
> >  >
> >  > There is just one remaining issue for discussion.
> >  > I've reproduced the thread here, but all the discussion is at the en=
d.
> >  >
> >  > Cheers,
> >  > Adrian
> >  >
> >  > >>>> Section 5
> >  > >>>>
> >  > >>>> Is it assumed that PCE(i) knows which domain the requesting
> >  > >>>> PCE(i-1) represents?
> >  > >>>> The reverse is obviously true because PCE(i-1) must select
> >  > >>>> PCE(i) on this basis, but it seems to me that the PCReq could
> >  > >>>> useful identify the neighboring (upstream) domain. This would
> >  > >>>> be particularly useful in the case of a requesting PCE that
> >  > >>>> represents multiple domains since it will allow PCE(i) to know
> >  > >>>> which are the BN-en(i) nodes.
> >  > >>>>
> >  > >>>> Conversely, if PCE(i) has computation capabilities for multiple
> >  > >>>> domains, it will need to be told which for domain(i) it should =
act.
> >  > >>>> So we either need protocol extensions (requesting domain,
> >  > >>>> computation domain) or we need to be told how to use existing
> >  > >>>> protocol fields for this purpose.
> >  > >>>>
> >  > >>>> Furthermore :-( how although the sequence of domains is known
> >  > >>>> (a priori) by the PCC, we need some way to convey the sequence
> >  > >>>> in the PCReq so that PCE(i) knows that the next domain in the
> >  > >>>> sequence is domain(i+1).
> >  > >>>> If this can be achieved by existing protocol mechanism, you need
> >  > >>>> to describe the procedures. If it can't be done, we need protoc=
ol
> >  > >>>> extensions.
> >  > >>>
> >  > >>> We make the assumption that the sequence of domains is pre-
> >  > >>> determined or discovered by some means that is outside of the
> >  > >>> scope of this document.
> >  > >>> You're right that we do not say that the sequence of PCE is also
> >  > >>> predetermined or discovery by some means. Do you want us to
> >  > >>> explicitly add this assumption?
> >  > >>>
> >  > >>> Consider the two following cases:
> >  > >>> 1) Inter-area: obvious
> >  > >>> 2) Inter-AS: if the sequences of domain and related PCEs are kno=
wn,
> >  > >>> there is no need for protocol extensions except if we want to
> enforce
> >  > >>> the sequence of PCEs, which can be done thanks to the PCE-ID
> >  > >>> object defined in
> >  > >>> http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-01=
.txt
> >  > >>> We could include the PCE-ID object definition in BRPC and add
> >  > >>> some text here.
> >  > >>> Thoughts?
> >  > >>
> >  > >> Well, I have no problems with "the sequence of domains is known a
> >  > >> priori." In fact, I strongly support it.
> >  > >>
> >  > >> However, to whom is this sequence known?
> >  > >>
> >  > >> Yes, if the ingress PCC or PCE knows the PCEs responsible for each
> >  > >> domain, then it could provide a list of such PCEs. But this is mo=
re
> >  > >> information than is implied in "the sequence of domains". My
> assumption
> >  > >> is that the default position is that PCE(i) will select PCE(i+1).
> >  > >
> >  > > This is what we referred to as =B3discovered by some means=B2 inde=
ed.
> >  > >
> >  > >> But how does PCE(i) know that the next domain is domain(i+1)? How
> >  > >> is the a priori knowledge passed to PCE(i)?
> >  > >
> >  > > By some means out of the scope of the document.
> >  > > Example: inter-area + PCE on the ABR + PCE discovery
> >  > > (RFC 5088/5089).
> >  > > There are other mechanisms available but out of the scope of this
> >  > > document.
> >  > >
> >  > >> This is important, because knowing the sequence of PCEs is not en=
ough
> >  > >> to know the sequence of domains. A PCE may serve more than one
> >  > >> domain.
> >  >
> >  > OK
> >  > The difference in our view point is, I think, what we mean by "the
> series of
> >  > domains is known a priori." Let's use ASes as the example, because i=
t is
> >  > slightly more complex.
> >  > Here comes some ASCII Art (TM)
> >  >
> >  > <ascii-art>
> >  >                 ---------
> >  >                | AS-B    |
> >  >  ---------     |         |     ---------
> >  > | AS-A    |----|         |----| AS-D    |
> >  > |         |    |         |    |         |
> >  > |   PCC   |----|         |----|  Egress |
> >  > |         |     ---------     |         |
> >  > |         |       |   |       |         |
> >  > |         |     ---------     |         |
> >  > |         |----| AS-C    |----|         |
> >  > |         |    |         |    |         |
> >  > |         |----|         |----|         |
> >  >  ---------     |         |     ---------
> >  >                |         |
> >  >                 ---------
> >  > </ascii-art>
> >  > Here we have 4 ASes and we want to get from the PCC to the Egress.
> >  > The ASes are interconnected as shown.
> >  > Let's assume that there are five PCEs. PCE-A, PCE-B, PCE-C and PCE-D
> have
> >  > obvious scope.
> >  > PCE-E is special, it is capable of computing paths in AS-B and AS-C.
> >  >
> >  > So, in my book, "the series of domains is known a priori" means that=
 it
> is
> >  > known before path computation starts. That means, either the PCC kno=
ws
> the
> >  > series of ASes (say, ABD) or the sequence is known by PCE-A.
> >  >
> >  > In the former case, we need a way for the PCC to pass that informati=
on
> to
> >  > PCE-A. Note that this is not a sequence of PCEs. It is a sequence of
> >  > domains.
> >  >
> >  > Let's suppose that PCE-A now knows the series of domains, ABD. Let us
> assume
> >  > that it selects PCE-B as the next PCE in the series. How does it
> communicate
> >  > to PCE-B that the series of domains is ABD and not ABCD? One possible
> way to
> >  > do this, would be to signal the series of PCEs (PCE-A, PCE-B, PCE-D).
> But
> >  > that has some implication of a one-to-one relationship between PCEs =
and
> >  > domains.
> >  >
> >  > So suppose PCE-A selects PCE-E as the next PCE in the series. How do=
es
> PCE-E
> >  > know the pre-determined series of domains? How does it know that it =
has
> been
> >  > asked to find a path across AS-B and not AS-C? Do we suppose that th=
is a
> >  > priori knowledge permeates the ether? Or is it passed along with the
> >  > request? Note that the sequence of PCEs PCE-A, PCE-E, PCE-D does not
> help
> >  > because we could still select a path through domains ABCD.
> >  >
> >  > So, I think that PCEP needs to be able to indicate the sequence of
> domains
> >  > that should be traversed. The additional ability to indicate the
> sequence of
> >  > PCEs is a great supplement.
> >  >
> >  >
> >  > _______________________________________________
> >  > Pce mailing list
> >  > Pce@ietf.org
> >  > https://www.ietf.org/mailman/listinfo/pce
> >  >
> >  >
> >
> >
> >
> >  _______________________________________________
> >  Pce mailing list
> >  Pce@ietf.org
> >  https://www.ietf.org/mailman/listinfo/pce
> >
>
>



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


From pce-bounces@ietf.org  Tue Apr  1 06:18:51 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9D99A3A6CB6;
	Tue,  1 Apr 2008 06:18:51 -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 99A073A6C94
	for <pce@core3.amsl.com>; Tue,  1 Apr 2008 06:18:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 DB8JupSrw9gH for <pce@core3.amsl.com>;
	Tue,  1 Apr 2008 06:18:46 -0700 (PDT)
Received: from hu-out-0506.google.com (hu-out-0506.google.com [72.14.214.230])
	by core3.amsl.com (Postfix) with ESMTP id 88BE23A6CB6
	for <pce@ietf.org>; Tue,  1 Apr 2008 06:15:51 -0700 (PDT)
Received: by hu-out-0506.google.com with SMTP id 31so239784huc.14
	for <pce@ietf.org>; Tue, 01 Apr 2008 06:15:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=Z/6ELPpI9gB7jrvmrMbEiOKxf6pmQVcVayz9o91Aq04=;
	b=Fi1gUMPaYwYKBm6+xtekshNMJOwnNSCavLGG7AYKjHc11WorDtotSk8eFj2+NPxbH/uYh1cge/r4Gca5OczaukuU0JDs8fC8+hNfFd7T6EidUne3W7R9INN5+StKgo295uGid9Alsxwe4tfuuNOu6XXhghnUtbVIzDkT7ikxsOM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=XsqMXDUqmCNOf6TkJInC1oU93fNyGTjG2ZA8bnqxxhKyMQpJ54ZBr/17Mc9/KxAPFB+2U0OwQI5SpkBK3zB7apGUTAms2EBPKxTole2DU6yiPOmuFQpq3OKC1tgY3wsy4zQdcFfa22jGLsXZig0l8LcsP6PdbNM4QUqOcla6He8=
Received: by 10.82.135.7 with SMTP id i7mr19092873bud.29.1207055748448;
	Tue, 01 Apr 2008 06:15:48 -0700 (PDT)
Received: by 10.86.87.20 with HTTP; Tue, 1 Apr 2008 06:15:48 -0700 (PDT)
Message-ID: <406e32c00804010615i27d33ea2nec0e98446841d912@mail.gmail.com>
Date: Tue, 1 Apr 2008 09:15:48 -0400
From: "Peng He" <peng.he.2000@gmail.com>
To: "Meral Shirazipour" <meral.shirazipour@polymtl.ca>
In-Reply-To: <1207022210.47f1b28255332@www.imp.polymtl.ca>
MIME-Version: 1.0
Content-Disposition: inline
References: <C41671A3.3173B%jvasseur@cisco.com>
	<023201c89373$818ca760$0300a8c0@your029b8cecfe>
	<1206999947.47f15b8b3331f@www.imp.polymtl.ca>
	<406e32c00803311535y718ce934yf0eaa94496a945f4@mail.gmail.com>
	<1207022210.47f1b28255332@www.imp.polymtl.ca>
Cc: "pce@ietf.org" <pce@ietf.org>
Subject: Re: [Pce] Remaining BRPC last call comment
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Please see inline...

On Mon, Mar 31, 2008 at 11:56 PM, Meral Shirazipour
<meral.shirazipour@polymtl.ca> wrote:
> Hi,
>    Please see inline...
>
>
>  > I agree with Adrian, the domain-sequence should be indicated
>  > explicitly and kept consistency when passing through.
>
>  Again, I believe this is a plus but not a must.
>  Some PCCs might not even have the capability to come up with such a doma=
in
>  sequence information.
>
>

Well, it is not a must that PCCs know the domain sequence, but I think
it is a must that somebody (e.g, either PCCs or PCEs) know it clearly
and follow it during the process of path computation. I strongly
support '"the series of domains is known a priori" means that it is
known before path computation starts.', which is actually one of the
very basic assumption of PCE architecture. Based on this assumption,
PCE architecture is able to compute optimal inter-domain (area or AS)
path. It should not be the task for PCEs to decide which (next) domain
to go freely although sometime it might see the next domain is the
best from its viewpoint.

Since given a domain sequence, there might be several PCE sequences
matched (different combinations), it is a one-to-many matching, I
agree with Adrian that  "PCEP needs to be able to indicate the
sequence of domains that should be traversed".


>  > But I don't understand "each PCE along the path would decide of the
>  > "best next domain" to traverse next" , I suppose the domain-sequence
>  > is kind of 'global optimality' by all means; then how does a PCE
>  > decide  the 'best next domain', how do you define the term 'best', and
>  > it might be 'local optimality' in most times as Adrian's example
>  > indicates.
>  Of course the term "best" would be of local significance, if the PCE mak=
ing the
>  decision does not have a global end to end view.
>
>
>  > >   On the other hand, I think it remains crucial to be able to indica=
te the
>  > >  domain(s) to exclude in the sequence of domains (for diversity or
>  > political
>  > >  reasons).
>  >
>  > If  the domain-sequence is decided by all means, then it might already
>  > exclude the unwanted domain(s) I guess.
>
>  Again  I don't agree here. Not all PCCs will be able to come up with the=
 domain
>  sequence information. However, and mostly for diversity reasons, they wi=
ll know
>  the domains/PCEs they want to avoid.

Similar example could be: they might want to include (not exclude)
some domains for some reasons. I believe such domain-level decision
should be decided by 'something' that is outside of PCE architecture.
This 'something' provides the domain sequence (might not be optimal),
then PCEs can compute optimal path following this domain sequence.
PCEs should not have the right/capability to decide which domain(s) to
go currently. And it is not a must for PCCs to know this also.

Regards,
Peng

>
>  > Regards,
>  > Peng
>  >
>
>  Regards,
>  Meral
>
>
>
>
>  > On Mon, Mar 31, 2008 at 5:45 PM, Meral Shirazipour
>  > <meral.shirazipour@polymtl.ca> wrote:
>  > > Hi Adrian,
>  > >   I do not disagree with you that it would be a plus to be able to
>  > 'sometimes'
>  > >  indicate the sequence of domains we want the path to go through; ho=
wever I
>  > >  understood that in most cases, each PCE along the path would decide=
 of the
>  > >  "best next domain" to traverse next.
>  > >
>  > >   On the other hand, I think it remains crucial to be able to indica=
te the
>  > >  domain(s) to exclude in the sequence of domains (for diversity or
>  > political
>  > >  reasons).
>  > >
>  > >  Regards,
>  > >  Meral
>  > >
>  > >
>  > >
>  > >  Selon Adrian Farrel <adrian@olddog.co.uk>:
>  > >
>  > >
>  > >
>  > >  > Hi JP,
>  > >  > Thanks for convergence.
>  > >  >
>  > >  > There is just one remaining issue for discussion.
>  > >  > I've reproduced the thread here, but all the discussion is at the=
 end.
>  > >  >
>  > >  > Cheers,
>  > >  > Adrian
>  > >  >
>  > >  > >>>> Section 5
>  > >  > >>>>
>  > >  > >>>> Is it assumed that PCE(i) knows which domain the requesting
>  > >  > >>>> PCE(i-1) represents?
>  > >  > >>>> The reverse is obviously true because PCE(i-1) must select
>  > >  > >>>> PCE(i) on this basis, but it seems to me that the PCReq could
>  > >  > >>>> useful identify the neighboring (upstream) domain. This would
>  > >  > >>>> be particularly useful in the case of a requesting PCE that
>  > >  > >>>> represents multiple domains since it will allow PCE(i) to kn=
ow
>  > >  > >>>> which are the BN-en(i) nodes.
>  > >  > >>>>
>  > >  > >>>> Conversely, if PCE(i) has computation capabilities for multi=
ple
>  > >  > >>>> domains, it will need to be told which for domain(i) it shou=
ld act.
>  > >  > >>>> So we either need protocol extensions (requesting domain,
>  > >  > >>>> computation domain) or we need to be told how to use existing
>  > >  > >>>> protocol fields for this purpose.
>  > >  > >>>>
>  > >  > >>>> Furthermore :-( how although the sequence of domains is known
>  > >  > >>>> (a priori) by the PCC, we need some way to convey the sequen=
ce
>  > >  > >>>> in the PCReq so that PCE(i) knows that the next domain in the
>  > >  > >>>> sequence is domain(i+1).
>  > >  > >>>> If this can be achieved by existing protocol mechanism, you =
need
>  > >  > >>>> to describe the procedures. If it can't be done, we need pro=
tocol
>  > >  > >>>> extensions.
>  > >  > >>>
>  > >  > >>> We make the assumption that the sequence of domains is pre-
>  > >  > >>> determined or discovered by some means that is outside of the
>  > >  > >>> scope of this document.
>  > >  > >>> You're right that we do not say that the sequence of PCE is a=
lso
>  > >  > >>> predetermined or discovery by some means. Do you want us to
>  > >  > >>> explicitly add this assumption?
>  > >  > >>>
>  > >  > >>> Consider the two following cases:
>  > >  > >>> 1) Inter-area: obvious
>  > >  > >>> 2) Inter-AS: if the sequences of domain and related PCEs are =
known,
>  > >  > >>> there is no need for protocol extensions except if we want to
>  > enforce
>  > >  > >>> the sequence of PCEs, which can be done thanks to the PCE-ID
>  > >  > >>> object defined in
>  > >  > >>> http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring=
-01.txt
>  > >  > >>> We could include the PCE-ID object definition in BRPC and add
>  > >  > >>> some text here.
>  > >  > >>> Thoughts?
>  > >  > >>
>  > >  > >> Well, I have no problems with "the sequence of domains is know=
n a
>  > >  > >> priori." In fact, I strongly support it.
>  > >  > >>
>  > >  > >> However, to whom is this sequence known?
>  > >  > >>
>  > >  > >> Yes, if the ingress PCC or PCE knows the PCEs responsible for =
each
>  > >  > >> domain, then it could provide a list of such PCEs. But this is=
 more
>  > >  > >> information than is implied in "the sequence of domains". My
>  > assumption
>  > >  > >> is that the default position is that PCE(i) will select PCE(i+=
1).
>  > >  > >
>  > >  > > This is what we referred to as =B3discovered by some means=B2 i=
ndeed.
>  > >  > >
>  > >  > >> But how does PCE(i) know that the next domain is domain(i+1)? =
How
>  > >  > >> is the a priori knowledge passed to PCE(i)?
>  > >  > >
>  > >  > > By some means out of the scope of the document.
>  > >  > > Example: inter-area + PCE on the ABR + PCE discovery
>  > >  > > (RFC 5088/5089).
>  > >  > > There are other mechanisms available but out of the scope of th=
is
>  > >  > > document.
>  > >  > >
>  > >  > >> This is important, because knowing the sequence of PCEs is not=
 enough
>  > >  > >> to know the sequence of domains. A PCE may serve more than one
>  > >  > >> domain.
>  > >  >
>  > >  > OK
>  > >  > The difference in our view point is, I think, what we mean by "the
>  > series of
>  > >  > domains is known a priori." Let's use ASes as the example, becaus=
e it is
>  > >  > slightly more complex.
>  > >  > Here comes some ASCII Art (TM)
>  > >  >
>  > >  > <ascii-art>
>  > >  >                 ---------
>  > >  >                | AS-B    |
>  > >  >  ---------     |         |     ---------
>  > >  > | AS-A    |----|         |----| AS-D    |
>  > >  > |         |    |         |    |         |
>  > >  > |   PCC   |----|         |----|  Egress |
>  > >  > |         |     ---------     |         |
>  > >  > |         |       |   |       |         |
>  > >  > |         |     ---------     |         |
>  > >  > |         |----| AS-C    |----|         |
>  > >  > |         |    |         |    |         |
>  > >  > |         |----|         |----|         |
>  > >  >  ---------     |         |     ---------
>  > >  >                |         |
>  > >  >                 ---------
>  > >  > </ascii-art>
>  > >  > Here we have 4 ASes and we want to get from the PCC to the Egress.
>  > >  > The ASes are interconnected as shown.
>  > >  > Let's assume that there are five PCEs. PCE-A, PCE-B, PCE-C and PC=
E-D
>  > have
>  > >  > obvious scope.
>  > >  > PCE-E is special, it is capable of computing paths in AS-B and AS=
-C.
>  > >  >
>  > >  > So, in my book, "the series of domains is known a priori" means t=
hat it
>  > is
>  > >  > known before path computation starts. That means, either the PCC =
knows
>  > the
>  > >  > series of ASes (say, ABD) or the sequence is known by PCE-A.
>  > >  >
>  > >  > In the former case, we need a way for the PCC to pass that inform=
ation
>  > to
>  > >  > PCE-A. Note that this is not a sequence of PCEs. It is a sequence=
 of
>  > >  > domains.
>  > >  >
>  > >  > Let's suppose that PCE-A now knows the series of domains, ABD. Le=
t us
>  > assume
>  > >  > that it selects PCE-B as the next PCE in the series. How does it
>  > communicate
>  > >  > to PCE-B that the series of domains is ABD and not ABCD? One poss=
ible
>  > way to
>  > >  > do this, would be to signal the series of PCEs (PCE-A, PCE-B, PCE=
-D).
>  > But
>  > >  > that has some implication of a one-to-one relationship between PC=
Es and
>  > >  > domains.
>  > >  >
>  > >  > So suppose PCE-A selects PCE-E as the next PCE in the series. How=
 does
>  > PCE-E
>  > >  > know the pre-determined series of domains? How does it know that =
it has
>  > been
>  > >  > asked to find a path across AS-B and not AS-C? Do we suppose that=
 this a
>  > >  > priori knowledge permeates the ether? Or is it passed along with =
the
>  > >  > request? Note that the sequence of PCEs PCE-A, PCE-E, PCE-D does =
not
>  > help
>  > >  > because we could still select a path through domains ABCD.
>  > >  >
>  > >  > So, I think that PCEP needs to be able to indicate the sequence of
>  > domains
>  > >  > that should be traversed. The additional ability to indicate the
>  > sequence of
>  > >  > PCEs is a great supplement.
>  > >  >
>  > >  >
>  > >  > _______________________________________________
>  > >  > Pce mailing list
>  > >  > Pce@ietf.org
>  > >  > https://www.ietf.org/mailman/listinfo/pce
>  > >  >
>  > >  >
>  > >
>  > >
>  > >
>  > >  _______________________________________________
>  > >  Pce mailing list
>  > >  Pce@ietf.org
>  > >  https://www.ietf.org/mailman/listinfo/pce
>  > >
>  >
>  >
>
>
>
>
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


From pce-bounces@ietf.org  Tue Apr  1 06:46:55 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9B16B3A6C10;
	Tue,  1 Apr 2008 06:46:55 -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 C7D163A6DE6
	for <pce@core3.amsl.com>; Tue,  1 Apr 2008 06:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.929
X-Spam-Level: 
X-Spam-Status: No, score=-1.929 tagged_above=-999 required=5 tests=[AWL=0.669, 
	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 uqcjuO2wVe2T for <pce@core3.amsl.com>;
	Tue,  1 Apr 2008 06:46:52 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id 8E0083A6E6B
	for <pce@ietf.org>; Tue,  1 Apr 2008 06:45:05 -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
	m31Dj2aR017114 for <pce@ietf.org>; Tue, 1 Apr 2008 14:45:02 +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
	m31Dj0ZQ017091 for <pce@ietf.org>; Tue, 1 Apr 2008 14:45:01 +0100
Message-ID: <02f501c893fe$94f30570$0300a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Tue, 1 Apr 2008 14:44:58 +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] Quesitons about OF draft
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,

A bunch of nits and a couple of technical question.

Cheers,
Adrian

Please run idnits (http://tools.ietf.org/tools/idnits/) and clean up
any issues shown.
===
Abstract
s/series/set/
s/criteria(s)/criteria/
s/may support one or multiple/may support one or more/
===
Abstract
   ...it is desired for a Path Computation Client (PCC) to
   automatically discover the set of objective functions supported by a
   PCE. Furthermore, it may be useful for a PCC to specify in a path
   computation request the required objective function to be used...
I think you might present the requirements in a slightly different
order. For example:
   A Path Computation Client (PCC) may want a path to be computed for
   one or more TE LSPs according to a specific objective function. Thus,
   the PCC needs to instruct the PCE to use the correct objective
   function. Furthermore, it is possible that not all PCEs support the
   same set of objective functions, therefore it is useful for the PCC
   to be able to automatically discover the set of objective functions
   supported by each PCE.
===
Abstract
   Thus the aim of this
   document is to define extensions to the PCE communication Protocol
   (PCEP) in order to allow a PCC to discover the set of objective
   functions supported by a PCE as well as to allow a PCC to indicate in
   a path computation request the required objective function and a PCE
   to indicate in a path computation reply the objective function that
   was used for path computation.
Can we break this up to make it a bit easier to read and start a new
paragraph? For example:
   This document defines extensions to the PCE communication Protocol
   (PCEP) to allow a PCE to indicate the set of objective functions it
   supports. Extensions are also defined so that a PCC can indicate in
   a path computation request the required objective function, and so
   that a PCE can report in a path computation reply the objective
   function that was used for path computation.
===
 1. Terminology
The indentation of all of the section headers is broken.
You need to have the Introduction as section 1. This means more than
just re-ordering the sections as any acronyms in the Introduction will
need to be expanded.
===
1. Terminology
s/criteria(s)/criteria/
===
2. Introduction
s/A PCE serves/A PCE services/
s/criteria(s)/criteria/
s/candidate path(s)/candidate paths/
s/non synchronized/non-synchronized/
s/It defines PCEP extensions allowing a PCE advertising a list/It defines 
PCEP extensions allowing a PCE to advertise a list/
s/extensions so as to carry/extensions to carry/
s/It thus complements/It complements/
s/parameters should rather be discovered/parameters should be discovered/
s/Objective functions pertain to this second/Objective functions are in this 
second/
s/section 3/Section 3/
s/the list of objective functions that it supports/to list the objective 
functions that it supports/
s/section 4/Section 4/
s/applied by a PCE or in a PCRep/applied by a PCE, or in a PCRep/
===
3.1. OF-List TLV
s/The OSPF OF-List TLV/The PCEP OF-List TLV/  (!)
In the figure, indent the bit numbering by one more space.
In your figure, I suggst you label the final two bytes "padding".
c/(see IANA section)/(see Section 6)/
===
3.2. Elements of procedure
s/A PCE MAY include and OF-List/A PCE MAY include an OF-List/

   The OF-List TLV MUST NOT appear more than once
   in an OPEN object.
Say what happens if more than one is present. I assume you class this
as an invalid Open message and would reject the PCEP session
establishment.

s/The absence of the OF-List TLV in an OPEN object must/The absence of the 
OF-List TLV in an OPEN object MUST/
===
4. Objective Function in PCEP Path Computation request and reply
   messages

Please capitalise the section heading.

At the end of section 4.2 you say that the OF object must not be used in
association with the No-Path object. I have comments about that later,
but if that remains the case, you should mention it in this section.

OLD
   A new flag is defined in the RP object, so as to indicate in a PCReq
   message that the PCE MUST provide in the PCRep message the objective
   function that was used during path computation.
NEW
   A new flag is defined in the RP object. The flag is used in a PCReq
   message to indicate that the PCE MUST include an OF object in the
   PCRep message to indicate the objective function that was used during
   path computation.

s/Also new//Also, new/
s/error type and value//error types and values/
===
4.1. OF Object
s/The OF Object-Types/The OF Object-Type/

Indent the bit number in the figure.

s/(see IANA section)/(see Section 6) /

   Optional TLVs may be defined so as to encode objective function
   parameters.
Perhaps say "in the future"?
===
4.1.1. Elements of Procedure

   To request the use of a specific objective function to be used by the
   PCE a PCC MUST include an OF object in the PCReq message.
This use of RFC2119 "MUST" is likely (on the basis of recent experience)
to cause confusion during IESG review. It is actually a conditional
"MUST", but could be misinterpretted. I think you can safely rephrase
as...
   To request the use of a specific objective function by the PCE, a PCC
   includes an OF object in the PCReq message.

OLD
   [PCEP] specifies a bit flag referred to as the P bit in a PCEP
   common header that can be set by a PCC to enforce a PCE to take into
   account the related information during the path computation.
NEW
   [PCEP] specifies a bit flag, referred to as the P bit, carried in the
   common PCEP object header. The P bit is set by a PCC to mandate that
   a PCE must take the information carried in the object into account
   during the path computation.


   If the
   objective function is mandatory (required objective function), the P
   bit in the OF object MUST be set, else if it is optional (desired
   objective function) the P bit MUST be cleared.
I would prefer to see this text reversed so that we describe the
behavior of the PCE if the bit is set/clear. As you have it at the
moment you are mandating the PCC behavior based on its desires. Either
you should not use RFC 2119 language, or you should re-word according to
how you want the PCE to behave. How about:
   If the P bit is set in the OF object, the objective function is
   mandatory (required objective function) and the PCE MUST use the
   objective function during path computation. If the P bit is clear in
   the OF object, the objective function is optional (desired objective
   function) and the PEC SHOULD apply the function if it is supported,
   but MAY choose to apply a different objective function according to
   local capablities and policy.


        - If the OF object is unknown/unsupported, the PCE MUST follow
          procedures defined in [PCEP], that is if the P bit is set, it
          sends a PCErr message with error type unknown/unsupported
          object (type 3 and 4) and the related path computation request
          MUST be discarded.
You need to describe the error-value to use.

        - If the objective function is unknown / unsupported and the P
          bit is set, the PCE MUST send a PCErr message with a new PCEP
          error type "objective function error" and error value
          "unknown/unsupported objective function" (defined in this
          document), and the related path computation request MUST be
          discarded.
My understanding of our discussion about the PCEP spec was that you
intended to have generic error-types and error-values. This would be a
case for using Error-type 3/4: Unknown/Not supported Object and Error-
value=4: Unrecognized/Unsupported parameter.

===
4.2. Carrying the OF object in a PCEP message

Please capitalise the section heading.

   The OF object MAY be carried within a PCReq message. An OF object
   specifying an objective function that applies to a set of
   synchronized path computation requests MUST be carried just after the
   corresponding SVEC object
Again, there is a conditional "MUST" here. You need to say, "If an
objective function is to be applied to a set... .. the OF object MUST be
carried..."


   An OF object specifying an objective function that applies to an
   individual path computation request (non synchronized case) MUST
   follow the RP object for which it applies.
1. Your BNF shows it following, but not immediately following. I guess
   that this is exactly what you meant to write.
   Wouldn't it be better to put <OF> next to <metric-list> ?
2. I don't like the fact that the OF is sometimes here, sometimes there.
   You need to facilitate several different cases.
   a. Message contains just one request with an OF to apply
   b. Message contains several unsynchronized requests each with an OF
   c. Message contains several synchronized requests with an OF to apply
      to the set of computations
   d. Message contains several synchronized requests with an OF to apply
      to the set of computations, and the message contains one or more
      unsynchronized requests each with an OF to apply.
   It seems to me that your handling of the synchronized requests is a
   problem because it appears that you can have a separate OF for each
   request in the set, but have no way to say the OF that applies to the
   whole set.
   So, I think you need...
     <PCReq Message>::= <Common Header>
                         [ [<OF>] <SVEC-list>]
                         <request-list>
      where:
         <svec-list>::=<SVEC>
                       [<svec-list>]

         <request-list>::=<request>[<request-list>]

         <request>::= <RP>
                      <END-POINTS>
                      [<LSPA>]
                      [<BANDWIDTH>]
                      [<OF>]
                      [<metric-list>]
                      [<RRO>]
                      [<IRO>]
                      [<LOAD-BALANCING>]

   Further, this allows that you to have an OF per requests, and an
   additional OF to cover the set of synchronized requests.


Now, you also have...
      <metric-list>::=<METRIC>[<metric-list>]
This is lifted from [PCEP] and is fine. But don't you also need a
metric list for the synchronized OF?
This would yield...
     <PCReq Message>::= <Common Header>
                         [ [<OF>] [<metric-list>] <SVEC-list>]
                         <request-list>



   When the PCE wants to indicate to the PCC the objective function that
   was used for the synchronized computation of a set of paths, the
   PCRep message MUST include the corresponding SVEC object directly
   followed by the OF object
Again, the conditional use of "MUST" is confusing. Since the previous
paragraph includes "MAY", I think you can use:
s/PCRep message MUST include/PCRep message includes/


   The format of the PCRep message is updated as follows:
Same issues as for the PCReq.

And similarly, aren't some of the metrics you need to report applicable
to the set rather than the individual path? For example, minimize the
cost of the set of paths - report the cost of the set.

s/<SVEC-list>/<svec-list>/


    Note: The OF object MUST NOT be associated to a negative reply, i.e.
    a reply with a NO-PATH object.
I can see that you have other ways of conveying a negative response
related to the OF (unknown, unsupported), or the specific issues
resulting from trying to use the OF (metric, etc.).
Now, suppose the request desires (not requires) an OF, and the response
says No-Path. Shouldn't the response also say which OF was used to
produce this result?

===
4.3. New RP object flag

Please capitalise the section heading.

s/does not follow the recommendation/does not follow the request/

   Objective Function (OF) flag (1 bit): 0x200 (bit number 16)
Currently, PCEP is numbering these bits form the other ned, so this is
bit 10.

s/this indicates that the PCE has to/this indicates that the PCE MUST/

===
4.3.1. Elements of procedure

Please capitalise the section heading.

s/it MUST set/it sets/
s/the PCE has to proceed as follows/the PCE proceeds as follows/

===
5. Objective Functions definition

Please capitalise the section heading.

s/be the IGP metric the TE metric or any/be the IGP metric, the TE metric, 
or any/

===
6.1. PCE Objective Function registry
s/registry/Sub-Registry/

   The guidelines (using terms defined in [RFC2434]) for the
   assignment of objective function code point values are as follows:

/Function code value in the range 1-32767/Function code values in the range 
1-32767/

===
6.2. PCEP code points

Please capitalise the section heading.
===
6.2.3. PCEP Error values

Please capitalise the section heading.

See comment for section 4.1.1
===
6.2.4. RP Object flag

Please capitalise the section heading.
===
7.                    Security Considerations

Ecessive tabs!
===
8.2. Information and Data Models

   The PCEP MIB Module defined in [PCEP-MIB] MUST be extended to include
   Objective Functions.
MUST or SHOULD?
===
8.5. Requirements on other protocols

Please capitalise the section heading.
===
8.6. Impact on network operations

Please capitalise the section heading.
===
10.1. Normative references

Please capitalise the section heading.

   [RFC2740] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6",
   RFC 2740, December 1999.
Unused reference

   [RFC3630] Katz, D., Yeung, D., Kompella, K., "Traffic Engineering
   Extensions to OSPF Version 2", RFC 3630, September 2003.
Unused reference

   [RFC3784] Li, T., Smit, H., "IS-IS extensions for Traffic
   Engineering", RFC 3784, June 2004.
Unused reference
===
10.2. Informative references

Please capitalise the section heading.

   RFC4674, October 2006.

===
11. Author's Addresses:
s/Author's Addresses:Authors' Addresses/
===


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


From pce-bounces@ietf.org  Tue Apr  1 08:28:46 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 69ACB3A6F20;
	Tue,  1 Apr 2008 08:28:46 -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 3A36E3A6F21
	for <pce@core3.amsl.com>; Tue,  1 Apr 2008 08:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 ZLlkmZMyt2qa for <pce@core3.amsl.com>;
	Tue,  1 Apr 2008 08:28:35 -0700 (PDT)
Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11])
	by core3.amsl.com (Postfix) with ESMTP id A186528C63F
	for <pce@ietf.org>; Tue,  1 Apr 2008 08:27:53 -0700 (PDT)
Received: from localhost (imp-4-2.polymtl.ca [132.207.4.77])
	by smtp.polymtl.ca (8.13.8/8.13.8) with ESMTP id m31FRmbV001169;
	Tue, 1 Apr 2008 11:27:49 -0400
Received: from bas1-sthubert21-1279581895.dsl.bell.ca
	(bas1-sthubert21-1279581895.dsl.bell.ca [76.68.222.199]) 
	by www.imp.polymtl.ca (IMP) with HTTP 
	for <meshi@132.207.4.132>; Tue, 01 Apr 2008 11:27:48 -0400
Message-ID: <1207063668.47f2547480648@www.imp.polymtl.ca>
Date: Tue, 01 Apr 2008 11:27:48 -0400
From: Meral Shirazipour <meral.shirazipour@polymtl.ca>
To: Peng He <peng.he.2000@gmail.com>
References: <C41671A3.3173B%jvasseur@cisco.com>
	<023201c89373$818ca760$0300a8c0@your029b8cecfe>
	<1206999947.47f15b8b3331f@www.imp.polymtl.ca>
	<406e32c00803311535y718ce934yf0eaa94496a945f4@mail.gmail.com>
	<1207022210.47f1b28255332@www.imp.polymtl.ca>
	<406e32c00804010615i27d33ea2nec0e98446841d912@mail.gmail.com>
In-Reply-To: <406e32c00804010615i27d33ea2nec0e98446841d912@mail.gmail.com>
MIME-Version: 1.0
User-Agent: Internet Messaging Program (IMP) 3.2.3
X-Originating-IP: 76.68.222.199
X-Poly-FromMTA: (imp-4-2.polymtl.ca [132.207.4.77]) at Tue,
	1 Apr 2008 15:27:48 +0000
Cc: "pce@ietf.org" <pce@ietf.org>
Subject: Re: [Pce] Remaining BRPC last call comment
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi,
   I see your point but please see counterarguments inline...

> Please see inline...
>
> On Mon, Mar 31, 2008 at 11:56 PM, Meral Shirazipour
> <meral.shirazipour@polymtl.ca> wrote:
> > Hi,
> >    Please see inline...
> >
> >
> >  > I agree with Adrian, the domain-sequence should be indicated
> >  > explicitly and kept consistency when passing through.
> >
> >  Again, I believe this is a plus but not a must.
> >  Some PCCs might not even have the capability to come up with such a do=
main
> >  sequence information.
> >
> >
>
> Well, it is not a must that PCCs know the domain sequence, but I think
> it is a must that somebody (e.g, either PCCs or PCEs) know it clearly
> and follow it during the process of path computation. I strongly
> support '"the series of domains is known a priori" means that it is
> known before path computation starts.', which is actually one of the
> very basic assumption of PCE architecture. Based on this assumption,
> PCE architecture is able to compute optimal inter-domain (area or AS)
> path. It should not be the task for PCEs to decide which (next) domain
> to go freely although sometime it might see the next domain is the
> best from its viewpoint.
>
> Since given a domain sequence, there might be several PCE sequences
> matched (different combinations), it is a one-to-many matching, I
> agree with Adrian that  "PCEP needs to be able to indicate the
> sequence of domains that should be traversed".

If the idea is just to add this functionality into PCEP and enable it to
communicate the complete domain sequence, I approve.
However I completely disapprove that all path computation should provide th=
is
information 'apriori'... This would imply that some entity (PCE or other) is
capable of coming up with this optimal? domain sequence... This in turn imp=
lies
that this entity has a global view of the network! From my understanding, t=
he
non-existence of such entity was the whole purpose of coming up with the PCE
architecture which would mainly function in a distributed fashion.

By coming up with such a constraint on all path computations (constraint of
knowing the domain sequence), we will then have to come up with the details=
 of
such entity, and I am afraid that to be functional this entity will have to
anyways implement many of the existing functionalities of the existing PCE
work.


> >  > But I don't understand "each PCE along the path would decide of the
> >  > "best next domain" to traverse next" , I suppose the domain-sequence
> >  > is kind of 'global optimality' by all means; then how does a PCE
> >  > decide  the 'best next domain', how do you define the term 'best', a=
nd
> >  > it might be 'local optimality' in most times as Adrian's example
> >  > indicates.
> >  Of course the term "best" would be of local significance, if the PCE
> making the
> >  decision does not have a global end to end view.
> >
> >
> >  > >   On the other hand, I think it remains crucial to be able to indi=
cate
> the
> >  > >  domain(s) to exclude in the sequence of domains (for diversity or
> >  > political
> >  > >  reasons).
> >  >
> >  > If  the domain-sequence is decided by all means, then it might alrea=
dy
> >  > exclude the unwanted domain(s) I guess.
> >
> >  Again  I don't agree here. Not all PCCs will be able to come up with t=
he
> domain
> >  sequence information. However, and mostly for diversity reasons, they =
will
> know
> >  the domains/PCEs they want to avoid.
>
> Similar example could be: they might want to include (not exclude)
> some domains for some reasons.

Then we could just add to PCEP enough to be able to signal domains to exclu=
de
and/or to exclude from the path. That should solve the problem.

>I believe such domain-level decision
> should be decided by 'something' that is outside of PCE architecture.
> This 'something' provides the domain sequence (might not be optimal),

Why opt for non optimal when PCEs deciding of the next domain could end up =
with
a 'more' optimal path ?

> then PCEs can compute optimal path following this domain sequence.
> PCEs should not have the right/capability to decide which domain(s) to
> go currently.

By removing this right from PCEs we will somehow partly force the local path
computation in the PCE's domain. Maybe not a problem...

>And it is not a must for PCCs to know this also.

If it is not the PCC nor the PCE, then another entity has to be described f=
or
this task, and this is just redundant work for no real reason.

Again I agree that it would be 'nice' to add this feature to PCEP, but I
completely disagree that it should be 'mandatory' for all path computations.
Making it mandatory would even go against the global/distributed vision the=
 PCE
architectures has given to interested parties since it beginnings in 2004-2=
005.

> Regards,
> Peng

Regards,
Meral


> >
> >  > Regards,
> >  > Peng
> >  >
> >
> >  Regards,
> >  Meral
> >
> >
> >
> >
> >  > On Mon, Mar 31, 2008 at 5:45 PM, Meral Shirazipour
> >  > <meral.shirazipour@polymtl.ca> wrote:
> >  > > Hi Adrian,
> >  > >   I do not disagree with you that it would be a plus to be able to
> >  > 'sometimes'
> >  > >  indicate the sequence of domains we want the path to go through;
> however I
> >  > >  understood that in most cases, each PCE along the path would deci=
de
> of the
> >  > >  "best next domain" to traverse next.
> >  > >
> >  > >   On the other hand, I think it remains crucial to be able to indi=
cate
> the
> >  > >  domain(s) to exclude in the sequence of domains (for diversity or
> >  > political
> >  > >  reasons).
> >  > >
> >  > >  Regards,
> >  > >  Meral
> >  > >
> >  > >
> >  > >
> >  > >  Selon Adrian Farrel <adrian@olddog.co.uk>:
> >  > >
> >  > >
> >  > >
> >  > >  > Hi JP,
> >  > >  > Thanks for convergence.
> >  > >  >
> >  > >  > There is just one remaining issue for discussion.
> >  > >  > I've reproduced the thread here, but all the discussion is at t=
he
> end.
> >  > >  >
> >  > >  > Cheers,
> >  > >  > Adrian
> >  > >  >
> >  > >  > >>>> Section 5
> >  > >  > >>>>
> >  > >  > >>>> Is it assumed that PCE(i) knows which domain the requesting
> >  > >  > >>>> PCE(i-1) represents?
> >  > >  > >>>> The reverse is obviously true because PCE(i-1) must select
> >  > >  > >>>> PCE(i) on this basis, but it seems to me that the PCReq co=
uld
> >  > >  > >>>> useful identify the neighboring (upstream) domain. This wo=
uld
> >  > >  > >>>> be particularly useful in the case of a requesting PCE that
> >  > >  > >>>> represents multiple domains since it will allow PCE(i) to =
know
> >  > >  > >>>> which are the BN-en(i) nodes.
> >  > >  > >>>>
> >  > >  > >>>> Conversely, if PCE(i) has computation capabilities for
> multiple
> >  > >  > >>>> domains, it will need to be told which for domain(i) it sh=
ould
> act.
> >  > >  > >>>> So we either need protocol extensions (requesting domain,
> >  > >  > >>>> computation domain) or we need to be told how to use exist=
ing
> >  > >  > >>>> protocol fields for this purpose.
> >  > >  > >>>>
> >  > >  > >>>> Furthermore :-( how although the sequence of domains is kn=
own
> >  > >  > >>>> (a priori) by the PCC, we need some way to convey the sequ=
ence
> >  > >  > >>>> in the PCReq so that PCE(i) knows that the next domain in =
the
> >  > >  > >>>> sequence is domain(i+1).
> >  > >  > >>>> If this can be achieved by existing protocol mechanism, you
> need
> >  > >  > >>>> to describe the procedures. If it can't be done, we need
> protocol
> >  > >  > >>>> extensions.
> >  > >  > >>>
> >  > >  > >>> We make the assumption that the sequence of domains is pre-
> >  > >  > >>> determined or discovered by some means that is outside of t=
he
> >  > >  > >>> scope of this document.
> >  > >  > >>> You're right that we do not say that the sequence of PCE is
> also
> >  > >  > >>> predetermined or discovery by some means. Do you want us to
> >  > >  > >>> explicitly add this assumption?
> >  > >  > >>>
> >  > >  > >>> Consider the two following cases:
> >  > >  > >>> 1) Inter-area: obvious
> >  > >  > >>> 2) Inter-AS: if the sequences of domain and related PCEs are
> known,
> >  > >  > >>> there is no need for protocol extensions except if we want =
to
> >  > enforce
> >  > >  > >>> the sequence of PCEs, which can be done thanks to the PCE-ID
> >  > >  > >>> object defined in
> >  > >  > >>>
> http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-01.txt
> >  > >  > >>> We could include the PCE-ID object definition in BRPC and a=
dd
> >  > >  > >>> some text here.
> >  > >  > >>> Thoughts?
> >  > >  > >>
> >  > >  > >> Well, I have no problems with "the sequence of domains is kn=
own
> a
> >  > >  > >> priori." In fact, I strongly support it.
> >  > >  > >>
> >  > >  > >> However, to whom is this sequence known?
> >  > >  > >>
> >  > >  > >> Yes, if the ingress PCC or PCE knows the PCEs responsible for
> each
> >  > >  > >> domain, then it could provide a list of such PCEs. But this =
is
> more
> >  > >  > >> information than is implied in "the sequence of domains". My
> >  > assumption
> >  > >  > >> is that the default position is that PCE(i) will select
> PCE(i+1).
> >  > >  > >
> >  > >  > > This is what we referred to as =B3discovered by some means=B2=
 indeed.
> >  > >  > >
> >  > >  > >> But how does PCE(i) know that the next domain is domain(i+1)?
> How
> >  > >  > >> is the a priori knowledge passed to PCE(i)?
> >  > >  > >
> >  > >  > > By some means out of the scope of the document.
> >  > >  > > Example: inter-area + PCE on the ABR + PCE discovery
> >  > >  > > (RFC 5088/5089).
> >  > >  > > There are other mechanisms available but out of the scope of =
this
> >  > >  > > document.
> >  > >  > >
> >  > >  > >> This is important, because knowing the sequence of PCEs is n=
ot
> enough
> >  > >  > >> to know the sequence of domains. A PCE may serve more than o=
ne
> >  > >  > >> domain.
> >  > >  >
> >  > >  > OK
> >  > >  > The difference in our view point is, I think, what we mean by "=
the
> >  > series of
> >  > >  > domains is known a priori." Let's use ASes as the example, beca=
use
> it is
> >  > >  > slightly more complex.
> >  > >  > Here comes some ASCII Art (TM)
> >  > >  >
> >  > >  > <ascii-art>
> >  > >  >                 ---------
> >  > >  >                | AS-B    |
> >  > >  >  ---------     |         |     ---------
> >  > >  > | AS-A    |----|         |----| AS-D    |
> >  > >  > |         |    |         |    |         |
> >  > >  > |   PCC   |----|         |----|  Egress |
> >  > >  > |         |     ---------     |         |
> >  > >  > |         |       |   |       |         |
> >  > >  > |         |     ---------     |         |
> >  > >  > |         |----| AS-C    |----|         |
> >  > >  > |         |    |         |    |         |
> >  > >  > |         |----|         |----|         |
> >  > >  >  ---------     |         |     ---------
> >  > >  >                |         |
> >  > >  >                 ---------
> >  > >  > </ascii-art>
> >  > >  > Here we have 4 ASes and we want to get from the PCC to the Egre=
ss.
> >  > >  > The ASes are interconnected as shown.
> >  > >  > Let's assume that there are five PCEs. PCE-A, PCE-B, PCE-C and
> PCE-D
> >  > have
> >  > >  > obvious scope.
> >  > >  > PCE-E is special, it is capable of computing paths in AS-B and
> AS-C.
> >  > >  >
> >  > >  > So, in my book, "the series of domains is known a priori" means
> that it
> >  > is
> >  > >  > known before path computation starts. That means, either the PCC
> knows
> >  > the
> >  > >  > series of ASes (say, ABD) or the sequence is known by PCE-A.
> >  > >  >
> >  > >  > In the former case, we need a way for the PCC to pass that
> information
> >  > to
> >  > >  > PCE-A. Note that this is not a sequence of PCEs. It is a sequen=
ce
> of
> >  > >  > domains.
> >  > >  >
> >  > >  > Let's suppose that PCE-A now knows the series of domains, ABD. =
Let
> us
> >  > assume
> >  > >  > that it selects PCE-B as the next PCE in the series. How does it
> >  > communicate
> >  > >  > to PCE-B that the series of domains is ABD and not ABCD? One
> possible
> >  > way to
> >  > >  > do this, would be to signal the series of PCEs (PCE-A, PCE-B,
> PCE-D).
> >  > But
> >  > >  > that has some implication of a one-to-one relationship between =
PCEs
> and
> >  > >  > domains.
> >  > >  >
> >  > >  > So suppose PCE-A selects PCE-E as the next PCE in the series. H=
ow
> does
> >  > PCE-E
> >  > >  > know the pre-determined series of domains? How does it know tha=
t it
> has
> >  > been
> >  > >  > asked to find a path across AS-B and not AS-C? Do we suppose th=
at
> this a
> >  > >  > priori knowledge permeates the ether? Or is it passed along with
> the
> >  > >  > request? Note that the sequence of PCEs PCE-A, PCE-E, PCE-D does
> not
> >  > help
> >  > >  > because we could still select a path through domains ABCD.
> >  > >  >
> >  > >  > So, I think that PCEP needs to be able to indicate the sequence=
 of
> >  > domains
> >  > >  > that should be traversed. The additional ability to indicate the
> >  > sequence of
> >  > >  > PCEs is a great supplement.
> >  > >  >
> >  > >  >
> >  > >  > _______________________________________________
> >  > >  > Pce mailing list
> >  > >  > Pce@ietf.org
> >  > >  > https://www.ietf.org/mailman/listinfo/pce
> >  > >  >
> >  > >  >
> >  > >
> >  > >
> >  > >
> >  > >  _______________________________________________
> >  > >  Pce mailing list
> >  > >  Pce@ietf.org
> >  > >  https://www.ietf.org/mailman/listinfo/pce
> >  > >
> >  >
> >  >
> >
> >
> >
> >
>
>



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


