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

Tarek Saad <> Wed, 29 May 2019 15:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9E4CE120146; Wed, 29 May 2019 08:48:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id LIk9w_rloSwO; Wed, 29 May 2019 08:48:40 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::d31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2BBCE12001A; Wed, 29 May 2019 08:48:40 -0700 (PDT)
Received: by with SMTP id e5so2270216iok.4; Wed, 29 May 2019 08:48:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-transfer-encoding:mime-version; bh=MaIa6bPbzfSODZAZ3aZorTWyKmWIFu1Ne3DpkZ4ZCNM=; b=RBNwVvl335nmskbZ2ENbmPI64p0h+M0gOKDWedAUbcZ92WITEGRfQ6pRcRze0JIagK gmYNvkZf+rz8Ox3Q0iQek0iCFBb4yQJlr2Rmb9gkDmCNXrZX/1dS3DWuVUAVtuqnl1qO hTRhNOd2KKnA3hrF2d5u+eiAxkkSSFDdd/86fAgKDlfza5gSMkPekRjUWhSdGv5v1Ge7 VrenFl4l1xPB9nj/ZRqYk4QL4O/E1nSwFJg76+L7uMhGvcj3ljChxgUz1GAccW29RlEz p1d/wsv0TPMoQ7855YPW4ajXpK4OMkm7JL2kj54fzRj4dAs0wK/UmY6+VKZwAYXw7C2c 6RvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-transfer-encoding:mime-version; bh=MaIa6bPbzfSODZAZ3aZorTWyKmWIFu1Ne3DpkZ4ZCNM=; b=VmgJCGfT3AaQcF/eczEvHTqcFRJx4cH5Pk/QA1XKPJTgU0COFV8cM7yTrtlclJGcjh sx9VaSSdqnZHv/+M7MF0ZazqjbtVQENaV2YyqMyNROEl79grUqXIilj4Br5mVxQfgMTQ AMkAM/qMhpOPchFdvojYgjKThpgZtqpnSyVrmWmJR5BRn/E/W60A9iqEKr4TFNaD7leH EH+JKuaAuon8hKTXSyxgeVdEI3eZrFy13pVEl70dBrQM9SThQoPAK4Kj26TXK65bNOEM AoQHZyBNUYRzRWNiCxs5tHM57DRAcpC8r+Dog/ySaWciE1ZIME9CnUdx5th2IgDgbBRR Ax1w==
X-Gm-Message-State: APjAAAWOExRLFldLBosZmj1dS2MlMfhHngrllwUd7H1Ipknpff7s2UWb E+/Vc1Q/XLy07UJuoh5voW8=
X-Google-Smtp-Source: APXvYqzdncY36BOLQZ8oEgikKzcDtykutKrhr5h7D2jQ4rKzZ+hPVCqxGwqw81XWUbnHaMc/842VbQ==
X-Received: by 2002:a6b:3b4d:: with SMTP id i74mr9271369ioa.207.1559144919547; Wed, 29 May 2019 08:48:39 -0700 (PDT)
Received: from ([]) by with ESMTPSA id k23sm6001937ios.34.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 May 2019 08:48:38 -0700 (PDT)
From: Tarek Saad <>
To: 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: AQHVFg5TRZzvY4cRwUmUh8ERqqpzjKaCP9iQ
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Wed, 29 May 2019 15:48:37 +0000
Message-ID: <>
References: <> <062101d5160d$a43329a0$>
In-Reply-To: <062101d5160d$a43329a0$>
Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-SCL: -1
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
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 15:48:43 -0000

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