From pce-bounces@ietf.org  Sun Nov  2 06:30:03 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E32128C0F7;
	Sun,  2 Nov 2008 06:30:03 -0800 (PST)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id E2A333A6891; Sun,  2 Nov 2008 06:30:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081102143001.E2A333A6891@core3.amsl.com>
Date: Sun,  2 Nov 2008 06:30:01 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-pcep-17.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-17.txt
	Pages           : 85
	Date            : 2008-11-02

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-17.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-17.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-11-02061745.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 Nov  2 07:22:04 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C48623A68D2;
	Sun,  2 Nov 2008 07:22:04 -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 E39D03A68D2
	for <pce@core3.amsl.com>; Sun,  2 Nov 2008 07:22:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.22
X-Spam-Level: 
X-Spam-Status: No, score=-6.22 tagged_above=-999 required=5 tests=[AWL=0.338, 
	BAYES_00=-2.599, MIME_BASE64_BLANKS=0.041, RCVD_IN_DNSWL_MED=-4]
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 97fTzPeEAxiX for <pce@core3.amsl.com>;
	Sun,  2 Nov 2008 07:22:02 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id A76AA3A688B
	for <pce@ietf.org>; Sun,  2 Nov 2008 07:22:02 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,529,1220227200"; 
	d="txt'208?scan'208,208";a="26463866"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 02 Nov 2008 15:22:00 +0000
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 mA2FM0or001873
	for <pce@ietf.org>; Sun, 2 Nov 2008 10:22:00 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id mA2FM01Y005124
	for <pce@ietf.org>; Sun, 2 Nov 2008 15:22: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); 
	Sun, 2 Nov 2008 10:22:00 -0500
Received: from 10.55.201.133 ([10.55.201.133]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Sun,  2 Nov 2008 15:22:00 +0000
User-Agent: Microsoft-Entourage/12.13.0.080930
Date: Sun, 02 Nov 2008 16:21:57 +0100
From: JP Vasseur <jvasseur@cisco.com>
To: <pce@ietf.org>
Message-ID: <C5338426.5B7CE%jvasseur@cisco.com>
Thread-Topic: I-D Action:draft-ietf-pce-pcep-17.txt 
Thread-Index: Ack8/r5e5PHTd9II+kujJbZKr5ZhVg==
In-Reply-To: <20081102143001.E2A333A6891@core3.amsl.com>
Mime-version: 1.0
Content-type: multipart/mixed;
	boundary="B_3308487719_17288285"
X-OriginalArrivalTime: 02 Nov 2008 15:22:00.0473 (UTC)
	FILETIME=[C0708890:01C93CFE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2817; t=1225639320;
	x=1226503320; 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=20I-D=20Action=3Adraft-ietf-pce-pcep-17.t
	xt=20 |Sender:=20 |To:=20<pce@ietf.org>;
	bh=6FpwChb641VRmn5HmHT5u/OPw2n025/JvFnZp6wGWak=;
	b=URtGxWthQxrcqhDLCwNYD4hWmP8Z3rVoQcRAXDgtHOcNJt0qKTptafhQac
	rxgKbWtIaxwdL967WK/zxyZYLCog5BOUChogAnMFXVw8HP5qxAA8H9nzvXwd
	iZadj4wc5B;
Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: [Pce] FW: I-D Action:draft-ietf-pce-pcep-17.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

> 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_3308487719_17288285
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Minor changes, mainly bits numbering alignments (all starting to bit 0 now).

Thanks.

JP.

------ Forwarded Message
From: <Internet-Drafts@ietf.org>
Reply-To: <internet-drafts@ietf.org>
Date: Sun,  2 Nov 2008 06:30:01 -0800 (PST)
To: <i-d-announce@ietf.org>
Cc: <pce@ietf.org>
Subject: I-D Action:draft-ietf-pce-pcep-17.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-17.txt
 Pages           : 85
 Date            : 2008-11-02

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-17.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.
_______________________________________________
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


--B_3308487719_17288285
Content-type: application/octet-stream; name="draft-ietf-pce-pcep-17.txt"
Content-disposition: attachment;
	filename="draft-ietf-pce-pcep-17.txt"
Content-transfer-encoding: base64


Q29udGVudC1UeXBlOiB0ZXh0L3BsYWluDUNvbnRlbnQtSUQ6IDwyMDA4LTExLTAyMDYxNzQ1
LkktREBpZXRmLm9yZz4NDQ==
--B_3308487719_17288285
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

--B_3308487719_17288285--



From pce-bounces@ietf.org  Sun Nov  2 12:00:04 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E30D528C115;
	Sun,  2 Nov 2008 12:00:04 -0800 (PST)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 19C933A6A33; Sun,  2 Nov 2008 12:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081102200002.19C933A6A33@core3.amsl.com>
Date: Sun,  2 Nov 2008 12:00:02 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-pcep-18.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-18.txt
	Pages           : 85
	Date            : 2008-11-02

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-18.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-18.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-11-02115240.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  Mon Nov  3 01:30:03 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B4DFC3A6B14;
	Mon,  3 Nov 2008 01:30:03 -0800 (PST)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 3A50F3A68F2; Mon,  3 Nov 2008 01:30:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081103093001.3A50F3A68F2@core3.amsl.com>
Date: Mon,  3 Nov 2008 01:30:01 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-monitoring-03.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           : A set of monitoring tools for Path Computation Element based Architecture
	Author(s)       : J. Vasseur, et al.
	Filename        : draft-ietf-pce-monitoring-03.txt
	Pages           : 20
	Date            : 2008-11-03

A Path Computation Element (PCE) based architecture has been
specified for the computation of Traffic Engineering (TE) Label
Switched Paths (LSPs) in Multiprotocol Label Switching (MPLS) and
Generalized MPLS (GMPLS) networks in the context of single or
multiple domains (where a domain refers to a collection of network
elements within a common sphere of address management or path
computational responsibility such as IGP areas and Autonomous
Systems).  In PCE-based environments, it is thus critical to monitor
the state of the path computation chain for troubleshooting and
performance monitoring purposes: liveness of each element (PCE)
involved in the PCE chain, detection of potential resource contention
states and statistics in term of path computation times are examples
of such metrics of interest.  This document specifies procedures and
extensions to the Path Computation Element Protocol (PCEP) in order
to gather such information.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-03.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-monitoring-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-11-03012850.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 pcdtm@sterrenkids.nl  Mon Nov  3 04:41:41 2008
Return-Path: <pcdtm@sterrenkids.nl>
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 295D53A6AEB
	for <ietfarch-pce-archive@core3.amsl.com>; Mon,  3 Nov 2008 04:41:41 -0800 (PST)
X-Quarantine-ID: <xhJbJNR3m3Et>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Non-encoded 8-bit data (char AE hex): From: VIAGRA
	\256 Official Site [...]
X-Spam-Flag: NO
X-Spam-Score: -34.015
X-Spam-Level: 
X-Spam-Status: No, score=-34.015 tagged_above=-999 required=5
	tests=[BAYES_95=3, HELO_EQ_DE=0.35, HELO_EQ_DSL=1.129,
	HTML_IMAGE_RATIO_02=0.383, HTML_MESSAGE=0.001,
	HTML_TAG_BALANCE_BODY=1.263, MIME_8BIT_HEADER=0.3,
	MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5,
	RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, SARE_FROM_DRUGS=1.666, SARE_SXLIFE=1.07,
	UNPARSEABLE_RELAY=0.001, URIBL_BLACK=20, URIBL_JP_SURBL=10,
	URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10,
	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 xhJbJNR3m3Et for <ietfarch-pce-archive@core3.amsl.com>;
	Mon,  3 Nov 2008 04:41:40 -0800 (PST)
Received: from e177102010.adsl.alicedsl.de (e177102010.adsl.alicedsl.de [85.177.102.10])
	by core3.amsl.com (Postfix) with SMTP id BBC843A6A69
	for <pce-archive@ietf.org>; Mon,  3 Nov 2008 04:41:38 -0800 (PST)
Received: from Tamera Anastasia (10.14.17.12) by e177102010.adsl.alicedsl.de (PowerMTA(TM) v3.2r4) id hfp73o01d82j11 for <pce-archive@ietf.org>; Mon, 3 Nov 2008 01:41:38 +0100
Message-Id: <20081103024138.3215.qmail@e177102010.adsl.alicedsl.de>
To: <pce-archive@ietf.org>
Subject: RE: Message
From: VIAGRA ® Official Site <pce-archive@ietf.org>
MIME-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Date: Mon,  3 Nov 2008 04:41:38 -0800 (PST)

<html>
<head>
<title>Men's Health Daily Dose</title>
</head>
<!--- Date of email: July 30, 2008--->
<!--- Subject Heading: Daily Dose --->
<body link="#227277" vlink="#227277" alink="#227277">
<script language="Javascript">
<!--
var axel = Math.random() + "";
var ord = axel * 1000000000000000000;
//-->
</script>
<table width="700" border="0" cellspacing="0" cellpadding="0"><tr><td valign="top" width="526">
<table width="526" border="0" cellspacing="0" cellpadding="0"><tr>
<td colspan="2" width="526"><img src="http://images.rodale.com/acc/mh/mhnewsletter/malegram/title-daily-dose-1.gif" alt="" width="526" height="24" border="0" ></td></tr><tr>
<td width="470"><a href="http://www.determinebroad.com"><img src="http://images.rodale.com/acc/mh/mhnewsletter/malegram/title-daily-dose-2.gif" alt="" width="470" height="20" border="0" ></a></td>
<!-- Date -->
<td align="center" bgcolor="#ff3300" width="56"><font size="2" face="arial" color="white"><b>07/30/08</b></font></td></tr>
<tr><td colspan="2" width="526"><a href="http://www."><img src="http://images.rodale.com/acc/mh/mhnewsletter/malegram/title-daily-dose-3.gif" alt="" width="526" height="22" border="0" ></a></td>
</tr></table>
<table width="524" border="0" cellspacing="0" cellpadding="0"><tr height="18"><td width="21" height="18"></td><td valign="top" width="296" height="18"></td><td width="12" height="18"></td>
<td valign="top" width="195" height="18"></td></tr><tr><td width="21"></td>
<!--- Feature Daily Dose --->
<td valign="top" width="296"><font face="arial" color="#860d0d" size="4"><b>FIRE UP YOUR SEX LIFE</b></font><br>
<font size="2" face="arial"><b><strong>Get her in the mood and reap the benefits</strong></b><br><br>
<!--- Feature Image ---><center><a href="http://www.determinebroad.com"><img src="http://www.menshealth.com/media/MH_Static/0601_transformsex_200x200.jpg" alt="" width="200" height="200" border="1"></a>
</center><br>
<a href="http://www."><img src="http://www.tellhigh.com/10.gif" border="0"></a></p>
<!-- Blogs -->
<img src="http://images.rodale.com/acc/mh/mhnewsletter/subtitle-blog-central2.gif" alt="" width="168" height="27" border="0">
<table width="168" border="0" cellspacing="0" cellpadding="3" bgcolor="#860d0d">
<tr height="5"><td width="3" height="5"></td><td valign="top" width="4" height="5"></td><td valign="top" width="143" height="5"></td></tr><tr><td width="3"></td>
<!-- Blog 1 -->
<td valign="top" width="4"><img src="http://images.rodale.com/acc/mh/mhnewsletter/malegram/bullet-arrow.gif" alt="" width="4" height="8" border="0"></td>
<td valign="top" width="143"><b><a href="http://www.determinebroad.com"><font size="2" face="arial" color="white"><I>MH</I> Today: The Latest Health News</font></a></b></td>
</tr><tr><td width="3"></td>
<!-- Blog 2 -->
<td valign="top" width="4"><img src="http://images.rodale.com/acc/mh/mhnewsletter/malegram/bullet-arrow.gif" alt="" width="4" height="8" border="0"></td>
<td valign="top" width="143"><b><a href="http://www.determinebroad.com"><font size="2" face="arial" color="white">Mysteries of the Sexes</font></a></b></td>
</tr><tr><td width="3"></td>
<!-- Blog 3 -->
<td valign="top" width="4"><img src="http://images.rodale.com/acc/mh/mhnewsletter/malegram/bullet-arrow.gif" alt="" width="4" height="8" border="0"></td>
<td valign="top" width="143"><b><a href="http://www."><font size="2" face="arial" color="white">The <I>MH</I> Life</font></a></b></td>
</tr><tr><td width="3"></td>
<!-- Blog 4 -->
<td valign="top" width="4"><img src="http://images.rodale.com/acc/mh/mhnewsletter/malegram/bullet-arrow.gif" alt="" width="4" height="8" border="0"></td>
<td valign="top" width="143"><b><a href="http://www."><font size="2" face="arial" color="white">The Trainer</font></a></b></td>
</tr></table>
<table width="4" border="0" cellspacing="0" cellpadding="0" height="4"><tr><td></td></tr></table>
<table width="168" border="0" cellspacing="0" cellpadding="0" height="98"><tr height="98">
<!-- Ad Unit 160x600 -->
<td align="center" valign="bottom" width="168" height="604"><a 
</tr></table><table width="4" border="0" cellspacing="0" cellpadding="0" height="4"><tr><td></td></tr></table>
<!-- Ad Unit Subscribe -->
</html>





From pce-bounces@ietf.org  Mon Nov  3 07:15:04 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A5E1228C24D;
	Mon,  3 Nov 2008 07:15:04 -0800 (PST)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 3BF6828C13D; Mon,  3 Nov 2008 07:15:00 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081103151501.3BF6828C13D@core3.amsl.com>
Date: Mon,  3 Nov 2008 07:15:01 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-dste-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>
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           : Diff-Serv Aware Class Type Object for Path Computation Element Communication Protocol
	Author(s)       : S. Sivabalan, et al.
	Filename        : draft-ietf-pce-dste-02.txt
	Pages           : 10
	Date            : 2008-11-03

This document specifies a CLASSTYPE object to support Diff-Serve 
Aware Traffic Engineering (DS-TE) where path computation is performed 
with an aid of Path Computation Element (PCE).  

Conventions used in this document 

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 Error! 
Reference source not found..

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-dste-02.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-dste-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-11-03070256.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  Mon Nov  3 07:17:03 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B0A528C2A7;
	Mon,  3 Nov 2008 07:17:03 -0800 (PST)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id 3F61E28C29A; Mon,  3 Nov 2008 07:17:01 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20081103151701.3F61E28C29A@core3.amsl.com>
Date: Mon,  3 Nov 2008 07:17:01 -0800 (PST)
Cc: Internet Architecture Board <iab@iab.org>, pce mailing list <pce@ietf.org>,
	pce chair <pce-chairs@tools.ietf.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Pce] Document Action: 'Policy-Enabled Path Computation Framework'
 to Informational RFC
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

The IESG has approved the following document:

- 'Policy-Enabled Path Computation Framework '
   <draft-ietf-pce-policy-enabled-path-comp-04.txt> as an Informational RFC

This document is the product of the Path Computation Element Working 
Group. 

The IESG contact persons are Ross Callon and David Ward.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-policy-enabled-path-comp-04.txt

Technical Summary

   The Path Computation Element (PCE) Architecture introduces the
   concept of policy in the context of path computation. This document
   provides additional details on policy within the PCE Architecture and
   also provides context for the support of PCE Policy. This document
   introduces the use of the Policy Core Information Model (PCIM) as a
   framework for supporting path computation policy. This document also
   provides representative scenarios for the support of PCE Policy.

Working Group Summary

   No controversy reported. The working group chairs were not
   completely convinced that there was a need for this document, 
   but members of the working group were supportive, and it is 
   certainly true that policy is discussed within the PCE 
   architecture (RFC 4655) and is very applicable for inter-AS PCE.
   To the shepherding AD (Ross), the information discussed in this
   document is very much central to the point of PCE, and the only
   issue is whether it is so obvious that it is not necessary to 
   actually write it down (but in general it seems better to write 
   down non-controversial explanatory material). 

   As reported in the PROTO writeup, there were no problems with 
   consensus for this document, and when the I-D was accepted by 
   the WG there was strong support.

Document Quality

   This is an informational document that does not specify any
   protocol that could be implemented. The work that is ongoing 
   in the PCE WG is compatible with this document. 

Personnel

   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. Ross Callon is the responsible AD.
   There are no IANA actions required. A null IANA section is present.

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


From pce-bounces@ietf.org  Mon Nov  3 09:48:06 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD0F528C13A;
	Mon,  3 Nov 2008 09:48: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 205A33A6BF0
	for <pce@core3.amsl.com>; Mon,  3 Nov 2008 09:48:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.821
X-Spam-Level: 
X-Spam-Status: No, score=-1.821 tagged_above=-999 required=5 tests=[AWL=0.777, 
	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 x0MciRuQS94s for <pce@core3.amsl.com>;
	Mon,  3 Nov 2008 09:48:03 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 30AB428C200
	for <pce@ietf.org>; Mon,  3 Nov 2008 09:47:23 -0800 (PST)
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
	mA3HlHKc026396 for <pce@ietf.org>; Mon, 3 Nov 2008 17:47:17 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
	mA3HlG5B026371 for <pce@ietf.org>; Mon, 3 Nov 2008 17:47:16 GMT
Message-ID: <0A932ACDA56843A4BF14B5C9917D2DA8@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Mon, 3 Nov 2008 17:47:11 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: [Pce] Fw: Please publish draft-ietf-pce-ds-te-02.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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

FYI, this I-D is now with the AD for review.
Adrian
----- Original Message ----- 
From: "JP Vasseur" <jvasseur@cisco.com>
To: "Ross Callon" <rcallon@juniper.net>; "The IESG" 
<iesg-secretary@ietf.org>
Cc: "David Ward" <dward@cisco.com>; "Adrian Farrel" <adrian@olddog.co.uk>; 
"Siva Sivabalan (msiva)" <msiva@cisco.com>
Sent: Monday, November 03, 2008 3:23 PM
Subject: Please publish draft-ietf-pce-ds-te-02.txt


> Proto-write-up for draft-ietf-pce-ds-te-02.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?
>
> JP Vasseur 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?
>
> The I-D was well discussed when first posted and then got stable fairly
> quickly.
>
>> (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?
>
> No concerns.
>
>> (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.
>
> No issue specific issues.
>
> No IPR disclosures 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?
>
> Good consensus, the document specifies fairly straightforward protocol
> extensions.
>
>> (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?
>
> Yes.
>
> 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].
>
> No downward reference.
>
>> (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 requests extensions to the PCEP IANA registries.
> The IANA section looks good.
>
>> (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?
>
> A reference to draft-farrel-rtg-common-bnf is included in the document for
> the BNF used in this document.
>
> [OBJ-ORD] Farrel, A., "Reduced Backus-Naur Form (RBNF) A Syntax Used
>             in Various Protocol Specifications", draft-farrel-rtg-
>             common-bnf-07.txt, November 2008.
>
>
> No tool has been used for verification.
>
>> (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.
>
>   The Internet Draft [PCEP-ID] 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, in compliance with [RFC4657].
>
>   Differentiated Service aware MPLS Traffic Engineering (DS-TE)
>   addresses the fundamental requirement to be able to enforce different
>   bandwidth constraints for different classes of traffic. It describes
>   mechanisms to achieve per-class traffic engineering, rather than on
>   an aggregate basis across all classes by enforcing Bandwidth
>   Constraints (BCs) on different classes. Requirements for DS-TE and
>   the associated protocol extensions are specified in [RFC3564] and
>   [RFC4124] respectively.
>
>   As per [RFC4657], PCEP must support traffic class-type as an MPLS TE
>   specific constraint. However, in the present form, PCEP [PCEP-ID]
>   does not have the capability to specify the class-type in the path
>   computation request.
>
>   In this document, we define a new PCEP object called CLASSTYPE which
>   carries the class-type of the TE LSP in the path computation request.
>   During path computation, a PCE uses the class-type to identify the
>   bandwidth constraint of the TE-LSP.
>
>>        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?
>
> Good support and no controversy.
>
>>        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?
>
> No known implementation of the I-D but several mentioned that they were
> planning to implement the protocol extensions specifies in the document.
> Furthermore, the protocol extensions are very straightforward.
>
> Thanks.
>
> JP.
> 

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


From pce-bounces@ietf.org  Mon Nov  3 15:45:04 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ED45128C412;
	Mon,  3 Nov 2008 15:45:04 -0800 (PST)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 503D328C3EE; Mon,  3 Nov 2008 15:45:00 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081103234501.503D328C3EE@core3.amsl.com>
Date: Mon,  3 Nov 2008 15:45:01 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] I-D ACTION:draft-ietf-pce-pcep-p2mp-extensions-01.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 Point-to-Multipoint Traffic Engineering Label Switched Paths
	Author(s)	: Q. Zhao, D. King, F. Verhaeghe, T. Takeda, M. Chaitou, J. Le Roux, Z. Ali
	Filename	: draft-ietf-pce-pcep-p2mp-extensions-01.txt
	Pages		: 29
	Date		: 2008-11-3
	
Point-to-point Multiprotocol Label Switching (MPLS) and Generalized    MPLS (GMPLS) Traffic Engineering Label Switched Paths (TE LSPs) may
   be established using signaling techniques, but their paths may first
   be determined.  The Path Computation Element (PCE) has been
   identified as an appropriate technology for the determination of the
   paths of P2MP TE LSPs.

   This document describes extensions to the PCE communication Protocol
   (PCEP) to handle requests and responses for the computation of paths
   for P2MP TE LSPs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-p2mp-extensions-01.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-p2mp-extensions-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-11-3153947.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 Nov  4 02:43: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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C89C83A6A47;
	Tue,  4 Nov 2008 02:43:51 -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 A875C3A6A47
	for <pce@core3.amsl.com>; Tue,  4 Nov 2008 02:43:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level: 
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_LOW=-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 O0PtRof0KZbj for <pce@core3.amsl.com>;
	Tue,  4 Nov 2008 02:43:49 -0800 (PST)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com
	[195.101.245.16])
	by core3.amsl.com (Postfix) with ESMTP id 4C58D3A696F
	for <pce@ietf.org>; Tue,  4 Nov 2008 02:43:49 -0800 (PST)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 4 Nov 2008 11:43:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 4 Nov 2008 11:43:43 +0100
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD10540AEB4@ftrdmel1>
In-Reply-To: <C52DFBC5.5A585%jvasseur@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: comments on  draft-ietf-pce-monitoring-03.txt
thread-index: AcktX7d31jLp09e2xkS/+riDXF4HuwGLeIswAYk6wyQBKeT2oA==
References: <DD8B8FEBBFAF9E488F63FF0F1A69EDD105395FCC@ftrdmel1>
	<C52DFBC5.5A585%jvasseur@cisco.com>
From: <emile.stephan@orange-ftgroup.com>
To: <pce@ietf.org>
X-OriginalArrivalTime: 04 Nov 2008 10:43:44.0211 (UTC)
	FILETIME=[3584A230:01C93E6A]
Subject: [Pce] comments on  draft-ietf-pce-monitoring-03.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: multipart/mixed; boundary="===============0427866865=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0427866865==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93E6A.3539F837"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93E6A.3539F837
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi
=20
Following are some typos and clarifications I noted while going through
the draft draft-ietf-pce-monitoring-03.txt. I was looking for management
information for the discovery MIB.
=20
=20
Typos
=20
"In PCE-based environments, it is critical to monitor the state of the
   path computation chain for <<<troubeshooting>>> and performance
monitoring"
=20
"such metric can have a form of a <<bolean>> "
=20
=20
Section 3.1
"If the Monitoring object is missing, the receiving PCE MUST <<send>> a
PCErr"
Perhaps <<respond with>> is preferable to <<send>>.=20
=20
=20
"For the sake of <<<illustraion>>>"
=20
Clarification:
=20
Section 3
The explanations of in band and out band may need some enhancement. The
following is unclear: "By "In band" we refer to the situation whereby a
PCC requests to gather metrics in the context of a path computation
request". "in band" and "out band" meaning may be introduced in the
terminology section.=20
=20
"state metrics" may be introduced in the terminology section too.
=20
=20
Section 3.1=20
It defines PCMonRep message but introduces a PCMonReq error message.
This mix makes the text "Other objects are optional" very unclear.=20
=20
Examples may illustrated "in band" and "out band" situations. Example 2
may detail the part of the PCMonReq message requesting the PROC-TIME
information in the PCMonrep.
=20
      Section 3.2
Does "<metric-pce-list>" differ from "<metric-list>"?
=20
=20
Regards
Emile
=20

------_=_NextPart_001_01C93E6A.3539F837
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 11">
<meta name=3DOriginator content=3D"Microsoft Word 11">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C93E72.96859320">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:DontDisplayPageBoundaries/>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:EnvelopeVis/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:UseFELayout/>
  </w:Compatibility>
 </w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" LatentStyleCount=3D"156">
 </w:LatentStyles>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-alt:\5B8B\4F53;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:SimSun;
	mso-ansi-language:EN-US;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:SimSun;
	mso-ansi-language:EN-US;}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:SimSun;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 69.6pt 72.0pt 69.6pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Tableau Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-ansi-language:#0400;
	mso-fareast-language:#0400;
	mso-bidi-language:#0400;}
</style>
<![endif]-->
</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:35.4pt'>

<div class=3DSection1>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>Hi<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>Following are some typos and clarifications I =
noted
while going through the draft draft-ietf-pce-monitoring-03.txt. I was =
looking
for management information for the discovery =
MIB.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>Typos<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&quot;In PCE-based environments, =
it is
critical to monitor the state of the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp;
</span><span class=3DGramE>path</span> computation chain for =
&lt;&lt;&lt;<span
class=3DSpellE>troubeshooting</span>&gt;&gt;&gt; and performance =
monitoring&quot;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&quot;<span =
class=3DGramE>such</span> metric
can have a form of a &lt;&lt;<span class=3DSpellE>bolean</span>&gt;&gt; =
&quot;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Section =
3.1<o:p></o:p></span></font></p>

<pre style=3D'margin-left:35.4pt'><font size=3D2 face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt;mso-ansi-language:EN-US'>&quot;</span></font><s=
pan
lang=3DEN-GB style=3D'mso-ansi-language:EN-GB'>If the Monitoring object =
is missing, the receiving PCE MUST &lt;&lt;send&gt;&gt; a <span
class=3DSpellE>PCErr</span>&quot;<o:p></o:p></span></pre><pre =
style=3D'margin-left:
35.4pt'><font size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
mso-ansi-language:EN-GB'>Perhaps &lt;&lt;respond with&gt;&gt; is =
preferable to &lt;&lt;send&gt;&gt;. <o:p></o:p></span></font></pre>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></spa=
n></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></spa=
n></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>&quot;For the sake of =
&lt;&lt;&lt;<span
class=3DSpellE>illustraion</span>&gt;&gt;&gt;&quot;</span></font><span
lang=3DEN-GB style=3D'mso-ansi-language:EN-GB'><o:p></o:p></span></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></spa=
n></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'>Clarification:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Section =
3<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>The explanations of in band and =
out band may
need some enhancement. The following is unclear: &quot;By &quot;In =
band&quot;
we refer to the situation whereby a PCC requests to gather metrics in =
the
context of a path computation request&quot;. </span></font><span =
lang=3DEN-GB
style=3D'mso-ansi-language:EN-GB'>&quot;<span class=3DGramE>in</span> =
band&quot;
and &quot;out band&quot; meaning may be introduced in the terminology =
section. <o:p></o:p></span></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></spa=
n></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'>&quot;<span
class=3DGramE>state</span> metrics&quot; may be introduced in the =
terminology
section too.</span><span lang=3DEN-US><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-US
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<pre style=3D'margin-left:35.4pt'><font size=3D2 face=3D"Courier =
New"><span
lang=3DEN-US =
style=3D'font-size:10.0pt;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></spa=
n></font></pre><pre
style=3D'margin-left:35.4pt'><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'>Section 3.1 =
<o:p></o:p></span></font></pre><pre
style=3D'margin-left:35.4pt'><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'>It defines <span =
class=3DSpellE>PCMonRep</span> message but introduces a <span
class=3DSpellE>PCMonReq</span> error message. This mix makes the text =
&quot;Other objects are optional&quot; very unclear. =
<o:p></o:p></span></font></pre>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></spa=
n></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-GB style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'>Examples =
may
illustrated &quot;in band&quot; and &quot;out band&quot; situations. =
Example 2
may detail the part of the <span class=3DSpellE>PCMonReq</span> message
requesting the PROC-TIME information in the <span =
class=3DSpellE>PCMonrep</span>.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-GB =
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></spa=
n></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'><span =
style=3D'mso-tab-count:
1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Section =
3.2<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:35.4pt'><font size=3D2 =
face=3D"Courier New"><span
lang=3DEN-US style=3D'font-size:10.0pt'>Does &quot;&lt;metric-<span =
class=3DSpellE>pce</span>-list&gt;&quot;
differ from &quot;&lt;metric-list&gt;&quot;?</span></font><span =
lang=3DEN-GB
style=3D'mso-ansi-language:EN-GB'><o:p></o:p></span></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></spa=
n></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'><o:p>&nbsp;</o:p></spa=
n></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'>Regards<o:p></o:p></sp=
an></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'>Emile<o:p></o:p></span=
></font></p>

<pre><font size=3D2 color=3Dblack face=3D"Courier New"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;color:black;mso-ansi-language:EN-GB'><o:p>&nbsp=
;</o:p></span></font></pre></div>

</body>

</html>

------_=_NextPart_001_01C93E6A.3539F837--

--===============0427866865==
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

--===============0427866865==--


From pce-bounces@ietf.org  Wed Nov  5 00:43: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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2368E3A680F;
	Wed,  5 Nov 2008 00:43:21 -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 99F3D3A6805
	for <pce@core3.amsl.com>; Wed,  5 Nov 2008 00:43:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.148
X-Spam-Level: 
X-Spam-Status: No, score=-4.148 tagged_above=-999 required=5 tests=[AWL=0.384, 
	BAYES_00=-2.599, 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 li2eqMyP66LN for <pce@core3.amsl.com>;
	Wed,  5 Nov 2008 00:43:18 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 577653A680F
	for <pce@ietf.org>; Wed,  5 Nov 2008 00:43:18 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,549,1220227200"; d="scan'208";a="26766890"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 05 Nov 2008 08:43:15 +0000
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 mA58hFD8027616
	for <pce@ietf.org>; Wed, 5 Nov 2008 03:43:15 -0500
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 mA58hFMG020912
	for <pce@ietf.org>; Wed, 5 Nov 2008 08:43:15 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, 5 Nov 2008 03:43:15 -0500
Received: from 144.254.188.136 ([144.254.188.136]) by
	xmb-rtp-213.amer.cisco.com ([64.102.31.112]) with Microsoft
	Exchange Server HTTP-DAV ; Wed,  5 Nov 2008 08:43:15 +0000
User-Agent: Microsoft-Entourage/12.13.0.080930
Date: Wed, 05 Nov 2008 09:43:12 +0100
From: JP Vasseur <jvasseur@cisco.com>
To: <pce@ietf.org>
Message-ID: <C5371B30.5C357%jvasseur@cisco.com>
Thread-Topic: [Pce] I-D ACTION:draft-ietf-pce-pcep-p2mp-extensions-01.txt
Thread-Index: Ack/IokyvMBGuA00o0GbgwxfF1k5Iw==
In-Reply-To: <20081103234501.503D328C3EE@core3.amsl.com>
Mime-version: 1.0
X-OriginalArrivalTime: 05 Nov 2008 08:43:15.0604 (UTC)
	FILETIME=[8B587D40:01C93F22]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1779; t=1225874595;
	x=1226738595; 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]=20I-D=20ACTION=3Adraft-ietf-pce-p
	cep-p2mp-extensions-01.txt |Sender:=20 |To:=20<pce@ietf.org>;
	bh=O9O/0pdW1uDmU+LXf7jn2ArNeuHMsqIHBDalWnQDLSg=;
	b=eLi6lHNfpeeQ6oZeeNtbyjqNWP69dOjkvD1vghO7yG1etsAl/oVE8q4gd5
	OOfX2XADC5Csz1nbaXBz/umb8RfE3UvXmFKtQnkQdfC7IZjuKi5tQNtHyCmi
	1ZEQ6uh2Uw;
Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: Re: [Pce] I-D ACTION:draft-ietf-pce-pcep-p2mp-extensions-01.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

Authors,

Can you summarize the changes on the list ?

Many Thanks.

JP.


On 11/4/08 12:45 AM, "Internet-Drafts@ietf.org" <Internet-Drafts@ietf.org>
wrote:

> 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 Point-to-Multipoint Traffic Engineering Label Switched Paths
> Author(s) : Q. Zhao, D. King, F. Verhaeghe, T. Takeda, M. Chaitou, J. Le Roux,
> Z. Ali
> Filename : draft-ietf-pce-pcep-p2mp-extensions-01.txt
> Pages  : 29
> Date  : 2008-11-3
> 
> Point-to-point Multiprotocol Label Switching (MPLS) and Generalized    MPLS
> (GMPLS) Traffic Engineering Label Switched Paths (TE LSPs) may
>    be established using signaling techniques, but their paths may first
>    be determined.  The Path Computation Element (PCE) has been
>    identified as an appropriate technology for the determination of the
>    paths of P2MP TE LSPs.
> 
>    This document describes extensions to the PCE communication Protocol
>    (PCEP) to handle requests and responses for the computation of paths
>    for P2MP TE LSPs.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-p2mp-extensions-01.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  Wed Nov  5 11:32:13 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B7EFA3A69F8;
	Wed,  5 Nov 2008 11:32:13 -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 80B8F3A69F8
	for <pce@core3.amsl.com>; Wed,  5 Nov 2008 11:32:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.528
X-Spam-Level: 
X-Spam-Status: No, score=-5.528 tagged_above=-999 required=5
	tests=[AWL=-0.326, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
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 tW0nzMSQ8XQd for <pce@core3.amsl.com>;
	Wed,  5 Nov 2008 11:32:11 -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 5CA203A6452
	for <pce@ietf.org>; Wed,  5 Nov 2008 11:32:11 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,552,1220227200"; d="scan'208,217";a="26874568"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 05 Nov 2008 19:31:53 +0000
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 mA5JVqkc018450
	for <pce@ietf.org>; Wed, 5 Nov 2008 14:31:52 -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.13.8/8.13.8) with ESMTP id mA5JVqaD000779
	for <pce@ietf.org>; Wed, 5 Nov 2008 19:31:52 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); 
	Wed, 5 Nov 2008 14:31:52 -0500
Received: from 10.61.104.94 ([10.61.104.94]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Wed,  5 Nov 2008 19:31:52 +0000
User-Agent: Microsoft-Entourage/12.13.0.080930
Date: Wed, 05 Nov 2008 20:31:51 +0100
From: JP Vasseur <jvasseur@cisco.com>
To: <pce@ietf.org>
Message-ID: <C537B337.5C58B%jvasseur@cisco.com>
Thread-Topic: PCE WG Draft Agenda published
Thread-Index: Ack/fSa6nxxL679LzES5VIMH4EO32g==
Mime-version: 1.0
X-OriginalArrivalTime: 05 Nov 2008 19:31:52.0719 (UTC)
	FILETIME=[27C0F9F0:01C93F7D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1002; t=1225913512;
	x=1226777512; 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:=20PCE=20WG=20Draft=20Agenda=20published |Sender:=20
	|To:=20<pce@ietf.org>;
	bh=0oOMp89czCjjiw6L7Tg3eMZ3D/rYxlq3zuqdegTGuEQ=;
	b=RoyrEDNG+iY3hOXoyEUVMXi/c8XinyDlrmbK95+K9yQAlkAtB3t0sqxBIL
	5k8O2kJeHX7u8kLseX1PyB7B+/sMm81LjKKGO0MJqeoDjXdBVVxcuNAMRZLk
	I9h3Qahhs/;
Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: [Pce] PCE WG Draft Agenda published
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="===============0565557059=="
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.

--===============0565557059==
Content-type: multipart/alternative;
	boundary="B_3308761912_1091499"

> 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_3308761912_1091499
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Dear all,

Here is the draft agenda for the PCE WG Meeting:
http://www.ietf.org/proceedings/08nov/agenda/pce.txt

Let us know if you have any comment.

Thanks.

JP.

--B_3308761912_1091499
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>PCE WG Draft Agenda published</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:13pt=
'>Dear all,<BR>
<BR>
Here is the draft agenda for the PCE WG Meeting: <a href=3D"http://www.ietf.o=
rg/proceedings/08nov/agenda/pce.txt">http://www.ietf.org/proceedings/08nov/a=
genda/pce.txt</a><BR>
<BR>
Let us know if you have any comment.<BR>
<BR>
Thanks.<BR>
<BR>
JP.</SPAN></FONT>
</BODY>
</HTML>


--B_3308761912_1091499--


--===============0565557059==
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

--===============0565557059==--



From pce-bounces@ietf.org  Wed Nov  5 13:05: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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 615EB3A6A8B;
	Wed,  5 Nov 2008 13:05: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 BEF0E3A6452
	for <pce@core3.amsl.com>; Wed,  5 Nov 2008 13:05:45 -0800 (PST)
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 Ln3y+kBJN0+V for <pce@core3.amsl.com>;
	Wed,  5 Nov 2008 13:05:45 -0800 (PST)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180])
	by core3.amsl.com (Postfix) with ESMTP id E1E1F3A6A8B
	for <pce@ietf.org>; Wed,  5 Nov 2008 13:05:44 -0800 (PST)
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 <0K9V00EKZP9F6M@usaga04-in.huawei.com> for
	pce@ietf.org; Wed, 05 Nov 2008 15:05:39 -0600 (CST)
Received: from Z73671a ([10.192.21.59])
	by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0K9V00GXEP9A19@usaga04-in.huawei.com> for
	pce@ietf.org; Wed, 05 Nov 2008 15:05:39 -0600 (CST)
Date: Wed, 05 Nov 2008 16:05:34 -0500
From: Quintin Zhao <qzhao@huawei.com>
In-reply-to: <mailman.44.1225915203.10466.pce@ietf.org>
To: pce@ietf.org
Message-id: <000801c93f8a$3f6d3c50$3b15c00a@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: Ack/gTieaavKpeBDRrKkiLgJasuzJwABQ+9Q
References: <mailman.44.1225915203.10466.pce@ietf.org>
Subject: [Pce] new version of draft-ietf-pce-pcep-p2mp-extensions
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 all,

We made an update for this draft. The main update in this new version is
based on the new requirement specified in section 2.1.7 of
draft-ietf-pce-p2mp-req-00.txt. 

The requirement is: 

A single P2MP LSP may have very many destinations, and the computed path
(tree) may be very extensive. In these cases it is possible that the entire
Path Computation Request or Response cannot fit within one PCE message.
Therefore, it MUST be possible for a single request or response to be
conveyed by a sequence of PCE messages.

In this new version of the draft, we propose to use SVEC/synctimer mechanism
both for PCReq message and PCRep message in case of too large P2MP Path
Computation Request or Response. 


Thanks,
Quintin
 

> 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 Point-to-Multipoint Traffic Engineering Label Switched Paths
> Author(s) : Q. Zhao, D. King, F. Verhaeghe, T. Takeda, M. Chaitou, J. Le
Roux,
> Z. Ali
> Filename : draft-ietf-pce-pcep-p2mp-extensions-01.txt
> Pages  : 29
> Date  : 2008-11-3
> 
> Point-to-point Multiprotocol Label Switching (MPLS) and Generalized
MPLS
> (GMPLS) Traffic Engineering Label Switched Paths (TE LSPs) may
>    be established using signaling techniques, but their paths may first
>    be determined.  The Path Computation Element (PCE) has been
>    identified as an appropriate technology for the determination of the
>    paths of P2MP TE LSPs.
> 
>    This document describes extensions to the PCE communication Protocol
>    (PCEP) to handle requests and responses for the computation of paths
>    for P2MP TE LSPs.
> 
> A URL for this Internet-Draft is:
>
http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-p2mp-extensions-01.t
xt
> 
> 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  Thu Nov  6 01:21:26 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA2183A69E0;
	Thu,  6 Nov 2008 01:21:26 -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 26E873A69E0
	for <pce@core3.amsl.com>; Thu,  6 Nov 2008 01:21:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.454
X-Spam-Level: 
X-Spam-Status: No, score=-3.454 tagged_above=-999 required=5
	tests=[AWL=-0.319, 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 CJ-+DWSOI0yy for <pce@core3.amsl.com>;
	Thu,  6 Nov 2008 01:21:20 -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 8D0193A6969
	for <pce@ietf.org>; Thu,  6 Nov 2008 01:21:20 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,556,1220227200"; d="scan'208,217";a="26939749"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 06 Nov 2008 09:21:15 +0000
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 mA69LFj8023277
	for <pce@ietf.org>; Thu, 6 Nov 2008 04:21:15 -0500
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 mA69LF8E005765
	for <pce@ietf.org>; Thu, 6 Nov 2008 09:21:15 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); 
	Thu, 6 Nov 2008 04:21:15 -0500
Received: from 144.254.43.8 ([144.254.43.8]) by xmb-rtp-213.amer.cisco.com
	([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu,  6 Nov 2008 09:21:15 +0000
User-Agent: Microsoft-Entourage/12.13.0.080930
Date: Thu, 06 Nov 2008 10:21:11 +0100
From: JP Vasseur <jvasseur@cisco.com>
To: JP Vasseur <jvasseur@cisco.com>, <pce@ietf.org>
Message-ID: <C5387597.5C7A4%jvasseur@cisco.com>
Thread-Topic: [Pce] PCE WG Draft Agenda published
Thread-Index: Ack/fSa6nxxL679LzES5VIMH4EO32gAc9tEy
In-Reply-To: <C537B337.5C58B%jvasseur@cisco.com>
Mime-version: 1.0
X-OriginalArrivalTime: 06 Nov 2008 09:21:15.0680 (UTC)
	FILETIME=[04CA3A00:01C93FF1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2128; t=1225963275;
	x=1226827275; 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]=20PCE=20WG=20Draft=20Agenda=20pub
	lished |Sender:=20
	|To:=20JP=20Vasseur=20<jvasseur@cisco.com>,=20<pce@ietf.org >;
	bh=4fGlNBdSDucJkRb+waoUeB/AhAgs/ugYqosgZNuTMnA=;
	b=rzV1AMrje/ocU8kgXxxSOrtCLnet0ErYE+TJ/4+wqvadgVUKmu0oPSWXXQ
	N8089tsLMxftp/K0NLQFT18ItSLPlJYQGTjD8oMRdQD5ugtJVUnjYi09GKbN
	VpdyrqZxXC;
Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: Re: [Pce] PCE WG Draft Agenda published
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="===============1271275863=="
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.

--===============1271275863==
Content-type: multipart/alternative;
	boundary="B_3308811673_2005324"

> 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_3308811673_2005324
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

New agenda published: http://www.ietf.org/proceedings/08nov/agenda/pce.txt


On 11/5/08 8:31 PM, "JP Vasseur" <jvasseur@cisco.com> wrote:

> Dear all,
> 
> Here is the draft agenda for the PCE WG Meeting:
> http://www.ietf.org/proceedings/08nov/agenda/pce.txt
> 
> Let us know if you have any comment.
> 
> Thanks.
> 
> JP.
> 
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce


--B_3308811673_2005324
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Pce] PCE WG Draft Agenda published</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:13pt=
'>New agenda published: <a href=3D"http://www.ietf.org/proceedings/08nov/agend=
a/pce.txt">http://www.ietf.org/proceedings/08nov/agenda/pce.txt</a><BR>
<BR>
<BR>
On 11/5/08 8:31 PM, &quot;JP Vasseur&quot; &lt;<a href=3D"jvasseur@cisco.com"=
>jvasseur@cisco.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:13pt'>Dear all,<BR>
<BR>
Here is the draft agenda for the PCE WG Meeting: <a href=3D"http://www.ietf.o=
rg/proceedings/08nov/agenda/pce.txt">http://www.ietf.org/proceedings/08nov/a=
genda/pce.txt</a><BR>
<BR>
Let us know if you have any comment.<BR>
<BR>
Thanks.<BR>
<BR>
JP.<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"></SPAN></FONT><FONT SIZE=3D"1"><FONT FA=
CE=3D"Consolas, Courier New, Courier"><SPAN STYLE=3D'font-size:10pt'>___________=
____________________________________<BR>
Pce mailing list<BR>
<a href=3D"Pce@ietf.org">Pce@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/pce">https://www.ietf.org/ma=
ilman/listinfo/pce</a><BR>
</SPAN></FONT></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3308811673_2005324--


--===============1271275863==
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

--===============1271275863==--



From pce-bounces@ietf.org  Tue Nov 11 16:08:59 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB41128C163;
	Tue, 11 Nov 2008 16:08:59 -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 9AACB28C163
	for <pce@core3.amsl.com>; Tue, 11 Nov 2008 16:08:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[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 zAWVr0tuxwbz for <pce@core3.amsl.com>;
	Tue, 11 Nov 2008 16:08:57 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 6693D28C150
	for <pce@ietf.org>; Tue, 11 Nov 2008 16:08:57 -0800 (PST)
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
	mAC08oxj032032 for <pce@ietf.org>; Wed, 12 Nov 2008 00:08:50 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
	mAC08nDc032019 for <pce@ietf.org>; Wed, 12 Nov 2008 00:08:50 GMT
Message-ID: <22094062BE0D47819B63D64BA3E17776@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Wed, 12 Nov 2008 00:08:46 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: [Pce] NOTE WELL: New Boilerplate Text Required for all new
	Submissions to IETF
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Note well. Your I-Ds will not be posted unless they conform to new 
boiler-plate requirements.

Adrian
----- Original Message ----- 
From: "Ed Juskevicius" <edj@nortel.com>
To: "IETF Discussion" <ietf@ietf.org>; <ietf-announce@ietf.org>; 
<ipr-wg@ietf.org>; <iesg@ietf.org>; <iab@iab.org>; "RFC Editor" 
<rfc-editor@rfc-editor.org>; <wgchairs@ietf.org>
Cc: <trustees@ietf.org>
Sent: Tuesday, November 11, 2008 11:03 PM
Subject: Announcement: New Boilerplate Text Required for all new 
Submissionsto IETF


> Greetings.  This message is to draw your attention to the significance
> of the publication of RFC5377 and RFC5378 earlier today.
>
> * RFC5377 is Advice to the Trustees of the IETF Trust on Rights to Be
> Granted in IETF Documents
> * RFC5378 is Rights Contributors Provide to the IETF Trust
>
> Note that RFC5378 is also BCP0078.  RFC5378 is an update to RFC2026, and
> RFC5378 obsoletes both RFC3978 and RFC4748.
>
> Coincident with the above, the IETF Trustees have posted a new policy
> document with guidance to the community on:
> * Legal Provisions Relating to IETF Documents at
> http://trustee.ietf.org/license-info/
>
> Taken as a set, the documents listed above specify changes that are now
> required in all new submissions into the IETF.
>
> Henrik Levkowetz has updated the idnit tool and AMS have updated the
> Internet-Draft submission tool to reflect the new requirements.  An
> update to the xml2rfc has been requested.
>
> Please review the "Legal Provisions Relating to IETF Documents" and
> RFC5378 to discover the new boilerplate text that is now required.
> Please also take action to update the tools you use for creating your
> documents.
>
> New submissions using either the old or the new boilerplate text will be
> accepted starting today, until 01h00 UTC on December 16th, 2008.  After
> this cutoff date, all new submissions will be required to use ONLY the
> new boilerplate text.  All submissions using old boilerplate text after
> the cutoff date will be rejected.
>
> Regards and FYI.
>
>
> Ed Juskevicius
> IETF Trust Chair
> edj@nortel.com
>
>
> p.s. - Don't be surprised if you see periodic reminders about this as we
> approach December 16th.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

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


From pce-bounces@ietf.org  Fri Nov 14 13:41:38 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BAA128C193;
	Fri, 14 Nov 2008 13:41:38 -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 3957F3A6A06;
	Fri, 14 Nov 2008 13:41:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5
	tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
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 2JJwBCx1G1i7; Fri, 14 Nov 2008 13:41:34 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id 61D1E3A6944;
	Fri, 14 Nov 2008 13:41:34 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id A1F0D175000; Fri, 14 Nov 2008 13:41:34 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081114214134.A1F0D175000@bosco.isi.edu>
Date: Fri, 14 Nov 2008 13:41:34 -0800 (PST)
Cc: pce@ietf.org, rfc-editor@rfc-editor.org
Subject: [Pce] RFC 5376 on Inter-AS Requirements for the Path Computation
	Element Communication Protocol (PCECP)
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org


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

        
        RFC 5376

        Title:      Inter-AS Requirements for the Path 
                    Computation Element Communication Protocol (PCECP) 
        Author:     N. Bitar, R. Zhang, K. Kumaki
        Status:     Informational
        Date:       November 2008
        Mailbox:    nabil.n.bitar@verizon.com, 
                    ke-kumaki@kddi.com, 
                    Raymond.zhang@bt.com
        Pages:      14
        Characters: 33114
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-interas-pcecp-reqs-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5376.txt

Multiprotocol Label Switching Traffic Engineered (MPLS TE) Label
Switched Paths (LSPs) may be established wholly within an Autonomous
System (AS) or may cross AS boundaries.

The Path Computation Element (PCE) is a component that is capable of
computing constrained paths for (G)MPLS TE LSPs.  The PCE Communication Protocol (PCECP) is defined to allow communication between Path Computation Clients (PCCs) and PCEs, as well as between PCEs.
The PCECP is used to request constrained paths and to supply computed
paths in response.  Generic requirements for the PCECP are set out in
"Path Computation Element (PCE) Communication Protocol Generic
Requirements", RFC 4657.  This document extends those requirements to
cover the use of PCECP in support of inter-AS MPLS TE.  This memo provides 
information for the Internet community.

This document is a product of the Path Computation Element Working Group of the IETF.


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

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


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


From pce-bounces@ietf.org  Fri Nov 14 14:33:26 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4260A3A6932;
	Fri, 14 Nov 2008 14:33:26 -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 37BE83A6932
	for <pce@core3.amsl.com>; Fri, 14 Nov 2008 14:33:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.489
X-Spam-Level: 
X-Spam-Status: No, score=-9.489 tagged_above=-999 required=5 tests=[AWL=1.109, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 4NxjYtob4EWs for <pce@core3.amsl.com>;
	Fri, 14 Nov 2008 14:33:23 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 4881D3A68F3
	for <pce@ietf.org>; Fri, 14 Nov 2008 14:33:23 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,606,1220227200"; d="scan'208";a="25725294"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 14 Nov 2008 22:33:22 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mAEMXMfS011166
	for <pce@ietf.org>; Fri, 14 Nov 2008 23:33:22 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mAEMXMGm005512
	for <pce@ietf.org>; Fri, 14 Nov 2008 22:33:22 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 14 Nov 2008 23:33:22 +0100
Received: from ams-jvasseur-8714.cisco.com ([10.55.201.133]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 14 Nov 2008 23:33:21 +0100
Message-Id: <897EA092-1F08-4989-A998-016CC0D634B6@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: pce@ietf.org
Mime-Version: 1.0 (Apple Message framework v926)
Date: Fri, 14 Nov 2008 23:33:21 +0100
X-Mailer: Apple Mail (2.926)
X-OriginalArrivalTime: 14 Nov 2008 22:33:21.0695 (UTC)
	FILETIME=[FFCE9AF0:01C946A8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=123; t=1226702002; x=1227566002;
	c=relaxed/simple; s=amsdkim1002;
	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=20Please |Sender:=20;
	bh=T8eiaCzDmnDwfYVbtL7e7pd+ljF50wz/nPHy9cr72Po=;
	b=skR/y+AtHpQYtBEfD6SNOavigDXH3dYaNvqowAVuA4O7vJekTvNIlxamzF
	bOOWLHlUEYSro137M8k4+GVDwYjrwlmgIBA5REUlQLZbE86GT2EFeI7NnmKy
	CjRpoFahZ6;
Authentication-Results: ams-dkim-1; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Subject: [Pce] Slides Please
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Dear all,

If you have a slot at the PCE WG Meeting next week, thanks to send  
your slides *today*.

Thanks.

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


From pce-bounces@ietf.org  Sun Nov 16 19:09: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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B35FB3A684C;
	Sun, 16 Nov 2008 19:09:31 -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 5DCB63A684C
	for <pce@core3.amsl.com>; Sun, 16 Nov 2008 19:09:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.246
X-Spam-Level: 
X-Spam-Status: No, score=-0.246 tagged_above=-999 required=5 tests=[AWL=2.352, 
	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 rqIR23P9rddO for <pce@core3.amsl.com>;
	Sun, 16 Nov 2008 19:09:29 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id 4B0F23A6358
	for <pce@ietf.org>; Sun, 16 Nov 2008 19:09:29 -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
	mAH39RTg014242 for <pce@ietf.org>; Mon, 17 Nov 2008 03:09:27 GMT
Received: from your029b8cecfe ([12.104.246.2]) (authenticated bits=0)
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	mAH39M6x014151 for <pce@ietf.org>; Mon, 17 Nov 2008 03:09:25 GMT
Message-ID: <3B009D5396D94E23963635252612B7AF@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Mon, 17 Nov 2008 03:09:18 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: [Pce] Fw: Last Call: draft-dasgupta-ccamp-path-comp-analysis
	(Performance Analysis of Inter-Domain Path Computation
	Methodologies) to Informational RFC
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Heads up
----- Original Message ----- 
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Sent: Sunday, November 16, 2008 10:54 PM
Subject: Last Call: draft-dasgupta-ccamp-path-comp-analysis (Performance 
Analysis of Inter-Domain Path Computation Methodologies) to Informational 
RFC


> The IESG has received a request from an individual submitter to consider
> the following document:
>
> - 'Performance Analysis of Inter-Domain Path Computation Methodologies '
>   <draft-dasgupta-ccamp-path-comp-analysis-02.txt> as an Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send substantive comments to the
> ietf@ietf.org mailing lists by 2008-12-14. Exceptionally,
> comments may be sent to iesg@ietf.org instead. In either case, please
> retain the beginning of the Subject line to allow automated sorting.
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-dasgupta-ccamp-path-comp-analysis-02.txt
>
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16050&rfc_flag=0
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> 

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


From pce-bounces@ietf.org  Mon Nov 17 05:00:04 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9FB933A677E;
	Mon, 17 Nov 2008 05:00:04 -0800 (PST)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id D412D3A6403; Mon, 17 Nov 2008 05:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081117130002.D412D3A6403@core3.amsl.com>
Date: Mon, 17 Nov 2008 05:00:01 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-path-key-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           : Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Key-Based Mechanism
	Author(s)       : R. Bradford, et al.
	Filename        : draft-ietf-pce-path-key-04.txt
	Pages           : 19
	Date            : 2008-11-17

Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
Traffic Engineering (TE) Label Switched Paths (LSPs) may be
computed by Path Computation Elements (PCEs). Where the TE LSP
crosses multiple domains, such as Autonomous Systems (ASes), the
path may be computed by multiple PCEs that cooperate, with each
responsible for computing a segment of the path. However, in some
cases (e.g., when ASes are administered by separate Service
Providers), it would break confidentiality rules for a PCE to
supply a path segment to a PCE in another domain, thus disclosing
AS-internal topology information. This issue may be circumvented
by returning a loose hop and by invoking a new path computation
from the domain boundary Label Switching Router (LSR) during TE
LSP setup as the signaling message enters the second domain, but
this technique has several issues including the problem of
maintaining path diversity.



Bradford, Vasseur and Farrel











[page 1]

draft-ietf-pce-path-key-04.txt








  November 2008

This document defines a mechanism to hide the contents of a
segment of a path, called the Confidential Path Segment (CPS). The
CPS may be replaced by a path-key that can be conveyed in the PCE
Communication Protocol (PCEP) and signaled within in a Resource
Reservation Protocol TE (RSVP-TE) explicit route object.

Conventions used in this document

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-path-key-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-path-key-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-11-17045759.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  Mon Nov 17 05:08:12 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9D0073A677E;
	Mon, 17 Nov 2008 05:08:12 -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 307613A677E
	for <pce@core3.amsl.com>; Mon, 17 Nov 2008 05:08:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.184
X-Spam-Level: 
X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5
	tests=[BAYES_40=-0.185, 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 HEYgnYRjC+5W for <pce@core3.amsl.com>;
	Mon, 17 Nov 2008 05:08:10 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 387673A6403
	for <pce@ietf.org>; Mon, 17 Nov 2008 05:08:10 -0800 (PST)
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
	mAHD804t014098 for <pce@ietf.org>; Mon, 17 Nov 2008 13:08:00 GMT
Received: from your029b8cecfe ([130.129.79.220]) (authenticated bits=0)
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	mAHD7vS6014045 for <pce@ietf.org>; Mon, 17 Nov 2008 13:08:00 GMT
Message-ID: <CB10B1028CF247ECA6E7D52C711318D1@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Mon, 17 Nov 2008 13:06:39 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: [Pce] Wondering about the new boilerplate?
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Were you wondering how to get the new boiler plate text right in your draft 
submissions?

You may find it easiest to crib from an existing draft by stealing the top 
and tail.

I think you will find it right in

http://www.ietf.org/internet-drafts/draft-ietf-pce-path-key-04.txt

Cheers,
Adrian 

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


From pce-bounces@ietf.org  Mon Nov 17 05:45:41 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6788D3A6936;
	Mon, 17 Nov 2008 05:45:41 -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 DB2773A6936
	for <pce@core3.amsl.com>; Mon, 17 Nov 2008 05:45:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.004
X-Spam-Level: 
X-Spam-Status: No, score=-1.004 tagged_above=-999 required=5 tests=[AWL=1.594, 
	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 X-8DfmZtWPL4 for <pce@core3.amsl.com>;
	Mon, 17 Nov 2008 05:45:40 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id D0DB53A679C
	for <pce@ietf.org>; Mon, 17 Nov 2008 05:45:39 -0800 (PST)
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
	mAHD86lj014165 for <pce@ietf.org>; Mon, 17 Nov 2008 13:08:06 GMT
Received: from your029b8cecfe ([130.129.79.220]) (authenticated bits=0)
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	mAHD7vS8014045 for <pce@ietf.org>; Mon, 17 Nov 2008 13:08:01 GMT
Message-ID: <DFBB90CB3972493ABCCBB050E5B1C71F@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Mon, 17 Nov 2008 13:07:52 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: [Pce] Fw:  I-D Action:draft-ietf-pce-path-key-04.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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This new version addresses review comments from GenArt.

The totality of the changes is...

> Section 2.1, paragraph 3:
OLD
   The PKS MUST be preceded by an ERO subobject that
   identifies the LSR that must expand the PKS, so the PKS will not
   be encountered in ERO processing until the LSR that can process
   it.
NEW
   The PKS MUST be preceded by an ERO subobject that
   identifies the LSR that must expand the PKS. This means that
   (following the rules for ERO processing set out in [RFC3209])
   the PKS will not be encountered in ERO processing until the ERO
   is being processed by the LSR that is capable of correctly handling
   the PKS.

> Section 4:
OLD
   The retrieval of the explicit path (the CPS) associated with a PKS
   by a PCC is no different than any other path computation request
   with the exception that the PCReq message MUST contain a PATH_KEY
   object and the Path Key bit of the RP object MUST the set.
NEW
   The retrieval of the explicit path (the CPS) associated with a PKS
   by a PCC is no different than any other path computation request
   with the exception that the PCReq message MUST contain a PATH_KEY
   object and the Path Key bit of the RP object MUST the set. On
   receipt of a PCRep containing a CPS, the requesting PCC SHOULD
   use insert the CPS into the ERO that it will signal, in accordance
   with local policy.

> Section 5, third bullet point in first list:
s/DNS attacks/DoS attacks/

> Section 6.1, paragraphs 2 and 3:
Para 2: yes. Should ref Section 2.1
Para 4: Should ref Section 2.1

> References:
Update references 

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


From pce-bounces@ietf.org  Mon Nov 17 08:15:04 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 45E553A6A6E;
	Mon, 17 Nov 2008 08:15:04 -0800 (PST)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id D4E7D3A6A56; Mon, 17 Nov 2008 08:15:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081117161501.D4E7D3A6A56@core3.amsl.com>
Date: Mon, 17 Nov 2008 08:15:01 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-path-key-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           : Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Key-Based Mechanism
	Author(s)       : R. Bradford, et al.
	Filename        : draft-ietf-pce-path-key-05.txt
	Pages           : 19
	Date            : 2008-11-17

Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
Traffic Engineering (TE) Label Switched Paths (LSPs) may be
computed by Path Computation Elements (PCEs). Where the TE LSP
crosses multiple domains, such as Autonomous Systems (ASes), the
path may be computed by multiple PCEs that cooperate, with each
responsible for computing a segment of the path. However, in some
cases (e.g., when ASes are administered by separate Service
Providers), it would break confidentiality rules for a PCE to
supply a path segment to a PCE in another domain, thus disclosing
AS-internal topology information. This issue may be circumvented
by returning a loose hop and by invoking a new path computation
from the domain boundary Label Switching Router (LSR) during TE
LSP setup as the signaling message enters the second domain, but
this technique has several issues including the problem of
maintaining path diversity.



Bradford, Vasseur and Farrel











[page 1]

draft-ietf-pce-path-key-05.txt








  November 2008

This document defines a mechanism to hide the contents of a
segment of a path, called the Confidential Path Segment (CPS). The
CPS may be replaced by a path-key that can be conveyed in the PCE
Communication Protocol (PCEP) and signaled within in a Resource
Reservation Protocol TE (RSVP-TE) explicit route object.

Conventions used in this document

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-path-key-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-path-key-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-11-17080924.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  Mon Nov 17 20:11:16 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F8E428C184;
	Mon, 17 Nov 2008 20:11:16 -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 CB7E928C184
	for <pce@core3.amsl.com>; Mon, 17 Nov 2008 20:11:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 U0PJG1SfC0mq for <pce@core3.amsl.com>;
	Mon, 17 Nov 2008 20:11:15 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 39CC928C180
	for <pce@ietf.org>; Mon, 17 Nov 2008 20:11:15 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,622,1220227200"; d="scan'208";a="106226718"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 18 Nov 2008 04:11:12 +0000
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 mAI4BCkh012499
	for <pce@ietf.org>; Mon, 17 Nov 2008 20:11:12 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id mAI4BChr006756
	for <pce@ietf.org>; Tue, 18 Nov 2008 04:11:12 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 17 Nov 2008 20:11:12 -0800
Received: from [130.129.76.145] ([10.21.79.253]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 17 Nov 2008 20:11:12 -0800
Message-Id: <70C14412-5516-4273-841E-9C0642AED614@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: pce@ietf.org
Mime-Version: 1.0 (Apple Message framework v926)
Date: Mon, 17 Nov 2008 22:11:11 -0600
X-Mailer: Apple Mail (2.926)
X-OriginalArrivalTime: 18 Nov 2008 04:11:12.0142 (UTC)
	FILETIME=[B12C9AE0:01C94933]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2; t=1226981472; x=1227845472; 
	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:=20All=20Slides=20Posted=20but=20=2211)=20PCE=20co
	mmunication=20protocol(PCEP)=20MIB=22 |Sender:=20;
	bh=frcCV1k9oG9oKj3dpUqdJg1PxRT2RSN/XKdLCPjaYaY=;
	b=VfHBumL1Ljz8DsjcNUhUJEr0/dcmPhPdH/XiwgQAfjmmtuVrGM8cEji/Xg
	uylJ4QbLWuJWeTNt0WH2IZ/oPmkmxi/+c4BnZKNNT7LGNLksc8MKp2N+R6Dr
	/EsvjZFm2g;
Authentication-Results: sj-dkim-3; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: [Pce] All Slides Posted but "11) PCE communication protocol(PCEP)
	MIB"
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


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


From pce-bounces@ietf.org  Tue Nov 18 13:45:33 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 07B843A6B1F;
	Tue, 18 Nov 2008 13:45:33 -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 D63493A6923
	for <pce@core3.amsl.com>; Tue, 18 Nov 2008 13:45:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 EhPDgolfI7f8 for <pce@core3.amsl.com>;
	Tue, 18 Nov 2008 13:45:31 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 05B8D3A6885
	for <pce@ietf.org>; Tue, 18 Nov 2008 13:45:29 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,627,1220227200"; d="scan'208";a="116942090"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 18 Nov 2008 21:45:28 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mAILjSiE014237; 
	Tue, 18 Nov 2008 13:45:28 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mAILjSGS025417;
	Tue, 18 Nov 2008 21:45:28 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Nov 2008 13:45:26 -0800
Received: from kkoushikwxp02 ([10.21.69.25]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Nov 2008 13:45:25 -0800
Message-ID: <02c001c949c6$e4fd5650$a358150a@cisco.com>
From: "Agrahara S Kiran Koushik" <kkoushik@cisco.com>
To: <pce@ietf.org>
References: <20081024104501.CA76E3A6A9E@core3.amsl.com>
Date: Tue, 18 Nov 2008 15:44:53 -0600
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.3350
X-OriginalArrivalTime: 18 Nov 2008 21:45:25.0495 (UTC)
	FILETIME=[F71C5070:01C949C6]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1780; t=1227044728;
	x=1227908728; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kkoushik@cisco.com;
	z=From:=20=22Agrahara=20S=20Kiran=20Koushik=22=20<kkoushik@c
	isco.com>
	|Subject:=20Re=3A=20[Pce]=20I-D=20Action=3Adraft-ietf-pce-d
	isc-mib-03.txt |Sender:=20;
	bh=5PgY3t7X73vHh+EJfH1i/6iOLGHev4R9XXnSDUYLVM4=;
	b=GFZtOIEP89tpFlX53U2aoXuUUyRmyg/pfWd9wrZHzF3RlKNMN0vy8gwf3h
	FhDrlYPbivbNwvVhyLn+hVRzBwOsuhlJkwLSjsBKzOvl0uOdaMMq+I38q3Ec
	2bGcu5jivnptA9yxgBo4wBMNLPjN6vr3t8/jtwKkb1byc0wBmkW0o=;
Authentication-Results: sj-dkim-1; header.From=kkoushik@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [Pce] I-D Action:draft-ietf-pce-disc-mib-03.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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi PCE wg,
To follow up my presentation at IETF wg today, can some of you
please review this updated draft and let me know of any
comments/suggestions?

Also, we have requested this to be a WG document. If you have
any reservations against this, please let us know.

Regards,
Kiran & Emile.

----- Original Message ----- 
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Cc: <pce@ietf.org>
Sent: Friday, October 24, 2008 4:45 AM
Subject: [Pce] I-D Action:draft-ietf-pce-disc-mib-03.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           : Definitions of Managed Objects for Path Computation 
> Element Discovery
> Author(s)       : E. Stephan
> Filename        : draft-ietf-pce-disc-mib-03.txt
> Pages           : 25
> Date            : 2008-10-24
>
> This memo defines a portion of the Management Information Base (MIB)
> for use with network management protocols in the Internet community.
> In particular, it describes objects used for managing Path
> Computation Elements Discovery.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pce-disc-mib-03.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  Wed Nov 19 03:04:52 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 890D43A6999;
	Wed, 19 Nov 2008 03:04:52 -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 A921D3A63D3
	for <pce@core3.amsl.com>; Wed, 19 Nov 2008 03:04:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.377
X-Spam-Level: 
X-Spam-Status: No, score=-6.377 tagged_above=-999 required=5 tests=[AWL=0.221, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 PxgQIriNVLCz for <pce@core3.amsl.com>;
	Wed, 19 Nov 2008 03:04:51 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 0412728C11E
	for <pce@ietf.org>; Wed, 19 Nov 2008 03:04:51 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,630,1220227200"; d="scan'208,217";a="53364583"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-5.cisco.com with ESMTP; 19 Nov 2008 11:04:50 +0000
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 mAJB4oAu000879
	for <pce@ietf.org>; Wed, 19 Nov 2008 03:04:50 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id mAJB4opG006508
	for <pce@ietf.org>; Wed, 19 Nov 2008 11:04:50 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Nov 2008 03:04:50 -0800
Received: from [130.129.76.145] ([10.21.67.188]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Nov 2008 03:04:49 -0800
Message-Id: <CE9D6E48-BAAE-4414-9A96-CBE4A5578617@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: pce@ietf.org
Mime-Version: 1.0 (Apple Message framework v926)
Date: Wed, 19 Nov 2008 05:04:48 -0600
X-Mailer: Apple Mail (2.926)
X-OriginalArrivalTime: 19 Nov 2008 11:04:49.0863 (UTC)
	FILETIME=[A41A0D70:01C94A36]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2399; t=1227092690;
	x=1227956690; 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:=20Adoption=20of=20two=20new=20Working=20Documents
	=20? |Sender:=20;
	bh=ztHnsglDR6DwFQiIMVuagU1I2Jkt285xmhHluzyDGyo=;
	b=SxKEUQD047pe9wGprjVpTYyLUWq6H1/pDexl7czqsSvdmpqN2oFIk5Gi4I
	hGKwMiWOTQsywJR04fMTXVngjv5slN1X4ct5F7zjcBffdUHteh4wzO+LOvb+
	TsoygG3cWe;
Authentication-Results: sj-dkim-3; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: [Pce] Adoption of two new Working Documents ?
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="===============1180601421=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org


--===============1180601421==
Content-Type: multipart/alternative; boundary=Apple-Mail-20--322614107


--Apple-Mail-20--322614107
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Dear WG,

Are you in favor or opposed to the adoption of the two following  
documents as PCE WG documents ?

draft-farrel-pce-vendor-constraints-02.txt
draft-kkoushik-pce-pcep-mib-02.txt
Thanks.

JP.
--Apple-Mail-20--322614107
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><font class=3D"Apple-style-span" =
face=3D"Arial">Dear WG,</font><div><font class=3D"Apple-style-span" =
face=3D"Arial"><br></font></div><div><font class=3D"Apple-style-span" =
face=3D"Arial">Are you in favor or opposed to the adoption of the two =
following documents as PCE WG documents ?</font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial"><br></font></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: Arial; white-space: =
pre-wrap; =
">draft-farrel-pce-vendor-constraints-02.txt</span></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: Times; font-size: 16px; =
"><pre style=3D"word-wrap: break-word; white-space: pre-wrap; "><font =
class=3D"Apple-style-span" face=3D"Arial" size=3D"4"><span =
class=3D"Apple-style-span" style=3D"font-size: =
14px;">draft-kkoushik-pce-pcep-mib-02.txt</span></font></pre><pre =
style=3D"word-wrap: break-word; white-space: pre-wrap; "><font =
class=3D"Apple-style-span" face=3D"Arial" size=3D"4"><span =
class=3D"Apple-style-span" style=3D"font-size: =
14px;"></span></font></pre><div><span class=3D"Apple-style-span" =
style=3D"white-space: pre-wrap;"><font class=3D"Apple-style-span" =
face=3D"Arial" size=3D"4"><span class=3D"Apple-style-span" =
style=3D"font-size: 14px;">Thanks.</span></font></span></div><div><span =
class=3D"Apple-style-span" style=3D"white-space: pre-wrap;"><font =
class=3D"Apple-style-span" face=3D"Arial" size=3D"4"><span =
class=3D"Apple-style-span" style=3D"font-size: =
14px;"><br></span></font></span></div><div><span =
class=3D"Apple-style-span" style=3D"white-space: pre-wrap;"><font =
class=3D"Apple-style-span" face=3D"Arial" size=3D"4"><span =
class=3D"Apple-style-span" style=3D"font-size: =
14px;">JP.</span></font></span></div></span></div></body></html>=

--Apple-Mail-20--322614107--

--===============1180601421==
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

--===============1180601421==--


From pce-bounces@ietf.org  Wed Nov 19 06:52: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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 11EAA28C133;
	Wed, 19 Nov 2008 06:52:31 -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 0337228C113
	for <pce@core3.amsl.com>; Wed, 19 Nov 2008 06:52:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=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 hsi2ZibH0hQr for <pce@core3.amsl.com>;
	Wed, 19 Nov 2008 06:52:29 -0800 (PST)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220])
	by core3.amsl.com (Postfix) with ESMTP id 1A12128C12E
	for <pce@ietf.org>; Wed, 19 Nov 2008 06:52:29 -0800 (PST)
Received: from huawei.com (usaga03-in [172.18.4.17])
	by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KAL00LZU5BF31@usaga03-in.huawei.com> for
	pce@ietf.org; Wed, 19 Nov 2008 08:52:27 -0600 (CST)
Received: from dan ([130.129.79.214])
	by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KAL004TN5BEAS@usaga03-in.huawei.com> for
	pce@ietf.org; Wed, 19 Nov 2008 08:52:27 -0600 (CST)
Date: Wed, 19 Nov 2008 22:52:24 +0800
From: Dan Li <danli@huawei.com>
To: JP Vasseur <jvasseur@cisco.com>, pce@ietf.org
Message-id: <C11429E4A72C419A8AC599E6C1D55584@dan>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-Priority: 3
X-MSMail-priority: Normal
References: <CE9D6E48-BAAE-4414-9A96-CBE4A5578617@cisco.com>
Subject: Re: [Pce] Adoption of two new Working Documents ?
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="===============1421327760=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1421327760==
Content-type: multipart/alternative;
 boundary="Boundary_(ID_wyH+tgkKLa58KsFAK280eA)"

This is a multi-part message in MIME format.

--Boundary_(ID_wyH+tgkKLa58KsFAK280eA)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

I support both.

Dan
  ----- Original Message ----- 
  From: JP Vasseur 
  To: pce@ietf.org 
  Sent: Wednesday, November 19, 2008 7:04 PM
  Subject: [Pce] Adoption of two new Working Documents ?


  Dear WG,


  Are you in favor or opposed to the adoption of the two following documents as PCE WG documents ?


  draft-farrel-pce-vendor-constraints-02.txt
draft-kkoushik-pce-pcep-mib-02.txtThanks.


  JP.


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


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

--Boundary_(ID_wyH+tgkKLa58KsFAK280eA)
Content-type: text/html; charset=iso-8859-1
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=iso-8859-1">
<META content="MSHTML 6.00.6000.16735" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY 
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space" 
bgColor=#ffffff>
<DIV><FONT face="Times New Roman">I support both.</FONT></DIV>
<DIV><FONT face="Times New Roman"></FONT>&nbsp;</DIV>
<DIV><FONT face="Times New Roman">Dan</FONT></DIV>
<BLOCKQUOTE 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV 
  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
  <A title=jvasseur@cisco.com href="mailto:jvasseur@cisco.com">JP Vasseur</A> 
  </DIV>
  <DIV style="FONT: 10pt arial"><B>To:</B> <A title=pce@ietf.org 
  href="mailto:pce@ietf.org">pce@ietf.org</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, November 19, 2008 7:04 
  PM</DIV>
  <DIV style="FONT: 10pt arial"><B>Subject:</B> [Pce] Adoption of two new 
  Working Documents ?</DIV>
  <DIV><BR></DIV><FONT class=Apple-style-span face=Arial>Dear WG,</FONT>
  <DIV><FONT class=Apple-style-span face=Arial><BR></FONT></DIV>
  <DIV><FONT class=Apple-style-span face=Arial>Are you in favor or opposed to 
  the adoption of the two following documents as PCE WG documents ?</FONT></DIV>
  <DIV><FONT class=Apple-style-span face=Arial><BR></FONT></DIV>
  <DIV><SPAN class=Apple-style-span 
  style="FONT-FAMILY: Arial">draft-farrel-pce-vendor-constraints-02.txt</SPAN></DIV>
  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 16px; FONT-FAMILY: Times"><PRE style="WORD-WRAP: break-word"><FONT class=Apple-style-span face=Arial size=4><SPAN class=Apple-style-span style="FONT-SIZE: 14px">draft-kkoushik-pce-pcep-mib-02.txt</SPAN></FONT></PRE><PRE style="WORD-WRAP: break-word"><FONT class=Apple-style-span face=Arial size=4><SPAN class=Apple-style-span style="FONT-SIZE: 14px"></SPAN></FONT></PRE>
  <DIV><SPAN class=Apple-style-span><FONT class=Apple-style-span face=Arial 
  size=4><SPAN class=Apple-style-span 
  style="FONT-SIZE: 14px">Thanks.</SPAN></FONT></SPAN></DIV>
  <DIV><SPAN class=Apple-style-span><FONT class=Apple-style-span face=Arial 
  size=4><SPAN class=Apple-style-span 
  style="FONT-SIZE: 14px"><BR></SPAN></FONT></SPAN></DIV>
  <DIV><SPAN class=Apple-style-span><FONT class=Apple-style-span face=Arial 
  size=4><SPAN class=Apple-style-span 
  style="FONT-SIZE: 14px">JP.</SPAN></FONT></SPAN></DIV></SPAN></DIV>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>Pce mailing 
  list<BR><A href="mailto:Pce@ietf.org">Pce@ietf.org</A><BR><A 
  href="https://www.ietf.org/mailman/listinfo/pce">https://www.ietf.org/mailman/listinfo/pce</A><BR></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_wyH+tgkKLa58KsFAK280eA)--

--===============1421327760==
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

--===============1421327760==--


From pce-bounces@ietf.org  Wed Nov 19 12:28:34 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 585423A6ABC;
	Wed, 19 Nov 2008 12:28:34 -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 1D99728C16B
	for <pce@core3.amsl.com>; Wed, 19 Nov 2008 12:28:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=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 0n63v-nrq3IX for <pce@core3.amsl.com>;
	Wed, 19 Nov 2008 12:28:32 -0800 (PST)
Received: from enfiets2.dataconnection.com (enfiets2.dataconnection.com
	[192.91.191.39])
	by core3.amsl.com (Postfix) with ESMTP id 2BF6D3A6ABC
	for <pce@ietf.org>; Wed, 19 Nov 2008 12:28:32 -0800 (PST)
Received: from ENFIMBOX1.ad.datcon.co.uk (172.18.10.27) by
	enfiets2.dataconnection.com (172.18.4.22) with Microsoft SMTP Server
	(TLS) id 8.1.311.2; Wed, 19 Nov 2008 20:29:17 +0000
Received: from ENFIMBOX1.ad.datcon.co.uk ([172.18.10.27]) by
	ENFIMBOX1.ad.datcon.co.uk ([172.18.10.27]) with mapi; Wed, 19 Nov 2008
	20:28:34 +0000
From: Nic Neate <Nic.Neate@dataconnection.com>
To: "qzhao@huawei.com" <qzhao@huawei.com>, "Mohamad.Chaitou@orange-ftgroup.com"
	<Mohamad.Chaitou@orange-ftgroup.com>
Date: Wed, 19 Nov 2008 20:28:33 +0000
Thread-Topic: Comment on draft-ietf-pce-pcep-p2mp-extensions
Thread-Index: AclKg6JZZBjAFX5eS4iUl6u4Ge7Nhw==
Message-ID: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B2B48@ENFIMBOX1.ad.datcon.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "Jeanlouis.Leroux@orange-ftgroup.com"
	<Jeanlouis.Leroux@orange-ftgroup.com>, "pce@ietf.org" <pce@ietf.org>,
	"daniel@olddog.co.uk" <daniel@olddog.co.uk>
Subject: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
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="===============1954152983=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

--===============1954152983==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B2B48ENFIMBOX1adda_"

--_000_11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B2B48ENFIMBOX1adda_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I have a suggestion for a small extension to the PCEP P2MP draft.

I believe the base PCEP specification currently has three options for calcu=
lating diverse protection paths: link diverse, node diverse and SRLG divers=
e (draft-ietf-pce-pcep section 7.13.2).

In P2MP, S2L sub-path diverse is another important case.  I think it would =
be good to allow the PCC to request computation of S2L sub-path diverse pro=
tection paths.

This is useful when doing 1+1 protection in a ring topology, for example.

Nic


--_000_11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B2B48ENFIMBOX1adda_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial, sans-serif" size=3D"2">
<div>Hi,</div>
<div>&nbsp;</div>
<div>I have a suggestion for a small extension to the PCEP P2MP draft.</div=
>
<div>&nbsp;</div>
<div>I believe the base PCEP specification currently has three options for =
calculating diverse protection paths: link diverse, node diverse and SRLG d=
iverse (draft-ietf-pce-pcep section 7.13.2).</div>
<div>&nbsp;</div>
<div>In P2MP, S2L sub-path diverse is another important case.&nbsp; I think=
 it would be good to allow the PCC to request computation of S2L sub-path d=
iverse protection paths.</div>
<div>&nbsp;</div>
<div>This is useful when doing 1&#43;1 protection in a ring topology, for e=
xample.</div>
<div>&nbsp;</div>
<div>Nic</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B2B48ENFIMBOX1adda_--

--===============1954152983==
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

--===============1954152983==--


From pce-bounces@ietf.org  Wed Nov 19 12:50:25 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E767228C21C;
	Wed, 19 Nov 2008 12:50:25 -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 4EDB928C21C
	for <pce@core3.amsl.com>; Wed, 19 Nov 2008 12:50:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.354
X-Spam-Level: 
X-Spam-Status: No, score=-2.354 tagged_above=-999 required=5 tests=[AWL=0.244, 
	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 o+YyJ64ymdm0 for <pce@core3.amsl.com>;
	Wed, 19 Nov 2008 12:50:23 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 4518228C1BB
	for <pce@ietf.org>; Wed, 19 Nov 2008 12:50:23 -0800 (PST)
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
	mAJKo7Aq023144; Wed, 19 Nov 2008 20:50:07 GMT
Received: from your029b8cecfe ([130.129.31.98]) (authenticated bits=0)
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	mAJKo59j023120; Wed, 19 Nov 2008 20:50:06 GMT
Message-ID: <76626FC9B3DE41E5AA7EB3813C817EB2@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Nic Neate" <Nic.Neate@dataconnection.com>, <qzhao@huawei.com>,
	<Mohamad.Chaitou@orange-ftgroup.com>
References: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B2B48@ENFIMBOX1.ad.datcon.co.uk>
Date: Wed, 19 Nov 2008 20:49:06 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: pce@ietf.org, Jeanlouis.Leroux@orange-ftgroup.com, daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Ah, that is an interesting and valid point, Nic.

And I think one might also consider "directional diversity" for your ring 
example.

A
----- Original Message ----- 
From: "Nic Neate" <Nic.Neate@dataconnection.com>
To: <qzhao@huawei.com>; <Mohamad.Chaitou@orange-ftgroup.com>
Cc: <Jeanlouis.Leroux@orange-ftgroup.com>; <pce@ietf.org>; 
<daniel@olddog.co.uk>
Sent: Wednesday, November 19, 2008 8:28 PM
Subject: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions


Hi,

I have a suggestion for a small extension to the PCEP P2MP draft.

I believe the base PCEP specification currently has three options for 
calculating diverse protection paths: link diverse, node diverse and SRLG 
diverse (draft-ietf-pce-pcep section 7.13.2).

In P2MP, S2L sub-path diverse is another important case.  I think it would 
be good to allow the PCC to request computation of S2L sub-path diverse 
protection paths.

This is useful when doing 1+1 protection in a ring topology, for example.

Nic




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


> _______________________________________________
> 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 Nov 19 16:05:11 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 097E928C1BC;
	Wed, 19 Nov 2008 16:05:11 -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 ADB1028C1B5
	for <pce@core3.amsl.com>; Wed, 19 Nov 2008 16:05:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=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 k7QdHNitCbGB for <pce@core3.amsl.com>;
	Wed, 19 Nov 2008 16:05:09 -0800 (PST)
Received: from pro46.abac.com (pro46.abac.com [66.226.64.47])
	by core3.amsl.com (Postfix) with ESMTP id F1DFB28C127
	for <pce@ietf.org>; Wed, 19 Nov 2008 16:05:08 -0800 (PST)
Received: from [172.19.160.212] ([198.202.202.20]) (authenticated bits=0)
	by pro46.abac.com (8.14.3/8.14.3) with ESMTP id mAK03c4k070299
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 19 Nov 2008 16:03:55 -0800 (PST)
	(envelope-from gregb@grotto-networking.com)
Message-ID: <4924A953.5020503@grotto-networking.com>
Date: Wed, 19 Nov 2008 18:03:31 -0600
From: Greg Bernstein <gregb@grotto-networking.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: JP Vasseur <jvasseur@cisco.com>
References: <CE9D6E48-BAAE-4414-9A96-CBE4A5578617@cisco.com>
In-Reply-To: <CE9D6E48-BAAE-4414-9A96-CBE4A5578617@cisco.com>
Cc: pce@ietf.org
Subject: Re: [Pce] Adoption of two new Working Documents ?
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="===============1090414703=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.
--===============1090414703==
Content-Type: multipart/alternative;
 boundary="------------000906010109030503000607"

This is a multi-part message in MIME format.
--------------000906010109030503000607
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Support both. (I'm a co-author on one).

Greg

JP Vasseur wrote:
> Dear WG,
>
> Are you in favor or opposed to the adoption of the two following 
> documents as PCE WG documents ?
>
> draft-farrel-pce-vendor-constraints-02.txt
> draft-kkoushik-pce-pcep-mib-02.txt
> Thanks.
>
> JP.
> ------------------------------------------------------------------------
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>   

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



--------------000906010109030503000607
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Support both. (I'm a co-author on one).<br>
<br>
Greg<br>
<br>
JP Vasseur wrote:
<blockquote cite="mid:CE9D6E48-BAAE-4414-9A96-CBE4A5578617@cisco.com"
 type="cite"><font class="Apple-style-span" face="Arial">Dear WG,</font>
  <div><font class="Apple-style-span" face="Arial"><br>
  </font></div>
  <div><font class="Apple-style-span" face="Arial">Are you in favor or
opposed to the adoption of the two following documents as PCE WG
documents ?</font></div>
  <div><font class="Apple-style-span" face="Arial"><br>
  </font></div>
  <div><span class="Apple-style-span" style="font-family: Arial;">draft-farrel-pce-vendor-constraints-02.txt</span></div>
  <div><span class="Apple-style-span"
 style="font-family: Times; font-size: 16px;">
  <pre style=""><font class="Apple-style-span" face="Arial" size="4"><span
 class="Apple-style-span" style="font-size: 14px;">draft-kkoushik-pce-pcep-mib-02.txt</span></font></pre>
  <pre style=""><font class="Apple-style-span" face="Arial" size="4"><span
 class="Apple-style-span" style="font-size: 14px;"></span></font></pre>
  <div><span class="Apple-style-span" style=""><font
 class="Apple-style-span" face="Arial" size="4"><span
 class="Apple-style-span" style="font-size: 14px;">Thanks.</span></font></span></div>
  <div><span class="Apple-style-span" style=""><font
 class="Apple-style-span" face="Arial" size="4"><span
 class="Apple-style-span" style="font-size: 14px;"><br>
  </span></font></span></div>
  <div><span class="Apple-style-span" style=""><font
 class="Apple-style-span" face="Arial" size="4"><span
 class="Apple-style-span" style="font-size: 14px;">JP.</span></font></span></div>
  </span></div>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Pce mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Pce@ietf.org">Pce@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/pce">https://www.ietf.org/mailman/listinfo/pce</a>
  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
===================================================
Dr Greg Bernstein, Grotto Networking (510) 573-2237

</pre>
</body>
</html>

--------------000906010109030503000607--

--===============1090414703==
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

--===============1090414703==--


From pce-bounces@ietf.org  Wed Nov 19 20:30:04 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 50D8828C0F8;
	Wed, 19 Nov 2008 20:30:04 -0800 (PST)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 00D453A68B2; Wed, 19 Nov 2008 20:30:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081120043002.00D453A68B2@core3.amsl.com>
Date: Wed, 19 Nov 2008 20:30:01 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-pcep-19.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-19.txt
	Pages           : 89
	Date            : 2008-11-19

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-19.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-19.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-11-19202804.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  Thu Nov 20 02:32:19 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BBD8B3A69FC;
	Thu, 20 Nov 2008 02:32:19 -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 8DB213A69F7
	for <pce@core3.amsl.com>; Thu, 20 Nov 2008 02:32:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=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 UwDkzlQqZ8zQ for <pce@core3.amsl.com>;
	Thu, 20 Nov 2008 02:32:16 -0800 (PST)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65])
	by core3.amsl.com (Postfix) with ESMTP id A5DC43A69B6
	for <pce@ietf.org>; Thu, 20 Nov 2008 02:32:15 -0800 (PST)
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KAM00LSTNXMDE@szxga02-in.huawei.com> for
	pce@ietf.org; Thu, 20 Nov 2008 18:32:10 +0800 (CST)
Received: from huawei.com ([172.24.1.12])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KAM00DO0NXMO9@szxga02-in.huawei.com> for
	pce@ietf.org; Thu, 20 Nov 2008 18:32:10 +0800 (CST)
Received: from SSK1548 ([10.18.24.148])
	by szxml05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KAM00K4DNXJYB@szxml05-in.huawei.com> for
	pce@ietf.org; Thu, 20 Nov 2008 18:32:10 +0800 (CST)
Date: Thu, 20 Nov 2008 16:02:06 +0530
From: "S.SenthilKumar" <senthilKumars@huawei.com>
To: pce@ietf.org
Message-id: <000001c94afb$3d2c4d10$9418120a@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: AclK8l6OvjZU3gexTFy7XOgdbU4dzg==
Subject: [Pce] Reg LSPA Object
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="===============1938759440=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1938759440==
Content-type: multipart/alternative;
 boundary="Boundary_(ID_2+W+JyjFQmfZVNyuiOrnfA)"

This is a multi-part message in MIME format.

--Boundary_(ID_2+W+JyjFQmfZVNyuiOrnfA)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Dear All

 

I like to understand more about LSPA Object defined in PCEP.

 

1. What will be content of the following fields?

*	Exclude-any                             
*	Include-any
*	Include-all

2. More information can be added into PCEP RFC

 

3. What is the use-case of this object

4. If more than one request is present in a single PCReq message, How LSPA
object is associated with a single request present in the message?

 

General comment:  PCEP RFC has lot of Typo errors and the same can be
rectified. I will also review and provide my comments in the mean time.

 

Thanking you,

 

Best regards,

S.SenthilKumar

 

 

7.11.  LSPA Object

 

   The LSPA object is optional and specifies various TE LSP attributes

   to be taken into account by the PCE during path computation.  The

   LSPA (LSP Attributes) object can be carried within a PCReq message,

   or a PCRep message in case of unsuccessful path computation (in this

   case, the PCRep message also contains a NO-PATH object and the LSPA

   object is used to indicate the set of constraints that could not be

   satisfied).  Most of the fields of the LSPA object are identical to

   the fields of the SESSION-ATTRIBUTE (C-Type = 7) object defined in

   [RFC3209] and [RFC4090].  When absent from the PCReq message, this

   means that the Setup and Holding priorities are equal to 0, and there

   are no affinity constraints.

 

   LSPA Object-Class is to be assigned by IANA (recommended value=9)

 

   LSPA Object-Types is to be assigned by IANA (recommended value=1)

 

   The format of the LSPA object body is:

 

    0                   1                   2                   3

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   |                       Exclude-any                             |

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   |                       Include-any                             |

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   |                       Include-all                             |

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   |  Setup Prio   |  Holding Prio |     Flags   |L|   Reserved    |

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   |                                                               |

   //                     Optional TLVs                           //

   |                                                               |

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


--Boundary_(ID_2+W+JyjFQmfZVNyuiOrnfA)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:KaiTi_GB2312;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@SimHei";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@KaiTi_GB2312";}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";}
h1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:21.55pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-21.55pt;
	page-break-after:avoid;
	mso-list:l11 level1 lfo35;
	font-size:16.0pt;
	font-family:Arial;
	font-weight:bold;}
h2
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.4in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.4in;
	page-break-after:avoid;
	mso-list:l11 level2 lfo35;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
h3
	{margin-top:13.0pt;
	margin-right:0in;
	margin-bottom:13.0pt;
	margin-left:.5in;
	mso-para-margin-top:13.0pt;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:13.0pt;
	mso-para-margin-left:2.0gd;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.5in;
	line-height:173%;
	page-break-after:avoid;
	mso-list:l11 level3 lfo35;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	layout-grid-mode:char;
	font-size:9.0pt;
	font-family:Arial;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:8.0pt;
	font-family:Tahoma;}
p.Table, li.Table, div.Table
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	mso-para-margin-top:1.0gd;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:0in;
	mso-para-margin-bottom:.0001pt;
	text-align:center;
	text-indent:0in;
	mso-list:l8 level9 lfo5;
	font-size:9.0pt;
	font-family:Arial;}
p.TableText, li.TableText, div.TableText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Arial;}
p.TableHeader, li.TableHeader, div.TableHeader
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:10.5pt;
	font-family:Arial;
	font-weight:bold;}
p.FigureStyle, li.FigureStyle, div.FigureStyle
	{margin-top:4.0pt;
	margin-right:0in;
	margin-bottom:4.0pt;
	margin-left:0in;
	text-align:center;
	line-height:150%;
	page-break-after:avoid;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";}
p.DocumentTitle, li.DocumentTitle, div.DocumentTitle
	{margin-top:15.0pt;
	margin-right:0in;
	margin-bottom:15.0pt;
	margin-left:0in;
	text-align:center;
	line-height:150%;
	text-autospace:none;
	font-size:18.0pt;
	font-family:Arial;}
p.NotesHeader, li.NotesHeader, div.NotesHeader
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0in;
	font-size:9.0pt;
	font-family:Arial;}
p.NotesText, li.NotesText, div.NotesText
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:.25in;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0in;
	font-size:9.0pt;
	font-family:Arial;}
p.CompilingAdvice, li.CompilingAdvice, div.CompilingAdvice
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:Arial;
	color:blue;
	font-style:italic;}
p.Figure, li.Figure, div.Figure
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	text-indent:0in;
	line-height:150%;
	mso-list:l8 level8 lfo5;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";}
span.EmailStyle30
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
 /* Page Definitions */
 @page
	{mso-endnote-separator:url("cid:header.htm\@01C94B20.78422FD0") es;
	mso-endnote-continuation-separator:url("cid:header.htm\@01C94B20.78422FD0") ecs;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.0in 1.0in 1.0in;
	mso-footer:url("cid:header.htm\@01C94B20.78422FD0") f1;
	layout-grid:15.6pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:171800355;
	mso-list-template-ids:-1278163850;}
@list l0:level1
	{mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l0:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l0:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l0:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l0:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l0:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l0:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l0:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l0:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l1
	{mso-list-id:191647984;
	mso-list-template-ids:345692754;}
@list l1:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:64.15pt;
	mso-level-number-position:left;
	margin-left:64.15pt;
	text-indent:-.3in;}
@list l1:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:71.35pt;
	mso-level-number-position:left;
	margin-left:71.35pt;
	text-indent:-.4in;}
@list l1:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:78.55pt;
	mso-level-number-position:left;
	margin-left:78.55pt;
	text-indent:-.5in;}
@list l1:level4
	{mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:114.55pt;
	mso-level-number-position:left;
	margin-left:114.55pt;
	text-indent:-1.0in;}
@list l1:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:121.75pt;
	mso-level-number-position:left;
	margin-left:121.75pt;
	text-indent:-1.1in;}
@list l2
	{mso-list-id:279995038;
	mso-list-type:hybrid;
	mso-list-template-ids:276302512 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l3
	{mso-list-id:541409008;
	mso-list-template-ids:-249166292;}
@list l3:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l3:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l3:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l3:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l3:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l3:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l3:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l3:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l3:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l4
	{mso-list-id:731736200;
	mso-list-template-ids:67698717;}
@list l4:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l4:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:57.25pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l4:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:96.55pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l4:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:153.8pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l4:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:193.05pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l4:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:232.3pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l4:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:271.55pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l4:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:310.8pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l4:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:350.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l5
	{mso-list-id:818422186;
	mso-list-template-ids:1344984950;}
@list l5:level1
	{mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l5:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l5:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l5:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l5:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l5:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l5:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l5:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l5:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l6
	{mso-list-id:838886720;
	mso-list-template-ids:-819953982;}
@list l6:level1
	{mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;
	mso-ansi-font-size:18.0pt;
	mso-bidi-font-size:18.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;
	mso-ansi-font-size:15.0pt;
	mso-bidi-font-size:15.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;
	mso-ansi-font-size:12.0pt;
	mso-bidi-font-size:12.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7
	{mso-list-id:942373150;
	mso-list-template-ids:67698717;}
@list l7:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l7:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:57.25pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l7:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:96.55pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l7:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:135.8pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l7:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:175.05pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l7:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:214.3pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l7:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:253.55pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l7:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:292.8pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l7:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:332.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l8
	{mso-list-id:1123964682;
	mso-list-template-ids:548200814;}
@list l8:level1
	{mso-level-suffix:none;
	mso-level-text:"%1  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:0in;
	mso-ansi-font-size:18.0pt;
	mso-bidi-font-size:18.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l8:level2
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:15.0pt;
	mso-bidi-font-size:15.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l8:level3
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:12.0pt;
	mso-bidi-font-size:12.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l8:level4
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l8:level5
	{mso-level-tab-stop:92.7pt;
	mso-level-number-position:left;
	margin-left:92.7pt;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l8:level6
	{mso-level-text:"%6\)";
	mso-level-tab-stop:92.7pt;
	mso-level-number-position:left;
	margin-left:92.7pt;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l8:level7
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:92.7pt;
	mso-level-number-position:left;
	margin-left:92.7pt;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l8:level8
	{mso-level-reset-level:level1;
	mso-level-style-link:Figure;
	mso-level-suffix:space;
	mso-level-text:Figure%8;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l8:level9
	{mso-level-reset-level:level1;
	mso-level-style-link:Table;
	mso-level-suffix:space;
	mso-level-text:Table%9;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l9
	{mso-list-id:1380013528;
	mso-list-template-ids:-1435872280;}
@list l9:level1
	{mso-level-number-format:none;
	mso-level-text:"\9644\5F55A ";
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l9:level2
	{mso-level-text:"A\.%2";
	mso-level-tab-stop:49.6pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l9:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l9:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:99.2pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l9:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:127.55pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l9:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:163.0pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l9:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:191.35pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l9:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:219.7pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l9:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:255.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l10
	{mso-list-id:1425803385;
	mso-list-template-ids:67698717;}
@list l10:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l10:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:57.25pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l10:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:96.55pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l10:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:153.8pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l10:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:193.05pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l10:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:232.3pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l10:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:271.55pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l10:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:310.8pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l10:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:350.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l11
	{mso-list-id:1666475049;
	mso-list-template-ids:-28945502;}
@list l11:level1
	{mso-level-style-link:"Heading 1";
	mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l11:level2
	{mso-level-style-link:"Heading 2";
	mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l11:level3
	{mso-level-style-link:"Heading 3";
	mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l11:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l11:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l11:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l11:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l11:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l11:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l12
	{mso-list-id:1916042858;
	mso-list-template-ids:-648263936;}
@list l12:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l12:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l12:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l12:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l12:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l12:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l12:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l12:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l12:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l13
	{mso-list-id:2114861838;
	mso-list-template-ids:-433129230;}
@list l13:level1
	{mso-level-number-format:none;
	mso-level-text:"\9644\5F55A ";
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l13:level2
	{mso-level-text:"A\.%2";
	mso-level-tab-stop:49.6pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l13:level3
	{mso-level-text:"%1A\.%2\.%3";
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l13:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:99.2pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l13:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:127.55pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l13:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:163.0pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l13:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:191.35pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l13:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:219.7pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l13:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:255.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="3074" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="2" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple style='text-justify-trim:punctuation'>

<div class=Section1 style='layout-grid:15.6pt'>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>Dear All<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>I like to
understand more about LSPA Object defined in PCEP.<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>1. What will be content
of the following fields?<o:p></o:p></span></font></p>

<ul style='margin-top:0in' type=disc>
 <li class=MsoNormal style='margin-left:.5in;mso-list:l2 level1 lfo38'><font
     size=2 face=Arial><span style='font-size:10.0pt;line-height:150%;
     font-family:Arial'>Exclude-any&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></li>
 <li class=MsoNormal style='margin-left:.5in;mso-list:l2 level1 lfo38'><font
     size=2 face=Arial><span style='font-size:10.0pt;line-height:150%;
     font-family:Arial'>Include-any<o:p></o:p></span></font></li>
 <li class=MsoNormal style='margin-left:.5in;mso-list:l2 level1 lfo38'><font
     size=2 face=Arial><span style='font-size:10.0pt;line-height:150%;
     font-family:Arial'>Include-all<o:p></o:p></span></font></li>
</ul>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>2. More information
can be added into PCEP RFC<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>3. What is the
use-case of this object<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>4. If more than one
request is present in a single PCReq message, How LSPA object is associated
with a single request present in the message?<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>General comment:&nbsp; PCEP
RFC has lot of Typo errors and the same can be rectified. I will also review
and provide my comments in the mean time.<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoAutoSig><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'>Thanking you,<o:p></o:p></span></font></p>

<p class=MsoAutoSig><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoAutoSig><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'>Best regards,<o:p></o:p></span></font></p>

<p class=MsoAutoSig><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>S.SenthilKumar</span><o:p></o:p></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>7.11.&nbsp; LSPA Object<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; The LSPA object
is optional and specifies various TE LSP attributes<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; to be taken into
account by the PCE during path computation.&nbsp; The<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; LSPA (LSP
Attributes) object can be carried within a PCReq message,<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; or a PCRep
message in case of unsuccessful path computation (in this<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; case, the PCRep
message also contains a NO-PATH object and the LSPA<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; object is used
to indicate the set of constraints that could not be<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; satisfied).&nbsp;
Most of the fields of the LSPA object are identical to<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; the fields of
the SESSION-ATTRIBUTE (C-Type = 7) object defined in<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; [RFC3209] and
[RFC4090].&nbsp; When absent from the PCReq message, this<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; means that the
Setup and Holding priorities are equal to 0, and there<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; are no affinity
constraints.<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; LSPA
Object-Class is to be assigned by IANA (recommended value=9)<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; LSPA
Object-Types is to be assigned by IANA (recommended value=1)<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp; The format of
the LSPA object body is:<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp;&nbsp; </span></font><font
size=2 face="Courier New"><span style='font-size:10.0pt;line-height:150%;
font-family:"Courier New"'>0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp;&nbsp; 0 1 2 3
4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp;
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Exclude-any&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp;
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Include-any&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp;
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Include-all&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp;
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp; |&nbsp; Setup
Prio&nbsp;&nbsp; |&nbsp; Holding Prio |&nbsp;&nbsp;&nbsp;&nbsp; Flags&nbsp;&nbsp; |L|&nbsp;&nbsp; Reserved&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp;
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp;
//&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Optional TLVs&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; //<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;line-height:150%;font-family:"Courier New"'>&nbsp;&nbsp;
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:p></span></font></p>

</div>

</body>

</html>

--Boundary_(ID_2+W+JyjFQmfZVNyuiOrnfA)--

--===============1938759440==
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

--===============1938759440==--


From pce-bounces@ietf.org  Thu Nov 20 04:17:07 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 991CA3A68B6;
	Thu, 20 Nov 2008 04:17:07 -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 6EF7E3A68B6
	for <pce@core3.amsl.com>; Thu, 20 Nov 2008 04:17:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.541
X-Spam-Level: 
X-Spam-Status: No, score=-6.541 tagged_above=-999 required=5 tests=[AWL=0.057, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 DZycVnlBr24h for <pce@core3.amsl.com>;
	Thu, 20 Nov 2008 04:17:05 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 1825A3A63D2
	for <pce@ietf.org>; Thu, 20 Nov 2008 04:17:05 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,639,1220227200"; 
	d="scan'208,217";a="107529905"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 20 Nov 2008 12:17:02 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id mAKCH2Gg006105; 
	Thu, 20 Nov 2008 04:17:02 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id mAKCH2BL023067;
	Thu, 20 Nov 2008 12:17:02 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Nov 2008 04:17:01 -0800
Received: from [130.129.76.145] ([10.21.69.241]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Nov 2008 04:17:00 -0800
Message-Id: <A071FDB2-E05C-42EF-97C7-88502A163BD2@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: "S.SenthilKumar" <senthilKumars@huawei.com>
In-Reply-To: <000001c94afb$3d2c4d10$9418120a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Thu, 20 Nov 2008 06:16:59 -0600
References: <000001c94afb$3d2c4d10$9418120a@china.huawei.com>
X-Mailer: Apple Mail (2.926)
X-OriginalArrivalTime: 20 Nov 2008 12:17:00.0820 (UTC)
	FILETIME=[E3F76540:01C94B09]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=35681; t=1227183422;
	x=1228047422; 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]=20Reg=20LSPA=20Object |Sender:=20;
	bh=JprbOpzKUiLWOe+lglfX/MIg3LEncC25YvGNUUi+rlc=;
	b=p69EKQ/VgUKYOO+Vddc7LqeZyuO3rihlMhXUddYRDArplLKAYC0zs+Wuxf
	SKj8J+ebt54g90Yk4gbtlOJpNNTirqlbI4LDje/Ei9h91j0alj+HAjTBj+0Z
	tH52U470Tn;
Authentication-Results: sj-dkim-3; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: pce@ietf.org
Subject: Re: [Pce] Reg LSPA Object
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="===============1710036962=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org


--===============1710036962==
Content-Type: multipart/alternative; boundary=Apple-Mail-13--231883290


--Apple-Mail-13--231883290
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Hi,

On Nov 20, 2008, at 4:32 AM, S.SenthilKumar wrote:

> Dear All
>
> I like to understand more about LSPA Object defined in PCEP.
>
> 1. What will be content of the following fields?
> Exclude-any
> Include-any
> Include-all
> 2. More information can be added into PCEP RFC
>

The text is quite clear:

Most of the fields of the LSPA object are identical to
>    the fields of the SESSION-ATTRIBUTE (C-Type = 7) object defined in
>    [RFC3209] and [RFC4090].

So you may want to red 3209 and 4090 for more details on these fields.

> 3. What is the use-case of this object

To express constraints.

> 4. If more than one request is present in a single PCReq message,  
> How LSPA object is associated with a single request present in the  
> message?
>

Please look at the BNF:

The format of a PCReq message is as follows:
    <PCReq Message>::= <Common Header>
                       [<SVEC-list>]
                       <request-list>

    where:
       <svec-list>::=<SVEC>[<svec-list>]
       <request-list>::=<request>[<request-list>]

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

    <metric-list>::=<METRIC>[<metric-list>]

What you want to do above is thus supported.

> General comment:  PCEP RFC has lot of Typo errors and the same can  
> be rectified. I will also review and provide my comments in the mean  
> time.

Most of them have been fixed. The RFC editor will correct the  
remaining ones if any,

Thanks.

JP.

>
> Thanking you,
>
> Best regards,
> S.SenthilKumar
>
>
> 7.11.  LSPA Object
>
>    The LSPA object is optional and specifies various TE LSP attributes
>    to be taken into account by the PCE during path computation.  The
>    LSPA (LSP Attributes) object can be carried within a PCReq message,
>    or a PCRep message in case of unsuccessful path computation (in  
> this
>    case, the PCRep message also contains a NO-PATH object and the LSPA
>    object is used to indicate the set of constraints that could not be
>    satisfied).  Most of the fields of the LSPA object are identical to
>    the fields of the SESSION-ATTRIBUTE (C-Type = 7) object defined in
>    [RFC3209] and [RFC4090].  When absent from the PCReq message, this
>    means that the Setup and Holding priorities are equal to 0, and  
> there
>    are no affinity constraints.
>
>    LSPA Object-Class is to be assigned by IANA (recommended value=9)
>
>    LSPA Object-Types is to be assigned by IANA (recommended value=1)
>
>    The format of the LSPA object body is:
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                       Exclude-any                             |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                       Include-any                             |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                       Include-all                             |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |  Setup Prio   |  Holding Prio |     Flags   |L|   Reserved    |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                                                               |
>    //                     Optional TLVs                           //
>    |                                                               |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce


--Apple-Mail-13--231883290
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Hi,<div><br><div><div>On Nov =
20, 2008, at 4:32 AM, S.SenthilKumar wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div lang=3D"EN-US" link=3D"blue" =
vlink=3D"purple"><div class=3D"Section1"><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">Dear =
All<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">I like to understand more about =
LSPA Object defined in PCEP.<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 10pt; =
margin-bottom: 0.0001pt; line-height: 150%; font-size: 10.5pt; =
font-family: 'Times New Roman'; "><font size=3D"2" face=3D"Arial"><span =
style=3D"font-size: 10pt; line-height: 150%; font-family: Arial; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">1. What will be content of the =
following fields?<o:p></o:p></span></font></div><ul type=3D"disc" =
style=3D"margin-top: 0in; margin-bottom: 0in; "><li class=3D"MsoNormal" =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 10pt; =
margin-bottom: 0.0001pt; line-height: 150%; font-size: 10.5pt; =
font-family: 'Times New Roman'; "><font size=3D"2" face=3D"Arial"><span =
style=3D"font-size: 10pt; line-height: 150%; font-family: Arial; =
">Exclude-any&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></span></font></li><li =
class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 10pt; margin-bottom: 0.0001pt; line-height: 150%; =
font-size: 10.5pt; font-family: 'Times New Roman'; "><font size=3D"2" =
face=3D"Arial"><span style=3D"font-size: 10pt; line-height: 150%; =
font-family: Arial; ">Include-any<o:p></o:p></span></font></li><li =
class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 10pt; margin-bottom: 0.0001pt; line-height: 150%; =
font-size: 10.5pt; font-family: 'Times New Roman'; "><font size=3D"2" =
face=3D"Arial"><span style=3D"font-size: 10pt; line-height: 150%; =
font-family: Arial; ">Include-all<o:p></o:p></span></font></li></ul><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 10pt; =
margin-bottom: 0.0001pt; line-height: 150%; font-size: 10.5pt; =
font-family: 'Times New Roman'; "><font size=3D"2" face=3D"Arial"><span =
style=3D"font-size: 10pt; line-height: 150%; font-family: Arial; ">2. =
More information can be added into PCEP =
RFC<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; =
"><o:p>&nbsp;</o:p></span></font></div></div></div></span></blockquote><di=
v><br></div><div>The text is quite clear:&nbsp;<span =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: 13px; =
line-height: 19px; "></span></div><div><br></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: 13px; =
line-height: 19px; ">Most of the fields of the LSPA object are identical =
to</span></div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"color: rgb(0, 0, 0); "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; the fields of the =
SESSION-ATTRIBUTE (C-Type =3D 7) object defined =
in<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; [RFC3209] and =
[RFC4090].</span></font></div></span></blockquote><div><br></div><div>So =
you may want to red 3209 and 4090 for more details on these =
fields.</div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div lang=3D"EN-US" link=3D"blue" =
vlink=3D"purple"><div class=3D"Section1"><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">3. What is the use-case of this =
object</span></font></div></div></div></span></blockquote><div><br></div><=
div>To express constraints.</div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div lang=3D"EN-US" link=3D"blue" =
vlink=3D"purple"><div class=3D"Section1"><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; =
"><o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">4. If more than one request is =
present in a single PCReq message, How LSPA object is associated with a =
single request present in the =
message?<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; =
"><o:p>&nbsp;</o:p></span></font></div></div></div></span></blockquote><di=
v><br></div><div>Please look at the =
BNF:</div><div><br></div><div><div>The format of a PCReq message is as =
follows:</div><div>&nbsp;&nbsp; &lt;PCReq Message>::=3D &lt;Common =
Header></div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;[&lt;SVEC-list>]</div><div>&nbsp;&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&lt;request-list></div><div><br></div><div>&nbsp;&nbsp; =
where:</div><div>&nbsp;&nbsp; &nbsp; =
&nbsp;&lt;svec-list>::=3D&lt;SVEC>[&lt;svec-list>]</div><div>&nbsp;&nbsp; =
&nbsp; =
&nbsp;&lt;request-list>::=3D&lt;request>[&lt;request-list>]</div><div><br>=
</div><div>&nbsp;&nbsp; &nbsp; &nbsp;&lt;request>::=3D =
&lt;RP></div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &lt;END-POINTS></div><div>&nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
[&lt;LSPA>]</div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; [&lt;BANDWIDTH>]</div><div>&nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
[&lt;metric-list>]</div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; =
[&lt;RRO>[&lt;BANDWIDTH>]]</div><div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; [&lt;IRO>]</div><div>&nbsp;&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
[&lt;LOAD-BALANCING>]</div><div>&nbsp;&nbsp; =
where:</div><div><br></div><div>&nbsp;&nbsp; =
&lt;metric-list>::=3D&lt;METRIC>[&lt;metric-list>]</div><div><br></div><di=
v>What you want to do above is thus =
supported.</div></div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div lang=3D"EN-US" link=3D"blue" =
vlink=3D"purple"><div class=3D"Section1"><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">General comment:&nbsp; PCEP RFC =
has lot of Typo errors and the same can be rectified. I will also review =
and provide my comments in the mean =
time.<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; =
"><o:p></o:p></span></font></div></div></div></span></blockquote><div><br>=
</div><div>Most of them have been fixed. The RFC editor will correct the =
remaining ones if =
any,</div><div><br></div><div>Thanks.</div><div><br></div><div>JP.</div><b=
r><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div lang=3D"EN-US" link=3D"blue" =
vlink=3D"purple"><div class=3D"Section1"><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"2" color=3D"black" =
face=3D"Arial"><span style=3D"font-size: 10pt; font-family: Arial; =
color: black; ">Thanking you,<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman'; "><font size=3D"2" color=3D"black" face=3D"Arial"><span =
style=3D"font-size: 10pt; font-family: Arial; color: black; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman'; "><font size=3D"2" color=3D"black" =
face=3D"Arial"><span style=3D"font-size: 10pt; font-family: Arial; =
color: black; ">Best regards,<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman'; "><font size=3D"3" face=3D"Times New Roman"><span =
style=3D"font-size: 12pt; =
">S.SenthilKumar</span><o:p></o:p></font></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">7.11.&nbsp; LSPA =
Object<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; The LSPA object is =
optional and specifies various TE LSP =
attributes<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; to be taken into =
account by the PCE during path computation.&nbsp; =
The<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; LSPA (LSP =
Attributes) object can be carried within a PCReq =
message,<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; or a PCRep message =
in case of unsuccessful path computation (in =
this<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; case, the PCRep =
message also contains a NO-PATH object and the =
LSPA<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; object is used to =
indicate the set of constraints that could not =
be<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; satisfied).&nbsp; =
Most of the fields of the LSPA object are identical =
to<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; the fields of the =
SESSION-ATTRIBUTE (C-Type =3D 7) object defined =
in<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; [RFC3209] and =
[RFC4090].&nbsp; When absent from the PCReq message, =
this<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; means that the =
Setup and Holding priorities are equal to 0, and =
there<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; are no affinity =
constraints.<o:p></o:p></span></font></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; LSPA Object-Class =
is to be assigned by IANA (recommended =
value=3D9)<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; LSPA Object-Types =
is to be assigned by IANA (recommended =
value=3D1)<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp; The format of the =
LSPA object body is:<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 10pt; =
margin-bottom: 0.0001pt; line-height: 150%; font-size: 10.5pt; =
font-family: 'Times New Roman'; "><font size=3D"2" face=3D"Arial"><span =
style=3D"font-size: 10pt; line-height: 150%; font-family: Arial; =
"><o:p>&nbsp;</o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Arial"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: Arial; ">&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></font><font =
size=3D"2" face=3D"Courier New"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: 'Courier New'; =
">0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 10pt; =
margin-bottom: 0.0001pt; line-height: 150%; font-size: 10.5pt; =
font-family: 'Times New Roman'; "><font size=3D"2" face=3D"Courier =
New"><span style=3D"font-size: 10pt; line-height: 150%; font-family: =
'Courier New'; ">&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 =
8 9 0 1 2 3 4 5 6 7 8 9 0 1<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 10pt; =
margin-bottom: 0.0001pt; line-height: 150%; font-size: 10.5pt; =
font-family: 'Times New Roman'; "><font size=3D"2" face=3D"Courier =
New"><span style=3D"font-size: 10pt; line-height: 150%; font-family: =
'Courier New'; ">&nbsp;&nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:=
p></span></font></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 10pt; margin-bottom: 0.0001pt; line-height: 150%; =
font-size: 10.5pt; font-family: 'Times New Roman'; "><font size=3D"2" =
face=3D"Courier New"><span style=3D"font-size: 10pt; line-height: 150%; =
font-family: 'Courier New'; ">&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Exclude-any&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 10pt; =
margin-bottom: 0.0001pt; line-height: 150%; font-size: 10.5pt; =
font-family: 'Times New Roman'; "><font size=3D"2" face=3D"Courier =
New"><span style=3D"font-size: 10pt; line-height: 150%; font-family: =
'Courier New'; ">&nbsp;&nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:=
p></span></font></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 10pt; margin-bottom: 0.0001pt; line-height: 150%; =
font-size: 10.5pt; font-family: 'Times New Roman'; "><font size=3D"2" =
face=3D"Courier New"><span style=3D"font-size: 10pt; line-height: 150%; =
font-family: 'Courier New'; ">&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Include-any&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 10pt; =
margin-bottom: 0.0001pt; line-height: 150%; font-size: 10.5pt; =
font-family: 'Times New Roman'; "><font size=3D"2" face=3D"Courier =
New"><span style=3D"font-size: 10pt; line-height: 150%; font-family: =
'Courier New'; ">&nbsp;&nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:=
p></span></font></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 10pt; margin-bottom: 0.0001pt; line-height: 150%; =
font-size: 10.5pt; font-family: 'Times New Roman'; "><font size=3D"2" =
face=3D"Courier New"><span style=3D"font-size: 10pt; line-height: 150%; =
font-family: 'Courier New'; ">&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Include-all&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></font></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 10pt; =
margin-bottom: 0.0001pt; line-height: 150%; font-size: 10.5pt; =
font-family: 'Times New Roman'; "><font size=3D"2" face=3D"Courier =
New"><span style=3D"font-size: 10pt; line-height: 150%; font-family: =
'Courier New'; ">&nbsp;&nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:=
p></span></font></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 10pt; margin-bottom: 0.0001pt; line-height: 150%; =
font-size: 10.5pt; font-family: 'Times New Roman'; "><font size=3D"2" =
face=3D"Courier New"><span style=3D"font-size: 10pt; line-height: 150%; =
font-family: 'Courier New'; ">&nbsp;&nbsp; |&nbsp; Setup =
Prio&nbsp;&nbsp; |&nbsp; Holding Prio |&nbsp;&nbsp;&nbsp;&nbsp; =
Flags&nbsp;&nbsp; |L|&nbsp;&nbsp; Reserved&nbsp;&nbsp;&nbsp; =
|<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Courier New"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: 'Courier New'; ">&nbsp;&nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:=
p></span></font></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 10pt; margin-bottom: 0.0001pt; line-height: 150%; =
font-size: 10.5pt; font-family: 'Times New Roman'; "><font size=3D"2" =
face=3D"Courier New"><span style=3D"font-size: 10pt; line-height: 150%; =
font-family: 'Courier New'; ">&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; |<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Courier New"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: 'Courier New'; ">&nbsp;&nbsp; =
//&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Optional =
TLVs&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; //<o:p></o:p></span></font></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Courier New"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: 'Courier New'; ">&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; |<o:p></o:p></span></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 10pt; margin-bottom: 0.0001pt; =
line-height: 150%; font-size: 10.5pt; font-family: 'Times New Roman'; =
"><font size=3D"2" face=3D"Courier New"><span style=3D"font-size: 10pt; =
line-height: 150%; font-family: 'Courier New'; ">&nbsp;&nbsp; =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:=
p></span></font></div></div>______________________________________________=
_<br>Pce mailing list<br><a href=3D"mailto:Pce@ietf.org" style=3D"color: =
blue; text-decoration: underline; ">Pce@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/pce" style=3D"color: blue; =
text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/pce</a><br></div></span></blockquo=
te></div><br></div></body></html>=

--Apple-Mail-13--231883290--

--===============1710036962==
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

--===============1710036962==--


From pce-bounces@ietf.org  Thu Nov 20 07:22:22 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 364DC3A69F7;
	Thu, 20 Nov 2008 07:22:22 -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 DADAE3A67DB
	for <pce@core3.amsl.com>; Thu, 20 Nov 2008 07:22:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 SlzXC07EBwzV for <pce@core3.amsl.com>;
	Thu, 20 Nov 2008 07:22:20 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 0B6BA3A6867
	for <pce@ietf.org>; Thu, 20 Nov 2008 07:22:20 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,639,1220227200"; 
	d="scan'208,217";a="198378786"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 20 Nov 2008 15:22:19 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id mAKFMJea018375
	for <pce@ietf.org>; Thu, 20 Nov 2008 07:22:19 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id mAKFMIOS001242
	for <pce@ietf.org>; Thu, 20 Nov 2008 15:22:19 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Nov 2008 07:22:18 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 20 Nov 2008 07:21:30 -0800
Message-ID: <70BC84B185C3EE448EDB7AB8956D3B0E06E9EA3B@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <CE9D6E48-BAAE-4414-9A96-CBE4A5578617@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pce] Adoption of two new Working Documents ?
Thread-Index: AclKNqYhasuCPk4CR22+pBi8qTgK+AA7PiMg
References: <CE9D6E48-BAAE-4414-9A96-CBE4A5578617@cisco.com>
From: "Dean Cheng (dcheng)" <dcheng@cisco.com>
To: "Jean Philippe Vasseur (jvasseur)" <jvasseur@cisco.com>, <pce@ietf.org>
X-OriginalArrivalTime: 20 Nov 2008 15:22:18.0921 (UTC)
	FILETIME=[C6DEF990:01C94B23]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3530; t=1227194539;
	x=1228058539; 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]=20Adoption=20of=20two=20new=20Wor
	king=20Documents=20? |Sender:=20;
	bh=D+s7rWP1JOoXZ46t/0DBBg7qo1J0mJwyMFb4V5k50NA=;
	b=AbFWBmpot878WbjUFpIo2QiVng9wlKDfRYFOW9h9WglZ/DRQo1QyFJiLoQ
	v7G0YybIq7j4TwHX9gpHkyKQmVDkvGyrcR6lGdGIyT0Row6GPsINg7VUGAjx
	MDNrq2GaN6;
Authentication-Results: sj-dkim-4; header.From=dcheng@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [Pce] Adoption of two new Working Documents ?
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="===============1939110990=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1939110990==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C94B23.AA64E6F2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C94B23.AA64E6F2
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Support both.


________________________________

	From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On
Behalf Of JP Vasseur (jvasseur)
	Sent: Wednesday, November 19, 2008 3:05 AM
	To: pce@ietf.org
	Subject: [Pce] Adoption of two new Working Documents ?
=09
=09
	Dear WG,=20
=09
=09
	Are you in favor or opposed to the adoption of the two following
documents as PCE WG documents ?
=09
=09
	draft-farrel-pce-vendor-constraints-02.txt
=09
	draft-kkoushik-pce-pcep-mib-02.txt
=09
	Thanks.
=09
=09
	JP.


------_=_NextPart_001_01C94B23.AA64E6F2
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3429" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D538112115-20112008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Support both.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> pce-bounces@ietf.org=20
  [mailto:pce-bounces@ietf.org] <B>On Behalf Of </B>JP Vasseur=20
  (jvasseur)<BR><B>Sent:</B> Wednesday, November 19, 2008 3:05 =
AM<BR><B>To:</B>=20
  pce@ietf.org<BR><B>Subject:</B> [Pce] Adoption of two new Working =
Documents=20
  ?<BR></FONT><BR></DIV>
  <DIV></DIV><FONT class=3DApple-style-span face=3DArial>Dear WG,</FONT>
  <DIV><FONT class=3DApple-style-span face=3DArial><BR></FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial>Are you in favor or =
opposed to=20
  the adoption of the two following documents as PCE WG documents =
?</FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial><BR></FONT></DIV>
  <DIV><SPAN class=3DApple-style-span=20
  style=3D"FONT-FAMILY: =
Arial">draft-farrel-pce-vendor-constraints-02.txt</SPAN></DIV>
  <DIV><SPAN class=3DApple-style-span style=3D"FONT-SIZE: 16px; =
FONT-FAMILY: Times"><PRE style=3D"WORD-WRAP: break-word"><FONT =
class=3DApple-style-span face=3DArial size=3D4><SPAN =
class=3DApple-style-span style=3D"FONT-SIZE: =
14px">draft-kkoushik-pce-pcep-mib-02.txt</SPAN></FONT></PRE><PRE =
style=3D"WORD-WRAP: break-word"><FONT class=3DApple-style-span =
face=3DArial size=3D4><SPAN class=3DApple-style-span style=3D"FONT-SIZE: =
14px"></SPAN></FONT></PRE>
  <DIV><SPAN class=3DApple-style-span><FONT class=3DApple-style-span =
face=3DArial=20
  size=3D4><SPAN class=3DApple-style-span=20
  style=3D"FONT-SIZE: 14px">Thanks.</SPAN></FONT></SPAN></DIV>
  <DIV><SPAN class=3DApple-style-span><FONT class=3DApple-style-span =
face=3DArial=20
  size=3D4><SPAN class=3DApple-style-span=20
  style=3D"FONT-SIZE: 14px"><BR></SPAN></FONT></SPAN></DIV>
  <DIV><SPAN class=3DApple-style-span><FONT class=3DApple-style-span =
face=3DArial=20
  size=3D4><SPAN class=3DApple-style-span=20
  style=3D"FONT-SIZE: =
14px">JP.</SPAN></FONT></SPAN></DIV></SPAN></DIV></BLOCKQUOTE></BODY></HT=
ML>

------_=_NextPart_001_01C94B23.AA64E6F2--

--===============1939110990==
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

--===============1939110990==--


From pce-bounces@ietf.org  Thu Nov 20 08:16:24 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 754183A698C;
	Thu, 20 Nov 2008 08:16:24 -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 E4D513A67B5
	for <pce@core3.amsl.com>; Thu, 20 Nov 2008 08:16:22 -0800 (PST)
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 V0Qo-EP8BWS1 for <pce@core3.amsl.com>;
	Thu, 20 Nov 2008 08:16:22 -0800 (PST)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211])
	by core3.amsl.com (Postfix) with ESMTP id 15AF43A6980
	for <pce@ietf.org>; Thu, 20 Nov 2008 08:16:22 -0800 (PST)
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 <0KAN0099A3V8JL@usaga01-in.huawei.com> for
	pce@ietf.org; Thu, 20 Nov 2008 08:16:20 -0800 (PST)
Received: from Z73671a ([130.129.29.115])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KAN00EQA3V3XH@usaga01-in.huawei.com> for
	pce@ietf.org; Thu, 20 Nov 2008 08:16:20 -0800 (PST)
Date: Thu, 20 Nov 2008 11:16:21 -0500
From: Quintin Zhao <qzhao@huawei.com>
In-reply-to: <76626FC9B3DE41E5AA7EB3813C817EB2@your029b8cecfe>
To: 'Adrian Farrel' <adrian@olddog.co.uk>,
	'Nic Neate' <Nic.Neate@dataconnection.com>
Message-id: <000f01c94b2b$54558ee0$731d8182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: AclKiHqezXI/YPsdRbqX5Q6CAL9jFQAolHqQ
References: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B2B48@ENFIMBOX1.ad.datcon.co.uk>
	<76626FC9B3DE41E5AA7EB3813C817EB2@your029b8cecfe>
Cc: Jeanlouis.Leroux@orange-ftgroup.com,
	'Mohamad CHAITOU' <mohamad.chaitou@gmail.com>, pce@ietf.org,
	daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
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

Nic and Adrian,

Thanks for your suggestions!
 
By using the existing SVEC functionality, PCC can request the secondary P2MP
LSP path computation to protect the whole P2MP path tree by specifying the
S/N/L bit in the SVEC object. 

If we understand the new requirements you suggested for S2L sub-path
diversity, you want the PCC to be able to ask the PCE to compute secondary
P2MP path tree with partial path diversity for certain leaves or certain S2L
sub-path. 

We will address these new requirements in our next version of the draft.
 
Quintin

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk] 
Sent: Wednesday, November 19, 2008 3:49 PM
To: Nic Neate; qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com
Cc: Jeanlouis.Leroux@orange-ftgroup.com; pce@ietf.org; daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Ah, that is an interesting and valid point, Nic.

And I think one might also consider "directional diversity" for your ring 
example.

A
----- Original Message ----- 
From: "Nic Neate" <Nic.Neate@dataconnection.com>
To: <qzhao@huawei.com>; <Mohamad.Chaitou@orange-ftgroup.com>
Cc: <Jeanlouis.Leroux@orange-ftgroup.com>; <pce@ietf.org>; 
<daniel@olddog.co.uk>
Sent: Wednesday, November 19, 2008 8:28 PM
Subject: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions


Hi,

I have a suggestion for a small extension to the PCEP P2MP draft.

I believe the base PCEP specification currently has three options for 
calculating diverse protection paths: link diverse, node diverse and SRLG 
diverse (draft-ietf-pce-pcep section 7.13.2).

In P2MP, S2L sub-path diverse is another important case.  I think it would 
be good to allow the PCC to request computation of S2L sub-path diverse 
protection paths.

This is useful when doing 1+1 protection in a ring topology, for example.

Nic




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


> _______________________________________________
> 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 Nov 20 08:33:41 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1E8DA28C217;
	Thu, 20 Nov 2008 08:33:41 -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 391DC28C214
	for <pce@core3.amsl.com>; Thu, 20 Nov 2008 08:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.073
X-Spam-Level: 
X-Spam-Status: No, score=-2.073 tagged_above=-999 required=5 tests=[AWL=0.526, 
	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 6yrFamt3sCFL for <pce@core3.amsl.com>;
	Thu, 20 Nov 2008 08:33:38 -0800 (PST)
Received: from enfiets2.dataconnection.com (enfiets2.dataconnection.com
	[192.91.191.39])
	by core3.amsl.com (Postfix) with ESMTP id 1639B28C217
	for <pce@ietf.org>; Thu, 20 Nov 2008 08:33:37 -0800 (PST)
Received: from ENFIMBOX1.ad.datcon.co.uk (172.18.10.27) by
	enfiets2.dataconnection.com (172.18.4.22) with Microsoft SMTP Server
	(TLS) id 8.1.311.2; Thu, 20 Nov 2008 16:34:24 +0000
Received: from ENFIMBOX1.ad.datcon.co.uk ([172.18.10.27]) by
	ENFIMBOX1.ad.datcon.co.uk ([172.18.10.27]) with mapi; Thu, 20 Nov 2008
	16:33:41 +0000
From: Nic Neate <Nic.Neate@dataconnection.com>
To: Quintin Zhao <qzhao@huawei.com>, Aria - Adrian Farrel Personal
	<adrian@olddog.co.uk>
Date: Thu, 20 Nov 2008 16:33:33 +0000
Thread-Topic: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
Thread-Index: AclKiHqezXI/YPsdRbqX5Q6CAL9jFQAolHqQAACFhuA=
Message-ID: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B3209@ENFIMBOX1.ad.datcon.co.uk>
References: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B2B48@ENFIMBOX1.ad.datcon.co.uk>
	<76626FC9B3DE41E5AA7EB3813C817EB2@your029b8cecfe>
	<000f01c94b2b$54558ee0$731d8182@china.huawei.com>
In-Reply-To: <000f01c94b2b$54558ee0$731d8182@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "Jeanlouis.Leroux@orange-ftgroup.com"
	<Jeanlouis.Leroux@orange-ftgroup.com>,
	'Mohamad CHAITOU' <mohamad.chaitou@gmail.com>,
	"pce@ietf.org" <pce@ietf.org>, "daniel@olddog.co.uk" <daniel@olddog.co.uk>
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
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 Quintin,

I don't think "partial path diversity for certain leaves" is quite the point I was suggesting.

The idea of S2L sub-path diversity is that, when you're doing 1+1 protection, you don't need complete tree diversity.  It is sufficient just to ensure that, for any given leaf, the S2L sub-paths to that leaf in the two trees are diverse.  Then, following some network failure, traffic will still be delivered to all leaves on at least one of the two trees.

Two P2MP LSPs going in opposite ways around a ring is the easiest way to picture this.

Nic

-----Original Message-----
From: Quintin Zhao [mailto:qzhao@huawei.com]
Sent: 20 November 2008 16:16
To: Aria - Adrian Farrel Personal; Nic Neate
Cc: Jeanlouis.Leroux@orange-ftgroup.com; pce@ietf.org; daniel@olddog.co.uk; 'Mohamad CHAITOU'; fabien.verhaeghe@marben-products.com; zali@cisco.com; takeda.tomonori@lab.ntt.co.jp
Subject: RE: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Nic and Adrian,

Thanks for your suggestions!

By using the existing SVEC functionality, PCC can request the secondary P2MP LSP path computation to protect the whole P2MP path tree by specifying the S/N/L bit in the SVEC object.

If we understand the new requirements you suggested for S2L sub-path diversity, you want the PCC to be able to ask the PCE to compute secondary P2MP path tree with partial path diversity for certain leaves or certain S2L sub-path.

We will address these new requirements in our next version of the draft.

Quintin

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk]
Sent: Wednesday, November 19, 2008 3:49 PM
To: Nic Neate; qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com
Cc: Jeanlouis.Leroux@orange-ftgroup.com; pce@ietf.org; daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Ah, that is an interesting and valid point, Nic.

And I think one might also consider "directional diversity" for your ring example.

A
----- Original Message -----
From: "Nic Neate" <Nic.Neate@dataconnection.com>
To: <qzhao@huawei.com>; <Mohamad.Chaitou@orange-ftgroup.com>
Cc: <Jeanlouis.Leroux@orange-ftgroup.com>; <pce@ietf.org>; <daniel@olddog.co.uk>
Sent: Wednesday, November 19, 2008 8:28 PM
Subject: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions


Hi,

I have a suggestion for a small extension to the PCEP P2MP draft.

I believe the base PCEP specification currently has three options for calculating diverse protection paths: link diverse, node diverse and SRLG diverse (draft-ietf-pce-pcep section 7.13.2).

In P2MP, S2L sub-path diverse is another important case.  I think it would be good to allow the PCC to request computation of S2L sub-path diverse protection paths.

This is useful when doing 1+1 protection in a ring topology, for example.

Nic




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


> _______________________________________________
> 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 Nov 20 09:01: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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 034163A6A2E;
	Thu, 20 Nov 2008 09:01: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 BC27F3A6A27
	for <pce@core3.amsl.com>; Thu, 20 Nov 2008 09:01:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=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 pROdA0NfOuZP for <pce@core3.amsl.com>;
	Thu, 20 Nov 2008 09:01:50 -0800 (PST)
Received: from bizpsie3.9services.com (bizpsie3.9services.com [84.96.93.161])
	by core3.amsl.com (Postfix) with ESMTP id 1BF9C28C1D2
	for <pce@ietf.org>; Thu, 20 Nov 2008 09:01:49 -0800 (PST)
Received: from pooky.marben-products.com ([86.65.15.130])
	by bizpsie3.9services.com with 9services
	id hV1l1a0062oN1dS03V1lFs; Thu, 20 Nov 2008 18:01:47 +0100
X-Biz3: ??
X-VRSPAM-SCORE: -150.00
Received: from AOFR11476 ([192.168.20.7])
	by pooky.marben-products.com (8.14.0/8.14.0) with ESMTP id
	mAKH1dCS019303; Thu, 20 Nov 2008 18:01:40 +0100
From: "Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com>
To: "'Nic Neate'" <Nic.Neate@dataconnection.com>, <qzhao@huawei.com>,
	<Mohamad.Chaitou@orange-ftgroup.com>
Date: Thu, 20 Nov 2008 17:59:37 +0100
Message-ID: <000001c94b31$64fd1c80$0714a8c0@marbenproducts.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AclKg6JZZBjAFX5eS4iUl6u4Ge7NhwAqzxGw
In-Reply-To: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B2B48@ENFIMBOX1.ad.datcon.co.uk>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Cc: pce@ietf.org, Jeanlouis.Leroux@orange-ftgroup.com, daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
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="===============1832748246=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1832748246==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0001_01C94B39.C6C3CE70"

This is a multi-part message in MIME format.

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

Hi Nic,

=20

Just to be sure we understand, can you please confirm that the following
definition corresponds to what you name =93S2L sub-path diversity=94:

=20

For each leaf Ln the path from S to Ln in the primary P2MP LSP is Link =
(or
node or SRLG) diverse with the S to Ln path in the secondary P2MP LSP.

=20

If this is correct I also think this is a good suggestion that would be
easily fulfilled by defining a new bit in the SVEC object in next draft
version.

=20

BR

Fabien

=20

=20

  _____ =20

De : Nic Neate [mailto:Nic.Neate@dataconnection.com]=20
Envoy=E9 : mercredi 19 novembre 2008 21:29
=C0 : qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com
Cc : daniel@olddog.co.uk; fabien.verhaeghe@marben-products.com;
takeda.tomonori@lab.ntt.co.jp; Jeanlouis.Leroux@orange-ftgroup.com;
zali@cisco.com; pce@ietf.org
Objet : Comment on draft-ietf-pce-pcep-p2mp-extensions

=20

Hi,

=20

I have a suggestion for a small extension to the PCEP P2MP draft.

=20

I believe the base PCEP specification currently has three options for
calculating diverse protection paths: link diverse, node diverse and =
SRLG
diverse (draft-ietf-pce-pcep section 7.13.2).

=20

In P2MP, S2L sub-path diverse is another important case.  I think it =
would
be good to allow the PCC to request computation of S2L sub-path diverse
protection paths.

=20

This is useful when doing 1+1 protection in a ring topology, for =
example.

=20

Nic

=20


------=_NextPart_000_0001_01C94B39.C6C3CE70
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:navy;
	text-decoration:underline;}
p.emailquote, li.emailquote, div.emailquote
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!-- converted from rtf -->
</head>

<body lang=3DFR link=3Dblue vlink=3Dnavy>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hi =
Nic,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Just to be sure =
we
understand, can you please confirm that the following definition =
corresponds to
what you name &#8220;S2L sub-path =
diversity&#8221;:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:12.0pt'>For each leaf Ln the path from S to Ln in the =
primary P2MP
LSP is Link (or node or SRLG) diverse with the S to Ln path in the =
secondary
P2MP LSP.</span></font><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>If this is =
correct I also
think this is a good suggestion that would be easily fulfilled by =
defining a
new bit in the SVEC object in next draft =
version.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>BR<o:p></o:p></sp=
an></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Fabien<o:p></o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm =
0cm 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>De&nbsp;:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Nic =
Neate
[mailto:Nic.Neate@dataconnection.com] <br>
<b><span style=3D'font-weight:bold'>Envoy=E9&nbsp;:</span></b> mercredi =
19 novembre
2008 21:29<br>
<b><span style=3D'font-weight:bold'>=C0&nbsp;:</span></b> =
qzhao@huawei.com;
Mohamad.Chaitou@orange-ftgroup.com<br>
<b><span style=3D'font-weight:bold'>Cc&nbsp;:</span></b> =
daniel@olddog.co.uk;
fabien.verhaeghe@marben-products.com; takeda.tomonori@lab.ntt.co.jp;
Jeanlouis.Leroux@orange-ftgroup.com; zali@cisco.com; pce@ietf.org<br>
<b><span style=3D'font-weight:bold'>Objet&nbsp;:</span></b> Comment on
draft-ietf-pce-pcep-p2mp-extensions</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi,<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I have a suggestion for a small extension to the PCEP =
P2MP
draft.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I believe the base PCEP specification currently has =
three
options for calculating diverse protection paths: link diverse, node =
diverse
and SRLG diverse (draft-ietf-pce-pcep section =
7.13.2).<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In P2MP, S2L sub-path diverse is another important
case.&nbsp; I think it would be good to allow the PCC to request =
computation of
S2L sub-path diverse protection paths.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>This is useful when doing 1+1 protection in a ring =
topology,
for example.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Nic<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;<o:p></o:p></span></font></p>

</div>

</div>

</div>

</body>

</html>

------=_NextPart_000_0001_01C94B39.C6C3CE70--


--===============1832748246==
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

--===============1832748246==--



From pce-bounces@ietf.org  Thu Nov 20 10:41:18 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 45ACD28C14D;
	Thu, 20 Nov 2008 10:41:18 -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 888DF3A6898
	for <pce@core3.amsl.com>; Thu, 20 Nov 2008 10:41:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[AWL=0.350, 
	BAYES_00=-2.599, HTML_MESSAGE=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 u63BtOAUY+Yf for <pce@core3.amsl.com>;
	Thu, 20 Nov 2008 10:41:16 -0800 (PST)
Received: from enfiets1.dataconnection.com (enfiets1.dataconnection.com
	[192.91.191.38])
	by core3.amsl.com (Postfix) with ESMTP id 2F6943A67D2
	for <pce@ietf.org>; Thu, 20 Nov 2008 10:41:16 -0800 (PST)
Received: from ENFIMBOX1.ad.datcon.co.uk (172.18.10.27) by
	enfiets1.dataconnection.com (172.18.4.21) with Microsoft SMTP Server
	(TLS) id 8.1.311.2; Thu, 20 Nov 2008 18:41:36 +0000
Received: from ENFIMBOX1.ad.datcon.co.uk ([172.18.10.27]) by
	ENFIMBOX1.ad.datcon.co.uk ([172.18.10.27]) with mapi; Thu, 20 Nov 2008
	18:41:19 +0000
From: Nic Neate <Nic.Neate@dataconnection.com>
To: Fabien Verhaeghe <fabien.verhaeghe@marben-products.com>,
	"qzhao@huawei.com" <qzhao@huawei.com>, "Mohamad.Chaitou@orange-ftgroup.com"
	<Mohamad.Chaitou@orange-ftgroup.com>
Date: Thu, 20 Nov 2008 18:41:09 +0000
Thread-Topic: Comment on draft-ietf-pce-pcep-p2mp-extensions
Thread-Index: AclKg6JZZBjAFX5eS4iUl6u4Ge7NhwAqzxGwAAQeNYA=
Message-ID: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B3321@ENFIMBOX1.ad.datcon.co.uk>
References: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B2B48@ENFIMBOX1.ad.datcon.co.uk>
	<000001c94b31$64fd1c80$0714a8c0@marbenproducts.com>
In-Reply-To: <000001c94b31$64fd1c80$0714a8c0@marbenproducts.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "pce@ietf.org" <pce@ietf.org>, "Jeanlouis.Leroux@orange-ftgroup.com"
	<Jeanlouis.Leroux@orange-ftgroup.com>,
	"daniel@olddog.co.uk" <daniel@olddog.co.uk>
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
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="===============0081106048=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

--===============0081106048==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B3321ENFIMBOX1adda_"

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

Exactly.  I agree that a new bit in the SVEC object is the way to do this.

Thanks,

Nic

________________________________
From: Fabien Verhaeghe [mailto:fabien.verhaeghe@marben-products.com]
Sent: 20 November 2008 17:00
To: Nic Neate; qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com
Cc: daniel@olddog.co.uk; takeda.tomonori@lab.ntt.co.jp; Jeanlouis.Leroux@or=
ange-ftgroup.com; zali@cisco.com; pce@ietf.org
Subject: RE: Comment on draft-ietf-pce-pcep-p2mp-extensions

Hi Nic,

Just to be sure we understand, can you please confirm that the following de=
finition corresponds to what you name "S2L sub-path diversity":

For each leaf Ln the path from S to Ln in the primary P2MP LSP is Link (or =
node or SRLG) diverse with the S to Ln path in the secondary P2MP LSP.

If this is correct I also think this is a good suggestion that would be eas=
ily fulfilled by defining a new bit in the SVEC object in next draft versio=
n.

BR
Fabien


________________________________
De : Nic Neate [mailto:Nic.Neate@dataconnection.com]
Envoy=E9 : mercredi 19 novembre 2008 21:29
=C0 : qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com
Cc : daniel@olddog.co.uk; fabien.verhaeghe@marben-products.com; takeda.tomo=
nori@lab.ntt.co.jp; Jeanlouis.Leroux@orange-ftgroup.com; zali@cisco.com; pc=
e@ietf.org
Objet : Comment on draft-ietf-pce-pcep-p2mp-extensions

Hi,

I have a suggestion for a small extension to the PCEP P2MP draft.

I believe the base PCEP specification currently has three options for calcu=
lating diverse protection paths: link diverse, node diverse and SRLG divers=
e (draft-ietf-pce-pcep section 7.13.2).

In P2MP, S2L sub-path diverse is another important case.  I think it would =
be good to allow the PCC to request computation of S2L sub-path diverse pro=
tection paths.

This is useful when doing 1+1 protection in a ring topology, for example.

Nic


--_000_11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B3321ENFIMBOX1adda_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint" xmlns:oa =3D=20
"urn:schemas-microsoft-com:office:activation"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.6000.16735" name=3DGENERATOR><!--[if !mso]>
<STYLE>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</STYLE>
<![endif]-->
<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:navy;
	text-decoration:underline;}
p.emailquote, li.emailquote, div.emailquote
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</STYLE>
<!-- converted from rtf --></HEAD>
<BODY lang=3DFR vLink=3Dnavy link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D937373918-20112008><FONT face=3DA=
rial=20
color=3D#008080 size=3D2>Exactly.&nbsp; I agree that a new bit in the SVEC =
object is=20
the way to do this.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D937373918-20112008><FONT face=3DA=
rial=20
color=3D#008080 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D937373918-20112008><FONT face=3DA=
rial=20
color=3D#008080 size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D937373918-20112008><FONT face=3DA=
rial=20
color=3D#008080 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D937373918-20112008><FONT face=3DA=
rial=20
color=3D#008080 size=3D2>Nic</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Fabien Verhaeghe=20
[mailto:fabien.verhaeghe@marben-products.com] <BR><B>Sent:</B> 20 November =
2008=20
17:00<BR><B>To:</B> Nic Neate; qzhao@huawei.com;=20
Mohamad.Chaitou@orange-ftgroup.com<BR><B>Cc:</B> daniel@olddog.co.uk;=20
takeda.tomonori@lab.ntt.co.jp; Jeanlouis.Leroux@orange-ftgroup.com;=20
zali@cisco.com; pce@ietf.org<BR><B>Subject:</B> RE: Comment on=20
draft-ietf-pce-pcep-p2mp-extensions<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Hi=20
Nic,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p=
></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN lang=3D=
EN-GB=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Just to be sure =
we=20
understand, can you please confirm that the following definition correspond=
s to=20
what you name =93S2L sub-path diversity=94:<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN lang=3D=
EN-GB=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p=
></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN lang=3DE=
N-GB=20
style=3D"FONT-SIZE: 12pt">For each leaf Ln the path from S to Ln in the pri=
mary=20
P2MP LSP is Link (or node or SRLG) diverse with the S to Ln path in the=20
secondary P2MP LSP.</SPAN></FONT><FONT face=3DArial color=3Dnavy size=3D2><=
SPAN=20
lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p></o:p></SPA=
N></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN lang=3D=
EN-GB=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p=
></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN lang=3D=
EN-GB=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">If this is corre=
ct I=20
also think this is a good suggestion that would be easily fulfilled by defi=
ning=20
a new bit in the SVEC object in next draft version.<o:p></o:p></SPAN></FONT=
></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN lang=3D=
EN-GB=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p=
></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN lang=3D=
EN-GB=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">BR<o:p></o:p></S=
PAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN lang=3D=
EN-GB=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Fabien<o:p></o:p=
></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN lang=3D=
EN-GB=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p=
></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN lang=3D=
EN-GB=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p=
></SPAN></FONT></P>
<DIV=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium =
none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: blue 1.5pt solid=
; PADDING-TOP: 0cm; BORDER-BOTTOM: medium none">
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">De&nbsp;:=
</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"=
> Nic Neate=20
[mailto:Nic.Neate@dataconnection.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Envoy=E9&nbsp;:</SPAN></B> mercredi 19 novembre=
 2008=20
21:29<BR><B><SPAN style=3D"FONT-WEIGHT: bold">=C0&nbsp;:</SPAN></B>=20
qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Cc&nbsp;:</SPAN></B> daniel@olddog.co.uk;=20
fabien.verhaeghe@marben-products.com; takeda.tomonori@lab.ntt.co.jp;=20
Jeanlouis.Leroux@orange-ftgroup.com; zali@cisco.com; pce@ietf.org<BR><B><SP=
AN=20
style=3D"FONT-WEIGHT: bold">Objet&nbsp;:</SPAN></B> Comment on=20
draft-ietf-pce-pcep-p2mp-extensions</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi,<o:p></o:p></SPAN></FONT><=
/P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;<o:p></o:p></SPAN></FON=
T></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I have a suggestion for a sma=
ll=20
extension to the PCEP P2MP draft.<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;<o:p></o:p></SPAN></FON=
T></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I believe the base PCEP=20
specification currently has three options for calculating diverse protectio=
n=20
paths: link diverse, node diverse and SRLG diverse (draft-ietf-pce-pcep sec=
tion=20
7.13.2).<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;<o:p></o:p></SPAN></FON=
T></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">In P2MP, S2L sub-path diverse=
 is=20
another important case.&nbsp; I think it would be good to allow the PCC to=
=20
request computation of S2L sub-path diverse protection=20
paths.<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;<o:p></o:p></SPAN></FON=
T></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">This is useful when doing 1+1=
=20
protection in a ring topology, for example.<o:p></o:p></SPAN></FONT></P></D=
IV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;<o:p></o:p></SPAN></FON=
T></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Nic<o:p></o:p></SPAN></FONT><=
/P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;<o:p></o:p></SPAN></FON=
T></P></DIV></DIV></DIV></BODY></HTML>

--_000_11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B3321ENFIMBOX1adda_--

--===============0081106048==
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

--===============0081106048==--


From pce-bounces@ietf.org  Thu Nov 20 12:09:33 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 585623A69A1;
	Thu, 20 Nov 2008 12:09:33 -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 4711F3A6992
	for <pce@core3.amsl.com>; Thu, 20 Nov 2008 12:09:32 -0800 (PST)
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 dnhN3Qu0oH-T for <pce@core3.amsl.com>;
	Thu, 20 Nov 2008 12:09:30 -0800 (PST)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220])
	by core3.amsl.com (Postfix) with ESMTP id 814D83A677D
	for <pce@ietf.org>; Thu, 20 Nov 2008 12:09:30 -0800 (PST)
Received: from huawei.com (usaga03-in [172.18.4.17])
	by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KAN00IGEENQ5K@usaga03-in.huawei.com> for
	pce@ietf.org; Thu, 20 Nov 2008 14:09:27 -0600 (CST)
Received: from L73682 ([130.129.78.81])
	by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KAN00M3YENNC5@usaga03-in.huawei.com> for
	pce@ietf.org; Thu, 20 Nov 2008 14:09:26 -0600 (CST)
Date: Thu, 20 Nov 2008 14:09:17 -0600
From: Young Lee <ylee@huawei.com>
In-reply-to: <mailman.1813.1227206477.4916.pce@ietf.org>
To: pce@ietf.org
Message-id: <001001c94b4b$de4760e0$514e8182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: AclLP5fiReFej4c2Qp6XWw1QNG2GdgADDWrg
References: <mailman.1813.1227206477.4916.pce@ietf.org>
Subject: Re: [Pce] Pce Digest, Vol 51, Issue 13
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

In favor of both drafts.

Young Lee

-----Original Message-----
From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of
pce-request@ietf.org
Sent: Thursday, November 20, 2008 12:41 PM
To: pce@ietf.org
Subject: Pce Digest, Vol 51, Issue 13

Send Pce mailing list submissions to
	pce@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://www.ietf.org/mailman/listinfo/pce
or, via email, send a message with subject or body 'help' to
	pce-request@ietf.org

You can reach the person managing the list at
	pce-owner@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Pce digest..."


Today's Topics:

   1. Re: Adoption of two new Working Documents ? (Dean Cheng (dcheng))
   2. Re: Comment on draft-ietf-pce-pcep-p2mp-extensions (Quintin Zhao)
   3. Re: Comment on draft-ietf-pce-pcep-p2mp-extensions (Nic Neate)
   4. Re: Comment on draft-ietf-pce-pcep-p2mp-extensions
      (Fabien Verhaeghe)
   5. Re: Comment on draft-ietf-pce-pcep-p2mp-extensions (Nic Neate)


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

Message: 1
Date: Thu, 20 Nov 2008 07:21:30 -0800
From: "Dean Cheng (dcheng)" <dcheng@cisco.com>
Subject: Re: [Pce] Adoption of two new Working Documents ?
To: "Jean Philippe Vasseur (jvasseur)" <jvasseur@cisco.com>,
	<pce@ietf.org>
Message-ID:
	
<70BC84B185C3EE448EDB7AB8956D3B0E06E9EA3B@xmb-sjc-234.amer.cisco.com>
Content-Type: text/plain; charset="us-ascii"

Support both.


________________________________

	From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On
Behalf Of JP Vasseur (jvasseur)
	Sent: Wednesday, November 19, 2008 3:05 AM
	To: pce@ietf.org
	Subject: [Pce] Adoption of two new Working Documents ?
	
	
	Dear WG, 
	
	
	Are you in favor or opposed to the adoption of the two following
documents as PCE WG documents ?
	
	
	draft-farrel-pce-vendor-constraints-02.txt
	
	draft-kkoushik-pce-pcep-mib-02.txt
	
	Thanks.
	
	
	JP.

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.ietf.org/pipermail/pce/attachments/20081120/87420629/attachment-
0001.htm>

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

Message: 2
Date: Thu, 20 Nov 2008 11:16:21 -0500
From: Quintin Zhao <qzhao@huawei.com>
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
To: 'Adrian Farrel' <adrian@olddog.co.uk>,	'Nic Neate'
	<Nic.Neate@dataconnection.com>
Cc: Jeanlouis.Leroux@orange-ftgroup.com,	'Mohamad CHAITOU'
	<mohamad.chaitou@gmail.com>, pce@ietf.org,	daniel@olddog.co.uk
Message-ID: <000f01c94b2b$54558ee0$731d8182@china.huawei.com>
Content-Type: text/plain; charset=us-ascii

Nic and Adrian,

Thanks for your suggestions!
 
By using the existing SVEC functionality, PCC can request the secondary P2MP
LSP path computation to protect the whole P2MP path tree by specifying the
S/N/L bit in the SVEC object. 

If we understand the new requirements you suggested for S2L sub-path
diversity, you want the PCC to be able to ask the PCE to compute secondary
P2MP path tree with partial path diversity for certain leaves or certain S2L
sub-path. 

We will address these new requirements in our next version of the draft.
 
Quintin

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk] 
Sent: Wednesday, November 19, 2008 3:49 PM
To: Nic Neate; qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com
Cc: Jeanlouis.Leroux@orange-ftgroup.com; pce@ietf.org; daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Ah, that is an interesting and valid point, Nic.

And I think one might also consider "directional diversity" for your ring 
example.

A
----- Original Message ----- 
From: "Nic Neate" <Nic.Neate@dataconnection.com>
To: <qzhao@huawei.com>; <Mohamad.Chaitou@orange-ftgroup.com>
Cc: <Jeanlouis.Leroux@orange-ftgroup.com>; <pce@ietf.org>; 
<daniel@olddog.co.uk>
Sent: Wednesday, November 19, 2008 8:28 PM
Subject: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions


Hi,

I have a suggestion for a small extension to the PCEP P2MP draft.

I believe the base PCEP specification currently has three options for 
calculating diverse protection paths: link diverse, node diverse and SRLG 
diverse (draft-ietf-pce-pcep section 7.13.2).

In P2MP, S2L sub-path diverse is another important case.  I think it would 
be good to allow the PCC to request computation of S2L sub-path diverse 
protection paths.

This is useful when doing 1+1 protection in a ring topology, for example.

Nic




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


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





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

Message: 3
Date: Thu, 20 Nov 2008 16:33:33 +0000
From: Nic Neate <Nic.Neate@dataconnection.com>
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
To: Quintin Zhao <qzhao@huawei.com>, Aria - Adrian Farrel Personal
	<adrian@olddog.co.uk>
Cc: "Jeanlouis.Leroux@orange-ftgroup.com"
	<Jeanlouis.Leroux@orange-ftgroup.com>,	'Mohamad CHAITOU'
	<mohamad.chaitou@gmail.com>,	"pce@ietf.org" <pce@ietf.org>,
	"daniel@olddog.co.uk" <daniel@olddog.co.uk>
Message-ID:
	
<11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B3209@ENFIMBOX1.ad.datcon.co.uk>
Content-Type: text/plain; charset="us-ascii"

Hi Quintin,

I don't think "partial path diversity for certain leaves" is quite the point
I was suggesting.

The idea of S2L sub-path diversity is that, when you're doing 1+1
protection, you don't need complete tree diversity.  It is sufficient just
to ensure that, for any given leaf, the S2L sub-paths to that leaf in the
two trees are diverse.  Then, following some network failure, traffic will
still be delivered to all leaves on at least one of the two trees.

Two P2MP LSPs going in opposite ways around a ring is the easiest way to
picture this.

Nic

-----Original Message-----
From: Quintin Zhao [mailto:qzhao@huawei.com]
Sent: 20 November 2008 16:16
To: Aria - Adrian Farrel Personal; Nic Neate
Cc: Jeanlouis.Leroux@orange-ftgroup.com; pce@ietf.org; daniel@olddog.co.uk;
'Mohamad CHAITOU'; fabien.verhaeghe@marben-products.com; zali@cisco.com;
takeda.tomonori@lab.ntt.co.jp
Subject: RE: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Nic and Adrian,

Thanks for your suggestions!

By using the existing SVEC functionality, PCC can request the secondary P2MP
LSP path computation to protect the whole P2MP path tree by specifying the
S/N/L bit in the SVEC object.

If we understand the new requirements you suggested for S2L sub-path
diversity, you want the PCC to be able to ask the PCE to compute secondary
P2MP path tree with partial path diversity for certain leaves or certain S2L
sub-path.

We will address these new requirements in our next version of the draft.

Quintin

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk]
Sent: Wednesday, November 19, 2008 3:49 PM
To: Nic Neate; qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com
Cc: Jeanlouis.Leroux@orange-ftgroup.com; pce@ietf.org; daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Ah, that is an interesting and valid point, Nic.

And I think one might also consider "directional diversity" for your ring
example.

A
----- Original Message -----
From: "Nic Neate" <Nic.Neate@dataconnection.com>
To: <qzhao@huawei.com>; <Mohamad.Chaitou@orange-ftgroup.com>
Cc: <Jeanlouis.Leroux@orange-ftgroup.com>; <pce@ietf.org>;
<daniel@olddog.co.uk>
Sent: Wednesday, November 19, 2008 8:28 PM
Subject: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions


Hi,

I have a suggestion for a small extension to the PCEP P2MP draft.

I believe the base PCEP specification currently has three options for
calculating diverse protection paths: link diverse, node diverse and SRLG
diverse (draft-ietf-pce-pcep section 7.13.2).

In P2MP, S2L sub-path diverse is another important case.  I think it would
be good to allow the PCC to request computation of S2L sub-path diverse
protection paths.

This is useful when doing 1+1 protection in a ring topology, for example.

Nic




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


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





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

Message: 4
Date: Thu, 20 Nov 2008 17:59:37 +0100
From: "Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com>
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
To: "'Nic Neate'" <Nic.Neate@dataconnection.com>, <qzhao@huawei.com>,
	<Mohamad.Chaitou@orange-ftgroup.com>
Cc: pce@ietf.org, Jeanlouis.Leroux@orange-ftgroup.com,
	daniel@olddog.co.uk
Message-ID: <000001c94b31$64fd1c80$0714a8c0@marbenproducts.com>
Content-Type: text/plain; charset="iso-8859-1"

Hi Nic,

 

Just to be sure we understand, can you please confirm that the following
definition corresponds to what you name ?S2L sub-path diversity?:

 

For each leaf Ln the path from S to Ln in the primary P2MP LSP is Link (or
node or SRLG) diverse with the S to Ln path in the secondary P2MP LSP.

 

If this is correct I also think this is a good suggestion that would be
easily fulfilled by defining a new bit in the SVEC object in next draft
version.

 

BR

Fabien

 

 

  _____  

De : Nic Neate [mailto:Nic.Neate@dataconnection.com] 
Envoy? : mercredi 19 novembre 2008 21:29
? : qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com
Cc : daniel@olddog.co.uk; fabien.verhaeghe@marben-products.com;
takeda.tomonori@lab.ntt.co.jp; Jeanlouis.Leroux@orange-ftgroup.com;
zali@cisco.com; pce@ietf.org
Objet : Comment on draft-ietf-pce-pcep-p2mp-extensions

 

Hi,

 

I have a suggestion for a small extension to the PCEP P2MP draft.

 

I believe the base PCEP specification currently has three options for
calculating diverse protection paths: link diverse, node diverse and SRLG
diverse (draft-ietf-pce-pcep section 7.13.2).

 

In P2MP, S2L sub-path diverse is another important case.  I think it would
be good to allow the PCC to request computation of S2L sub-path diverse
protection paths.

 

This is useful when doing 1+1 protection in a ring topology, for example.

 

Nic

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.ietf.org/pipermail/pce/attachments/20081120/e04e83bb/attachment-
0001.htm>

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

Message: 5
Date: Thu, 20 Nov 2008 18:41:09 +0000
From: Nic Neate <Nic.Neate@dataconnection.com>
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
To: Fabien Verhaeghe <fabien.verhaeghe@marben-products.com>,
	"qzhao@huawei.com" <qzhao@huawei.com>,
	"Mohamad.Chaitou@orange-ftgroup.com"
	<Mohamad.Chaitou@orange-ftgroup.com>
Cc: "pce@ietf.org" <pce@ietf.org>,
	"Jeanlouis.Leroux@orange-ftgroup.com"
	<Jeanlouis.Leroux@orange-ftgroup.com>,	"daniel@olddog.co.uk"
	<daniel@olddog.co.uk>
Message-ID:
	
<11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B3321@ENFIMBOX1.ad.datcon.co.uk>
Content-Type: text/plain; charset="iso-8859-1"

Exactly.  I agree that a new bit in the SVEC object is the way to do this.

Thanks,

Nic

________________________________
From: Fabien Verhaeghe [mailto:fabien.verhaeghe@marben-products.com]
Sent: 20 November 2008 17:00
To: Nic Neate; qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com
Cc: daniel@olddog.co.uk; takeda.tomonori@lab.ntt.co.jp;
Jeanlouis.Leroux@orange-ftgroup.com; zali@cisco.com; pce@ietf.org
Subject: RE: Comment on draft-ietf-pce-pcep-p2mp-extensions

Hi Nic,

Just to be sure we understand, can you please confirm that the following
definition corresponds to what you name "S2L sub-path diversity":

For each leaf Ln the path from S to Ln in the primary P2MP LSP is Link (or
node or SRLG) diverse with the S to Ln path in the secondary P2MP LSP.

If this is correct I also think this is a good suggestion that would be
easily fulfilled by defining a new bit in the SVEC object in next draft
version.

BR
Fabien


________________________________
De : Nic Neate [mailto:Nic.Neate@dataconnection.com]
Envoy? : mercredi 19 novembre 2008 21:29
? : qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com
Cc : daniel@olddog.co.uk; fabien.verhaeghe@marben-products.com;
takeda.tomonori@lab.ntt.co.jp; Jeanlouis.Leroux@orange-ftgroup.com;
zali@cisco.com; pce@ietf.org
Objet : Comment on draft-ietf-pce-pcep-p2mp-extensions

Hi,

I have a suggestion for a small extension to the PCEP P2MP draft.

I believe the base PCEP specification currently has three options for
calculating diverse protection paths: link diverse, node diverse and SRLG
diverse (draft-ietf-pce-pcep section 7.13.2).

In P2MP, S2L sub-path diverse is another important case.  I think it would
be good to allow the PCC to request computation of S2L sub-path diverse
protection paths.

This is useful when doing 1+1 protection in a ring topology, for example.

Nic

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.ietf.org/pipermail/pce/attachments/20081120/267cb277/attachment.
htm>

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

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


End of Pce Digest, Vol 51, Issue 13
***********************************


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


From pce-bounces@ietf.org  Thu Nov 20 19:09: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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B6C923A6A5A;
	Thu, 20 Nov 2008 19:09:31 -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 B5F353A6A41
	for <pce@core3.amsl.com>; Thu, 20 Nov 2008 19:09:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	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 tbaeG32YO3Le for <pce@core3.amsl.com>;
	Thu, 20 Nov 2008 19:09:28 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67])
	by core3.amsl.com (Postfix) with ESMTP id B915A3A6A01
	for <pce@ietf.org>; Thu, 20 Nov 2008 19:09:28 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KAN0059BY3H4J@szxga04-in.huawei.com> for
	pce@ietf.org; Fri, 21 Nov 2008 11:09:17 +0800 (CST)
Received: from huawei.com ([172.24.1.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KAN003P6Y3HL2@szxga04-in.huawei.com> for
	pce@ietf.org; Fri, 21 Nov 2008 11:09:17 +0800 (CST)
Received: from hpSAQUIB ([10.18.5.57])
	by szxml05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KAN001ZDY3F78@szxml05-in.huawei.com> for
	pce@ietf.org; Fri, 21 Nov 2008 11:09:17 +0800 (CST)
Date: Fri, 21 Nov 2008 08:39:15 +0530
From: saquib khan <saquibk@huawei.com>
In-reply-to: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B3209@ENFIMBOX1.ad.datcon.co.uk>
To: 'Nic Neate' <Nic.Neate@dataconnection.com>,
	'Quintin Zhao' <qzhao@huawei.com>,
	'Aria - Adrian Farrel Personal' <adrian@olddog.co.uk>
Message-id: <009201c94b86$89e11420$3905120a@china.huawei.com>
Organization: htipl
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Thread-index: AclKiHqezXI/YPsdRbqX5Q6CAL9jFQAolHqQAACFhuAAFiej0A==
Cc: pce@ietf.org, 'Mohamad CHAITOU' <mohamad.chaitou@gmail.com>,
	Jeanlouis.Leroux@orange-ftgroup.com, daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: saquibk@huawei.com
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 Nic,
If we consider S2L diversity for all the leaves in the tree, automatically
the complete tree will become diverse, then why do we require a new
diversity option?


-----Original Message-----
From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of Nic
Neate
Sent: Thursday, November 20, 2008 10:04 PM
To: Quintin Zhao; Aria - Adrian Farrel Personal
Cc: Jeanlouis.Leroux@orange-ftgroup.com; 'Mohamad CHAITOU'; pce@ietf.org;
daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Hi Quintin,

I don't think "partial path diversity for certain leaves" is quite the point
I was suggesting.

The idea of S2L sub-path diversity is that, when you're doing 1+1
protection, you don't need complete tree diversity.  It is sufficient just
to ensure that, for any given leaf, the S2L sub-paths to that leaf in the
two trees are diverse.  Then, following some network failure, traffic will
still be delivered to all leaves on at least one of the two trees.

Two P2MP LSPs going in opposite ways around a ring is the easiest way to
picture this.

Nic

-----Original Message-----
From: Quintin Zhao [mailto:qzhao@huawei.com]
Sent: 20 November 2008 16:16
To: Aria - Adrian Farrel Personal; Nic Neate
Cc: Jeanlouis.Leroux@orange-ftgroup.com; pce@ietf.org; daniel@olddog.co.uk;
'Mohamad CHAITOU'; fabien.verhaeghe@marben-products.com; zali@cisco.com;
takeda.tomonori@lab.ntt.co.jp
Subject: RE: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Nic and Adrian,

Thanks for your suggestions!

By using the existing SVEC functionality, PCC can request the secondary P2MP
LSP path computation to protect the whole P2MP path tree by specifying the
S/N/L bit in the SVEC object.

If we understand the new requirements you suggested for S2L sub-path
diversity, you want the PCC to be able to ask the PCE to compute secondary
P2MP path tree with partial path diversity for certain leaves or certain S2L
sub-path.

We will address these new requirements in our next version of the draft.

Quintin

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk]
Sent: Wednesday, November 19, 2008 3:49 PM
To: Nic Neate; qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com
Cc: Jeanlouis.Leroux@orange-ftgroup.com; pce@ietf.org; daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Ah, that is an interesting and valid point, Nic.

And I think one might also consider "directional diversity" for your ring
example.

A
----- Original Message -----
From: "Nic Neate" <Nic.Neate@dataconnection.com>
To: <qzhao@huawei.com>; <Mohamad.Chaitou@orange-ftgroup.com>
Cc: <Jeanlouis.Leroux@orange-ftgroup.com>; <pce@ietf.org>;
<daniel@olddog.co.uk>
Sent: Wednesday, November 19, 2008 8:28 PM
Subject: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions


Hi,

I have a suggestion for a small extension to the PCEP P2MP draft.

I believe the base PCEP specification currently has three options for
calculating diverse protection paths: link diverse, node diverse and SRLG
diverse (draft-ietf-pce-pcep section 7.13.2).

In P2MP, S2L sub-path diverse is another important case.  I think it would
be good to allow the PCC to request computation of S2L sub-path diverse
protection paths.

This is useful when doing 1+1 protection in a ring topology, for example.

Nic




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


> _______________________________________________
> 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 Nov 21 08:19: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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BEA7B3A69F0;
	Fri, 21 Nov 2008 08:19: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 94C7E3A6A40
	for <pce@core3.amsl.com>; Fri, 21 Nov 2008 08:19:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.336
X-Spam-Level: 
X-Spam-Status: No, score=-2.336 tagged_above=-999 required=5 tests=[AWL=0.263, 
	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 pqyDWM8wOC1z for <pce@core3.amsl.com>;
	Fri, 21 Nov 2008 08:19:55 -0800 (PST)
Received: from enfiets2.dataconnection.com (enfiets2.dataconnection.com
	[192.91.191.39])
	by core3.amsl.com (Postfix) with ESMTP id 623583A697A
	for <pce@ietf.org>; Fri, 21 Nov 2008 08:19:55 -0800 (PST)
Received: from ENFIMBOX1.ad.datcon.co.uk (172.18.10.27) by
	enfiets2.dataconnection.com (172.18.4.22) with Microsoft SMTP Server
	(TLS) id 8.1.311.2; Fri, 21 Nov 2008 16:20:41 +0000
Received: from ENFIMBOX1.ad.datcon.co.uk ([172.18.10.27]) by
	ENFIMBOX1.ad.datcon.co.uk ([172.18.10.27]) with mapi; Fri, 21 Nov 2008
	16:19:59 +0000
From: Nic Neate <Nic.Neate@dataconnection.com>
To: "saquibk@huawei.com" <saquibk@huawei.com>
Date: Fri, 21 Nov 2008 16:19:58 +0000
Thread-Topic: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
Thread-Index: AclKiHqezXI/YPsdRbqX5Q6CAL9jFQAolHqQAACFhuAAFiej0AAbwgaw
Message-ID: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4FECF0@ENFIMBOX1.ad.datcon.co.uk>
References: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B3209@ENFIMBOX1.ad.datcon.co.uk>
	<009201c94b86$89e11420$3905120a@china.huawei.com>
In-Reply-To: <009201c94b86$89e11420$3905120a@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "pce@ietf.org" <pce@ietf.org>
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
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 Saquib,

In S2L sub-path diversity, it is allowed for the sub-path to leaf A in the first tree to share resources with the sub-path to leaf B in the second tree.  So the complete trees are not (necessarily) diverse.

Nic

-----Original Message-----
From: saquib khan [mailto:saquibk@huawei.com]
Sent: 21 November 2008 03:09
To: Nic Neate; 'Quintin Zhao'; Aria - Adrian Farrel Personal
Cc: Jeanlouis.Leroux@orange-ftgroup.com; 'Mohamad CHAITOU'; pce@ietf.org; daniel@olddog.co.uk
Subject: RE: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions



Hi Nic,
If we consider S2L diversity for all the leaves in the tree, automatically the complete tree will become diverse, then why do we require a new diversity option?


-----Original Message-----
From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of Nic Neate
Sent: Thursday, November 20, 2008 10:04 PM
To: Quintin Zhao; Aria - Adrian Farrel Personal
Cc: Jeanlouis.Leroux@orange-ftgroup.com; 'Mohamad CHAITOU'; pce@ietf.org; daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Hi Quintin,

I don't think "partial path diversity for certain leaves" is quite the point I was suggesting.

The idea of S2L sub-path diversity is that, when you're doing 1+1 protection, you don't need complete tree diversity.  It is sufficient just to ensure that, for any given leaf, the S2L sub-paths to that leaf in the two trees are diverse.  Then, following some network failure, traffic will still be delivered to all leaves on at least one of the two trees.

Two P2MP LSPs going in opposite ways around a ring is the easiest way to picture this.

Nic

-----Original Message-----
From: Quintin Zhao [mailto:qzhao@huawei.com]
Sent: 20 November 2008 16:16
To: Aria - Adrian Farrel Personal; Nic Neate
Cc: Jeanlouis.Leroux@orange-ftgroup.com; pce@ietf.org; daniel@olddog.co.uk; 'Mohamad CHAITOU'; fabien.verhaeghe@marben-products.com; zali@cisco.com; takeda.tomonori@lab.ntt.co.jp
Subject: RE: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Nic and Adrian,

Thanks for your suggestions!

By using the existing SVEC functionality, PCC can request the secondary P2MP LSP path computation to protect the whole P2MP path tree by specifying the S/N/L bit in the SVEC object.

If we understand the new requirements you suggested for S2L sub-path diversity, you want the PCC to be able to ask the PCE to compute secondary P2MP path tree with partial path diversity for certain leaves or certain S2L sub-path.

We will address these new requirements in our next version of the draft.

Quintin

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk]
Sent: Wednesday, November 19, 2008 3:49 PM
To: Nic Neate; qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com
Cc: Jeanlouis.Leroux@orange-ftgroup.com; pce@ietf.org; daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Ah, that is an interesting and valid point, Nic.

And I think one might also consider "directional diversity" for your ring example.

A
----- Original Message -----
From: "Nic Neate" <Nic.Neate@dataconnection.com>
To: <qzhao@huawei.com>; <Mohamad.Chaitou@orange-ftgroup.com>
Cc: <Jeanlouis.Leroux@orange-ftgroup.com>; <pce@ietf.org>; <daniel@olddog.co.uk>
Sent: Wednesday, November 19, 2008 8:28 PM
Subject: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions


Hi,

I have a suggestion for a small extension to the PCEP P2MP draft.

I believe the base PCEP specification currently has three options for calculating diverse protection paths: link diverse, node diverse and SRLG diverse (draft-ietf-pce-pcep section 7.13.2).

In P2MP, S2L sub-path diverse is another important case.  I think it would be good to allow the PCC to request computation of S2L sub-path diverse protection paths.

This is useful when doing 1+1 protection in a ring topology, for example.

Nic




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


> _______________________________________________
> 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 Nov 24 09:26:36 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 10CC428C0D9;
	Mon, 24 Nov 2008 09:26:36 -0800 (PST)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id 66EE13A6BB9; Mon, 24 Nov 2008 09:26:33 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20081124172633.66EE13A6BB9@core3.amsl.com>
Date: Mon, 24 Nov 2008 09:26:33 -0800 (PST)
Cc: Internet Architecture Board <iab@iab.org>, pce mailing list <pce@ietf.org>,
	pce chair <pce-chairs@tools.ietf.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Pce] Protocol Action: 'Path Computation Element (PCE)
 Communication Protocol (PCEP)' to Proposed Standard
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

The IESG has approved the following document:

- 'Path Computation Element (PCE) Communication Protocol (PCEP) '
   <draft-ietf-pce-pcep-19.txt> as a Proposed Standard

This document is the product of the Path Computation Element Working 
Group. 

The IESG contact persons are Ross Callon and David Ward.

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

Technical Summary

   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

   No controversy reported (see PROTO writeup by Adrian Farrel, that
   I have included below). This protocol is central to the work of 
   the PCE working group and it therefore has been very carefully
   reviewed and enjoys strong consensus in the working group. 

Document Quality

   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, and the spec updated accordingly. The document has
   been extensively reviewed. 

Personnel

   Adrian Farrel is the document shepherd. Ross Callon is the 
   responsible AD.  

RFC Editor Note

  The reference to [RFC2385] should be moved from informative 
  references (section 13.2) to normative references (section 13.1).

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


From pce-bounces@ietf.org  Mon Nov 24 19:21:27 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4FBD43A67FB;
	Mon, 24 Nov 2008 19:21:27 -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 77B3A3A67FB
	for <pce@core3.amsl.com>; Mon, 24 Nov 2008 19:21:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.617
X-Spam-Level: 
X-Spam-Status: No, score=-0.617 tagged_above=-999 required=5
	tests=[AWL=-1.982, BAYES_20=-0.74, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 YtM6XML6nJxL for <pce@core3.amsl.com>;
	Mon, 24 Nov 2008 19:21:24 -0800 (PST)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65])
	by core3.amsl.com (Postfix) with ESMTP id 20E5F3A67E3
	for <pce@ietf.org>; Mon, 24 Nov 2008 19:21:24 -0800 (PST)
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KAV00E3JDBB86@szxga02-in.huawei.com> for
	pce@ietf.org; Tue, 25 Nov 2008 11:21:11 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KAV00936DBB7Y@szxga02-in.huawei.com> for
	pce@ietf.org; Tue, 25 Nov 2008 11:21:11 +0800 (CST)
Received: from SSK1548 ([10.18.24.148])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KAV007AJDB9GR@szxml04-in.huawei.com> for
	pce@ietf.org; Tue, 25 Nov 2008 11:21:11 +0800 (CST)
Date: Tue, 25 Nov 2008 08:51:09 +0530
From: "S.SenthilKumar" <senthilKumars@huawei.com>
To: pce@ietf.org
Message-id: <000d01c94eac$dcf190d0$9418120a@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: AclOrNw1v9FXrqhAR1W8ectMYNq/LA==
Subject: [Pce] Reg Max Unknown Request
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="===============1265814732=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1265814732==
Content-type: multipart/alternative;
 boundary="Boundary_(ID_Q9YBdEJqZtthRYHLfgnybQ)"

This is a multi-part message in MIME format.

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

Dear All

Please correct this typo error. MAX-UNKOWN-REQUESTS in Draft 19 of PCEP.

In addition, I like to understand the use of this parameter to close the
session. In the PCEP Draft, only error in RP Object is considered to be
unknown request. Please let me know if is there any other use case to
declare that the request is said to be unknown 

 

Thanking you,

 

Best regards,

S.SenthilKumar

 


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

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="stockticker"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:KaiTi_GB2312;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@SimHei";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@KaiTi_GB2312";}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";}
h1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:21.55pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-21.55pt;
	page-break-after:avoid;
	mso-list:l10 level1 lfo35;
	font-size:16.0pt;
	font-family:Arial;
	font-weight:bold;}
h2
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.4in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.4in;
	page-break-after:avoid;
	mso-list:l10 level2 lfo35;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
h3
	{margin-top:13.0pt;
	margin-right:0in;
	margin-bottom:13.0pt;
	margin-left:.5in;
	mso-para-margin-top:13.0pt;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:13.0pt;
	mso-para-margin-left:2.0gd;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.5in;
	line-height:173%;
	page-break-after:avoid;
	mso-list:l10 level3 lfo35;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	layout-grid-mode:char;
	font-size:9.0pt;
	font-family:Arial;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:8.0pt;
	font-family:Tahoma;}
p.Table, li.Table, div.Table
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	mso-para-margin-top:1.0gd;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:0in;
	mso-para-margin-bottom:.0001pt;
	text-align:center;
	text-indent:0in;
	mso-list:l7 level9 lfo5;
	font-size:9.0pt;
	font-family:Arial;}
p.TableText, li.TableText, div.TableText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Arial;}
p.TableHeader, li.TableHeader, div.TableHeader
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:10.5pt;
	font-family:Arial;
	font-weight:bold;}
p.FigureStyle, li.FigureStyle, div.FigureStyle
	{margin-top:4.0pt;
	margin-right:0in;
	margin-bottom:4.0pt;
	margin-left:0in;
	text-align:center;
	line-height:150%;
	page-break-after:avoid;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";}
p.DocumentTitle, li.DocumentTitle, div.DocumentTitle
	{margin-top:15.0pt;
	margin-right:0in;
	margin-bottom:15.0pt;
	margin-left:0in;
	text-align:center;
	line-height:150%;
	text-autospace:none;
	font-size:18.0pt;
	font-family:Arial;}
p.NotesHeader, li.NotesHeader, div.NotesHeader
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0in;
	font-size:9.0pt;
	font-family:Arial;}
p.NotesText, li.NotesText, div.NotesText
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:.25in;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0in;
	font-size:9.0pt;
	font-family:Arial;}
p.CompilingAdvice, li.CompilingAdvice, div.CompilingAdvice
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:Arial;
	color:blue;
	font-style:italic;}
p.Figure, li.Figure, div.Figure
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	text-indent:0in;
	line-height:150%;
	mso-list:l7 level8 lfo5;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";}
span.EmailStyle30
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
 /* Page Definitions */
 @page
	{mso-endnote-separator:url("cid:header.htm\@01C94EDA.F5E8C6C0") es;
	mso-endnote-continuation-separator:url("cid:header.htm\@01C94EDA.F5E8C6C0") ecs;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.0in 1.0in 1.0in;
	mso-footer:url("cid:header.htm\@01C94EDA.F5E8C6C0") f1;
	layout-grid:15.6pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:171800355;
	mso-list-template-ids:-1278163850;}
@list l0:level1
	{mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l0:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l0:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l0:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l0:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l0:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l0:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l0:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l0:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l1
	{mso-list-id:191647984;
	mso-list-template-ids:345692754;}
@list l1:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:64.15pt;
	mso-level-number-position:left;
	margin-left:64.15pt;
	text-indent:-.3in;}
@list l1:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:71.35pt;
	mso-level-number-position:left;
	margin-left:71.35pt;
	text-indent:-.4in;}
@list l1:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:78.55pt;
	mso-level-number-position:left;
	margin-left:78.55pt;
	text-indent:-.5in;}
