Subject: Price for 100mg x 60 pills $129.95

From: "Janice Gardner" <[email-masked]>
Date: Sun, 1 Jul 2007 02:07:33 -0900

$159.95 Viagra (Sildenafil) 100mg x 90 pills price
http://skinplural.hk

Delivery-date: Sat, 30 Jun 2007 22:39:19 +0000
Reply-To: "Adrian Farrel" <[email-masked]>
From: "Adrian Farrel" <[email-masked]>
To: <[email-masked]>
Cc: "Ross Callon" <[email-masked]>, <[email-masked]>, "'Sam Hartman'" <[email-masked]>, "Brungard, Deborah A, ALABS" <[email-masked]>
Subject: Progress with draft-ietf-ccamp-rsvp-restart-ext
Date: Sat, 30 Jun 2007 23:34:33 +0100

Hi,

The Routing ADs and chairs got together with Sam (as Security AD) to work 
through Sam's Discuss on this I-D.

Sam had some clear concerns about the trust model and security consequences 
introduced by the restart mechanisms introduced by this I-D. By dint of some 
hard work and open communication we have netted down the concerns and come 
up with a small set of changes to the draft that address Sam's concerns and 
make the draft clearer.

I don't believe that these edits in any way change the technical content of 
the draft, but they do make it clearer what you are not allowed to do. So I 
won't be issuing another WG last call, and there won't be another IETF last 
call.

But please look through the changes (below) and shout if there are any 
issues. It is still not too late to fine tune.

Thanks,
Adrian
===
Abstract
Add new 4th paragraph.

   These extensions are not used to create or restore data plane state.

===
Section 3. Introduction

Paragraph 2 begins...

   This document presents extensions to address two aspects of graceful
   restart not previously supported.  The presented extensions enable a
   restarting node to recover all objects in previously transmitted Path
   messages including the Explicit Route Object (ERO), from its
   downstream neighbors.

Append to this...

   and so recover control plane state. The extensions do not facilitate
   the recovery or creation of data/forwarding plane state, and can only
   be used to re-establish control plane state which matches in-place
   data/forwarding state.

===
Section 4.3.  Related Procedures

Add new 4th paragraph.

   There are no changes to the procedures with respect of the
   data/forwarding plane as described in [RFC3473]. In particular, a
   restarting node MUST NOT create data/forwarding plane state as the
   result of any of the extensions defined in this document.

===
4.5.2.  Procedures for the Restarting Node

Add to end of first paragraph.

   The restarting node MUST NOT create data plane or forwarding
   state to match the received RecoveryPath message.

===
4.5.2.2.  Re-Synchronization Procedures

Replace the final paragraph

OLD
   If no forwarding state is located, the node treats the path message
   as a setup for a new LSP.  The outgoing interface and label(s)
   indicated in the RecoveryPath message SHOULD be reused, when
   possible.  All other information contained in the RecoveryPath
   message MAY also be used.

NEW
   If no forwarding state is located, the node treats the received Path
   message as a setup request for a new LSP.  The outgoing interface and
   label(s) indicated in the RecoveryPath message SHOULD be reused, when
   possible.  All other information contained in the RecoveryPath
   message MAY also be used. That is, forwarding state MUST NOT be
   created except after receipt of a Path message from upstream or, at
   an ingress node, the receipt of a command from the management plane.
   Further, the forwarding state created is subject to local policy and
   the information received from downstream in the RecoveryPath message
   is treated only as advisory.

===
6.  Security Considerations

Add a final paragraph.

   Note that the procedures defined in this document cannot be used to
   create false forwarding state.  The restarting node that receives a
   RecoveryPath message that does not match the existing forwarding
   state MUST NOT create or modify its forwarding state to match.  A
   restarting node SHOULD log such an event or otherwise notify the
   operator since it might represent an attack.

Delivery-date: Sat, 30 Jun 2007 01:37:48 +0000
Date: Sat, 30 Jun 2007 09:34:33 +0800
From: Zhang Renhai <[email-masked]>
Subject: Re: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?
To: Adrian Farrel <[email-masked]>, Dan Li <[email-masked]>, ccamp <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>, Arun Satyanarayana <[email-masked]>

Yes, support it.

Zhang Renhai

> Hi,
> 
> In Prague we found that there was some support for this work, and no 
> opposition.
> 
> There were questions regarding clarifying that the work does not define new 
> process or procedures, but explains how existing procedures (i.e. 
> draft-ietf-ccamp-rsvp-restart-ext-08.txt) can be applied in a variety of 
> situations. I think that this revision has included this clarification.
> 
> There was a request to broaden the draft to cover all scenarios (not just 
> multi-node as before), and this has been done.
> 
> There was concern about whether there was "service provider" interest in 
> this work. In fact, several of the hands raised to express interest worked 
> for service providers. But I am not personally convinced that this 
> Informational work needs strong support from that sector. More to the point 
> would be support from the vendors who need to agree how they will operate 
> draft-ietf-ccamp-rsvp-restart-ext.
> 
> So, I'd like to ask the WG whether there is support to make this I-D a WG 
> draft.
> If we do, I would like to see it complete quite quickly. It would need:
> - review by vendors to make sure it is accurate
> - a bit more text on security issues
> 
> Thanks,
> Adrian
> 
> ----- Original Message ----- 
> From: "Dan Li" <[email-masked]>
> To: "ccamp" <[email-masked]>
> Cc: "Deborah A. Brungard" <[email-masked]>; "Farrel, Adrian" 
> <[email-masked]>; "Arun Satyanarayana" <[email-masked]>
> Sent: Friday, June 22, 2007 2:08 AM
> Subject: New draft: draft-li-ccamp-gr-description-00.txt
> 
> 
>> Dear CCAMPers,
>>
>> We have published a "new" I-D:
>> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-gr-description-00.txt
>>
>> This I-D replaces the previous I-D 
>> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-multinodes-gr-proc-01.txt.
>>
>> According to the discussion in Prague meeting, we have:
>> 1) Changed draft to be Informational. Mainly rewords the draft to make 
>> sure that it does not give instructions that could be interpreted as 
>> defining the procedures.
>> 2) The title of the I-D has been changed to "Description of the RSVP-TE 
>> Graceful Restart Procedures", in order to wide the scope of this I-D to 
>> include the single node graceful restart scenario.
>>
>> Best regards,
>> Dan Li 
> 
> 
> 
>

Delivery-date: Fri, 29 Jun 2007 09:49:17 +0000
Reply-To: "Adrian Farrel" <[email-masked]>
From: "Adrian Farrel" <[email-masked]>
To: <[email-masked]>
Subject: Fw: Internet-Drafts Submission Cutoff Dates for the 69th IETF  Meeting in Chicago, IL, USA 
Date: Fri, 29 Jun 2007 10:41:59 +0100

Reminder on draft cut-off dates.

Don't forget to use idnits (http://tools.ietf.org/tools/idnits/) to avoid 
having your submission rejected.

Adrian
----- Original Message ----- 
From: <[email-masked]>
To: <[email-masked]>
Cc: <[email-masked]>
Sent: Friday, June 29, 2007 5:00 AM
Subject: Internet-Drafts Submission Cutoff Dates for the 69th IETF Meeting 
in Chicago, IL, USA

>
> There are two (2) Internet-Draft cutoff dates for the 69th
> IETF Meeting in Chicago, IL, USA:
>
> July 2nd: Cutoff Date for Initial (i.e., version -00)
> Internet-Draft Submissions
>
> All initial Internet-Drafts (version -00) must be submitted by Monday,
> July 2nd at 9:00 AM ET. As always, all initial submissions with a
> filename beginning with "draft-ietf" must be approved by the
> appropriate WG Chair before they can be processed or announced.  The
> Secretariat would appreciate receiving WG Chair approval by Monday,
> June 25th at 9:00 AM ET.
>
> July 9th: Cutoff Date for Revised (i.e., version -01 and higher)
> Internet-Draft Submissions
>
> All revised Internet-Drafts (version -01 and higher) must be submitted
> by Monday, July 9th at 9:00 AM ET.
>
> Initial and revised Internet-Drafts received after their respective
> cutoff dates will not be made available in the Internet-Drafts
> directory or announced until on or after Monday, July 23rd at 9:00
> AM ET, when Internet-Draft posting resumes.  Please do not wait until
> the last minute to submit.
>
> Thank you for your understanding and cooperation. If you have any
> questions or concerns, then please send a message to
> [email-masked].
>
> The IETF Secretariat
>
> FYI: The Internet-Draft cutoff dates as well as other significant dates
> for the 69th IETF Meeting can be found at 
> http://www.ietf.org/meetings/cutoff_dates_69.html.
>
> 

Delivery-date: Thu, 28 Jun 2007 05:54:46 +0000
From: "fabien.verhaeghe" <[email-masked]>
To: "Adrian Farrel" <[email-masked]>, "Dan Li" <[email-masked]>, "ccamp" <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>, "Arun Satyanarayana" <[email-masked]>
Subject: Re: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?
Date: Thu, 28 Jun 2007 07:51:14 +0200

I support this draft.

Fabien

----- Original Message ----- 
From: "Adrian Farrel" <[email-masked]>
To: "Dan Li" <[email-masked]>; "ccamp" <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>; "Arun Satyanarayana" 
<[email-masked]>
Sent: Sunday, June 24, 2007 2:40 PM
Subject: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?

> Hi,
>
> In Prague we found that there was some support for this work, and no 
> opposition.
>
> There were questions regarding clarifying that the work does not define 
> new process or procedures, but explains how existing procedures (i.e. 
> draft-ietf-ccamp-rsvp-restart-ext-08.txt) can be applied in a variety of 
> situations. I think that this revision has included this clarification.
>
> There was a request to broaden the draft to cover all scenarios (not just 
> multi-node as before), and this has been done.
>
> There was concern about whether there was "service provider" interest in 
> this work. In fact, several of the hands raised to express interest worked 
> for service providers. But I am not personally convinced that this 
> Informational work needs strong support from that sector. More to the 
> point would be support from the vendors who need to agree how they will 
> operate draft-ietf-ccamp-rsvp-restart-ext.
>
> So, I'd like to ask the WG whether there is support to make this I-D a WG 
> draft.
> If we do, I would like to see it complete quite quickly. It would need:
> - review by vendors to make sure it is accurate
> - a bit more text on security issues
>
> Thanks,
> Adrian
>
> ----- Original Message ----- 
> From: "Dan Li" <[email-masked]>
> To: "ccamp" <[email-masked]>
> Cc: "Deborah A. Brungard" <[email-masked]>; "Farrel, Adrian" 
> <[email-masked]>; "Arun Satyanarayana" <[email-masked]>
> Sent: Friday, June 22, 2007 2:08 AM
> Subject: New draft: draft-li-ccamp-gr-description-00.txt
>
>
>> Dear CCAMPers,
>>
>> We have published a "new" I-D:
>> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-gr-description-00.txt
>>
>> This I-D replaces the previous I-D 
>> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-multinodes-gr-proc-01.txt.
>>
>> According to the discussion in Prague meeting, we have:
>> 1) Changed draft to be Informational. Mainly rewords the draft to make 
>> sure that it does not give instructions that could be interpreted as 
>> defining the procedures.
>> 2) The title of the I-D has been changed to "Description of the RSVP-TE 
>> Graceful Restart Procedures", in order to wide the scope of this I-D to 
>> include the single node graceful restart scenario.
>>
>> Best regards,
>> Dan Li
>
>
>
> 

Delivery-date: Wed, 27 Jun 2007 23:24:28 +0000
Content-class: urn:content-classes:message
Subject: RE: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?
Date: Wed, 27 Jun 2007 18:22:07 -0500
From: "Bardalai, Snigdho" <[email-masked]>
To: "Adrian Farrel" <[email-masked]>, "Dan Li" <[email-masked]>, "ccamp" <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>, "Arun Satyanarayana" <[email-masked]>

Support this ID as a WG document.

Snigdho

-----Original Message-----
From: [email-masked] [mailto:[email-masked]]On
Behalf Of Adrian Farrel
Sent: Sunday, June 24, 2007 7:41 AM
To: Dan Li; ccamp
Cc: Deborah A. Brungard; Arun Satyanarayana
Subject: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?

Hi,

In Prague we found that there was some support for this work, and no=20
opposition.

There were questions regarding clarifying that the work does not define =
new=20
process or procedures, but explains how existing procedures (i.e.=20
draft-ietf-ccamp-rsvp-restart-ext-08.txt) can be applied in a variety of =

situations. I think that this revision has included this clarification.

There was a request to broaden the draft to cover all scenarios (not =
just=20
multi-node as before), and this has been done.

There was concern about whether there was "service provider" interest in =

this work. In fact, several of the hands raised to express interest =
worked=20
for service providers. But I am not personally convinced that this=20
Informational work needs strong support from that sector. More to the =
point=20
would be support from the vendors who need to agree how they will =
operate=20
draft-ietf-ccamp-rsvp-restart-ext.

So, I'd like to ask the WG whether there is support to make this I-D a =
WG=20
draft.
If we do, I would like to see it complete quite quickly. It would need:
- review by vendors to make sure it is accurate
- a bit more text on security issues

Thanks,
Adrian

----- Original Message -----=20
From: "Dan Li" <[email-masked]>
To: "ccamp" <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>; "Farrel, Adrian"=20
<[email-masked]>; "Arun Satyanarayana" <[email-masked]>
Sent: Friday, June 22, 2007 2:08 AM
Subject: New draft: draft-li-ccamp-gr-description-00.txt

> Dear CCAMPers,
>
> We have published a "new" I-D:
> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-gr-description-00.txt
>
> This I-D replaces the previous I-D=20
> =
http://tools.ietf.org/wg/ccamp/draft-li-ccamp-multinodes-gr-proc-01.txt.
>
> According to the discussion in Prague meeting, we have:
> 1) Changed draft to be Informational. Mainly rewords the draft to make =

> sure that it does not give instructions that could be interpreted as=20
> defining the procedures.
> 2) The title of the I-D has been changed to "Description of the =
RSVP-TE=20
> Graceful Restart Procedures", in order to wide the scope of this I-D =
to=20
> include the single node graceful restart scenario.
>
> Best regards,
> Dan Li=20

Delivery-date: Wed, 27 Jun 2007 17:43:27 +0000
Date: Wed, 27 Jun 2007 10:39:29 -0700
From: Greg Bernstein <[email-masked]>
To: ccamp <[email-masked]>, [email-masked]
CC: Young Lee <[email-masked]>
Subject: New draft on wavelength switched optical networks

Hi CCAMPer's and PCEr's, we have just published a new draft on the 
"Applicability of GMPLS and PCE to Wavelength Switched Optical 
Networks"  
http://www.ietf.org/internet-drafts/draft-bernstein-ccamp-wavelength-switched-00.txt 
.

This draft looks at optical networks that include tunable lasers and 
ROADM (reconfigurable optical add/drop multiplexers) with no or limited 
wavelength conversion capability (these components are defined in the 
draft). 
These limitations lead to the RWA (routing and wavelength assignment) 
problem which is a bit more demanding in terms of input information and 
computation than other constrained path computation problems.  In the 
draft we look at the implications for GMPLS signaling, GMPLS routing, 
and PCE protocols and suggest some potential extensions to better 
accommodate this application.

We'd appreciate feedback/collaboration on (a) overall interest in this 
application, (b) requirements discussions, and (c) solution/extension 
discussions.

Cheers

Greg B.

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

Delivery-date: Wed, 27 Jun 2007 09:55:09 +0000
Content-class: urn:content-classes:message
Subject: RE: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?
Date: Wed, 27 Jun 2007 11:52:17 +0200
From: "Diego Caviglia (GA/ERI)" <[email-masked]>
To: "Adrian Farrel" <[email-masked]>, "Dan Li" <[email-masked]>, "ccamp" <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>

Me too I support this ID.

BR

Diego

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] On =
Behalf Of Mach Chen
Sent: mercoled=EC 27 giugno 2007 3.03
To: Adrian Farrel; Dan Li; ccamp
Cc: Deborah A. Brungard; Arun Satyanarayana
Subject: Re: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?

Yes,  Support this I-D to be a WG document.

Best regards,
Mach

----- Original Message -----=20
From: "Adrian Farrel" <[email-masked]>
To: "Dan Li" <[email-masked]>; "ccamp" <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>; "Arun Satyanarayana" =
<[email-masked]>
Sent: Sunday, June 24, 2007 8:40 PM
Subject: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?

> Hi,
>=20
> In Prague we found that there was some support for this work, and no=20
> opposition.
>=20
> There were questions regarding clarifying that the work does not =
define new=20
> process or procedures, but explains how existing procedures (i.e.=20
> draft-ietf-ccamp-rsvp-restart-ext-08.txt) can be applied in a variety =
of=20
> situations. I think that this revision has included this =
clarification.
>=20
> There was a request to broaden the draft to cover all scenarios (not =
just=20
> multi-node as before), and this has been done.
>=20
> There was concern about whether there was "service provider" interest =
in=20
> this work. In fact, several of the hands raised to express interest =
worked=20
> for service providers. But I am not personally convinced that this=20
> Informational work needs strong support from that sector. More to the =
point=20
> would be support from the vendors who need to agree how they will =
operate=20
> draft-ietf-ccamp-rsvp-restart-ext.
>=20
> So, I'd like to ask the WG whether there is support to make this I-D a =
WG=20
> draft.
> If we do, I would like to see it complete quite quickly. It would =
need:
> - review by vendors to make sure it is accurate
> - a bit more text on security issues
>=20
> Thanks,
> Adrian
>=20
> ----- Original Message -----=20
> From: "Dan Li" <[email-masked]>
> To: "ccamp" <[email-masked]>
> Cc: "Deborah A. Brungard" <[email-masked]>; "Farrel, Adrian"=20
> <[email-masked]>; "Arun Satyanarayana" <[email-masked]>
> Sent: Friday, June 22, 2007 2:08 AM
> Subject: New draft: draft-li-ccamp-gr-description-00.txt
>=20
>=20
>> Dear CCAMPers,
>>
>> We have published a "new" I-D:
>> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-gr-description-00.txt
>>
>> This I-D replaces the previous I-D=20
>> =
http://tools.ietf.org/wg/ccamp/draft-li-ccamp-multinodes-gr-proc-01.txt.
>>
>> According to the discussion in Prague meeting, we have:
>> 1) Changed draft to be Informational. Mainly rewords the draft to =
make=20
>> sure that it does not give instructions that could be interpreted as=20
>> defining the procedures.
>> 2) The title of the I-D has been changed to "Description of the =
RSVP-TE=20
>> Graceful Restart Procedures", in order to wide the scope of this I-D =
to=20
>> include the single node graceful restart scenario.
>>
>> Best regards,
>> Dan Li=20
>=20
>=20
>=20
>

Delivery-date: Wed, 27 Jun 2007 01:05:45 +0000
Date: Wed, 27 Jun 2007 09:02:45 +0800
From: Mach Chen <[email-masked]>
Subject: Re: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?
To: Adrian Farrel <[email-masked]>, Dan Li <[email-masked]>, ccamp <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>, Arun Satyanarayana <[email-masked]>

Yes,  Support this I-D to be a WG document.

Best regards,
Mach

----- Original Message ----- 
From: "Adrian Farrel" <[email-masked]>
To: "Dan Li" <[email-masked]>; "ccamp" <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>; "Arun Satyanarayana" <[email-masked]>
Sent: Sunday, June 24, 2007 8:40 PM
Subject: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?

> Hi,
> 
> In Prague we found that there was some support for this work, and no 
> opposition.
> 
> There were questions regarding clarifying that the work does not define new 
> process or procedures, but explains how existing procedures (i.e. 
> draft-ietf-ccamp-rsvp-restart-ext-08.txt) can be applied in a variety of 
> situations. I think that this revision has included this clarification.
> 
> There was a request to broaden the draft to cover all scenarios (not just 
> multi-node as before), and this has been done.
> 
> There was concern about whether there was "service provider" interest in 
> this work. In fact, several of the hands raised to express interest worked 
> for service providers. But I am not personally convinced that this 
> Informational work needs strong support from that sector. More to the point 
> would be support from the vendors who need to agree how they will operate 
> draft-ietf-ccamp-rsvp-restart-ext.
> 
> So, I'd like to ask the WG whether there is support to make this I-D a WG 
> draft.
> If we do, I would like to see it complete quite quickly. It would need:
> - review by vendors to make sure it is accurate
> - a bit more text on security issues
> 
> Thanks,
> Adrian
> 
> ----- Original Message ----- 
> From: "Dan Li" <[email-masked]>
> To: "ccamp" <[email-masked]>
> Cc: "Deborah A. Brungard" <[email-masked]>; "Farrel, Adrian" 
> <[email-masked]>; "Arun Satyanarayana" <[email-masked]>
> Sent: Friday, June 22, 2007 2:08 AM
> Subject: New draft: draft-li-ccamp-gr-description-00.txt
> 
> 
>> Dear CCAMPers,
>>
>> We have published a "new" I-D:
>> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-gr-description-00.txt
>>
>> This I-D replaces the previous I-D 
>> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-multinodes-gr-proc-01.txt.
>>
>> According to the discussion in Prague meeting, we have:
>> 1) Changed draft to be Informational. Mainly rewords the draft to make 
>> sure that it does not give instructions that could be interpreted as 
>> defining the procedures.
>> 2) The title of the I-D has been changed to "Description of the RSVP-TE 
>> Graceful Restart Procedures", in order to wide the scope of this I-D to 
>> include the single node graceful restart scenario.
>>
>> Best regards,
>> Dan Li 
> 
> 
> 
>

