> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of
> Christopher Morrow
> Sent: Saturday, March 24, 2012 10:09 AM
> To: Matt Lepinski
> Cc: [email protected]
> Subject: Re: [sidr] wg adoption call for draft-ymbk-bgpsec-rtr-rekeying-00.txt
>
> oh, except that the -rollover doc says:
> "The BGPSEC key roll-over process should be very tighten to the key
>    provisioning mechanisms that would be in place.  The key provisioning
>    mechanisms for BGPSEC are not yet documented.  We will assume that
>    such an automatic provisioning mechanism will be in place (a possible
>    provisioning mechanism when the private key lives only inside the BGP
>    speaker is the Enrollment over Secure Transport (EST).  This protocol
>    will allow BGPSEC code to include automatic re-keying scripts with
>    minimum development cost."
>
> in the second sentence it's asking for this doc... (the first sentence
> seems to have some missing words though)
>
> > thanks!
> > -chris
> >


[WEG] the cited text can be changed, especially now that the referenced 
documentation exists. :-)
My point was not that all of the information isn't important, but rather that 
this occupies similar space and I don't know that it needs to be separated, 
other than as a separate section in one document. This WG generates a lot of 
documents that are logically separated by subject matter, but by necessity very 
intertwined, which sometimes makes it hard for those not intimately involved in 
writing/reviewing the drafts to keep track of what information is discussed 
where, and requires a fair amount of cross-referencing to truly understand the 
implementation. I'm thinking that if there are obvious places to consolidate, 
we should do so.

Wes

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

Reply via email to