
From Internet-Drafts@ietf.org  Wed Dec  1 06:30:14 2010
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F135C28C0F4; Wed,  1 Dec 2010 06:30:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.443
X-Spam-Level: 
X-Spam-Status: No, score=-102.443 tagged_above=-999 required=5 tests=[AWL=0.156, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7wi11bMm4SS7; Wed,  1 Dec 2010 06:30:03 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 11C5F3A6D05; Wed,  1 Dec 2010 06:30:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.09
Message-ID: <20101201143002.24190.6477.idtracker@localhost>
Date: Wed, 01 Dec 2010 06:30:02 -0800
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-00.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Dec 2010 14:30:14 -0000

--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           : GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)
	Author(s)       : A. Takacs, et al.
	Filename        : draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-00.txt
	Pages           : 14
	Date            : 2010-12-01

This document defines a method for the support of GMPLS asymmetric
bandwidth bidirectional Label Switched Paths (LSPs).  The presented
approach is applicable to any switching technology and builds on the
original Resource Reservation Protocol (RSVP) model for the transport
of traffic-related parameters.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-00.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-12-01062101.I-D@ietf.org>


--NextPart--

From Internet-Drafts@ietf.org  Wed Dec  1 09:15:03 2010
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E3F728C10B; Wed,  1 Dec 2010 09:15:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.442
X-Spam-Level: 
X-Spam-Status: No, score=-102.442 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l9EUiGuspmBF; Wed,  1 Dec 2010 09:15:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7FFC728C100; Wed,  1 Dec 2010 09:15:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.09
Message-ID: <20101201171502.21612.32997.idtracker@localhost>
Date: Wed, 01 Dec 2010 09:15:02 -0800
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-general-constraint-encode-04.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Dec 2010 17:15:03 -0000

--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           : General Network Element Constraint Encoding for GMPLS Controlled Networks
	Author(s)       : G. Bernstein
	Filename        : draft-ietf-ccamp-general-constraint-encode-04.txt
	Pages           : 28
	Date            : 2010-12-01

Generalized Multiprotocol Label Switching can be used to control a 
wide variety of technologies. In some of these technologies network 
elements and links may impose additional routing constraints such as 
asymmetric switch connectivity, non-local label assignment, and label 
range limitations on links.
 

This document provides efficient, protocol-agnostic encodings for 
general information elements representing connectivity and label 
constraints as well as label availability. It is intended that 
protocol-specific documents will reference this memo to describe how 
information is carried for specific uses.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-general-constraint-encode-04.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-general-constraint-encode-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-12-01090846.I-D@ietf.org>


--NextPart--

From Internet-Drafts@ietf.org  Wed Dec  1 09:30:18 2010
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 904D33A6C56; Wed,  1 Dec 2010 09:30:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.443
X-Spam-Level: 
X-Spam-Status: No, score=-102.443 tagged_above=-999 required=5 tests=[AWL=0.156, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fyLT9Xy1rNqF; Wed,  1 Dec 2010 09:30:12 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 909A828C0EE; Wed,  1 Dec 2010 09:30:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.09
Message-ID: <20101201173001.27874.54129.idtracker@localhost>
Date: Wed, 01 Dec 2010 09:30:01 -0800
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-rwa-wson-encode-07.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Dec 2010 17:30:19 -0000

--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           : Routing and Wavelength Assignment Information Encoding for Wavelength Switched Optical Networks
	Author(s)       : G. Bernstein
	Filename        : draft-ietf-ccamp-rwa-wson-encode-07.txt
	Pages           : 34
	Date            : 2010-12-01

A wavelength switched optical network (WSON) requires that certain 
key information elements are made available to facilitate path 
computation and the establishment of label switching paths (LSPs). 
The information model described in "Routing and Wavelength Assignment 
Information for Wavelength Switched Optical Networks" shows what 
information is required at specific points in the WSON. Part of the 
WSON information model contains aspects that may be of general 
applicability to other technologies, while other parts are fairly 
specific to WSONs.  

This document provides efficient, protocol-agnostic encodings for the 
WSON specific information elements. It is intended that protocol-
specific documents will reference this memo to describe how 
information is carried for specific uses. Such encodings can be used 
to extend GMPLS signaling and routing protocols. In addition these 
encodings could be used by other mechanisms to convey this same 
information to a path computation element (PCE).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-rwa-wson-encode-07.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-rwa-wson-encode-07.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-12-01092205.I-D@ietf.org>


--NextPart--

From adrian@olddog.co.uk  Wed Dec  1 14:31:00 2010
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 380DE3A67F7 for <ccamp@core3.amsl.com>; Wed,  1 Dec 2010 14:31:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZgxEBBTRiIy3 for <ccamp@core3.amsl.com>; Wed,  1 Dec 2010 14:30:59 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by core3.amsl.com (Postfix) with ESMTP id 07A683A67D3 for <ccamp@ietf.org>; Wed,  1 Dec 2010 14:30:58 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id oB1MW7Tf012507;  Wed, 1 Dec 2010 22:32:07 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id oB1MW6aE012498;  Wed, 1 Dec 2010 22:32:07 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Preeti Daundiyal'" <preeti.daundiyal@aricent.com>, "'Lou Berger'" <lberger@labn.net>
References: <78BB64A749208840A7FE3DF032E036940125854C71@GUREXMB01.ASIAN.AD.ARICENT.COM>	<4CDB1470.6040905@labn.net> <78BB64A749208840A7FE3DF032E03694014B8C471C@GUREXMB01.ASIAN.AD.ARICENT.COM>
In-Reply-To: <78BB64A749208840A7FE3DF032E03694014B8C471C@GUREXMB01.ASIAN.AD.ARICENT.COM>
Date: Wed, 1 Dec 2010 22:32:10 -0000
Message-ID: <073201cb91a7$9821a9a0$c864fce0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQDhGtqRAkkf+df5FAmQzhfDDxSwBwHgSKB4AW+TWMeVRpby4A==
Content-Language: en-gb
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] GMPLS: RFC 3473 RSVP Notify Request Query
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Dec 2010 22:31:00 -0000

Hi Preeti,

You say:

> per our requirement , from the LSP ingress node we intend to signal=20
> both the upstream and downstream notify receipt address to the LSP
> intermediate/egress node.=20

Perhaps we need to spend some time exposing this requirement?
Why does the ingress need to tell a transit node which are the =
downstream notify
recipients?

You say in an earlier email that you want to be able to send both the =
upstream
and downstream notify recipients in the Path message, but you don't say =
why, or
how this is useful.

> As per the flow specified below, (suppose we have tunnel from Node A =
to Node
C).
> Node A (Tunnel ingress) sends two notify object in the RSVP path =
message to
node B .
>=A0One Notify request object specifying the upstream notify receipent =
address and
the
> another specify downstream notify address.
>
> The address values being sent in notify request is as per rfc 4802 MIB =
objects
> (gmplsTunnelUpstreamNotifyRecipient, =
gmplsTunnelSendPathNotifyRecipient).=20
=A0
But please read 4802 more carefully!
The first object...
    "Indicates the address of the upstream recipient for Notify
     messages relating to this tunnel and issued by this LSR.  This
     information is typically received from an upstream LSR in a Path
     message.

The second object...
    "Indicates to a downstream LSR the address to which it should
     send upstream Notify messages relating to this tunnel.

Only the second object is signaled by this LSR.

Cheers,
Adrian


From adrian@olddog.co.uk  Sun Dec  5 11:19:33 2010
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6FCB328C135 for <ccamp@core3.amsl.com>; Sun,  5 Dec 2010 11:19:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZzYMwuGhUGoj for <ccamp@core3.amsl.com>; Sun,  5 Dec 2010 11:19:32 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by core3.amsl.com (Postfix) with ESMTP id 44B5128C133 for <ccamp@ietf.org>; Sun,  5 Dec 2010 11:19:32 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id oB5JKrxk025094 for <ccamp@ietf.org>; Sun, 5 Dec 2010 19:20:53 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id oB5JKqit025090 for <ccamp@ietf.org>; Sun, 5 Dec 2010 19:20:52 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ccamp@ietf.org>
References: <20101205191501.19204.27416.idtracker@localhost>
In-Reply-To: <20101205191501.19204.27416.idtracker@localhost>
Date: Sun, 5 Dec 2010 19:20:56 -0000
Message-ID: <0d4101cb94b1$8ad15d10$a0741730$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIFM/NXmjQucSvfeIEoooPg3/b6EZMe+vlQ
Content-Language: en-gb
Subject: [CCAMP] FW: I-D Action:draft-shiomoto-ccamp-switch-programming-04.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Dec 2010 19:19:33 -0000

FYI

This revision contains a few editorial clean-ups resulting from review by the
document shepherd.

Cheers,
Adrian

> -----Original Message-----
> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org]
> On Behalf Of Internet-Drafts@ietf.org
> Sent: 05 December 2010 19:15
> To: i-d-announce@ietf.org
> Subject: I-D Action:draft-shiomoto-ccamp-switch-programming-04.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> 
> 	Title           : Advice on When It is Safe to Start Sending Data on
Label
> Switched Paths Established Using RSVP-TE
> 	Author(s)       : K. Shiomoto, A. Farrel
> 	Filename        : draft-shiomoto-ccamp-switch-programming-04.txt
> 	Pages           : 11
> 	Date            : 2010-12-05
> 
> The Resource Reservation Protocol (RSVP) has been extended to support
> Traffic Engineering (TE) in Multiprotocol Label Switching (MPLS) and
> Generalized MPLS (GMPLS) networks. The protocol enables signaling
> exchanges to establish Label Switched Paths (LSPs) that traverse
> nodes and links to provide end-to-end data paths. Each node is
> programmed with "cross-connect" information as the signaling messages
> are processed. The cross-connection information instructs the node
> how to forward data that it receives.
> 
> End points of an LSP need to know when it is safe to start sending
> data so that it is not misdelivered, and so that safety issues
> specific to optical data plane technology are satisfied. Likewise,
> all label switching routers along the path of the LSP need to know
> when to programme their data planes relative to sending and receiving
> control plane messages.
> 
> This document clarifies and summarises the RSVP-TE protocol exchanges
> with relation to the programming of cross-connects along an LSP for
> both unidirectional and bidirectional LSPs. This document does not
> define any new procedures or protocol extensions, and defers
> completely to the documents that provide normative references. The
> clarifications set out in this document may also be used to help
> interpret LSP establishment performance figures for MPLS-TE and GMPLS
> devices.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-shiomoto-ccamp-switch-
> programming-04.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.


From mach@huawei.com  Tue Dec  7 01:39:38 2010
Return-Path: <mach@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B3113A6836 for <ccamp@core3.amsl.com>; Tue,  7 Dec 2010 01:39:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.632
X-Spam-Level: 
X-Spam-Status: No, score=-1.632 tagged_above=-999 required=5 tests=[AWL=-1.738, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_83=0.6, RDNS_NONE=0.1, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SuTPpgUh8FWN for <ccamp@core3.amsl.com>; Tue,  7 Dec 2010 01:39:37 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 1FFCC3A682F for <ccamp@ietf.org>; Tue,  7 Dec 2010 01:39:37 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LD1002UNXIVA0@szxga05-in.huawei.com> for ccamp@ietf.org; Tue, 07 Dec 2010 17:40:08 +0800 (CST)
Received: from m55527c ([10.110.98.66]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LD1008OSXIUIT@szxga05-in.huawei.com> for ccamp@ietf.org; Tue, 07 Dec 2010 17:40:07 +0800 (CST)
Date: Tue, 07 Dec 2010 17:40:06 +0800
From: Mach Chen <mach@huawei.com>
In-reply-to: <201012070810.oB78AATj085314@mse2.zte.com.cn>
To: wang.xuerong@zte.com.cn, zhangrenhai@huawei.com, duanxiaodong@chinamobile.com
Message-id: <2EB8875CE9724971A97B05EBC39717B6@m55527c>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8064.206
X-Mailer: Microsoft Windows Live Mail 14.0.8064.206
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=original
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3
X-MSMail-priority: Normal
References: <201012070810.oB78AATj085314@mse2.zte.com.cn>
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] A question about RFC5392
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Dec 2010 09:39:38 -0000

Hi,

Since, in the current specification, an ASBR is responsible for advertising 
both directions of an inter-AS TE link and the parameters of the reverse 
direction are manually configured at the ASBR; as stated in the RFC, Remote 
AS number and ASBR ID are essential for inter-AS path computation and are 
rarely changed when configured. But for other alterable paramerters as you 
pointed out, they may be changed as time goes on (e.g., a TE LSP established 
over the link, unused bandwidth should be changed accordingly), and the ASBR 
may be difficult/impossible to get the lastest value of those permerters 
timely.

The vague sentence intends to give choice to the implementation and 
operators whehter to advertise the other TE link paramerters, and of cause 
the current specification does preclude advertising other paramerters when 
needed.

Hope this could clarify your question.

Best regards,
Mach


--------------------------------------------------
From: <wang.xuerong@zte.com.cn>
Sent: Tuesday, December 07, 2010 3:40 PM
To: <mach@huawei.com>; <zhangrenhai@huawei.com>; 
<duanxiaodong@chinamobile.com>
Cc: <ccamp@ietf.org>
Subject: A question about RFC5392

> Hi Mach, Renhai and Xiaodong
>
> I read the following words in RFC5392: "Only some essential TE information
> for the link needs to be
> advertised; i.e., the Link Type, the Remote AS number, and the Remote ASBR
> ID."
>
> I don't know why only Link Type, Remote AS number, and Remote ASBR ID are
> described in the above sentence?
> Since other parameters are also necessary for CSPF computation, such as
> Metrics, bandwith,etc.
> So, what's the consideration when you're writting this document? Could you
> tell me the reason?
>
> Many thanks!
>
> Best Regards,
> Xuerong Wang
>
>
>
> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this mail is 
> solely property of the sender's organization. This mail communication is 
> confidential. Recipients named above are obligated to maintain secrecy and 
> are not permitted to disclose the contents of this communication to 
> others.
> This email and any files transmitted with it are confidential and intended 
> solely for the use of the individual or entity to whom they are addressed. 
> If you have received this email in error please notify the originator of 
> the message. Any views expressed in this message are those of the 
> individual sender.
> This message has been scanned for viruses and Spam by ZTE Anti-Spam 
> system.
> 

From wang.xuerong@zte.com.cn  Tue Dec  7 00:09:43 2010
Return-Path: <wang.xuerong@zte.com.cn>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8099D3A692E for <ccamp@core3.amsl.com>; Tue,  7 Dec 2010 00:09:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.354
X-Spam-Level: 
X-Spam-Status: No, score=-100.354 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_83=0.6, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dgBI-4eV0WTJ for <ccamp@core3.amsl.com>; Tue,  7 Dec 2010 00:09:42 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 1E1D93A6926 for <ccamp@ietf.org>; Tue,  7 Dec 2010 00:09:41 -0800 (PST)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 20595473195744; Tue, 7 Dec 2010 16:07:30 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.16] with StormMail ESMTP id 4090.473195744; Tue, 7 Dec 2010 16:05:47 +0800 (CST)
Received: (from root@localhost) by mse2.zte.com.cn id oB78B7jN085985 for <ccamp@ietf.org>; Tue, 7 Dec 2010 16:11:07 +0800 (CST) (envelope-from wang.xuerong@zte.com.cn)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id oB77evQS058501; Tue, 7 Dec 2010 15:40:58 +0800 (CST) (envelope-from wang.xuerong@zte.com.cn)
Message-Id: <201012070811.oB78B7jN085985@mse2.zte.com.cn>
To: mach@huawei.com, zhangrenhai@huawei.com, duanxiaodong@chinamobile.com
MIME-Version: 1.0
X-KeepSent: 12F867A1:E15AC7FF-482577F2:0025A390; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
From: wang.xuerong@zte.com.cn
Date: Tue, 7 Dec 2010 15:40:45 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2010-12-07 15:40:44, Serialize complete at 2010-12-07 15:40:44
Content-Type: multipart/alternative; boundary="=_alternative 002A3221482577F2_="
X-MAIL: mse2.zte.com.cn oB78B7jN085985
X-MSS: AUDITRELEASE@mse2.zte.com.cn
X-Mailman-Approved-At: Tue, 07 Dec 2010 08:14:36 -0800
Cc: ccamp@ietf.org
Subject: [CCAMP] A question about RFC5392
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Dec 2010 08:09:43 -0000