Delivery-date: Tue, 26 Jun 2007 14:50:45 +0000
Date: Tue, 26 Jun 2007 07:47:55 -0700
From: Greg Bernstein <[email-masked]>
To: ccamp <[email-masked]>
Subject: Re: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?

Yes. Promoting a clear understanding of the use of graceful restart in 
multiple contexts is beneficial.

Regards

Greg B.

Adrian Farrel wrote:
> Hi,
>
> In Prague we found that there was some support for this work, and no 
> opposition.
>
> There were questions regarding clarifying that the work does not 
> define new process or procedures, but explains how existing procedures 
> (i.e. draft-ietf-ccamp-rsvp-restart-ext-08.txt) can be applied in a 
> variety of situations. I think that this revision has included this 
> clarification.
>
> There was a request to broaden the draft to cover all scenarios (not 
> just multi-node as before), and this has been done.
>
> There was concern about whether there was "service provider" interest 
> in this work. In fact, several of the hands raised to express interest 
> worked for service providers. But I am not personally convinced that 
> this Informational work needs strong support from that sector. More to 
> the point would be support from the vendors who need to agree how they 
> will operate draft-ietf-ccamp-rsvp-restart-ext.
>
> So, I'd like to ask the WG whether there is support to make this I-D a 
> WG draft.
> If we do, I would like to see it complete quite quickly. It would need:
> - review by vendors to make sure it is accurate
> - a bit more text on security issues
>
> Thanks,
> Adrian
>
> ----- Original Message ----- From: "Dan Li" <[email-masked]>
> To: "ccamp" <[email-masked]>
> Cc: "Deborah A. Brungard" <[email-masked]>; "Farrel, Adrian" 
> <[email-masked]>; "Arun Satyanarayana" <[email-masked]>
> Sent: Friday, June 22, 2007 2:08 AM
> Subject: New draft: draft-li-ccamp-gr-description-00.txt
>
>
>> Dear CCAMPers,
>>
>> We have published a "new" I-D:
>> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-gr-description-00.txt
>>
>> This I-D replaces the previous I-D 
>> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-multinodes-gr-proc-01.txt.
>>
>> According to the discussion in Prague meeting, we have:
>> 1) Changed draft to be Informational. Mainly rewords the draft to 
>> make sure that it does not give instructions that could be 
>> interpreted as defining the procedures.
>> 2) The title of the I-D has been changed to "Description of the 
>> RSVP-TE Graceful Restart Procedures", in order to wide the scope of 
>> this I-D to include the single node graceful restart scenario.
>>
>> Best regards,
>> Dan Li 
>
>
>
>

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

Delivery-date: Mon, 25 Jun 2007 16:29:26 +0000
Date: Mon, 25 Jun 2007 11:28:45 -0500
From: Young Lee <[email-masked]>
Subject: RE: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?
To: 'Adrian Farrel' <[email-masked]>, 'Dan Li' <[email-masked]>, 'ccamp' <[email-masked]>
Cc: "'Deborah A. Brungard'" <[email-masked]>, 'Arun Satyanarayana' <[email-masked]>

Yes, I support this draft. 

Young

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] On Behalf
Of Adrian Farrel
Sent: Sunday, June 24, 2007 7:41 AM
To: Dan Li; ccamp
Cc: Deborah A. Brungard; Arun Satyanarayana
Subject: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?

Hi,

In Prague we found that there was some support for this work, and no 
opposition.

There were questions regarding clarifying that the work does not define new 
process or procedures, but explains how existing procedures (i.e. 
draft-ietf-ccamp-rsvp-restart-ext-08.txt) can be applied in a variety of 
situations. I think that this revision has included this clarification.

There was a request to broaden the draft to cover all scenarios (not just 
multi-node as before), and this has been done.

There was concern about whether there was "service provider" interest in 
this work. In fact, several of the hands raised to express interest worked 
for service providers. But I am not personally convinced that this 
Informational work needs strong support from that sector. More to the point 
would be support from the vendors who need to agree how they will operate 
draft-ietf-ccamp-rsvp-restart-ext.

So, I'd like to ask the WG whether there is support to make this I-D a WG 
draft.
If we do, I would like to see it complete quite quickly. It would need:
- review by vendors to make sure it is accurate
- a bit more text on security issues

Thanks,
Adrian

----- Original Message ----- 
From: "Dan Li" <[email-masked]>
To: "ccamp" <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>; "Farrel, Adrian" 
<[email-masked]>; "Arun Satyanarayana" <[email-masked]>
Sent: Friday, June 22, 2007 2:08 AM
Subject: New draft: draft-li-ccamp-gr-description-00.txt

> Dear CCAMPers,
>
> We have published a "new" I-D:
> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-gr-description-00.txt
>
> This I-D replaces the previous I-D 
> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-multinodes-gr-proc-01.txt.
>
> According to the discussion in Prague meeting, we have:
> 1) Changed draft to be Informational. Mainly rewords the draft to make 
> sure that it does not give instructions that could be interpreted as 
> defining the procedures.
> 2) The title of the I-D has been changed to "Description of the RSVP-TE 
> Graceful Restart Procedures", in order to wide the scope of this I-D to 
> include the single node graceful restart scenario.
>
> Best regards,
> Dan Li 

Delivery-date: Mon, 25 Jun 2007 16:24:29 +0000
From: "Lucy Yong" <[email-masked]>
To: "'Adrian Farrel'" <[email-masked]>, "'Dan Li'" <[email-masked]>, "'ccamp'" <[email-masked]>
Cc: "'Deborah A. Brungard'" <[email-masked]>, "'Arun Satyanarayana'" <[email-masked]>
Subject: RE: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?
Date: Mon, 25 Jun 2007 11:22:03 -0500

I support this draft to be a WG doc.
Lucy

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] On Behalf
Of Adrian Farrel
Sent: Sunday, June 24, 2007 7:41 AM
To: Dan Li; ccamp
Cc: Deborah A. Brungard; Arun Satyanarayana
Subject: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?

Hi,

In Prague we found that there was some support for this work, and no 
opposition.

There were questions regarding clarifying that the work does not define new 
process or procedures, but explains how existing procedures (i.e. 
draft-ietf-ccamp-rsvp-restart-ext-08.txt) can be applied in a variety of 
situations. I think that this revision has included this clarification.

There was a request to broaden the draft to cover all scenarios (not just 
multi-node as before), and this has been done.

There was concern about whether there was "service provider" interest in 
this work. In fact, several of the hands raised to express interest worked 
for service providers. But I am not personally convinced that this 
Informational work needs strong support from that sector. More to the point 
would be support from the vendors who need to agree how they will operate 
draft-ietf-ccamp-rsvp-restart-ext.

So, I'd like to ask the WG whether there is support to make this I-D a WG 
draft.
If we do, I would like to see it complete quite quickly. It would need:
- review by vendors to make sure it is accurate
- a bit more text on security issues

Thanks,
Adrian

----- Original Message ----- 
From: "Dan Li" <[email-masked]>
To: "ccamp" <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>; "Farrel, Adrian" 
<[email-masked]>; "Arun Satyanarayana" <[email-masked]>
Sent: Friday, June 22, 2007 2:08 AM
Subject: New draft: draft-li-ccamp-gr-description-00.txt

> Dear CCAMPers,
>
> We have published a "new" I-D:
> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-gr-description-00.txt
>
> This I-D replaces the previous I-D 
> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-multinodes-gr-proc-01.txt.
>
> According to the discussion in Prague meeting, we have:
> 1) Changed draft to be Informational. Mainly rewords the draft to make 
> sure that it does not give instructions that could be interpreted as 
> defining the procedures.
> 2) The title of the I-D has been changed to "Description of the RSVP-TE 
> Graceful Restart Procedures", in order to wide the scope of this I-D to 
> include the single node graceful restart scenario.
>
> Best regards,
> Dan Li 

Delivery-date: Sun, 24 Jun 2007 19:29:46 +0000
Date: Sun, 24 Jun 2007 12:27:39 -0700
From: "ping pan" <[email-masked]>
To: pwe3 <[email-masked]>, ccamp-list <[email-masked]>
Subject: Re: [Fwd: I-D ACTION:draft-pan-pwe3-pbb-tunnels-00.txt]

------=_Part_180664_551517.1182713259597
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 6/22/07, Ping Pan <[email-masked]> wrote:
>
> Hi,
>
> There has been much discussion on PBB/PBT vs. MPLS etc. Let's not go
> down that path here. ;-)
>
> Here is a proposal that we think it solves a practical problem, and
> takes the advantage of PBB and MPLS/PWE3.
>
> Please provide comment.
>
> Thanks!
>
> - Ping and others
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>        Title           : Setup and Manage PBB-based Tunnels with PWE3
> Mechanism
>        Author(s)       : P. Pan, et al.
>        Filename        : draft-pan-pwe3-pbb-tunnels-00.txt
>        Pages           : 11
>        Date            : 2007-6-22
>
>   This document describes a mechanism that enables providers to setup
>   point-to-point tunnels over PBB networks for the purpose of
>   aggregating customer flows. The interior network nodes will not be
>   disturbed with this mechanism.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> [email-masked] with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
> "get draft-pan-pwe3-pbb-tunnels-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
>        [email-masked].
> In the body type:
>        "FILE /internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt".
>
> NOTE:   The mail server at ietf.org can return the document in
>        MIME-encoded form by using the "mpack" utility.  To use this
>        feature, insert the command "ENCODING mime" before the "FILE"
>        command.  To decode the response(s), you will need "munpack" or
>        a MIME-compliant mail reader.  Different MIME-compliant mail
> readers
>        exhibit different behavior, especially when dealing with
>        "multipart" MIME messages (i.e. documents which have been split
>        up into multiple messages), so check your local documentation on
>        how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
> _______________________________________________
> I-D-Announce mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/i-d-announce
>
>

------=_Part_180664_551517.1182713259597
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<br>
<div><span class="gmail_quote">On 6/22/07, <b class="gmail_sendername">Ping Pan</b> &lt;<a href="mailto:[email-masked]">[email-masked]</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>There has been much discussion on PBB/PBT vs. MPLS etc. Let&#39;s not go<br>down that path here. ;-)
<br><br>Here is a proposal that we think it solves a practical problem, and<br>takes the advantage of PBB and MPLS/PWE3.<br><br>Please provide comment.<br><br>Thanks!<br><br>- Ping and others<br><br>A New Internet-Draft is available from the on-line Internet-Drafts
<br>directories.<br><br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Setup and Manage PBB-based Tunnels with PWE3 Mechanism<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : P. Pan, et al.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-pan-pwe3-pbb-tunnels-00.txt<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 11
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2007-6-22<br><br>&nbsp;&nbsp;This document describes a mechanism that enables providers to setup<br>&nbsp;&nbsp;point-to-point tunnels over PBB networks for the purpose of<br>&nbsp;&nbsp;aggregating customer flows. The interior network nodes will not be
<br>&nbsp;&nbsp;disturbed with this mechanism.<br><br><br>A URL for this Internet-Draft is:<br><a href="http://www.ietf.org/internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt">http://www.ietf.org/internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt
</a><br><br>To remove yourself from the I-D Announcement list, send a message to<br><a href="mailto:[email-masked]">[email-masked]</a> with the word unsubscribe in the body of<br>the message.
<br>You can also visit <a href="https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.ietf.org/mailman/listinfo/I-D-announce</a><br>to change your subscription settings.<br><br>Internet-Drafts are also available by anonymous FTP. Login with the
<br>username &quot;anonymous&quot; and a password of your e-mail address. After<br>logging in, type &quot;cd internet-drafts&quot; and then<br>&quot;get draft-pan-pwe3-pbb-tunnels-00.txt&quot;.<br><br>A list of Internet-Drafts directories can be found in
<br><a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a><br>or <a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br><br>Internet-Drafts can also be obtained by e-mail.
<br><br>Send a message to:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="mailto:[email-masked]">[email-masked]</a>.<br>In the body type:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;FILE /internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt&quot;.<br><br>NOTE:&nbsp;&nbsp; The mail server at 
<a href="http://ietf.org">ietf.org</a> can return the document in<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MIME-encoded form by using the &quot;mpack&quot; utility.&nbsp;&nbsp;To use this<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature, insert the command &quot;ENCODING mime&quot; before the &quot;FILE&quot;
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command.&nbsp;&nbsp;To decode the response(s), you will need &quot;munpack&quot; or<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a MIME-compliant mail reader.&nbsp;&nbsp;Different MIME-compliant mail readers<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exhibit different behavior, especially when dealing with
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;multipart&quot; MIME messages (i.e. documents which have been split<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; up into multiple messages), so check your local documentation on<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how to manipulate these messages.<br><br>Below is the data which will enable a MIME compliant mail reader
<br>implementation to automatically retrieve the ASCII version of the<br>Internet-Draft.<br><br><br>_______________________________________________<br>I-D-Announce mailing list<br><a href="mailto:[email-masked]">[email-masked]
</a><br><a href="https://www1.ietf.org/mailman/listinfo/i-d-announce">https://www1.ietf.org/mailman/listinfo/i-d-announce</a><br><br></blockquote></div><br>

------=_Part_180664_551517.1182713259597--

Delivery-date: Sun, 24 Jun 2007 16:51:04 +0000
Reply-To: "Adrian Farrel" <[email-masked]>
From: "Adrian Farrel" <[email-masked]>
To: "Dan Li" <[email-masked]>, "ccamp" <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>, "Arun Satyanarayana" <[email-masked]>
Subject: Support for draft-li-ccamp-gr-description-00.txt as WG I-D?
Date: Sun, 24 Jun 2007 13:40:34 +0100

Hi,

In Prague we found that there was some support for this work, and no 
opposition.

There were questions regarding clarifying that the work does not define new 
process or procedures, but explains how existing procedures (i.e. 
draft-ietf-ccamp-rsvp-restart-ext-08.txt) can be applied in a variety of 
situations. I think that this revision has included this clarification.

There was a request to broaden the draft to cover all scenarios (not just 
multi-node as before), and this has been done.

There was concern about whether there was "service provider" interest in 
this work. In fact, several of the hands raised to express interest worked 
for service providers. But I am not personally convinced that this 
Informational work needs strong support from that sector. More to the point 
would be support from the vendors who need to agree how they will operate 
draft-ietf-ccamp-rsvp-restart-ext.

So, I'd like to ask the WG whether there is support to make this I-D a WG 
draft.
If we do, I would like to see it complete quite quickly. It would need:
- review by vendors to make sure it is accurate
- a bit more text on security issues

Thanks,
Adrian

----- Original Message ----- 
From: "Dan Li" <[email-masked]>
To: "ccamp" <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>; "Farrel, Adrian" 
<[email-masked]>; "Arun Satyanarayana" <[email-masked]>
Sent: Friday, June 22, 2007 2:08 AM
Subject: New draft: draft-li-ccamp-gr-description-00.txt

> Dear CCAMPers,
>
> We have published a "new" I-D:
> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-gr-description-00.txt
>
> This I-D replaces the previous I-D 
> http://tools.ietf.org/wg/ccamp/draft-li-ccamp-multinodes-gr-proc-01.txt.
>
> According to the discussion in Prague meeting, we have:
> 1) Changed draft to be Informational. Mainly rewords the draft to make 
> sure that it does not give instructions that could be interpreted as 
> defining the procedures.
> 2) The title of the I-D has been changed to "Description of the RSVP-TE 
> Graceful Restart Procedures", in order to wide the scope of this I-D to 
> include the single node graceful restart scenario.
>
> Best regards,
> Dan Li 

Delivery-date: Sat, 23 Jun 2007 00:20:19 +0000
Date: Fri, 22 Jun 2007 17:15:47 -0700
From: Ping Pan <[email-masked]>
To: pwe3 <[email-masked]>, ccamp-list <[email-masked]>
Subject: [Fwd: I-D ACTION:draft-pan-pwe3-pbb-tunnels-00.txt]

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

Hi,

There has been much discussion on PBB/PBT vs. MPLS etc. Let's not go 
down that path here. ;-)

Here is a proposal that we think it solves a practical problem, and 
takes the advantage of PBB and MPLS/PWE3.

Please provide comment.

Thanks!

- Ping and others

--------------020906040204010404030608
Content-Type: message/rfc822;
 name="I-D ACTION:draft-pan-pwe3-pbb-tunnels-00.txt.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="I-D ACTION:draft-pan-pwe3-pbb-tunnels-00.txt.eml"

To: [email-masked]
Cc: 
From: [email-masked]
Date: Fri, 22 Jun 2007 15:50:01 -0400
Subject: I-D ACTION:draft-pan-pwe3-pbb-tunnels-00.txt 
Reply-To: [email-masked]

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.

	Title		: Setup and Manage PBB-based Tunnels with PWE3 Mechanism 
	Author(s)	: P. Pan, et al.
	Filename	: draft-pan-pwe3-pbb-tunnels-00.txt
	Pages		: 11
	Date		: 2007-6-22
	
   This document describes a mechanism that enables providers to setup 
   point-to-point tunnels over PBB networks for the purpose of 
   aggregating customer flows. The interior network nodes will not be 
   disturbed with this mechanism. 

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt

To remove yourself from the I-D Announcement list, send a message to 
[email-masked] with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-pan-pwe3-pbb-tunnels-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="[email-masked]"

Content-Type: text/plain
Content-ID: <[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-pan-pwe3-pbb-tunnels-00.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-pan-pwe3-pbb-tunnels-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <[email-masked]>

--OtherAccess--

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

_______________________________________________
I-D-Announce mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/i-d-announce

--NextPart--

--------------020906040204010404030608--

Delivery-date: Fri, 22 Jun 2007 01:12:32 +0000
Date: Fri, 22 Jun 2007 09:08:56 +0800
From: Dan Li <[email-masked]>
Subject: New draft: draft-li-ccamp-gr-description-00.txt
To: ccamp <[email-masked]>
Cc: "Deborah A. Brungard" <[email-masked]>, "Farrel, Adrian" <[email-masked]>, Arun Satyanarayana <[email-masked]>

This is a multi-part message in MIME format.

--Boundary_(ID_4FuVPMchlFA7tI9EAfGMMQ)
Content-type: text/plain; charset=Windows-1252
Content-transfer-encoding: 7BIT

Dear CCAMPers,

We have published a "new" I-D:
http://tools.ietf.org/wg/ccamp/draft-li-ccamp-gr-description-00.txt

This I-D replaces the previous I-D http://tools.ietf.org/wg/ccamp/draft-li-ccamp-multinodes-gr-proc-01.txt.

According to the discussion in Prague meeting, we have:
1) Changed draft to be Informational. Mainly rewords the draft to make sure that it does not give instructions that could be interpreted as defining the procedures. 
2) The title of the I-D has been changed to "Description of the RSVP-TE Graceful Restart Procedures", in order to wide the scope of this I-D to include the single node graceful restart scenario.

Best regards,

Dan Li

Advanced Technology Department
Wireline Networking Business Unit
Huawei Technologies Co., LTD.
Huawei Base, Bantian, Longgang,
Shenzhen 518129 P.R.China
Tel: +86-755-28973237
Fax: +86-755-28972935
***************************************************************************************
This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
***************************************************************************************

--Boundary_(ID_4FuVPMchlFA7tI9EAfGMMQ)
Content-type: text/html; charset=Windows-1252
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2800.1561" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>Dear CCAMPers,</DIV>
<DIV>&nbsp;</DIV>
<DIV>We have published a "new" I-D:</DIV>
<DIV><A 
href="http://tools.ietf.org/wg/ccamp/draft-li-ccamp-gr-description-00.txt">http://tools.ietf.org/wg/ccamp/draft-li-ccamp-gr-description-00.txt</A></DIV>
<DIV>&nbsp;</DIV>
<DIV>This I-D replaces the previous I-D <A 
href="http://tools.ietf.org/wg/ccamp/draft-li-ccamp-multinodes-gr-proc-01.txt">http://tools.ietf.org/wg/ccamp/draft-li-ccamp-multinodes-gr-proc-01.txt</A>.</DIV>
<DIV>&nbsp;</DIV>
<DIV>According to the discussion in Prague meeting, we have:</DIV>
<DIV>1)&nbsp;Changed draft to be Informational. Mainly rewords the draft to make 
sure that it does not give instructions that could be interpreted 
as&nbsp;defining the procedures. </DIV>
<DIV>2) The&nbsp;title of the I-D has been changed to "Description of the 
RSVP-TE Graceful Restart Procedures", in order to wide the scope of this I-D to 
include the single node&nbsp;graceful restart scenario.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Best regards,</DIV>
<DIV>&nbsp;&nbsp;<BR></DIV>
<DIV>Dan Li</DIV>
<DIV>&nbsp;</DIV>
<DIV>Advanced Technology Department<BR>Wireline Networking Business 
Unit<BR>Huawei Technologies Co., LTD.<BR>Huawei Base, Bantian, 
Longgang,<BR>Shenzhen 518129 P.R.China<BR>Tel: +86-755-28973237<BR>Fax: 
+86-755-28972935<BR>***************************************************************************************<BR>This 
e-mail and its attachments contain confidential information from HUAWEI, which 
is intended only for the person or entity whose address is listed above. Any use 
of the information contained herein in any way (including, but not limited to, 
total or partial disclosure, reproduction, or dissemination) by persons other 
than the intended recipient(s) is prohibited. If you receive this e-mail in 
error, please notify the sender by phone or email immediately and delete 
it!<BR>***************************************************************************************<BR></DIV></BODY></HTML>

--Boundary_(ID_4FuVPMchlFA7tI9EAfGMMQ)--

Delivery-date: Sat, 16 Jun 2007 10:44:25 +0000
Reply-To: "Adrian Farrel" <[email-masked]>
From: "Adrian Farrel" <[email-masked]>
To: <[email-masked]>
Subject: Fw: 69th IETF - DRAFT Meeting Agenda 
Date: Sat, 16 Jun 2007 11:40:24 +0100

The Secretariat has stabilised the agenda for Chicago:

> The DRAFT agenda for the 69th IETF Meeting can be found at:
> http://www.ietf.org/meetings/69-IETF.html
>
> Please note that the agenda is in draft form and is subject to change
> before the final agenda is published on Monday, July 2nd.

CCAMP again has two slots:
Tuesday 9.00-11.30
Wednesday 13.00-15.00

We hope that the double slot at Prague and in Chicago will help us clear the 
backlog and we will be able to revert to using less agenda time in future 
meetings.

Please let us know if you have material for the agenda in Chicago.

Thanks,
Adrian and Deborah 

Delivery-date: Fri, 15 Jun 2007 13:50:41 +0000
To: [email-masked]
From: "Thomas D. Nadeau" <[email-masked]>
Subject: =?WINDOWS-1252?Q?IEEE_ComMag_Feature_Topic_on_"Next-Generation_C?= =?WINDOWS-1252?Q?arrier_Ethernet_Transport_Technologies=94?=
Date: Fri, 15 Jun 2007 09:48:04 -0400

                                    CALL FOR PAPERS
                             ------------------------------

IEEE Communications Magazine Feature Topic on
"Next-Generation Carrier Ethernet Transport Technologies=94

Over the last few years, the share of packet-dominated traffic has =20
grown exponentially in networks worldwide. As a result packet-based =20
transport technologies such as MPLS are increasingly deemed to be =20
more efficient for carrying this traffic compared to legacy SDH/SONET =20=

technology (and its next-generation incarnations) or the more =20
familiar ATM/FR technology. A majority of this traffic is now either =20
Ethernet or Internet Protocol (IP), so enterprises (and even =20
residential customers) familiar with Ethernet technology have begun =20
demanding a simple, inexpensive and high-speed universal Ethernet =20
service. With the availability of low-cost, high-bandwidth Ethernet =20
beyond the Local Area Network, the Metro Ethernet Forum (MEF) has =20
defined such a service as Carrier Ethernet, and defined it as a =20
ubiquitous, standardized, carrier-class service/application =20
characterized by some key attributes: reliability, hard Quality-of-=20
Service (QoS), service management, and scalability.

These features set it apart from the ubiquitously deployed LAN-based =20
Ethernet and serve as an add-on to switched Ethernet (GigE, and =20
10GigE variants). There are, however, several options for building =20
the underlying transport infrastructure to deliver such a carrier =20
Ethernet service. These include, for example, using: IP/MPLS =20
technology to deliver point-to-point Ethernet circuits joined =20
together with physical Ethernet bridges/switches; IP/MPLS with =20
Virtual-Private LAN Service (VPLS) or Hierarchical Virtual Private =20
LAN Service (H-VPLS) (developed at the IETF); Transport-MPLS (T-MPLS) =20=

being proposed at the ITU-T, using modified Ethernet technology with =20
Provider Backbone Bridging (PBB) and Provider-Backbone Transport =20
(PBT) being proposed at the IEEE; using a combination of a modified =20
Ethernet data-plane and a GMPLS-based control-plane with VLAN cross-=20
connect (being proposed by several vendors and under consideration at =20=

the IETF) and Circuit Emulation Services (CES) over an Ethernet =20
fabric to provision Pseudo Wires (PWs).

The quest, therefore, is for the most feature rich, and CAPEX/OPEX =20
efficient, packet-based transport infrastructure for next-generation =20
Carrier Ethernet services. Debate and discussion is rife in the =20
industry and the academic/research communities about which technology =20=

will provide the best combination of cost, ease of use, OAM features, =20=

performance and service management, ability to offer Quality-of-=20
Service (QoS) guarantees, traffic engineering, and resilience, and =20
capability to manage and bill for services running atop the transport =20=

infrastructure.

This special issue aims to consolidate and disseminate the latest =20
developments and advances in transport technology options for Carrier =20=

Ethernet service. With this objective, the list of topics includes =20
(but will not be limited to) the following:

=95           Metro Ethernet and Carrier Ethernet evolutions =96 =20
requirements, services specifications, carrier drivers, customer drivers
=95           Requirements on QoS, traffic engineering, resilience, =20
manageability, OAM, and service scalability for carrier Ethernet =20
transport technologies
=95           IP/MPLS (VPLS, H-VPLS) for carrier Ethernet services =96 =20=

choices, pros, cons, costs/benefits
=95           Provider Backbone Bridging (PBB) and Provider Backbone =20
Transport-Traffic Engineered (PBT-TE) as alternatives to IP/MPLS for =20
Ethernet transport =96 pros, cons, costs/benefits
=95           Transport-MPLS for carrier Ethernet =96 pros, cons, costs/=20=

benefits
=95           GMPLS-based control of Ethernet networks =96 changes in =
the =20
data and control planes
=95           Assessment of the proposed transport solutions in terms =20=

of their ability to provide QoS, traffic engineering, resilience, =20
manageability, and so on.
=95           OAM, network management, service management =96 options, =20=

choices, pitfalls, needs, and cost analysis and comparison of solutions.
=95           Solutions that meet the perceived requirements of the =20
community that are alternatives to the ones being proposed in the =20
various standards bodies.
=95           Traffic engineering and dimensioning of carrier Ethernet =20=

transport networks
=95           Techniques to ensure QoS, especially with a mix of =20
transport technologies in use
=95           Analysis and studies of resilience and protection =20
approaches utilized by different transport architectures and =20
associated technologies
=95           Studies comparing the different transport technologies =20
along multiple dimensions =96 deployment cost, day-to-day running cost, =20=

features provided, ease of deployment/management, and so on
=95           Comparisons and case-studies from the provider community =20=

to highlight why existing technologies do not meet current and =20
evolving provider requirements.
=95           Commentaries from providers who feel existing techniques/=20=

choices meet their requirements or can be easily modified to meet =20
their requirements.
=95           Network operators, vendors, and standards bodies=92 =20
perspectives on any of the above.
=95           Implementations, test-beds and field trials related to =20
carrier Ethernet transport technologies
=95           State of current standards

Submission

Articles should be tutorial in nature and should be written in a =20
style comprehensible to readers outside the specialty of the article. =20=

Articles may be edited for clarity and grammatical accuracy, and will =20=

be copyedited according to the Magazine's style. Mathematical =20
equations should not be used (in justified cases up to three simple =20
equations could be allowed, provided there is consent of the Guest =20
Editor; more than three equations require permission from the Editor-=20
in-Chief). Articles should have no more than 4,500 words, no more =20
than 6 tables/figures, and no more than 15 references. Guidelines for =20=

prospective authors can be found on-line at http://www.comsoc.org/=20
pubs/commag/sub_guidelines.html. Please submit no later than 31 July =20
2007. All articles to be considered for publication must be submitted =20=

through IEEE Manuscript Central (http://commag-=20
ieee.manuscriptcentral.com). Please select "March 2008/Next-=20
Generation Carrier Ethernet Transport Technologies" in the drop down =20
menu. Accepted papers will also be included in Communications =20
Interactive (CI), the online version of Communications Magazine.

Manuscript Due:                        1 August  2007
Acceptance Notification:             1 November 2007
Final Manuscript Due:                1 December 2007
Publication Date:                       March 2008

Guest Editors:
Thomas D. Nadeau, Cisco Systems, Inc., ([email-masked])
Vishal Sharma, Metanoia, Inc. ([email-masked])
Ashwin Gumaste, Indian Institute of Technology Bombay ([email-masked])

Envelope-to: [email-masked]
Delivery-date: Thu, 14 Jun 2007 15:05:08 +0000
To: IETF-Announce <[email-masked]>
From: The IESG <[email-masked]>
Subject: Last Call: draft-ietf-ccamp-te-node-cap (IGP Routing Protocol  Extensions for Discovery of Traffic Engineering Node  Capabilities) to Proposed Standard 
Reply-To: [email-masked]
Cc: <[email-masked]>
Message-Id: <[email-masked]>
Date: Thu, 14 Jun 2007 11:02:11 -0400

The IESG has received a request from the Common Control and Measurement 
Plane WG (ccamp) to consider the following document:

- 'IGP Routing Protocol Extensions for Discovery of Traffic Engineering 
   Node Capabilities '
   <draft-ietf-ccamp-te-node-cap-05.txt> as a Proposed Standard

This last call is being repeated to clarify a downref.

This document has a normative reference to an informational RFC,
RFC 3784.  RFC 3784 is part of a group of informational RFCs that
was published as informational instead of standards-track for
historical reasons, and there is current work in progress to advance
it to standards track.  However, to avoid unnecessary delay for
this document, the IESG proposes using a combination of the RFC
3967 rule (this Last Call) and the annotation described in section
4 of draft-klensin-norm-ref (currently in Last Call).  The annotation
will read:

    As of this writing, there is ongoing work to republish RFC  
    3784 on the IETF Standards Track.  Please consult the
    RFC Index to see if this has occurred, and see the updated
    reference if so.

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
[email-masked] mailing lists by 2007-06-28. Exceptionally, 
comments may be sent to [email-masked] 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-ccamp-te-node-cap-05.txt

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

Envelope-to: [email-masked]
Delivery-date: Tue, 12 Jun 2007 19:01:05 +0000
From: The IESG <[email-masked]>
To: IETF-Announce <[email-masked]>
Cc: Internet Architecture Board <[email-masked]>, RFC Editor <[email-masked]>, ccamp mailing list <[email-masked]>, ccamp chair <[email-masked]>
Subject: Document Action: 'Use of Addresses in Generalized  Multi-Protocol Label Switching (GMPLS) Networks' to  Informational RFC 
Message-Id: <[email-masked]>
Date: Tue, 12 Jun 2007 14:57:58 -0400

The IESG has approved the following document:

- 'Use of Addresses in Generalized Multi-Protocol Label Switching 
   (GMPLS) Networks '
   <draft-ietf-ccamp-gmpls-addressing-08.txt> as an Informational RFC

This document is the product of the Common Control and Measurement Plane
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-ccamp-gmpls-addressing-08.txt

Technical Summary
 
   This informational document clarifies the use of addresses in 
   Generalized Multi-Protocol Label Switching (GMPLS) networks. The 
   aim is to facilitate interworking of GMPLS-capable Label Switching   
   Routers (LSRs). The document is based on experience gained in 
   implementation, interoperability testing, and deployment.

   This document does not define new procedures nor processes nor 
   does it define a standard. 

Working Group Summary
 
   There was general consensus to publish this as informational. 
 
Protocol Quality
 
   Ross Callon has reviewed this for the IESG. Adrian Farrel has also
   reviewed this informational document.

Delivery-date: Mon, 11 Jun 2007 20:03:05 +0000
Reply-To: "Adrian Farrel" <[email-masked]>
From: "Adrian Farrel" <[email-masked]>
To: <[email-masked]>
Subject: Fw: I-D ACTION:draft-ietf-ccamp-gmpls-addressing-08.txt 
Date: Mon, 11 Jun 2007 21:02:04 +0100

New revision to address the Comments and one Discuss raised during IESG 
review.

See 
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13120&rfc_flag=0

Adrian
----- Original Message ----- 
From: <[email-masked]>
To: <[email-masked]>
Cc: <[email-masked]>
Sent: Monday, June 11, 2007 8:50 PM
Subject: I-D ACTION:draft-ietf-ccamp-gmpls-addressing-08.txt

>A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Common Control and Measurement Plane 
> Working Group of the IETF.
>
> Title : Use of Addresses in Generalized Multi-Protocol Label Switching 
> (GMPLS) Networks
> Author(s) : K. Shiomoto, et al.
> Filename : draft-ietf-ccamp-gmpls-addressing-08.txt
> Pages : 22
> Date : 2007-6-11
>
> This document clarifies the use of addresses in Generalized
>   Multi-Protocol Label Switching (GMPLS) networks. The aim is to
>   facilitate interworking of GMPLS-capable Label Switching Routers
>   (LSRs). The document is based on experience gained in implementation,
>   interoperability testing, and deployment.
>
>   The document describes how to interpret address and identifier fields
>   within GMPLS protocols, and how to choose which addresses to set in
>   those fields for specific control plane usage models. It also
>   discusses how to handle IPv6 sources and destinations in the MPLS and
>   GMPLS Traffic Engineering (TE) Management Information Base (MIB)
>   modules.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-addressing-08.txt
>

Delivery-date: Mon, 11 Jun 2007 19:52:44 +0000
To: [email-masked]
Cc: [email-masked]
From: [email-masked]
Subject: I-D ACTION:draft-ietf-ccamp-gmpls-addressing-08.txt 
Date: Mon, 11 Jun 2007 15:50:02 -0400

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.

	Title		: Use of Addresses in Generalized Multi-Protocol Label Switching (GMPLS) Networks
	Author(s)	: K. Shiomoto, et al.
	Filename	: draft-ietf-ccamp-gmpls-addressing-08.txt
	Pages		: 22
	Date		: 2007-6-11
	
This document clarifies the use of addresses in Generalized
   Multi-Protocol Label Switching (GMPLS) networks. The aim is to
   facilitate interworking of GMPLS-capable Label Switching Routers
   (LSRs). The document is based on experience gained in implementation,
   interoperability testing, and deployment.

   The document describes how to interpret address and identifier fields
   within GMPLS protocols, and how to choose which addresses to set in
   those fields for specific control plane usage models. It also
   discusses how to handle IPv6 sources and destinations in the MPLS and
   GMPLS Traffic Engineering (TE) Management Information Base (MIB)
   modules.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-addressing-08.txt

To remove yourself from the I-D Announcement list, send a message to 
[email-masked] with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-ccamp-gmpls-addressing-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-ccamp-gmpls-addressing-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-ccamp-gmpls-addressing-08.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-gmpls-addressing-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email-masked]>

--OtherAccess--

--NextPart--

Delivery-date: Mon, 11 Jun 2007 13:15:59 +0000
Reply-To: "Adrian Farrel" <[email-masked]>
From: "Adrian Farrel" <[email-masked]>
To: "Zafar Ali" <[email-masked]>, <[email-masked]>
Cc: "'Jean Philippe Vasseur'" <[email-masked]>, "'Anca Zamfir'" <[email-masked]>, <[email-masked]>, "Brungard, Deborah A, ALABS" <[email-masked]>
Subject: Re: I-D ACTION:draft-ietf-ccamp-mpls-graceful-shutdown-03.txt 
Date: Mon, 11 Jun 2007 14:11:51 +0100

Hi,

The authors have indicated that this draft is complete and ready for WG last 
call.

As is now our customary ritual, the chairs have done a pre-last call review. 
In this case, I am the lucky reviewer.

Although the changes below are relatively minor in substance, they are many. 
I feel it would be helpful to reviewers in last call if you could provide an 
update with these issues fixed. As soon as I see it published we can 
initiate last call (subject to the Chicago meeting not getting in the way).

Thanks,
Adrian

===
"GMPLS" in title, abstract, and first use in main text.
Unfortunately, "GMPLS" is still not a recognised term in the wider IETF.
You must, therefore, expand the acronym where it first occurs.
===
Abstract line 1
s/shutdown/Shutdown/
===
Abstract para 1
s/towards/toward/
===
Abstract para 1
s/addressing the planned/addressing planned/
===
Abstract
"These operations are equally
   applicable for both MPLS and its GMPLS extensions."
If so, why have you named the document as you have.
Wouldn't a better name have been:
Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks
===
Conventions used in this document
Section contains a reference to "[i]" that is not resolved.
===
Contents table
Formatting is scrappy
===
1. Terminology
s/LSR - Label Switching Device./LSR - Label Switching Router./
===
1. Terminology
"LSP - An MPLS Label Switched Path"
What happened to GMPLS?
===
1. Terminology
The definition for "Head-end or Ingress node:" is very hard to read and, I 
suspect, non-intuitive. Redefining "head-end" to mean "sometimes also a 
transit node" will really fry people's minds! If you need a term for a node 
that performs a specific function, I suggest that you create a new term 
rather than overloading an existing one.
===
1. Terminology
"GMPLS - The term GMPLS is used in this document to refer to both
 classic MPLS, as well as the GMPLS extensions to MPLS."
You mean LDP?
===
1. Terminology
TE Link
a. You need to provide an expansion of FA-LSP, and probably a reference
b. Your definition has not caught all of the possible uses of a TE link 
(such
   as link bundles). Perhaps you want to use a generic definition?
===
2. Introduction
"disable Traffic Engineering on a TE Link"
This begs the question: what is traffic engineering?
Are you disabling TE on the link, or are you disabling data traffic on the 
link?
I think some work throughout the document to clarify the difference between:
- the impact of disabling a link (viz. traffic cannot flow)
and
- disabling TE advertisement (viz. the link's capacity is withdrawn from the 
TED).
The latter being the way to gracefully advertise the former.
===
2. Introduction  para 1
s/graceful reroute/gracefully reroute/
===
2. Introduction
"The node initiating the graceful shutdown condition
   SHOULD delay the removal of the resources for forwarding, for
   some period determined by local policy."
The point is not the delay. The point is the delay between disabling the 
resource in the control plane and removing the resource for forwarding.
Can you clarify, please.
===
2. Introduction para 2
s/allow control/allow the control/
===
2. Introduction para 2
"Similarly, trigger for the graceful
   shutdown event is a local matter at the node initiating the
   graceful shutdown."
a. Similarly to what?
b. s/trigger/the trigger/
===
2. Introduction
"traditional shutdown operation of an interface"
I like this phrase.
My family have been shutting down interfaces for generations. We use 
traditional techniques involving spun grass and a hand axe.
===
2. Introduction
Last line
s/node/nodes/
===
Section 3.
Formatting is broken.
Indentation and bullets.
===
Section 3  2nd requirement
This reads a bit odd. Would it be better as:

- Once an operator has initiated graceful shutdown of a network
resource, no new TE LSPs may be set up that use the resource.
Any signaling message for a new LSP that explicitly specifies the
resource, or that would require the use of the resource due to
local constraints, must be rejected as if the resource were
unavailable.

- It is desirable for new LSP setup attempts that would be rejected
because of graceful shutdown of a resource (as described in the
previous requirement) to avoid any attempt to use the resource by
selecting an alternate route or other resources.
===
Section 3
"   - It is required to reduce/eliminate traffic disruption on the
   LSP(s) using the network resources which are about to be
   shutdown."
Is this the requirement, or is the requirement to give the ingress the 
opportunity to perform this function if policy and configuration require it, 
and if network resources allow?
===
Section 3
"   - In order to make rerouting effective, it is required to
   communicate information about the TE resource under graceful
   shutdown."
I know what you mean, but you have been terribly non-specific. Communicate 
what information from whom to whom?
It is probably:
- the fact that the resource is being shut down
- from the node where the resource is located
- to all other network nodes
===
Page 4 (and several other places)
Excessive page throws
===
Section 4.1
  "Setup request for new LSPs over the TE resource being gracefully
   shutdown SHOULD be rejected using the existing mechanisms that
   are applied when the TE resource is not available."
Are you sure that you don't want to reject the setup using one of your new 
error codes?
===
Section 4.1.1
   The "local
   TE link maintenance required" error code is defined in [PATH-
   REOPT].
s/local TE link/local link/
In the whole of this section, and the rest of the document, please be 
careful to distinguish Error Codes and Error Values. In this case you are 
talking about an Error Value that is associated with the "Notify" Error 
Code. It is necessary to describe both fields.
===
Section 4.1.1
Suddenly you are abbreviating to "GS". I think that is inadvisable.
===
General question.
Would it help the ingress or PLR if the PathErr reporting imminent graceful 
shutdown included additional information such as the likely time of shutdown 
in the data plane, and the likely time of restart?
We do have mechanisms for this function in RFC 4783.
===
Section 4.1.1
   When a head-end LSR receives a Path Error (or Notify) message
   with sub-code "Local Maintenance on TE Link required Flag", it
   SHOULD immediately trigger a make-before-break procedure. A head-
   end node SHOULD avoid the IP address contained in the PathErr (or
   Notify message) when performing path computation for the new LSP.
a. The name of the subcode continues to mutate :-)
b. The first SHOULD is *entirely* a matter of local policy. It is a MAY.
c. The second SHOULD is ambiguous as you haven't told us which
   IP address is contained in the PathErr. Since the Error Value is
   related to a TE Link, presumably it is the TE link IP address. But
   what if it is a node being shut down? What if it is only a lambda
   being shut down?
   Can you not use some more informative fields and reason codes
   as provided in draft-ietf-ccamp-crankback-06.txt or RFC4872?
