Re: [Teas] Fwd: IETF WG state changed for draft-ietf-teas-yang-te-topo

Igor Bryskin <> Fri, 08 March 2019 20:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F06DE126DFA; Fri, 8 Mar 2019 12:57:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.189
X-Spam-Status: No, score=-4.189 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_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id i9OoLL6MmDX6; Fri, 8 Mar 2019 12:57:08 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 981CD1228B7; Fri, 8 Mar 2019 12:57:07 -0800 (PST)
Received: from (unknown []) by Forcepoint Email with ESMTP id DF0C9ABDF0CEE86736F9; Fri, 8 Mar 2019 20:57:03 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 8 Mar 2019 20:57:03 +0000
Received: from ([]) by ([]) with mapi id 14.03.0415.000; Fri, 8 Mar 2019 12:56:58 -0800
From: Igor Bryskin <>
To: Lou Berger <>, Xufeng Liu <>
CC: TEAS WG <>, "" <>
Thread-Topic: [Teas] Fwd: IETF WG state changed for draft-ietf-teas-yang-te-topo
Thread-Index: AQHU1E1aBQyCSlkYE0u3B2IoGmQNwqX/ooYAgAMESYCAAAepAP//g1YQ
Date: Fri, 8 Mar 2019 20:56:57 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_0C72C38E7EBC34499E8A9E7DD00786391C6B1B1Csjceml521mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Teas] Fwd: IETF WG state changed for draft-ietf-teas-yang-te-topo
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: Fri, 08 Mar 2019 20:57:10 -0000

Hi Lou,

We have had quite a bit of  private discussions between the co-anthers, and I believe, we provided a summary to the WG.
In our opinion it is a very simple, straightforward, yet quite useful addition. It was brought  to our attention by the model implementers that for a given topological element (e.g. TE link) there could be more than one instance of the same source of where the information has come from. For example, there could be more  than one instance of OSPF-TE protocol running in the network, and it is useful for the client application to understand which instance discovered/provided information for which TE links.  Before the change the model could only indicate the type of the information source (OSPF-TE protocol), but not its specific instance, hence the addition of the instance leaf.

Igor (and co-authors)

From: Lou Berger []
Sent: Friday, March 08, 2019 2:53 PM
To: Xufeng Liu
Subject: Re: [Teas] Fwd: IETF WG state changed for draft-ietf-teas-yang-te-topo


    Can you (or other authors) discuss the motivations/issue addressed by the information-source-instance?-- Perhaps I missed it, but I believe  this was a change made without WG discussion.

Thank you,

On 3/8/2019 2:25 PM, Xufeng Liu wrote:
Hi Lou,

The change summary has been posted to the WG mailing list ( Please advise if the authors need to do anything further.
- Xufeng

On Wed, Mar 6, 2019 at 4:21 PM Lou Berger <<>> wrote:


    The recent versions of the te-topology doc had sufficiently significant technical changes that our AD and I, with input from the authors, agreed that the document should come back to the WG and to rerun a full last call process.  The key changes in rev -19 were:

- Referencing the te-types document and updates to point to its module

- introduction of information-source-instance

The second change is a technical change resulting from implementation experience, so is a good change, but as it is a substantive technical change the document has to come out of the RFC editor queue to accept it.
    Can you send out a message summarizing all changes.

We will then restart the WG LC process.

Thank you,
Lou (as Shepherd/co-chair)

-------- Forwarded Message --------

IETF WG state changed for draft-ietf-teas-yang-te-topo


Wed, 06 Mar 2019 10:49:31 -0800


IETF Secretariat <><>


The IETF WG state of draft-ietf-teas-yang-te-topo has been changed to "WG
Document" from "Submitted to IESG for Publication" by Deborah Brungard:

Teas mailing list<>