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

"Belotti, Sergio (Nokia - IT/Vimercate)" <> Wed, 29 May 2019 16:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 32F9E12015F; Wed, 29 May 2019 09:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id FW8nNKm5aqkV; Wed, 29 May 2019 09:16:14 -0700 (PDT)
Received: from ( [IPv6:2a01:111:f400:fe0e::72e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7A55512002F; Wed, 29 May 2019 09:16:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AvWJlffuNdQAte84/E8rE5R16+tJGahCQgzUe15FKNM=; b=xvFcz7I/bqn3moN9WWXQ/DRTFvFqESGXZ58hAl/NW0JawZHM90sx+VcpKMJq093JbY/9sXq88sHcAts9asBIV4+KTxclKkZXFSp56kNXVk+Mf0/SId4blMhgj8pdR+W1fcwoSXSiJnlaFq3uaXsrrOdYNBJhXH6lVIXtSnHnz8g=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1943.14; Wed, 29 May 2019 16:16:11 +0000
Received: from ([fe80::b9f4:de7a:fe2e:b585]) by ([fe80::b9f4:de7a:fe2e:b585%6]) with mapi id 15.20.1943.016; Wed, 29 May 2019 16:16:11 +0000
From: "Belotti, Sergio (Nokia - IT/Vimercate)" <>
To: Tarek Saad <>, tom petch <>, "" <>
CC: "" <>, "" <>, "" <>, "" <>
Thread-Topic: [Teas] Last Call: <draft-ietf-teas-yang-te-types-09.txt> (Traffic Engineering Common YANG Types) to Proposed Standard
Thread-Index: AQHVFg5Q84bzNm31ZEidiilOCUuGp6aCP9iAgAAFH6A=
Date: Wed, 29 May 2019 16:16:10 +0000
Message-ID: <>
References: <> <062101d5160d$a43329a0$> <>
In-Reply-To: <>
Accept-Language: it-IT, en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c6557d62-4dc0-4346-7d2e-08d6e450f6f9
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:HE1PR07MB3225;
x-ms-traffictypediagnostic: HE1PR07MB3225:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0052308DC6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(346002)(39860400002)(366004)(376002)(136003)(189003)(199004)(13464003)(68736007)(102836004)(99286004)(6306002)(11346002)(476003)(446003)(52536014)(3846002)(6116002)(71200400001)(305945005)(53936002)(71190400001)(14454004)(55016002)(66946007)(73956011)(66446008)(64756008)(66556008)(66476007)(76116006)(33656002)(74316002)(7736002)(6436002)(9686003)(966005)(508600001)(8676002)(8936002)(2501003)(26005)(76176011)(25786009)(53546011)(81156014)(81166006)(14444005)(4326008)(186003)(6506007)(5660300002)(256004)(316002)(2906002)(229853002)(486006)(6246003)(86362001)(66066001)(110136005)(7696005)(54906003); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB3225;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: RbhUpCTJan6bQJlyrUQyAne6VQ356kf659GBclYX3xeAUkpg4AwlM2/Q8IG7R4y+uLAPAQAyARTaJmI7FqA6V0icpKgaBFsv1m4pp1ee7z0lgJ+GzwOy7zr/F7g6wxtn4cZaAdVIR+QnfUsNaovalE12UymAGd51+JZcj10IGSPYeMonoLqaxEatQPPPaeFfOh9naeRb5rY7xKlauOyXWBaj4GyjXvCoLbDCd6DTfSkwS5BcqVW1cLgFnSYz6R+qr+4LT/3zIIGxXJezIjodAQ2dYmEPOK+x6+nDaYiJhAZtaY9FM3MmjN5Ju7WQB9y+U1Mwb2deW+iOXrPPgQuma0YV86X2Tr42GMGkDziPpsB78iJQWqnOa7+n9zqAOf5qSVlQmsZ1O+SXLh8Yy17PbFQQaFVUiOv1yjnLklwcMUY=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c6557d62-4dc0-4346-7d2e-08d6e450f6f9
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 May 2019 16:16:11.0057 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3225
Archived-At: <>
Subject: Re: [Teas] Last Call: <draft-ietf-teas-yang-te-types-09.txt> (Traffic Engineering Common YANG Types) to Proposed Standard
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 29 May 2019 16:16:17 -0000

Hi Tarek, Tom,
For ODUCn and all so said OTN part "beyond 100G" the most updated reference in IETF is

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


-----Original Message-----
From: Teas <> On Behalf Of Tarek Saad
Sent: Wednesday, May 29, 2019 5:49 PM
To: tom petch <>om>;
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.


On 5/29/19, 7:04 AM, "Teas on behalf of tom petch" < on behalf of> wrote:

    One of the identities defined herein is
    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" <>
    To: "IETF-Announce" <>
    Cc: <>rg>; <>rg>;
    <>rg>; <>
    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
    > comments on this action. Please send substantive comments to the
    > mailing lists by 2019-05-16. Exceptionally, comments may
    > sent to 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
    >    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
    > IESG discussion can be tracked via
    > No IPR declarations have been submitted directly on this I-D.
    Teas mailing list
Teas mailing list