d. Please be consistent and use "Path Error" or "PathErr". I prefer the
   second.
===
Section 4.1.1
   If the resource being gracefully shutdown is on the Path of the
   protecting LSP/ local detour, the branch node/ PLR reroutes the
   protecting LSP/ local detour just a head-end LSR would reroute
   any other LSP.
Need to tidy up the text.
But what are you saying? One LSP is the same as another, and reroute takes 
place from the head end. That is all.
===
Section 4.1.2
   RSVP error-code "Routing Problem" (24) [RSVP-TE] is
   needed:
         9 (TBA)   Local component link maintenance required
Why is this a subcode of Routing Problem, when you have used a subcode of 
Notify for the case of the whole TE link?
More importantly, the use of Routing Problem is likely to cause us to run 
into questions about whether the upstream transit nodes will panic and tear 
the LSP or not. Using the Notify Error Code is a much safer approach.
===
Section 4.1.2
   The head-end LSR MAY still use the IP address
   contained in the Path Error or Notify message in performing path
   computation for rerouting the LSP. This is because, this address
   is an IP address of the component link and the flag is an
   implicit indication that the TE link may still have capacity to
   admit new LSPs.
If the IP address is the address of the component link being shut down, then 
it cannot be used in the new path. If, however, the address is the address 
of the link bundle, then it can still be used.
===
Important
I think you are missing an element of procedure that applies at the node 
doing shut down.
please state clearly which addresses are placed in which fields when 
reporting graceful shutdown for a:
- node
- te link
- component link
- label resource
===
Section 4.1.2
   However, if the ERO is computed such that it also
   provides details of the component link selection(s) along the
   Path, the component link selection with IP address contained in
   the Path Error or Notify message SHOULD be avoided.
The use of "SHOULD" implies that there may be a good reason to continue to 
use the address. Please supply the text
"MAY continue to use it in order to ...."
===
Section 4.1.3
Doesn't give enough information to the head end to avoid the problem node in 
its reroute computations.
Perhaps you need to reorder your document to say that the IGP pieces happen 
first, and the shutdown node should wait to allow the IGP to converge before 
sending out PathErr and or Notify?
===
Section 4.2.1
Why not include also specifying Minimum LSP Bandwidth as greater than the 
available bandwidth and greater than the maximum LSP bandwidth?
This goes further than "discouraging" the use of the TE link, it makes it 
impossible to use even for zero-bandwidth LSPs.
I'm pretty sure this was discussed several times in the WG.
===
Section 4.2.1
   Neighbors of the node where graceful shutdown procedure is in
   progress SHOULD continue to advertise the actual unreserved
   bandwidth of the TE links from the neighbors to that node,
   without any routing adjacency change.
Doesn't this mean that the TE link is only shut down in one direction? So 
unidirectional LSPs would still try to use the link.
===
Section 5
I don't think you will get this past the Security ADs.
What happens if graceful shutdown is:
- spoofed
- hidden (i.e. the signaling or routing is blocked)
You have not mentioned the IGP security.
it might be a good idea to include a reference to Luyuan's draft.
===
Section 6
You need to give IANA far clearer instructions than this.
Please look at a recent RFC for an example.
I suggest RFC 4873 section 9.5
===
References
Personally, I like references to RFCs to use the RFC numbers as this is far 
quicker to look up. But you don't have to make this change.
===

----- Original Message ----- 
From: <[email-masked]>
To: <[email-masked]>
Cc: <[email-masked]>
Sent: Friday, June 08, 2007 8:50 PM
Subject: I-D ACTION:draft-ietf-ccamp-mpls-graceful-shutdown-03.txt

>A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Common Control and Measurement Plane 
> Working Group of the IETF.
>
> Title : Graceful Shutdown in GMPLS Traffic Engineering Networks
> Author(s) : Z. Ali, et al.
> Filename : draft-ietf-ccamp-mpls-graceful-shutdown-03.txt
> Pages : 9
> Date : 2007-6-8
>
> GMPLS-TE Graceful shutdown is a method for explicitly notifying
>   the nodes in a Traffic Engineering (TE) enabled network that the
>   TE capability on a link or on an entire Label Switching Router
>   (LSR) is going to be disabled. GMPLS-TE graceful shutdown
>   mechanisms are tailored towards addressing the planned outage in
>   the network.
>
>   This document provides requirements and protocol mechanisms so as
>   to reduce/eliminate traffic disruption in the event of a planned
>   shutdown of a network resource. These operations are equally
>   applicable for both MPLS and its GMPLS extensions.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ccamp-mpls-graceful-shutdown-03.txt

Delivery-date: Fri, 08 Jun 2007 19:52:54 +0000
To: [email-masked]
Cc: [email-masked]
From: [email-masked]
Subject: I-D ACTION:draft-ietf-ccamp-mpls-graceful-shutdown-03.txt 
Date: Fri, 08 Jun 2007 15:50:02 -0400

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.

	Title		: Graceful Shutdown in GMPLS Traffic Engineering Networks
	Author(s)	: Z. Ali, et al.
	Filename	: draft-ietf-ccamp-mpls-graceful-shutdown-03.txt
	Pages		: 9
	Date		: 2007-6-8
	
GMPLS-TE Graceful shutdown is a method for explicitly notifying 
   the nodes in a Traffic Engineering (TE) enabled network that the 
   TE capability on a link or on an entire Label Switching Router 
   (LSR) is going to be disabled. GMPLS-TE graceful shutdown 
   mechanisms are tailored towards addressing the planned outage in 
   the network.  
    
   This document provides requirements and protocol mechanisms so as 
   to reduce/eliminate traffic disruption in the event of a planned 
   shutdown of a network resource. These operations are equally 
   applicable for both MPLS and its GMPLS extensions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-mpls-graceful-shutdown-03.txt

To remove yourself from the I-D Announcement list, send a message to 
[email-masked] with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-ccamp-mpls-graceful-shutdown-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-ccamp-mpls-graceful-shutdown-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-ccamp-mpls-graceful-shutdown-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-mpls-graceful-shutdown-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email-masked]>

--OtherAccess--

--NextPart--

Delivery-date: Wed, 06 Jun 2007 19:53:06 +0000
To: [email-masked]
Cc: [email-masked]
From: [email-masked]
Subject: I-D ACTION:draft-ietf-ccamp-ethernet-traffic-parameters-02.txt 
Date: Wed, 06 Jun 2007 15:50:02 -0400

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.

	Title		: MEF Ethernet Traffic Parameters
	Author(s)	: D. Papadimitriou
	Filename	: draft-ietf-ccamp-ethernet-traffic-parameters-02.txt
	Pages		: 11
	Date		: 2007-6-6
	
This document described the Metro Ethernet Forum (MEF) - specific 
   Ethernet Traffic Parameters as described in MEF.10 when using 
   Generalized Multi-Protocol Label Switching (GMPLS) Resource 
   ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-ethernet-traffic-parameters-02.txt

To remove yourself from the I-D Announcement list, send a message to 
[email-masked] with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-ccamp-ethernet-traffic-parameters-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-ccamp-ethernet-traffic-parameters-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-ccamp-ethernet-traffic-parameters-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-ethernet-traffic-parameters-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email-masked]>

--OtherAccess--

--NextPart--

Delivery-date: Wed, 06 Jun 2007 19:52:58 +0000
To: [email-masked]
Cc: [email-masked]
From: [email-masked]
Subject: I-D ACTION:draft-ietf-ccamp-ospf-interas-te-extension-00.txt 
Date: Wed, 06 Jun 2007 15:50:02 -0400

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Common Control and Measurement Plane Working Group of the IETF.

	Title		: OSPF Traffic Engineering (OSPF-TE) Extensions in Support of Inter-AS Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering 
	Author(s)	: M. Chen, R. Zhang
	Filename	: draft-ietf-ccamp-ospf-interas-te-extension-00.txt
	Pages		: 12
	Date		: 2007-6-6
	
   This document describes extensions to the OSPF Traffic Engineering 
   (OSPF-TE) mechanisms to support Multiprotocol Label Switching (MPLS) 
   and Generalized MPLS (GMPLS) Traffic Engineering (TE) for multiple 
   Autonomous Systems (ASes). It defines OSPF-TE extensions for the 
   flooding of TE information about inter-AS links which can be used to 
   perform inter-AS TE path computation. 

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-ospf-interas-te-extension-00.txt

To remove yourself from the I-D Announcement list, send a message to 
[email-masked] with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-ccamp-ospf-interas-te-extension-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-ietf-ccamp-ospf-interas-te-extension-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="[email-masked]"

Content-Type: text/plain
Content-ID:	<[email-masked]>

ENCODING mime
FILE /internet-drafts/draft-ietf-ccamp-ospf-interas-te-extension-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-ospf-interas-te-extension-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email-masked]>

--OtherAccess--

--NextPart--

Delivery-date: Tue, 05 Jun 2007 13:08:45 +0000
Reply-To: "Adrian Farrel" <[email-masked]>
From: "Adrian Farrel" <[email-masked]>
To: "Thomas D. Nadeau" <[email-masked]>, "Weiqiang Sun" <[email-masked]>
Cc: "'Monique Morrow'" <[email-masked]>, "'BRUNGARD, DEBORAH A, ATTLABS'" <[email-masked]>, "'zhangguoying'" <[email-masked]>, "'Han Jianghui'" <[email-masked]>, "'blithe'" <[email-masked]>, "'xqwei'" <[email-masked]>, "'gjhhit'" <[email-masked]>, "'lufang'" <[email-masked]>, "'i-nishioka'" <[email-masked]>, "'julien.meuric'" <[email-masked]>, "'MORTON, ALFRED C, JR. \(AL\), ATTLABS'" <[email-masked]>, "'Weisheng HU'" <[email-masked]>, <[email-masked]>, <[email-masked]>, <[email-masked]>
Subject: Re: Updates on draft GMPLS LSP Dynamical Provisioning Performance Metrics
Date: Tue, 5 Jun 2007 14:03:34 +0100

>> 1) We modified the intro part to state the fact that the metrics  
>> defined are also applicable for TE-MIB inclusion, as may be  
>> interest of carriers to monitor the control plane performance in  
>> realtime, through NMS.
> 
> Just to be precise, do you mean RFC3812?  That is called the MPLS-TE- 
> STD-MIB in case you do.

Or RFC 4802 (GMPLS-TE-STD-MIB)

I suggest you add a reference so it is clear.

Thanks,
Adrian

Delivery-date: Tue, 05 Jun 2007 12:39:07 +0000
Cc: "'Monique Morrow'" <[email-masked]>, "'BRUNGARD, DEBORAH A, ATTLABS'" <[email-masked]>, "'zhangguoying'" <[email-masked]>, "'Han Jianghui'" <[email-masked]>, "'blithe'" <[email-masked]>, "'xqwei'" <[email-masked]>, "'gjhhit'" <[email-masked]>, "'lufang'" <[email-masked]>, "'i-nishioka'" <[email-masked]>, "'julien.meuric'" <[email-masked]>, "'MORTON, ALFRED C, JR. \(AL\), ATTLABS'" <[email-masked]>, "'Weisheng HU'" <[email-masked]>, <[email-masked]>, <[email-masked]>, <[email-masked]>
From: "Thomas D. Nadeau" <[email-masked]>
Subject: Re: Updates on draft GMPLS LSP Dynamical Provisioning Performance Metrics
Date: Tue, 5 Jun 2007 08:34:46 -0400
To: Weiqiang Sun <[email-masked]>

--Apple-Mail-1-876223945
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=ISO-2022-JP;
	delsp=yes;
	format=flowed

On Jun 4, 2007:9:43 PM, at 9:43 PM, Weiqiang Sun wrote:

> Hi all,
>
>
>
> We have updated the GMPLS LSP DPPM draft recently (see announcement  
> below). The draft has received positive responses after the last  
> CCAMP meeting. A discussion group was later setup by Guoying Zhang  
> (RITT, MII of China). Thanks for those who has participated in the  
> group and gave suggestions. In particular, we would like to thank  
> Monique Morrow (Cisco) for indicating a new draft in benchmarking  
> WG related to RSVP-TE performance authored by Cisco folks (http:// 
> www.ietf.org/internet-drafts/draft-vapiwala-bmwg-rsvpte-convergence- 
> motivation-00.txt). We regard this as interests in GMPLS  
> performance, whose progress will help motivating and progressing  
> the GMPLS LSP DPPM draft.
>
>
>
> The major improvements in this version include:
>
> 1) We modified the intro part to state the fact that the metrics  
> defined are also applicable for TE-MIB inclusion, as may be  
> interest of carriers to monitor the control plane performance in  
> realtime, through NMS.

	Just to be precise, do you mean RFC3812?  That is called the MPLS-TE- 
STD-MIB in case you do.

	--Tom

