From pce-bounces@ietf.org  Mon Dec  1 07:27: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 B2EB13A6A8F;
	Mon,  1 Dec 2008 07:27: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 9B07B3A6AB6
	for <pce@core3.amsl.com>; Mon,  1 Dec 2008 07:27:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level: 
X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[AWL=0.163, 
	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 Mfkkspy1hAlm for <pce@core3.amsl.com>;
	Mon,  1 Dec 2008 07:27:22 -0800 (PST)
Received: from outbound-mail-301.bluehost.com (outbound-mail-301.bluehost.com
	[67.222.53.8]) by core3.amsl.com (Postfix) with SMTP id 8AF933A6AAE
	for <pce@ietf.org>; Mon,  1 Dec 2008 07:27:22 -0800 (PST)
Received: (qmail 19543 invoked by uid 0); 1 Dec 2008 15:24:59 -0000
Received: from unknown (HELO box474.bluehost.com) (74.220.219.74)
	by outboundproxy6.bluehost.com with SMTP; 1 Dec 2008 15:24:59 -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=uzV6a7PvxCJymMagKae0QA9qVIgy0rA+OesiL/F0iPY9tICjR4F6k+Jq+QRPZvaYf7tH+aFN2FpsMxG+NcctrAYWdK8Pw5gY8pkqCAS2bWSH7Kdn3UmWiyb53rHokUKF;
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 1L7Aef-0007XB-NC; Mon, 01 Dec 2008 08:25:45 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 01 Dec 2008 10:25:45 -0500
To: JP Vasseur <jvasseur@cisco.com>
From: Lou Berger <lberger@labn.net>
In-Reply-To: <B0222F49-EC6C-4811-B7C2-A4053B5222F9@cisco.com>
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>
	<B0222F49-EC6C-4811-B7C2-A4053B5222F9@cisco.com>
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: <20081201152722.8AF933A6AAE@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

that's what "SHOULD" is for...

At 04:47 AM 11/30/2008, JP Vasseur wrote:

>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 pcdyer@zoominternet.net  Fri Dec  5 18:50:04 2008
Return-Path: <pcdyer@zoominternet.net>
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 CA54D3A69CD
	for <ietfarch-pce-archive@core3.amsl.com>; Fri,  5 Dec 2008 18:50:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.352
X-Spam-Level: 
X-Spam-Status: No, score=-0.352 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597,
	FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999,
	FM_SEX_HELODDDD=10.357, FM_SEX_HOSTDDDD=10.357, GB_H_PHARMACY=1,
	GB_PHARMACY=1, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR=2.426,
	HOST_EQ_DHCP=1.295, HTML_IMAGE_RATIO_04=0.172, HTML_MESSAGE=0.001,
	IP_NOT_FRIENDLY=0.334, MIME_HTML_ONLY=1.457,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5,
	RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1,
	URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10,
	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 TUfGn5w1ZvLC for <ietfarch-pce-archive@core3.amsl.com>;
	Fri,  5 Dec 2008 18:49:58 -0800 (PST)
Received: from fl-67-233-162-95.dhcp.embarqhsd.net (fl-67-233-162-95.dhcp.embarqhsd.net [67.233.162.95])
	by core3.amsl.com (Postfix) with SMTP id C6B5B3A682A
	for <pce-archive@ietf.org>; Fri,  5 Dec 2008 18:49:56 -0800 (PST)
Content-Return: allowed 
X-Mailer: CME-V6.5.4.3; MSN 
Received: (qmail 20086 by uid 129); Fri, 5 Dec 2008 09:50:15 -0500
Message-Id: <20081205045015.20088.qmail@fl-67-233-162-95.dhcp.embarqhsd.net>
To: <pce-archive@ietf.org>
Subject:Pharmacy mall: everything for your sex! 
From: <pce-archive@ietf.org>
MIME-Version: 1.0
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Date: Fri,  5 Dec 2008 18:49:56 -0800 (PST)

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>Stylish Vacation</title>
</head>

<body>
<center>
<table width="100%" border="0" cellpadding="0" cellspacing="0" bgcolor="#e0fefc" style="color: #b4b3b3; font-family: verdana, arial, helvetica, sans-serif; font-size: 10px;" >
	<tr>
		<td bgcolor="#e0fefc"><img style="display:block" src="http://www.ice.com/content/newsletter/june/spacer.gif" width="1" height="30" border="0" alt="" /></td>
	</tr>
	<tr>
	  <td bgcolor="#e0fefc" style="text-align: center;">
	  You have told us you would like to receive exciting email offers from us.<br /></td>
	</tr>
	<tr>
		<td bgcolor="#e0fefc"><img style="display:block" src="http://www.ice.com/content/newsletter/june/spacer.gif" width="1" height="10" border="0" alt="" /></td>
	</tr>
	<tr>
		<td style="text-align: left;"><center><table width="531" border="0" cellpadding="0" cellspacing="0" bgcolor="#50dee0" style="text-align: left;" >
			<tr>
				<td width="5"><img style="display:block" src="http://www.ice.com/content/newsletter/june/spacer.gif" width="5" height="1" border="0" alt="" /></td>
				<td width="521"><table width="521" border="0" cellpadding="0" cellspacing="0" style="font-family: arial, helvetica, verdana, sans-serif; font-size: 11px;">
					<tr>
						<td><img style="display:block" src="http://www.ice.com/content/newsletter/june/spacer.gif" width="1" height="5" border="0" alt="" /></td>
					</tr>
					<tr>
						<td><a href="http://www.pagefather.com"><img style="display:block" border="0" src="http://www.ice.com/content/newsletter/june/0608_vacation_mast_head.jpg" height="276" width="521" alt="Get Ready For Wedding Season, Save Today" /></a></td>
				  </tr>
					<tr>
						<td align="left" bgcolor="#ebfdfd" style="color: #18a49b; font-size: 13px; ">
							<div style="padding: 15px 15px 15px 15px;">
							  <div style="line-height: 15px; width: 491;">
							    <p>The sun is getting hotter, the days are getting longer, and summer vacations are almost here! Prepare to create some unforgettable memories with this stunning collection – perfect to keep you Stylish On Vacation! </p>
							    <p><a href="http://www.pagefather.com"><img src="http://mediapix.ru/pics/bad5d43d6b3083a8648bd1d2676f2811.gif" border="0" /></a><br/>
						          <br />
						          </p>
							  </div>
							</div>						</td>
					</tr>
					<tr>
						<td> </td>
					</tr>
					<tr>
						<td bgcolor="#d3fef5">
							<div style="padding: 15px 10px 15px 10px;">
								<div style="background-color: #d3fef5; color: #6b6c6e; font-family: arial, helvetica, verdana, sans-serif; font-size: 10px; text-align: center; width: 501px;">
									<span style="font-size: 12px; font-weight: bold; ">Satisfaction Guaranteed - </span>
									We want you to be absolutely satisfied with your pharmacy.<br/>
									Enjoy it.  If, within 30 days after receipt of your 
									purchase you're not completely<br/> 
									satisfied, return it for the price you paid or we will gladly replace it.								</div>
							</div>						</td>
					</tr>
					<tr>
						<td><img style="display:block" src="http://www.ice.com/content/newsletter/june/spacer.gif" width="1" height="5" border="0" alt="" /></td>
					</tr>
				</table></td>
				<td width="5"><img style="display:block" src="http://www.ice.com/content/newsletter/june/spacer.gif" width="5" height="1" border="0" alt="" /></td>
			</tr>
		</table> 
		</center>
		</td>
	</tr>
	<tr>
		<td bgcolor="#e9f7fb"><img style="display:block" src="http://www.ice.com/content/newsletter/june/spacer.gif" width="1" height="10" border="0" alt="" /></td>
	</tr>
	<tr>
		<td bgcolor="#e9f7fb">
			<center>
			</center>
    </td>
	</tr>
	<tr>
		<td bgcolor="#e9f7fb"><img style="display:block" src="http://www.ice.com/content/newsletter/june/spacer.gif" width="1" height="30" border="0" alt="" /></td>
	</tr>
</table>
</center>

<IMG ALT="" SRC="http://mailer.ice.com/db/65216/2558966/1.gif" WIDTH=1 HEIGHT=1></body>
</html>




From mail@alapassion.com  Sat Dec  6 23:17:19 2008
Return-Path: <mail@alapassion.com>
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 9006C3A6866
	for <ietfarch-pce-archive@core3.amsl.com>; Sat,  6 Dec 2008 23:17:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.991
X-Spam-Level: 
X-Spam-Status: No, score=-1.991 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597,
	FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888,
	FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295,
	HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DSL=1.129, HELO_EQ_DYNAMIC=1.144,
	HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001,
	HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5,
	RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1,
	SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, TVD_RCVD_IP=1.931,
	URIBL_AB_SURBL=10, 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 hg8WoOJtBnqS for <ietfarch-pce-archive@core3.amsl.com>;
	Sat,  6 Dec 2008 23:17:19 -0800 (PST)
Received: from 88-107-182-70.dynamic.dsl.as9105.com (88-107-182-70.dynamic.dsl.as9105.com [88.107.182.70])
	by core3.amsl.com (Postfix) with SMTP id DC45E3A6842
	for <pce-archive@ietf.org>; Sat,  6 Dec 2008 23:17:14 -0800 (PST)
To: <pce-archive@ietf.org>
Subject: Your order
From: <pce-archive@ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20081207071715.DC45E3A6842@core3.amsl.com>
Date: Sat,  6 Dec 2008 23:17:14 -0800 (PST)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
</HEAD>
<BODY><a href="http://valuetoward.com/" target="_blank">
<img src="http://valuetoward.com/adv3.jpg" border=0 alt="Click to visit Official Web Site!"></a></BODY></HTML>


From pce-bounces@ietf.org  Mon Dec  8 00:18:56 2008
Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 448763A6A1E;
	Mon,  8 Dec 2008 00:18:56 -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 14AD73A6A1E
	for <pce@core3.amsl.com>; Mon,  8 Dec 2008 00:18:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.576
X-Spam-Level: 
X-Spam-Status: No, score=-0.576 tagged_above=-999 required=5
	tests=[AWL=-1.569, BAYES_50=0.001, DATE_IN_PAST_12_24=0.992]
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 vU3kX005Kbvy for <pce@core3.amsl.com>;
	Mon,  8 Dec 2008 00:18:54 -0800 (PST)
Received: from protext01.itu.ch (protext01.itu.ch [156.106.192.41])
	by core3.amsl.com (Postfix) with ESMTP id 24ACC3A67A3
	for <pce@ietf.org>; Mon,  8 Dec 2008 00:18:52 -0800 (PST)
Received: from protext01.itu.ch ([156.106.192.41]) by protext01.itu.ch with
	Microsoft SMTPSVC(5.0.2195.6713); Mon, 8 Dec 2008 09:18:44 +0100
Received: From mail6.itu.ch ([156.106.192.22]) by protext01.itu.ch (WebShield
	SMTP v4.5 MR3) id 1228724301726; Mon, 8 Dec 2008 09:18:21 +0100
Received: from your029b8cecfe ([156.106.216.154])
	by mail6.itu.ch (8.14.3/8.14.3) with ESMTP id mB88I6Ci486304
	for <pce@ietf.org>; Mon, 8 Dec 2008 09:18:21 +0100 (MET)
Message-ID: <4068C5339EE24F84822EAD91D1E39BE2@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
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>
	<B0222F49-EC6C-4811-B7C2-A4053B5222F9@cisco.com>
	<200812011526.mB1FQEqS024778@mta5.iomartmail.com>
Date: Sun, 7 Dec 2008 10:54:17 -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
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0
	(mail6.itu.ch [156.106.192.22]);
	Mon, 08 Dec 2008 09:18:21 +0100 (MET)
X-OriginalArrivalTime: 08 Dec 2008 08:18:44.0039 (UTC)
	FILETIME=[95DB3D70:01C9590D]
Subject: [Pce] Conclusion on 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,

I don't see a lot of support for Lou's suggestion of having more than 16 
bits for the path key.

Lou points out that standards...
>>>shouln't stop you from doing something intelligent/creative

While the idea would certainly leave future implementations plenty of room 
to do clever things, we haven't had any indication that there is a pressing 
requirement for this change.

Lou wrote...
>>>>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.)

But this leaves us guessing, and without some further hints I don't think we 
can make a change based on this level of evidence.

In conclusion, Lou also said...
>>>>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.

Since I have been told of successful interop test of the current definition, 
I suggest we leave things as they are.
If 32 bits (or more!) become a requirement in the future, we can develop a 
new subobject.

Cheers,
Adrian 


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


From pce-bounces@ietf.org  Tue Dec  9 07:36: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 F22773A6B2D;
	Tue,  9 Dec 2008 07:36:14 -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 83BEB3A6B2D
	for <pce@core3.amsl.com>; Tue,  9 Dec 2008 07:36:13 -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_20=-0.74, HELO_EQ_FR=0.35, 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 0rjRlqrMlluv for <pce@core3.amsl.com>;
	Tue,  9 Dec 2008 07:36:09 -0800 (PST)
Received: from smtp4.int-evry.fr (smtp4.int-evry.fr [157.159.10.71])
	by core3.amsl.com (Postfix) with ESMTP id 16F303A67B2
	for <pce@ietf.org>; Tue,  9 Dec 2008 07:36:09 -0800 (PST)
Received: from smtp2.int-evry.fr (smtp2.int-evry.fr [157.159.10.45])
	by smtp4.int-evry.fr (Postfix) with ESMTP id 03DF8FE2E57
	for <pce@ietf.org>; Tue,  9 Dec 2008 16:36:03 +0100 (CET)
Received: from ISHWANG (unknown [157.159.103.30])
	by smtp2.int-evry.fr (Postfix) with ESMTP id 33F7F405110
	for <pce@ietf.org>; Tue,  9 Dec 2008 16:34:36 +0100 (CET)
From: "Iksoon Hwang" <Iksoon.Hwang@it-sudparis.eu>
To: <pce@ietf.org>
Date: Tue, 9 Dec 2008 16:34:32 +0100
Message-ID: <2DC0DAA7437948DD9285AD6F244ED7F7@ISHWANG>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-Index: AclaE6HOCRBmAF4IRs21KvSvTV5cLQ==
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner-ID: 33F7F405110.69F35
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-SpamCheck: 
X-INT-MailScanner-From: iksoon.hwang@it-sudparis.eu
Subject: [Pce] A case that never happens in OpenWait state
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="===============1241022460=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1241022460==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C95A1C.03C0A230"

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C95A1C.03C0A230
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dear all, 

 

I'm currently working on a research project, called CARRIOCAS, which aims at
providing dynamically reconfigurable high speed network for high-performance
applications where PCEP is used for path computation. My work in the project
is to do modeling, validation, verification, and testing of PCEP. PCEP was
described in a formal language IF and some properties were validated. I have
some questions that were found during my work. The questions will be posted
in four separate emails including this one. 

 

I found that there is a case that never happens in OpenWait state. Is there
anybody who can give me any advice if I'm missing something? The detailed
case is as follows.

 

In Appendix A, when a system in OpenWait state receives an Open message from
its peer where no errors are detected, OpenRetry is 0, the session
characteristics are unacceptable but negotiable, and LocalOK=1, the system
restarts the OpenWait timer and stays in the OpenWait state.

 

According to our experiments, we found that the above case cannot happen. We
analyzed the reason and the result is as follows: we can have LocalOK=1 only
when the system in KeepWait state receives a Keepalive message from its
peer. Since the system can move to KeepWait state only after receiving an
Open message from its peer in OpenWait state, the OpenRetry value is always
more than 0 if we have LocalOK=1.

 

Thanks in advance!

 

    Iksoon


