Robert –
I have brought this in the context of the waif-for-bfd OSPF proposal. This is the first time LSR WG is facing such a requirement so IMO it would be proper to at least discuss this in the draft. [LES:] Well – no – that statement isn’t true. The strict-mode drafts (OSPF and BGP) are specifying behavior which has long been deployed. IS-IS specified this in RFC 6213 many years ago. Proprietary implementations of the equivalent functionality in OSPF have been deployed for many years – but they lack a means to successfully interoperate with implementations which do not have the functionality and/or are not configured to enable it. All this draft is doing is defining protocol extensions for OSPF to support strict-mode as it has been deployed for many years. As such, most of the discussion is out of scope and we should simply approve the document. It is both understandable and potentially useful that the context here has revived other concerns that you may have had for a long time. But addressing those concerns is new work, outside the scope of this draft, and likely demands a broader audience than LSR WG provides. Let’s move on with this draft as is. If you or others want to pursue new work related to this functionality, please do so – but NOT in the context of this draft. Les
_______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
