IDR generally requires at least two interoperable implementations of a draft before it is advanced to RFC. Our goals in doing this include gaining some level of document quality assurance (can an implementor, working from the spec, implement it interoperably?) but also gaining some level of protocol quality assurance, some assurance that the proposal is implementable in practice (most BGP implementations are large and have many moving parts that new proposals must integrate with). If, as a side-effect, fewer IDR RFCs go unimplimented, that's a benefit too. Of course, perfection is impossible and even with this requirement, mistakes will creep in. Exception cases may exist where the implementation requirement wouldn't advance these goals.
Implementation reports are published on our wiki (see below). Implementation reports should highlight aspects of the spec that have been implemented (for example, consider the sections and SHOULD/MUST/MAY/etc keywords as a matrix, with tickmarks to indicate compliance), aspects that have not been implemented (and why, if the answer would be interesting), what testing, interoperation, and deployment the implementation has seen, and any observations that the reporter deems interesting. Naturally it should indicate the software release, organization, and individual filing the report.
If you have questions or concerns regarding the implementation requirement, please send questions to the IDR mailing list or the IDR chairs.
June 07, 2021 - Flow Specification Feedback
June 21, 2021 - AutoConfiguration Feedback
August 23, 2021 - Chairs on new Drafts
September 27, 2021 - Flow Specification v2
October 11, 2021 - Embedded NLRI and Error Handling (CAR, Classful Transport)) - cancelled
October 18, 2021 - BGP Autoconfiguration + New Drafts
The content of this page was last updated on 2023-06-01. It was migrated from the old Trac wiki on 2023-01-25.