> 2) We corrected some error pointed out by X. Wei(Fiberhome) and J.  
> Gao(Huawei).
>
> 3) We changed the measurement unit from "seconds" to "milli- 
> seconds" as devices that have an averaged per-node processing delay  
> of less than 100ms is readily available.
>
>
>
> During preparation of this version, there has been controversy on  
> whether and how LSP rerouting metrics should be added to the draft.  
> Carriers have shown their interest in this metric. However, it  
> seems to us that the measurement of rerouting time will inevitably  
> change the simplicity of methodologies that have been introduced in  
> the draft so far, and the measurement may also be tightly coupled  
> with implementations. Finally Guoying and I would rather leave it  
> to the working group for possible suggestions and solutions.
>
>
>
> Please kindly give your comments and suggestions.
>
>
>
> Regards,
>
> Weiqiang Sun
>
> Shanghai Jiao Tong University
>
>
>
> To: i-d-announce at ietf.org
>
> Subject: I-D ACTION:draft-xie-ccamp-lsp-dppm-01.txt
>
> From: Internet-Drafts at ietf.org
>
> Date: Wed, 30 May 2007 18:50:01 -0400
>
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
>
> directories.
>
>
>
>
>
>          Title           : Label Switched Path (LSP) Dynamical  
> Provisioning Performance Metrics in Generalized MPLS Networks
>
>          Author(s)  : G. Xie, et al.
>
>          Filename : draft-xie-ccamp-lsp-dppm-01.txt
>
>          Pages                : 34
>
>          Date          : 2007-5-30
>
> …
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-xie-ccamp-lsp-dppm-01.txt
>
>
> -----Original Message-----
> From: Monique Morrow [mailto:[email-masked]]
> Sent: Thursday, May 31, 2007 2:54 AM
> To: [email-masked]
> Cc: 'BRUNGARD, DEBORAH A, ATTLABS'; 'zhangguoying'; 'Han Jianghui';  
> 'blithe'; 'xqwei'; 'gjhhit'; 'lufang'; 'i-nishioka';  
> 'julien.meuric'; 'MORTON, ALFRED C, JR. (AL), ATTLABS'; 'Weisheng  
> HU'; [email-masked]; [email-masked]
> Subject: Re: New discussion group formed on draft GMPLS LSP DPPM
>
>
>
> I shall do this -- stay tuned!
>
>
>
>
>
> On 5/25/07 9:38 PM, "Weiqiang Sun" <[email-masked]> wrote:
>
>
>
> > Hi Monique,
>
> >
>
> > It's nice that we have one other language in common :)
>
> >
>
> > Last month when Fred Baker visited SJTU, we were given five  
> minutes to
>
> > introduce the draft. Mr. Baker showed interest in this and we also
>
> > mentioned your involvement in this :).
>
> >
>
> > We are happy to see that cisco folks also started to work on this,
>
> > though in BMWG. It would be great if you could kindly introduce the
>
> > authors of the draft into this discussion group and possiblly  
> arrange a
>
> > discussion in the next ietf meeting for us, which I believe will
>
> > increase mutual understanding and help fasten the standardization
>
> > process of metrics and related methodologies.
>
> >
>
> > Thanks.
>
> >
>
> > --
>
> > Weiqiang
>
> > SJTU
>
> >
>
> >
>
> >
>
> > On 2007-05-25 08:06 -0700，Monique Morrow Wrote:
>
> >
>
> > Nimen hao!
>
> >>
>
> >> Your timing is perfect as I was about to ping you on the draft.
>
> >>
>
> >> You may want to look at new draft for possible harmonization  
> with the GMPLS
>
> >> LSP DDPM draft:
>
> >>
>
> >> http://www.ietf.org/internet-drafts/draft-vapiwala-bmwg-rsvpte- 
> convergence-m
>
> >> otivation-00.txt
>
> >>
>
> >>
>
> >> Kind regards,
>
> >>
>
> >> Monique
>
> >>
>
> >> On 5/25/07 1:35 AM, "Weiqiang Sun" <[email-masked]> wrote:
>
> >>
>
> >>> Hi all,
>
> >>>
>
> >>> We have just updated the draft GMPLS LSP DPPM according the  
> feedbacks we get
>
> >>> since its publication on IETF website. Many thanks to those who  
> have given
>
> >>> valuable suggestions and also to Adrian and Deborah for  
> allocating the slot
>
> >>> in the last meeting.
>
> >>>
>
> >>> The major improvements are:
>
> >>> 1) We modified the intro part to state the fact that the  
> metrics defined are
>
> >>> also applicable for TE-MIB inclusion, as may be interest of  
> carriers to
>
> >>> monitor the control plane performance in realtime, through NMS.
>
> >>> 2) We corrected some error pointed out by X. Wei(Fiberhome) and J.
>
> >>> Gao(Huawei).
>
> >>> 3) We changed the measurement unit from "seconds" to "milli- 
> seconds" as
>
> >>> devices that have an averaged per-node processing delay of less  
> than 100ms
>
> >>> is readily available.
>
> >>>
>
> >>> The updated draft is attached for your review, before we submit  
> it to IETF
>
> >>> for publication. Please give your comments.
>
> >>>
>
> >>> Thanks and regards.
>
> >>>
>
> >>> Weiqiang
>
> >>> SJTU
>
> >>> -----Original Message-----
>
> >>> From: Weiqiang Sun [mailto:[email-masked]]
>
> >>> Sent: Thursday, April 05, 2007 1:11 PM
>
> >>> To: 'BRUNGARD, DEBORAH A, ATTLABS'; 'Monique Morrow';  
> 'zhangguoying'; 'Han
>
> >>> Jianghui'; 'blithe'; 'xqwei'; 'gjhhit'; 'lufang'; 'i-nishioka';
>
> >>> 'julien.meuric'; 'MORTON, ALFRED C, JR. (AL), ATTLABS'
>
> >>> Cc: 'Weisheng HU'; [email-masked]'; [email-masked]'
>
> >>> Subject: RE: New discussion group formed on draft GMPLS LSP DPPM
>
> >>>
>
> >>> Hi all,
>
> >>>
>
> >>> It is really nice to have all of you together to discuss this  
> draft. The
>
> >>> draft team has had a difficult time when the draft was in its  
> primary stage
>
> >>> months ago. Now I believe your valuable suggestions and  
> comments will make
>
> >>> it a lot easier.
>
> >>>
>
> >>> As you may be aware, the draft deals only with control plane  
> performance, in
>
> >>> terms of circuit provisioning capability. One reason that  
> justifies this
>
> >>> work, IMHO, is that the control plane not only automates the  
> provisioning
>
> >>> process, but more importantly, it also significantly reduces  
> the setup
>
> >>> delay. This opens up opportunities for applications or services  
> that rely on
>
> >>> dynamically provisioned circuits. One such application has been  
> implemented
>
> >>> in a GMPLS testbed in Eastern China. However, up to date, there  
> is no
>
> >>> systematic way to evaluate the provisioning performance of the  
> control
>
> >>> plane, especially when the circuit hold-time is comparable with  
> or several
>
> >>> times the provisioning delay. A set of standardized metrics  
> that vividly
>
> >>> characterize the performance of control plane will definitely  
> increase the
>
> >>> confidence of applying GMPLS networks in the most natural way  
> and help to
>
> >>> design a proper timing model.
>
> >>> At the same time, as you may have seen in Guoying's talk during  
> the last WG
>
> >>> meeting, although variations are observed for all traffic loads
>
> >>> (dynamicity), higher load will lead to higher variation in  
> provisioning
>
> >>> delay. As control plane scalability and resilience issues are  
> getting into
>
> >>> our sight, a set of standardized metrics will hopefully  
> stimulate the
>
> >>> improvement of control plane implementations, e.g., using hardware
>
> >>> acceleration to reduce the processing time and variation. A  
> reliable and
>
> >>> stable control plane implementation will in turn encourage novel
>
> >>> applications being devised.
>
> >>> Hope Monique would be satisfied with this in regarding to  
> question 2. :)
>
> >>>
>
> >>> As to the metrics themselves, the existing ones are merely  
> about control
>
> >>> plane performance, with no regard to CP DP synchronization.  
> This is the most
>
> >>> lightweight solution we can think of so far and is reasonable  
> when the time
>
> >>> needed to establish a local XC is neglectable if compared with  
> signaling
>
> >>> processing delay. If this is not the case, still, we can use  
> the control
>
> >>> plane delay, plus a constant representing the XC operation  
> overhead.
>
> >>> By the term provisioning, we have intended to describe  
> application models
>
> >>> that circuits are established PRIOR to data transfer. This is  
> different from
>
> >>> the reroute model, where data transfer are ongoing and the  
> rerouting
>
> >>> procedure will eventually leads to packet loss (or service  
> interruption).
>
> >>> Thus a more reasonable metric that describes rerouting  
> performance, in my
>
> >>> opinion, would be packet loss, or service interruption time,  
> not delay (in
>
> >>> the control plane's point of view).It seems to me that  
> measurement of GMPLS
>
> >>> LSP rerouting is very similar to measurement of MPLS  
> protection, which is
>
> >>> now been defined in BMWG. Personally, I suggest we initiate  
> another draft to
>
> >>> deal of LSP rerouting, with reference to MPLS protection in  
> BMWG. Hopefully
>
> >>> we can get more suggestions from Al in this direction.
>
> >>>
>
> >>> For the first question raised by Monique, I have nothing to say  
> by now since
>
> >>> we are still working on the mentioned documents. Should you  
> have any
>
> >>> comments, please let us know.
>
> >>>
>
> >>> For the discussion group, we have a new member, Dr. Huandong  
> Zhao from China
>
> >>> Telecom Shanghai Research Institute.
>
> >>>
>
> >>> Cheers,
>
> >>> Weiqiang
>
> >>> SJTU
>
> >>> -----Original Message-----
>
> >>> From: BRUNGARD, DEBORAH A, ATTLABS [mailto:[email-masked]]
>
> >>> Sent: Wednesday, April 04, 2007 1:56 AM
>
> >>> To: Monique Morrow; zhangguoying; Weiqiang Sun; Han Jianghui;  
> blithe; xqwei;
>
> >>> gjhhit; lufang; i-nishioka; julien.meuric; MORTON, ALFRED C,  
> JR. (AL),
>
> >>> ATTLABS
>
> >>> Subject: RE: New discussion group formed on draft GMPLS LSP DPPM
>
> >>>
>
> >>> Hi all,
>
> >>>
>
> >>> I've added Al's address-
>
> >>> Deborah
>
> >>>
>
> >>> -----Original Message-----
>
> >>> From: Monique Morrow [mailto:[email-masked]]
>
> >>> Sent: Monday, April 02, 2007 5:16 AM
>
> >>> To: zhangguoying; Weiqiang Sun; 'Han Jianghui'; 'blithe';  
> 'xqwei'; 'gjhhit';
>
> >>> BRUNGARD, DEBORAH A, ATTLABS; lufang; i-nishioka; julien.meuric
>
> >>> Subject: Re: New discussion group formed on draft GMPLS LSP DPPM
>
> >>>
>
> >>> Greetings colleagues,
>
> >>>
>
> >>> This is an excellent proposal in terms of focused dialogue with  
> regard to
>
> >>> this topic.
>
> >>>
>
> >>> To progress:
>
> >>>
>
> >>>
>
> >>> - Important is note what work has been done in this direction   
> <Al Morton
>
> >>> has done quite a bit of work  -- in this direction for example  
> in the ITU
>
> >>> <y.1540, y.1541, y.1542> -- gap analysis as to what is missing;
>
> >>>
>
> >>> - Agreement as to the metrics themselves ;
>
> >>>
>
> >>> - Problem to be solved -- why is this an important ? <somewhat  
> implied in
>
> >>> the draft;
>
> >>>
>
> >>> - Method as to actual mechanism to measure would be last IMHO;
>
> >>>
>
> >>>
>
> >>> Looking forward -
>
> >>>
>
> >>> /m
>
> >>>
>
> >>>
>
> >>>
>
> >>>
>
> >>> On 2/4/07 12:08 am, "zhangguoying"  
> <[email-masked]> wrote:
>
> >>>
>
> >>>> Hi all,
>
> >>>>
>
> >>>> Fist of all, I suggest we form a new discussion group to  
> include experts
>
> >>> who
>
> >>>> are interested in the "GMPLS LSP dynamic provisioning  
> performance draft"
>
> >>>> during the IETF 68 meeting.
>
> >>>> Let me say welcome to:
>
> >>>> Julien Meuric, France Telecom,
>
> >>>> Deborah A. Brungard, AT&T,
>
> >>>> Monique Jeanne Morrow, Cisco,
>
> >>>> Luyuan Fang, Cisco
>
> >>>> Itaru Nishioka, NEC
>
> >>>>
>
> >>>> Deborah would also introduce her colleague Al Morton, chair of  
> the
>
> >>>> benchmarking methodology WG to join our discussion.
>
> >>>>
>
> >>>> The previous discussion group include :
>
> >>>> Guowu Xie,SJTU
>
> >>>> Weiqiang Sun,SJTU
>
> >>>> Guoying Zhang, CATR MII
>
> >>>> Jianghui Han, IXIA
>
> >>>> Xueqing Wei, Fiberhome
>
> >>>> Jianhua Gao, Huawei
>
> >>>>
>
> >>>>
>
> >>>> Here are some important suggestions I received during the  
> meeting:
>
> >>>> 1. Hear more voices and comments from the carriers. Currently  
> the draft
>
> >>> could
>
> >>>> be discussed in ccamp group, but may be transfered to the  
> management AD
>
> >>>> later.---- Adrian
>
> >>>> 2. Refer to the work of benchmarking WG. ---- Deborah
>
> >>>> 3. Include the performance metrics of LSP rerouting. These  
> performance
>
> >>> metrics
>
> >>>> would be useful if the GMPLS MIB support monitoring them in  
> deployed
>
> >>>> network.---- Julien
>
> >>>> 4. Define the method on how to measure the performance  
> metrics, and refer
>
> >>> to
>
> >>>> the work of benchmarking WG.  ----Itaru Nishioka
>
> >>>>
>
> >>>>
>
> >>>> Next we should discuss the plan for 01 version. I suggest we  
> fist refer to
>
> >>> the
>
> >>>> benchmarking methodology WG work, and consider the possibility of
>
> >>> including
>
> >>>> the LSP rerouting performance in the 01 version.
>
> >>>>
>
> >>>>
>
> >>>>
>
> >>>> 　　　　　　　　zhangguoying
>
> >>>>                Institute of Telecommunication Standards
>
> >>>>                China Academy of Telecom Research ,MII
>
> >>>> 　　　　　　　　[email-masked]
>
> >>>> 　　　　　　　　　　2007-04-02
>
>

--Apple-Mail-1-876223945
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=UTF-8

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; "><BR><DIV><DIV>On Jun 4, =
2007:9:43 PM, at 9:43 PM, Weiqiang Sun wrote:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><SPAN =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 16px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PlaceName"><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PlaceType"><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"City"><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"country-region"><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"State"><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"place"><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"chsdate" downloadurl=3D""><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"><DIV class=3D"Section1" =
style=3D"layout-grid:15.6pt"><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">Hi all,</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=
=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US"><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
10px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 10px; ">=C2=A0</SPAN></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">We have updated the GMPLS LSP =
DPPM draft recently (see announcement below). The draft has received =
positive responses after the last CCAMP meeting. A discussion group was =
later setup by Guoying Zhang (RITT, MII of China). Thanks for those who =
has participated in the group and gave suggestions. In particular, we =
would like to thank Monique Morrow (Cisco) for indicating a new draft in =
benchmarking WG related to RSVP-TE performance authored by Cisco folks =
(<A =
href=3D"http://www.ietf.org/internet-drafts/draft-vapiwala-bmwg-rsvpte-con=
vergence-motivation-00.txt">http://www.ietf.org/internet-drafts/draft-vapi=
wala-bmwg-rsvpte-convergence-motivation-00.txt</A>). We regard this as =
interests in GMPLS performance, whose progress will help motivating and =
progressing the GMPLS LSP DPPM draft.</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US"><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
10px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 10px; ">=C2=A0</SPAN></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">The major improvements in this =
version include:</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">1) We modified the intro part to state the =
fact that the metrics defined are also applicable for TE-MIB inclusion, =
as may be interest of carriers to monitor the control plane performance =
in realtime, through =
NMS.</SPAN></SPAN></FONT></P></DIV></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:S=
MARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTA=
GTYPE></O:SMARTTAGTYPE></SPAN></BLOCKQUOTE><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Just to be precise, do you mean =
RFC3812?=C2=A0 That is called the MPLS-TE-STD-MIB in case you =
do.</DIV><DIV><BR class=3D"khtml-block-placeholder"></DIV><DIV><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>--Tom</DIV><DIV><BR><BLOCKQUOTE type=3D"cite"><SPAN =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 16px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PlaceName"><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PlaceType"><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"City"><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"country-region"><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"State"><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"place"><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"chsdate" downloadurl=3D""><O:SMARTTAGTYPE =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"><DIV class=3D"Section1" =
style=3D"layout-grid:15.6pt"><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">2) We corrected some error pointed out by X. =
Wei(Fiberhome) and J. Gao(Huawei).</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">3) We changed the measurement =
unit from "seconds" to "milli-seconds" as devices that have an averaged =
per-node processing delay of less than 100ms is readily =
available.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US"><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 10px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">=C2=A0</SPAN></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">During preparation of this =
version, there has been controversy on whether and how LSP rerouting =
metrics should be added to the draft. Carriers have shown their interest =
in this metric. However, it seems to us that the measurement of =
rerouting time will inevitably change the simplicity of methodologies =
that have been introduced in the draft so far, and the measurement may =
also be tightly coupled with implementations. Finally Guoying and I =
would rather leave it to the working group for possible suggestions and =
solutions.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US"><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 10px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">=C2=A0</SPAN></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">Please kindly give your comments =
and suggestions.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US"><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 10px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">=C2=A0</SPAN></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">Regards,</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">Weiqiang Sun</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><ST1:PLACE w:st=3D"on"><ST1:PLACENAME =
w:st=3D"on"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size:9.0pt; font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; =
">Shanghai</SPAN></SPAN></FONT></ST1:PLACENAME><SPAN lang=3D"EN-US"><SPAN =
class=3D"Apple-style-span" style=3D"font-family: SimSun; font-size: =
12px; "> </SPAN><ST1:PLACENAME w:st=3D"on"><SPAN =
class=3D"Apple-style-span" style=3D"font-family: SimSun; font-size: =
12px; ">Jiao</SPAN></ST1:PLACENAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: SimSun; font-size: 12px; "> </SPAN><ST1:PLACENAME =
w:st=3D"on"><SPAN class=3D"Apple-style-span" style=3D"font-family: =
SimSun; font-size: 12px; ">Tong</SPAN></ST1:PLACENAME><SPAN =
class=3D"Apple-style-span" style=3D"font-family: SimSun; font-size: =
12px; "> </SPAN><ST1:PLACETYPE w:st=3D"on"><SPAN =
class=3D"Apple-style-span" style=3D"font-family: SimSun; font-size: =
12px; ">University</SPAN></ST1:PLACETYPE></SPAN></ST1:PLACE><SPAN =
lang=3D"EN-US"><O:P style=3D"font-family: SimSun; font-size: 12px; =
"></O:P></SPAN></P><DIV =
style=3D"mso-element:para-border-div;border:none;border-bottom:solid =
windowtext 1.0pt; padding:0cm 0cm 1.0pt 0cm"><P class=3D"MsoPlainText" =
style=3D"border:none;padding:0cm; font-family: SimSun; font-size: 12px; =
"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US"><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 10px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">=C2=A0</SPAN></O:P></SPAN></FONT></P></DIV><P =
class=3D"MsoPlainText"><FONT size=3D"1" color=3D"blue" =
face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Arial;color:blue; color: rgb(0, 0, =
255); font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 255); font-family: Arial; font-size: 12px; ">To: i-d-announce =
at ietf.org</SPAN><O:P style=3D"color: rgb(0, 0, 255); font-family: =
Arial; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" color=3D"blue" =
face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Arial;color:blue; color: rgb(0, 0, =
255); font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 255); font-family: Arial; font-size: 12px; ">Subject: I-D =
ACTION:draft-xie-ccamp-lsp-dppm-01.txt</SPAN><O:P style=3D"color: rgb(0, =
0, 255); font-family: Arial; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
color=3D"blue" face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Arial;color:blue; color: rgb(0, 0, =
255); font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 255); font-family: Arial; font-size: 12px; ">From: =
Internet-Drafts at ietf.org</SPAN><O:P style=3D"color: rgb(0, 0, 255); =
font-family: Arial; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" color=3D"blue" =
face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Arial;color:blue; color: rgb(0, 0, =
255); font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 255); font-family: Arial; font-size: 12px; ">Date: Wed, 30 May =
2007 18:50:01 -0400</SPAN><O:P style=3D"color: rgb(0, 0, 255); =
font-family: Arial; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT color=3D"blue" face=3D"Arial"><SPAN =
lang=3D"EN-US" style=3D"font-family:Arial;color:blue; color: rgb(0, 0, =
255); font-size: 12px; "><O:P style=3D"color: rgb(0, 0, 255); =
font-family: Arial; font-size: 12px; "><SPAN class=3D"Apple-style-span" =
style=3D"color: rgb(0, 0, 255); font-family: Arial; font-size: 12px; =
">=C2=A0</SPAN></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT =
size=3D"1" color=3D"blue" face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Arial;color:blue; color: rgb(0, 0, =
255); font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 255); font-family: Arial; font-size: 12px; ">A New =
Internet-Draft is available from the on-line Internet-Drafts</SPAN><O:P =
style=3D"color: rgb(0, 0, 255); font-family: Arial; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
color=3D"blue" face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Arial;color:blue; color: rgb(0, 0, =
255); font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 255); font-family: Arial; font-size: 12px; =
">directories.</SPAN><O:P style=3D"color: rgb(0, 0, 255); font-family: =
Arial; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT color=3D"blue" face=3D"Arial"><SPAN =
lang=3D"EN-US" style=3D"font-family:Arial;color:blue; color: rgb(0, 0, =
255); font-size: 12px; "><O:P style=3D"color: rgb(0, 0, 255); =
font-family: Arial; font-size: 12px; "><SPAN class=3D"Apple-style-span" =
style=3D"color: rgb(0, 0, 255); font-family: Arial; font-size: 12px; =
">=C2=A0</SPAN></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT =
color=3D"blue" face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-family:Arial;color:blue; color: rgb(0, 0, 255); font-size: =
12px; "><O:P style=3D"color: rgb(0, 0, 255); font-family: Arial; =
font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 255); font-family: Arial; font-size: 12px; =
">=C2=A0</SPAN></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT =
size=3D"1" color=3D"blue" face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Arial;color:blue; color: rgb(0, 0, =
255); font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 255); font-family: Arial; font-size: 12px; ">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 Title=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 : Label Switched Path (LSP) Dynamical Provisioning =
Performance Metrics in Generalized MPLS Networks</SPAN><O:P =
style=3D"color: rgb(0, 0, 255); font-family: Arial; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
color=3D"blue" face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Arial;color:blue; color: rgb(0, 0, =
255); font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 255); font-family: Arial; font-size: 12px; ">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 Author(s)=C2=A0 : G. Xie, et al.</SPAN><O:P =
style=3D"color: rgb(0, 0, 255); font-family: Arial; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
color=3D"blue" face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Arial;color:blue; color: rgb(0, 0, =
255); font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 255); font-family: Arial; font-size: 12px; ">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 Filename : =
draft-xie-ccamp-lsp-dppm-01.txt</SPAN><O:P style=3D"color: rgb(0, 0, =
255); font-family: Arial; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" color=3D"blue" =
face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Arial;color:blue; color: rgb(0, 0, =
255); font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 255); font-family: Arial; font-size: 12px; ">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 Pages=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 34</SPAN><O:P =
style=3D"color: rgb(0, 0, 255); font-family: Arial; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
color=3D"blue" face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Arial;color:blue; color: rgb(0, 0, =
255); font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"color: =
rgb(0, 0, 255); font-family: Arial; font-size: 12px; ">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 Date=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 : </SPAN><ST1:CHSDATE year=3D"2007" month=3D"5" day=3D"30" =
islunardate=3D"False" isrocdate=3D"False" w:st=3D"on"><SPAN =
class=3D"Apple-style-span" style=3D"color: rgb(0, 0, 255); font-family: =
Arial; font-size: 12px; ">2007-5-30</SPAN></ST1:CHSDATE><O:P =
style=3D"color: rgb(0, 0, 255); font-family: Arial; font-size: 12px; =
"></O:P></SPAN></FONT></P><PRE style=3D"font-family: SimSun; =
white-space: pre; "><FONT size=3D"1" face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;
font-family:Arial; font-size: 12px; white-space: pre; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: 12px; =
white-space: pre; ">=E2=80=A6</SPAN><O:P style=3D"font-family: Arial; =
font-size: 12px; white-space: pre; "></O:P></SPAN></FONT></PRE><PRE =
style=3D"font-family: SimSun; white-space: pre; "><FONT size=3D"1" =
face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Arial; font-size: 12px; =
white-space: pre; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 Arial; font-size: 12px; white-space: pre; ">A URL for this =
Internet-Draft is:</SPAN><O:P style=3D"font-family: Arial; font-size: =
12px; white-space: pre; "></O:P></SPAN></FONT></PRE><DIV =
style=3D"mso-element:para-border-div;border:none;border-bottom:solid =
windowtext 1.0pt; padding:0cm 0cm 1.0pt 0cm"><PRE =
style=3D"border:none;padding:0cm; font-family: SimSun; white-space: pre; =
"><FONT size=3D"1" face=3D"Arial"><SPAN lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Arial; font-size: 12px; =
white-space: pre; "><A =
href=3D"http://www.ietf.org/internet-drafts/draft-xie-ccamp-lsp-dppm-01.tx=
t"><SPAN class=3D"Apple-style-span" style=3D"color: rgb(0, 0, 255); =
font-family: Arial; font-size: 12px; -khtml-text-decorations-in-effect: =
underline; white-space: pre; =
">http://www.ietf.org/internet-drafts/draft-xie-ccamp-lsp-dppm-01.txt</SPA=
N></A><O:P style=3D"font-family: Arial; font-size: 12px; white-space: =
pre; "></O:P></SPAN></FONT></PRE></DIV><P class=3D"MsoPlainText"><FONT =
size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US"><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 10px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">=C2=A0</SPAN></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">-----Original =
Message-----</SPAN><BR style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; ">From: Monique Morrow [<A =
href=3D"mailto:[email-masked]">mailto:[email-masked]</A>] =
</SPAN><BR style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93=
; font-size: 12px; ">Sent: Thursday, May 31, 2007 2:54 AM</SPAN><BR =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">To: <A =
href=3D"mailto:[email-masked]">[email-masked]</A></SPAN><BR =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">Cc: 'BRUNGARD, DEBORAH A, ATTLABS'; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'zhangguoying'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">'Han =
Jianghui'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'blithe'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'xqwei'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'gjhhit'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'lufang'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'i-nishioka'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'julien.meuric'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">'MORTON, =
ALFRED C, JR.</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "> (AL), =
ATTLABS'; 'Weisheng HU'; <A =
href=3D"mailto:[email-masked]">[email-masked]</A>; <A =
href=3D"mailto:[email-masked]">[email-masked]</A></SPAN><BR =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">Subject: Re: New discussion group formed on draft =
GMPLS LSP DPPM</SPAN></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT =
size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US"><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 10px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">=C2=A0</SPAN></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">I shall do this -- stay =
tuned!</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US"><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 10px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">=C2=A0</SPAN></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US"><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
10px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 10px; ">=C2=A0</SPAN></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">On 5/25/07 9:38 PM, "Weiqiang =
Sun" &lt;<A href=3D"mailto:[email-masked]">[email-masked]</A>&gt; =
wrote:</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US"><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 10px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">=C2=A0</SPAN></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt; Hi Monique,</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93=
; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt; It's nice that we have one =
other language in common :)</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=
=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt; Last month when Fred Baker visited SJTU, we were =
given five minutes to</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt; introduce the draft. Mr. =
Baker showed interest in this and we also</SPAN><O:P style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt; mentioned your involvement =
in this :).</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt; We are happy to see that =
cisco folks also started to work on this,</SPAN><O:P style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt; though in BMWG. It would be =
great if you could kindly introduce the</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt; authors of the draft into =
this discussion group and possiblly arrange a</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt; discussion in the next ietf meeting for us, =
which I believe will</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt; increase mutual understanding and help =
fasten the standardization</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=
=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt; process of metrics and =
related methodologies.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93=
; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt; Thanks.</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt; --</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=
=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt; Weiqiang</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt; SJTU</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93=
; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt; On 2007-05-25 08:06 -0700</SPAN></SPAN><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">=EF=BC=8C</SPAN><SPAN lang=3D"EN-US"><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">Monique Morrow Wrote:</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 10px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt; Nimen hao!</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt; Your timing is perfect as I was about to =
ping you on the draft.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93=
; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt; You may want to look at new draft for =
possible harmonization with the GMPLS</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt; LSP DDPM =
draft:</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=
=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt; <A =
href=3D"http://www.ietf.org/internet-drafts/draft-vapiwala-bmwg-rsvpte-con=
vergence-m">http://www.ietf.org/internet-drafts/draft-vapiwala-bmwg-rsvpte=
-convergence-m</A></SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt; otivation-00.txt</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=
=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt; Kind regards,</SPAN><O:P style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt; Monique</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt; On 5/25/07 1:35 AM, "Weiqiang Sun" &lt;<A =
href=3D"mailto:[email-masked]">[email-masked]</A>&gt; =
wrote:</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=
=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; Hi all,</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; We have just =
updated the draft GMPLS LSP DPPM according the feedbacks we =
get</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; since its publication on IETF website. =
Many thanks to those who have given</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; valuable =
suggestions and also to Adrian and Deborah for allocating the =
slot</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; in the last meeting.</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; The major =
improvements are:</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt; 1) We modified the intro part to =
state the fact that the metrics defined are</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; also applicable for TE-MIB inclusion, as =
may be interest of carriers to</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; monitor the control =
plane performance in realtime, through NMS.</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; 2) We corrected some error pointed out =
by X. Wei(Fiberhome) and J.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=
=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; =
Gao(Huawei).</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt; 3) We changed the measurement =
unit from "seconds" to "milli-seconds" as</SPAN><O:P style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; devices that have =
an averaged per-node processing delay of less than 100ms</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; is readily available.</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; The updated draft =
is attached for your review, before we submit it to IETF</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; for publication. Please give your =
comments.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; Thanks and =
regards.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; Weiqiang</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; SJTU</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; -----Original =
Message-----</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt; From: Weiqiang Sun [<A =
href=3D"mailto:[email-masked]">mailto:[email-masked]</A>]</SPAN><O:P=
 style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; Sent: Thursday, April 05, 2007 1:11 =
PM</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; To: 'BRUNGARD, DEBORAH A, ATTLABS'; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">'Monique =
Morrow'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'zhangguoying'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
'Han</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; Jianghui'; </SPAN><ST1:PERSONNAME =
w:st=3D"on"><SPAN class=3D"Apple-style-span" style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; =
">'blithe'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'xqwei'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'gjhhit'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'lufang'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'i-nishioka'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">;</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; </SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">'julien.meuric'</SPAN></ST1:PERSONNAME><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">; </SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">'MORTON, ALFRED C, JR.</SPAN></ST1:PERSONNAME><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "> (</SPAN><ST1:STATE w:st=3D"on"><ST1:PLACE =
w:st=3D"on"><SPAN class=3D"Apple-style-span" style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; =
">AL</SPAN></ST1:PLACE></ST1:STATE><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">), =
ATTLABS'</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; Cc: 'Weisheng HU'; '<A =
href=3D"mailto:[email-masked]">[email-masked]</A>'; '<A =
href=3D"mailto:[email-masked]">[email-masked]</A>'</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; Subject: RE: New discussion group formed =
on draft GMPLS LSP DPPM</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93=
; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; Hi all,</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; It is really nice to have all of you =
together to discuss this draft. The</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; draft team has had =
a difficult time when the draft was in its primary stage</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; months ago. Now I believe your valuable =
suggestions and comments will make</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; it a lot =
easier.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; As you may be =
aware, the draft deals only with control plane performance, =
in</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; terms of circuit provisioning =
capability. One reason that justifies this</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; work, IMHO, is that the control plane =
not only automates the provisioning</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; process, but more =
importantly, it also significantly reduces the setup</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; delay. This opens up opportunities for =
applications or services that rely on</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; dynamically =
provisioned circuits. One such application has been =
implemented</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt; in a GMPLS testbed in =
</SPAN><ST1:PLACE w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">Eastern =
China</SPAN></ST1:PLACE><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">. However, =
up to date, there is no</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93=
; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; systematic way to =
evaluate the provisioning performance of the control</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; plane, especially when the circuit =
hold-time is comparable with or several</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; times the =
provisioning delay. A set of standardized metrics that =
vividly</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; characterize the performance of control =
plane will definitely increase the</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; confidence of =
applying GMPLS networks in the most natural way and help to</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; design a proper timing model.</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; At the same time, as you may have seen =
in Guoying's talk during the last WG</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; meeting, although =
variations are observed for all traffic loads</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; (dynamicity), higher load will lead to =
higher variation in provisioning</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; delay. As control =
plane scalability and resilience issues are getting into</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; our sight, a set of standardized metrics =
will hopefully stimulate the</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; improvement of =
control plane implementations, e.g., using hardware</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; acceleration to reduce the processing =
time and variation. A reliable and</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; stable control =
plane implementation will in turn encourage novel</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; applications being devised.</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; Hope Monique would be satisfied with =
this in regarding to question 2. :)</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; As to the metrics themselves, the =
existing ones are merely about control</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; plane performance, =
with no regard to CP DP synchronization. This is the most</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; lightweight solution we can think of so =
far and is reasonable when the time</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; needed to establish =
a local XC is neglectable if compared with signaling</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; processing delay. If this is not the =
case, still, we can use the control</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; plane delay, plus a =
constant representing the XC operation overhead.</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; By the term provisioning, we have =
intended to describe application models</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; that circuits are =
established PRIOR to data transfer. This is different from</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; the reroute model, where data transfer =
are ongoing and the rerouting</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; procedure will =
eventually leads to packet loss (or service interruption).</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; Thus a more reasonable metric that =
describes rerouting performance, in my</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; opinion, would be =
packet loss, or service interruption time, not delay (in</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; the control plane's point of view).It =
seems to me that measurement of GMPLS</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; LSP rerouting is =
very similar to measurement of MPLS protection, which is</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; now been defined in BMWG. Personally, I =
suggest we initiate another draft to</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; deal of LSP =
rerouting, with reference to MPLS protection in BMWG. =
Hopefully</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt; we can get more suggestions from =
Al in this direction.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; For the first question raised by =
Monique, I have nothing to say by now since</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; we are still working on the mentioned =
documents. Should you have any</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; comments, please =
let us know.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; For the discussion =
group, we have a new member, Dr. Huandong Zhao from =
</SPAN><ST1:COUNTRY-REGION w:st=3D"on"><ST1:PLACE w:st=3D"on"><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">China</SPAN></ST1:PLACE></ST1:COUNTRY-REGION><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; Telecom Shanghai Research =
Institute.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; Cheers,</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; Weiqiang</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; SJTU</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; -----Original Message-----</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; From: BRUNGARD, DEBORAH A, ATTLABS [<A =
href=3D"mailto:[email-masked]">mailto:[email-masked]</A>]</SPAN><O:P=
 style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; Sent: Wednesday, April 04, 2007 1:56 =
AM</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; To: Monique Morrow; zhangguoying; =
Weiqiang Sun; Han Jianghui; blithe; xqwei;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; gjhhit; lufang; i-nishioka; =
julien.meuric; MORTON, ALFRED C, JR. (</SPAN><ST1:STATE =
w:st=3D"on"><ST1:PLACE w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">AL</SPAN></ST1:PLACE></ST1:STATE><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">),</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; ATTLABS</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; Subject: RE: New =
discussion group formed on draft GMPLS LSP DPPM</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; Hi all,</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; I've added Al's =
address-</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; Deborah</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; -----Original Message-----</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; From: Monique Morrow [<A =
href=3D"mailto:[email-masked]">mailto:[email-masked]</A>]</SPAN><O:P=
 style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; Sent: Monday, April 02, 2007 5:16 =
AM</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; To: zhangguoying; Weiqiang Sun; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">'Han =
Jianghui'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'blithe'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'xqwei'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">; =
</SPAN><ST1:PERSONNAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">'gjhhit'</SPAN></ST1:PERSONNAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">;</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; BRUNGARD, DEBORAH A, ATTLABS; lufang; =
i-nishioka; julien.meuric</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=
=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; Subject: Re: New =
discussion group formed on draft GMPLS LSP DPPM</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; Greetings =
colleagues,</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; This is an =
excellent proposal in terms of focused dialogue with regard =
to</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; this topic.</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; To =
progress:</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; - Important is note what work has been =
done in this direction=C2=A0 &lt;Al Morton</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; has done quite a bit of work=C2=A0 -- in =
this direction for example in the ITU</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; &lt;y.1540, y.1541, =
y.1542&gt; -- gap analysis as to what is missing;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; - Agreement as to =
the metrics themselves ;</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93=
; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; - Problem to be solved -- why is this an =
important ? &lt;somewhat implied in</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; the =
draft;</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; - Method as to =
actual mechanism to measure would be last IMHO;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; Looking forward -</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt; /m</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; On 2/4/07 12:08 am, "zhangguoying" =
&lt;<A =
href=3D"mailto:[email-masked]">[email-masked]=
n</A>&gt; wrote:</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; Hi =
all,</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; Fist of all, I =
suggest we form a new discussion group to include experts</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; who</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; are interested =
in the "GMPLS LSP dynamic provisioning performance draft"</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; during the IETF 68 =
meeting.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; Let me say welcome to:</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; </SPAN><ST1:PLACE =
w:st=3D"on"><ST1:CITY w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">Julien =
Meuric</SPAN></ST1:CITY><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; ">, =
</SPAN><ST1:COUNTRY-REGION w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">France</SPAN></ST1:COUNTRY-REGION></ST1:PLACE><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "> Telecom,</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; Deborah A. =
Brungard, AT&amp;T,</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; Monique Jeanne Morrow, =
Cisco,</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; Luyuan Fang, Cisco</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; Itaru Nishioka, NEC</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; Deborah would =
also introduce her colleague Al Morton, chair of the</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; benchmarking methodology WG to join =
our discussion.</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; The previous discussion group =
include :</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT=
 size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" =
style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: =
12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; Guowu Xie,SJTU</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; Weiqiang Sun,SJTU</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; Guoying Zhang, CATR MII</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; Jianghui Han, IXIA</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; Xueqing Wei, Fiberhome</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; Jianhua Gao, Huawei</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; Here are some important suggestions =
I received during the meeting:</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; 1. Hear more =
voices and comments from the carriers. Currently the draft</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; could</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; be discussed in =
ccamp group, but may be transfered to the management AD</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; later.---- </SPAN><ST1:CITY =
w:st=3D"on"><ST1:PLACE w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">Adrian</SPAN></ST1:PLACE></ST1:CITY><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; 2. Refer to the =
work of benchmarking WG. ---- Deborah</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; 3. Include the =
performance metrics of LSP rerouting. These performance</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; metrics</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; would be useful =
if the GMPLS MIB support monitoring them in deployed</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; network.---- Julien</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; 4. Define the method on how to =
measure the performance metrics, and refer</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; to</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; the work of =
benchmarking WG.=C2=A0 ----Itaru Nishioka</SPAN><O:P style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; Next we should =
discuss the plan for 01 version. I suggest we fist refer to</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; the</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; benchmarking =
methodology WG work, and consider the possibility of</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt; including</SPAN><O:P style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt; the LSP =
rerouting performance in the 01 version.</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt;</SPAN><O:P style=3D"font-family: =
=E5=AE=8B=E4=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; ">&gt;&gt;&gt;&gt;</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; </SPAN></SPAN><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">=E3=80=80=E3=80=80=E3=80=80=E3=80=80=E3=80=80=E3=80=80=E3=
=80=80=E3=80=80</SPAN><SPAN lang=3D"EN-US"><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">zhangguoying</SPAN><O:P style=3D"font-family: =E5=AE=8B=
=E4=BD=93; font-size: 10px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; =
">&gt;&gt;&gt;&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </SPAN><ST1:PLACE =
w:st=3D"on"><ST1:PLACETYPE w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">Institute</SPAN></ST1:PLACETYPE><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "> of =
</SPAN><ST1:PLACENAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">Telecommunication</SPAN></ST1:PLACENAME></ST1:PLACE><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "> Standards</SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=
=BD=93; font-size: 12px; "></O:P></SPAN></FONT></P><P =
class=3D"MsoPlainText"><FONT size=3D"1" face=3D"=E5=AE=8B=E4=BD=93"><SPAN =
lang=3D"EN-US" style=3D"font-size: 9.0pt; font-family: =E5=AE=8B=E4=BD=93;=
 font-size: 12px; "><SPAN class=3D"Apple-style-span" style=3D"font-family:=
 =E5=AE=8B=E4=BD=93; font-size: 12px; =
">&gt;&gt;&gt;&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </SPAN><ST1:PLACE =
w:st=3D"on"><ST1:PLACENAME w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">China</SPAN></ST1:PLACENAME><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "> =
</SPAN><ST1:PLACETYPE w:st=3D"on"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
">Academy</SPAN></ST1:PLACETYPE></ST1:PLACE><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; "> of Telecom Research ,MII</SPAN><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; =
"></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1" =
face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; </SPAN></SPAN><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">=E3=80=80=E3=80=80=E3=80=80=E3=80=80=E3=80=80=E3=80=80=E3=
=80=80=E3=80=80</SPAN><SPAN lang=3D"EN-US"><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; "><A =
href=3D"mailto:[email-masked]">[email-masked]=
n</A></SPAN><O:P style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: =
10px; "></O:P></SPAN></FONT></P><P class=3D"MsoPlainText"><FONT size=3D"1"=
 face=3D"=E5=AE=8B=E4=BD=93"><SPAN lang=3D"EN-US" style=3D"font-size: =
9.0pt; font-family: =E5=AE=8B=E4=BD=93; font-size: 12px; "><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 12px; ">&gt;&gt;&gt;&gt; </SPAN></SPAN><SPAN =
class=3D"Apple-style-span" style=3D"font-family: =E5=AE=8B=E4=BD=93; =
font-size: 10px; ">=E3=80=80=E3=80=80=E3=80=80=E3=80=80=E3=80=80=E3=80=80=E3=
=80=80=E3=80=80=E3=80=80=E3=80=80</SPAN><ST1:CHSDATE isrocdate=3D"False" =
islunardate=3D"False" day=3D"2" month=3D"4" year=3D"2007" =
w:st=3D"on"><SPAN lang=3D"EN-US"><SPAN class=3D"Apple-style-span" =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 10px; =
">2007-04-02</SPAN></SPAN></ST1:CHSDATE><SPAN lang=3D"EN-US"><O:P =
style=3D"font-family: =E5=AE=8B=E4=BD=93; font-size: 10px; =
"></O:P></SPAN></FONT></P></DIV></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMAR=
TTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTY=
PE></O:SMARTTAGTYPE><BR =
class=3D"Apple-interchange-newline"></SPAN></BLOCKQUOTE></DIV><BR></BODY><=
/HTML>=

--Apple-Mail-1-876223945--

Delivery-date: Tue, 05 Jun 2007 01:47:06 +0000
From: "Weiqiang Sun" <[email-masked]>
To: "'Monique Morrow'" <[email-masked]>, "'BRUNGARD, DEBORAH A, ATTLABS'" <[email-masked]>, "'zhangguoying'" <[email-masked]>, "'Han Jianghui'" <[email-masked]>, "'blithe'" <[email-masked]>, "'xqwei'" <[email-masked]>, "'gjhhit'" <[email-masked]>, "'lufang'" <[email-masked]>, "'i-nishioka'" <[email-masked]>, "'julien.meuric'" <[email-masked]>, "'MORTON, ALFRED C, JR. \(AL\), ATTLABS'" <[email-masked]>, "'Weisheng HU'" <[email-masked]>, <[email-masked]>, <[email-masked]>
Cc: <[email-masked]>
Subject: Updates on draft GMPLS LSP Dynamical Provisioning Performance Metrics
Date: Tue, 5 Jun 2007 09:43:55 +0800

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01C7A756.08A8BA50
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit

Hi all,

We have updated the GMPLS LSP DPPM draft recently (see announcement below).
The draft has received positive responses after the last CCAMP meeting. A
discussion group was later setup by Guoying Zhang (RITT, MII of China).
Thanks for those who has participated in the group and gave suggestions. In
particular, we would like to thank Monique Morrow (Cisco) for indicating a
new draft in benchmarking WG related to RSVP-TE performance authored by
Cisco folks
(http://www.ietf.org/internet-drafts/draft-vapiwala-bmwg-rsvpte-convergence-
motivation-00.txt). We regard this as interests in GMPLS performance, whose
progress will help motivating and progressing the GMPLS LSP DPPM draft.

The major improvements in this version include:

1) We modified the intro part to state the fact that the metrics defined are
also applicable for TE-MIB inclusion, as may be interest of carriers to
monitor the control plane performance in realtime, through NMS.

2) We corrected some error pointed out by X. Wei(Fiberhome) and J.
Gao(Huawei).

3) We changed the measurement unit from "seconds" to "milli-seconds" as
devices that have an averaged per-node processing delay of less than 100ms
is readily available.

During preparation of this version, there has been controversy on whether
and how LSP rerouting metrics should be added to the draft. Carriers have
shown their interest in this metric. However, it seems to us that the
measurement of rerouting time will inevitably change the simplicity of
methodologies that have been introduced in the draft so far, and the
measurement may also be tightly coupled with implementations. Finally
Guoying and I would rather leave it to the working group for possible
suggestions and solutions. 

Please kindly give your comments and suggestions.

Regards,

Weiqiang Sun

Shanghai Jiao Tong University

To: i-d-announce at ietf.org 

Subject: I-D ACTION:draft-xie-ccamp-lsp-dppm-01.txt 

From: Internet-Drafts at ietf.org 

Date: Wed, 30 May 2007 18:50:01 -0400 

A New Internet-Draft is available from the on-line Internet-Drafts 

directories.

         Title           : Label Switched Path (LSP) Dynamical Provisioning
Performance Metrics in Generalized MPLS Networks

         Author(s)  : G. Xie, et al.

         Filename : draft-xie-ccamp-lsp-dppm-01.txt

         Pages                : 34

         Date          : 2007-5-30

…
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-xie-ccamp-lsp-dppm-01.txt

-----Original Message-----
From: Monique Morrow [mailto:[email-masked]] 
Sent: Thursday, May 31, 2007 2:54 AM
To: [email-masked]
Cc: 'BRUNGARD, DEBORAH A, ATTLABS'; 'zhangguoying'; 'Han Jianghui';
'blithe'; 'xqwei'; 'gjhhit'; 'lufang'; 'i-nishioka'; 'julien.meuric';
'MORTON, ALFRED C, JR. (AL), ATTLABS'; 'Weisheng HU'; [email-masked];
[email-masked]
Subject: Re: New discussion group formed on draft GMPLS LSP DPPM

I shall do this -- stay tuned!

On 5/25/07 9:38 PM, "Weiqiang Sun" <[email-masked]> wrote:

> Hi Monique,

> It's nice that we have one other language in common :)

> Last month when Fred Baker visited SJTU, we were given five minutes to

> introduce the draft. Mr. Baker showed interest in this and we also

> mentioned your involvement in this :).

> We are happy to see that cisco folks also started to work on this,

> though in BMWG. It would be great if you could kindly introduce the

> authors of the draft into this discussion group and possiblly arrange a

> discussion in the next ietf meeting for us, which I believe will

> increase mutual understanding and help fasten the standardization

> process of metrics and related methodologies.

> Thanks.

> --

> Weiqiang

> SJTU

> On 2007-05-25 08:06 -0700，Monique Morrow Wrote:

> Nimen hao!

>> Your timing is perfect as I was about to ping you on the draft.

>> You may want to look at new draft for possible harmonization with the
GMPLS

>> LSP DDPM draft:

http://www.ietf.org/internet-drafts/draft-vapiwala-bmwg-rsvpte-convergence-m

>> otivation-00.txt

>> Kind regards,

>> Monique

>> On 5/25/07 1:35 AM, "Weiqiang Sun" <[email-masked]> wrote:

>>> Hi all,

>>> We have just updated the draft GMPLS LSP DPPM according the feedbacks we
get

>>> since its publication on IETF website. Many thanks to those who have
given

>>> valuable suggestions and also to Adrian and Deborah for allocating the
slot

>>> in the last meeting.

>>> The major improvements are:

>>> 1) We modified the intro part to state the fact that the metrics defined
are

>>> also applicable for TE-MIB inclusion, as may be interest of carriers to

>>> monitor the control plane performance in realtime, through NMS.

>>> 2) We corrected some error pointed out by X. Wei(Fiberhome) and J.

>>> Gao(Huawei).

>>> 3) We changed the measurement unit from "seconds" to "milli-seconds" as

>>> devices that have an averaged per-node processing delay of less than
100ms

>>> is readily available.

>>> The updated draft is attached for your review, before we submit it to
IETF

>>> for publication. Please give your comments.

>>> Thanks and regards.

>>> Weiqiang

>>> SJTU

>>> -----Original Message-----

>>> From: Weiqiang Sun [mailto:[email-masked]]

>>> Sent: Thursday, April 05, 2007 1:11 PM

>>> To: 'BRUNGARD, DEBORAH A, ATTLABS'; 'Monique Morrow'; 'zhangguoying';
'Han

>>> Jianghui'; 'blithe'; 'xqwei'; 'gjhhit'; 'lufang'; 'i-nishioka';

>>> 'julien.meuric'; 'MORTON, ALFRED C, JR. (AL), ATTLABS'

>>> Cc: 'Weisheng HU'; [email-masked]'; [email-masked]'

>>> Subject: RE: New discussion group formed on draft GMPLS LSP DPPM

>>> Hi all,

>>> It is really nice to have all of you together to discuss this draft. The

>>> draft team has had a difficult time when the draft was in its primary
stage

>>> months ago. Now I believe your valuable suggestions and comments will
make

>>> it a lot easier.

>>> As you may be aware, the draft deals only with control plane
performance, in

>>> terms of circuit provisioning capability. One reason that justifies this

>>> work, IMHO, is that the control plane not only automates the
provisioning

>>> process, but more importantly, it also significantly reduces the setup

>>> delay. This opens up opportunities for applications or services that
rely on

>>> dynamically provisioned circuits. One such application has been
implemented

>>> in a GMPLS testbed in Eastern China. However, up to date, there is no

>>> systematic way to evaluate the provisioning performance of the control

>>> plane, especially when the circuit hold-time is comparable with or
several

>>> times the provisioning delay. A set of standardized metrics that vividly

>>> characterize the performance of control plane will definitely increase
the

>>> confidence of applying GMPLS networks in the most natural way and help
to

>>> design a proper timing model.

>>> At the same time, as you may have seen in Guoying's talk during the last
WG

>>> meeting, although variations are observed for all traffic loads

>>> (dynamicity), higher load will lead to higher variation in provisioning

>>> delay. As control plane scalability and resilience issues are getting
into

>>> our sight, a set of standardized metrics will hopefully stimulate the

>>> improvement of control plane implementations, e.g., using hardware

>>> acceleration to reduce the processing time and variation. A reliable and

>>> stable control plane implementation will in turn encourage novel

>>> applications being devised.

>>> Hope Monique would be satisfied with this in regarding to question 2. :)

>>> As to the metrics themselves, the existing ones are merely about control

>>> plane performance, with no regard to CP DP synchronization. This is the
most

>>> lightweight solution we can think of so far and is reasonable when the
time

>>> needed to establish a local XC is neglectable if compared with signaling

>>> processing delay. If this is not the case, still, we can use the control

>>> plane delay, plus a constant representing the XC operation overhead.

>>> By the term provisioning, we have intended to describe application
models

>>> that circuits are established PRIOR to data transfer. This is different
from

>>> the reroute model, where data transfer are ongoing and the rerouting

>>> procedure will eventually leads to packet loss (or service
interruption).

>>> Thus a more reasonable metric that describes rerouting performance, in
my

>>> opinion, would be packet loss, or service interruption time, not delay
(in

>>> the control plane's point of view).It seems to me that measurement of
GMPLS

>>> LSP rerouting is very similar to measurement of MPLS protection, which
is

>>> now been defined in BMWG. Personally, I suggest we initiate another
draft to

>>> deal of LSP rerouting, with reference to MPLS protection in BMWG.
Hopefully

>>> we can get more suggestions from Al in this direction.

>>> For the first question raised by Monique, I have nothing to say by now
since

>>> we are still working on the mentioned documents. Should you have any

>>> comments, please let us know.

>>> For the discussion group, we have a new member, Dr. Huandong Zhao from
China

>>> Telecom Shanghai Research Institute.

>>> Cheers,

>>> Weiqiang

>>> SJTU

>>> -----Original Message-----

>>> From: BRUNGARD, DEBORAH A, ATTLABS [mailto:[email-masked]]

>>> Sent: Wednesday, April 04, 2007 1:56 AM

>>> To: Monique Morrow; zhangguoying; Weiqiang Sun; Han Jianghui; blithe;
xqwei;

>>> gjhhit; lufang; i-nishioka; julien.meuric; MORTON, ALFRED C, JR. (AL),

>>> ATTLABS

>>> Subject: RE: New discussion group formed on draft GMPLS LSP DPPM

>>> Hi all,

>>> I've added Al's address-

>>> Deborah 

>>> -----Original Message-----

>>> From: Monique Morrow [mailto:[email-masked]]

>>> Sent: Monday, April 02, 2007 5:16 AM

>>> To: zhangguoying; Weiqiang Sun; 'Han Jianghui'; 'blithe'; 'xqwei';
'gjhhit';

>>> BRUNGARD, DEBORAH A, ATTLABS; lufang; i-nishioka; julien.meuric

>>> Subject: Re: New discussion group formed on draft GMPLS LSP DPPM

>>> Greetings colleagues,

>>> This is an excellent proposal in terms of focused dialogue with regard
to

>>> this topic. 

>>> To progress:

>>> - Important is note what work has been done in this direction  <Al
Morton

>>> has done quite a bit of work  -- in this direction for example in the
ITU

>>> <y.1540, y.1541, y.1542> -- gap analysis as to what is missing;

>>> - Agreement as to the metrics themselves ;

>>> - Problem to be solved -- why is this an important ? <somewhat implied
in

>>> the draft;

>>> - Method as to actual mechanism to measure would be last IMHO;

>>> Looking forward -

>>> /m 

>>> On 2/4/07 12:08 am, "zhangguoying" <[email-masked]>
wrote:

>>>> Hi all,

>>>> Fist of all, I suggest we form a new discussion group to include
experts

>>> who

>>>> are interested in the "GMPLS LSP dynamic provisioning performance
draft"

>>>> during the IETF 68 meeting.

>>>> Let me say welcome to:

>>>> Julien Meuric, France Telecom,

>>>> Deborah A. Brungard, AT&T,

>>>> Monique Jeanne Morrow, Cisco,

>>>> Luyuan Fang, Cisco

>>>> Itaru Nishioka, NEC

>>>> Deborah would also introduce her colleague Al Morton, chair of the

>>>> benchmarking methodology WG to join our discussion.

>>>> The previous discussion group include :

>>>> Guowu Xie,SJTU

>>>> Weiqiang Sun,SJTU

>>>> Guoying Zhang, CATR MII

>>>> Jianghui Han, IXIA

>>>> Xueqing Wei, Fiberhome

>>>> Jianhua Gao, Huawei

>>>> Here are some important suggestions I received during the meeting:

>>>> 1. Hear more voices and comments from the carriers. Currently the draft

>>> could

>>>> be discussed in ccamp group, but may be transfered to the management AD

>>>> later.---- Adrian

>>>> 2. Refer to the work of benchmarking WG. ---- Deborah

>>>> 3. Include the performance metrics of LSP rerouting. These performance

>>> metrics

>>>> would be useful if the GMPLS MIB support monitoring them in deployed

>>>> network.---- Julien

>>>> 4. Define the method on how to measure the performance metrics, and
refer

>>> to

>>>> the work of benchmarking WG.  ----Itaru Nishioka

>>>> Next we should discuss the plan for 01 version. I suggest we fist refer
to

>>> the

>>>> benchmarking methodology WG work, and consider the possibility of

>>> including

>>>> the LSP rerouting performance in the 01 version.

>>>> 　　　　　　　　zhangguoying

>>>>                Institute of Telecommunication Standards

>>>>                China Academy of Telecom Research ,MII

>>>> 　　　　　　　　[email-masked]

>>>> 　　　　　　　　　　2007-04-02

------=_NextPart_000_000E_01C7A756.08A8BA50
Content-Type: text/html;
	charset="iso-2022-jp"
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: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-2022-jp">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceName"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceType"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"chsdate" downloadurl=3D""/>
<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:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 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;
	font-size:10.5pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:SimSun;}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
 /* Page Definitions */
 @page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 126.65pt 72.0pt 126.65pt;
	layout-grid:15.6pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DZH-CN link=3Dblue vlink=3Dpurple =
style=3D'text-justify-trim:punctuation'>

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

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>Hi all,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>We have updated the GMPLS LSP DPPM draft recently (see =
announcement below).
The draft has received positive responses after the last CCAMP meeting. =
A
discussion group was later setup by Guoying Zhang (RITT, MII of China). =
Thanks
for those who has participated in the group and gave suggestions. In =
particular,
we would like to thank Monique Morrow (Cisco) for indicating a new draft =
in
benchmarking WG related to RSVP-TE performance authored by Cisco folks =
(http://www.ietf.org/internet-drafts/draft-vapiwala-bmwg-rsvpte-convergen=
ce-motivation-00.txt).
We regard this as interests in GMPLS performance, whose progress will =
help
motivating and progressing the GMPLS LSP DPPM =
draft.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>The major improvements in this version =
include:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>1) We modified the intro part to state the fact that the metrics =
defined
are also applicable for TE-MIB inclusion, as may be interest of carriers =
to monitor
the control plane performance in realtime, through =
NMS.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>2) We corrected some error pointed out by X. Wei(Fiberhome) and =
J. Gao(Huawei).<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>3) We changed the measurement unit from &quot;seconds&quot; to
&quot;milli-seconds&quot; as devices that have an averaged per-node =
processing
delay of less than 100ms is readily =
available.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>During preparation of this version, there has been controversy on =
whether
and how LSP rerouting metrics should be added to the draft. Carriers =
have shown
their interest in this metric. However, it seems to us that the =
measurement of rerouting
time will inevitably change the simplicity of methodologies that have =
been
introduced in the draft so far, and the measurement may also be tightly =
coupled
with implementations. Finally Guoying and I would rather leave it to the
working group for possible suggestions and solutions. =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>Please kindly give your comments and =
suggestions.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>Regards,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>Weiqiang Sun<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><st1:place w:st=3D"on"><st1:PlaceName =
w:st=3D"on"><font
  size=3D1 face=3D=1B$BAWBN=1B(B><span lang=3DEN-US =
style=3D'font-size:9.0pt'>Shanghai</span></font></st1:PlaceName><span
 lang=3DEN-US> <st1:PlaceName w:st=3D"on">Jiao</st1:PlaceName> =
<st1:PlaceName
 w:st=3D"on">Tong</st1:PlaceName> <st1:PlaceType =
w:st=3D"on">University</st1:PlaceType></span></st1:place><span
lang=3DEN-US><o:p></o:p></span></p>

<div =
style=3D'mso-element:para-border-div;border:none;border-bottom:solid =
windowtext 1.0pt;
padding:0cm 0cm 1.0pt 0cm'>

<p class=3DMsoPlainText style=3D'border:none;padding:0cm'><font size=3D1 =
face=3D=1B$BAWBN=1B(B><span
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

</div>

<p class=3DMsoPlainText><font size=3D1 color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:blue'>To: i-d-announce =
at
ietf.org <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:blue'>Subject: I-D
ACTION:draft-xie-ccamp-lsp-dppm-01.txt <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:blue'>From: =
Internet-Drafts at
ietf.org <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:blue'>Date: Wed, 30 May =
2007
18:50:01 -0400 <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p=

<p class=3DMsoPlainText><font size=3D1 color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:blue'>A New =
Internet-Draft is
available from the on-line Internet-Drafts <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:blue'>directories.<o:p><=
/o:p></span></font></p>

<p class=3DMsoPlainText><font color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p=

<p class=3DMsoPlainText><font color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p=

<p class=3DMsoPlainText><font size=3D1 color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:blue'>&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
Label Switched Path (LSP) Dynamical Provisioning Performance Metrics in
Generalized MPLS Networks<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:blue'>&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Author(s)&nbsp; :
G. Xie, et al.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:blue'>&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Filename :
draft-xie-ccamp-lsp-dppm-01.txt<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:blue'>&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; :
34<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 color=3Dblue face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;font-family:Arial;color:blue'>&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
<st1:chsdate Year=3D"2007" Month=3D"5" Day=3D"30" IsLunarDate=3D"False"
IsROCDate=3D"False" =
w:st=3D"on">2007-5-30</st1:chsdate><o:p></o:p></span></font></p>

<pre><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:9.0pt;
font-family:Arial'>=1B$B!D=1B(B<o:p></o:p></span></font></pre><pre><font =
size=3D1
face=3DArial><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:Arial'>A URL for this =
Internet-Draft is:<o:p></o:p></span></font></pre>

<div =
style=3D'mso-element:para-border-div;border:none;border-bottom:solid =
windowtext 1.0pt;
padding:0cm 0cm 1.0pt 0cm'><pre style=3D'border:none;padding:0cm'><font =
size=3D1
face=3DArial><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:Arial'><a
href=3D"http://www.ietf.org/internet-drafts/draft-xie-ccamp-lsp-dppm-01.t=
xt">http://www.ietf.org/internet-drafts/draft-xie-ccamp-lsp-dppm-01.txt</=
a><o:p></o:p></span></font></pre></div>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>-----Original Message-----<br>
From: Monique Morrow [mailto:[email-masked]] <br>
Sent: Thursday, May 31, 2007 2:54 AM<br>
To: [email-masked]<br>
Cc: 'BRUNGARD, DEBORAH A, ATTLABS'; <st1:PersonName =
w:st=3D"on">'zhangguoying'</st1:PersonName>;
<st1:PersonName w:st=3D"on">'Han Jianghui'</st1:PersonName>; =
<st1:PersonName
w:st=3D"on">'blithe'</st1:PersonName>; <st1:PersonName =
w:st=3D"on">'xqwei'</st1:PersonName>;
<st1:PersonName w:st=3D"on">'gjhhit'</st1:PersonName>; <st1:PersonName =
w:st=3D"on">'lufang'</st1:PersonName>;
<st1:PersonName w:st=3D"on">'i-nishioka'</st1:PersonName>; =
<st1:PersonName w:st=3D"on">'julien.meuric'</st1:PersonName>;
<st1:PersonName w:st=3D"on">'MORTON, ALFRED C, JR.</st1:PersonName> =
(AL),
ATTLABS'; 'Weisheng HU'; [email-masked]; [email-masked]<br>
Subject: Re: New discussion group formed on draft GMPLS LSP =
DPPM</span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>I shall do this -- stay tuned!<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>On 5/25/07 9:38 PM, &quot;Weiqiang Sun&quot; =
&lt;[email-masked]&gt;
wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; Hi Monique,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; It's nice that we have one other language in common =
:)<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; Last month when Fred Baker visited SJTU, we were given five =
minutes
to<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; introduce the draft. Mr. Baker showed interest in this and =
we also<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; mentioned your involvement in this =
:).<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; We are happy to see that cisco folks also started to work on =
this,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; though in BMWG. It would be great if you could kindly =
introduce the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; authors of the draft into this discussion group and =
possiblly
arrange a<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; discussion in the next ietf meeting for us, which I believe =
will<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; increase mutual understanding and help fasten the =
standardization<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; process of metrics and related =
methodologies.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; Thanks.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; --<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; Weiqiang<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; SJTU<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; On 2007-05-25 08:06 -0700</span>=1B$B!$=1B(B<span =
lang=3DEN-US>Monique Morrow
Wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt; Nimen hao!<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; Your timing is perfect as I was about to ping you on the =
draft.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; You may want to look at new draft for possible =
harmonization
with the GMPLS<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; LSP DDPM draft:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;
http://www.ietf.org/internet-drafts/draft-vapiwala-bmwg-rsvpte-convergenc=
e-m<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; otivation-00.txt<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; Kind regards,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; Monique<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; On 5/25/07 1:35 AM, &quot;Weiqiang Sun&quot;
&lt;[email-masked]&gt; wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Hi all,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; We have just updated the draft GMPLS LSP DPPM =
according the
feedbacks we get<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; since its publication on IETF website. Many thanks =
to those
who have given<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; valuable suggestions and also to Adrian and Deborah =
for
allocating the slot<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; in the last meeting.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; The major improvements =
are:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; 1) We modified the intro part to state the fact that =
the
metrics defined are<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; also applicable for TE-MIB inclusion, as may be =
interest of
carriers to<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; monitor the control plane performance in realtime, =
through
NMS.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; 2) We corrected some error pointed out by X. =
Wei(Fiberhome)
and J.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Gao(Huawei).<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; 3) We changed the measurement unit from =
&quot;seconds&quot;
to &quot;milli-seconds&quot; as<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; devices that have an averaged per-node processing =
delay of
less than 100ms<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; is readily available.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; The updated draft is attached for your review, =
before we
submit it to IETF<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; for publication. Please give your =
comments.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Thanks and regards.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Weiqiang<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; SJTU<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; -----Original =
Message-----<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; From: Weiqiang Sun =
[mailto:[email-masked]]<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Sent: Thursday, April 05, 2007 1:11 =
PM<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; To: 'BRUNGARD, DEBORAH A, ATTLABS'; <st1:PersonName =
w:st=3D"on">'Monique
 Morrow'</st1:PersonName>; <st1:PersonName =
w:st=3D"on">'zhangguoying'</st1:PersonName>;
'Han<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Jianghui'; <st1:PersonName =
w:st=3D"on">'blithe'</st1:PersonName>;
<st1:PersonName w:st=3D"on">'xqwei'</st1:PersonName>; <st1:PersonName =
w:st=3D"on">'gjhhit'</st1:PersonName>;
<st1:PersonName w:st=3D"on">'lufang'</st1:PersonName>; <st1:PersonName =
w:st=3D"on">'i-nishioka'</st1:PersonName>;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <st1:PersonName =
w:st=3D"on">'julien.meuric'</st1:PersonName>;
<st1:PersonName w:st=3D"on">'MORTON, ALFRED C, JR.</st1:PersonName> =
(<st1:State
w:st=3D"on"><st1:place w:st=3D"on">AL</st1:place></st1:State>), =
ATTLABS'<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Cc: 'Weisheng HU'; [email-masked]'; =
[email-masked]'<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Subject: RE: New discussion group formed on draft =
GMPLS LSP
DPPM<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Hi all,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; It is really nice to have all of you together to =
discuss
this draft. The<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; draft team has had a difficult time when the draft =
was in
its primary stage<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; months ago. Now I believe your valuable suggestions =
and
comments will make<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; it a lot easier.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; As you may be aware, the draft deals only with =
control
plane performance, in<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; terms of circuit provisioning capability. One reason =
that
justifies this<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; work, IMHO, is that the control plane not only =
automates
the provisioning<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; process, but more importantly, it also significantly
reduces the setup<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; delay. This opens up opportunities for applications =
or
services that rely on<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; dynamically provisioned circuits. One such =
application has
been implemented<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; in a GMPLS testbed in <st1:place w:st=3D"on">Eastern =
China</st1:place>.
However, up to date, there is no<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; systematic way to evaluate the provisioning =
performance of
the control<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; plane, especially when the circuit hold-time is =
comparable
with or several<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; times the provisioning delay. A set of standardized =
metrics
that vividly<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; characterize the performance of control plane will
definitely increase the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; confidence of applying GMPLS networks in the most =
natural
way and help to<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; design a proper timing =
model.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; At the same time, as you may have seen in Guoying's =
talk
during the last WG<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; meeting, although variations are observed for all =
traffic
loads<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; (dynamicity), higher load will lead to higher =
variation in
provisioning<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; delay. As control plane scalability and resilience =
issues
are getting into<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; our sight, a set of standardized metrics will =
hopefully
stimulate the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; improvement of control plane implementations, e.g., =
using
hardware<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; acceleration to reduce the processing time and =
variation. A
reliable and<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; stable control plane implementation will in turn =
encourage
novel<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; applications being =
devised.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Hope Monique would be satisfied with this in =
regarding to
question 2. :)<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; As to the metrics themselves, the existing ones are =
merely
about control<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; plane performance, with no regard to CP DP =
synchronization.
This is the most<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; lightweight solution we can think of so far and is
reasonable when the time<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; needed to establish a local XC is neglectable if =
compared
with signaling<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; processing delay. If this is not the case, still, we =
can
use the control<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; plane delay, plus a constant representing the XC =
operation
overhead.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; By the term provisioning, we have intended to =
describe
application models<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; that circuits are established PRIOR to data =
transfer. This
is different from<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; the reroute model, where data transfer are ongoing =
and the
rerouting<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; procedure will eventually leads to packet loss (or =
service
interruption).<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Thus a more reasonable metric that describes =
rerouting
performance, in my<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; opinion, would be packet loss, or service =
interruption
time, not delay (in<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; the control plane's point of view).It seems to me =
that
measurement of GMPLS<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; LSP rerouting is very similar to measurement of MPLS
protection, which is<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; now been defined in BMWG. Personally, I suggest we =
initiate
another draft to<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; deal of LSP rerouting, with reference to MPLS =
protection in
BMWG. Hopefully<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; we can get more suggestions from Al in this =
direction.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; For the first question raised by Monique, I have =
nothing to
say by now since<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; we are still working on the mentioned documents. =
Should you
have any<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; comments, please let us =
know.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; For the discussion group, we have a new member, Dr. =
Huandong
Zhao from <st1:country-region w:st=3D"on"><st1:place =
w:st=3D"on">China</st1:place></st1:country-region><o:p></o:p></span></fon=
t></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Telecom Shanghai Research =
Institute.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Cheers,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Weiqiang<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; SJTU<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; -----Original =
Message-----<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; From: BRUNGARD, DEBORAH A, ATTLABS
[mailto:[email-masked]]<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Sent: Wednesday, April 04, 2007 1:56 =
AM<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; To: Monique Morrow; zhangguoying; Weiqiang Sun; Han
Jianghui; blithe; xqwei;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; gjhhit; lufang; i-nishioka; julien.meuric; MORTON, =
ALFRED
C, JR. (<st1:State w:st=3D"on"><st1:place =
w:st=3D"on">AL</st1:place></st1:State>),<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; ATTLABS<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Subject: RE: New discussion group formed on draft =
GMPLS LSP
DPPM<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Hi all,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; I've added Al's =
address-<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Deborah <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; -----Original =
Message-----<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; From: Monique Morrow =
[mailto:[email-masked]]<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Sent: Monday, April 02, 2007 5:16 =
AM<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; To: zhangguoying; Weiqiang Sun; <st1:PersonName =
w:st=3D"on">'Han
 Jianghui'</st1:PersonName>; <st1:PersonName =
w:st=3D"on">'blithe'</st1:PersonName>;
<st1:PersonName w:st=3D"on">'xqwei'</st1:PersonName>; <st1:PersonName =
w:st=3D"on">'gjhhit'</st1:PersonName>;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; BRUNGARD, DEBORAH A, ATTLABS; lufang; i-nishioka;
julien.meuric<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Subject: Re: New discussion group formed on draft =
GMPLS LSP
DPPM<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Greetings colleagues,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; This is an excellent proposal in terms of focused =
dialogue
with regard to<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; this topic. <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; To progress:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; - Important is note what work has been done in this
direction&nbsp; &lt;Al Morton<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; has done quite a bit of work&nbsp; -- in this =
direction for
example in the ITU<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; &lt;y.1540, y.1541, y.1542&gt; -- gap analysis as to =
what
is missing;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; - Agreement as to the metrics themselves =
;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; - Problem to be solved -- why is this an important ?
&lt;somewhat implied in<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; the draft;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; - Method as to actual mechanism to measure would be =
last
IMHO;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; Looking forward -<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; /m <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; On 2/4/07 12:08 am, &quot;zhangguoying&quot;
&lt;[email-masked]&gt; =
wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Hi all,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Fist of all, I suggest we form a new discussion =
group
to include experts<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; who<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; are interested in the &quot;GMPLS LSP dynamic
provisioning performance draft&quot;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; during the IETF 68 =
meeting.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Let me say welcome =
to:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Julien Meuric</st1:City>,
 <st1:country-region w:st=3D"on">France</st1:country-region></st1:place> =
Telecom,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Deborah A. Brungard, =
AT&amp;T,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Monique Jeanne Morrow, =
Cisco,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Luyuan Fang, Cisco<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Itaru Nishioka, NEC<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Deborah would also introduce her colleague Al =
Morton,
chair of the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; benchmarking methodology WG to join our =
discussion.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; The previous discussion group include =
:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Guowu Xie,SJTU<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Weiqiang Sun,SJTU<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Guoying Zhang, CATR =
MII<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Jianghui Han, IXIA<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Xueqing Wei, =
Fiberhome<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Jianhua Gao, Huawei<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Here are some important suggestions I received =
during
the meeting:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; 1. Hear more voices and comments from the =
carriers.
Currently the draft<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; could<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; be discussed in ccamp group, but may be =
transfered to
the management AD<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; later.---- <st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Adrian</st1:place></st1:City><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; 2. Refer to the work of benchmarking WG. ---- =
Deborah<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; 3. Include the performance metrics of LSP =
rerouting.
These performance<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; metrics<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; would be useful if the GMPLS MIB support =
monitoring
them in deployed<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; network.---- Julien<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; 4. Define the method on how to measure the =
performance
metrics, and refer<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; to<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; the work of benchmarking WG.&nbsp; ----Itaru =
Nishioka<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; Next we should discuss the plan for 01 version. =
I
suggest we fist refer to<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; benchmarking methodology WG work, and consider =
the
possibility of<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt; including<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; the LSP rerouting performance in the 01 =
version.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; </span>=1B$B!!!!!!!!!!!!!!!!=1B(B<span =
lang=3DEN-US>zhangguoying<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<st1:place w:st=3D"on"><st1:PlaceType =
w:st=3D"on">Institute</st1:PlaceType> of <st1:PlaceName
 w:st=3D"on">Telecommunication</st1:PlaceName></st1:place> =
Standards<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<st1:place w:st=3D"on"><st1:PlaceName w:st=3D"on">China</st1:PlaceName> =
<st1:PlaceType
 w:st=3D"on">Academy</st1:PlaceType></st1:place> of Telecom Research =
,MII<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; </span>=1B$B!!!!!!!!!!!!!!!!=1B(B<span =
lang=3DEN-US>[email-masked]<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D=1B$BAWBN=1B(B><span =
lang=3DEN-US style=3D'font-size:
9.0pt'>&gt;&gt;&gt;&gt; =
</span>=1B$B!!!!!!!!!!!!!!!!!!!!=1B(B<st1:chsdate IsROCDate=3D"False"
IsLunarDate=3D"False" Day=3D"2" Month=3D"4" Year=3D"2007" =
w:st=3D"on"><span lang=3DEN-US>2007-04-02</span></st1:chsdate><span
lang=3DEN-US><o:p></o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_000E_01C7A756.08A8BA50--

Delivery-date: Tue, 05 Jun 2007 01:08:22 +0000
Date: Tue, 05 Jun 2007 09:06:29 +0800
From: Mach Chen <[email-masked]>
Subject: Re: Polling for WG adoption of draft-chen-ccamp-ospf-interas-te-extension-02.txt
To: Adrian Farrel <[email-masked]>
Cc: [email-masked]

Hi Adrian and all,

Yes, we will resubmit this I-D before the cut-offs for Chicago. 

Best regards,
Mach

----- Original Message ----- 
From: "Adrian Farrel" <[email-masked]>
To: <[email-masked]>
Sent: Tuesday, June 05, 2007 7:07 AM
Subject: Re: Polling for WG adoption of draft-chen-ccamp-ospf-interas-te-extension-02.txt

> Well, I wouldn't say we were overwhelmed with responses, but all that we saw
> were positive (although there is a technical point from Jean-Louis to be
> addresses).
> 
> The chairs believe that this I-D is a useful, if small, building block for
> inter-AS TE so we will make it a WG draft.
> 
> Authors, please resubmit your I-D as
> draft-ietf-ccamp-ospf-interas-te-extension-00.txt. Please make no changes
> except:
> - file name
> - dates
> - anything needed to pass through idnits
> 
> Can you get this done before he cut-offs for Chicago?
> 
> Thanks,
> Adrian
> 
> ----- Original Message ----- 
> From: "Adrian Farrel" <[email-masked]>
> To: <[email-masked]>
> Sent: Monday, April 30, 2007 4:00 PM
> Subject: Polling for WG adoption of
> draft-chen-ccamp-ospf-interas-te-extension-02.txt
> 
> 
>> Hi,
>>
>> In Prague we discussed this draft and the general opinion seemed to be
>> that this is a useful extension, but that some clarifications needed to be
>> added to the I-D. This new revision appears to address all of the concerns
>> as below.
>>
>> Therefore given the interest in Prague and the relevance of this I-D to
>> our inter-domain TE charter actions, we are polling the WG for adoption of
>> this I-D as a CCAMP draft.
>>
>> Opinions please.
>>
>> Thanks
>> Adrian and Deborah
>>
>> ====
>> Overlap with L1VPN autodiscovery
>>
>>    A question was raised as to whether there was an overlap
>>    with the L1VPN autodiscovery work used to distribute
>>    membership information (draft-ietf-l1vpn-ospf-auto-discovery)
>>
>>    It appears that the mechanisms and purposes are different.
>>
>>    The authors have added text to clarify that there is no overlap.
>>
>> Language change for "OSPF" becomes "OSPF-TE"
>>
>>    Concern was raised that the I-D talked about "OSPF" but the
>>    function is "OSPF-TE".
>>
>>    The authors have updated the I-D accordingly.
>>
>> Include reference to OSPFv3 as well
>>
>>    A request was made to include OSPFv3.
>>
>>    The authors have added text to explain that the same extensions
>>    apply to OSPF v2 and OSPF v3 TE extensions.
>>
>> Make it *incredibly* clear that TE distribution between ASes is
>> not in scope.
>>
>>    Although the I-D had plenty of this material, the authors have
>>    beefed it up further by including the list of things that they are
>>    not doing from their Prague slides.
>>
>>
>>
>>
>>
>>
>>
> 
> 
> 
>

Delivery-date: Mon, 04 Jun 2007 23:10:26 +0000
Reply-To: "Adrian Farrel" <[email-masked]>
From: "Adrian Farrel" <[email-masked]>
To: <[email-masked]>
Subject: Re: Polling for WG adoption of draft-chen-ccamp-ospf-interas-te-extension-02.txt
Date: Tue, 5 Jun 2007 00:07:48 +0100
Organization: Old Dog Consulting

Well, I wouldn't say we were overwhelmed with responses, but all that we saw
were positive (although there is a technical point from Jean-Louis to be
addresses).

The chairs believe that this I-D is a useful, if small, building block for
inter-AS TE so we will make it a WG draft.

Authors, please resubmit your I-D as
draft-ietf-ccamp-ospf-interas-te-extension-00.txt. Please make no changes
except:
- file name
- dates
- anything needed to pass through idnits

Can you get this done before he cut-offs for Chicago?

Thanks,
Adrian

----- Original Message ----- 
From: "Adrian Farrel" <[email-masked]>
To: <[email-masked]>
Sent: Monday, April 30, 2007 4:00 PM
Subject: Polling for WG adoption of
draft-chen-ccamp-ospf-interas-te-extension-02.txt

> Hi,
>
> In Prague we discussed this draft and the general opinion seemed to be
> that this is a useful extension, but that some clarifications needed to be
> added to the I-D. This new revision appears to address all of the concerns
> as below.
>
> Therefore given the interest in Prague and the relevance of this I-D to
> our inter-domain TE charter actions, we are polling the WG for adoption of
> this I-D as a CCAMP draft.
>
> Opinions please.
>
> Thanks
> Adrian and Deborah
>
> ====
> Overlap with L1VPN autodiscovery
>
>    A question was raised as to whether there was an overlap
>    with the L1VPN autodiscovery work used to distribute
>    membership information (draft-ietf-l1vpn-ospf-auto-discovery)
>
>    It appears that the mechanisms and purposes are different.
>
>    The authors have added text to clarify that there is no overlap.
>
> Language change for "OSPF" becomes "OSPF-TE"
>
>    Concern was raised that the I-D talked about "OSPF" but the
>    function is "OSPF-TE".
>
>    The authors have updated the I-D accordingly.
>
> Include reference to OSPFv3 as well
>
>    A request was made to include OSPFv3.
>
>    The authors have added text to explain that the same extensions
>    apply to OSPF v2 and OSPF v3 TE extensions.
>
> Make it *incredibly* clear that TE distribution between ASes is
> not in scope.
>
>    Although the I-D had plenty of this material, the authors have
>    beefed it up further by including the list of things that they are
>    not doing from their Prague slides.
>
>
>
>
>
>
>

Delivery-date: Mon, 04 Jun 2007 16:16:54 +0000
To: Tony Jeffree <[email-masked]>
Cc: Paul Congdon <[email-masked]>, Dan Romascanu <[email-masked]>, Ross Callon <[email-masked]>, Dave Ward <[email-masked]>, Bernard Aboba <[email-masked]>, Bert Wijnen <[email-masked]>, CCAMP Mailing List <[email-masked]>, GELS Mailing List <[email-masked]>, Adrian Farrel <[email-masked]>, Deborah Brungard <[email-masked]>, Adrian Farrel <[email-masked]>, Deborah Brungard <[email-masked]>
From: Adrian Farrel (IETF CCAMP WG) <[email-masked]>
Subject: New Liaison Statement, "GMPLS Control of 802.1Qay Networks" 
Reply-To: Adrian Farrel <[email-masked]>
Date: Mon, 04 Jun 2007 12:14:16 -0400

Title: GMPLS Control of 802.1Qay Networks
Submission Date: 2007-06-04
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=336 
Please reply by 2007-07-19

From: Adrian Farrel(IETF CCAMP WG) <[email-masked]>
To: IEEE 802.1(Tony Jeffree <[email-masked]>)
Cc: Paul Congdon <[email-masked]>
Dan Romascanu <[email-masked]>
Ross Callon <[email-masked]>
Dave Ward <[email-masked]>
Bernard Aboba <[email-masked]>
Bert Wijnen <[email-masked]>
CCAMP Mailing List <[email-masked]>
GELS Mailing List <[email-masked]>
Reponse Contact: Adrian Farrel <[email-masked]>
Deborah Brungard <[email-masked]>
Technical Contact: Adrian Farrel <[email-masked]>
Deborah Brungard <[email-masked]>
Purpose: For action 
Body: The CCAMP Working Group of the IETF notes the recent approval
of a PAR for the 802.1Qay project, and we understand that 
part of the intent of this project is to support provisioning
systems that explicitly select traffic engineered paths within
Provider Backbone Bridge (802.1ah) Networks.

It has been suggested that GMPLS protocols developed within 
the IETF under the care of the CCAMP Working Group are 
suitable aids to such provisioning systems. We propose to 
investigate the applicability of GMPLS protocols to the 
control of 802.1Qay networks, and we would like to work with 
the IEEE by proposing suitable GMPLS protocol extensions for 
use in single and multi-domain networks subject to 802.1 
reaching consensus on the definition of the data plane.
 
Please confirm that in your opinion the use of GMPLS control 
plane protocols in this way is appropriate, and that IEEE 
802.1 has no objection to the IETF CCAMP Working Group 
starting work in this area.
 
Best regards,
Adrian Farrel and Deborah Brungard
IETF CCAMP Working Group Co-Chairs
Attachment(s):
No document has been attached

Delivery-date: Mon, 04 Jun 2007 01:28:01 +0000
Reply-To: "Adrian Farrel" <[email-masked]>
From: "Adrian Farrel" <[email-masked]>
To: "Bijan Jabbari" <[email-masked]>, <[email-masked]>
Cc: "'Ross Callon'" <[email-masked]>, "'Brungard, Deborah A, ALABS'" <[email-masked]>
Subject: Re: Moving forward with a GELS Control Plane
Date: Mon, 4 Jun 2007 02:26:50 +0100

I think CCAMP is limited to GMPLS.

If you have other proposals, I suggest floating them initially on the GELS 
list and then considering holding a BoF.

Adrian
----- Original Message ----- 
From: "Bijan Jabbari" <[email-masked]>
To: "'Adrian Farrel'" <[email-masked]>; <[email-masked]>
Cc: "'Ross Callon'" <[email-masked]>; "'Brungard, Deborah A, ALABS'" 
<[email-masked]>
Sent: Monday, June 04, 2007 3:10 PM
Subject: RE: Moving forward with a GELS Control Plane

> Adrian,
>
>  Will the scope be limited to GMPLS or other provisioning methods will 
> also
> be considered in updating the CCAMP charter?
>
>  - Bijan
>
>
> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]] On Behalf
> Of Adrian Farrel
> Sent: Saturday, June 02, 2007 12:18 PM
> To: [email-masked]
> Cc: Ross Callon; Brungard, Deborah A, ALABS
> Subject: Moving forward with a GELS Control Plane
>
> Hi,
>
> Deborah and I have been discussing this with Ross. We are sending the
> liaison below to IEEE 802.1, and if their answer is satisfactory, we will
> make any updates necessary to the CCAMP charter to take on this work.
>
> Cheers,
> Adrian
>
> ==
>
> From: IETF CCAMP Working Group
> To: IEEE 802.1
> Cc: Ross Callon, Dave Ward, Tony Jeffree, Paul Congdon, Dan Ramascanu,
> Bernard Aboba, Bert Wijnen, CCAMP Mailing List
>
> Subject: GMPLS Control of 802.1Qay Networks
> For Action:
> Deadline: 19th July 2007
>
> We note the recent approval of a PAR for the 802.1Qay project, and we
> understand that part of the intent of this project is to support
> provisioning systems that explicitly select traffic engineered paths
> within Provider Backbone Bridge (802.1ah) Networks.
>
> It has been suggested that GMPLS protocols developed within the IETF
> under the care of the CCAMP Working Group are suitable aids to such
> provisioning systems. We propose to investigate the applicability of GMPLS
> protocols to the control of 802.1Qay networks, and we would like to work
> with the IEEE by proposing suitable GMPLS protocol extensions for use in
> single and multi-domain networks subject to 802.1 reaching consensus on
> the definition of the data plane.
>
> Please confirm that in your opinion the use of GMPLS control plane
> protocols in this way is appropriate, and that IEEE 802.1 has no objection
> to the IETF CCAMP Working Group starting work in this area.
>
> Best regards,
> Adrian Farrel and Deborah Brungard
> IETF CCAMP Working Group Co-Chairs
>
>
>
>
>
>
> 

Delivery-date: Mon, 04 Jun 2007 01:13:22 +0000
From: "Bijan Jabbari" <[email-masked]>
To: "'Adrian Farrel'" <[email-masked]>, <[email-masked]>
Cc: "'Ross Callon'" <[email-masked]>, "'Brungard, Deborah A, ALABS'" <[email-masked]>
Subject: RE: Moving forward with a GELS Control Plane
Date: Mon, 4 Jun 2007 10:10:30 -0400

Adrian,

  Will the scope be limited to GMPLS or other provisioning methods will also
be considered in updating the CCAMP charter?

  - Bijan

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] On Behalf
Of Adrian Farrel
Sent: Saturday, June 02, 2007 12:18 PM
To: [email-masked]
Cc: Ross Callon; Brungard, Deborah A, ALABS
Subject: Moving forward with a GELS Control Plane

Hi,

Deborah and I have been discussing this with Ross. We are sending the 
liaison below to IEEE 802.1, and if their answer is satisfactory, we will 
make any updates necessary to the CCAMP charter to take on this work.

Cheers,
Adrian

==

From: IETF CCAMP Working Group
To: IEEE 802.1
Cc: Ross Callon, Dave Ward, Tony Jeffree, Paul Congdon, Dan Ramascanu,
Bernard Aboba, Bert Wijnen, CCAMP Mailing List

Subject: GMPLS Control of 802.1Qay Networks
For Action:
Deadline: 19th July 2007

We note the recent approval of a PAR for the 802.1Qay project, and we
understand that part of the intent of this project is to support
provisioning systems that explicitly select traffic engineered paths
within Provider Backbone Bridge (802.1ah) Networks.

It has been suggested that GMPLS protocols developed within the IETF
under the care of the CCAMP Working Group are suitable aids to such
provisioning systems. We propose to investigate the applicability of GMPLS
protocols to the control of 802.1Qay networks, and we would like to work
with the IEEE by proposing suitable GMPLS protocol extensions for use in
single and multi-domain networks subject to 802.1 reaching consensus on
the definition of the data plane.

Please confirm that in your opinion the use of GMPLS control plane
protocols in this way is appropriate, and that IEEE 802.1 has no objection
to the IETF CCAMP Working Group starting work in this area.

Best regards,
Adrian Farrel and Deborah Brungard
IETF CCAMP Working Group Co-Chairs

Delivery-date: Sun, 03 Jun 2007 04:29:44 +0000
Reply-To: "Adrian Farrel" <[email-masked]>
From: "Adrian Farrel" <[email-masked]>
To: "Kim Young Hwa" <[email-masked]>, <[email-masked]>
Subject: Re: Inquiry of GELS
Date: Sun, 3 Jun 2007 05:14:42 +0100

Hi,

Please see the email describing a liaison to 802.1.

In the both Don and Loa have been preparing the ground by looking at the 
changes/extensions that might be required for GMPLS signaling.

Cheers,
Adrian

> Hi ccampers,
>
> I'd like to know the latest status of GELS and the detailed
. mechanism for the GELS.
> Who could tell me the information of GELS?
>
> Thanks in advance,
> Young
>
> ====================================
> Young Hwa Kim
> Principal Member / Ph.D
> BcN Research Division, ETRI
> Tel:     +82-42-860-5819
> Fax:    +82-42-860-6104
> e-mail: [email-masked]
> ==================================== 

Delivery-date: Sun, 03 Jun 2007 04:17:42 +0000
Reply-To: "Adrian Farrel" <[email-masked]>
From: "Adrian Farrel" <[email-masked]>
To: <[email-masked]>
Cc: "Ross Callon" <[email-masked]>, "Brungard, Deborah A, ALABS" <[email-masked]>
Subject: Moving forward with a GELS Control Plane
Date: Sat, 2 Jun 2007 17:18:23 +0100

Hi,

Deborah and I have been discussing this with Ross. We are sending the 
liaison below to IEEE 802.1, and if their answer is satisfactory, we will 
make any updates necessary to the CCAMP charter to take on this work.

Cheers,
Adrian

==

From: IETF CCAMP Working Group
To: IEEE 802.1
Cc: Ross Callon, Dave Ward, Tony Jeffree, Paul Congdon, Dan Ramascanu,
Bernard Aboba, Bert Wijnen, CCAMP Mailing List

Subject: GMPLS Control of 802.1Qay Networks
For Action:
Deadline: 19th July 2007

We note the recent approval of a PAR for the 802.1Qay project, and we
understand that part of the intent of this project is to support
provisioning systems that explicitly select traffic engineered paths
within Provider Backbone Bridge (802.1ah) Networks.

It has been suggested that GMPLS protocols developed within the IETF
under the care of the CCAMP Working Group are suitable aids to such
provisioning systems. We propose to investigate the applicability of GMPLS
protocols to the control of 802.1Qay networks, and we would like to work
with the IEEE by proposing suitable GMPLS protocol extensions for use in
single and multi-domain networks subject to 802.1 reaching consensus on
the definition of the data plane.

Please confirm that in your opinion the use of GMPLS control plane
protocols in this way is appropriate, and that IEEE 802.1 has no objection
to the IETF CCAMP Working Group starting work in this area.

Best regards,
Adrian Farrel and Deborah Brungard
IETF CCAMP Working Group Co-Chairs