Re: [RTG-DIR] RtgDir review: draft-ietf-ccamp-gmpls-g-694-lambda-labels-10.txt

Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp> Fri, 31 December 2010 15:02 UTC

Return-Path: <takeda.tomonori@lab.ntt.co.jp>
X-Original-To: rtg-dir@core3.amsl.com
Delivered-To: rtg-dir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA8423A6931 for <rtg-dir@core3.amsl.com>; Fri, 31 Dec 2010 07:02:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.09
X-Spam-Level:
X-Spam-Status: No, score=-100.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, 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 pu7tuVFf0zRT for <rtg-dir@core3.amsl.com>; Fri, 31 Dec 2010 07:02:04 -0800 (PST)
Received: from tama500.ecl.ntt.co.jp (tama500.ecl.ntt.co.jp [129.60.39.148]) by core3.amsl.com (Postfix) with ESMTP id C27373A6923 for <rtg-dir@ietf.org>; Fri, 31 Dec 2010 07:02:03 -0800 (PST)
Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149]) by tama500.ecl.ntt.co.jp (8.14.4/8.14.4) with ESMTP id oBVF3p53019910; Sat, 1 Jan 2011 00:03:51 +0900 (JST)
Received: from mfs6.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id E5FBB65F9; Sat, 1 Jan 2011 00:03:50 +0900 (JST)
Received: from imail2.m.ecl.ntt.co.jp (imail2.m.ecl.ntt.co.jp [129.60.5.247]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id E089865EB; Sat, 1 Jan 2011 00:03:50 +0900 (JST)
Received: from imf.m.ecl.ntt.co.jp (webmail.ecl.ntt.co.jp [129.60.39.130]) by imail2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with SMTP id oBVF3oAA008419; Sat, 1 Jan 2011 00:03:50 +0900
Message-Id: <201012311503.oBVF3oAA008419@imail2.m.ecl.ntt.co.jp>
To: danli@huawei.com
From: Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp>
Date: Sat, 01 Jan 2011 00:03:50 +0900
In-Reply-To: <011d01cba8ba$da07f890$7d4d460a@china.huawei.com>
X-Mailer: WebMail V3.7 PL3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: rtg-dir@ietf.org, draft-ietf-ccamp-gmpls-g-694-lambda-labels.all@tools.ietf.org, rtg-ads@tools.ietf.org
Subject: Re: [RTG-DIR] RtgDir review: draft-ietf-ccamp-gmpls-g-694-lambda-labels-10.txt
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-dir>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Dec 2010 15:02:04 -0000

Hi Dan,

Thanks for your reply.

The proposed text is good for me.

Tomonori

> Hi Tomonori,
> 
> Thanks for your comments! I would like to update the description of Identifier in section 3.2 and 3.3.
> 
> OLD
>    (3) Identifier: 9 bits
> 
>    The identifier field is a per-node assigned and scoped value. This
>    field MAY change on a per-hop basis. In all cases but one, a node MAY
>    select any value, including zero (0), for this field. Once selected,
>    the value MUST NOT change until the LSP is torn down and the value
>    MUST be used in all LSP related messages, e.g., in Resv messages and
>    label RRO subobjects. The sole special case occurs when this label
>    format is used in a label ERO subobject. In this case, the special
>    value of zero (0) means that the referenced node MAY assign any
>    Identifier field value, including zero (0), when establishing the
>    corresponding LSP.
> NEW
>    (3) Identifier: 9 bits
> 
>    The identifier field in lambda label format is used to distinguish different 
>    lasers (in one node) when they can transmit the same frequency lambda.
>    The identifier field is a per-node assigned and scoped value. This
>    field MAY change on a per-hop basis. In all cases but one, a node MAY
>    select any value, including zero (0), for this field. Once selected,
>    the value MUST NOT change until the LSP is torn down and the value
>    MUST be used in all LSP related messages, e.g., in Resv messages and
>    label RRO subobjects. The sole special case occurs when this label
>    format is used in a label ERO subobject. In this case, the special
>    value of zero (0) means that the referenced node MAY assign any
>    Identifier field value, including zero (0), when establishing the
>    corresponding LSP. When non-zero value is assigned to the identifier 
>    field in a label ERO subobject, the referenced node MUST use the 
>    assigned value for the identifier field in the corresponding LSP related 
>    messages.
> 
> Is this ok?
> 
> Thanks,
> 
> Dan
>