Re: [Pce] Update in ID: draft-dhody-pce-pcep-domain-sequence
Zhangfatai <zhangfatai@huawei.com> Fri, 21 October 2011 03:55 UTC
Return-Path: <zhangfatai@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17C1921F8A35 for <pce@ietfa.amsl.com>; Thu, 20 Oct 2011 20:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.094
X-Spam-Level:
X-Spam-Status: No, score=-4.094 tagged_above=-999 required=5 tests=[AWL=-1.699, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id htAdu1bctqtc for <pce@ietfa.amsl.com>; Thu, 20 Oct 2011 20:55:36 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 8E65221F891D for <pce@ietf.org>; Thu, 20 Oct 2011 20:55:35 -0700 (PDT)
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 <0LTE00E15DK10A@szxga04-in.huawei.com> for pce@ietf.org; Fri, 21 Oct 2011 11:55:13 +0800 (CST)
Received: from szxrg01-dlp.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 <0LTE00JX0DK1WV@szxga04-in.huawei.com> for pce@ietf.org; Fri, 21 Oct 2011 11:55:13 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AEP24640; Fri, 21 Oct 2011 11:55:08 +0800
Received: from SZXEML409-HUB.china.huawei.com (10.82.67.136) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 21 Oct 2011 11:55:03 +0800
Received: from SZXEML520-MBX.china.huawei.com ([169.254.1.196]) by szxeml409-hub.china.huawei.com ([10.82.67.136]) with mapi id 14.01.0270.001; Fri, 21 Oct 2011 11:55:01 +0800
Date: Fri, 21 Oct 2011 03:55:00 +0000
From: Zhangfatai <zhangfatai@huawei.com>
In-reply-to: <23CE718903A838468A8B325B80962F9BB65844@SZXEML520-MBX.china.huawei.com>
X-Originating-IP: [10.70.76.157]
To: Dhruv Dhody <dhruv.dhody@huawei.com>, "pce@ietf.org" <pce@ietf.org>
Message-id: <F82A4B6D50F9464B8EBA55651F541CF825C877C0@SZXEML520-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_vVJWJ7MXcQKM03qn7XBf+A)"
Content-language: en-US
Accept-Language: zh-CN, en-US
Thread-topic: Update in ID: draft-dhody-pce-pcep-domain-sequence
Thread-index: AcxxOKGkuTRlAQXDT8SZMz6PceJEHAeaMZWA
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
References: <23CE718903A838468A8B325B80962F9BB65844@SZXEML520-MBX.china.huawei.com>
Subject: Re: [Pce] Update in ID: draft-dhody-pce-pcep-domain-sequence
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Oct 2011 03:55:37 -0000
Hi Dhruv and all, You may notice the mail from Ramon about [HPCE- PCEP-EXT], which raised a point about the format of the Domain-ID TLV. We also put a editors’ note in section 3.1.3 to capture this issue. In [HPCE- PCEP-EXT] draft, we defined the Domain-ID TLV which has the same format as PCE-DOMAIN sub-TLV format defined in RFC5088, but we did not notice that the length of ISIS area ID should be variable. So, we need to refine the format as follows at least (just my suggestions): 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Domain Type | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ // Domain ID // +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type=1: an AS number (4 bytes) Type=2: OSPF area ID (4 bytes) Type=3: ISIS area ID, the length is variable Note that this Domain-ID TLV can be included in many PCEP objects like OPEN, NOTIFICATION, RP objects. As for [draft-dhody], the sub-objects extended in this draft is for IRO, which has the same format of ERO. So I think it is better to have this draft to follow the RSVP sub-objects format. In summary, I think the Domain ID TLV can be defined as defined in [HPCE- PCEP-EXT] (with some refinement), IRO subject extension can be defined as defined in [draft-dhody]. What are your opinions? Thanks Fatai From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of Dhruv Dhody Sent: 2011年9月12日 18:50 To: pce@ietf.org Subject: [Pce] Update in ID: draft-dhody-pce-pcep-domain-sequence Dear All, We have rolled out a new version for DOMAIN-SEQ draft. http://tools.ietf.org/html/draft-dhody-pce-pcep-domain-sequence-01 Main Changes done: * Alignment for the new sub-objects * Support for 4 byte AS number We are still awaiting comments/suggestions in WG regarding * New IRO Class Type for domain Sequence * Use of RBNF to explain Subobjects ordering within domain-sequence(IRO Object) For more information refer Message Thread: http://www.ietf.org/mail-archive/web/pce/current/msg02580.html We plan to resolve this before/during the next IETF meeting. Regards, Dhruv ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Dhruv Dhody Senior Technical Leader, Huawei Technologies India Pvt. Ltd., Bangalore, India. Ph +91-9845062422 This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------