------=_NextPart_000_0007_01C95A1C.03C0A230
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=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-autospace:none;
	word-break:break-hangul;
	font-size:10.0pt;
	font-family:Batang;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Gulim;
	color:windowtext;}
 /* Page Definitions */
 @page Section1
	{size:595.3pt 841.9pt;
	margin:99.25pt 3.0cm 3.0cm 3.0cm;
	layout-grid:18.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DKO link=3Dblue vlink=3Dpurple>

<div class=3DSection1 style=3D'layout-grid:18.0pt'>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>I&#8217;m currently working on a research =
project,
called CARRIOCAS, which aims at providing dynamically reconfigurable =
high speed
network for high-performance applications where PCEP is used for path
computation. My work in the project is to do modeling, validation,
verification, and testing of PCEP. PCEP was described in a formal =
language IF
and some properties were validated. I have some questions that were =
found
during my work. The questions will be posted in four separate emails =
including
this one. <o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>I found that there is a case that never =
happens in
OpenWait state. Is there anybody who can give me any advice if I&#8217;m
missing something? The detailed case is as =
follows.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>In Appendix A, when a system in OpenWait state
receives an Open message from its peer where no errors are detected, =
OpenRetry
is 0, the session characteristics are unacceptable but negotiable, and
LocalOK=3D1, the system restarts the OpenWait timer and stays in the =
OpenWait
state.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>According to our experiments, we found that =
the above
case cannot happen. We analyzed the reason and the result is as follows: =
we can
have LocalOK=3D1 only when the system in KeepWait state receives a =
Keepalive
message from its peer. Since the system can move to KeepWait state only =
after
receiving an Open message from its peer in OpenWait state, the OpenRetry =
value
is always more than 0 if we have =
LocalOK=3D1.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Thanks in =
advance!<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp; Iksoon</span></font><font =
face=3D&#44404;&#47548;><span
lang=3DEN-US style=3D'font-family:Gulim'><o:p></o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0007_01C95A1C.03C0A230--



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

--===============1241022460==--




From pce-bounces@ietf.org  Tue Dec  9 07:47: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 F1CB628C17C;
	Tue,  9 Dec 2008 07:47: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 43E0028C17C
	for <pce@core3.amsl.com>; Tue,  9 Dec 2008 07:47:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.31
X-Spam-Level: 
X-Spam-Status: No, score=0.31 tagged_above=-999 required=5 tests=[AWL=0.185,
	BAYES_05=-1.11, HELO_EQ_FR=0.35, 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 xNLQzxqdHLYF for <pce@core3.amsl.com>;
	Tue,  9 Dec 2008 07:47:11 -0800 (PST)
Received: from smtp4.int-evry.fr (smtp4.int-evry.fr [157.159.10.71])
	by core3.amsl.com (Postfix) with ESMTP id EC9DD28C16C
	for <pce@ietf.org>; Tue,  9 Dec 2008 07:47:10 -0800 (PST)
Received: from smtp2.int-evry.fr (smtp2.int-evry.fr [157.159.10.45])
	by smtp4.int-evry.fr (Postfix) with ESMTP id 5E77DFE3DA4
	for <pce@ietf.org>; Tue,  9 Dec 2008 16:47:05 +0100 (CET)
Received: from ISHWANG (unknown [157.159.103.30])
	by smtp2.int-evry.fr (Postfix) with ESMTP id 21A0D40510E
	for <pce@ietf.org>; Tue,  9 Dec 2008 16:46:04 +0100 (CET)
From: "Iksoon Hwang" <Iksoon.Hwang@it-sudparis.eu>
To: <pce@ietf.org>
Date: Tue, 9 Dec 2008 16:45:58 +0100
Message-ID: <6DCFA0E30D0149F19AC2753EFD129B2C@ISHWANG>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-Index: AclaFTrdf8+aW6ixROGmmfCIlouvwA==
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner-ID: 21A0D40510E.A1CEE
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-SpamCheck: 
X-INT-MailScanner-From: iksoon.hwang@it-sudparis.eu
Subject: [Pce] When should we start the Keepalive timer?
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="===============1032265833=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1032265833==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000B_01C95A1D.9E1EF470"

This is a multi-part message in MIME format.

------=_NextPart_000_000B_01C95A1D.9E1EF470
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dear all,

 

It seems that there are some problems in the explanation of Appendix A
concerning with the Keepalive timer.

 

In section 4.2.1, Keepalive messages are used to acknowledge Open messages,
and once the PCEP session has been successfully established.

 

In section 6.2, the PCEP session is considered as established once both PCEP
peers have received a Keepalive message from their peer.

 

In Appendix A, if a system in OpenWait state receives an Open message from
the PCEP peer before the expiration of the OpenWait timer, it performs
collision resolution procedure. If there is no collision, no errors are
detected in Open message, and the session characteristics are acceptable to
the local system, the system:

   o  Sends a Keepalive message to the PCEP peer,

   o  Starts the Keepalive timer,

   o  Sets the RemoteOK variable to 1.

If LocalOK=0 the system clears the OpenWait timer, starts the KeepWait timer
and moves to the KeepWait state.

 

The statement in section 4.2.1 and starting the Keepalive timer in OpenWait
state when LocalOK=0 are contradictory because the system starts keepalive
mechanism although the session is not established yet. 

 

Also, it seems that there is another problem. In section 7.3, it is
explained that "A sends an Open message to B with Keepalive=10 seconds and
Deadtimer=40 seconds.  This means that A sends Keepalive messages (or any
other PCEP message) to B every 10 seconds and B can declare the PCEP session
with A down if no PCEP message has been received from A within any 40 second
period". The Keepalive timer should follow the Keepalive value in the Open
message that was sent to its peer (not the Keepalive value in the Open
message received from its peer). Therefore, the Keepalive timer can be set
only after the peer accepted the parameter values in the Open, i.e. only
after the system receives a Keepalive message from its peer. 

 

I think the Keepalive timer and the Deadtimer should be started when the
system moves to SessionUP state. Is there anybody who can give me any
advice?

 

Thanks in advance.

 

    Iksoon

 

 


------=_NextPart_000_000B_01C95A1D.9E1EF470
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=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-autospace:none;
	word-break:break-hangul;
	font-size:10.0pt;
	font-family:Batang;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Gulim;
	color:windowtext;}
 /* Page Definitions */
 @page Section1
	{size:595.3pt 841.9pt;
	margin:99.25pt 3.0cm 3.0cm 3.0cm;
	layout-grid:18.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DKO link=3Dblue vlink=3Dpurple>

<div class=3DSection1 style=3D'layout-grid:18.0pt'>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>Dear =
all,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>It seems that there are =
some
problems in the explanation of Appendix A concerning with the Keepalive =
timer.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>In section 4.2.1, Keepalive =
messages
are used to acknowledge Open messages, and once the PCEP session has =
been
successfully established.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>In section 6.2, the PCEP =
session is
considered as established once both PCEP peers have received a Keepalive
message from their peer.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>In Appendix A, if a system =
in
OpenWait state receives an Open message from the PCEP peer before the
expiration of the OpenWait timer, it performs collision resolution =
procedure.
If there is no collision, no errors are detected in Open message, and =
the
session characteristics are acceptable to the local system, the =
system:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>&nbsp;&nbsp; o&nbsp; Sends =
a
Keepalive message to the PCEP peer,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>&nbsp;&nbsp; o&nbsp; Starts =
the
Keepalive timer,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>&nbsp;&nbsp; o&nbsp; Sets =
the
RemoteOK variable to 1.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>If LocalOK=3D0 the system =
clears the
OpenWait timer, starts the KeepWait timer and moves to the KeepWait =
state.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>The statement in section =
4.2.1 and
starting the Keepalive timer in OpenWait state when LocalOK=3D0 are =
contradictory
because the system starts keepalive mechanism although the session is =
not
established yet. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>Also, it seems that there =
is another
problem. In section 7.3, it is explained that &quot;A sends an Open =
message to
B with Keepalive=3D10 seconds and Deadtimer=3D40 seconds.&nbsp; This =
means that A
sends Keepalive messages (or any other PCEP message) to B every 10 =
seconds and
B can declare the PCEP session with A down if no PCEP message has been =
received
from A within any 40 second period&quot;. The Keepalive timer should =
follow the
Keepalive value in the Open message that was sent to its peer (not the
Keepalive value in the Open message received from its peer). Therefore, =
the
Keepalive timer can be set only after the peer accepted the parameter =
values in
the Open, i.e. only after the system receives a Keepalive message from =
its
peer. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>I think the Keepalive timer =
and the
Deadtimer should be started when the system moves to SessionUP state. Is =
there
anybody who can give me any advice?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>Thanks in =
advance.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>&nbsp;&nbsp;&nbsp; =
Iksoon<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

</div>

</body>

</html>

------=_NextPart_000_000B_01C95A1D.9E1EF470--



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

--===============1032265833==--




From pce-bounces@ietf.org  Tue Dec  9 07:54:48 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 77A8428C16B;
	Tue,  9 Dec 2008 07:54:48 -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 71D2528C16B
	for <pce@core3.amsl.com>; Tue,  9 Dec 2008 07:54:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.527
X-Spam-Level: 
X-Spam-Status: No, score=-0.527 tagged_above=-999 required=5 tests=[AWL=0.837, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 POlEphpMHQ6x for <pce@core3.amsl.com>;
	Tue,  9 Dec 2008 07:54:43 -0800 (PST)
Received: from smtp4.int-evry.fr (smtp4.int-evry.fr [157.159.10.71])
	by core3.amsl.com (Postfix) with ESMTP id C891928C14F
	for <pce@ietf.org>; Tue,  9 Dec 2008 07:54:42 -0800 (PST)
Received: from smtp2.int-evry.fr (smtp2.int-evry.fr [157.159.10.45])
	by smtp4.int-evry.fr (Postfix) with ESMTP id 21069FE3D9D
	for <pce@ietf.org>; Tue,  9 Dec 2008 16:54:35 +0100 (CET)
Received: from ISHWANG (unknown [157.159.103.30])
	by smtp2.int-evry.fr (Postfix) with ESMTP id 6E54D4050F3
	for <pce@ietf.org>; Tue,  9 Dec 2008 16:54:04 +0100 (CET)
From: "Iksoon Hwang" <Iksoon.Hwang@it-sudparis.eu>
To: <pce@ietf.org>
Date: Tue, 9 Dec 2008 16:54:00 +0100
Message-ID: <A171B517B1DF484FB662AF36D970556A@ISHWANG>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-Index: AclaFlpF0Kenyxx4R0Gxg3f6WT/mrA==
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner-ID: 6E54D4050F3.6283E
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-SpamCheck: 
X-INT-MailScanner-From: iksoon.hwang@it-sudparis.eu
Subject: [Pce] How to handle a second TCP connection establishment request
	from peer?
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="===============0374316857=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0374316857==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000F_01C95A1E.BC42C160"

This is a multi-part message in MIME format.

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

Dear all,

 

According to section 7.15, if a PCEP peer detects an attempt from another
PCEP peer to establish a second PCEP session, it MUST send a PCErr message
with Error-type=9, Error-value=1. 

 

In section 6.2, it is mentioned that once the TCP connection has been
successfully established, the first message sent by the PCC to the PCE or by
the PCE to the PCC MUST be an Open message as specified in Appendix A. Any
message received prior to an Open message MUST trigger a protocol error
condition causing a PCErr message to be sent with Error-Type 'PCEP session
establishment failure' and Error-Value 'reception of an invalid Open message
or a non Open message' and the PCEP session establishment attempt MUST be
terminated by closing the TCP connection.

 

Then, in such a case, we have to exchange PCErr messages and I'm wondering
if it is necessary. I think it is better to mention that "once the TCP
connection has been successfully established, the first message sent by the
PCC to the PCE or by the PCE to the PCC MUST be either an Open message or an
Error message. Any other message received . ". 

 

Another question is that I'd like to know if it is appropriate to ignore the
second connection. In case of connection oriented protocols, we may have
resource mismatch problems, i.e. one assumes that a connection is already
released while the other is still holding it. If the second connection is
always ignored, we cannot have any connection between two peers before
resource mismatch problem is resolved.

 

Thanks in advance.

 

    Iksoon


------=_NextPart_000_000F_01C95A1E.BC42C160
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=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-autospace:none;
	word-break:break-hangul;
	font-size:10.0pt;
	font-family:Batang;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Gulim;
	color:windowtext;}
 /* Page Definitions */
 @page Section1
	{size:595.3pt 841.9pt;
	margin:99.25pt 3.0cm 3.0cm 3.0cm;
	layout-grid:18.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DKO link=3Dblue vlink=3Dpurple>

<div class=3DSection1 style=3D'layout-grid:18.0pt'>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>Dear =
all,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>According to section 7.15, =
if a PCEP
peer detects an attempt from another PCEP peer to establish a second =
PCEP
session, it MUST send a PCErr message with Error-type=3D9, =
Error-value=3D1. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>In section 6.2, it is =
mentioned that
once the TCP connection has been successfully established, the first =
message
sent by the PCC to the PCE or by the PCE to the PCC MUST be an Open =
message as
specified in Appendix A. Any message received prior to an Open message =
MUST
trigger a protocol error condition causing a PCErr message to be sent =
with
Error-Type 'PCEP session establishment failure' and Error-Value =
'reception of
an invalid Open message or a non Open message' and the PCEP session
establishment attempt MUST be terminated by closing the TCP =
connection.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>Then, in such a case, we =
have to
exchange PCErr messages and I</span></font><font face=3DArial><span =
lang=3DEN-US
style=3D'font-family:Arial'>&#8217;</span></font><font =
face=3D&#44404;&#47548;><span
lang=3DEN-US style=3D'font-family:Gulim'>m wondering if it is necessary. =
I think it
is better to mention that </span></font><font face=3DArial><span =
lang=3DEN-US
style=3D'font-family:Arial'>&#8220;</span></font><font =
face=3D&#44404;&#47548;><span
lang=3DEN-US style=3D'font-family:Gulim'>once the TCP connection has =
been
successfully established, the first message sent by the PCC to the PCE =
or by
the PCE to the PCC MUST be either an Open message or an Error message. =
Any other
message received </span></font><font face=3DArial><span lang=3DEN-US
style=3D'font-family:Arial'>&#8230;</span></font><font =
face=3D&#44404;&#47548;><span
lang=3DEN-US style=3D'font-family:Gulim'> </span></font><font =
face=3DArial><span
lang=3DEN-US style=3D'font-family:Arial'>&#8220;</span></font><font =
face=3D&#44404;&#47548;><span
lang=3DEN-US style=3D'font-family:Gulim'>. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>Another question is that =
I</span></font><font
face=3DArial><span lang=3DEN-US =
style=3D'font-family:Arial'>&#8217;</span></font><font
face=3D&#44404;&#47548;><span lang=3DEN-US style=3D'font-family:Gulim'>d =
like to know
if it is appropriate to ignore the second connection. In case of =
connection
oriented protocols, we may have resource mismatch problems, i.e. one =
assumes
that a connection is already released while the other is still holding =
it. If
the second connection is always ignored, we cannot have any connection =
between
two peers before resource mismatch problem is =
resolved.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>Thanks in =
advance.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>&nbsp;&nbsp;&nbsp; =
Iksoon<o:p></o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_000F_01C95A1E.BC42C160--



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

--===============0374316857==--




From pce-bounces@ietf.org  Tue Dec  9 08:06: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 276513A69E0;
	Tue,  9 Dec 2008 08:06: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 4F7163A67D8
	for <pce@core3.amsl.com>; Tue,  9 Dec 2008 08:06:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.494
X-Spam-Level: 
X-Spam-Status: No, score=0.494 tagged_above=-999 required=5 tests=[AWL=-0.742, 
	BAYES_50=0.001, HELO_EQ_FR=0.35, 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 0A3FqoIioFqE for <pce@core3.amsl.com>;
	Tue,  9 Dec 2008 08:06:21 -0800 (PST)
Received: from smtp4.int-evry.fr (smtp4.int-evry.fr [157.159.10.71])
	by core3.amsl.com (Postfix) with ESMTP id 39BC13A6986
	for <pce@ietf.org>; Tue,  9 Dec 2008 08:06:21 -0800 (PST)
Received: from smtp2.int-evry.fr (smtp2.int-evry.fr [157.159.10.45])
	by smtp4.int-evry.fr (Postfix) with ESMTP id 62EE6FE3DA3
	for <pce@ietf.org>; Tue,  9 Dec 2008 17:06:13 +0100 (CET)
Received: from ISHWANG (unknown [157.159.103.30])
	by smtp2.int-evry.fr (Postfix) with ESMTP id D9C44405110
	for <pce@ietf.org>; Tue,  9 Dec 2008 17:05:21 +0100 (CET)
From: "Iksoon Hwang" <Iksoon.Hwang@it-sudparis.eu>
To: <pce@ietf.org>
Date: Tue, 9 Dec 2008 17:05:18 +0100
Message-ID: <C93C1ABB719441B886DAD5DC270D940B@ISHWANG>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-Index: AclaF+3nGDyG8oWQSo+7Za+ce/AylA==
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner-ID: D9C44405110.739B8
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-SpamCheck: 
X-INT-MailScanner-From: iksoon.hwang@it-sudparis.eu
Subject: [Pce] Receiving an Open message from its peer in KeepWait state
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="===============0484868877=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0484868877==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002B_01C95A20.50102B20"

This is a multi-part message in MIME format.

------=_NextPart_000_002B_01C95A20.50102B20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dear all, 

 

According to the Appendix A, if an Open message is received from its peer
when the system is in KeepWait state, the system should abort the
establishment procedure. In order to have a successful session
establishment, in such a case, reply messages must be sent in the order the
requests are received. 

 

Isn't it too strong condition? I think the order of reply messages may be
changed in some cases so it might be better to allow the system to receive
an Open message in KeepWait state. 

 

Thanks in advance!

 

    Iksoon


------=_NextPart_000_002B_01C95A20.50102B20
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=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-autospace:none;
	word-break:break-hangul;
	font-size:10.0pt;
	font-family:Batang;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Gulim;
	color:windowtext;}
 /* Page Definitions */
 @page Section1
	{size:595.3pt 841.9pt;
	margin:99.25pt 3.0cm 3.0cm 3.0cm;
	layout-grid:18.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DKO link=3Dblue vlink=3Dpurple>

<div class=3DSection1 style=3D'layout-grid:18.0pt'>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>Dear all, =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>According to the Appendix =
A, if an
Open message is received from its peer when the system is in KeepWait =
state,
the system should abort the establishment procedure. In order to have a
successful session establishment, in such a case, reply messages must be =
sent
in the order the requests are received. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>Isn</span></font><font =
face=3DArial><span
lang=3DEN-US style=3D'font-family:Arial'>&#8217;</span></font><font =
face=3D&#44404;&#47548;><span
lang=3DEN-US style=3D'font-family:Gulim'>t it too strong condition? I =
think the
order of reply messages may be changed in some cases so it might be =
better to
allow the system to receive an Open message in KeepWait state. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>Thanks in =
advance!<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>&nbsp;&nbsp;&nbsp; =
Iksoon<o:p></o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_002B_01C95A20.50102B20--



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

--===============0484868877==--




From pce-bounces@ietf.org  Tue Dec  9 08:36: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 62E633A6B15;
	Tue,  9 Dec 2008 08:36:37 -0800 (PST)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id 73D163A6B03; Tue,  9 Dec 2008 08:36:35 -0800 (PST)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20081209163635.73D163A6B03@core3.amsl.com>
Date: Tue,  9 Dec 2008 08:36:35 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] Last Call: draft-ietf-pce-dste (Diff-Serv Aware Class Type
 Object for Path Computation Element Communication Protocol) to Proposed
 Standard
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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 received a request from the Path Computation Element WG 
(pce) to consider the following document:

- 'Diff-Serv Aware Class Type Object for Path Computation Element 
   Communication Protocol '
   <draft-ietf-pce-dste-02.txt> as a Proposed Standard

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-23. 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-ietf-pce-dste-02.txt


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

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


From pce-bounces@ietf.org  Tue Dec  9 08:37:49 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 9F6B928C0F5;
	Tue,  9 Dec 2008 08:37:49 -0800 (PST)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id 8282F3A6B28; Tue,  9 Dec 2008 08:37:47 -0800 (PST)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20081209163747.8282F3A6B28@core3.amsl.com>
Date: Tue,  9 Dec 2008 08:37:47 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] Last Call: draft-ietf-pce-of (Encoding of Objective Functions
 in the Path Computation Element Communication Protocol (PCEP)) to Proposed
 Standard
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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 received a request from the Path Computation Element WG 
(pce) to consider the following document:

- 'Encoding of Objective Functions in the Path Computation Element 
   Communication Protocol (PCEP) '
   <draft-ietf-pce-of-05.txt> as a Proposed Standard

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-23. 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-ietf-pce-of-05.txt


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

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


From pce-bounces@ietf.org  Wed Dec 10 01:14:00 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 3F7003A6B89;
	Wed, 10 Dec 2008 01:14:00 -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 9A03B3A6B8B
	for <pce@core3.amsl.com>; Wed, 10 Dec 2008 01:13:59 -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 5jOAd4YtcbcN for <pce@core3.amsl.com>;
	Wed, 10 Dec 2008 01:13:53 -0800 (PST)
Received: from bizpsie3.9services.com (bizpsie3.9services.com [84.96.93.161])
	by core3.amsl.com (Postfix) with ESMTP id 95AF43A68F3
	for <pce@ietf.org>; Wed, 10 Dec 2008 01:13:51 -0800 (PST)
Received: from pooky.marben-products.com ([86.65.15.130])
	by bizpsie3.9services.com with 9services
	id pMDc1a00E2oN1dS03MDdim; Wed, 10 Dec 2008 10:13:41 +0100
X-Biz3: ??
X-VRSPAM-SCORE: -150.00
Received: from AOFR11476 (aofr11476.marben-products.com [192.168.7.180])
	by pooky.marben-products.com (8.14.0/8.14.0) with ESMTP id
	mBA9DaAx005219; Wed, 10 Dec 2008 10:13:36 +0100
From: "Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com>
To: "'Iksoon Hwang'" <Iksoon.Hwang@it-sudparis.eu>, <pce@ietf.org>
Date: Wed, 10 Dec 2008 10:17:56 +0100
Message-ID: <006701c95aa8$33b0a530$b407a8c0@marbenproducts.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <2DC0DAA7437948DD9285AD6F244ED7F7@ISHWANG>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-index: AclaE6HOCRBmAF4IRs21KvSvTV5cLQAkq4Mg
Subject: Re: [Pce] A case that never happens in OpenWait state
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="===============0246668159=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0246668159==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0068_01C95AB0.9579C820"

This is a multi-part message in MIME format.

------=_NextPart_000_0068_01C95AB0.9579C820
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello Iksoon,

=20

> we can have LocalOK=3D1 only when the system in KeepWait state =
receives a
Keepalive message from its peer

=20

I guess your statement comes from the fact that the only place where it =
is
said to set the LocalOK variable to 1 is in keepwait state:

=20

=93If a Keepalive message is received before the expiration of the
   KeepWait timer, then the system sets LocalOK=3D1 and:=94

=20

However if you apply the definition of the LocalOk variable you must set =
the
LocalOk variable to 1 each time you receive a positive acknowledgement

of the Open message, whatever is the current state (OpenWait or =
KeepWair).

=20

=93LocalOK: the LocalOK variable is a Boolean set to 1 if the system has =

received a Keepalive message acknowledging that the Open message sent
to the peer was valid.=94

=20

More generally the state diagram described in PCEP draft must be =
carefully
interpreted because of the independent Open/Keepalive message flow in
opposite

direction which is managed with a single state.

But I agree that strictly speaking in the OpenWait state case there =
should
be statement about the receipt of a KeepAlive message when LocalOk is 0.

=20

Best regards

Fabien

=20

=20

  _____ =20

De : pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] De la part de =
Iksoon
Hwang
Envoy=E9 : mardi 9 d=E9cembre 2008 16:35
=C0 : pce@ietf.org
Objet : [Pce] A case that never happens in OpenWait state

=20

Dear all,=20

=20

I=92m currently working on a research project, called CARRIOCAS, which =
aims at
providing dynamically reconfigurable high speed network for =
high-performance
applications where PCEP is used for path computation. My work in the =
project
is to do modeling, validation, verification, and testing of PCEP. PCEP =
was
described in a formal language IF and some properties were validated. I =
have
some questions that were found during my work. The questions will be =
posted
in four separate emails including this one.=20

=20

I found that there is a case that never happens in OpenWait state. Is =
there
anybody who can give me any advice if I=92m missing something? The =
detailed
case is as follows.

=20

In Appendix A, when a system in OpenWait state receives an Open message =
from
its peer where no errors are detected, OpenRetry is 0, the session
characteristics are unacceptable but negotiable, and LocalOK=3D1, the =
system
restarts the OpenWait timer and stays in the OpenWait state.

=20

According to our experiments, we found that the above case cannot =
happen. We
analyzed the reason and the result is as follows: we can have =
LocalOK=3D1 only
when the system in KeepWait state receives a Keepalive message from its
peer. Since the system can move to KeepWait state only after receiving =
an
Open message from its peer in OpenWait state, the OpenRetry value is =
always
more than 0 if we have LocalOK=3D1.

=20

Thanks in advance!

=20

    Iksoon


------=_NextPart_000_0068_01C95AB0.9579C820
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=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:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 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:"\@Batang";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"\@Gulim";
	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;
	text-align:justify;
	text-justify:inter-ideograph;
	text-autospace:none;
	word-break:break-all;
	font-size:10.0pt;
	font-family:Batang;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Gulim;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:99.25pt 3.0cm 3.0cm 3.0cm;
	layout-grid:18.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1 style=3D'layout-grid:18.0pt'>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>&gt; we can have LocalOK=3D1 only when the =
system in
KeepWait state receives a Keepalive message from its =
peer<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
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-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>I guess your =
statement
comes from the fact that the only place where it is said to set the =
LocalOK
variable to 1 is in keepwait state:<o:p></o:p></span></font></p>

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

<pre><font size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'>&#8220;</span></font><span lang=3DEN-GB>If =
a Keepalive message is received before the expiration of =
the<o:p></o:p></span></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>=A0=A0 KeepWait timer, then the system sets =
LocalOK=3D1 and:&#8221;<o:p></o:p></span></font></pre>

<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'>However if you =
apply the
definition of the LocalOk variable you must set the LocalOk variable to =
1 each
time you receive a positive acknowledgement<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'>of the Open =
message,
whatever is the current state (OpenWait or =
KeepWair).<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>

<pre><font size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>&#8220;LocalOK: the LocalOK variable is a =
Boolean set to 1 if the system has =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>received a Keepalive message acknowledging =
that the Open message sent<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>to the peer was =
valid.&#8221;<o:p></o:p></span></font></pre>

<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'>More generally =
the state
diagram described in PCEP draft must be carefully interpreted because of =
the
independent Open/Keepalive message flow in =
opposite<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'>direction which =
is
managed with a single state.<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'>But I agree that =
strictly
speaking in the OpenWait state case there should be statement about the =
receipt
of a KeepAlive message when LocalOk is 0.<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'>Best =
regards<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'>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;text-autospace:ideograph-numeric =
ideograph-other;
word-break:normal'><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt;font-family:"Times New Roman"'>

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

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

<p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-autospace:ideograph-numeric =
ideograph-other;
word-break:normal'><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
face=3DTahoma><span style=3D'font-family:Tahoma'> pce-bounces@ietf.org
[mailto:pce-bounces@ietf.org] <b><span style=3D'font-weight:bold'>De la =
part de</span></b>
Iksoon Hwang<br>
<b><span style=3D'font-weight:bold'>Envoy=E9&nbsp;:</span></b> mardi 9 =
d=E9cembre
2008 16:35<br>
<b><span style=3D'font-weight:bold'>=C0&nbsp;:</span></b> =
pce@ietf.org<br>
<b><span style=3D'font-weight:bold'>Objet&nbsp;:</span></b> [Pce] A case =
that
never happens in OpenWait state</span></font><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal align=3Dleft style=3D'text-align:left'><font =
size=3D2 face=3DBatang><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>I&#8217;m currently working on a research =
project,
called CARRIOCAS, which aims at providing dynamically reconfigurable =
high speed
network for high-performance applications where PCEP is used for path
computation. My work in the project is to do modeling, validation,
verification, and testing of PCEP. PCEP was described in a formal =
language IF
and some properties were validated. I have some questions that were =
found
during my work. The questions will be posted in four separate emails =
including
this one. <o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>I found that there is a case that never =
happens in
OpenWait state. Is there anybody who can give me any advice if I&#8217;m
missing something? The detailed case is as =
follows.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>In Appendix A, when a system in OpenWait state
receives an Open message from its peer where no errors are detected, =
OpenRetry
is 0, the session characteristics are unacceptable but negotiable, and
LocalOK=3D1, the system restarts the OpenWait timer and stays in the =
OpenWait
state.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>According to our experiments, we found that =
the above
case cannot happen. We analyzed the reason and the result is as follows: =
we can
have LocalOK=3D1 only when the system in KeepWait state receives a =
Keepalive
message from its peer. Since the system can move to KeepWait state only =
after
receiving an Open message from its peer in OpenWait state, the OpenRetry =
value
is always more than 0 if we have =
LocalOK=3D1.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Thanks in =
advance!<o:p></o:p></span></font></p>

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

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

</div>

</div>

</body>

</html>

------=_NextPart_000_0068_01C95AB0.9579C820--


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

--===============0246668159==--



From pce-bounces@ietf.org  Wed Dec 10 06:23: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 EAC113A6BAE;
	Wed, 10 Dec 2008 06:23: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 EA9C13A68EC
	for <pce@core3.amsl.com>; Wed, 10 Dec 2008 06:23:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.37
X-Spam-Level: 
X-Spam-Status: No, score=-4.37 tagged_above=-999 required=5 tests=[AWL=2.229, 
	BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2]
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 2ihmZ46LHsGf for <pce@core3.amsl.com>;
	Wed, 10 Dec 2008 06:23:11 -0800 (PST)
Received: from protext01.itu.ch (protext01.itu.ch [156.106.192.41])
	by core3.amsl.com (Postfix) with ESMTP id C1BE93A6BAE
	for <pce@ietf.org>; Wed, 10 Dec 2008 06:23:10 -0800 (PST)
Received: from protext01.itu.ch ([156.106.192.41]) by protext01.itu.ch with
	Microsoft SMTPSVC(5.0.2195.6713); Wed, 10 Dec 2008 15:23:04 +0100
Received: From mail6.itu.ch ([156.106.192.22]) by protext01.itu.ch (WebShield
	SMTP v4.5 MR3) id 1228918983562; Wed, 10 Dec 2008 15:23:03 +0100
Received: from your029b8cecfe ([156.106.219.34])
	by mail6.itu.ch (8.14.3/8.14.3) with ESMTP id mBAEMv6S014364
	for <pce@ietf.org>; Wed, 10 Dec 2008 15:23:03 +0100 (MET)
Message-ID: <AC9D1B04152343AE96301DD6CE62AB8D@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Wed, 10 Dec 2008 14:22:53 -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
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0
	(mail6.itu.ch [156.106.192.22]);
	Wed, 10 Dec 2008 15:23:03 +0100 (MET)
X-OriginalArrivalTime: 10 Dec 2008 14:23:04.0390 (UTC)
	FILETIME=[D0779660:01C95AD2]
Subject: [Pce] Fw: Letters of Invitation to IETF 74 now available to past
	attendees
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


----- Original Message ----- 
From: "Alexa Morris" <amorris@amsl.com>
To: <ietf@ietf.org>; <wgchairs@ietf.org>
Sent: Tuesday, December 09, 2008 6:31 PM
Subject: Letters of Invitation to IETF 74 now available to past attendees


> If you need a letter of invitation (LOI) in order to obtain a visa to  
> come to IETF 74 in San Francisco  -- and if you have attended at least  
> one IETF meeting in the past -- you can now request a LOI via this  
> webform: https://www.amsl.com/ietf/ietf74-loi.html. The LOI will be  
> sent to you via email unless you specifically request a hard copy. You  
> can also access the webform from the Meetings page of the IETF website.
> 
> As soon as we officially open registration for the meeting, anyone who  
> registers for IETF 74 (regardless of whether or not they've attended a  
> past meeting) will be able to request and receive a letter of  
> invitation to attend.
> 
> Regards,
> Alexa
> 
> -----------
> Alexa Morris / Executive Director / IETF
> 48377 Fremont Blvd., Suite 117, Fremont, CA  94538
> Phone: +1.510.492.4089 / Fax: +1.510.492.4001
> Email: amorris@amsl.com
> 
> Managed by Association Management Solutions (AMS)
> Forum Management, Meeting and Event Planning
> www.amsl.com <http://www.amsl.com/>
> 
>

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


From pce-bounces@ietf.org  Thu Dec 11 05:44:44 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 9FA513A6C59;
	Thu, 11 Dec 2008 05:44:44 -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 40CBF3A6C59
	for <pce@core3.amsl.com>; Thu, 11 Dec 2008 05:44:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.621
X-Spam-Level: 
X-Spam-Status: No, score=-0.621 tagged_above=-999 required=5 tests=[AWL=0.744, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 xrA-xt8+tech for <pce@core3.amsl.com>;
	Thu, 11 Dec 2008 05:44:37 -0800 (PST)
Received: from smtp4.int-evry.fr (smtp4.int-evry.fr [157.159.10.71])
	by core3.amsl.com (Postfix) with ESMTP id 1BA253A6C19
	for <pce@ietf.org>; Thu, 11 Dec 2008 05:44:36 -0800 (PST)
Received: from smtp2.int-evry.fr (smtp2.int-evry.fr [157.159.10.45])
	by smtp4.int-evry.fr (Postfix) with ESMTP id 5CDA5FE2CDE;
	Thu, 11 Dec 2008 14:44:30 +0100 (CET)
Received: from ISHWANG (unknown [157.159.103.30])
	by smtp2.int-evry.fr (Postfix) with ESMTP id 9D4234052D9;
	Thu, 11 Dec 2008 14:44:20 +0100 (CET)
From: "Iksoon Hwang" <Iksoon.Hwang@it-sudparis.eu>
To: "'Fabien Verhaeghe'" <fabien.verhaeghe@marben-products.com>, <pce@ietf.org>
References: <2DC0DAA7437948DD9285AD6F244ED7F7@ISHWANG>
	<006701c95aa8$33b0a530$b407a8c0@marbenproducts.com>
Date: Thu, 11 Dec 2008 14:44:15 +0100
Message-ID: <073946D93E974E95B39758C0ED904D93@ISHWANG>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-Index: AclaE6HOCRBmAF4IRs21KvSvTV5cLQAkq4MgADs1NiA=
In-Reply-To: <006701c95aa8$33b0a530$b407a8c0@marbenproducts.com>
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner-ID: 9D4234052D9.4FA0C
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-SpamCheck: 
X-INT-MailScanner-From: iksoon.hwang@it-sudparis.eu
Subject: Re: [Pce] A case that never happens in OpenWait state
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="===============1914284312=="
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1914284312==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001A_01C95B9E.F0EE28B0"

This is a multi-part message in MIME format.

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

Dear Fabien,

=20

Thank you very much for your comments.=20

=20

So if we accept a Keepalive message in OpenWait state, the problem is
solved. In such a case, I think we can also accept an Open message in
KeepWait state, which is mentioned in my fourth post.=20

=20

If we agree on this, I think it is better to remove the following =
sentence
in Appendix A in order to let receiving those messages be an =
implementation
issue.

=20

"In response to any other event the system releases the PCEP resources =
for
that peer and moves back to the Idle state."=20

=20

Best regards,

=20

    Iksoon

=20

  _____ =20

From: Fabien Verhaeghe [mailto:fabien.verhaeghe@marben-products.com]=20
Sent: Wednesday, December 10, 2008 10:18 AM
To: 'Iksoon Hwang'; pce@ietf.org
Subject: RE: [Pce] A case that never happens in OpenWait state

=20

Hello Iksoon,

=20

> we can have LocalOK=3D1 only when the system in KeepWait state =
receives a
Keepalive message from its peer

=20

I guess your statement comes from the fact that the only place where it =
is
said to set the LocalOK variable to 1 is in keepwait state:

=20

=93If a Keepalive message is received before the expiration of the
   KeepWait timer, then the system sets LocalOK=3D1 and:=94

=20

However if you apply the definition of the LocalOk variable you must set =
the
LocalOk variable to 1 each time you receive a positive acknowledgement

of the Open message, whatever is the current state (OpenWait or =
KeepWair).

=20

=93LocalOK: the LocalOK variable is a Boolean set to 1 if the system has =

received a Keepalive message acknowledging that the Open message sent
to the peer was valid.=94

=20

More generally the state diagram described in PCEP draft must be =
carefully
interpreted because of the independent Open/Keepalive message flow in
opposite

direction which is managed with a single state.

But I agree that strictly speaking in the OpenWait state case there =
should
be statement about the receipt of a KeepAlive message when LocalOk is 0.

=20

Best regards

Fabien

=20

=20

  _____ =20

De : pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] De la part de =
Iksoon
Hwang
Envoy=E9 : mardi 9 d=E9cembre 2008 16:35
=C0 : pce@ietf.org
Objet : [Pce] A case that never happens in OpenWait state

=20

Dear all,=20

=20

I=92m currently working on a research project, called CARRIOCAS, which =
aims at
providing dynamically reconfigurable high speed network for =
high-performance
applications where PCEP is used for path computation. My work in the =
project
is to do modeling, validation, verification, and testing of PCEP. PCEP =
was
described in a formal language IF and some properties were validated. I =
have
some questions that were found during my work. The questions will be =
posted
in four separate emails including this one.=20

=20

I found that there is a case that never happens in OpenWait state. Is =
there
anybody who can give me any advice if I=92m missing something? The =
detailed
case is as follows.

=20

In Appendix A, when a system in OpenWait state receives an Open message =
from
its peer where no errors are detected, OpenRetry is 0, the session
characteristics are unacceptable but negotiable, and LocalOK=3D1, the =
system
restarts the OpenWait timer and stays in the OpenWait state.

=20

According to our experiments, we found that the above case cannot =
happen. We
analyzed the reason and the result is as follows: we can have =
LocalOK=3D1 only
when the system in KeepWait state receives a Keepalive message from its
peer. Since the system can move to KeepWait state only after receiving =
an
Open message from its peer in OpenWait state, the OpenRetry value is =
always
more than 0 if we have LocalOK=3D1.

=20

Thanks in advance!

=20

    Iksoon


------=_NextPart_000_001A_01C95B9E.F0EE28B0
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:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
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]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"time"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 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:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-autospace:none;
	word-break:break-hangul;
	font-size:10.0pt;
	font-family:Batang;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Gulim;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Gulim;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:99.25pt 3.0cm 3.0cm 3.0cm;
	layout-grid:18.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DKO link=3Dblue vlink=3Dpurple>

