On Nov 04, 2015, at 20:14, t.petch <ie...@btconnect.com> wrote: > > ----- Original Message ----- > From: "Sean Turner" <s...@sn3rd.com> > To: "sidr wg list" <sidr@ietf.org> > Sent: Tuesday, November 03, 2015 2:07 AM > >> Incorporates comments received during WGLC. >> >> Willing to be shouted down on the tweaks in the IANA considerations > section, but I am hoping that we can move progress this version of the > document towards our AD. > > Sean > > More a gentle nudge than a shout. > > draft-leiba-cotton-iana-5226bis-11 introduces the idea of a registry > being within a group and this I-D makes no mention of the latter. Is > the intent to have a new BGPsec Group, slotting in between Battery > Technologies and BFD, or is it part of the existing RPKI Group? I > suggest making that explicit in the IANA Considerations.
Oh good idea. I think we should put the BGPsec registry in the RPKI group so how about : The Internet Assigned Numbers Authority (IANA) is requested to define the "BGPsec Algorithm Suite Registry" described below in the Resource Public Key Infrastructure (RPKI) group. > And to make the IANA Considerations complete of themselves, since they > get extracted onto a web site, should there be a reference to the > constraints imposed on the algorithms in section two i.e. the two > algorithms to be registered must be as specified in rfc6485bis? An > rfc6485ter would then have to have IANA Considerations to update that > part but I expect we would remember to do that. So there’s no registry for the algorithms used to sign RPKI objects. Folks that start out in IANA registries will need to follow some bread crumbs from ROAs, Manifests, and Ghostbusters to 6487 to 6485bis. BGPsec will be no different in this regard. Again, this assume readers start in the IANA registries, which I hope is not where they’re starting ;) spt _______________________________________________ sidr mailing list sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr
