Re: [CCAMP] Backward compatibility for Availability sub-TLV
"Yemin (Amy)" <amy.yemin@huawei.com> Wed, 02 July 2014 07:30 UTC
Return-Path: <amy.yemin@huawei.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72D891A0AA1 for <ccamp@ietfa.amsl.com>; Wed, 2 Jul 2014 00:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level:
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1UrEVgmFnVfK for <ccamp@ietfa.amsl.com>; Wed, 2 Jul 2014 00:30:05 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BCE51A040B for <ccamp@ietf.org>; Wed, 2 Jul 2014 00:30:04 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BGR97520; Wed, 02 Jul 2014 07:30:03 +0000 (GMT)
Received: from SZXEMA401-HUB.china.huawei.com (10.82.72.33) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 2 Jul 2014 08:30:02 +0100
Received: from SZXEMA506-MBS.china.huawei.com ([169.254.4.76]) by SZXEMA401-HUB.china.huawei.com ([10.82.72.33]) with mapi id 14.03.0158.001; Wed, 2 Jul 2014 15:29:52 +0800
From: "Yemin (Amy)" <amy.yemin@huawei.com>
To: Fatai Zhang <zhangfatai@huawei.com>, Gregory Mirsky <gregory.mirsky@ericsson.com>, "CCAMP (ccamp@ietf.org)" <ccamp@ietf.org>
Thread-Topic: Backward compatibility for Availability sub-TLV
Thread-Index: Ac+O7u90aym7H5uoQvO3hZMzL1AZewBYoRcgAV0tjqA=
Date: Wed, 02 Jul 2014 07:29:51 +0000
Message-ID: <9C5FD3EFA72E1740A3D41BADDE0B461F73D920C7@szxema506-mbs.china.huawei.com>
References: <7347100B5761DC41A166AC17F22DF1121B7E0051@eusaamb103.ericsson.se> <F82A4B6D50F9464B8EBA55651F541CF85CB34888@SZXEMA504-MBS.china.huawei.com>
In-Reply-To: <F82A4B6D50F9464B8EBA55651F541CF85CB34888@SZXEMA504-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.169.33.63]
Content-Type: multipart/alternative; boundary="_000_9C5FD3EFA72E1740A3D41BADDE0B461F73D920C7szxema506mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/xuBbmSPLx3hf_FM7jnRuSf3Qu-s
Subject: Re: [CCAMP] Backward compatibility for Availability sub-TLV
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 02 Jul 2014 07:30:07 -0000
Hi all, I also prefer the second approach. The first approach seems not to resolve the backward issues, unless all the legacy nodes are updated to accept the new length of Ethernet BW Profile TLV. And on the other side, the Availability TLV extension is only for links with variable discrete bandwidth. Thus I feel it might be not suitable to define the Availability TLV MUST be accompanied with Ethernet BW Profile TLV. Will update the draft following by the second approach. Any more comments are welcome. BR, Amy From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of Fatai Zhang Sent: Wednesday, June 25, 2014 4:55 PM To: Gregory Mirsky; CCAMP (ccamp@ietf.org) Subject: Re: [CCAMP] Backward compatibility for Availability sub-TLV Hi Greg, I think there were some similar discussions on Bandwidth encoding for [draft-ietf-pce-gmpls-pcep-extensionsin] in PCE WG. Per RFC3471, Bandwidth encodings are carried in 32 bit number in IEEE floating point format. There were lots of discussions on how to encode the accurate bandwidth information for the transport networks. Consequently, two new types of Bandwidth are being defined in [draft-ietf-pce-gmpls-pcep-extensionsin], which are variable. Therefore, I would prefer to introduce a new type of BW Profile, which should be the second option you mentioned below if my understanding is correct on your options. Best Regards Fatai From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of Gregory Mirsky Sent: Monday, June 23, 2014 10:34 PM To: CCAMP (ccamp@ietf.org<mailto:ccamp@ietf.org>) Subject: [CCAMP] Backward compatibility for Availability sub-TLV Dear All, on behalf of authors of the RSVP-TE Signaling Extension for Links with Variable Discrete Bandwidth would like to ask for expert opinion. The Availability sub-TLV defined in the draft as a sub-TLV under Ethernet bandwidth profile. The length field in the Ethernet bandwidth profile will be different from the current definition(24), which might cause some backward issues. Possible way to address this problem: * define Availability as TLV that MUST be accompanied by Ethernet BW Profile TLV; * define Extended Ethernet BW Profile TLV that includes Ethernet BW TLV and has variable length. Definition of Availability characteristics remains as sub-TLV which MAY be included into Extended Ethernet BW Profile TLV. Regards, Greg
- [CCAMP] Backward compatibility for Availability s… Gregory Mirsky
- Re: [CCAMP] Backward compatibility for Availabili… Fatai Zhang
- Re: [CCAMP] Backward compatibility for Availabili… Yemin (Amy)