On Jul 8, 2014, at 4:23 PM, Geoff Huston <[email protected]> wrote: > > On 9 Jul 2014, at 5:02 am, Sandra Murphy <[email protected]> wrote: > >> >> The rfc6485bis draft is intended to clean up errors in RFC6485. That should >> progress. Implementations already comply with the corrected text. >> >> The bgpsec-algs draft is adding new algorithms to be used in new RPKI >> objects and in the bgpsec protocol. The bgpsec-algs draft should be >> updating the rfc6485bis document. As there's still work in progress here, >> there should be no problem with the order of publication. I can see that >> there are several references to RFC6485 in bgpsec-algs that will have to >> take the final publication of rfc6485bis draft into account, in order to >> clear up the relationships. >> > > this seems to me to be a deliberate decision to proliferate more documents. > > - we are updating rfc6485 to clean up an error > > - we are updating rfc6485 to add crypto profiles for BGPSEC router use > > And out of this the chair is saying "lets have TWO documents", RFC6485bis and > RFC6485bisupdate > > If this is what you are saying, then as a WG member I strongly disagree with > this edict from the chair. We should consider the poor consumer of our > various efforts and try to consolidate our work, and not proliferate the > madness across many documents in such a profligate manner! (0.5 :-))
The RFC6485bis draft corrects errors, where the error corrections are known. The bgpsec-algs document is new stuff and not yet completely worked out and not yet implemented or in use. I see those as two different separable issues and do not want to see the error correction wait for, confused with, the bgpsec-algs completion. RFC6485 is in use and deployment in the RPKI origin validation, as will the eventual RFC6485bis. The additional algorithms in bgpsec-algs will be used in path validation in the bgpsec protocol, not in origin validation. The uses are separable. --Sandy, speaking as one of the co-chairs
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