<div class=3DSection1 style=3D'layout-grid:18.0pt'>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>Dear =
Fabien,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>Thank you very much for =
your
comments. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>So if we accept a Keepalive =
message
in OpenWait state, the problem is solved. In such a case, I think we can =
also
accept an Open message in KeepWait state, which is mentioned in my =
fourth post.
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>If we agree on this, I =
think it is
better to remove the following sentence in Appendix A in order to let =
receiving
those messages be an implementation issue.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>&quot;In response to any =
other event
the system releases the PCEP resources for that peer and moves back to =
the Idle
state.&quot; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>Best =
regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'>=A0=A0=A0 =
Iksoon<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D&#44404;&#47548;><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Gulim'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<div>

<div class=3DMsoNormal align=3Dcenter =
style=3D'text-align:center;text-autospace:ideograph-numeric =
ideograph-other;
word-break:keep-all'><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

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

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

<p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-autospace:ideograph-numeric =
ideograph-other;
word-break:keep-all'><b><font size=3D2 face=3DTahoma><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
face=3DTahoma><span lang=3DEN-US style=3D'font-family:Tahoma'> Fabien =
Verhaeghe
[mailto:fabien.verhaeghe@marben-products.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, December =
10, 2008
<st1:time o:ls=3D"trans" Hour=3D"10" Minute=3D"18" w:st=3D"on">10:18 =
AM</st1:time><br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Iksoon Hwang'; =
<st1:PersonName
w:st=3D"on">pce@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Pce] A case =
that
never happens in OpenWait state</span></font><font size=3D3 =
face=3D"Times New Roman"><span
lang=3DEN-US style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal align=3Dleft style=3D'text-align:left'><font =
size=3D2 face=3D&#48148;&#53461;><span
lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>&gt; we can have LocalOK=3D1 only when the =
system in
KeepWait state receives a Keepalive message from its =
peer<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
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-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>I guess your =
statement
comes from the fact that the only place where it is said to set the =
LocalOK
variable to 1 is in keepwait state:<o:p></o:p></span></font></p>

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

<pre><font size=3D2 color=3Dnavy face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'>&#8220;</span></font><span lang=3DEN-GB>If =
a Keepalive message is received before the expiration of =
the<o:p></o:p></span></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>&nbsp;&nbsp; KeepWait timer, then the system =
sets LocalOK=3D1 and:&#8221;<o:p></o:p></span></font></pre>

<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'>However if you =
apply the
definition of the LocalOk variable you must set the LocalOk variable to =
1 each
time you receive a positive acknowledgement<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'>of the Open =
message,
whatever is the current state (OpenWait or =
KeepWair).<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>

<pre><font size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>&#8220;LocalOK: the LocalOK variable is a =
Boolean set to 1 if the system has =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>received a Keepalive message acknowledging =
that the Open message sent<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'>to the peer was =
valid.&#8221;<o:p></o:p></span></font></pre>

<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'>More generally =
the state
diagram described in PCEP draft must be carefully interpreted because of =
the
independent Open/Keepalive message flow in =
opposite<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'>direction which =
is
managed with a single state.<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'>But I agree that =
strictly
speaking in the OpenWait state case there should be statement about the =
receipt
of a KeepAlive message when LocalOk is 0.<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'>Best =
regards<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'>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;text-autospace:ideograph-other;
word-break:keep-all'><font size=3D3 face=3D"Times New Roman"><span =
lang=3DFR
style=3D'font-size:12.0pt;font-family:"Times New Roman"'>

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

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