This is a multipart message in MIME format.
--=_alternative 002A3221482577F2_=
Content-Type: text/plain; charset="US-ASCII"

Hi Mach, Renhai and Xiaodong

I read the following words in RFC5392: "Only some essential TE information 
for the link needs to be 
advertised; i.e., the Link Type, the Remote AS number, and the Remote ASBR 
ID."

I don't know why only Link Type, Remote AS number, and Remote ASBR ID are 
described in the above sentence? 
Since other parameters are also necessary for CSPF computation, such as 
Metrics, bandwith,etc. 
So, what's the consideration when you're writting this document? Could you 
tell me the reason?

Many thanks!

Best Regards,
Xuerong Wang

 

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

--=_alternative 002A3221482577F2_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="@Fixedsys">Hi Mach, Renhai and Xiaodong<br>
<br>
I read the following words in RFC5392: &quot;Only some essential TE information
for the link needs to be </font>
<br><font size=2 face="@Fixedsys">advertised; i.e., the Link Type, the
Remote AS number, and the Remote ASBR ID.&quot;</font>
<br>
<br><font size=2 face="@Fixedsys">I don't know why only Link Type, Remote
AS number, and Remote ASBR ID are described in the above sentence? </font>
<br><font size=2 face="@Fixedsys">Since other parameters are also necessary
for CSPF computation, such as Metrics, bandwith,etc. </font>
<br><font size=2 face="@Fixedsys">So, what's the consideration when you're
writting this document? Could you tell me the reason?</font>
<br>
<br><font size=2 face="@Fixedsys">Many thanks!<br>
<br>
Best Regards,<br>
Xuerong Wang</font><tt><font size=2><br>
</font></tt><tt><font size=3><br>
</font></tt><font size=3> </font><br><pre>
--------------------------------------------------------
ZTE&nbsp;Information&nbsp;Security&nbsp;Notice:&nbsp;The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;mail&nbsp;is&nbsp;solely&nbsp;property&nbsp;of&nbsp;the&nbsp;sender's&nbsp;organization.&nbsp;This&nbsp;mail&nbsp;communication&nbsp;is&nbsp;confidential.&nbsp;Recipients&nbsp;named&nbsp;above&nbsp;are&nbsp;obligated&nbsp;to&nbsp;maintain&nbsp;secrecy&nbsp;and&nbsp;are&nbsp;not&nbsp;permitted&nbsp;to&nbsp;disclose&nbsp;the&nbsp;contents&nbsp;of&nbsp;this&nbsp;communication&nbsp;to&nbsp;others.
This&nbsp;email&nbsp;and&nbsp;any&nbsp;files&nbsp;transmitted&nbsp;with&nbsp;it&nbsp;are&nbsp;confidential&nbsp;and&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or&nbsp;entity&nbsp;to&nbsp;whom&nbsp;they&nbsp;are&nbsp;addressed.&nbsp;If&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;email&nbsp;in&nbsp;error&nbsp;please&nbsp;notify&nbsp;the&nbsp;originator&nbsp;of&nbsp;the&nbsp;message.&nbsp;Any&nbsp;views&nbsp;expressed&nbsp;in&nbsp;this&nbsp;message&nbsp;are&nbsp;those&nbsp;of&nbsp;the&nbsp;individual&nbsp;sender.
This&nbsp;message&nbsp;has&nbsp;been&nbsp;scanned&nbsp;for&nbsp;viruses&nbsp;and&nbsp;Spam&nbsp;by&nbsp;ZTE&nbsp;Anti-Spam&nbsp;system.
</pre>
--=_alternative 002A3221482577F2_=--


From zhang.fei3@zte.com.cn  Wed Dec  8 19:20:07 2010
Return-Path: <zhang.fei3@zte.com.cn>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 28B203A6893; Wed,  8 Dec 2010 19:20:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.087
X-Spam-Level: 
X-Spam-Status: No, score=-99.087 tagged_above=-999 required=5 tests=[AWL=2.752, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4EkyqFENFWoG; Wed,  8 Dec 2010 19:20:05 -0800 (PST)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 1AC643A69B4; Wed,  8 Dec 2010 19:20:04 -0800 (PST)
Received: from [10.34.0.130] by mx5.zte.com.cn with surfront esmtp id 35102043691617; Thu, 9 Dec 2010 11:19:21 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.16] with StormMail ESMTP id 46413.3679150617; Thu, 9 Dec 2010 11:16:11 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id oB93LFc1013385; Thu, 9 Dec 2010 11:21:15 +0800 (CST) (envelope-from zhang.fei3@zte.com.cn)
To: CCAMP <ccamp@ietf.org>, MPLS-TP <mpls-tp@ietf.org>, mpls@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF22F41156.8029053B-ON482577F4.000F53C3-482577F4.0012AED8@zte.com.cn>
From: zhang.fei3@zte.com.cn
Date: Thu, 9 Dec 2010 11:21:08 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2010-12-09 11:21:06, Serialize complete at 2010-12-09 11:21:06
Content-Type: multipart/alternative; boundary="=_alternative 0012AED4482577F4_="
X-MAIL: mse2.zte.com.cn oB93LFc1013385
Cc: jingrq@ctbri.com.cn, yang.fan5@zte.com.cn
Subject: [CCAMP] [ccamp][mpls-tp][mpls] draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-02
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Dec 2010 03:20:07 -0000

This is a multipart message in MIME format.
--=_alternative 0012AED4482577F4_=
Content-Type: text/plain; charset="US-ASCII"

Hi all,

According to the discussions at IETF79 in Beijing, we have updated and 
posted the rev-02 of the document about the associated bidirectional LSP. 

(1)Add one section to address the provisioning model, divided into single 
sided provisioning and double sided provisioning.

(2)Add one section to address the recovery scenarios of associated 
bidirectional LSPs.

(3)Adjust the sequence of the document, and put the extensions to the 
object at the end.

The authors would like to seek more feedback from the mailing list, 
especially about the provisioning model, and would be grateful if you 
could review the document and post comments on the mailing list.
 
Thanks,

The authors

-----Original Message-----

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

                 Title           : RSVP-TE Extensions to Establish 
Associated Bidirectional LSP
                 Author(s)       : F. Zhang, et al.
                 Filename        : 
draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-02.txt
                 Pages           : 10
                 Date            : 2010-12-07

This document provides a method to bind two unidirectional LSPs into
an associated bidirectional LSP, by extending the Extended
ASSOCIATION object defined in [I-D.ietf-ccamp-assoc-info].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-02.txt


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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://anonymous@ftp.ietf.org/internet-drafts/draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-02.txt
_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--=_alternative 0012AED4482577F4_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=3>Hi all,</font>
<br>
<br><font size=3>According to the discussions at IETF79 in Beijing, we
have updated and posted the rev-02 of the document about the associated
bidirectional LSP. </font>
<br>
<br><font size=3>(1)Add one section to address the provisioning model,
divided into single sided provisioning and double sided provisioning.</font>
<br>
<br><font size=3>(2)Add one section to address the recovery scenarios of
associated bidirectional LSPs.</font>
<br>
<br><font size=3>(3)Adjust the sequence of the document, and put the extensions
to the object at the end.</font>
<br><font size=3><br>
The authors would like to seek more feedback from the mailing list, especially
about the provisioning model, and would be grateful if you could review
the document and post comments on the mailing list.<br>
 <br>
Thanks,<br>
<br>
The authors</font>
<br>
<br><font size=2><tt>-----Original Message-----</tt></font>
<br>
<br><font size=2><tt>A New Internet-Draft is available from the on-line
Internet-Drafts directories.<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
Title &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : RSVP-TE Extensions to Establish
Associated Bidirectional LSP<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
Author(s) &nbsp; &nbsp; &nbsp; : F. Zhang, et al.<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
Filename &nbsp; &nbsp; &nbsp; &nbsp;: draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-02.txt<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
Pages &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 10<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
Date &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 2010-12-07<br>
<br>
This document provides a method to bind two unidirectional LSPs into<br>
an associated bidirectional LSP, by extending the Extended<br>
ASSOCIATION object defined in [I-D.ietf-ccamp-assoc-info].<br>
<br>
A URL for this Internet-Draft is:<br>
http://www.ietf.org/internet-drafts/draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-02.txt<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
ftp://ftp.ietf.org/internet-drafts/<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>
</tt></font><font size=2 face="sans-serif">ftp://anonymous@ftp.ietf.org/internet-drafts/draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-02.txt</font><font size=2><tt>_______________________________________________<br>
I-D-Announce mailing list<br>
I-D-Announce@ietf.org<br>
https://www.ietf.org/mailman/listinfo/i-d-announce<br>
Internet-Draft directories: http://www.ietf.org/shadow.html<br>
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt<br>
</tt></font>
--=_alternative 0012AED4482577F4_=--


From Internet-Drafts@ietf.org  Wed Dec  8 23:00:07 2010
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED9DB3A6A2A; Wed,  8 Dec 2010 23:00:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.38
X-Spam-Level: 
X-Spam-Status: No, score=-102.38 tagged_above=-999 required=5 tests=[AWL=0.219, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xv4-6Kxh-C1w; Wed,  8 Dec 2010 23:00:05 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D9CFB3A6A0F; Wed,  8 Dec 2010 23:00:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20101209070004.26565.81905.idtracker@localhost>
Date: Wed, 08 Dec 2010 23:00:04 -0800
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-gmpls-g-694-lambda-labels-09.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Dec 2010 07:00:07 -0000

--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           : Generalized Labels for Lambda-Switching Capable Label Switching Routers
	Author(s)       : T. Otani, et al.
	Filename        : draft-ietf-ccamp-gmpls-g-694-lambda-labels-09.txt
	Pages           : 14
	Date            : 2010-12-08

Technology in the optical domain is constantly evolving and as a 
consequence new equipment providing lambda switching capability has 
been developed and is currently being deployed. [RFC3471] has 
defined that a wavelength label (section 3.2.1.1) "only has 
significance between two neighbors" and global wavelength semantics 
is not considered. In order to facilitate interoperability in a 
network composed of next generation lambda switch-capable equipment, 
this document defines a standard lambda label format, which is 
compliant with both [G.694.1](DWDM-grid) or [G.694.2](CWDM-grid).  
This document is a companion to the Generalized Multi-Protocol Label 
Switching (GMPLS) signaling. It defines the label format when Lambda 
Switching is requested in an all optical network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-g-694-lambda-labels-09.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-gmpls-g-694-lambda-labels-09.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-12-08225310.I-D@ietf.org>


--NextPart--

From danli@huawei.com  Wed Dec  8 23:15:18 2010
Return-Path: <danli@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2AF9428C0CF for <ccamp@core3.amsl.com>; Wed,  8 Dec 2010 23:15:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level: 
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lTyRaaAL5seW for <ccamp@core3.amsl.com>; Wed,  8 Dec 2010 23:15:09 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 0BCE73A6A5A for <ccamp@ietf.org>; Wed,  8 Dec 2010 23:14:07 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LD500CUAG5G2M@szxga04-in.huawei.com> for ccamp@ietf.org; Thu, 09 Dec 2010 15:15:16 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LD500H9YG5GPI@szxga04-in.huawei.com> for ccamp@ietf.org; Thu, 09 Dec 2010 15:15:16 +0800 (CST)
Received: from l00037133 ([10.70.77.77]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LD500KADG5F08@szxml04-in.huawei.com> for ccamp@ietf.org; Thu, 09 Dec 2010 15:15:16 +0800 (CST)
Date: Thu, 09 Dec 2010 15:15:14 +0800
From: Dan Li <danli@huawei.com>
To: ccamp@ietf.org
Message-id: <00f301cb9770$d3611f40$4d4d460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
Content-type: multipart/mixed; boundary="Boundary_(ID_KIPPgM+VZ6kpPSsu4xeHNA)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [CCAMP] Fw: I-D Action:draft-ietf-ccamp-gmpls-g-694-lambda-labels-09.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Dec 2010 07:15:19 -0000

This is a multi-part message in MIME format.

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

Hi all,

We just updated the g.694-lambda draft only with several editorial changes. If you compare with the previous version (08), you can find out the changes.

Thanks,

Dan


----- Original Message ----- 
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Cc: <ccamp@ietf.org>
Sent: Thursday, December 09, 2010 3:00 PM
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-gmpls-g-694-lambda-labels-09.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           : Generalized Labels for Lambda-Switching Capable Label Switching Routers
> Author(s)       : T. Otani, et al.
> Filename        : draft-ietf-ccamp-gmpls-g-694-lambda-labels-09.txt
> Pages           : 14
> Date            : 2010-12-08
> 
> Technology in the optical domain is constantly evolving and as a 
> consequence new equipment providing lambda switching capability has 
> been developed and is currently being deployed. [RFC3471] has 
> defined that a wavelength label (section 3.2.1.1) "only has 
> significance between two neighbors" and global wavelength semantics 
> is not considered. In order to facilitate interoperability in a 
> network composed of next generation lambda switch-capable equipment, 
> this document defines a standard lambda label format, which is 
> compliant with both [G.694.1](DWDM-grid) or [G.694.2](CWDM-grid).  
> This document is a companion to the Generalized Multi-Protocol Label 
> Switching (GMPLS) signaling. It defines the label format when Lambda 
> Switching is requested in an all optical network.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-g-694-lambda-labels-09.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>


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


> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>

--Boundary_(ID_KIPPgM+VZ6kpPSsu4xeHNA)
Content-type: text/plain; name=draft-ietf-ccamp-gmpls-g-694-lambda-labels-09.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment;
 filename=draft-ietf-ccamp-gmpls-g-694-lambda-labels-09.txt

Content-Type: text/plain
Content-ID: <2010-12-08225310.I-D@ietf.org>


--Boundary_(ID_KIPPgM+VZ6kpPSsu4xeHNA)--

From lberger@labn.net  Thu Dec  9 08:34:37 2010
Return-Path: <lberger@labn.net>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 399F728C118 for <ccamp@core3.amsl.com>; Thu,  9 Dec 2010 08:34:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.024
X-Spam-Level: 
X-Spam-Status: No, score=-102.024 tagged_above=-999 required=5 tests=[AWL=0.241, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BzHSd586t1q6 for <ccamp@core3.amsl.com>; Thu,  9 Dec 2010 08:34:32 -0800 (PST)
Received: from oproxy3-pub.bluehost.com (oproxy3-pub.bluehost.com [69.89.21.8]) by core3.amsl.com (Postfix) with SMTP id 5E4AF28C0DC for <ccamp@ietf.org>; Thu,  9 Dec 2010 08:34:32 -0800 (PST)
Received: (qmail 14949 invoked by uid 0); 9 Dec 2010 16:35:58 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy3.bluehost.com with SMTP; 9 Dec 2010 16:35:58 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=d8uxrO1f0AlIxwkYUT284VG8eUqNl6jD1yrTWtLuD+EICvVeUP6meNhmftT3PPH8KffsbMJR3obADucLCBcQI7p42BnSXXAn3YPx9JkvBrRsN7DsFroSxb2nKrRv1R8m;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1PQjTK-0001It-5J; Thu, 09 Dec 2010 09:35:58 -0700
Message-ID: <4D010576.1010904@labn.net>
Date: Thu, 09 Dec 2010 11:36:06 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: CCAMP ADs <ccamp-ads@tools.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: CCAMP <ccamp@ietf.org>, The IESG Secretary <iesg-secretary@ietf.org>
Subject: [CCAMP] Please publish: draft-ietf-ccamp-gmpls-g-694-lambda-labels-09.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Dec 2010 16:34:37 -0000

Adrian,
	Here is the PROTO write up for 
draft-ietf-ccamp-gmpls-g-694-lambda-labels-09.txt.

Lou (and Deborah)
==========================================================================
PROTO-write-up for:	draft-ietf-ccamp-gmpls-g-694-lambda-labels
Intended status: 	Proposed Standard

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

Lou Berger is the Document Shepherd.
He has reviewed the document and believes it is ready for forwarding to
the IESG for publication.

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

Yes.  The document has been extensively reviewed and the Shepherd
believes all issues have been addressed.

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

No concerns or additional review needed.

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

No concerns or issues.  No IPR found in the datatracker.

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

There is strong consensus behind this document.

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

No.

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

Yes.  There is one instance of a line too long, this can be fixed as
part of the publication process.  No other reviews are required.

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

Split looks good.

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

No IANA implications.

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

Yes, no automated checks needed.

   (1.k) The IESG approval announcement includes a Document
         Announcement Write-Up. Please provide such a Document
         Announcement Write-Up? Recent examples can be found in the
         "Action" announcements for approved documents. The approval
         announcement contains the following sections:

      Technical Summary
         Relevant content can frequently be found in the abstract
         and/or introduction of the document. If not, this may be
         an indication that there are deficiencies in the abstract
         or introduction.

This document is a companion to the Generalized Multi-Protocol Label
Switching (GMPLS) signaling.  [RFC3471] defined that a wavelength label
(section 3.2.1.1) "only has significance between two neighbors" and
global wavelength semantics is not considered. In order to facilitate
interoperability in a network composed of lambda switch-capable
equipment, this document defines a standard lambda label format, which
is compliant with both [G.694.1](DWDM-grid) and [G.694.2](CWDM-grid).

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

This document received much attention and discussion in its early
revisions.  The document has been largely stable for quite some time,
mainly needing revisions as part of the publication process.

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

There have been no public statements related to intent to implement, but
the portions of the extensions are now being used as part of the GMPLS
tool set and are expected to implemented (at least) in those contexts.

From Adrian.Farrel@huawei.com  Thu Dec  9 13:45:45 2010
Return-Path: <Adrian.Farrel@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A59128C113 for <ccamp@core3.amsl.com>; Thu,  9 Dec 2010 13:45:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.424
X-Spam-Level: 
X-Spam-Status: No, score=-103.424 tagged_above=-999 required=5 tests=[AWL=-0.825, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eE4prTX8E9fQ for <ccamp@core3.amsl.com>; Thu,  9 Dec 2010 13:45:44 -0800 (PST)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 46B603A6818 for <ccamp@ietf.org>; Thu,  9 Dec 2010 13:45:44 -0800 (PST)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LD600KBLKIP02@usaga01-in.huawei.com> for ccamp@ietf.org; Thu, 09 Dec 2010 13:47:13 -0800 (PST)
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LD600DEPKIHLD@usaga01-in.huawei.com> for ccamp@ietf.org; Thu, 09 Dec 2010 13:47:13 -0800 (PST)
Date: Thu, 09 Dec 2010 21:47:04 +0000
From: Adrian Farrel <Adrian.Farrel@huawei.com>
To: danli@huawei.com, tm-otani@kddi.com, rabbat@alum.mit.edu, sidney.shiba@yahoo.com, hongxiang.guo@gmail.com, miyazaki.keiji@jp.fujitsu.com, diego.caviglia@ericsson.com, tsuri@kddilabs.jp
Message-id: <06ea01cb97ea$a3b57230$eb205690$@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 14.0
Content-type: text/plain; charset=us-ascii
Content-language: en-gb
Content-transfer-encoding: 7BIT
Thread-index: AcuX6n+MNNbZM5IIR9SmyV2wqTy1aw==
Cc: ccamp@ietf.org, ccamp-chairs@tools.ietf.org
Subject: [CCAMP] AD review of draft-ietf-ccamp-gmpls-g-694-lambda-labels-09
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian.Farrel@huawei.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Dec 2010 21:45:45 -0000

Hi,

I have performed an AD review of your draft.

Don't panic!

I review all drafts that I am responsible for before putting them
forward for IETF last call. The main objective is to catch nits and
minor issues that would show up during the last call or in IESG
review. The intention is to help polish your document and make sure
it is clean and shiny so that other reviewers will stick to the
technical details.

I think your small draft is actually a very significant contribution to
the GMPLS family.

Most of my comments are pretty trivial, but a couple have more meat
on them and I'd like to see a quick respin of the document before I
issue the IETF last call. As soon as I see a new revision posted,
I'll set the ball in motion.

Of course, all of my issues are up for discussion.

Thanks for the work,
Adrian

---

idnits throws up a number of minor issues...

> ** There is 1 instance of too long lines in the document, the longest
>    one being 1 character in excess of 72.

This seems to be line 46

> == The 'Updates: ' line in the draft header should list only the
>    _numbers_ of the RFCs which will be updated by this document (if
>    approved); it should not include the word 'RFC' in the list.

This is in the document header...

s/Updates: RFC3471/Updates: 3471 (if approved)/

> == The document seems to lack a disclaimer for pre-RFC5378 work, but
>    was first submitted before 10 November 2008.  Should you add the 
>    disclaimer? (See the Legal Provisions document at
>    http://trustee.ietf.org/license-info for more information.) 
>    -- however, there's a paragraph with a matching beginning. 
>    Boilerplate error?

Just need to check with you that the authors are happy to not include
the boilerplate and are assigning the copyright. Usually not a problem,     
but if you have trouble tracking down the authors, just add the 
disclaimer boilerplate - it is quite safe!

> == Unused Reference: 'RFC3209' is defined on line 433, but no 
>    explicit reference was found in the text

You can just remove the reference.

---

The Abstract needs to be self-contained, so cannot include citations of
RFCs or other documents.

You also need to spell out acronyms.

Can I suggest:

OLD
   Technology in the optical domain is constantly evolving and as a 
   consequence new equipment providing lambda switching capability has 
   been developed and is currently being deployed. [RFC3471] has 
   defined that a wavelength label (section 3.2.1.1) "only has 
   significance between two neighbors" and global wavelength semantics 
   is not considered. In order to facilitate interoperability in a 
   network composed of next generation lambda switch-capable equipment, 
   this document defines a standard lambda label format, which is 
   compliant with both [G.694.1](DWDM-grid) or [G.694.2](CWDM-grid).  
   This document is a companion to the Generalized Multi-Protocol Label 
   Switching (GMPLS) signaling. It defines the label format when Lambda 
   Switching is requested in an all optical network. 
NEW                       
   Technology in the optical domain is constantly evolving and as a 
   consequence new equipment providing lambda switching capability has 
   been developed and is currently being deployed. 
   
   Generalized MPLS (GMPLS) is a family of protocols that can be used 
   to operate networks built from a range of technologies including
   wavelength (or lambda) switching. For this purpose, GMPLS defined
   that a wavelength label only has significance between two neighbors 
   and global wavelength semantics are not considered.
   
   In order to facilitate interoperability in a network composed of next
   generation lambda switch-capable equipment, this document defines a
   standard lambda label format that is compliant with Dense Wavelength
   Division Multiplexing and Coarse Wavelength Division Multiplexing 
   grids defined by the International Telecommunication Union
   Telecommunication Standardization Sector. The label format defined in
   this document can be used in GMPLS signaling and routing protocols.
END

---

You are not required to include a Table of Contents in a document of less
than fifteen pages (but you are allowed to).

---

Section 1

You need to expand DWDM and CWDM on first use.
You can then remove the expansions from Section 2.

---

Section 2

Could you capitalise the section header to match the others.
 

---

Section 2

s/vendor's/vendors'/
s/consists of number/consists of a number/

---

Section 2

s/a LSP/an LSP/

---

Section 2 (last line)

Expand "LSR" on first use.

---                                                                

Section 3.3

   We do not need to define a new type as the information stored is 
   either a port label or a wavelength label. Only the wavelength label 
   as above needs to be defined. 

This is very true, but I think the text does not belong here.
I would try to work it into Section 3.1

---
 

Section 4

   This document introduces no new security considerations to [RFC3473]. 
   For a general discussion on MPLS and GMPLS related security issues, 
   see the MPLS/GMPLS security framework [RFC5920]. 

I think you should 
s/[RFC3473]/[RFC3471] and [RFC3473]/
because this I-D updates 3471.
                                                         
---

Section 5

Why did you decide that there is no requirement for IANA to track the
codepoints (Grid and C.S.) used in the DWDM and CWDM Wavelength Labels? 

It looks like you could have three registries {Grid, DWDM C.S., and 
CWDM C.S.)

---

Section 8

OLD
8. Author's Address
NEW
8. Authors' Addresses
END


From Adrian.Farrel@huawei.com  Fri Dec 10 13:58:50 2010
Return-Path: <Adrian.Farrel@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D725028C133 for <ccamp@core3.amsl.com>; Fri, 10 Dec 2010 13:58:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.365
X-Spam-Level: 
X-Spam-Status: No, score=-103.365 tagged_above=-999 required=5 tests=[AWL=-0.766, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EONT5liuOkgb for <ccamp@core3.amsl.com>; Fri, 10 Dec 2010 13:58:50 -0800 (PST)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 350173A6988 for <ccamp@ietf.org>; Fri, 10 Dec 2010 13:58:50 -0800 (PST)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LD8005MTFSLM0@usaga01-in.huawei.com> for ccamp@ietf.org; Fri, 10 Dec 2010 14:00:21 -0800 (PST)
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LD8005JUFSJB8@usaga01-in.huawei.com> for ccamp@ietf.org; Fri, 10 Dec 2010 14:00:21 -0800 (PST)
Date: Fri, 10 Dec 2010 22:00:19 +0000
From: Adrian Farrel <Adrian.Farrel@huawei.com>
To: draft-ietf-ccamp-assoc-info@tools.ietf.org
Message-id: <01b201cb98b5$a40cb5b0$ec262110$@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 14.0
Content-type: text/plain; charset=us-ascii
Content-language: en-gb
Content-transfer-encoding: 7BIT
Thread-index: AcuYtZ+3TfKDcI7GT1KPOQm6t0xe5g==
Cc: ccamp@ietf.org
Subject: [CCAMP] Question on Extended Association I-D
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian.Farrel@huawei.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Dec 2010 21:58:50 -0000

Hi,

Can you tell me, how many associations do you think you actually need?
Certainly 2**48 should be enough.
And, you are making the claim that 2**16 is too few (although I wonder how many
deployments have used more than 2**8 associations).

I'm wondering whether 2**20 or 2**24 might be enough.

If it was, then there is no need to extend the Association object because there
are plenty of Association type values available. 

Cheers,
Adrian




From lberger@labn.net  Fri Dec 10 14:40:51 2010
Return-Path: <lberger@labn.net>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C76E28C0F3 for <ccamp@core3.amsl.com>; Fri, 10 Dec 2010 14:40:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.043
X-Spam-Level: 
X-Spam-Status: No, score=-102.043 tagged_above=-999 required=5 tests=[AWL=0.222, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zepEBmK-Zt5x for <ccamp@core3.amsl.com>; Fri, 10 Dec 2010 14:40:48 -0800 (PST)
Received: from cpoproxy1-pub.bluehost.com (cpoproxy1-pub.bluehost.com [69.89.21.11]) by core3.amsl.com (Postfix) with SMTP id 9BE6F3A6CC6 for <ccamp@ietf.org>; Fri, 10 Dec 2010 14:40:48 -0800 (PST)
Received: (qmail 6449 invoked by uid 0); 10 Dec 2010 22:42:20 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy1.bluehost.com with SMTP; 10 Dec 2010 22:42:20 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=gHMzhYs6NofLQFnqXJyxhxEPlqhIakmo2kUGfJc2srsYKr52fmdpi2jwmScgLImdI2sR8gTqNpPHBD055/NMVZs8F5KMS/LbrAXrhqBGMIZujheQ0EgZIzscJFPqRZe5;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1PRBfQ-0000FJ-1I; Fri, 10 Dec 2010 15:42:20 -0700
Message-ID: <4D02ACD6.7010606@labn.net>
Date: Fri, 10 Dec 2010 17:42:30 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Adrian.Farrel@huawei.com
References: <01b201cb98b5$a40cb5b0$ec262110$@huawei.com>
In-Reply-To: <01b201cb98b5$a40cb5b0$ec262110$@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: ccamp@ietf.org, draft-ietf-ccamp-assoc-info@tools.ietf.org
Subject: Re: [CCAMP] Question on Extended Association I-D
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Dec 2010 22:40:51 -0000

Hi Adrian,
	We have two requirements driving changing/extending the association 
object.  The first is not covered in the current rev of the document, 
but was in the slides presented in Beijing, is to support the IP 
identifiers document and TP Global identifiers in particular.

The second is to support a more centralized model for the determination 
of associations.  In such a centralized case, a very large number of 
associations are possible.  Francois and Ashok are the advocates for 
this.  Some of their original motivation can be found in 
draft-narayanan-tsvwg-rsvp-resource-sharing-01.  They'll need to field 
any follow-ups on this requirement.

Lou (as co-author)

On 12/10/2010 5:00 PM, Adrian Farrel wrote:
> Hi,
>
> Can you tell me, how many associations do you think you actually need?
> Certainly 2**48 should be enough.
> And, you are making the claim that 2**16 is too few (although I wonder how many
> deployments have used more than 2**8 associations).
>
> I'm wondering whether 2**20 or 2**24 might be enough.
>
> If it was, then there is no need to extend the Association object because there
> are plenty of Association type values available.
>
> Cheers,
> Adrian
>
>
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>
>
>
>

From zhang.fei3@zte.com.cn  Sun Dec 12 17:23:00 2010
Return-Path: <zhang.fei3@zte.com.cn>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34CF83A6D53; Sun, 12 Dec 2010 17:23:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.535
X-Spam-Level: 
X-Spam-Status: No, score=-97.535 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F7Ac+XENq6XS; Sun, 12 Dec 2010 17:22:59 -0800 (PST)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 68C303A6D4E; Sun, 12 Dec 2010 17:22:57 -0800 (PST)
Received: from [10.34.0.130] by mx5.zte.com.cn with surfront esmtp id 35101578366850; Mon, 13 Dec 2010 09:22:24 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.15] with StormMail ESMTP id 55813.2477328926; Mon, 13 Dec 2010 09:24:29 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id oBD1O3Vq019187; Mon, 13 Dec 2010 09:24:09 +0800 (CST) (envelope-from zhang.fei3@zte.com.cn)
In-Reply-To: <01b701cb98b7$29e67f80$7db37e80$@olddog.co.uk>
To: adrian@olddog.co.uk
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OFD73E832E.B6F4BCC2-ON482577F8.00039DD3-482577F8.0007FAB7@zte.com.cn>
From: zhang.fei3@zte.com.cn
Date: Mon, 13 Dec 2010 09:24:08 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2010-12-13 09:24:03, Serialize complete at 2010-12-13 09:24:03
Content-Type: multipart/alternative; boundary="=_alternative 0007FAB4482577F8_="
X-MAIL: mse2.zte.com.cn oBD1O3Vq019187
Cc: ccamp@ietf.org, mpls-tp-bounces@ietf.org, draft-zhang-mpls-tp-rsvpte-ext-associated-lsp@tools.ietf.prg, mpls-tp@ietf.org
Subject: Re: [CCAMP] [mpls-tp] Questions about draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-02
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Dec 2010 01:23:00 -0000

This is a multipart message in MIME format.
--=_alternative 0007FAB4482577F8_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

SGkgQWRyaWFuDQoNClNlZSBpbiBsaW5lDQoNClRoYW5rcw0KOikNCkZlaSAoYXMgY28tYXV0aG9y
KQ0KDQoNCg0KIkFkcmlhbiBGYXJyZWwiIDxhZHJpYW5Ab2xkZG9nLmNvLnVrPiANCreivP7Iyzog
IG1wbHMtdHAtYm91bmNlc0BpZXRmLm9yZw0KMjAxMC0xMi0xMSAwNjoxMQ0Kx+u08Li0ILj4DQph
ZHJpYW5Ab2xkZG9nLmNvLnVrDQoNCg0KytW8/sjLDQo8ZHJhZnQtemhhbmctbXBscy10cC1yc3Zw
dGUtZXh0LWFzc29jaWF0ZWQtbHNwQHRvb2xzLmlldGYucHJnPg0Ks63LzQ0KbXBscy10cEBpZXRm
Lm9yZw0K1vfM4g0KW21wbHMtdHBdIFF1ZXN0aW9ucyBhYm91dCBkcmFmdC16aGFuZy1tcGxzLXRw
LXJzdnB0ZS1leHQtYXNzb2NpYXRlZC1sc3AtMDINCg0KDQoNCg0KDQoNCkhpLA0KDQpJIGhhdmUg
YSBmZXcgcXVlc3Rpb25zIGFib3V0IA0KZHJhZnQtemhhbmctbXBscy10cC1yc3ZwdGUtZXh0LWFz
c29jaWF0ZWQtbHNwLTAyDQoNCjEuIFdoeSBoYXZlbid0IHlvdSB0YXJnZXRlZCB0aGlzIHF1ZXN0
aW9uIGF0IHRoZSBDQ0FNUCB3b3JraW5nIGdyb3VwPw0KDQpbRmVpXSBBY3R1YWxseSwgSSBoYXZl
IHB1dCB0aGVtIGJvdGggaW4gQ0NBTVAgYW5kIE1QTFMtVFAgd29ya2luZyBncm91cC4NCg0KMi4g
QXJlIHlvdSBvbmx5IGV4dGVuZGluZyB0aGUgRXh0ZW5kZWQgQXNzb2NpYXRpb24gb2JqZWN0Pw0K
T3Igd2lsbCB5b3UgYWxzbyBleHRlbmQgdGhlIEFzc29jaWF0aW9uIG9iamVjdD8NCkluIFNlY3Rp
b24gMSB5b3UgaGF2ZToNCiAgIFRoaXMgZG9jdW1lbnQgZXh0ZW5kcyB0aGUgRXh0ZW5kZWQgQVNT
T0NJQVRJT04gb2JqZWN0IHRvIGVzdGFibGlzaA0KICAgYXNzb2NpYXRlZCBiaWRpcmVjdGlvbmFs
IExTUHMuDQpJIHRoaW5rIHRoZSByZWdpc3RyeSBvZiBBc3NvY2lhdGlvbiBUeXBlcyB3aWxsIGFw
cGx5IGVxdWFsbHkgdG8gYm90aCANCm9iamVjdHMuDQoNCltGZWldIFllYWgsIHRoZSBBc3NvY2lh
dGlvbiB0eXBlcyBhcHBseSB0byBib3RoIG9iamVjdHMsIGJ1dCBJIG5lZWQgdG8gcHV0IA0KVHVu
bmVsIElEIGFuZCBMU1AgSUQgaW50byB0aGUgQXNzb2NpYXRpb24gSUQgZmllbGQgKFRQJ3MgaWRl
bnRpZmllciANCnJlcXVpcmVtZW50cykuDQogT2J2aW91c2x5IEFTU09DSUFUSU9OIG9iamVjdCBj
YW4gbm90IG1lZXQgdGhpcyByZXF1aXJlbWVudHMgZm9yIHRoZXJlIGFyZSANCm9ubHkgMTYgYml0
cyBpbiB0aGUgZmllbGQgb2YgQXNzb2NpYXRpb24gSUQuIEZ1cnRoZXJtb3JlLCBpdCB3aWxsIGJl
IGdyZWF0IA0KaWYgR2xvYmFsX05vZGVfSUQgY2FuDQpiZSBjb25zaWRlcmVkIHRvIGJlIHB1dCBp
bnRvIHRoZSBmaWVsZCBvZiBBc3NvY2lhdGlvbiBTb3VyY2Ugb3IgDQpBc3NvY2lhdGlvbiBJRC4N
CkJ5IHRoZSB3YXksIHRoZSBmb3JtYXQgb2YgTVBMUy1UUCBMU1AgSWRlbnRpZmllcnMgaXMgDQpT
cmMtR2xvYmFsX05vZGVfSUQ6OlNyYy1UdW5uZWxfTnVtOjpEc3QtR2xvYmFsX05vZGVfSUQ6OkRz
dC1UdW5uZWxfTnVtOjpMU1BfTnVtDQoNCg0KMy4gV2hhdCBpcyB0aGUgdmFsdWUgb2YgcmVkZWZp
bmluZyB0aGUgRXh0ZW5kZWQgQXNzb2NpYXRpb24gb2JqZWN0Pw0KSSB0aGluayBpdCBpcyBlbm91
Z2ggZm9yIHlvdSB0byByZWZlcmVuY2UgdGhlIEktRCB0aGF0IGNvbnRhaW5zIHRoZSANCmRlZmlu
aXRpb24uDQoNCltGZWldIFNvcnJ5IGZvciB0aGUgdW5jbGVhciBkZXNjcmlwdGlvbnMgaW4gdGhl
IGRvY3VtZW50LCB3aGF0IEkgd2FudCB0byANCmRvIGlzIG9ubHkgdG8gZGVmaW5lIGEgbmV3IEFz
c29pY2F0aW9uIHR5cGUgaW4gdGhlIHNjb3BlIG9mIHRoZSBFeHRlbmRlZCANCkFzc29jaWF0aW9u
IG9iamVjdC4NCg0KVGhhbmtzLA0KQWRyaWFuDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQptcGxzLXRwIG1haWxpbmcgbGlzdA0KbXBscy10cEBpZXRm
Lm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxzLXRwDQoNCg0K
DQo=
--=_alternative 0007FAB4482577F8_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpIEFkcmlhbjwvZm9udD4NCjxi
cj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+U2VlIGluIGxpbmU8L2ZvbnQ+
DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlRoYW5rczwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Oik8L2ZvbnQ+DQo8YnI+PGZvbnQg
c2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkZlaSAoYXMgY28tYXV0aG9yKTwvZm9udD4NCjxicj4N
Cjxicj4NCjxicj4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQgd2lk
dGg9MzUlPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj48Yj4mcXVvdDtBZHJpYW4gRmFy
cmVsJnF1b3Q7DQombHQ7YWRyaWFuQG9sZGRvZy5jby51ayZndDs8L2I+IDwvZm9udD4NCjxicj48
Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+t6K8/sjLOiAmbmJzcDttcGxzLXRwLWJvdW5j
ZXNAaWV0Zi5vcmc8L2ZvbnQ+DQo8cD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+MjAx
MC0xMi0xMSAwNjoxMTwvZm9udD4NCjx0YWJsZSBib3JkZXI+DQo8dHIgdmFsaWduPXRvcD4NCjx0
ZCBiZ2NvbG9yPXdoaXRlPg0KPGRpdiBhbGlnbj1jZW50ZXI+PGZvbnQgc2l6ZT0xIGZhY2U9InNh
bnMtc2VyaWYiPsfrtPC4tCC4+Dxicj4NCmFkcmlhbkBvbGRkb2cuY28udWs8L2ZvbnQ+PC9kaXY+
PC90YWJsZT4NCjxicj4NCjx0ZCB3aWR0aD02NCU+DQo8dGFibGUgd2lkdGg9MTAwJT4NCjx0ciB2
YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fu
cy1zZXJpZiI+ytW8/sjLPC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9MSBmYWNlPSJzYW5z
LXNlcmlmIj4mbHQ7ZHJhZnQtemhhbmctbXBscy10cC1yc3ZwdGUtZXh0LWFzc29jaWF0ZWQtbHNw
QHRvb2xzLmlldGYucHJnJmd0OzwvZm9udD4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBh
bGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+s63LzTwvZm9udD48L2Rp
dj4NCjx0ZD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+bXBscy10cEBpZXRmLm9yZzwv
Zm9udD4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXpl
PTEgZmFjZT0ic2Fucy1zZXJpZiI+1vfM4jwvZm9udD48L2Rpdj4NCjx0ZD48Zm9udCBzaXplPTEg
ZmFjZT0ic2Fucy1zZXJpZiI+W21wbHMtdHBdIFF1ZXN0aW9ucyBhYm91dCAmbmJzcDsgJm5ic3A7
DQombmJzcDsgJm5ic3A7ZHJhZnQtemhhbmctbXBscy10cC1yc3ZwdGUtZXh0LWFzc29jaWF0ZWQt
bHNwLTAyPC9mb250PjwvdGFibGU+DQo8YnI+DQo8dGFibGU+DQo8dHIgdmFsaWduPXRvcD4NCjx0
ZD4NCjx0ZD48L3RhYmxlPg0KPGJyPjwvdGFibGU+DQo8YnI+DQo8YnI+DQo8YnI+PGZvbnQgc2l6
ZT0yPjx0dD5IaSw8YnI+DQo8YnI+DQpJIGhhdmUgYSBmZXcgcXVlc3Rpb25zIGFib3V0IGRyYWZ0
LXpoYW5nLW1wbHMtdHAtcnN2cHRlLWV4dC1hc3NvY2lhdGVkLWxzcC0wMjxicj4NCjxicj4NCjEu
IFdoeSBoYXZlbid0IHlvdSB0YXJnZXRlZCB0aGlzIHF1ZXN0aW9uIGF0IHRoZSBDQ0FNUCB3b3Jr
aW5nIGdyb3VwPzwvdHQ+PC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj1ibHVl
Pjx0dD5bRmVpXSBBY3R1YWxseSwgSSBoYXZlIHB1dCB0aGVtIGJvdGggaW4NCkNDQU1QIGFuZCBN
UExTLVRQIHdvcmtpbmcgZ3JvdXAuPC90dD48L2ZvbnQ+PGZvbnQgc2l6ZT0yPjx0dD48YnI+DQo8
YnI+DQoyLiBBcmUgeW91IG9ubHkgZXh0ZW5kaW5nIHRoZSBFeHRlbmRlZCBBc3NvY2lhdGlvbiBv
YmplY3Q/PGJyPg0KT3Igd2lsbCB5b3UgYWxzbyBleHRlbmQgdGhlIEFzc29jaWF0aW9uIG9iamVj
dD88YnI+DQpJbiBTZWN0aW9uIDEgeW91IGhhdmU6PGJyPg0KICZuYnNwOyBUaGlzIGRvY3VtZW50
IGV4dGVuZHMgdGhlIEV4dGVuZGVkIEFTU09DSUFUSU9OIG9iamVjdCB0byBlc3RhYmxpc2g8YnI+
DQogJm5ic3A7IGFzc29jaWF0ZWQgYmlkaXJlY3Rpb25hbCBMU1BzLjxicj4NCkkgdGhpbmsgdGhl
IHJlZ2lzdHJ5IG9mIEFzc29jaWF0aW9uIFR5cGVzIHdpbGwgYXBwbHkgZXF1YWxseSB0byBib3Ro
IG9iamVjdHMuPC90dD48L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGNvbG9yPWJsdWU+
PHR0PltGZWldIFllYWgsIHRoZSBBc3NvY2lhdGlvbiB0eXBlcyBhcHBseQ0KdG8gYm90aCBvYmpl
Y3RzLCBidXQgSSBuZWVkIHRvIHB1dCBUdW5uZWwgSUQgYW5kIExTUCBJRCBpbnRvIHRoZSBBc3Nv
Y2lhdGlvbg0KSUQgZmllbGQgKFRQJ3MgaWRlbnRpZmllciByZXF1aXJlbWVudHMpLjwvdHQ+PC9m
b250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj1ibHVlPjx0dD4mbmJzcDtPYnZpb3VzbHkgQVNT
T0NJQVRJT04gb2JqZWN0IGNhbg0Kbm90IG1lZXQgdGhpcyByZXF1aXJlbWVudHMgZm9yIHRoZXJl
IGFyZSBvbmx5IDE2IGJpdHMgaW4gdGhlIGZpZWxkIG9mIEFzc29jaWF0aW9uDQpJRC4gRnVydGhl
cm1vcmUsIGl0IHdpbGwgYmUgZ3JlYXQgaWYgR2xvYmFsX05vZGVfSUQgY2FuPC90dD48L2ZvbnQ+
DQo8YnI+PGZvbnQgc2l6ZT0yIGNvbG9yPWJsdWU+PHR0PmJlIGNvbnNpZGVyZWQgdG8gYmUgcHV0
IGludG8gdGhlIGZpZWxkDQpvZiBBc3NvY2lhdGlvbiBTb3VyY2Ugb3IgQXNzb2NpYXRpb24gSUQu
PC90dD48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGNvbG9yPWJsdWU+PHR0PkJ5IHRoZSB3YXks
IHRoZSBmb3JtYXQgb2YgTVBMUy1UUCBMU1AgSWRlbnRpZmllcnMNCmlzIFNyYy1HbG9iYWxfTm9k
ZV9JRDo6U3JjLVR1bm5lbF9OdW06OkRzdC1HbG9iYWxfTm9kZV9JRDo6RHN0LVR1bm5lbF9OdW06
OkxTUF9OdW08L3R0PjwvZm9udD48Zm9udCBzaXplPTI+PHR0Pjxicj4NCjxicj4NCjMuIFdoYXQg
aXMgdGhlIHZhbHVlIG9mIHJlZGVmaW5pbmcgdGhlIEV4dGVuZGVkIEFzc29jaWF0aW9uIG9iamVj
dD88YnI+DQpJIHRoaW5rIGl0IGlzIGVub3VnaCBmb3IgeW91IHRvIHJlZmVyZW5jZSB0aGUgSS1E
IHRoYXQgY29udGFpbnMgdGhlIGRlZmluaXRpb24uPC90dD48L2ZvbnQ+DQo8YnI+DQo8YnI+PGZv
bnQgc2l6ZT0yIGNvbG9yPWJsdWU+PHR0PltGZWldIFNvcnJ5IGZvciB0aGUgdW5jbGVhciBkZXNj
cmlwdGlvbnMNCmluIHRoZSBkb2N1bWVudCwgd2hhdCBJIHdhbnQgdG8gZG8gaXMgb25seSB0byBk
ZWZpbmUgYSBuZXcgQXNzb2ljYXRpb24NCnR5cGUgaW4gdGhlIHNjb3BlIG9mIHRoZSBFeHRlbmRl
ZCBBc3NvY2lhdGlvbiBvYmplY3QuPC90dD48L2ZvbnQ+PGZvbnQgc2l6ZT0yPjx0dD48YnI+DQo8
YnI+DQpUaGFua3MsPGJyPg0KQWRyaWFuPGJyPg0KPGJyPg0KX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQptcGxzLXRwIG1haWxpbmcgbGlzdDxicj4N
Cm1wbHMtdHBAaWV0Zi5vcmc8YnI+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL21wbHMtdHA8YnI+DQo8YnI+DQo8L3R0PjwvZm9udD4NCjxicj4NCg==
--=_alternative 0007FAB4482577F8_=--


From Internet-Drafts@ietf.org  Sun Dec 12 17:30:02 2010
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ABEB83A6D52; Sun, 12 Dec 2010 17:30:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jaSTXmc+toVD; Sun, 12 Dec 2010 17:30:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A94943A6D4E; Sun, 12 Dec 2010 17:30:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20101213013001.20521.59523.idtracker@localhost>
Date: Sun, 12 Dec 2010 17:30:01 -0800
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-gmpls-g-694-lambda-labels-10.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Dec 2010 01:30:02 -0000

--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           : Generalized Labels for Lambda-Switching Capable Label Switching Routers
	Author(s)       : T. Otani, et al.
	Filename        : draft-ietf-ccamp-gmpls-g-694-lambda-labels-10.txt
	Pages           : 15
	Date            : 2010-12-12

Technology in the optical domain is constantly evolving and as a 
consequence new equipment providing lambda switching capability has 
been developed and is currently being deployed. 

Generalized MPLS (GMPLS) is a family of protocols that can be used

to operate networks built from a range of technologies including

wavelength (or lambda) switching. For this purpose, GMPLS defined

that a wavelength label only has significance between two neighbors

and global wavelength semantics are not considered. 

In order to facilitate interoperability in a network composed of 
next generation lambda switch-capable equipment, this document 
defines a standard lambda label format that is compliant with Dense 
Wavelength Division Multiplexing and Coarse Wavelength Division 
Multiplexing grids defined by the International Telecommunication 
Union Telecommunication Standardization Sector. The label format 
defined in this document can be used in GMPLS signaling and routing 
protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-g-694-lambda-labels-10.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-gmpls-g-694-lambda-labels-10.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-12-12171820.I-D@ietf.org>


--NextPart--

From danli@huawei.com  Sun Dec 12 17:59:59 2010
Return-Path: <danli@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E94943A6D33 for <ccamp@core3.amsl.com>; Sun, 12 Dec 2010 17:59:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.495
X-Spam-Level: 
X-Spam-Status: No, score=-3.495 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id shwy589Ozd+8 for <ccamp@core3.amsl.com>; Sun, 12 Dec 2010 17:59:58 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 20C283A6D93 for <ccamp@ietf.org>; Sun, 12 Dec 2010 17:59:58 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LDC00EOOGAC42@szxga04-in.huawei.com> for ccamp@ietf.org; Mon, 13 Dec 2010 10:01:24 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LDC00JA4GACYG@szxga04-in.huawei.com> for ccamp@ietf.org; Mon, 13 Dec 2010 10:01:24 +0800 (CST)
Received: from l00037133 ([10.70.77.77]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LDC00CY5GACS0@szxml04-in.huawei.com> for ccamp@ietf.org; Mon, 13 Dec 2010 10:01:24 +0800 (CST)
Date: Mon, 13 Dec 2010 10:01:23 +0800
From: Dan Li <danli@huawei.com>
To: Adrian.Farrel@huawei.com, tm-otani@kddi.com, rabbat@alum.mit.edu, sidney.shiba@yahoo.com, hongxiang.guo@gmail.com, miyazaki.keiji@jp.fujitsu.com, diego.caviglia@ericsson.com, tsuri@kddilabs.jp
Message-id: <00be01cb9a69$a4d30ed0$4d4d460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <06ea01cb97ea$a3b57230$eb205690$@huawei.com>
Cc: ccamp@ietf.org, ccamp-chairs@tools.ietf.org
Subject: Re: [CCAMP] AD review of draft-ietf-ccamp-gmpls-g-694-lambda-labels-09
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Dec 2010 02:00:00 -0000

Hi Adrian,

Thanks for the AD review for this draft!

We have updated the draft-g.694-labels according to your comments, two major changes as following (except several minor editorial changes which have been accepted):
1) added the disclaimer for pre-RFC5378 work in "Copyright Notice" section;
2) added a requirement for IANA to create three subregistries (Grid, DWDM C.S. and CWDM C.S.) under "Generalized Multi-Protocol Label Switching  (GMPLS) Signaling Parameters" registry.

The updated version (10) of this draft has been posted.

Thanks,

Dan

----- Original Message ----- 
From: "Adrian Farrel" <Adrian.Farrel@huawei.com>
To: <danli@huawei.com>; <tm-otani@kddi.com>; <rabbat@alum.mit.edu>; <sidney.shiba@yahoo.com>; <hongxiang.guo@gmail.com>; <miyazaki.keiji@jp.fujitsu.com>; <diego.caviglia@ericsson.com>; <tsuri@kddilabs.jp>
Cc: <ccamp@ietf.org>; <ccamp-chairs@tools.ietf.org>
Sent: Friday, December 10, 2010 5:47 AM
Subject: AD review of draft-ietf-ccamp-gmpls-g-694-lambda-labels-09


> Hi,
> 
> I have performed an AD review of your draft.
> 
> Don't panic!
> 
> I review all drafts that I am responsible for before putting them
> forward for IETF last call. The main objective is to catch nits and
> minor issues that would show up during the last call or in IESG
> review. The intention is to help polish your document and make sure
> it is clean and shiny so that other reviewers will stick to the
> technical details.
> 
> I think your small draft is actually a very significant contribution to
> the GMPLS family.
> 
> Most of my comments are pretty trivial, but a couple have more meat
> on them and I'd like to see a quick respin of the document before I
> issue the IETF last call. As soon as I see a new revision posted,
> I'll set the ball in motion.
> 
> Of course, all of my issues are up for discussion.
> 
> Thanks for the work,
> Adrian
> 
> ---
> 
> idnits throws up a number of minor issues...
> 
>> ** There is 1 instance of too long lines in the document, the longest
>>    one being 1 character in excess of 72.
> 
> This seems to be line 46
> 
>> == The 'Updates: ' line in the draft header should list only the
>>    _numbers_ of the RFCs which will be updated by this document (if
>>    approved); it should not include the word 'RFC' in the list.
> 
> This is in the document header...
> 
> s/Updates: RFC3471/Updates: 3471 (if approved)/
> 
>> == The document seems to lack a disclaimer for pre-RFC5378 work, but
>>    was first submitted before 10 November 2008.  Should you add the 
>>    disclaimer? (See the Legal Provisions document at
>>    http://trustee.ietf.org/license-info for more information.) 
>>    -- however, there's a paragraph with a matching beginning. 
>>    Boilerplate error?
> 
> Just need to check with you that the authors are happy to not include
> the boilerplate and are assigning the copyright. Usually not a problem,     
> but if you have trouble tracking down the authors, just add the 
> disclaimer boilerplate - it is quite safe!
> 
>> == Unused Reference: 'RFC3209' is defined on line 433, but no 
>>    explicit reference was found in the text
> 
> You can just remove the reference.
> 
> ---
> 
> The Abstract needs to be self-contained, so cannot include citations of
> RFCs or other documents.
> 
> You also need to spell out acronyms.
> 
> Can I suggest:
> 
> OLD
>   Technology in the optical domain is constantly evolving and as a 
>   consequence new equipment providing lambda switching capability has 
>   been developed and is currently being deployed. [RFC3471] has 
>   defined that a wavelength label (section 3.2.1.1) "only has 
>   significance between two neighbors" and global wavelength semantics 
>   is not considered. In order to facilitate interoperability in a 
>   network composed of next generation lambda switch-capable equipment, 
>   this document defines a standard lambda label format, which is 
>   compliant with both [G.694.1](DWDM-grid) or [G.694.2](CWDM-grid).  
>   This document is a companion to the Generalized Multi-Protocol Label 
>   Switching (GMPLS) signaling. It defines the label format when Lambda 
>   Switching is requested in an all optical network. 
> NEW                       
>   Technology in the optical domain is constantly evolving and as a 
>   consequence new equipment providing lambda switching capability has 
>   been developed and is currently being deployed. 
>   
>   Generalized MPLS (GMPLS) is a family of protocols that can be used 
>   to operate networks built from a range of technologies including
>   wavelength (or lambda) switching. For this purpose, GMPLS defined
>   that a wavelength label only has significance between two neighbors 
>   and global wavelength semantics are not considered.
>   
>   In order to facilitate interoperability in a network composed of next
>   generation lambda switch-capable equipment, this document defines a
>   standard lambda label format that is compliant with Dense Wavelength
>   Division Multiplexing and Coarse Wavelength Division Multiplexing 
>   grids defined by the International Telecommunication Union
>   Telecommunication Standardization Sector. The label format defined in
>   this document can be used in GMPLS signaling and routing protocols.
> END
> 
> ---
> 
> You are not required to include a Table of Contents in a document of less
> than fifteen pages (but you are allowed to).
> 
> ---
> 
> Section 1
> 
> You need to expand DWDM and CWDM on first use.
> You can then remove the expansions from Section 2.
> 
> ---
> 
> Section 2
> 
> Could you capitalise the section header to match the others.
> 
> 
> ---
> 
> Section 2
> 
> s/vendor's/vendors'/
> s/consists of number/consists of a number/
> 
> ---
> 
> Section 2
> 
> s/a LSP/an LSP/
> 
> ---
> 
> Section 2 (last line)
> 
> Expand "LSR" on first use.
> 
> ---                                                                
> 
> Section 3.3
> 
>   We do not need to define a new type as the information stored is 
>   either a port label or a wavelength label. Only the wavelength label 
>   as above needs to be defined. 
> 
> This is very true, but I think the text does not belong here.
> I would try to work it into Section 3.1
> 
> ---
> 
> 
> Section 4
> 
>   This document introduces no new security considerations to [RFC3473]. 
>   For a general discussion on MPLS and GMPLS related security issues, 
>   see the MPLS/GMPLS security framework [RFC5920]. 
> 
> I think you should 
> s/[RFC3473]/[RFC3471] and [RFC3473]/
> because this I-D updates 3471.
>                                                         
> ---
> 
> Section 5
> 
> Why did you decide that there is no requirement for IANA to track the
> codepoints (Grid and C.S.) used in the DWDM and CWDM Wavelength Labels? 
> 
> It looks like you could have three registries {Grid, DWDM C.S., and 
> CWDM C.S.)
> 
> ---
> 
> Section 8
> 
> OLD
> 8. Author's Address
> NEW
> 8. Authors' Addresses
> END
> 
>

From zhangfatai@huawei.com  Sun Dec 12 23:01:32 2010
Return-Path: <zhangfatai@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A4B43A68C5 for <ccamp@core3.amsl.com>; Sun, 12 Dec 2010 23:01:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.669
X-Spam-Level: 
X-Spam-Status: No, score=0.669 tagged_above=-999 required=5 tests=[AWL=1.163,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EOK2G8GsRy80 for <ccamp@core3.amsl.com>; Sun, 12 Dec 2010 23:01:31 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 6D5E23A6855 for <ccamp@ietf.org>; Sun, 12 Dec 2010 23:01:31 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LDC00JKSU74P3@szxga05-in.huawei.com> for ccamp@ietf.org; Mon, 13 Dec 2010 15:01:52 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LDC005HTU73L0@szxga05-in.huawei.com> for ccamp@ietf.org; Mon, 13 Dec 2010 15:01:51 +0800 (CST)
Received: from z41162a ([10.70.76.157]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LDC00I5JU71I2@szxml04-in.huawei.com> for ccamp@ietf.org; Mon, 13 Dec 2010 15:01:51 +0800 (CST)
Date: Mon, 13 Dec 2010 15:01:49 +0800
From: Fatai Zhang <zhangfatai@huawei.com>
To: ccamp@ietf.org, "Sadler, Jonathan B." <Jonathan.Sadler@tellabs.com>, Dimitri.Papadimitriou@alcatel-lucent.com
Message-id: <9AE0E9E3472F47E8B6DA49CA1D502063@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_xw0fNKkyjrpjBcjChQ1mbQ)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [CCAMP] Answer the comments on draft-zhang-ccamp-gmpls-h-lsp-mln-02.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Dec 2010 07:01:32 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_xw0fNKkyjrpjBcjChQ1mbQ)
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT

Hi Jonathan, Dimitri and all,

We got some comments at the Beijing meeting. 

One is from Jonathan. Jonathan said he likes the generalized nature of this draft, but he also pointed out that since different adaptations may be supported on the boundary nodes, the GPID used in the server layer signaling will be key to  keep the lower layer connection from being refused. Therefore, the question from him is: Is there a way for the SERVER_LAYER_INFO object can convey this information?

After investigation, we think that GPID is very important to tell how the client signals can be adapted into the server layer. We will update the draft to be capble of conveying GPID information.

Another comment from Dimitri, who pointed out that this capability already exists in [RFC 6001]. Actually, we had noticed the mechanism defined in [RFC 6001]. In [RFC 6001], it can only specify the switching capability implicitly by excluding some SCs, but it can not specify switching granularity to be used at the server layer. Some text is already stated in Section 3.1 and 4.2 of draft-zhang-ccamp-gmpls-h-lsp-mln-02.txt.

Welcome any more comments.

Fatai

Thanks




--Boundary_(ID_xw0fNKkyjrpjBcjChQ1mbQ)
Content-type: text/html; charset=gb2312
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=gb2312">
<META content="MSHTML 6.00.2900.6036" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial>Hi Jonathan, Dimitri and all,</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>We got some comments at the Beijing meeting. </FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>One is from Jonathan. Jonathan said he likes the 
generalized nature of this draft, but he also pointed out that since different 
adaptations may be supported on the boundary&nbsp;nodes, the GPID used in the 
server layer signaling will be key to&nbsp; keep the lower layer connection from 
being refused. Therefore, the question from him is: Is there a&nbsp;way for the 
SERVER_LAYER_INFO object can convey this information?<BR></FONT></DIV>
<DIV><FONT face=Arial>After investigation, we think that GPID is very important 
to tell how the client signals can be adapted into the server layer. We will 
update the draft to be capble of conveying GPID information.</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>Another comment from Dimitri, who&nbsp;pointed out that 
this capability already exists in [RFC 6001]. Actually, we had noticed the 
mechanism defined in [RFC 6001]. In [RFC 6001],&nbsp;it can only&nbsp;specify 
the switching capability implicitly by excluding some SCs, but it can not 
specify </FONT><FONT face=Arial>switching granularity to be used at the server 
layer. Some text is already stated&nbsp;in Section 3.1 and 4.2 of 
draft-zhang-ccamp-gmpls-h-lsp-mln-02.txt.</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>Welcome any more comments.</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>Fatai</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>Thanks</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

--Boundary_(ID_xw0fNKkyjrpjBcjChQ1mbQ)--

From iesg-secretary@ietf.org  Mon Dec 13 05:29:40 2010
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 05CA33A6E9D; Mon, 13 Dec 2010 05:29:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.414
X-Spam-Level: 
X-Spam-Status: No, score=-102.414 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NrNpP2KvU5MF; Mon, 13 Dec 2010 05:29:39 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 648673A6E90; Mon, 13 Dec 2010 05:29:39 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20101213132939.2894.72916.idtracker@localhost>
Date: Mon, 13 Dec 2010 05:29:39 -0800
Cc: ccamp@ietf.org
Subject: [CCAMP] Last Call: <draft-ietf-ccamp-gmpls-g-694-lambda-labels-10.txt>	(Generalized Labels for Lambda-Switching Capable Label	Switching Routers) to Proposed Standard
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Dec 2010 13:29:40 -0000

The IESG has received a request from the Common Control and Measurement
Plane WG (ccamp) to consider the following document:
- 'Generalized Labels for Lambda-Switching Capable Label Switching
   Routers'
  <draft-ietf-ccamp-gmpls-g-694-lambda-labels-10.txt> as a Proposed
Standard

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

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-ccamp-gmpls-g-694-lambda-labels/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-ccamp-gmpls-g-694-lambda-labels/


No IPR declarations have been submitted directly on this I-D.

From gregb@grotto-networking.com  Tue Dec 14 10:22:15 2010
Return-Path: <gregb@grotto-networking.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A6FC23A6EB8 for <ccamp@core3.amsl.com>; Tue, 14 Dec 2010 10:22:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level: 
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jKinPK1vGi6k for <ccamp@core3.amsl.com>; Tue, 14 Dec 2010 10:22:14 -0800 (PST)
Received: from mail32c40.carrierzone.com (mail32c40.carrierzone.com [209.235.156.172]) by core3.amsl.com (Postfix) with ESMTP id 5666D3A6EA9 for <ccamp@ietf.org>; Tue, 14 Dec 2010 10:22:14 -0800 (PST)
X-Authenticated-User: gregb.grotto-networking.com
Received: from [192.168.0.124] (c-71-202-41-133.hsd1.ca.comcast.net [71.202.41.133]) (authenticated bits=0) by mail32c40.carrierzone.com (8.13.6/8.13.1) with ESMTP id oBEINq6D002868 for <ccamp@ietf.org>; Tue, 14 Dec 2010 18:23:53 GMT
Message-ID: <4D07B635.1030503@grotto-networking.com>
Date: Tue, 14 Dec 2010 10:23:49 -0800
From: Greg Bernstein <gregb@grotto-networking.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: CCAMP <ccamp@ietf.org>
Content-Type: multipart/alternative; boundary="------------060205020200070203030604"
X-CSC: 0
X-CHA: v=1.1 cv=VUt4bLtRU7RspfXdhy6wiXQdwFUR8ThHFgSMx6cBvw0= c=1 sm=1 a=Lxd8k5WMpIsA:10 a=OkPnmgdRXU7//wtL+yd+jg==:17 a=H2uK6G9ZUNGPL5fnDEcA:9 a=K1aUvFiqYB4zwlQnNfEA:7 a=dP3f-vakNIUMDNIJ8ebyIXfwM70A:4 a=wPNLvfGTeEIA:10 a=EgY3od2ZU2QA:10 a=h-I_03WOSDMA:10 a=U6-pXGRpkCAubcbr:21 a=8ZPbU3fhpxR7oFUr:21 a=4PKvjmU2AKhrDFqYu5EA:9 a=ZS__cJqsmiQsIvFOoCsA:7 a=Ijqz9-5vkPx759vIAJUUMUqYaegA:4 a=OkPnmgdRXU7//wtL+yd+jg==:117
Subject: [CCAMP] Top Level TLVs for WSON and General Constraint Extensions to OSPF (long)
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Dec 2010 18:22:15 -0000

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

Hi all two weeks ago we updated 
draft-ietf-ccamp-general-constraint-encode and 
draft-ietf-ccamp-rwa-wson-encode based on comments from the list and the 
Beijing meeting. These changes were editorial in nature and consisted of 
removing some informational text.
To move things forward in general we need to reach agreement on the top 
level TLVs to be used to carry this information.  We have two main types 
of information: (a) link related, and (b) node related.  In addition, 
depending on the complexity of the system we may want to split the 
information for a particular node or link into multiple LSAs  to keep 
the size of the LSA below a particular limit or to separate rapidly 
changing node or link information from relatively static. In general 
multiple TE LSA instances provide a mechanism for this.

*For Link information* *RFC3630* defines the "Traffic Engineering LSA". 
This has area scope.
"One new LSA is defined, the Traffic Engineering LSA.  This LSA 
describes routers, point-to-point links, and connections to multi-access 
networks (similar to a Router LSA)."

Multiple instances can exist from a single source:
"The Instance field is an arbitrary value used to maintain multiple 
Traffic Engineering LSAs.  A maximum of 16777216 Traffic Engineering 
LSAs may be sourced by a single system."

Two top level TLVs are defined: Router Address TLV (section 2.4.1) and 
Link TLV (section 2.4.2). The router address is just as it says. The 
link TLV is the generally useful one for us:
"The Link TLV describes a single link.  It is constructed of a set of 
sub-TLVs.  There are no ordering requirements for the sub-TLVs. Only one 
Link TLV shall be carried in each LSA, allowing for fine granularity 
changes in topology."

There does not appear to be any constraints on breaking up information 
about a single link into multiple LSAs. For WSON use we may want to keep 
static information (port wavelength constraints) separate from dynamic 
information (wavelength availability).

*For Node Level information* (such as connectivity matrices, resource 
block information, resource block usage state) it seemed like *RFC 5786* 
which has extensions for advertising a routers local addresses in TE 
extensions would be useful. It defines the OSPF TE LSA Node TLV and they 
state:
"It is anticipated that the Node Attribute TLV will also prove more 
generally useful."
However in section 4.2 (Operation) they state:
"*/The Node Attribute TLV MUST NOT appear in more than one TE LSA 
originated by a router/*.  Furthermore, such an LSA MUST NOT include 
more than one Node Attribute TLV."

The first of these restrictions on use seems to preclude us from 
separating traffic matrices, resource block descriptions, and resource 
block utilization status into separate LSA instances using this TLV. 
Unless this rule can be changed it seems that we will need a new top 
level "node properties" TLV for use in both WSON specific and General 
constraint extensions to OSPF.  Pierre and Giovanni in 
draft-peloso-ccamp-wson-ospf-oeo-02.txt wanted to define a new top level 
TLV for the resource block information, however it seems that we 
probably should ask for a general "node properties" (or whatever better 
name we can think of) top level TLV that could be applied to the general 
constraint node information (connectivity matrices) as well as the 
various resource related quantities.

Pierre and Giovanni does this sound like a reasonable way forward? Or do 
you have a different suggestion.  Comments and suggestions from all are 
welcome.

Best Regards

Greg B.

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



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Hi all two weeks ago we updated
    draft-ietf-ccamp-general-constraint-encode and
    draft-ietf-ccamp-rwa-wson-encode based on comments from the list and
    the Beijing meeting. These changes were editorial in nature and
    consisted of removing some informational text. <br>
    To move things forward in general we need to reach agreement on the
    top level TLVs to be used to carry this information.&nbsp; We have two
    main types of information: (a) link related, and (b) node related.&nbsp;
    In addition, depending on the complexity of the system we may want
    to split the information for a particular node or link into multiple
    LSAs&nbsp; to keep the size of the LSA below a particular limit or to
    separate rapidly changing node or link information from relatively
    static. In general multiple TE LSA instances provide a mechanism for
    this.<br>
    <br>
    <b>For Link information</b> <b>RFC3630</b> defines the "Traffic
    Engineering LSA". This has area scope.<br>
    "One new LSA is defined, the Traffic Engineering LSA.&nbsp; This LSA
    describes routers, point-to-point links, and connections to
    multi-access networks (similar to a Router LSA)."<br>
    <br>
    Multiple instances can exist from a single source:<br>
    "The Instance field is an arbitrary value used to maintain multiple
    Traffic Engineering LSAs.&nbsp; A maximum of 16777216 Traffic Engineering
    LSAs may be sourced by a single system."<br>
    <br>
    Two top level TLVs are defined: Router Address TLV (section 2.4.1)
    and Link TLV (section 2.4.2). The router address is just as it says.
    The link TLV is the generally useful one for us:<br>
    "The Link TLV describes a single link.&nbsp; It is constructed of a set
    of sub-TLVs.&nbsp; There are no ordering requirements for the sub-TLVs.
    Only one Link TLV shall be carried in each LSA, allowing for fine
    granularity changes in topology."<br>
    <br>
    There does not appear to be any constraints on breaking up
    information about a single link into multiple LSAs. For WSON use we
    may want to keep static information (port wavelength constraints)
    separate from dynamic information (wavelength availability).<br>
    <br>
    <b>For Node Level information</b> (such as connectivity matrices,
    resource block information, resource block usage state) it seemed
    like <b>RFC 5786</b> which has extensions for advertising a routers
    local addresses in TE extensions would be useful. It defines the
    OSPF TE LSA Node TLV and they state:<br>
    "It is anticipated that the Node Attribute TLV will also prove more
    generally useful."<br>
    However in section 4.2 (Operation) they state:<br>
    "<b><i>The Node Attribute TLV MUST NOT appear in more than one TE
        LSA originated by a router</i></b>.&nbsp; Furthermore, such an LSA
    MUST NOT include more than one Node Attribute TLV."<br>
    <br>
    The first of these restrictions on use seems to preclude us from
    separating traffic matrices, resource block descriptions, and
    resource block utilization status into separate LSA instances using
    this TLV. Unless this rule can be changed it seems that we will need
    a new top level "node properties" TLV for use in both WSON specific
    and General constraint extensions to OSPF.&nbsp; Pierre and Giovanni in
    draft-peloso-ccamp-wson-ospf-oeo-02.txt wanted to define a new top
    level TLV for the resource block information, however it seems that
    we probably should ask for a general "node properties" (or whatever
    better name we can think of) top level TLV that could be applied to
    the general constraint node information (connectivity matrices) as
    well as the various resource related quantities.&nbsp; <br>
    <br>
    Pierre and Giovanni does this sound like a reasonable way forward?
    Or do you have a different suggestion.&nbsp; Comments and suggestions
    from all are welcome.<br>
    <br>
    Best Regards<br>
    <br>
    Greg B.<br>
    <br>
    <pre class="moz-signature" cols="72">-- 
===================================================
Dr Greg Bernstein, Grotto Networking (510) 573-2237

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

--------------060205020200070203030604--

From Attila.Takacs@ericsson.com  Tue Dec 14 12:52:09 2010
Return-Path: <Attila.Takacs@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EAC3428C0EB for <ccamp@core3.amsl.com>; Tue, 14 Dec 2010 12:52:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NQCSWRWndvcQ for <ccamp@core3.amsl.com>; Tue, 14 Dec 2010 12:52:07 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 86B2428C131 for <ccamp@ietf.org>; Tue, 14 Dec 2010 12:52:06 -0800 (PST)
X-AuditID: c1b4fb39-b7bd2ae000001d22-68-4d07d95ab6b5
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 94.B3.07458.A59D70D4; Tue, 14 Dec 2010 21:53:46 +0100 (CET)
Received: from ESESSCMS0365.eemea.ericsson.se ([169.254.1.32]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Tue, 14 Dec 2010 21:53:46 +0100
From: Attila Takacs <Attila.Takacs@ericsson.com>
To: Aidan Copeland <aidan.copeland@metaswitch.com>, "draft-ietf-ccamp-oam-configuration-fwk@tools.ietf.org" <draft-ietf-ccamp-oam-configuration-fwk@tools.ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>
Date: Tue, 14 Dec 2010 21:53:45 +0100
Thread-Topic: Comment on draft-ietf-ccamp-oam-configuration-fwk
Thread-Index: Acubl/y5re6ec9P7TeuT0MF0LmJHnwAN5Avg
Message-ID: <6477E10CC7D76444A479B9AC31F262A9DA73EEB2@ESESSCMS0365.eemea.ericsson.se>
References: <11DE3EEC54A8A44EAD99D8C0D3FD7207A348BACC23@ENFIMBOX1.ad.datcon.co.uk>
In-Reply-To: <11DE3EEC54A8A44EAD99D8C0D3FD7207A348BACC23@ENFIMBOX1.ad.datcon.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_6477E10CC7D76444A479B9AC31F262A9DA73EEB2ESESSCMS0365eem_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [CCAMP] Comment on draft-ietf-ccamp-oam-configuration-fwk
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Dec 2010 20:52:10 -0000

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

Hi Aidan,

I think a node's behavior on receipt of an OAM Configuration TLV with an un=
recognised OAM Method should instead be determined by whether the TLV is co=
ntained within an LSP_ATTRIBUTES or an LSP_REQUIRED_ATTRIBUTES object, so t=
hat the TLV will be forwarded unchanged if contained within an LSP_ATTRIBUT=
ES object.  Do you agree?

Yes, this is the intended operation. I will check and clarify as needed in =
the draft, good catch!
Thanks,
Attila

Thanks

Aidan Copeland


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18527" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Wingdings;
}
@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page WordSection1 {size: 612.0pt 792.0pt; margin: 72.0pt 72.0pt 72.0pt 72.=
0pt; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-se=
rif"; mso-style-priority: 34
}
LI.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-se=
rif"; mso-style-priority: 34
}
DIV.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-se=
rif"; mso-style-priority: 34
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Arial","sans-serif"; mso-style-type: pers=
onal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
OL {
	MARGIN-BOTTOM: 0cm
}
UL {
	MARGIN-BOTTOM: 0cm
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-GB vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D482234320-14122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi Aidan,</FONT></SPAN></DIV>
<DIV class=3DWordSection1><![if !supportLists]><![endif]><![if !supportList=
s]><![endif]>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 18pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p>&nbsp;</o=
:p></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">I think a node=
&#8217;s=20
behavior on receipt of an OAM Configuration TLV with an unrecognised OAM Me=
thod=20
should instead be determined by whether the TLV is contained within an=20
LSP_ATTRIBUTES or an LSP_REQUIRED_ATTRIBUTES object, so that the TLV will b=
e=20
forwarded unchanged if contained within an LSP_ATTRIBUTES object.&nbsp; Do =
you=20
agree?<SPAN style=3D"COLOR: maroon">&nbsp;</SPAN></SPAN><o:p></o:p></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p>&nbsp;</o=
:p></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p><SPAN=20
class=3D482234320-14122010><FONT color=3D#0000ff>Yes, this is the intended=
=20
operation. I will check and clarify as needed in the draft, good=20
catch!</FONT></SPAN></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p><SPAN=20
class=3D482234320-14122010><FONT=20
color=3D#0000ff>Thanks,</FONT></SPAN></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p><SPAN=20
class=3D482234320-14122010><FONT=20
color=3D#0000ff>Attila</FONT></SPAN></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p><FONT=20
color=3D#0000ff></FONT></o:p></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Thanks<o:p></o=
:p></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p>&nbsp;</o=
:p></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Aidan=20
Copeland<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p>&nbsp;</o=
:p></SPAN></P></DIV></BODY></HTML>

--_000_6477E10CC7D76444A479B9AC31F262A9DA73EEB2ESESSCMS0365eem_--

From Attila.Takacs@ericsson.com  Tue Dec 14 12:55:12 2010
Return-Path: <Attila.Takacs@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 17CD828C12C for <ccamp@core3.amsl.com>; Tue, 14 Dec 2010 12:55:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gKGOQh4YOgVu for <ccamp@core3.amsl.com>; Tue, 14 Dec 2010 12:55:11 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id E266128C0EB for <ccamp@ietf.org>; Tue, 14 Dec 2010 12:55:10 -0800 (PST)
X-AuditID: c1b4fb3d-b7ceeae0000031e4-3d-4d07da13a62f
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 85.83.12772.31AD70D4; Tue, 14 Dec 2010 21:56:51 +0100 (CET)
Received: from ESESSCMS0365.eemea.ericsson.se ([169.254.1.32]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Tue, 14 Dec 2010 21:56:50 +0100
From: Attila Takacs <Attila.Takacs@ericsson.com>
To: Aidan Copeland <aidan.copeland@metaswitch.com>, "draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext@tools.ietf.org" <draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext@tools.ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>
Date: Tue, 14 Dec 2010 21:56:49 +0100
Thread-Topic: Comments/queries on draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext
Thread-Index: Acubl/qDCoocHkIXQiWLN470m1YpTgAOE+ew
Message-ID: <6477E10CC7D76444A479B9AC31F262A9DA73EEB3@ESESSCMS0365.eemea.ericsson.se>
References: <11DE3EEC54A8A44EAD99D8C0D3FD7207A348BACC21@ENFIMBOX1.ad.datcon.co.uk>
In-Reply-To: <11DE3EEC54A8A44EAD99D8C0D3FD7207A348BACC21@ENFIMBOX1.ad.datcon.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_6477E10CC7D76444A479B9AC31F262A9DA73EEB3ESESSCMS0365eem_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [CCAMP] Comments/queries on draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Dec 2010 20:55:12 -0000

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

Hi Aidan,

Regarding your first point:


*         I note that the FMS OAM Function flag (section 3.2) is not yet de=
fined in draft-ietf-ccamp-oam-configuration-fwk.  Please could you request =
the authors of that draft to define this flag in their next revision?

I think this flag should be defined in draft-ietf-ccamp-rsvp-te-mpls-tp-oam=
-ext as this is the first document that introduces the functionality that t=
his flag is used for.

Best regards,
Attila



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18527" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: Wingdings;
}
@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@page WordSection1 {size: 612.0pt 792.0pt; margin: 72.0pt 72.0pt 72.0pt 72.=
0pt; }
P.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-se=
rif"; mso-style-priority: 34
}
LI.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-se=
rif"; mso-style-priority: 34
}
DIV.MsoListParagraph {
	FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-se=
rif"; mso-style-priority: 34
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: "Arial","sans-serif"; mso-style-type: pers=
onal-compose
}
.MsoChpDefault {
	mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
OL {
	MARGIN-BOTTOM: 0cm
}
UL {
	MARGIN-BOTTOM: 0cm
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-GB vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D955404820-14122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi Aidan,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D955404820-14122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D955404820-14122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Regarding your first point:</FONT></SPAN></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft><SPAN=
=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p>&nbsp;</o=
:p></SPAN></DIV>
<DIV class=3DWordSection1>
<P class=3DMsoListParagraph=20
style=3D"MARGIN-LEFT: 18pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo3"><=
![if !supportLists]><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Symbol"><SPAN=20
style=3D"mso-list: Ignore">&middot;<SPAN=20
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
</SPAN></SPAN></SPAN><![endif]><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">I note that th=
e FMS=20
OAM Function flag (section 3.2) is not yet defined in=20
draft-ietf-ccamp-oam-configuration-fwk.&nbsp; Please could you request the=
=20
authors of that draft to define this flag in their next=20
revision?<o:p></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p>&nbsp;</o=
:p></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p><SPAN=20
class=3D955404820-14122010><FONT color=3D#0000ff>I think this flag should b=
e defined=20
in draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext as this is the first document t=
hat=20
introduces the functionality that this flag is used for.=20
</FONT></SPAN></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p><FONT=20
color=3D#0000ff></FONT></o:p></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p><SPAN=20
class=3D955404820-14122010><FONT color=3D#0000ff>Best=20
regards,</FONT></SPAN></o:p></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p><SPAN=20
class=3D955404820-14122010></SPAN></o:p></SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p><SPAN=20
class=3D955404820-14122010><FONT color=3D#0000ff>Attila</FONT></SPAN></o:p>=
<![if !supportLists]><![endif]><![if !supportLists]><![endif]><![if !suppor=
tLists]><![endif]><![if !supportLists]><![endif]></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p>&nbsp;</o=
:p></SPAN></P>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p>&nbsp;</o=
:p></SPAN></P></DIV></BODY></HTML>

--_000_6477E10CC7D76444A479B9AC31F262A9DA73EEB3ESESSCMS0365eem_--

From db3546@att.com  Thu Dec 16 11:52:04 2010
Return-Path: <db3546@att.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A5B13A697D for <ccamp@core3.amsl.com>; Thu, 16 Dec 2010 11:52:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.499
X-Spam-Level: 
X-Spam-Status: No, score=-106.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nl4jDpfQ15ZN for <ccamp@core3.amsl.com>; Thu, 16 Dec 2010 11:52:02 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by core3.amsl.com (Postfix) with ESMTP id 0BEC83A6949 for <ccamp@ietf.org>; Thu, 16 Dec 2010 11:52:01 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: db3546@att.com
X-Msg-Ref: server-15.tower-119.messagelabs.com!1292529226!307114!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 26304 invoked from network); 16 Dec 2010 19:53:46 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-15.tower-119.messagelabs.com with AES256-SHA encrypted SMTP; 16 Dec 2010 19:53:46 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id oBGJr1Rt021823 for <ccamp@ietf.org>; Thu, 16 Dec 2010 14:53:01 -0500
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id oBGJqwxg021761 for <ccamp@ietf.org>; Thu, 16 Dec 2010 14:52:58 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 16 Dec 2010 14:53:42 -0500
Message-ID: <D6CB948F7AFD6F4881D4B4F80C8509AA090FB10D@gaalpa1msgusr7e.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Last Call on draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-00.txt
Thread-Index: AcudWvD5GWk3bU1rQNydPTsXcmhgqQ==
From: "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>
To: "CCAMP" <ccamp@ietf.org>
Subject: [CCAMP] WG Last Call on draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-00.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Dec 2010 19:52:05 -0000

All,

This is to start a three-week (extended for the holidays) working group
last call on draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-00.txt.

This working group last call ends Jan. 6. Please send your comments to
the CCAMP mailing list.

Deborah (and Lou)


From adrian@olddog.co.uk  Thu Dec 16 13:37:07 2010
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 466B13A69F7 for <ccamp@core3.amsl.com>; Thu, 16 Dec 2010 13:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zepstjhN09+S for <ccamp@core3.amsl.com>; Thu, 16 Dec 2010 13:37:06 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by core3.amsl.com (Postfix) with ESMTP id 34CCF3A69CF for <ccamp@ietf.org>; Thu, 16 Dec 2010 13:37:05 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id oBGLcmGL000869 for <ccamp@ietf.org>; Thu, 16 Dec 2010 21:38:48 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id oBGLclD8000834 for <ccamp@ietf.org>; Thu, 16 Dec 2010 21:38:47 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'CCAMP'" <ccamp@ietf.org>
Date: Thu, 16 Dec 2010 21:38:49 -0000
Message-ID: <054601cb9d69$a0c20d70$e2462850$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AcudaZY7XiXn4qqGQaWUN9hHDUWnKQ==
Content-Language: en-gb
Subject: Re: [CCAMP] WG Last Call on draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-00.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Dec 2010 21:37:07 -0000

Hi,

Can I get in an early question about how this relates to RFC 5467?

Is it you intention that the 5467 Experiment should remain in place, or do you
want to replace it with this document? 

The text says:
   This document
   has no technical changes from the approach defined in [RFC5467].
   This document removes an alternate approach that is not part of the
   Standards Track solution.

So the question is whether the (mystery) alternate approach that is removed is
to remain as experimental or is completely discarded.

If you are replacing 5467 (which I hope is the case), the document needs to say
so:
1. Header should include "Obsoletes: 5467 (if approved)"
2. Abstract should say "This document moves the experiment documented in RFC
5467 to the standards track and obsoletes RFC 5467."
3. The Introduction should include a similar statement.
4. Somewhere in the document you need to explain which piece has been left out
from 5467 and why.

If you are wanting to do something more complicated with keeping the experiment
alive, but also standardising part of the material, you will have to ask your AD
how to do this (because I don't know! :-).

I guess the authors and the WG can discuss what exactly the intention is, and
update the document accordingly.

Thanks,
Adrian

> -----Original Message-----
> From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of 
> BRUNGARD, DEBORAH A (ATTLABS)
> Sent: 16 December 2010 19:54
> To: CCAMP
> Subject: [CCAMP] WG Last Call on draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-
> 00.txt
> 
> All,
> 
> This is to start a three-week (extended for the holidays) working group
> last call on draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-00.txt.
> 
> This working group last call ends Jan. 6. Please send your comments to
> the CCAMP mailing list.
> 
> Deborah (and Lou)
> 
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp


From Internet-Drafts@ietf.org  Fri Dec 17 15:15:05 2010
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C7163A69ED; Fri, 17 Dec 2010 15:15:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.515
X-Spam-Level: 
X-Spam-Status: No, score=-102.515 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l48cd6wdKY1F; Fri, 17 Dec 2010 15:15:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 643183A69C7; Fri, 17 Dec 2010 15:15:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20101217231502.18464.16387.idtracker@localhost>
Date: Fri, 17 Dec 2010 15:15:02 -0800
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-rwa-wson-framework-08.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Dec 2010 23:15:05 -0000

--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           : Framework for GMPLS and PCE Control of Wavelength Switched Optical Networks (WSON)
	Author(s)       : G. Bernstein, et al.
	Filename        : draft-ietf-ccamp-rwa-wson-framework-08.txt
	Pages           : 56
	Date            : 2010-12-17

This document provides a framework for applying Generalized Multi-
Protocol Label Switching (GMPLS) and the Path Computation Element
(PCE) architecture to the control of wavelength switched optical
networks (WSON).  In particular, it examines Routing and Wavelength
Assignment (RWA) of optical paths.

This document focuses on topological elements and path selection
constraints that are common across different WSON environments as
such it does not address optical impairments in any depth.

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

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ccamp-rwa-wson-framework-08.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-12-17150419.I-D@ietf.org>


--NextPart--

From pierre.peloso@alcatel-lucent.com  Mon Dec 20 04:26:01 2010
Return-Path: <pierre.peloso@alcatel-lucent.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F1AE3A6873 for <ccamp@core3.amsl.com>; Mon, 20 Dec 2010 04:26:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.248
X-Spam-Level: 
X-Spam-Status: No, score=-4.248 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gwinKrz5UNkI for <ccamp@core3.amsl.com>; Mon, 20 Dec 2010 04:25:59 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id 61E6C3A686A for <ccamp@ietf.org>; Mon, 20 Dec 2010 04:25:58 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id oBKCRfTn005983 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 20 Dec 2010 13:27:44 +0100
Received: from FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com ([135.120.45.34]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Mon, 20 Dec 2010 13:27:41 +0100
From: "PELOSO, PIERRE (PIERRE)" <pierre.peloso@alcatel-lucent.com>
To: Greg Bernstein <gregb@grotto-networking.com>, CCAMP <ccamp@ietf.org>
Date: Mon, 20 Dec 2010 13:27:39 +0100
Thread-Topic: [CCAMP] Top Level TLVs for WSON and General Constraint Extensions to OSPF (long)
Thread-Index: AcubvBvITgieW37hQieBgLKzwiFtuAEceESQ
Message-ID: <CCBFBB7025DF984494DEC3285C0581521269ED11D9@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com>
References: <4D07B635.1030503@grotto-networking.com>
In-Reply-To: <4D07B635.1030503@grotto-networking.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR, en-US
Content-Type: multipart/alternative; boundary="_000_CCBFBB7025DF984494DEC3285C0581521269ED11D9FRMRSSXCHMBSA_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.84
Subject: Re: [CCAMP] Top Level TLVs for WSON and General Constraint Extensions to OSPF (long)
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Dec 2010 12:26:01 -0000

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

Hi Greg,

To start with, I am pretty in-line with the part related to the link TLV, w=
hich was already agreed.

Regarding the node related information, I am happy to see that you consider=
 splitting its information over 2 top-level TLVs, which we have been pronin=
g in order to ease the scalability and the information organisation.
I do encourage you to adopt even more the concepts proned in draft-peloso-c=
camp-won-ospf-oeo, by defining this new top-level TLV in a way that allows =
to have multiple instance of it, one for each conistent entity of ressoruce=
s.

To detail my point of view, considering that I bet you would keep inside th=
e node attribute top-level TLV the connectivity matrix object, and transfer=
 the informations concerning the OEO ressources to the new top-level TLV th=
at you suggest to name Node Property. I have no hard convinctions on any na=
me, and this one can fit with me, it is not the important thing anyway.
I insist that, what seems more important to me is really to benefit fully f=
rom the advantages brought by introducing a new top-level TLV (which was ap=
parently one of the thinks you were reluctant to do), namely the capability=
 to have one instance of this type per pool. Here a pool, being a consisten=
t bunch of OEO resources, sharing the fact that updating the usage of one o=
f them will have consequences on the accessibility of the others. Which is =
to my mind the smallest information entity that will need a single update o=
n the modification of usage of one of its members, hence the most compliant=
 with scalability.

To summarize, once the cost of introducing a new top-level TLV is accepted,=
 let's use the advantages of the concepts introduced in our solution to the=
ir full extent, and then use a layout of information compliant with that. D=
oes this sems reasonnable for you, and for the WG ?

- pierre

P.S. Let's keep aside right now the discussions concerning the administrati=
ve group, and TE metric sub-TLVs.
________________________________
De : ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] De la part de G=
reg Bernstein
Envoy=E9 : mardi 14 d=E9cembre 2010 19:24
=C0 : CCAMP
Objet : [CCAMP] Top Level TLVs for WSON and General Constraint Extensions t=
o OSPF (long)

Hi all two weeks ago we updated draft-ietf-ccamp-general-constraint-encode =
and draft-ietf-ccamp-rwa-wson-encode based on comments from the list and th=
e Beijing meeting. These changes were editorial in nature and consisted of =
removing some informational text.
To move things forward in general we need to reach agreement on the top lev=
el TLVs to be used to carry this information.  We have two main types of in=
formation: (a) link related, and (b) node related.  In addition, depending =
on the complexity of the system we may want to split the information for a =
particular node or link into multiple LSAs  to keep the size of the LSA bel=
ow a particular limit or to separate rapidly changing node or link informat=
ion from relatively static. In general multiple TE LSA instances provide a =
mechanism for this.

For Link information RFC3630 defines the "Traffic Engineering LSA". This ha=
s area scope.
"One new LSA is defined, the Traffic Engineering LSA.  This LSA describes r=
outers, point-to-point links, and connections to multi-access networks (sim=
ilar to a Router LSA)."

Multiple instances can exist from a single source:
"The Instance field is an arbitrary value used to maintain multiple Traffic=
 Engineering LSAs.  A maximum of 16777216 Traffic Engineering LSAs may be s=
ourced by a single system."

Two top level TLVs are defined: Router Address TLV (section 2.4.1) and Link=
 TLV (section 2.4.2). The router address is just as it says. The link TLV i=
s the generally useful one for us:
"The Link TLV describes a single link.  It is constructed of a set of sub-T=
LVs.  There are no ordering requirements for the sub-TLVs. Only one Link TL=
V shall be carried in each LSA, allowing for fine granularity changes in to=
pology."

There does not appear to be any constraints on breaking up information abou=
t a single link into multiple LSAs. For WSON use we may want to keep static=
 information (port wavelength constraints) separate from dynamic informatio=
n (wavelength availability).

For Node Level information (such as connectivity matrices, resource block i=
nformation, resource block usage state) it seemed like RFC 5786 which has e=
xtensions for advertising a routers local addresses in TE extensions would =
be useful. It defines the OSPF TE LSA Node TLV and they state:
"It is anticipated that the Node Attribute TLV will also prove more general=
ly useful."
However in section 4.2 (Operation) they state:
"The Node Attribute TLV MUST NOT appear in more than one TE LSA originated =
by a router.  Furthermore, such an LSA MUST NOT include more than one Node =
Attribute TLV."

The first of these restrictions on use seems to preclude us from separating=
 traffic matrices, resource block descriptions, and resource block utilizat=
ion status into separate LSA instances using this TLV. Unless this rule can=
 be changed it seems that we will need a new top level "node properties" TL=
V for use in both WSON specific and General constraint extensions to OSPF. =
 Pierre and Giovanni in draft-peloso-ccamp-wson-ospf-oeo-02.txt wanted to d=
efine a new top level TLV for the resource block information, however it se=
ems that we probably should ask for a general "node properties" (or whateve=
r better name we can think of) top level TLV that could be applied to the g=
eneral constraint node information (connectivity matrices) as well as the v=
arious resource related quantities.

Pierre and Giovanni does this sound like a reasonable way forward? Or do yo=
u have a different suggestion.  Comments and suggestions from all are welco=
me.

Best Regards

Greg B.


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



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3Dcontent-type content=3D"text/html; charset=3DISO-8859-1"=
>
<META content=3D"MSHTML 6.00.2900.6036" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D736280910-20122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi Greg,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D736280910-20122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D736280910-20122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>To start with, I am pretty in-line with the part r=
elated to=20
the link TLV, which was already agreed.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D736280910-20122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><SPAN lang=3DFR></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D736280910-20122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><SPAN lang=3DFR>Regarding the node related informa=
tion, I am=20
happy to see that you consider splitting its information over 2 top-level T=
LVs,=20
which we have been proning in order to ease the scalability and the informa=
tion=20
organisation.</SPAN></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D736280910-20122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><SPAN lang=3DFR>I do encourage you to adopt even m=
ore the=20
concepts proned in draft-peloso-ccamp-won-ospf-oeo, by defining this new=20
top-level TLV in a way that allows to have multiple instance of it, one for=
 each=20
conistent entity of ressoruces.</SPAN></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D736280910-20122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><SPAN lang=3DFR></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D736280910-20122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><SPAN lang=3DFR>To detail my point of view, consid=
ering that=20
</SPAN></FONT></SPAN><SPAN class=3D736280910-20122010><FONT face=3DArial=20
color=3D#0000ff size=3D2><SPAN lang=3DFR>I&nbsp;bet you would keep inside t=
he node=20
attribute top-level TLV the connectivity matrix object, and transfer the=20
informations concerning the OEO ressources to the new top-level TLV that yo=
u=20
suggest to name Node Property. I have no hard convinctions on any name, and=
 this=20
one can fit with me, it is not the important thing=20
anyway.</SPAN></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D736280910-20122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><SPAN lang=3DFR>I insist that, what seems more imp=
ortant to=20
me is really to benefit fully from the advantages brought by introducing a =
new=20
top-level TLV (which was apparently one of the thinks you were reluctant to=
 do),=20
namely the capability to have one instance of this&nbsp;type per pool. Here=
 a=20
pool, being a consistent&nbsp;bunch of OEO resources, sharing the fact that=
=20
updating the usage of&nbsp;one of them will have consequences&nbsp;on the=20
accessibility of the others. Which is to my mind the smallest=20
information&nbsp;entity that will need a single update on the modification =
of=20
usage of one of its members, hence the most compliant with=20
scalability.</SPAN></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D736280910-20122010><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><SPAN lang=3DFR></SPAN></FONT></SPAN><SPAN=20
class=3D736280910-20122010><FONT face=3DArial color=3D#0000ff size=3D2><SPA=
N=20
lang=3DFR></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT color=3D#0000ff><FONT =
size=3D2><SPAN=20
class=3D736280910-20122010><SPAN lang=3DFR>To summarize, once the cost of=20
introducing a new top-level TLV is accepted, let's use the advantages of th=
e=20
concepts introduced in our solution to their full extent, and then use a la=
yout=20
of information compliant with that. Does this sems reasonnable for you, and=
 for=20
the WG ?</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT color=3D#0000ff><FONT =
size=3D2><SPAN=20
class=3D736280910-20122010></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial><FONT size=3D2>- p<SPAN=20
class=3D736280910-20122010>ierre</SPAN></FONT></FONT></DIV>
<DIV><SPAN class=3D736280910-20122010><FONT face=3DArial color=3D#0000ff=20
size=3D2>&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=3D736280910-20122010><FONT face=3DArial color=3D#0000ff si=
ze=3D2>P.S.=20
Let's keep aside right now&nbsp;the discussions concerning the administrati=
ve=20
group, and TE metric sub-TLVs.</FONT></SPAN></DIV>
<DIV>
<HR tabIndex=3D-1>
</DIV>
<DIV><FONT face=3DTahoma size=3D2><B>De&nbsp;:</B> ccamp-bounces@ietf.org=20
[mailto:ccamp-bounces@ietf.org] <B>De la part de</B> Greg=20
Bernstein<BR><B>Envoy=E9&nbsp;:</B> mardi 14 d=E9cembre 2010=20
19:24<BR><B>=C0&nbsp;:</B> CCAMP<BR><B>Objet&nbsp;:</B> [CCAMP] Top Level T=
LVs for=20
WSON and General Constraint Extensions to OSPF (long)<BR></FONT><BR></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>Hi all two weeks ago we updated=20
  draft-ietf-ccamp-general-constraint-encode and=20
  draft-ietf-ccamp-rwa-wson-encode based on comments from the list and the=
=20
  Beijing meeting. These changes were editorial in nature and consisted of=
=20
  removing some informational text. <BR>To move things forward in general w=
e=20
  need to reach agreement on the top level TLVs to be used to carry this=20
  information.&nbsp; We have two main types of information: (a) link relate=
d,=20
  and (b) node related.&nbsp; In addition, depending on the complexity of t=
he=20
  system we may want to split the information for a particular node or link=
 into=20
  multiple LSAs&nbsp; to keep the size of the LSA below a particular limit =
or to=20
  separate rapidly changing node or link information from relatively static=
. In=20
  general multiple TE LSA instances provide a mechanism for this.<BR><BR><B=
>For=20
  Link information</B> <B>RFC3630</B> defines the "Traffic Engineering LSA"=
.=20
  This has area scope.<BR>"One new LSA is defined, the Traffic Engineering=
=20
  LSA.&nbsp; This LSA describes routers, point-to-point links, and connecti=
ons=20
  to multi-access networks (similar to a Router LSA)."<BR><BR>Multiple inst=
ances=20
  can exist from a single source:<BR>"The Instance field is an arbitrary va=
lue=20
  used to maintain multiple Traffic Engineering LSAs.&nbsp; A maximum of=20
  16777216 Traffic Engineering LSAs may be sourced by a single=20
  system."<BR><BR>Two top level TLVs are defined: Router Address TLV (secti=
on=20
  2.4.1) and Link TLV (section 2.4.2). The router address is just as it say=
s.=20
  The link TLV is the generally useful one for us:<BR>"The Link TLV describ=
es a=20
  single link.&nbsp; It is constructed of a set of sub-TLVs.&nbsp; There ar=
e no=20
  ordering requirements for the sub-TLVs. Only one Link TLV shall be carrie=
d in=20
  each LSA, allowing for fine granularity changes in topology."<BR><BR>Ther=
e=20
  does not appear to be any constraints on breaking up information about a=
=20
  single link into multiple LSAs. For WSON use we may want to keep static=20
  information (port wavelength constraints) separate from dynamic informati=
on=20
  (wavelength availability).<BR><BR><B>For Node Level information</B> (such=
 as=20
  connectivity matrices, resource block information, resource block usage s=
tate)=20
  it seemed like <B>RFC 5786</B> which has extensions for advertising a rou=
ters=20
  local addresses in TE extensions would be useful. It defines the OSPF TE =
LSA=20
  Node TLV and they state:<BR>"It is anticipated that the Node Attribute TL=
V=20
  will also prove more generally useful."<BR>However in section 4.2 (Operat=
ion)=20
  they state:<BR>"<B><I>The Node Attribute TLV MUST NOT appear in more than=
 one=20
  TE LSA originated by a router</I></B>.&nbsp; Furthermore, such an LSA MUS=
T NOT=20
  include more than one Node Attribute TLV."<BR><BR>The first of these=20
  restrictions on use seems to preclude us from separating traffic matrices=
,=20
  resource block descriptions, and resource block utilization status into=20
  separate LSA instances using this TLV. Unless this rule can be changed it=
=20
  seems that we will need a new top level "node properties" TLV for use in =
both=20
  WSON specific and General constraint extensions to OSPF.&nbsp; Pierre and=
=20
  Giovanni in draft-peloso-ccamp-wson-ospf-oeo-02.txt wanted to define a ne=
w top=20
  level TLV for the resource block information, however it seems that we=20
  probably should ask for a general "node properties" (or whatever better n=
ame=20
  we can think of) top level TLV that could be applied to the general const=
raint=20
  node information (connectivity matrices) as well as the various resource=
=20
  related quantities.&nbsp; <BR><BR>Pierre and Giovanni does this sound lik=
e a=20
  reasonable way forward? Or do you have a different suggestion.&nbsp; Comm=
ents=20
  and suggestions from all are welcome.<BR><BR>Best Regards<BR><BR>Greg=20
  B.<BR><BR><PRE class=3Dmoz-signature cols=3D"72">--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
Dr Greg Bernstein, Grotto Networking (510) 573-2237

</PRE></BLOCKQUOTE></BODY></HTML>

--_000_CCBFBB7025DF984494DEC3285C0581521269ED11D9FRMRSSXCHMBSA_--

From Attila.Takacs@ericsson.com  Mon Dec 20 06:57:01 2010
Return-Path: <Attila.Takacs@ericsson.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C1F53A6A48 for <ccamp@core3.amsl.com>; Mon, 20 Dec 2010 06:57:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h5YG9DHan0Xg for <ccamp@core3.amsl.com>; Mon, 20 Dec 2010 06:56:59 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id B05213A6A53 for <ccamp@ietf.org>; Mon, 20 Dec 2010 06:56:56 -0800 (PST)
X-AuditID: c1b4fb39-b7cfbae000005c8e-f3-4d0f6f29bec0
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 25.9A.23694.92F6F0D4; Mon, 20 Dec 2010 15:58:49 +0100 (CET)
Received: from ESESSCMS0365.eemea.ericsson.se ([169.254.1.32]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Mon, 20 Dec 2010 15:58:48 +0100
From: Attila Takacs <Attila.Takacs@ericsson.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'CCAMP' <ccamp@ietf.org>
Date: Mon, 20 Dec 2010 15:58:46 +0100
Thread-Topic: [CCAMP] WG Last Call on draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-00.txt
Thread-Index: AcudaZY7XiXn4qqGQaWUN9hHDUWnKQC7EqPA
Message-ID: <6477E10CC7D76444A479B9AC31F262A9DA81262E@ESESSCMS0365.eemea.ericsson.se>
References: <054601cb9d69$a0c20d70$e2462850$@olddog.co.uk>
In-Reply-To: <054601cb9d69$a0c20d70$e2462850$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [CCAMP] WG Last Call on	draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-00.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Dec 2010 14:57:01 -0000

Hi Adrian,
Please see inline [at].
Thanks,
Attila=20

-----Original Message-----
From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of A=
drian Farrel
Sent: Thursday, December 16, 2010 10:39 PM
To: 'CCAMP'
Subject: Re: [CCAMP] WG Last Call on draft-ietf-ccamp-asymm-bw-bidir-lsps-b=
is-00.txt

Hi,

Can I get in an early question about how this relates to RFC 5467?

Is it you intention that the 5467 Experiment should remain in place, or do =
you want to replace it with this document?=20

[at] Replace with this document.

The text says:
   This document
   has no technical changes from the approach defined in [RFC5467].
   This document removes an alternate approach that is not part of the
   Standards Track solution.

So the question is whether the (mystery) alternate approach that is removed=
 is to remain as experimental or is completely discarded.

[at] Discard.

If you are replacing 5467 (which I hope is the case), the document needs to=
 say
so:
1. Header should include "Obsoletes: 5467 (if approved)"
2. Abstract should say "This document moves the experiment documented in RF=
C
5467 to the standards track and obsoletes RFC 5467."
3. The Introduction should include a similar statement.
4. Somewhere in the document you need to explain which piece has been left =
out from 5467 and why.

[at] Ok agreed. Is it ok to update the doc with the above after the WG LC e=
nded and handle this with possible other comments received?


If you are wanting to do something more complicated with keeping the experi=
ment alive, but also standardising part of the material, you will have to a=
sk your AD how to do this (because I don't know! :-).

I guess the authors and the WG can discuss what exactly the intention is, a=
nd update the document accordingly.

Thanks,
Adrian

> -----Original Message-----
> From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf=20
> Of BRUNGARD, DEBORAH A (ATTLABS)
> Sent: 16 December 2010 19:54
> To: CCAMP
> Subject: [CCAMP] WG Last Call on=20
> draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-
> 00.txt
>=20
> All,
>=20
> This is to start a three-week (extended for the holidays) working=20
> group last call on draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-00.txt.
>=20
> This working group last call ends Jan. 6. Please send your comments to=20
> the CCAMP mailing list.
>=20
> Deborah (and Lou)
>=20
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp

_______________________________________________
CCAMP mailing list
CCAMP@ietf.org
https://www.ietf.org/mailman/listinfo/ccamp

From ylee@huawei.com  Mon Dec 20 12:47:49 2010
Return-Path: <ylee@huawei.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 450BC3A68C7 for <ccamp@core3.amsl.com>; Mon, 20 Dec 2010 12:47:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9mV4twmMYv0i for <ccamp@core3.amsl.com>; Mon, 20 Dec 2010 12:47:48 -0800 (PST)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 62EB13A68C3 for <ccamp@ietf.org>; Mon, 20 Dec 2010 12:47:48 -0800 (PST)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LDQ0021RV6UHE@usaga01-in.huawei.com> for ccamp@ietf.org; Mon, 20 Dec 2010 12:49:42 -0800 (PST)
Received: from L73682 (pool-96-226-231-54.dllstx.fios.verizon.net [96.226.231.54]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LDQ00LYFV6TK3@usaga01-in.huawei.com> for ccamp@ietf.org; Mon, 20 Dec 2010 12:49:42 -0800 (PST)
Date: Mon, 20 Dec 2010 14:49:39 -0600
From: Young Lee <ylee@huawei.com>
To: ccamp@ietf.org
Message-id: <00aa01cba087$6be06bd0$6600a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/mixed; boundary="Boundary_(ID_tJtO9Oza7cX4LyKlRVBsyA)"
Thread-index: AcueQL3SVyLSjAmTQzivNhRLXwSUGACP37VA
Subject: [CCAMP] FW: I-D Action:draft-ietf-ccamp-rwa-wson-framework-08.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Dec 2010 20:47:49 -0000

This is a multi-part message in MIME format.

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

Hi CCAMPers,

We have published 08 version of WSON Framework draft per WG co-chairs
comments as part of Shepherding Process. Here's the summary of the changes:

>From Version 7 to Version 8:
---------------------------

- Global changes on key terms: "lightpaths" -> "optical paths"; "The RWA
problem" -> RWA; "side" -> "tributary"
- Extensive editorial changes for clarity and choice of words in Section 4,
Section 4.1.3, and Section 6.1.6. 
- Moved RFC4465 from Informative reference to Normative reference in
Reference Section
- Moved references [G.694.1], [WSON-Compat], [WSON-Encode], (WSON-Imp],
[WSON-Info] to Normative Reference Section


>From Version 6 to Version 7:
---------------------------

- Global editorials on grammar, punctuation, and style 
- Eliminated all texts that reference academic papers
- Shortened Abstract and moved up the Abstract in the beginning of document
- Moved document history to the Appendix at the end of the document
- Clarified the wordings in Introduction 
- Terminology Changes:
	- Added "Tributary", "Line Side", "Degree" and "Drop and continue"
      - Globally changed "ingress/egress" to "input/output"
- Section 3.2, the title changed from "Optical Transmitters" to "Optical
Transmitters and Receivers" 
- Figure 7 title is added in Section 5.1
- Added RFC3945 in the Reference Section
- Deleted all academic papers from the Reference Section

Appendix will be removed in the next update. 

If you have any question, please let me know. Thanks. 

Best Regards,
Young
-----Original Message-----
From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of
Internet-Drafts@ietf.org
Sent: Friday, December 17, 2010 5:15 PM
To: i-d-announce@ietf.org
Cc: ccamp@ietf.org
Subject: [CCAMP] I-D Action:draft-ietf-ccamp-rwa-wson-framework-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           : Framework for GMPLS and PCE Control of Wavelength
Switched Optical Networks (WSON)
	Author(s)       : G. Bernstein, et al.
	Filename        : draft-ietf-ccamp-rwa-wson-framework-08.txt
	Pages           : 56
	Date            : 2010-12-17

This document provides a framework for applying Generalized Multi-
Protocol Label Switching (GMPLS) and the Path Computation Element
(PCE) architecture to the control of wavelength switched optical
networks (WSON).  In particular, it examines Routing and Wavelength
Assignment (RWA) of optical paths.

This document focuses on topological elements and path selection
constraints that are common across different WSON environments as
such it does not address optical impairments in any depth.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-rwa-wson-framework-08.t
xt

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

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

--Boundary_(ID_tJtO9Oza7cX4LyKlRVBsyA)
Content-type: Message/External-body;
 name=draft-ietf-ccamp-rwa-wson-framework-08.txt
Content-transfer-encoding: 7bit
Content-disposition: attachment;
 filename=draft-ietf-ccamp-rwa-wson-framework-08.txt

Content-Type: text/plain
Content-ID: <2010-12-17150419.I-D@ietf.org>


--Boundary_(ID_tJtO9Oza7cX4LyKlRVBsyA)
Content-type: text/plain; name=ATT00008.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=ATT00008.txt

_______________________________________________
CCAMP mailing list
CCAMP@ietf.org
https://www.ietf.org/mailman/listinfo/ccamp

--Boundary_(ID_tJtO9Oza7cX4LyKlRVBsyA)--

From adrian@olddog.co.uk  Tue Dec 21 07:47:12 2010
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 514CB3A6B27 for <ccamp@core3.amsl.com>; Tue, 21 Dec 2010 07:47:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.854
X-Spam-Level: 
X-Spam-Status: No, score=-1.854 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VWM645+Xji-V for <ccamp@core3.amsl.com>; Tue, 21 Dec 2010 07:47:11 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by core3.amsl.com (Postfix) with ESMTP id 393143A69F7 for <ccamp@ietf.org>; Tue, 21 Dec 2010 07:47:11 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id oBLFn46T016255;  Tue, 21 Dec 2010 15:49:04 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id oBLFn1RO016227;  Tue, 21 Dec 2010 15:49:03 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Attila Takacs'" <Attila.Takacs@ericsson.com>, "'CCAMP'" <ccamp@ietf.org>
References: <054601cb9d69$a0c20d70$e2462850$@olddog.co.uk> <6477E10CC7D76444A479B9AC31F262A9DA81262E@ESESSCMS0365.eemea.ericsson.se>
In-Reply-To: <6477E10CC7D76444A479B9AC31F262A9DA81262E@ESESSCMS0365.eemea.ericsson.se>
Date: Tue, 21 Dec 2010 15:49:05 -0000
Message-ID: <039b01cba126$9994dc10$ccbe9430$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-index: AQLjKcbH9Fi9GGXrVTeH4Iz/PcMMmgHpfcSokWyscJA=
Content-language: en-gb
Subject: Re: [CCAMP] WG Last Call on	draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-00.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Dec 2010 15:47:12 -0000

> [at] Ok agreed. Is it ok to update the doc with the above after the WG LC
ended
> and handle this with possible other comments received?

You should wait until after WG last call completes.

A


From lberger@labn.net  Thu Dec 23 06:56:31 2010
Return-Path: <lberger@labn.net>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 517503A67EB for <ccamp@core3.amsl.com>; Thu, 23 Dec 2010 06:56:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.058
X-Spam-Level: 
X-Spam-Status: No, score=-102.058 tagged_above=-999 required=5 tests=[AWL=0.207, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2GEpz16lSQYu for <ccamp@core3.amsl.com>; Thu, 23 Dec 2010 06:56:30 -0800 (PST)
Received: from oproxy2-pub.bluehost.com (oproxy2-pub.bluehost.com [67.222.39.60]) by core3.amsl.com (Postfix) with SMTP id 4614B3A67E5 for <ccamp@ietf.org>; Thu, 23 Dec 2010 06:56:30 -0800 (PST)
Received: (qmail 25011 invoked by uid 0); 23 Dec 2010 14:58:29 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy2.bluehost.com with SMTP; 23 Dec 2010 14:58:29 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=zbxInQjlI+t7PedaHmN++daDzTpZALuE2wBSkTXHcCThWBjK7Nirmd2N4RFiaLRm4ACQKRcPLJa6hBSd1nxhkmCe/rGOjs3VdHBa1ls2ckaP4e+zv7uu0o+U698lpTSh;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1PVmcf-0000uY-E8 for ccamp@ietf.org; Thu, 23 Dec 2010 07:58:29 -0700
Message-ID: <4D136395.7040606@labn.net>
Date: Thu, 23 Dec 2010 09:58:29 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: CCAMP <ccamp@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Subject: [CCAMP] 2nd WG LC on draft-ietf-ccamp-rwa-wson-framework
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Dec 2010 14:56:31 -0000

All,

This mail begins a second working group last call on:
http://tools.ietf.org/html/draft-ietf-ccamp-rwa-wson-framework-08.  The 
last call ends on January 7th (slight extension due to holidays.)

Note this second last call is being held due to the changes in the draft 
since it was (1st) last called.  The authors have provided a summary of 
changes in:
http://www.ietf.org/mail-archive/web/ccamp/current/msg11765.html

LC reviews/comments should focus on the modified text.

Please send your comments to the CCAMP mailing list.

Lou (and Deborah)


