I've reviewed multiple iterations of this draft, and I believe it is mostly ready to go.
However, the concerns I raised during WGLC in http://www.ietf.org/mail-archive/web/sidr/current/msg05010.html regarding the ambiguity of some of the guidance regarding location of RPKI caches ("close") in section 3 still have not been addressed. IMO if it is important enough to discuss proximity, it is important enough to devote some words to explaining the rationale for that recommendation so that operators can make an informed design decision. Thanks, Wes George > -----Original Message----- > From: ietf-announce-boun...@ietf.org [mailto:ietf-announce- > boun...@ietf.org] On Behalf Of The IESG > Sent: Tuesday, September 17, 2013 10:52 AM > To: IETF-Announce > Cc: s...@ietf.org > Subject: Last Call: <draft-ietf-sidr-origin-ops-21.txt> (RPKI-Based > Origin Validation Operation) to Best Current Practice > > > The IESG has received a request from the Secure Inter-Domain Routing WG > (sidr) to consider the following document: > - 'RPKI-Based Origin Validation Operation' > <draft-ietf-sidr-origin-ops-21.txt> as Best Current Practice > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive comments to the > ietf@ietf.org mailing lists by 2013-10-01. Exceptionally, comments may > be > sent to i...@ietf.org instead. In either case, please retain the > beginning of the Subject line to allow automated sorting. > > Abstract > > > Deployment of RPKI-based BGP origin validation has many operational > considerations. This document attempts to collect and present those > which are most critical. It is expected to evolve as RPKI-based > origin validation continues to be deployed and the dynamics are > better understood. > > > > > > The file can be obtained via > http://datatracker.ietf.org/doc/draft-ietf-sidr-origin-ops/ > > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-ietf-sidr-origin-ops/ballot/ > > > No IPR declarations have been submitted directly on this I-D. > This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