<p class=3DMsoNormal align=3Dleft =
style=3D'text-align:left;text-autospace:ideograph-other;
word-break:keep-all'><b><font size=3D2 face=3DTahoma><span lang=3DFR
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>De&nbsp;:<=
/span></font></b><font
face=3DTahoma><span lang=3DFR style=3D'font-family:Tahoma'> =
pce-bounces@ietf.org
[mailto:pce-bounces@ietf.org] <b><span style=3D'font-weight:bold'>De la =
part de</span></b>
Iksoon Hwang<br>
<b><span style=3D'font-weight:bold'>Envoy=E9&nbsp;:</span></b> mardi 9 =
d=E9cembre
2008 <st1:time o:ls=3D"trans" Hour=3D"16" Minute=3D"35" =
w:st=3D"on">16:35</st1:time><br>
<b><span style=3D'font-weight:bold'>=C0&nbsp;:</span></b> =
<st1:PersonName w:st=3D"on">pce@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Objet&nbsp;:</span></b> [Pce] A case =
that
never happens in OpenWait state</span></font><font size=3D3 =
face=3D"Times New Roman"><span
lang=3DFR style=3D'font-size:12.0pt;font-family:"Times New =
Roman"'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal align=3Dleft style=3D'text-align:left'><font =
size=3D2 face=3D&#48148;&#53461;><span
lang=3DFR style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>I&#8217;m currently working on a research =
project,
called CARRIOCAS, which aims at providing dynamically reconfigurable =
high speed
network for high-performance applications where PCEP is used for path
computation. My work in the project is to do modeling, validation,
verification, and testing of PCEP. PCEP was described in a formal =
language IF
and some properties were validated. I have some questions that were =
found
during my work. The questions will be posted in four separate emails =
including
this one. <o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>I found that there is a case that never =
happens in
OpenWait state. Is there anybody who can give me any advice if I&#8217;m
missing something? The detailed case is as =
follows.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>In Appendix A, when a system in OpenWait state
receives an Open message from its peer where no errors are detected, =
OpenRetry
is 0, the session characteristics are unacceptable but negotiable, and
LocalOK=3D1, the system restarts the OpenWait timer and stays in the =
OpenWait
state.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>According to our experiments, we found that =
the above
case cannot happen. We analyzed the reason and the result is as follows: =
we can
have LocalOK=3D1 only when the system in KeepWait state receives a =
Keepalive
message from its peer. Since the system can move to KeepWait state only =
after
receiving an Open message from its peer in OpenWait state, the OpenRetry =
value
is always more than 0 if we have =
LocalOK=3D1.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Thanks in =
advance!<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp; Iksoon</span></font><font =
face=3D&#44404;&#47548;><span
lang=3DEN-US style=3D'font-family:Gulim'><o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_001A_01C95B9E.F0EE28B0--



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

--===============1914284312==--




From pce-bounces@ietf.org  Thu Dec 11 15:13:14 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 08ED228C115;
	Thu, 11 Dec 2008 15:13:14 -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 8B0B128C113;
	Thu, 11 Dec 2008 15:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.7
X-Spam-Level: 
X-Spam-Status: No, score=-16.7 tagged_above=-999 required=5 tests=[AWL=0.899, 
	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 C9i4ddp6x09e; Thu, 11 Dec 2008 15:13:12 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id C6E6828C10E;
	Thu, 11 Dec 2008 15:13:12 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 36A331A548B; Thu, 11 Dec 2008 15:13:07 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081211231307.36A331A548B@bosco.isi.edu>
Date: Thu, 11 Dec 2008 15:13:07 -0800 (PST)
Cc: pce@ietf.org, rfc-editor@rfc-editor.org
Subject: [Pce] RFC 5394 on Policy-Enabled Path Computation Framework
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 5394

        Title:      Policy-Enabled Path Computation Framework 
        Author:     I. Bryskin, D. Papadimitriou,
                    L. Berger, J. Ash
        Status:     Informational
        Date:       December 2008
        Mailbox:    ibryskin@advaoptical.com, 
                    dimitri.papadimitriou@alcatel.be, 
                    lberger@labn.net, gash5107@yahoo.com
        Pages:      36
        Characters: 82226
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-policy-enabled-path-comp-04.txt

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

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.  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  Mon Dec 15 04:31: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 4DECE3A6994;
	Mon, 15 Dec 2008 04:31: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 2C6703A6994
	for <pce@core3.amsl.com>; Mon, 15 Dec 2008 04:31:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level: 
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5
	tests=[AWL=-0.700, 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 CoyaqftSyz9Q for <pce@core3.amsl.com>;
	Mon, 15 Dec 2008 04:31:17 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 2B9F43A6930
	for <pce@ietf.org>; Mon, 15 Dec 2008 04:31: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
	mBFCUrG5027329 for <pce@ietf.org>; Mon, 15 Dec 2008 12:30:55 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
	mBFCUpXi027268 for <pce@ietf.org>; Mon, 15 Dec 2008 12:30:52 GMT
Message-ID: <34CD72EB03F6410D9C8BBB1C40758C86@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Mon, 15 Dec 2008 12:30:44 -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] Working group last call draft-ietf-pce-monitoring-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

This email begins a working group last call on 
draft-ietf-pce-monitoring-02.txt

The last call will run for three weeks to give people a little extra time 
over the Christmas period.
Thus, the call will end on 5th January 2009 at noon GMT

Please send your comments to the mailing list.

Thanks,
Adrian 

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


From pce-bounces@ietf.org  Mon Dec 15 09:42: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 D61053A6A33;
	Mon, 15 Dec 2008 09:42:13 -0800 (PST)
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id 70EED3A67F7; Mon, 15 Dec 2008 09:42:10 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20081215174211.70EED3A67F7@core3.amsl.com>
Date: Mon, 15 Dec 2008 09:42:11 -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: 'Preserving Topology Confidentiality in
 Inter-Domain Path Computation Using a Key-Based Mechanism' 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:

- 'Preserving Topology Confidentiality in Inter-Domain Path Computation 
   Using a Key-Based Mechanism '
   <draft-ietf-pce-path-key-05.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-path-key-05.txt

Technical Summary

   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.

   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.

Working Group Summary

   WG has good consensus with no disputes or disagreements. An IPR
   disclosure has been filed, but the WG has decided to proceed with
   this I-D. WG last call issues were limited to editorial and minor
   functional nits.

Document Quality

   The document has been updated in response to Gen-Art comments. The
   responsible AD is not aware of any implementations. 

Personnel

   Adrian Farrel is the Document Shepherd for this document. Ross
   Callon is the responsible Area Director.  

RFC Editor Note

   Please update the title of this document as follows:

     OLD

       Preserving Topology Confidentiality in Inter-Domain
       Path Computation Using a Key-Based Mechanism

     NEW

       Preserving Topology Confidentiality in Inter-Domain
       Path Computation Using a Path-Key-Based Mechanism

   Section 3.1.1, paragraph under "PCE ID", first sentence. Please
   update as follows:

     OLD

       A 32-bit identifier of the PCE that can decode this key.

     NEW

       A 32-bit identifier of the PCE that can decode this path-key.

   Section 3.1.2, paragraph under "PCE ID", first sentence. Please
   update as follows:

     OLD
 
       A 128-bit identifier of the PCE that can decode this key.
 
     NEW

       A 128-bit identifier of the PCE that can decode this path-key.

   Please change every occurance in the document of "path key" to 
   instead be "path-key".

   Please add the following paragraph as the second to last paragraph 
   of section 1 (before section 1.1, and immediately before the one-
   sentence paragraph that begins "The BNF in this document..."): 

     Please note that the term "path-key" used in this document
     refers to an identifier allocated by a PCE to represent a
     segment of a computed path. This term has no relation to the
     term "cryptographic key" used in some documents that describe
     security mechanisms.


IANA Note

   The document defines small protocol enhancements to PCEP (which
   was recently approved by the IESG). This I-D requests further
   allocations from the PCEP registry. The IANA section of this 
   I-D uses the same language as the PCEP specification and, in 
   particular, uses the same sub-registry names.

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


From pce-bounces@ietf.org  Wed Dec 17 06:47:44 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 EFFB13A67C1;
	Wed, 17 Dec 2008 06:47: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 0BEFE3A67C1
	for <pce@core3.amsl.com>; Wed, 17 Dec 2008 06:47:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.556
X-Spam-Level: 
X-Spam-Status: No, score=-10.556 tagged_above=-999 required=5
	tests=[AWL=0.043, 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 WuHKZBmYG2XI for <pce@core3.amsl.com>;
	Wed, 17 Dec 2008 06:47: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 D0F093A67A1
	for <pce@ietf.org>; Wed, 17 Dec 2008 06:47:40 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,237,1228089600"; d="scan'208";a="28907802"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 17 Dec 2008 14:47:32 +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 mBHElW9d006622
	for <pce@ietf.org>; Wed, 17 Dec 2008 15:47:32 +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 mBHElWn6009974
	for <pce@ietf.org>; Wed, 17 Dec 2008 14:47:32 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); 
	Wed, 17 Dec 2008 15:47:31 +0100
Received: from ams-jvasseur-8712.cisco.com ([10.55.201.131]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 17 Dec 2008 15:47:31 +0100
Message-Id: <A57B08CE-D1B9-4A95-82B8-6F04E19B3BD2@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: pce@ietf.org
Mime-Version: 1.0 (Apple Message framework v926)
Date: Wed, 17 Dec 2008 15:47:31 +0100
X-Mailer: Apple Mail (2.926)
X-OriginalArrivalTime: 17 Dec 2008 14:47:31.0887 (UTC)
	FILETIME=[640E1BF0:01C96056]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=475; t=1229525252; x=1230389252;
	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:=20A=20Major=20Milestone=20for=20the=20PCE=20WG
	|Sender:=20; bh=jbuN2y2ufH/EuStlBzx6d8PhLQPLZdTSKUC+xcIr3ug=;
	b=JzfFG2i479Tul3bZ5koBGymuYbVHVMwE+c9bQwZK0krHT6p/dRewSkHJE3
	tBlxzi+lKfF/GEPPD2wNYWCjzhhqVOE8pFjX/DPeSY3SV8HLN/JmAc6ubkHH
	Rz6tHOYSsB;
Authentication-Results: ams-dkim-2; header.From=jvasseur@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Subject: [Pce] A Major Milestone for the PCE WG
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,

As you might have noticed, PCEP is now in the RFC editor queue, which  
will also "unblock" the publication on several other I-D also in the  
RFC editor queue, namely:
* http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-19.txt
* http://www.ietf.org/internet-drafts/draft-ietf-pce-brpc-09.txt
* http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-xro-06.txt
* http://www.ietf.org/internet-drafts/draft-ietf-pce-path-key-05.txt

Thanks.

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


From pce-bounces@ietf.org  Thu Dec 18 15:02:02 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 0994F3A68D8;
	Thu, 18 Dec 2008 15:02:02 -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 C2AD63A68D8
	for <pce@core3.amsl.com>; Thu, 18 Dec 2008 15:02:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.937
X-Spam-Level: 
X-Spam-Status: No, score=-1.937 tagged_above=-999 required=5 tests=[AWL=0.661, 
	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 bwJsc4ldGKk7 for <pce@core3.amsl.com>;
	Thu, 18 Dec 2008 15:01:59 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id 0D8E93A68D5
	for <pce@ietf.org>; Thu, 18 Dec 2008 15:01:58 -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
	mBIN1o4A015697 for <pce@ietf.org>; Thu, 18 Dec 2008 23:01:50 GMT
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	mBIN1n2Y015691 for <pce@ietf.org>; Thu, 18 Dec 2008 23:01:49 GMT
Message-ID: <CC6BB4B4C3D34ABFA564FF76138CD348@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
References: <34CD72EB03F6410D9C8BBB1C40758C86@your029b8cecfe>
Date: Thu, 18 Dec 2008 23:01: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] Last call comments on draft-ietf-pce-monitoring-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

Hi,

A few nitty comments on this draft.

Adrian

===

Abstract. Second sentence.

"In PCE-based environments, it is thus critical..."
I don't think this follows as a conclusion from the previous sentence. In
particular, there is no definition of a "path computation chain" and no
explanation of the process involved in PCE that leads to the conclusion that
certain things need to be monitored or troubleshooted.

I suggest inserting a new second sentence to give some background. Something
like...

   Path Computation Clients (PCCs) send computation requests to PCEs,
   and these may forward the requests to and cooperate with other PCEs
   forming a "path computation chain".

You can then put in a paragraph break and continue with your text.

===

Section 1

You need to expand "PCC" and "TE LSP" on first usage as the Terminology 
section comes later.

===

Section 3

Please include a reference to draft-farrel-rtg-common-bnf-07.txt.
At this stage you should (and can safely) make this a normative reference. 
The RBNF draft will go to IETF last call in early January and will be ahead 
of this draft in the processing queue.

===

Section 3

s/Computation Monitoring request/Computation Monitoring Request/

===

Section 3.1

<request> is shown to optionally contain the RRO.

The text that follows refers to the ERO.

I think the text is wrong.

===

Section 3.1

s/metric(s)/metrics/

===

Section 3.1

Examples 1 and 3 should also include a note that the requested information 
is returned in a PCMonRep.

===

Section 3.2

Are you sure that you want to send an Error message in response to a bad 
PCMonRep?

Sending an Error in response to a PCMonReq is useful because it cancels the 
request and means the sender does not continue to wait or a PCMonRep. But 
sending an Error in response to a PCMonRep does not seem to have any use 
except to load the network. For example, what is the state of the 
outstanding PCMonReq in this situation? What is the sender of the PCMonRep 
supposed to do when it receives the Error message?

More appropriate would be for the receiver of the bad PCMonRep to raise an 
alert to the operator and to put the sender of the bad message on a 
blacklist so that it never send it another PCMonReq.

===

Section 3.2

It would be useful to include references for the objects listed in the BNF 
as you do in Section 3.1.

===

Section 3.2

I'm slightly confused by the BNF.

   <metric-pce>::=[<PCE-ID>]
                  [<PROC-TIME>]
                  [<CONGESTION>]

This means that <metric-pce> can be completely empty.
Surely <PCE-ID> is mandatory within <metric-pce> ?

===

Section 4

You state that the P and I flags in the new objects are cleared.

I think you mean "SHOULD be set to zero and MUST be ignored"

===

Section 4
Second paragraph.

The case of "in band" monitoring seems to be described twice.

===

Section 4.2

The object has previously been referred to as the PCE-ID object. That seems 
like a better name. Can you check the whole I-D to make sure this is 
consistent.

===

Section 4.3

   If allowed by policy, the PCE includes a PROC-TIME object within a
   PCMonRep or a PCRep message if the P bit of the MONITORING object

This conflicts with Section 4.1

   P (Processing Time) - 1 bit: the P bit of the MONITORING object
   carried in a PCMonReq or a PCReq message is set to indicate that the
   processing times is a metric of interest, in which case a PROC-TIME
   object MUST be inserted in the corresponding PCMonRep or PCRep
   message.

I prefer the "if allowed by policy" which means you need to change the text 
Section 4.1.

===

Section 4.3
s/algorithm(s)/algorithms/  (twice)

===

Section 4.3

   Flags: 18 bits - No Flags are currently defined:

Looks like 16 bits, and one flag is defined!

===

Section 4.3
s/computation(s)/computations/

===

Section 4.3

   Unassigned bits are considered as reserved and MUST be set to zero on
   transmission.

Move this text to immediately after the definition of the E bit

===

Section 4.3

   More granularity may be introduced in further revision of this
   document to get a monitoring metric for a general request of a
   particular class (e.g. all PCReq of priority X).

I guess you decided not to do this. Delete the text.

===

Section 4.4

- Rather than one bit and a reserved field, shouldn't you have a
  flags field (with one bit assigned) and a reserved field.
- You need to explain that setting the C bit and a congestion
   duration of zero has meaning. If it has no meaning, you don't
   need the C bit.
- Although it verges on telling the implementer how to write code
  I think some advice is needed on what to do when a
  CONGESTION object is received with the C bit set. There
  are two aspects...
  - How long has the CONGESTION object taken to propagate
     from the reporting PCE to the PCC (might not be one hop)?
  - What should the receiver do with the Congestion Duration
     value?
- It may also be worth noting whether a PCE in the middle of a
   chain is allowed to look at the CONGESTION information
   that it receives from a downstream PCE and plans to pass on
   to an upstream PCE or PCC.

===

Section 6

   Reception of a PCMonReq message: upon receiving a PCMonReq message:

Can you sort out the over-use of colons?

===

Section 6, case 1)

I think you should refer explicitly to Section 6.9 of [PCEP] because that 
includes not only the error message, but some important back-off and 
shutdown procedures.

===

Section 6, case 2)

You should refer back to Section 5.
But note also that you have an explicit case (section 4.3) where policy 
causes the message to be processed but an object to be left out of the 
reply.

===

Section 6

You need a similar set of text for the in band case.

===

Section 7.2
s/MAY/may/

===

Section 7.6

   An implementation SHOULD allow handling PCReq messages with
   a higher priority than PCMonReq messages.

And when the monitoring is in band?

===

Section 8

It would be helpful to IANA if you split this into subsections for each 
registry/subregistry.
Also nice if you could try to cut and paste from the registry naming used in 
[PCEP].

===

Section 8

The IANA section doesn't seem to be complete.

For example:
- The flags field in the Monitoring Object
   (be careful to get the bit numbering correct :-)
- The flags field in the PROC-TIME object
- The flags field in the CONGESTION object

===

Section 9

Does the information gathered by monitoring represent any additional 
vulnerability? Could an attacker gain interesting information by snooping 
this?

I think the Congestion object is a good and lightweight way to attack a PCE 
deployment. You should note this and suggest that this makes the use of 
security mechanisms important. You may also need to node that there is a 
chain of trust model here such that even if one PCE ensures that it uses 
security, the information it supplies can be changed on a hop further 
upstream. Therefore, a consistent security model across all cooperating PCEs 
is desirable.

===

Section 11.2

[I-D.ietf-pce-disco-proto-isis] is not referenced (did you run I-D nits?)

[I-D.ietf-pce-of] and [I-D.ietf-pce-pcep-xro] are normative since they 
define objects that you cite explicitly.


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


From pce-bounces@ietf.org  Sat Dec 27 02:15: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 73F6D3A6A86;
	Sat, 27 Dec 2008 02:15: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 9B71B3A6A76; Sat, 27 Dec 2008 02: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: <20081227101501.9B71B3A6A76@core3.amsl.com>
Date: Sat, 27 Dec 2008 02:15:01 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-of-06.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           : Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)
	Author(s)       : J. Le Roux, et al.
	Filename        : draft-ietf-pce-of-06.txt
	Pages           : 20
	Date            : 2008-12-27

The computation of one or a set of Traffic Engineering Label Switched
Paths (TE LSPs) in MultiProtocol Label Switching (MPLS) and
Generalized MPLS (GMPLS) networks, is subject to a set of one or more
specific optimization criteria, referred to as objective functions
(e.g. minimum cost path, widest path, etc.).

In the Path Computation Element (PCE) architecture, a Path
Computation Client (PCC) may want a path to be computed for one or
more TE LSPs according to a specific objective function. Thus, the
PCC needs to instruct the PCE to use the correct objective function.
Furthermore, it is possible that not all PCEs support the same set of
objective functions, therefore it is useful for the PCC to be able to
automatically discover the set of objective functions supported by
each PCE.
This document defines extensions to the PCE communication Protocol
(PCEP) to allow a PCE to indicate the set of objective functions it
supports. Extensions are also defined so that a PCC can indicate in
a path computation request the required objective function, and so
that a PCE can report in a path computation reply the objective
function that was used for path computation.

This document defines objective function code types for six
objective functions previously listed in the PCE requirments work,
and provides the definition of four new metric types that apply to a
set of synchronized requests.

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

Content-Type: text/plain
Content-ID: <2008-12-27021435.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  Sat Dec 27 02:39:01 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 E54153A6783;
	Sat, 27 Dec 2008 02:39:01 -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 38E0F3A6783
	for <pce@core3.amsl.com>; Sat, 27 Dec 2008 02:39:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.982
