On 5/3/16, 6:30 AM, "Stephen Farrell" <[email protected]> wrote:
> >Hi Wes, > >This is only a timing problem if bgpsec doesn't change in some >incompatible manner. If such a change happens then this is more >than a timing issue. >What'd be bad about just holding this in the WG until bgpsec is >ready? Since there's a normative reference anyway getting the >IESG to approve both at once seems like it'd be better. WG] Well, I don't think the BGPSec protocol draft is really far enough behind that holding this one would make much difference in the outcome. My co-author (and WG Chair) replied in another thread that the BGPSec doc is past WGLC and waiting for chair publication request. The primary thing outstanding is a discussion between the Routing ADs and WG as to whether it will be experimental status or PS. If you have concerns, both drafts are sufficiently complete that you could review both now, but I don't expect major chances of the type you express concern about at this late stage. As primary author, I can say that I'd really like this to be off my plate and in the RFC editor's queue, because given current job/merger uncertainty, I can't be certain what my involvement with IETF will be in the coming months. Completing approval on this one while it's in queue also seems a better use of IESG cycles rather than re-cycling the draft such that it has to be reviewed and discussed by IESG a second time, but I defer to the WG and IESG as to how to proceed here. Thanks, Wes George Anything below this line has been added by my company’s mail server, I have no control over it. ----------- ________________________________ 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. _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
