[Teas] 答复: Last Call: <draft-ietf-teas-yang-te-types-09.txt> (Traffic Engineering Common YANG Types) to Proposed Standard

"Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)" <zhenghaomian@huawei.com> Thu, 30 May 2019 01:29 UTC

Return-Path: <zhenghaomian@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7E93120148; Wed, 29 May 2019 18:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 mqo9c8LaDsdU; Wed, 29 May 2019 18:29:41 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 888FE1200B9; Wed, 29 May 2019 18:29:41 -0700 (PDT)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 9F8C429DCBFC13776787; Thu, 30 May 2019 02:29:39 +0100 (IST)
Received: from lhreml709-chm.china.huawei.com (10.201.108.58) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 30 May 2019 02:29:39 +0100
Received: from lhreml709-chm.china.huawei.com (10.201.108.58) by lhreml709-chm.china.huawei.com (10.201.108.58) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 30 May 2019 02:29:39 +0100
Received: from DGGEML423-HUB.china.huawei.com (10.1.199.40) by lhreml709-chm.china.huawei.com (10.201.108.58) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Thu, 30 May 2019 02:29:38 +0100
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.177]) by dggeml423-hub.china.huawei.com ([10.1.199.40]) with mapi id 14.03.0439.000; Thu, 30 May 2019 09:29:35 +0800
From: "Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)" <zhenghaomian@huawei.com>
To: "Belotti, Sergio (Nokia - IT/Vimercate)" <sergio.belotti@nokia.com>, "Tarek Saad" <tsaad.net@gmail.com>, tom petch <daedulus@btconnect.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "draft-ietf-teas-yang-te-types@ietf.org" <draft-ietf-teas-yang-te-types@ietf.org>, "teas-chairs@ietf.org" <teas-chairs@ietf.org>, "db3546@att.com" <db3546@att.com>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] Last Call: <draft-ietf-teas-yang-te-types-09.txt> (Traffic Engineering Common YANG Types) to Proposed Standard
Thread-Index: AQHVFg5bAZ/LRMx4EECumIZrLHrmtqaBubyAgAAHsgCAAR4MoA==
Date: Thu, 30 May 2019 01:29:34 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43B7E3948@dggeml511-mbx.china.huawei.com>
References: <155683002335.24918.14137794782361366345.idtracker@ietfa.amsl.com> <062101d5160d$a43329a0$4001a8c0@gateway.2wire.net> <BL0PR06MB432164D1D18082741254374BFC1F0@BL0PR06MB4321.namprd06.prod.outlook.com> <HE1PR07MB319577BFE760FEF0E501D8B3911F0@HE1PR07MB3195.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB319577BFE760FEF0E501D8B3911F0@HE1PR07MB3195.eurprd07.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.57.78.212]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/3uLF8yy9cV1Y-dbu4RgoGydWyUI>
Subject: [Teas] =?utf-8?b?562U5aSNOiAgTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi10?= =?utf-8?q?eas-yang-te-types-09=2Etxt=3E_=28Traffic_Engineering_Common_YAN?= =?utf-8?q?G_Types=29_to_Proposed_Standard?=
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 30 May 2019 01:29:44 -0000

Hi, Tarek, Tom, Sergio, 

This draft has been adopted in CCAMP a few months ago, the latest can be found at https://tools.ietf.org/html/draft-ietf-ccamp-gmpls-otn-b100g-applicability. Technically it's not different with the I-D -01. 

Regarding the identity oducn, the best reference should be ITU-T G.709-2016 if we want to keep it, or we can also use ccamp draft as an alternative reference. It would be even simpler if we remove the identity. 

Thanks. 

Best wishes,
Haomian


-----邮件原件-----
发件人: Teas [mailto:teas-bounces@ietf.org] 代表 Belotti, Sergio (Nokia - IT/Vimercate)
发送时间: 2019年5月30日 0:16
收件人: Tarek Saad <tsaad.net@gmail.com>;; tom petch <daedulus@btconnect.com>;; ietf@ietf.org
抄送: draft-ietf-teas-yang-te-types@ietf.org; teas-chairs@ietf.org; db3546@att.com; teas@ietf.org
主题: Re: [Teas] Last Call: <draft-ietf-teas-yang-te-types-09.txt> (Traffic Engineering Common YANG Types) to Proposed Standard

Hi Tarek, Tom,
For ODUCn and all so said OTN part "beyond 100G" the most updated reference in IETF is https://www.ietf.org/id/draft-merge-ccamp-gmpls-otn-b100g-applicability-01.txt

There are no further signaling extension document since in this document is stated that for the applicability scenarios addressed no further extension is needed. 

Thanks
Sergio


-----Original Message-----
From: Teas <teas-bounces@ietf.org>; On Behalf Of Tarek Saad
Sent: Wednesday, May 29, 2019 5:49 PM
To: tom petch <daedulus@btconnect.com>;; ietf@ietf.org
Cc: draft-ietf-teas-yang-te-types@ietf.org; teas-chairs@ietf.org; teas@ietf.org; db3546@att.com
Subject: Re: [Teas] Last Call: <draft-ietf-teas-yang-te-types-09.txt> (Traffic Engineering Common YANG Types) to Proposed Standard

Hi Tom,

You are right. ODUCn is introduced in ITU-T G709-2016 - RFC7139 only covered G709-2012.
I noticed some expired IETF I-D(s) tried to bring in support for ODUCn but aborted: draft-merge-ccamp-otn-b100g-fwk and draft-ali-ccamp-oducn-signal-type.
I will discuss with authors to remove this identity from those defined in this document.

Regards,
Tarek

On 5/29/19, 7:04 AM, "Teas on behalf of tom petch" <teas-bounces@ietf.org on behalf of daedulus@btconnect.com>; wrote:

    One of the identities defined herein is
    ODUCn
    with a reference of RFC7139.
    
    I see no mention of ODUCn in RFC 7139 nor can I find it in the IANA
    registries for GMPLS
    
    Tom Petch
    
    
    ----- Original Message -----
    From: "The IESG" <iesg-secretary@ietf.org>;
    To: "IETF-Announce" <ietf-announce@ietf.org>;
    Cc: <draft-ietf-teas-yang-te-types@ietf.org>;; <teas-chairs@ietf.org>;;
    <teas@ietf.org>;; <db3546@att.com>;
    Sent: Thursday, May 02, 2019 9:47 PM
    Subject: Last Call: <draft-ietf-teas-yang-te-types-09.txt> (Traffic
    Engineering Common YANG Types) to Proposed Standard
    
    
    >
    > The IESG has received a request from the Traffic Engineering
    Architecture and
    > Signaling WG (teas) to consider the following document: - 'Traffic
    > Engineering Common YANG Types'
    >   <draft-ietf-teas-yang-te-types-09.txt> as 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 2019-05-16. 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.
    >
    > Abstract
    >
    >
    >    This document defines a collection of common data types and
    groupings
    >    in YANG data modeling language.  These derived common types and
    >    groupings are intended to be imported by modules that model Traffic
    >    Engineering (TE) configuration and state capabilities.
    >
    >
    >
    >
    > The file can be obtained via
    > https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-types/
    >
    > IESG discussion can be tracked via
    > https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-types/ballot/
    >
    >
    > No IPR declarations have been submitted directly on this I-D.
    >
    >
    >
    >
    
    _______________________________________________
    Teas mailing list
    Teas@ietf.org
    https://www.ietf.org/mailman/listinfo/teas
    
_______________________________________________
Teas mailing list
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas
_______________________________________________
Teas mailing list
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas