IETF Logo Mail Archive

Re: [Teas] Update on <draft-ietf-teas-network-assigned-upstream-label>

"Zhangxian (Xian)" <zhang.xian@huawei.com> Fri, 20 March 2015 07:45 UTC

Return-Path: <zhang.xian@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73F031B2C6A for <teas@ietfa.amsl.com>; Fri, 20 Mar 2015 00:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 EbBBjBjmTZpY for <teas@ietfa.amsl.com>; Fri, 20 Mar 2015 00:45:17 -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 ECAE01B2C69 for <teas@ietf.org>; Fri, 20 Mar 2015 00:45:13 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTX15880; Fri, 20 Mar 2015 07:44:33 +0000 (GMT)
Received: from SZXEMA414-HUB.china.huawei.com (10.82.72.73) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 20 Mar 2015 07:44:32 +0000
Received: from SZXEMA512-MBS.china.huawei.com ([169.254.8.171]) by SZXEMA414-HUB.china.huawei.com ([10.82.72.73]) with mapi id 14.03.0158.001; Fri, 20 Mar 2015 15:44:30 +0800
From: "Zhangxian (Xian)" <zhang.xian@huawei.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Thread-Topic: [Teas] Update on <draft-ietf-teas-network-assigned-upstream-label>
Thread-Index: AQHQYnvfaKUHfhGyQ0KAGqtWg0kKZJ0kj6tQ
Date: Fri, 20 Mar 2015 07:44:29 +0000
Message-ID: <C636AF2FA540124E9B9ACB5A6BECCE6B471AB716@SZXEMA512-MBS.china.huawei.com>
References: <CA+YzgTsfE9nEmL+SnDStaiko_+wBTGDa5W=0vm9WqJwHFc8cjQ@mail.gmail.com>
In-Reply-To: <CA+YzgTsfE9nEmL+SnDStaiko_+wBTGDa5W=0vm9WqJwHFc8cjQ@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.104.209]
Content-Type: multipart/alternative; boundary="_000_C636AF2FA540124E9B9ACB5A6BECCE6B471AB716SZXEMA512MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/vRL-qTbdHEMqv25PzIu1y_N9IdM>
Cc: "draft-ietf-teas-network-assigned-upstream-label@tools.ietf.org" <draft-ietf-teas-network-assigned-upstream-label@tools.ietf.org>, "teas@ietf.org" <teas@ietf.org>
Subject: Re: [Teas] Update on <draft-ietf-teas-network-assigned-upstream-label>
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Mar 2015 07:45:18 -0000

Hi, Pavan,

Thank you for the update.

Could you explain a bit the motivation of this update? Since now it is SHOULD not MUST; so with a good reason, the ingress/egress can choose to ignore such label modify received from the other end, by not tuning the new wavelength, will it be any issue? Any additional texts needed to handle it?

  I will send more detailed review comments probably after this IETF.

Regards,
Xian

From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Vishnu Pavan Beeram
Sent: 2015年3月20日 3:35
To: teas@ietf.org; draft-ietf-teas-network-assigned-upstream-label@tools.ietf.org
Subject: [Teas] Update on <draft-ietf-teas-network-assigned-upstream-label>

WG, Hi!
Latest Update:
A new version was published recently. The following are the diffs -

     *   Section 6.2 - Change MUST->SHOULD

        *   “In such a scenario, if the ingress client receives a changed label via the LABEL object in a RESV modify, it SHOULD retune the laser at the ingress to the new wavelength. Similarly if the egress client receives a changed label via UPSTREAM_LABEL/LABEL_SET in a PATH modify, it SHOULD retune the laser at the egress to the new wavelength.”

     *   Added Zafar Ali to the list of contributors
Open Issues:
None.
Next Steps:
Request further review from the WG (authors believe that the draft is ready to progress to the next stage)

Regards,
-Pavan
(On behalf of the authors/contributors)

v2.23.0 | Report a Bug | By Email