@list l1:level4
	{mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:114.55pt;
	mso-level-number-position:left;
	margin-left:114.55pt;
	text-indent:-1.0in;}
@list l1:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:121.75pt;
	mso-level-number-position:left;
	margin-left:121.75pt;
	text-indent:-1.1in;}
@list l2
	{mso-list-id:541409008;
	mso-list-template-ids:-249166292;}
@list l2:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l2:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l2:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l2:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l2:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l2:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l2:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l2:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l2:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l3
	{mso-list-id:731736200;
	mso-list-template-ids:67698717;}
@list l3:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l3:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:57.25pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l3:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:96.55pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l3:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:153.8pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l3:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:193.05pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l3:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:232.3pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l3:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:271.55pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l3:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:310.8pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l3:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:350.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l4
	{mso-list-id:818422186;
	mso-list-template-ids:1344984950;}
@list l4:level1
	{mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l4:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l4:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l4:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l4:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l4:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l4:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l4:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l4:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l5
	{mso-list-id:838886720;
	mso-list-template-ids:-819953982;}
@list l5:level1
	{mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;
	mso-ansi-font-size:18.0pt;
	mso-bidi-font-size:18.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;
	mso-ansi-font-size:15.0pt;
	mso-bidi-font-size:15.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;
	mso-ansi-font-size:12.0pt;
	mso-bidi-font-size:12.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6
	{mso-list-id:942373150;
	mso-list-template-ids:67698717;}
@list l6:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l6:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:57.25pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l6:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:96.55pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l6:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:135.8pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l6:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:175.05pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l6:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:214.3pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l6:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:253.55pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l6:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:292.8pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l6:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:332.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l7
	{mso-list-id:1123964682;
	mso-list-template-ids:548200814;}
@list l7:level1
	{mso-level-suffix:none;
	mso-level-text:"%1  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:0in;
	mso-ansi-font-size:18.0pt;
	mso-bidi-font-size:18.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level2
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:15.0pt;
	mso-bidi-font-size:15.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level3
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:12.0pt;
	mso-bidi-font-size:12.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level4
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level5
	{mso-level-tab-stop:92.7pt;
	mso-level-number-position:left;
	margin-left:92.7pt;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level6
	{mso-level-text:"%6\)";
	mso-level-tab-stop:92.7pt;
	mso-level-number-position:left;
	margin-left:92.7pt;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level7
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:92.7pt;
	mso-level-number-position:left;
	margin-left:92.7pt;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level8
	{mso-level-reset-level:level1;
	mso-level-style-link:Figure;
	mso-level-suffix:space;
	mso-level-text:Figure%8;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level9
	{mso-level-reset-level:level1;
	mso-level-style-link:Table;
	mso-level-suffix:space;
	mso-level-text:Table%9;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l8
	{mso-list-id:1380013528;
	mso-list-template-ids:-1435872280;}
@list l8:level1
	{mso-level-number-format:none;
	mso-level-text:"\9644\5F55A ";
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l8:level2
	{mso-level-text:"A\.%2";
	mso-level-tab-stop:49.6pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l8:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l8:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:99.2pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l8:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:127.55pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l8:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:163.0pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l8:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:191.35pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l8:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:219.7pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l8:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:255.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l9
	{mso-list-id:1425803385;
	mso-list-template-ids:67698717;}
@list l9:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l9:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:57.25pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l9:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:96.55pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l9:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:153.8pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l9:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:193.05pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l9:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:232.3pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l9:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:271.55pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l9:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:310.8pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l9:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:350.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l10
	{mso-list-id:1666475049;
	mso-list-template-ids:-28945502;}
@list l10:level1
	{mso-level-style-link:"Heading 1";
	mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l10:level2
	{mso-level-style-link:"Heading 2";
	mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l10:level3
	{mso-level-style-link:"Heading 3";
	mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l10:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l10:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l10:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l10:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l10:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l10:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l11
	{mso-list-id:1916042858;
	mso-list-template-ids:-648263936;}
@list l11:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l11:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l11:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l11:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l11:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l11:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l11:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l11:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l11:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l12
	{mso-list-id:2114861838;
	mso-list-template-ids:-433129230;}
@list l12:level1
	{mso-level-number-format:none;
	mso-level-text:"\9644\5F55A ";
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l12:level2
	{mso-level-text:"A\.%2";
	mso-level-tab-stop:49.6pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l12:level3
	{mso-level-text:"%1A\.%2\.%3";
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l12:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:99.2pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l12:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:127.55pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l12:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:163.0pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l12:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:191.35pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l12:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:219.7pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l12:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:255.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="3074" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="2" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple style='text-justify-trim:punctuation'>

<div class=Section1 style='layout-grid:15.6pt'>

<p class=MsoNormal style='margin-left:0in'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>Dear All<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:21.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>Please correct this
typo error. <st1:stockticker w:st="on">MAX</st1:stockticker>-UNKOWN-REQUESTS in
Draft 19 of PCEP.<o:p></o:p></span></font></p>

<p class=MsoNormal style='margin-left:21.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>In addition, I like
to understand the use of this parameter to close the session. In the PCEP
Draft, only error in RP Object is considered to be unknown request. Please let
me know if is there any other use case to declare that the request is said to
be unknown <o:p></o:p></span></font></p>

<p class=MsoAutoSig><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoAutoSig><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'>Thanking you,<o:p></o:p></span></font></p>

<p class=MsoAutoSig><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoAutoSig><font size=2 color=black face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:black'>Best regards,<o:p></o:p></span></font></p>

<p class=MsoAutoSig><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>S.SenthilKumar</span><o:p></o:p></font></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Times New Roman"><span
style='font-size:10.5pt;line-height:150%'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--Boundary_(ID_Q9YBdEJqZtthRYHLfgnybQ)--

--===============1265814732==
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

--===============1265814732==--


From pce-bounces@ietf.org  Mon Nov 24 21:49:42 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 43CD83A69CA;
	Mon, 24 Nov 2008 21:49:42 -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 8A44C3A6BE8
	for <pce@core3.amsl.com>; Mon, 24 Nov 2008 18:49:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.09
X-Spam-Level: 
X-Spam-Status: No, score=-6.09 tagged_above=-999 required=5 tests=[AWL=0.509, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 fEeyZHB-iJec for <pce@core3.amsl.com>;
	Mon, 24 Nov 2008 18:49:28 -0800 (PST)
Received: from exprod7og114.obsmtp.com (exprod7ob114.obsmtp.com [64.18.2.214])
	by core3.amsl.com (Postfix) with ESMTP id 5C5CC3A67FB
	for <pce@ietf.org>; Mon, 24 Nov 2008 18:49:28 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by
	exprod7ob114.postini.com ([64.18.6.12]) with SMTP
	ID DSNKSStnrd37HZqZFVGiYDhcKHEaHWg5LqMq@postini.com;
	Mon, 24 Nov 2008 18:49:26 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net
	(172.24.192.35) with Microsoft SMTP Server id 8.1.311.2;
	Mon, 24 Nov 2008 18:47:58 -0800
Received: from p-emsmtp03.jnpr.net ([66.129.254.54]) by p-emfe01-sac.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959);
	Mon, 24 Nov 2008 18:47:57 -0800
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emsmtp03.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959);	 Mon, 24 Nov 2008 18:47:57 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 24 Nov 2008 21:47:55 -0500
Message-ID: <3525C9833C09ED418C6FD6CD9514668C0527CE0A@emailwf1.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: draft-dasgupta-ccamp-path-comp-analysis (Performance
	Analysis of Inter-Domain Path Computation Methodologies) to
	Informational RFC 
Thread-Index: AclIPpkoVOfZj2+HQrWsxfehn50BeAGaTM0g
From: Ross Callon <rcallon@juniper.net>
To: <ccamp@ops.ietf.org>,
	<pce@ietf.org>
X-OriginalArrivalTime: 25 Nov 2008 02:47:57.0005 (UTC)
	FILETIME=[38BB6FD0:01C94EA8]
X-Mailman-Approved-At: Mon, 24 Nov 2008 21:49:40 -0800
Cc: ccamp-chairs@tools.ietf.org, pce-chairs@tools.ietf.org
Subject: [Pce] FW: Last Call: draft-dasgupta-ccamp-path-comp-analysis
	(Performance Analysis of Inter-Domain Path Computation
	Methodologies) to Informational RFC
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

FYI. This document may be of interest to folks in the PCE and CCAMP
working groups. As is normal for IETF last calls, comments can be sent
to ietf@ietf.org (or exceptionally, to iesg@ietf.org instead). 

Thanks, Ross

-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG
Sent: 16 November 2008 17:55
To: IETF-Announce
Subject: Last Call: draft-dasgupta-ccamp-path-comp-analysis (Performance
Analysis of Inter-Domain Path Computation Methodologies) to
Informational RFC 

The IESG has received a request from an individual submitter to consider

the following document:

- 'Performance Analysis of Inter-Domain Path Computation Methodologies '
   <draft-dasgupta-ccamp-path-comp-analysis-02.txt> as an Informational
RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2008-12-14. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-dasgupta-ccamp-path-comp-analy
sis-02.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=
16050&rfc_flag=0

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


From pce-bounces@ietf.org  Tue Nov 25 00:58:43 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3D14A3A6ACE;
	Tue, 25 Nov 2008 00:58:43 -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 41F833A6ACD
	for <pce@core3.amsl.com>; Tue, 25 Nov 2008 00:58:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 zryUk6+ZVtG1 for <pce@core3.amsl.com>;
	Tue, 25 Nov 2008 00:58:41 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id BC8A83A6AB2
	for <pce@ietf.org>; Tue, 25 Nov 2008 00:58:29 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,663,1220227200"; d="scan'208,217";a="26699732"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 25 Nov 2008 08:57:07 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mAP8v754008706
	for <pce@ietf.org>; Tue, 25 Nov 2008 09:57:07 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mAP8v7Ea002824
	for <pce@ietf.org>; Tue, 25 Nov 2008 08:57:07 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 25 Nov 2008 09:57:07 +0100
Received: from ams-jvasseur-8712.cisco.com ([10.55.201.131]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 25 Nov 2008 09:57:06 +0100
Message-Id: <3D1E7B57-07FE-41F0-AAAB-3E07162200E4@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: pce@ietf.org
Mime-Version: 1.0 (Apple Message framework v926)
Date: Tue, 25 Nov 2008 09:57:06 +0100
X-Mailer: Apple Mail (2.926)
X-OriginalArrivalTime: 25 Nov 2008 08:57:06.0907 (UTC)
	FILETIME=[CB1A42B0:01C94EDB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2095; t=1227603427;
	x=1228467427; c=relaxed/simple; s=amsdkim1002;
	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:=20Working=20Group=20Last=20Call=3A=20draft-ietf-p
	ce-global-concurrent-optimization-05.txt |Sender:=20;
	bh=0kTFvQJcvzmUnyGXmh5IZs5NZ2ANjhvQf16Ho9yJhAg=;
	b=s+MJweBlc4zqPDx4QmkviK24EI+Hs79vX3QR14L/nJrdhV0brCyywVH/fi
	JXUreJLygqqHqssbwzo5W8w8f/gF2WpSEYI0qZJFAJSMD5WkS2AjIHLBb0as
	C03dfIq6dk;
Authentication-Results: ams-dkim-1; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Subject: [Pce] Working Group Last Call:
	draft-ietf-pce-global-concurrent-optimization-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>
Content-Type: multipart/mixed; boundary="===============1772167250=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org


--===============1772167250==
Content-Type: multipart/alternative; boundary=Apple-Mail-75-188123499


--Apple-Mail-75-188123499
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Dear WG,

This starts a 2-week Working Group Last Call on draft-ietf-pce-global- 
concurrent-optimization-05.txt, which will end on December 9 at noon ET.

Please send your comment on the Mailing list and to the authors.

Thanks.

JP.
--Apple-Mail-75-188123499
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><font class=3D"Apple-style-span" =
face=3D"Arial">Dear WG,</font><div><font class=3D"Apple-style-span" =
face=3D"Arial"><br></font></div><div><font class=3D"Apple-style-span" =
face=3D"Arial">This starts a 2-week Working Group Last Call =
on&nbsp;</font><span class=3D"Apple-style-span" style=3D"white-space: =
pre-wrap; "><font class=3D"Apple-style-span" =
face=3D"Arial">draft-ietf-pce-global-concurrent-optimization-05.txt, =
which will end on December 9 at noon ET.</font></span></div><div><span =
class=3D"Apple-style-span" style=3D"white-space: pre-wrap; "><font =
class=3D"Apple-style-span" =
face=3D"Arial"><br></font></span></div><div><span =
class=3D"Apple-style-span" style=3D"white-space: pre-wrap; "><font =
class=3D"Apple-style-span" face=3D"Arial">Please send your comment on =
the Mailing list and to the authors.</font></span></div><div><font =
class=3D"Apple-style-span" face=3D"Arial"><span class=3D"Apple-style-span"=
 style=3D"white-space: pre-wrap;"><br></span></font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial"><span class=3D"Apple-style-span"=
 style=3D"white-space: pre-wrap;">Thanks.</span></font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial"><span class=3D"Apple-style-span"=
 style=3D"white-space: pre-wrap;"><br></span></font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial"><span class=3D"Apple-style-span"=
 style=3D"white-space: pre-wrap;">JP.</span></font></div></body></html>=

--Apple-Mail-75-188123499--

--===============1772167250==
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

--===============1772167250==--


From pce-bounces@ietf.org  Tue Nov 25 01:51:30 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F35E83A6B03;
	Tue, 25 Nov 2008 01:51:29 -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 82B823A6B03
	for <pce@core3.amsl.com>; Tue, 25 Nov 2008 01:51:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.209
X-Spam-Level: ***
X-Spam-Status: No, score=3.209 tagged_above=-999 required=5
	tests=[BAYES_40=-0.185, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,
	HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=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 F63eDzN4LI4K for <pce@core3.amsl.com>;
	Tue, 25 Nov 2008 01:51:27 -0800 (PST)
Received: from tyo202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.32.8.206])
	by core3.amsl.com (Postfix) with ESMTP id 8EEBE3A6ACD
	for <pce@ietf.org>; Tue, 25 Nov 2008 01:51:27 -0800 (PST)
Received: from mailgate3.nec.co.jp ([10.7.69.193])
	by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id mAP9pMaf002394; 
	Tue, 25 Nov 2008 18:51:22 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp
	(8.11.7/3.7W-MAILGATE-NEC)
	id mAP9pMC19412; Tue, 25 Nov 2008 18:51:22 +0900 (JST)
Received: from mail03.kamome.nec.co.jp (mail03.kamome.nec.co.jp [10.25.43.7])
	by mailsv3.nec.co.jp (8.13.8/8.13.4) with ESMTP id mAP9pM3p028529;
	Tue, 25 Nov 2008 18:51:22 +0900 (JST)
Received: from shoin.jp.nec.com ([10.26.220.3] [10.26.220.3]) by
	mail02.kamome.nec.co.jp with ESMTP id BT-MMP-121924;
	Tue, 25 Nov 2008 18:50:34 +0900
Received: from C08AUG00201 ([10.56.131.165] [10.56.131.165]) by
	mail.jp.nec.com with ESMTP; Tue, 25 Nov 2008 18:50:34 +0900
From: "Itaru Nishioka" <i-nishioka@cb.jp.nec.com>
To: "'JP Vasseur'" <jvasseur@cisco.com>, <pce@ietf.org>
References: <CE9D6E48-BAAE-4414-9A96-CBE4A5578617@cisco.com>
In-Reply-To: <CE9D6E48-BAAE-4414-9A96-CBE4A5578617@cisco.com>
Date: Tue, 25 Nov 2008 18:50:32 +0900
Organization: NEC
Message-ID: <A531E4BE29104DA29F9E5A10875C259B@nsl.ad.nec.co.jp>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18000
Thread-Index: AclKNqaRFMsDjtzcRcmQi+hWU5o03AErH7Rg
Subject: Re: [Pce] Adoption of two new Working Documents ?
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: i-nishioka@cb.jp.nec.com
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="===============1157143338=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1157143338==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0048_01C94F2E.B18A4A90"

This is a multi-part message in MIME format.

------=_NextPart_000_0048_01C94F2E.B18A4A90
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Support both.
 
 
Itaru.
 
 


  _____  

From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of JP
Vasseur
Sent: Wednesday, November 19, 2008 8:05 PM
To: pce@ietf.org
Subject: [Pce] Adoption of two new Working Documents ?


Dear WG, 


Are you in favor or opposed to the adoption of the two following documents
as PCE WG documents ?


draft-farrel-pce-vendor-constraints-02.txt

draft-kkoushik-pce-pcep-mib-02.txt

Thanks.


JP.


------=_NextPart_000_0048_01C94F2E.B18A4A90
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18148" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" color=3D#0000ff size=3D2><SPAN =

class=3D861444909-25112008>Support both.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" color=3D#0000ff size=3D2><SPAN =

class=3D861444909-25112008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" color=3D#0000ff size=3D2><SPAN =

class=3D861444909-25112008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" color=3D#0000ff size=3D2><SPAN =

class=3D861444909-25112008>Itaru.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"&#65325;&#65331; =
&#65328;&#12468;&#12471;&#12483;&#12463;" color=3D#0000ff size=3D2><SPAN =

class=3D861444909-25112008></SPAN></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Dja dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> pce-bounces@ietf.org=20
  [mailto:pce-bounces@ietf.org] <B>On Behalf Of </B>JP =
Vasseur<BR><B>Sent:</B>=20
  Wednesday, November 19, 2008 8:05 PM<BR><B>To:</B>=20
  pce@ietf.org<BR><B>Subject:</B> [Pce] Adoption of two new Working =
Documents=20
  ?<BR></FONT><BR></DIV>
  <DIV></DIV><FONT class=3DApple-style-span face=3DArial>Dear WG,</FONT>
  <DIV><FONT class=3DApple-style-span face=3DArial><BR></FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial>Are you in favor or =
opposed to=20
  the adoption of the two following documents as PCE WG documents =
?</FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial><BR></FONT></DIV>
  <DIV><SPAN class=3DApple-style-span=20
  style=3D"FONT-FAMILY: =
Arial">draft-farrel-pce-vendor-constraints-02.txt</SPAN></DIV>
  <DIV><SPAN class=3DApple-style-span style=3D"FONT-SIZE: 16px; =
FONT-FAMILY: Times"><PRE style=3D"WORD-WRAP: break-word"><FONT =
class=3DApple-style-span face=3DArial size=3D4><SPAN =
class=3DApple-style-span style=3D"FONT-SIZE: =
14px">draft-kkoushik-pce-pcep-mib-02.txt</SPAN></FONT></PRE><PRE =
style=3D"WORD-WRAP: break-word"><FONT class=3DApple-style-span =
face=3DArial size=3D4><SPAN class=3DApple-style-span style=3D"FONT-SIZE: =
14px"></SPAN></FONT></PRE>
  <DIV><SPAN class=3DApple-style-span><FONT class=3DApple-style-span =
face=3DArial=20
  size=3D4><SPAN class=3DApple-style-span=20
  style=3D"FONT-SIZE: 14px">Thanks.</SPAN></FONT></SPAN></DIV>
  <DIV><SPAN class=3DApple-style-span><FONT class=3DApple-style-span =
face=3DArial=20
  size=3D4><SPAN class=3DApple-style-span=20
  style=3D"FONT-SIZE: 14px"><BR></SPAN></FONT></SPAN></DIV>
  <DIV><SPAN class=3DApple-style-span><FONT class=3DApple-style-span =
face=3DArial=20
  size=3D4><SPAN class=3DApple-style-span=20
  style=3D"FONT-SIZE: =
14px">JP.</SPAN></FONT></SPAN></DIV></SPAN></DIV></BLOCKQUOTE></BODY></HT=
ML>

------=_NextPart_000_0048_01C94F2E.B18A4A90--


--===============1157143338==
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

--===============1157143338==--



From pce-bounces@ietf.org  Thu Nov 27 15:41: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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 876213A6AF4;
	Thu, 27 Nov 2008 15:41: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 8824A3A6B22
	for <pce@core3.amsl.com>; Thu, 27 Nov 2008 15:41:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.866
X-Spam-Level: 
X-Spam-Status: No, score=-1.866 tagged_above=-999 required=5 tests=[AWL=0.732, 
	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 T8Kiooz-EYv3 for <pce@core3.amsl.com>;
	Thu, 27 Nov 2008 15:41:55 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 812E03A6A2E
	for <pce@ietf.org>; Thu, 27 Nov 2008 15:41:53 -0800 (PST)
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
	mARNfYjC029180; Thu, 27 Nov 2008 23:41:35 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
	mARNfY2L029167; Thu, 27 Nov 2008 23:41:34 GMT
Message-ID: <3A07C62A84C14C739800C738E7716B3B@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Thu, 27 Nov 2008 23:37:43 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: [Pce] Path Key I-D : number of bits
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi,

To repeat something discussed briefly in Minneapolis (this was raised in 
CCAMP in discussion of draft-ietf-ccamp-path-key-ero-02.txt, but more 
properly applies to draft-ietf-pce-path-key-05.txt).

The path key subobject is formed as...

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |L|    Type     |     Length    |           Path Key            |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                         PCE ID (4 bytes)                      |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The question is: Are 16 bits enough for the Path Key? Isn't it possible that 
more than 2^16 path segments will be computed and "held" for possible 
expansion during signaling at any one time?

My feeling is that this would not be the case. The keys are relatively short 
lived, and can be recycled after a short safety period as described in the 
draft.

There are some special cases where resignaling of the LSP (from the head end 
with the same path key) would require the key to be held for longer, but the 
domain entry router can hold the key (in association with the session) to 
avoid any issues in this case.

Further, if there really are issues with depletion of keys, the PCE could 
use another PCE ID to create a further 2^16 keys.

What does the working group think?

Thanks,
Adrian


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


From pce-bounces@ietf.org  Thu Nov 27 21:53: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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB86C28C12C;
	Thu, 27 Nov 2008 21:53:55 -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 8440B28C0D9
	for <pce@core3.amsl.com>; Thu, 27 Nov 2008 21:53:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.436
X-Spam-Level: 
X-Spam-Status: No, score=-10.436 tagged_above=-999 required=5
	tests=[AWL=0.163, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 KeJOEqjZl7Lt for <pce@core3.amsl.com>;
	Thu, 27 Nov 2008 21:53:53 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id E6B3528C12C
	for <pce@ietf.org>; Thu, 27 Nov 2008 21:53:52 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,680,1220227200"; d="scan'208";a="27054477"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 28 Nov 2008 05:53:47 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mAS5rkPU002115; 
	Fri, 28 Nov 2008 06:53:46 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mAS5rkuU009120;
	Fri, 28 Nov 2008 05:53:46 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 28 Nov 2008 06:53:46 +0100
Received: from ams-jvasseur-8712.cisco.com ([10.55.201.131]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 28 Nov 2008 06:53:46 +0100
From: JP Vasseur <jvasseur@cisco.com>
To: Adrian Farrel <adrian@olddog.co.uk>
In-Reply-To: <3A07C62A84C14C739800C738E7716B3B@your029b8cecfe>
X-Priority: 3
References: <3A07C62A84C14C739800C738E7716B3B@your029b8cecfe>
Message-Id: <F6461931-1BDB-4A23-AC03-B854D89D460C@cisco.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Fri, 28 Nov 2008 06:53:45 +0100
X-Mailer: Apple Mail (2.926)
X-OriginalArrivalTime: 28 Nov 2008 05:53:46.0180 (UTC)
	FILETIME=[AD65C840:01C9511D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2008; t=1227851626;
	x=1228715626; c=relaxed/simple; s=amsdkim1002;
	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]=20Path=20Key=20I-D=20=3A=20number
	=20of=20bits |Sender:=20;
	bh=pKR9btivSlLy1XVj8tzWCGax3ZDViaxazs+xkcLYplU=;
	b=Mbu2HFNH/Eo6RPXXKtxo4bHDo6BFTz3FCQo6PlZNPW/Mlr4762uLa+rNQ+
	+NP1szYaM12vAGipe/qE3jo0tnUGt3+VXqiVcUgVUtRi7dOhEctqZ2wqrasZ
	oMf0IH9Cqp;
Authentication-Results: ams-dkim-1; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: pce@ietf.org
Subject: Re: [Pce] Path Key I-D : number of bits
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi Adrian,

I certainly share my opinion; I think that in realistic deployment  
we'll be very far from seeing 2^16 pending LSP computations at any  
given time.

Cheers,

JP.


On Nov 28, 2008, at 12:37 AM, Adrian Farrel wrote:

> Hi,
>
> To repeat something discussed briefly in Minneapolis (this was  
> raised in CCAMP in discussion of draft-ietf-ccamp-path-key- 
> ero-02.txt, but more properly applies to draft-ietf-pce-path- 
> key-05.txt).
>
> The path key subobject is formed as...
>
>    0                   1                   2                   3
>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |L|    Type     |     Length    |           Path Key            |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                         PCE ID (4 bytes)                      |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> The question is: Are 16 bits enough for the Path Key? Isn't it  
> possible that more than 2^16 path segments will be computed and  
> "held" for possible expansion during signaling at any one time?
>
> My feeling is that this would not be the case. The keys are  
> relatively short lived, and can be recycled after a short safety  
> period as described in the draft.
>
> There are some special cases where resignaling of the LSP (from the  
> head end with the same path key) would require the key to be held  
> for longer, but the domain entry router can hold the key (in  
> association with the session) to avoid any issues in this case.
>
> Further, if there really are issues with depletion of keys, the PCE  
> could use another PCE ID to create a further 2^16 keys.
>
> What does the working group think?
>
> 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 Nov 28 00:19:20 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF06C3A6A7C;
	Fri, 28 Nov 2008 00:19:20 -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 DA4633A6A7C
	for <pce@core3.amsl.com>; Fri, 28 Nov 2008 00:19:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Fz3yAR4dbkGI for <pce@core3.amsl.com>;
	Fri, 28 Nov 2008 00:19:17 -0800 (PST)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9])
	by core3.amsl.com (Postfix) with ESMTP id D8B983A6847
	for <pce@ietf.org>; Fri, 28 Nov 2008 00:19:17 -0800 (PST)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
	[138.85.77.51])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id mAS8M8Nq015039;
	Fri, 28 Nov 2008 02:22:11 -0600
Received: from eusrcmw721.eamcs.ericsson.se ([138.85.77.21]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 28 Nov 2008 02:19:11 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 28 Nov 2008 02:19:09 -0600
Message-ID: <941D5DCD8C42014FAF70FB7424686DCF04343620@eusrcmw721.eamcs.ericsson.se>
In-Reply-To: <3A07C62A84C14C739800C738E7716B3B@your029b8cecfe>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pce] Path Key I-D : number of bits
Thread-Index: AclQ6b2b9MZaImJ2SQaYHT5XTK/H0QAQ52Kw
References: <3A07C62A84C14C739800C738E7716B3B@your029b8cecfe>
From: "Eric Gray" <eric.gray@ericsson.com>
To: "Adrian Farrel" <adrian@olddog.co.uk>, <pce@ietf.org>
X-OriginalArrivalTime: 28 Nov 2008 08:19:11.0579 (UTC)
	FILETIME=[FE2402B0:01C95131]
Subject: Re: [Pce] Path Key I-D : number of bits
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

Adrian,

	I mostly agree with your reasoning.

	In the first case, it is probably going to be a too
interesting world in which we live if we can expect to get
close to exceeding this many current path keys for each of
potentially many PCEs.  This implies that we would expect
to see on the rough order of 64K traffic engineered multi
(adminstrative) domain LSPs for which it is necessary for
a subset of all PCEs to maintain active state information
relative to ongoing signaling transactions.  I dislike 
thinking about the number of actual steady-state traffic
engineered, multi (administrative) domain LSPs that might
be expected to exist when we expect this many to be in the
process of being setup at any time.  I also have trouble
imagining the application that would require orders of
magnitude more than 64K such multi domain TE LSPs.

	Also, if real-world implementations find it necessary
to exceed this number by (for example) 2 or 3 times, a need 
to maintain multiple PCE IDs is likely to be the least of 
the issues they will face.  

	However, should a need arise for orders of magnitude
greater numbers of path keys (for example, should it turn
out that there's a need to record assigned path key values
for some period of time - like 24 hours - for any reason),
then the approach of using multiple PCE IDs scales rather
poorly and would probably require more work.  For one thing, 
I am not sure how this would work; would the PCE from whom 
a path computation is requested be able to provide responses 
that specify a separate PCE ID?  Do we expect that both PCS 
and PCC implementations will be able to maintain state on 
orders of magnitude more PCE IDs?  Do extra PCE ID instances 
go away when no longer needed?

	Wasn't one of the options to possibly define another
subobject in the future - should the need arise?  If that
were the case, the current sub-object definition allows the
implementers today to scale their implementation resource 
needs to fit a smaller number of possible values we think
we might need in the near future, while leaving open the
the possibility of later implementations that support
larger values...

--
Eric Gray
Principal Engineer
Ericsson  

> -----Original Message-----
> From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On 
> Behalf Of Adrian Farrel
> Sent: Thursday, November 27, 2008 6:38 PM
> To: pce@ietf.org
> Subject: [Pce] Path Key I-D : number of bits
> 
> Hi,
> 
> To repeat something discussed briefly in Minneapolis (this was raised
> in CCAMP in discussion of draft-ietf-ccamp-path-key-ero-02.txt, but
> more properly applies to draft-ietf-pce-path-key-05.txt).
> 
> The path key subobject is formed as...
> 
>      0                   1                   2                   3
>      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |L|    Type     |     Length    |           Path Key            |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     |                         PCE ID (4 bytes)                      |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> The question is: Are 16 bits enough for the Path Key? Isn't it
possible
> that more than 2^16 path segments will be computed and "held" for 
> possible expansion during signaling at any one time?
> 
> My feeling is that this would not be the case. The keys are relatively
> short lived, and can be recycled after a short safety period as 
> described in the draft.
> 
> There are some special cases where resignaling of the LSP (from the
> head end with the same path key) would require the key to be held for 
> longer, but the domain entry router can hold the key (in association
> with the session) to avoid any issues in this case.
> 
> Further, if there really are issues with depletion of keys, the PCE
> could use another PCE ID to create a further 2^16 keys.
> 
> What does the working group think?
> 
> 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 Nov 28 03:04: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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8FBF23A6AD4;
	Fri, 28 Nov 2008 03:04:37 -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 270963A6AD4
	for <pce@core3.amsl.com>; Fri, 28 Nov 2008 03:04:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.751
X-Spam-Level: 
X-Spam-Status: No, score=-0.751 tagged_above=-999 required=5
	tests=[AWL=-0.567, BAYES_40=-0.185, 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 WG-jxa4dSMtB for <pce@core3.amsl.com>;
	Fri, 28 Nov 2008 03:04:35 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 3A4A23A68EB
	for <pce@ietf.org>; Fri, 28 Nov 2008 03:04:35 -0800 (PST)
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
	mASB4SH8022745 for <pce@ietf.org>; Fri, 28 Nov 2008 11:04:30 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
	mASB4Rj3022733 for <pce@ietf.org>; Fri, 28 Nov 2008 11:04:28 GMT
Message-ID: <461121D3F9E44400B97FCF44B3709196@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
References: <3A07C62A84C14C739800C738E7716B3B@your029b8cecfe>
	<941D5DCD8C42014FAF70FB7424686DCF04343620@eusrcmw721.eamcs.ericsson.se>
Date: Fri, 28 Nov 2008 11:04:25 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: Re: [Pce] Path Key I-D : number of bits
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi Eric,

> Wasn't one of the options to possibly define another
> subobject in the future - should the need arise?

Yes. We always have that option.
And if we believe 2^16 is enough for the foreseeable future, then we have 
nothing more to do at the moment.

As JP says...

> I certainly share my opinion;

Which is good to know :-)

Adrian 

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


From pce-bounces@ietf.org  Fri Nov 28 14:38:15 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3CB993A6994;
	Fri, 28 Nov 2008 14:38:15 -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 19BBC3A6994
	for <pce@core3.amsl.com>; Fri, 28 Nov 2008 14:38:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level: 
X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[AWL=0.186, 
	BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 ItMfwYDRGJVS for <pce@core3.amsl.com>;
	Fri, 28 Nov 2008 14:38:13 -0800 (PST)
Received: from outbound-mail-104.bluehost.com (outbound-mail-104.bluehost.com
	[69.89.22.14]) by core3.amsl.com (Postfix) with SMTP id 598D93A6824
	for <pce@ietf.org>; Fri, 28 Nov 2008 14:38:13 -0800 (PST)
Received: (qmail 21894 invoked by uid 0); 28 Nov 2008 22:38:07 -0000
Received: from unknown (HELO box474.bluehost.com) (74.220.219.74)
	by outboundproxy3.bluehost.com with SMTP; 28 Nov 2008 22:38:07 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net;
	h=Received:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To:References:Mime-Version:Content-Type:X-Identified-User;
	b=HFoqxlOHZJON742yhvgXE3hKpBUit4R7Mr5aFKHfTVH2aZnkMRZdE9xjR7miVIPm/ziYeqLCFNqVfuXTFzQxs6473LoxVKEkWooBUXPjEwYLfAhdFLGp9O4HePHSja38;
Received: from box474.bluehost.com ([74.220.219.74] helo=LC2.labn.net)
	by box474.bluehost.com with esmtpa (Exim 4.69)
	(envelope-from <lberger@labn.net>)
	id 1L6ByQ-00013Y-2s; Fri, 28 Nov 2008 15:38:06 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 28 Nov 2008 17:38:03 -0500
To: "Adrian Farrel" <adrian@olddog.co.uk>
From: Lou Berger <lberger@labn.net>
In-Reply-To: <3A07C62A84C14C739800C738E7716B3B@your029b8cecfe>
References: <3A07C62A84C14C739800C738E7716B3B@your029b8cecfe>
Mime-Version: 1.0
X-Identified-User: {2629:box474.bluehost.com:labnmobi:labn.net} {sentby:smtp
	auth 74.220.219.74 authed with lberger@labn.net}
Message-Id: <20081128223813.598D93A6824@core3.amsl.com>
Cc: pce@ietf.org
Subject: Re: [Pce] Path Key I-D : number of bits
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

So bits in this object are cheap and a 32 bit key would allow for 
potential future cases that we can already envision as well as 
today's known cases.  (BTW I know of one experimental usage of PCE 
that I suspect will want this immediately.)  IMO optimizing the 
subobject by 2/4 bytes is completely unwarranted.

Now, that said, it is quite late in the process to raise this 
point.  (mea culpa.) If the only impact of this change is a minor 
delay in progressing the documents, then I think we should make the 
change now.  On the other hand, if changing this now also impacts 
implementations, I think we should only support longer keys once 
there is real (not today's theoretical) demand for them.

So, IMO we should make this change based on implementation impact.

Is there anyone with an implementation who wants to weigh in on the 
real/practical impact to them on this change?

Lou

At 06:37 PM 11/27/2008, Adrian Farrel wrote:
>Hi,
>
>To repeat something discussed briefly in Minneapolis (this was 
>raised in CCAMP in discussion of 
>draft-ietf-ccamp-path-key-ero-02.txt, but more properly applies to 
>draft-ietf-pce-path-key-05.txt).
>
>The path key subobject is formed as...
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |L|    Type     |     Length    |           Path Key            |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                         PCE ID (4 bytes)                      |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>The question is: Are 16 bits enough for the Path Key? Isn't it 
>possible that more than 2^16 path segments will be computed and 
>"held" for possible expansion during signaling at any one time?
>
>My feeling is that this would not be the case. The keys are 
>relatively short lived, and can be recycled after a short safety 
>period as described in the draft.
>
>There are some special cases where resignaling of the LSP (from the 
>head end with the same path key) would require the key to be held 
>for longer, but the domain entry router can hold the key (in 
>association with the session) to avoid any issues in this case.
>
>Further, if there really are issues with depletion of keys, the PCE 
>could use another PCE ID to create a further 2^16 keys.
>
>What does the working group think?
>
>Thanks,
>Adrian
>
>
>

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


From pce-bounces@ietf.org  Sat Nov 29 05:06:08 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3995A3A689B;
	Sat, 29 Nov 2008 05:06:08 -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 838683A689B
	for <pce@core3.amsl.com>; Sat, 29 Nov 2008 05:06:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.469
X-Spam-Level: 
X-Spam-Status: No, score=-10.469 tagged_above=-999 required=5
	tests=[AWL=0.130, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 1n8v8b+wQeSw for <pce@core3.amsl.com>;
	Sat, 29 Nov 2008 05:06:05 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id AB8A83A680D
	for <pce@ietf.org>; Sat, 29 Nov 2008 05:06:04 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,687,1220227200"; d="scan'208";a="27169855"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 29 Nov 2008 13:05:56 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mATD5uIQ012216; 
	Sat, 29 Nov 2008 14:05:56 +0100
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mATD5uY2019022;
	Sat, 29 Nov 2008 13:05:56 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 29 Nov 2008 14:05:56 +0100
Received: from ams-jvasseur-8714.cisco.com ([10.55.201.133]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 29 Nov 2008 14:05:46 +0100
Message-Id: <21EC8840-183F-49AD-A5FA-77EC580221F7@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: Lou Berger <lberger@labn.net>
In-Reply-To: <20081128223813.598D93A6824@core3.amsl.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Sat, 29 Nov 2008 14:05:46 +0100
References: <3A07C62A84C14C739800C738E7716B3B@your029b8cecfe>
	<20081128223813.598D93A6824@core3.amsl.com>
X-Mailer: Apple Mail (2.926)
X-OriginalArrivalTime: 29 Nov 2008 13:05:46.0842 (UTC)
	FILETIME=[31BAABA0:01C95223]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3061; t=1227963956;
	x=1228827956; c=relaxed/simple; s=amsdkim1002;
	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]=20Path=20Key=20I-D=20=3A=20number
	=20of=20bits |Sender:=20;
	bh=lkfm1A4l0496GFoOSJKxkc8rYtYiGm2YhjeGbvuEeKs=;
	b=RzYi/ONSN9/f1B4PJI3LwJMcdcNoszVpgX6xeJqmtp6ZyZTuUvy7JSp1xN
	y5BOqjy6orSnNw73VIPIcd63aM5ZYOL5UvC94fgRZBamYW5qk7uzo5kuYArj
	pMWNyRmU2b;
Authentication-Results: ams-dkim-1; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: pce@ietf.org
Subject: Re: [Pce] Path Key I-D : number of bits
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org


On Nov 28, 2008, at 11:38 PM, Lou Berger wrote:

> So bits in this object are cheap and a 32 bit key would allow for  
> potential future cases that we can already envision as well as  
> today's known cases.  (BTW I know of one experimental usage of PCE  
> that I suspect will want this immediately.)

Well, I may make a comment: in this case, I can see a *number* of  
issues that they will be facing if they have a model where you can end  
up with more than 65 K pending requests ...

>  IMO optimizing the subobject by 2/4 bytes is completely unwarranted.
>
> Now, that said, it is quite late in the process to raise this  
> point.  (mea culpa.) If the only impact of this change is a minor  
> delay in progressing the documents, then I think we should make the  
> change now.  On the other hand, if changing this now also impacts  
> implementations, I think we should only support longer keys once  
> there is real (not today's theoretical) demand for them.
>
> So, IMO we should make this change based on implementation impact.
>
> Is there anyone with an implementation who wants to weigh in on the  
> real/practical impact to them on this change?
>
> Lou
>
> At 06:37 PM 11/27/2008, Adrian Farrel wrote:
>> Hi,
>>
>> To repeat something discussed briefly in Minneapolis (this was  
>> raised in CCAMP in discussion of draft-ietf-ccamp-path-key- 
>> ero-02.txt, but more properly applies to draft-ietf-pce-path- 
>> key-05.txt).
>>
>> The path key subobject is formed as...
>>
>>    0                   1                   2                   3
>>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>   |L|    Type     |     Length    |           Path Key            |
>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>   |                         PCE ID (4 bytes)                      |
>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>> The question is: Are 16 bits enough for the Path Key? Isn't it  
>> possible that more than 2^16 path segments will be computed and  
>> "held" for possible expansion during signaling at any one time?
>>
>> My feeling is that this would not be the case. The keys are  
>> relatively short lived, and can be recycled after a short safety  
>> period as described in the draft.
>>
>> There are some special cases where resignaling of the LSP (from the  
>> head end with the same path key) would require the key to be held  
>> for longer, but the domain entry router can hold the key (in  
>> association with the session) to avoid any issues in this case.
>>
>> Further, if there really are issues with depletion of keys, the PCE  
>> could use another PCE ID to create a further 2^16 keys.
>>
>> What does the working group think?
>>
>> 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 Nov 29 07:31: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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7AB433A6872;
	Sat, 29 Nov 2008 07:31: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 2D7293A6897
	for <pce@core3.amsl.com>; Sat, 29 Nov 2008 06:58:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.846
X-Spam-Level: 
X-Spam-Status: No, score=-4.846 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
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 UU58HsrLt2Et for <pce@core3.amsl.com>;
	Sat, 29 Nov 2008 06:58:32 -0800 (PST)
Received: from smtp04.bis.na.blackberry.com (smtp04.bis.na.blackberry.com
	[216.9.248.51]) by core3.amsl.com (Postfix) with ESMTP id 25CE83A67AE
	for <pce@ietf.org>; Sat, 29 Nov 2008 06:58:31 -0800 (PST)
Received: from bxe126.bisx.prod.on.blackberry (bxe126.bisx.prod.on.blackberry
	[172.20.225.155])
	by srs.bis.na.blackberry.com (8.13.7 TEAMON/8.13.7) with ESMTP id
	mATEpKIY030703; Sat, 29 Nov 2008 14:58:47 GMT
X-rim-org-msg-ref-id: 1813186841
Message-ID: <1813186841-1227970708-cardhu_decombobulator_blackberry.rim.net-1312515812-@bxe126.bisx.prod.on.blackberry>
X-Priority: Normal
References: <3A07C62A84C14C739800C738E7716B3B@your029b8cecfe>
	<20081128223813.598D93A6824@core3.amsl.com><21EC8840-183F-49AD-A5FA-77EC580221F7@cisco.com>
In-Reply-To: <21EC8840-183F-49AD-A5FA-77EC580221F7@cisco.com>
Sensitivity: Normal
Importance: Normal
To: "JP Vasseur" <jvasseur@cisco.com>, "Lou Berger" <lberger@labn.net>
From: "Lou Berger" <lberger@labn.net>
Date: Sat, 29 Nov 2008 14:58:25 +0000
MIME-Version: 1.0
Cc: pce@ietf.org
Subject: Re: [Pce] Path Key I-D : number of bits
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: lberger@labn.net
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

Sure, but that's their *implementation* issue. Standards don't stop you from doing something stupid, but they shouln't stop you from doing something intelligent/creative either...

Lou
-----Original Message-----
From: JP Vasseur <jvasseur@cisco.com>

Date: Sat, 29 Nov 2008 14:05:46 
To: Lou Berger<lberger@labn.net>
Cc: Adrian Farrel<adrian@olddog.co.uk>; <pce@ietf.org>
Subject: Re: [Pce] Path Key I-D : number of bits



On Nov 28, 2008, at 11:38 PM, Lou Berger wrote:

> So bits in this object are cheap and a 32 bit key would allow for
> potential future cases that we can already envision as well as
> today's known cases.  (BTW I know of one experimental usage of PCE
> that I suspect will want this immediately.)

Well, I may make a comment: in this case, I can see a *number* of
issues that they will be facing if they have a model where you can end
up with more than 65 K pending requests ...

>  IMO optimizing the subobject by 2/4 bytes is completely unwarranted.
>
> Now, that said, it is quite late in the process to raise this
> point.  (mea culpa.) If the only impact of this change is a minor
> delay in progressing the documents, then I think we should make the
> change now.  On the other hand, if changing this now also impacts
> implementations, I think we should only support longer keys once
> there is real (not today's theoretical) demand for them.
>
> So, IMO we should make this change based on implementation impact.
>
> Is there anyone with an implementation who wants to weigh in on the
> real/practical impact to them on this change?
>
> Lou
>
> At 06:37 PM 11/27/2008, Adrian Farrel wrote:
>> Hi,
>>
>> To repeat something discussed briefly in Minneapolis (this was
>> raised in CCAMP in discussion of draft-ietf-ccamp-path-key-
>> ero-02.txt, but more properly applies to draft-ietf-pce-path-
>> key-05.txt).
>>
>> The path key subobject is formed as...
>>
>>    0                   1                   2                   3
>>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>   |L|    Type     |     Length    |           Path Key            |
>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>   |                         PCE ID (4 bytes)                      |
>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>> The question is: Are 16 bits enough for the Path Key? Isn't it
>> possible that more than 2^16 path segments will be computed and
>> "held" for possible expansion during signaling at any one time?
>>
>> My feeling is that this would not be the case. The keys are
>> relatively short lived, and can be recycled after a short safety
>> period as described in the draft.
>>
>> There are some special cases where resignaling of the LSP (from the
>> head end with the same path key) would require the key to be held
>> for longer, but the domain entry router can hold the key (in
>> association with the session) to avoid any issues in this case.
>>
>> Further, if there really are issues with depletion of keys, the PCE
>> could use another PCE ID to create a further 2^16 keys.
>>
>> What does the working group think?
>>
>> 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  Sun Nov 30 01:47:09 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E5D793A6883;
	Sun, 30 Nov 2008 01:47:09 -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 C26F43A6883
	for <pce@core3.amsl.com>; Sun, 30 Nov 2008 01:47:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.491
X-Spam-Level: 
X-Spam-Status: No, score=-10.491 tagged_above=-999 required=5
	tests=[AWL=0.108, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 B4f4FLk+eG6x for <pce@core3.amsl.com>;
	Sun, 30 Nov 2008 01:47:07 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 3AECC3A67AA
	for <pce@ietf.org>; Sun, 30 Nov 2008 01:47:07 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,689,1220227200"; d="scan'208";a="27194554"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 30 Nov 2008 09:47:02 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mAU9l2oU008387; 
	Sun, 30 Nov 2008 10:47:02 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mAU9l22M009787;
	Sun, 30 Nov 2008 09:47:02 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 30 Nov 2008 10:47:02 +0100
Received: from ams-jvasseur-8714.cisco.com ([10.55.201.133]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 30 Nov 2008 10:47:01 +0100
From: JP Vasseur <jvasseur@cisco.com>
To: lberger@labn.net
In-Reply-To: <1813186841-1227970708-cardhu_decombobulator_blackberry.rim.net-1312515812-@bxe126.bisx.prod.on.blackberry>
X-Priority: Normal
References: <3A07C62A84C14C739800C738E7716B3B@your029b8cecfe>
	<20081128223813.598D93A6824@core3.amsl.com><21EC8840-183F-49AD-A5FA-77EC580221F7@cisco.com>
	<1813186841-1227970708-cardhu_decombobulator_blackberry.rim.net-1312515812-@bxe126.bisx.prod.on.blackberry>
Message-Id: <B0222F49-EC6C-4811-B7C2-A4053B5222F9@cisco.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Sun, 30 Nov 2008 10:47:00 +0100
X-Mailer: Apple Mail (2.926)
X-OriginalArrivalTime: 30 Nov 2008 09:47:01.0775 (UTC)
	FILETIME=[983F99F0:01C952D0]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3723; t=1228038422;
	x=1228902422; c=relaxed/simple; s=amsdkim2001;
	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]=20Path=20Key=20I-D=20=3A=20number
	=20of=20bits |Sender:=20;
	bh=MPtc0bnki2ZyU9uCxVd1I//CkJVnrsvZ/+BB8RN15Co=;
	b=SsoQjZMMbQV4rOViBSMRnzRhQdzromdceqaYDjv0xwJcLyhAGIoFoVPByw
	jUFI66rtUoLTDyKV9yrEjNRtPxdTwXz/Pg6feKHt63uYNhBeXDobcm91sLHC
	LXVIFELzxr;
Authentication-Results: ams-dkim-2; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: pce@ietf.org
Subject: Re: [Pce] Path Key I-D : number of bits
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org


On Nov 29, 2008, at 3:58 PM, Lou Berger wrote:

> Sure, but that's their *implementation* issue. Standards don't stop  
> you from doing something stupid,

Well standard should at least "warn" you from doing something stupid ...

> but they shouln't stop you from doing something intelligent/creative  
> either...
>

Surely.

Cheers,

JP.

> Lou
> -----Original Message-----
> From: JP Vasseur <jvasseur@cisco.com>
>
> Date: Sat, 29 Nov 2008 14:05:46
> To: Lou Berger<lberger@labn.net>
> Cc: Adrian Farrel<adrian@olddog.co.uk>; <pce@ietf.org>
> Subject: Re: [Pce] Path Key I-D : number of bits
>
>
>
> On Nov 28, 2008, at 11:38 PM, Lou Berger wrote:
>
>> So bits in this object are cheap and a 32 bit key would allow for
>> potential future cases that we can already envision as well as
>> today's known cases.  (BTW I know of one experimental usage of PCE
>> that I suspect will want this immediately.)
>
> Well, I may make a comment: in this case, I can see a *number* of
> issues that they will be facing if they have a model where you can end
> up with more than 65 K pending requests ...
>
>> IMO optimizing the subobject by 2/4 bytes is completely unwarranted.
>>
>> Now, that said, it is quite late in the process to raise this
>> point.  (mea culpa.) If the only impact of this change is a minor
>> delay in progressing the documents, then I think we should make the
>> change now.  On the other hand, if changing this now also impacts
>> implementations, I think we should only support longer keys once
>> there is real (not today's theoretical) demand for them.
>>
>> So, IMO we should make this change based on implementation impact.
>>
>> Is there anyone with an implementation who wants to weigh in on the
>> real/practical impact to them on this change?
>>
>> Lou
>>
>> At 06:37 PM 11/27/2008, Adrian Farrel wrote:
>>> Hi,
>>>
>>> To repeat something discussed briefly in Minneapolis (this was
>>> raised in CCAMP in discussion of draft-ietf-ccamp-path-key-
>>> ero-02.txt, but more properly applies to draft-ietf-pce-path-
>>> key-05.txt).
>>>
>>> The path key subobject is formed as...
>>>
>>>   0                   1                   2                   3
>>>   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>  |L|    Type     |     Length    |           Path Key            |
>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>  |                         PCE ID (4 bytes)                      |
>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>
>>> The question is: Are 16 bits enough for the Path Key? Isn't it
>>> possible that more than 2^16 path segments will be computed and
>>> "held" for possible expansion during signaling at any one time?
>>>
>>> My feeling is that this would not be the case. The keys are
>>> relatively short lived, and can be recycled after a short safety
>>> period as described in the draft.
>>>
>>> There are some special cases where resignaling of the LSP (from the
>>> head end with the same path key) would require the key to be held
>>> for longer, but the domain entry router can hold the key (in
>>> association with the session) to avoid any issues in this case.
>>>
>>> Further, if there really are issues with depletion of keys, the PCE
>>> could use another PCE ID to create a further 2^16 keys.
>>>
>>> What does the working group think?
>>>
>>> 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  Sun Nov 30 03:58:17 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 [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 62B763A68C5;
	Sun, 30 Nov 2008 03:58:17 -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 A683D3A68C5
	for <pce@core3.amsl.com>; Sun, 30 Nov 2008 03:58:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.439
X-Spam-Level: 
X-Spam-Status: No, score=-0.439 tagged_above=-999 required=5
	tests=[AWL=-0.441, 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 OVu7CDTLQ1QC for <pce@core3.amsl.com>;
	Sun, 30 Nov 2008 03:58:16 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id B424B3A689D
	for <pce@ietf.org>; Sun, 30 Nov 2008 03:58:14 -0800 (PST)
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
	mAUBw4Xa001870 for <pce@ietf.org>; Sun, 30 Nov 2008 11:58:07 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
	mAUBw46V001864 for <pce@ietf.org>; Sun, 30 Nov 2008 11:58:04 GMT
Message-ID: <D0DAF106CEDF43DCBC3F8F06E3C3E10E@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Sun, 30 Nov 2008 11:58:01 -0000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: [Pce] Drafts ready for last call
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi,

In Minneapolis we identify several drafts ready for last call.

draft-ietf-pce-global-concurrent-optimization
draft-ietf-pce-monitoring
draft-ietf-pce-inter-layer-frwk
draft-ietf-pce-p2mp-app

We have decided to last call these one at a time to give a bit more space 
for people to read them.

The first last call has already started (GCO) and we hope to follow on with 
the others through December and January.

Thanks,
Adrian and JP 

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