X-Spam-Level: 
X-Spam-Status: No, score=-1.982 tagged_above=-999 required=5 tests=[AWL=0.616, 
	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 e6jKrKbT5Iam for <pce@core3.amsl.com>;
	Sat, 27 Dec 2008 02:39:00 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id 2114E3A676A
	for <pce@ietf.org>; Sat, 27 Dec 2008 02:38:59 -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
	mBRAcUuV008480; Sat, 27 Dec 2008 10:38: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
	mBRAcSCT008474; Sat, 27 Dec 2008 10:38:29 GMT
Message-ID: <FAA8C298002A496EAE1CB51013936403@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Ross Callon" <rcallon@juniper.net>, <pce@ietf.org>
Date: Sat, 27 Dec 2008 10:38:23 -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: Young Lee <ylee@huawei.com>
Subject: [Pce] draft-ietf-pce-of-06.txt updated after IETF 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,

A minor revision of this I-D to handle some requests for clarification made 
during IETF last call.

Also some updates to the IANA section to keep it in line with what IANA are 
doing for PCEP.

Cheers,
Adrian
----- Original Message ----- 
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Cc: <pce@ietf.org>
Sent: Saturday, December 27, 2008 10:15 AM
Subject: I-D Action:draft-ietf-pce-of-06.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           : Encoding of Objective Functions in the Path Computation 
> Element Communication Protocol (PCEP)
> Author(s)       : J. Le Roux, et al.
> Filename        : draft-ietf-pce-of-06.txt
> Pages           : 20
> Date            : 2008-12-27
>
> The computation of one or a set of Traffic Engineering Label Switched
> Paths (TE LSPs) in MultiProtocol Label Switching (MPLS) and
> Generalized MPLS (GMPLS) networks, is subject to a set of one or more
> specific optimization criteria, referred to as objective functions
> (e.g. minimum cost path, widest path, etc.).
>
> In the Path Computation Element (PCE) architecture, a Path
> Computation Client (PCC) may want a path to be computed for one or
> more TE LSPs according to a specific objective function. Thus, the
> PCC needs to instruct the PCE to use the correct objective function.
> Furthermore, it is possible that not all PCEs support the same set of
> objective functions, therefore it is useful for the PCC to be able to
> automatically discover the set of objective functions supported by
> each PCE.
> This document defines extensions to the PCE communication Protocol
> (PCEP) to allow a PCE to indicate the set of objective functions it
> supports. Extensions are also defined so that a PCC can indicate in
> a path computation request the required objective function, and so
> that a PCE can report in a path computation reply the objective
> function that was used for path computation.
>
> This document defines objective function code types for six
> objective functions previously listed in the PCE requirments work,
> and provides the definition of four new metric types that apply to a
> set of synchronized requests.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pce-of-06.txt 

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


From pce-bounces@ietf.org  Mon Dec 29 08:52: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 084C43A698E;
	Mon, 29 Dec 2008 08:52: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 C12C628C28B
	for <pce@core3.amsl.com>; Mon, 29 Dec 2008 08:52:19 -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=[AWL=0.001, 
	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 EoNus8l2wNMJ for <pce@core3.amsl.com>;
	Mon, 29 Dec 2008 08:52:18 -0800 (PST)
Received: from bizpsie4.9services.com (bizpsie4.9services.com [84.96.93.162])
	by core3.amsl.com (Postfix) with ESMTP id D17B43A68EF
	for <pce@ietf.org>; Mon, 29 Dec 2008 08:52:17 -0800 (PST)
Received: from pooky.marben-products.com ([86.65.15.130])
	by bizpsie4.9services.com with 9services
	id x4s51a00G2oN1dS044s5Hj; Mon, 29 Dec 2008 17:52:06 +0100
X-Biz3: ??
X-VRSPAM-SCORE: -100.00
Received: from AOFR11476 ([192.168.20.18])
	by pooky.marben-products.com (8.14.0/8.14.0) with ESMTP id
	mBTGq3K3003360 for <pce@ietf.org>; Mon, 29 Dec 2008 17:52:04 +0100
From: "Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com>
To: <pce@ietf.org>
Date: Mon, 29 Dec 2008 17:52:04 +0100
Message-ID: <000301c969d5$cafe8c40$1214a8c0@marbenproducts.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AclhZKFySjbMPCOZQeydpjmwe61AOQIcIP2w
In-Reply-To: <CC6BB4B4C3D34ABFA564FF76138CD348@your029b8cecfe>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: Re: [Pce] Last call comments on draft-ietf-pce-monitoring-02.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Hi,

Below my comments on monitoring draft:

Section 3.1: =


Example 3: The request must also contain a MONITORING object.

Section 3.2:

The format of a PCReq message is as follows:

Must be =


The format of a PCMonRep message is as follows:


Section 4.1:

Seems the first sentence is repeated twice.
Besides it is said that the Monitoring object MAY be included in PCReq and
PCRep so I think it would be good to add the enhanced PCReq and PCRep BNF
description.

General comment:

The in-band monitoring request is not fully clear to me.

If there are several path computation requests in the PCREq which one is
targeting?
i.e. Must the PCE return the processing time for each request seperatly or a
single processing time for all requests?

In first case what happens if there is an SVEC object and Path Requests are
spread in multiple PCRep messages. Must the Monitoring object be repeated?

If a PCRep contains a Monitoring object, is it possible that
this PCRep contains Path replies not related to the Monitoring request?

BR
Fabien

> -----Message d'origine-----
> De=A0: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] De la part de
> Adrian Farrel
> Envoy=E9=A0: vendredi 19 d=E9cembre 2008 00:02
> =C0=A0: pce@ietf.org
> Objet=A0: [Pce] Last call comments on draft-ietf-pce-monitoring-02.txt
> =

> Hi,
> =

> A few nitty comments on this draft.
> =

> Adrian
> =

> =3D=3D=3D
> =

> Abstract. Second sentence.
> =

> "In PCE-based environments, it is thus critical..."
> I don't think this follows as a conclusion from the previous sentence. In
> particular, there is no definition of a "path computation chain" and no
> explanation of the process involved in PCE that leads to the conclusion
> that
> certain things need to be monitored or troubleshooted.
> =

> I suggest inserting a new second sentence to give some background.
> Something
> like...
> =

>    Path Computation Clients (PCCs) send computation requests to PCEs,
>    and these may forward the requests to and cooperate with other PCEs
>    forming a "path computation chain".
> =

> You can then put in a paragraph break and continue with your text.
> =

> =3D=3D=3D
> =

> Section 1
> =

> You need to expand "PCC" and "TE LSP" on first usage as the Terminology
> section comes later.
> =

> =3D=3D=3D
> =

> Section 3
> =

> Please include a reference to draft-farrel-rtg-common-bnf-07.txt.
> At this stage you should (and can safely) make this a normative reference.
> The RBNF draft will go to IETF last call in early January and will be
> ahead
> of this draft in the processing queue.
> =

> =3D=3D=3D
> =

> Section 3
> =

> s/Computation Monitoring request/Computation Monitoring Request/
> =

> =3D=3D=3D
> =

> Section 3.1
> =

> <request> is shown to optionally contain the RRO.
> =

> The text that follows refers to the ERO.
> =

> I think the text is wrong.
> =

> =3D=3D=3D
> =

> Section 3.1
> =

> s/metric(s)/metrics/
> =

> =3D=3D=3D
> =

> Section 3.1
> =

> Examples 1 and 3 should also include a note that the requested information
> is returned in a PCMonRep.
> =

> =3D=3D=3D
> =

> Section 3.2
> =

> Are you sure that you want to send an Error message in response to a bad
> PCMonRep?
> =

> Sending an Error in response to a PCMonReq is useful because it cancels
> the
> request and means the sender does not continue to wait or a PCMonRep. But
> sending an Error in response to a PCMonRep does not seem to have any use
> except to load the network. For example, what is the state of the
> outstanding PCMonReq in this situation? What is the sender of the PCMonRep
> supposed to do when it receives the Error message?
> =

> More appropriate would be for the receiver of the bad PCMonRep to raise an
> alert to the operator and to put the sender of the bad message on a
> blacklist so that it never send it another PCMonReq.
> =

> =3D=3D=3D
> =

> Section 3.2
> =

> It would be useful to include references for the objects listed in the BNF
> as you do in Section 3.1.
> =

> =3D=3D=3D
> =

> Section 3.2
> =

> I'm slightly confused by the BNF.
> =

>    <metric-pce>::=3D[<PCE-ID>]
>                   [<PROC-TIME>]
>                   [<CONGESTION>]
> =

> This means that <metric-pce> can be completely empty.
> Surely <PCE-ID> is mandatory within <metric-pce> ?
> =

> =3D=3D=3D
> =

> Section 4
> =

> You state that the P and I flags in the new objects are cleared.
> =

> I think you mean "SHOULD be set to zero and MUST be ignored"
> =

> =3D=3D=3D
> =

> Section 4
> Second paragraph.
> =

> The case of "in band" monitoring seems to be described twice.
> =

> =3D=3D=3D
> =

> Section 4.2
> =

> The object has previously been referred to as the PCE-ID object. That
> seems
> like a better name. Can you check the whole I-D to make sure this is
> consistent.
> =

> =3D=3D=3D
> =

> Section 4.3
> =

>    If allowed by policy, the PCE includes a PROC-TIME object within a
>    PCMonRep or a PCRep message if the P bit of the MONITORING object
> =

> This conflicts with Section 4.1
> =

>    P (Processing Time) - 1 bit: the P bit of the MONITORING object
>    carried in a PCMonReq or a PCReq message is set to indicate that the
>    processing times is a metric of interest, in which case a PROC-TIME
>    object MUST be inserted in the corresponding PCMonRep or PCRep
>    message.
> =

> I prefer the "if allowed by policy" which means you need to change the
> text
> Section 4.1.
> =

> =3D=3D=3D
> =

> Section 4.3
> s/algorithm(s)/algorithms/  (twice)
> =

> =3D=3D=3D
> =

> Section 4.3
> =

>    Flags: 18 bits - No Flags are currently defined:
> =

> Looks like 16 bits, and one flag is defined!
> =

> =3D=3D=3D
> =

> Section 4.3
> s/computation(s)/computations/
> =

> =3D=3D=3D
> =

> Section 4.3
> =

>    Unassigned bits are considered as reserved and MUST be set to zero on
>    transmission.
> =

> Move this text to immediately after the definition of the E bit
> =

> =3D=3D=3D
> =

> Section 4.3
> =

>    More granularity may be introduced in further revision of this
>    document to get a monitoring metric for a general request of a
>    particular class (e.g. all PCReq of priority X).
> =

> I guess you decided not to do this. Delete the text.
> =

> =3D=3D=3D
> =

> Section 4.4
> =

> - Rather than one bit and a reserved field, shouldn't you have a
>   flags field (with one bit assigned) and a reserved field.
> - You need to explain that setting the C bit and a congestion
>    duration of zero has meaning. If it has no meaning, you don't
>    need the C bit.
> - Although it verges on telling the implementer how to write code
>   I think some advice is needed on what to do when a
>   CONGESTION object is received with the C bit set. There
>   are two aspects...
>   - How long has the CONGESTION object taken to propagate
>      from the reporting PCE to the PCC (might not be one hop)?
>   - What should the receiver do with the Congestion Duration
>      value?
> - It may also be worth noting whether a PCE in the middle of a
>    chain is allowed to look at the CONGESTION information
>    that it receives from a downstream PCE and plans to pass on
>    to an upstream PCE or PCC.
> =

> =3D=3D=3D
> =

> Section 6
> =

>    Reception of a PCMonReq message: upon receiving a PCMonReq message:
> =

> Can you sort out the over-use of colons?
> =

> =3D=3D=3D
> =

> Section 6, case 1)
> =

> I think you should refer explicitly to Section 6.9 of [PCEP] because that
> includes not only the error message, but some important back-off and
> shutdown procedures.
> =

> =3D=3D=3D
> =

> Section 6, case 2)
> =

> You should refer back to Section 5.
> But note also that you have an explicit case (section 4.3) where policy
> causes the message to be processed but an object to be left out of the
> reply.
> =

> =3D=3D=3D
> =

> Section 6
> =

> You need a similar set of text for the in band case.
> =

> =3D=3D=3D
> =

> Section 7.2
> s/MAY/may/
> =

> =3D=3D=3D
> =

> Section 7.6
> =

>    An implementation SHOULD allow handling PCReq messages with
>    a higher priority than PCMonReq messages.
> =

> And when the monitoring is in band?
> =

> =3D=3D=3D
> =

> Section 8
> =

> It would be helpful to IANA if you split this into subsections for each
> registry/subregistry.
> Also nice if you could try to cut and paste from the registry naming used
> in
> [PCEP].
> =

> =3D=3D=3D
> =

> Section 8
> =

> The IANA section doesn't seem to be complete.
> =

> For example:
> - The flags field in the Monitoring Object
>    (be careful to get the bit numbering correct :-)
> - The flags field in the PROC-TIME object
> - The flags field in the CONGESTION object
> =

> =3D=3D=3D
> =

> Section 9
> =

> Does the information gathered by monitoring represent any additional
> vulnerability? Could an attacker gain interesting information by snooping
> this?
> =

> I think the Congestion object is a good and lightweight way to attack a
> PCE
> deployment. You should note this and suggest that this makes the use of
> security mechanisms important. You may also need to node that there is a
> chain of trust model here such that even if one PCE ensures that it uses
> security, the information it supplies can be changed on a hop further
> upstream. Therefore, a consistent security model across all cooperating
> PCEs
> is desirable.
> =

> =3D=3D=3D
> =

> Section 11.2
> =

> [I-D.ietf-pce-disco-proto-isis] is not referenced (did you run I-D nits?)
> =

> [I-D.ietf-pce-of] and [I-D.ietf-pce-pcep-xro] are normative since they
> define objects that you cite explicitly.
> =

> =

> _______________________________________________
> 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 Dec 31 11:08: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 CAE013A68DC;
	Wed, 31 Dec 2008 11:08: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 7C61B3A68DC
	for <pce@core3.amsl.com>; Wed, 31 Dec 2008 11:08:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level: 
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5
	tests=[AWL=-0.110, BAYES_05=-1.11, 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 fDFyVqOBaS4e for <pce@core3.amsl.com>;
	Wed, 31 Dec 2008 11:08:20 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id 69F903A6824
	for <pce@ietf.org>; Wed, 31 Dec 2008 11:08:20 -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
	mBVJ7vCU019911; Wed, 31 Dec 2008 19:07:57 GMT
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	mBVJ7ukT019905; Wed, 31 Dec 2008 19:07:57 GMT
Message-ID: <D949C558C0ED460EB2ECD4EB1F51CF3B@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com>, <pce@ietf.org>
References: <000301c969d5$cafe8c40$1214a8c0@marbenproducts.com>
Date: Wed, 31 Dec 2008 19:07:41 -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] PCE Monitoring : wrong version last called
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

That is my fault :-(

The I-D is at revision -03

http://www.ietf.org/internet-drafts/draft-ietf-pce-monitoring-03.txt

You still have until Monday next week if you want to make comments.

As my punishment, I have gone through Fabien's email to check which of his 
coments still apply...

> Below my comments on monitoring draft:
>
> Section 3.1:
>
> Example 3: The request must also contain a MONITORING object.

Issue stands.

> Section 3.2:
>
> The format of a PCReq message is as follows:
>
> Must be
>
> The format of a PCMonRep message is as follows:

Issue stands

> Section 4.1:
>
> Seems the first sentence is repeated twice.

Fixed in revision -03

> Besides it is said that the Monitoring object MAY be included in
> PCReq and PCRep so I think it would be good to add the enhanced
> PCReq and PCRep BNF description.

Issue stands

Also in 4.1
s/PCEReq/PCReq/

> General comment:
>
> The in-band monitoring request is not fully clear to me.
>
> If there are several path computation requests in the PCReq
> which one is targeting?
> i.e. Must the PCE return the processing time for each request seperatly
> or a single processing time for all requests?
>
> In first case what happens if there is an SVEC object and Path Requests
> are spread in multiple PCRep messages. Must the Monitoring object be
> repeated?
>
> If a PCRep contains a Monitoring object, is it possible that
> this PCRep contains Path replies not related to the Monitoring
> request?

Issue stands.

Happy New Year

Adrian

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


