Re: [Idr] WG Last Call on draft-ietf-idr-bgp-model-16

[tom petch <[e-mail]>]

From: Idr <[e-mail]> on behalf of Dongjie (Jimmy) <jie.dong=[e-mail]>
Sent: 11 April 2023 03:17
Hi WG,

This begins the Working Group Last Call for "YANG Model for Border Gateway Protocol (BGP-4)", draft-ietf-idr-bgp-model-16. The draft could be found at: https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-model-16.

<tp>
This I-D ticks a lot of the boxes that discourages me from going any further; I do not expect to review it in any level of detail.

Submodules - what are they? much discussed in the early days of YANG but I see them as an idea whose time never came, just risking an increase in misunderstandings about the rules thereof, e.g. scope of names (which I once knew).

Mixing information with different life cycles, IANA modules that are obsolete as soon as they are published 
with protocol modules which likely will be revised thus creating a difficult, impossible even, situation for the IETF at a future date as to how to update the document.

multiple identifiers made so brief - two letter prefix  - that I will struggle to remember what they are

mismatch of prefix within the I-D

lots of groupings leading to long lists pf groupings with names that I do not find obvous making the detail hard to follow e.g.
           uses bgp-adj-rib-attr-state;
           uses bgp-adj-rib-common-attr-refs;
           uses bgp-common-route-annotations-state;
           uses bgp-adj-rib-in-post-route-annotations-state;
           uses bgp-unknown-attr-top;
           uses rib-ext-route-annotations;
(is there an attr-bottom to go with the attr-top?)

Normative Reference to an I-D with MISSREF that may or may not progress soon (shades of OSPF YANG which took a few years to resolve)

'reference to the standard MIB TCP connection table.
Is the BGP MIB a pre-requisite?

Out-of- date text such as 
       "WG Web:   <http://tools.ietf.org/wg/idr>
and
Simplified BSD License 
with example dates in 2016


Tom Petch
Since all the IDR chairs are coauthors of this document, I’m helping with this last call procedure. Please reply to the list with your comments. Considering this is a long document with a big YANG model, the last call will last for 4 weeks and conclude on Sunday, 7 May, 2023.



The authors are requested to state whether they are aware of applicable IPR related to this draft. Similarly, if others in the Working Group are aware of applicable IPR, please also disclose them.


People are encouraged to indicate whether there is implementation of this document. According to the IDR rule, at least two implementations will be required to advance the document.





Best regards,

Jie (on behalf of the IDR chairs)