From: Lsr on behalf of "Acee Lindem (acee)"
Date: Tuesday, July 5, 2022 at 5:23 PM
To: Robert Raszuk , Jeff Haas
Cc: Susan Hares , IDR List , lsr
Subject: Re: [Lsr] [Idr] YANG requirements for IDR drafts (was Re:
draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20))
Hi
Hi Robert,
Like the SNMP MIBs before them, the YANG models trail the routing protocol
functional drafts. We have enough trouble satisfying all the references without
requiring YANG models. If you pay attention during the WG document status at
IETF 114, you’ll get a picture of where the base
Hi Jeff,
Many thx for your note. As I clarified to Sue my question was really about
LSR WG not IDR :)
And the trigger was Gunter's claim that his employer's OS is already
sending content of LSDB over YANG.
So I was a bit puzzled what happens with new extensions if they like ISIS
reflection if
Robert,
> On Jun 30, 2022, at 6:56 PM, Robert Raszuk wrote:
>
> Isn't the YANG section a requirement for all protocol extension documents
> before they are sent for publications these days ?
>
We're not yet to the point where extensions to YANG modules are part of base
IETF work, but
Hi Hannes,
Thank you. Not everyone is yet in agreement with this, so we are discussing
correct wording.
T
> On Jul 5, 2022, at 7:00 AM, Hannes Gredler
> wrote:
>
> Hi Tony, et al,
>
> minor nit:
>
> ---
> As an example, consider the Extended IS Reachability TLV (type 22).
> A
Bruno,
Thank you, the authors are discussing this.
T
> On Jul 5, 2022, at 4:52 AM,
> wrote:
>
> Hi Tony,
>
> Thanks the update.
> 1 clarification question on §5 (new capability)
> « If all routers in an area advertise the Multi-part TLV Capability a node
> MAY advertise multi-part TLVs
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Link State Routing WG of the IETF.
Title : Flooding Topology Minimum Degree Algorithm
Authors : Huaimo Chen
Mehmet Toy
Hi Tony, et al,
minor nit:
---
As an example, consider the Extended IS Reachability TLV (type 22).
A neighbor in this TLV is specified by:
* 7 octets of system ID and pseudonode number
* 3 octets of default metric
This acts as the key for this entry. The key is followed by up
Hi Tony,
Thanks the update.
1 clarification question on §5 (new capability)
« If all routers in an area advertise the Multi-part TLV Capability a node MAY
advertise multi-part TLVs "
Does this mean that if one router does not advertise the capability, routers
MUST NOT advertise multi-part
