On Wed, Apr 01, 2026 at 08:19:13AM -0400, Acee Lindem wrote: > > On Apr 1, 2026, at 7:48 AM, Job Snijders <[email protected]> wrote: > > IESG - please consider this an objection to this document moving forward > > for RFC standards track publication at this point in time. > > > > The objection mainly being: there are no known implementations and > > the LSR working group consensus on whether to publish this document > > appears weak. In light of this, the request for RFC publication appears > > premature. > > We do have implementations of the base IGP models but these came AFTER > publication of RFC 9129 and RFC 9130 (see holo links that you snipped > out).
Ah, in other words: publication of RFC 9129 & RFC 9130 could just as well have waited for real implementation work to catch up? The links you shared are not implementations of the internet-draft at hand, correct? What exactly is their relevance in this mail thread? > This is in contrast to the IDR WG where they still don't have the base > model standardized and have a significant protocol feature/YANG gap. > > https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-model/ As I understand the state of things, this is because there are real challenges in modeling the BGP protocol states in the YANG language and efficiently implementing the resulting model. Whether this is because BGP is complicated or YANG too limited I don't know, perhaps a bit of both. Are you making a reference to the IDR BGP YANG model because you experienced similar implementation obstacles with draft-ietf-lsr-ospf-flex-algo-yang? Of course, IDR not having published a yang model for BGP is orthogonal to whether draft-ietf-lsr-ospf-flex-algo-yang-05 should be published. > We will continue to move forward and IDR is considering doing the > same. Objections are irrelevant and need not be addressed? > Perhaps you can direct your energy as that is where you have > been active in the past. What a strange thing to say. Kind regards, Job _______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
