I just posted draft-austein-sidr-rpki-rtr-rfc6810bis-00, which is intended as an update to the RPKI-Router protocol (RFC 6810).
An HTMLized rfcdiff against RFC 6810 is available at: http://subvert-ietf.hactrn.net/sidr-rpki-rtr-bis/draft-austein-sidr-rpki-rtr-rfc6810bis-00-from-rfc6810.diff.html Summary of changes to date from RFC 6810: 1) New Router Certificate PDU, to support BGPSEC. Those who remember the earlier (and now expired) draft-ymbk-rpki-rtr-keys may notice that the format of this PDU has changed slightly: per discussion at this week's face-to-face meeting in London, we need to support binding a single router key to multiple ASNs, so we changed the PDU format slightly to allow this. 2) We added a few timing parameters to the End Of Data PDU. These, like the Serial Number mechanism, are lifted almost verbatim from the DNS zone transfer protocol. We left them out of RFC 6810, but subsequent exploration of some of the corner cases of the RPKI Router protocol convinced us that leaving these timing parameters out of the protocol had been a mistake. This draft bumps the protocol version number from 0 to 1. Immediately after posting this I-D we received a gentle reminder that we need to specify what a client and server are meant to do when they support different versions of the protocol, so we'll say something about that in the next revision. We'd like to ask the WG to adopt this as a WG draft. We hope this will be a non-contentious request, as the WG is chartered to work on BGPSEC and we're pretty sure that we need the Router Key PDU to support this, but of course this is up to the chairs and the WG. _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
