[sidr] I-D Action: draft-ietf-sidr-rpki-oob-setup-09.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Inter-Domain Routing of the IETF. Title : An Out-Of-Band Setup Protocol For RPKI Production Services Author : Rob Austein Filename: draft-ietf-sidr-rpki-oob-setup-09.txt Pages : 22 Date: 2017-02-22 Abstract: This note describes a simple out-of-band protocol to ease setup of the RPKI provisioning and publication protocols between two parties. The protocol is encoded in a small number of XML messages, which can be passed back and forth by any mutually agreeable means which provides acceptable data integrity and authentication. This setup protocol is not part of the provisioning or publication protocol, rather, it is intended to simplify configuration of these protocols by setting up relationships and exchanging keying material used to authenticate those relationships. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sidr-rpki-oob-setup/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-sidr-rpki-oob-setup-09 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-sidr-rpki-oob-setup-09 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ sidr mailing list sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr
[sidr] Alissa Cooper's No Objection on draft-ietf-sidr-rpki-oob-setup-08: (with COMMENT)
Alissa Cooper has entered the following ballot position for draft-ietf-sidr-rpki-oob-setup-08: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-sidr-rpki-oob-setup/ -- COMMENT: -- Thanks for addressing my DISCUSS points, keeping COMMENTs below for posterity. 5.2.4: Per my comment on draft-ietf-sidr-publication, it would be good if service_uri accommodated either HTTPS or HTTP URLs, if HTTP URLs must be supported. 5.4: If it becomes obvious that a new reason code needs to be added to the element in the future, will that require a new version of the protocol? That seems like a bit of a heavy lift as compared to, say, creating a registry for these with an appropriate registration policy. ___ sidr mailing list sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr
Re: [sidr] Alissa Cooper's Discuss on draft-ietf-sidr-rpki-oob-setup-06: (with DISCUSS and COMMENT)
At Wed, 22 Feb 2017 14:25:12 -0500, Alissa Cooper wrote: > > On Feb 9, 2017, at 6:12 PM, Rob Austeinwrote: > > > > Sorry, missed this part: > > > > At Wed, 8 Feb 2017 10:03:32 -0500, Alissa Cooper wrote: > -- > DISCUSS: > -- > > (2) If there is in fact supposed to be a protocol specified here, I have > the same question as I had on draft-ietf-sidr-publication, which is how > do the entities migrate from one version to another and do version > negotiation? > > > > Essentially the same answer as for draft-ietf-sidr-publication, so > > will include some variation of same text if that's acceptable. > > That would do the trick. Thanks. Whoops, then I went and lost having promised to fix this in -07 just like I missed the original issue the first time. Consistency is not always a good thing. Sigh. Sorry. Since this was a DISCUSS rather than just a COMMENT I'm assuming that there will be no objection to uploading a -08 now with the fix, so I will do that immediately after posting this. ___ sidr mailing list sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr