Randy, because the goal of this draft can already be reached simply through use of existing means, i do not support publication. i am not strongly opposed. it's just one more bit of ietf work that is not obviously needed.
Here are the three reasons that may refresh our mind on why after 4 years this draft is still important to move forward to the IESG: 1) Scope beyond BGP communities: This document creates an IANA registry for the "BGP origin validation state". This makes the document the standard for the encoding of this state (valid/invalid/not found). We are already used it as reference for the IPFIX Information Element 294 (for which we went through all the process with the IPFIX policy to get it registered here: http://www.iana.org/assignments/ipfix/ipfix.xhtml). There are other use cases that I can think of where this registry will be required (MRT exports as one top of my mind) 2) Documenting change on BGP decision process changes: Section 3. Basically the origin validation happens before any other policy applied. This goes beyond the iBGP community but even for stand-alone routers. In this sense, you can implement RPKI in a device without modifying any existing policy description. 3) Documentation of non-standard BGP communities: Over the years, we have seen a number of attempts to document and standardise providers communities with less than great results. One particularly use case (that I suffered) is when you have to merge two networks due to an acquisition, standardised communities are very helpful. And lets not forget: Running Code: Last but not least…the draft has been delayed more than what it should and several implementations (including two from Cisco) has running code + documentation + training. As we are pushing to improve adoption of RPKI, I rather spend time adding the missing pieces that removing what is not broken…although the need may not be obvious for everyone. Roque randy _______________________________________________ sidr mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/sidr
_______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
