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

Igor Bryskin <> Sun, 10 March 2019 20:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E7D671279B3; Sun, 10 Mar 2019 13:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.19
X-Spam-Status: No, score=-4.19 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] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lBK95N2c49eP; Sun, 10 Mar 2019 13:22:33 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 54EA0127990; Sun, 10 Mar 2019 13:22:33 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 635A2D22DCD5A11FA0FF; Sun, 10 Mar 2019 20:22:31 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 10 Mar 2019 20:22:30 +0000
Received: from ([]) by ([]) with mapi id 14.03.0415.000; Sun, 10 Mar 2019 13:22:21 -0700
From: Igor Bryskin <>
To: "" <>, Igor Bryskin <>, "" <>, "" <>
CC: "" <>, "" <>
Thread-Topic: [Teas] Fwd: IETF WG state changed for draft-ietf-teas-yang-te-topo
Thread-Index: AQHU1E1aBQyCSlkYE0u3B2IoGmQNwqX/ooYAgAMESYCAAAepAP//g1YQgAIgpoCAAQLfRg==
Date: Sun, 10 Mar 2019 20:22:21 +0000
Message-ID: <etPan.5c857298.71b896f2.28d2@localhost>
References: <> <> <> <> <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_etPan5c85729871b896f228d2localhost_"
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: Sun, 10 Mar 2019 20:22:36 -0000

Hi Xufeng,

I believe every time we published an update for the document we provided a summary of the changes since the previous revision.
Could you find the one for the latest update?

Since the document was put into the RFC  Editor queue we have made far more serious change - we replaced the dependency on te-tunnel model  with the dependency on te-types model. You knew about our intention long time ago, as well as that the document would need in this case another close look by WG. You have not warned us about the problem, nor pulled the document out of the queue then.
Now you are focused on the most trivial change (almost as harmful as changing Tarek's association from CSCO to Jniper), which could be easily reviewed by the WG along with consequences of the depency change. Why is that?


From:Lou Berger
To:Igor Bryskin,Xufeng Liu,
Date:2019-03-09 15:56:11
Subject:Re: [Teas] Fwd: IETF WG state changed for draft-ietf-teas-yang-te-topo

Hi Igor, (and authors)

    Can you point to where in the archive this discussion took place - isn't yielding helpful information.  It's also fine for the authors to make the case for the change now if a suitable reference can't be found.


PS For future reference, technical changes are generally now allowed once a document has been approved by the IESG, and even more rarely once in the RFC editor queue.  (This is nothing new - I remember having quite a discussion back when Jon P. was RFC editor and having to convince him that moving the '|' in a packet format half a bit over in a drawing didn't require moving the doc out of the RFC editor queue even though half bits clearly didn't match the text.)

On 3/8/2019 3:56 PM, Igor Bryskin wrote:
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
Cc: TEAS WG;<>
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<>