I thought that I had commented on this Last Call but perhaps not.
The English is quirky, e.g. mixed singular and plural, missing definite
and indefinite articles and such like but I do not think that that
impairs my understanding.
Contacts needs https:
The examples use the line folding convention which needs a reference
else our XML reviewers will complain
What makes life more difficult is the terminology which I find
inconsistent e.g. tag, route tag, administrative tag - are these the
same or different? and if different, which is the YANG leaf tag? RIP
has a tag which I think different but perhaps confusing to those who are
familiar with it.
The Introduction sounds very generic in its talk of routing protocols
but I think that it promises more than it delivers; the YANG description
seem to do the same in places. The reality is that in some places only
static routes are augmented; what about dynamic routes? And where they
are augmented then I think that that needs calling out. In a similar
vein, I think the first paragraph of s.3 wrong.
'The following tree snapshot' looks like an extract to me, not a snapshot.
I have commented in the past about active route and I still find it
tautological.
Authors address gmail.com.com?
Tom Petch
On 17/04/2023 22:40, The IESG wrote:
The IESG has received a request from the Routing Area Working Group WG
(rtgwg) to consider the following document: - 'RIB Extension YANG Data Model'
<draft-ietf-rtgwg-yang-rib-extend-14.txt> as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@xxxxxxxx mailing lists by 2023-05-01. Exceptionally, comments may
be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.
Abstract
A Routing Information Base (RIB) is a list of routes and their
corresponding administrative data and operational state.
RFC 8349 defines the basic building blocks for RIB, and this model
augments it to support multiple next-hops (aka, paths) for each route
as well as additional attributes.
1111111111111111>
The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-rib-extend/
No IPR declarations have been submitted directly on this I-D.
_______________________________________________
rtgwg mailing list
rtgwg@xxxxxxxx
https://www.ietf.org/mailman/listinfo/rtgwg
.
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
