Re: [sidr] wg adoption call for draft-ymbk-bgpsec-rtr-rekeying-00.txt

[Matt Lepinski <[e-mail]>]

I have read now this document.
The issues discussed in this document are issues should be documented 
somewhere.
(It is possible that this could be rolled into another document, since 
its short, but this stuff definitely should be documented in some 
product of the SIDR working group)
I really appreciate that the authors took the time to document these issues.

On 3/24/2012 6:18 AM, Christopher Morrow wrote:
> <crickets>
> Hey folk,
> Is this draft stating something obvious and doesn't need to be
> documented? or are we in need of this doc to keep us all on the same
> page (us == ops + vendors) as to getting a cert created and installed
> on our lovely devices?
>
> If people could take a few minutes to read the 4 pages (minus
> boilerplate) and think/comment that would be nice.
>
> (for the record, it seems like documenting this is a good thing, from
> my perspective.)
>
> -chris
>
> On Mon, Mar 12, 2012 at 4:13 PM, Sean Turner<[e-mail]>  wrote:
>> Well I'd like to see it adopted and I promise to work on it ;)
>>
>> spt
>>
>>
>> On 3/7/12 6:07 PM, Murphy, Sandra wrote:
>>> An alert eye pointed out that the URL below is incorrect.  The correct
>>> pointer is
>>>
>>> http://tools.ietf.org/html/draft-ymbk-bgpsec-rtr-rekeying-00
>>>
>>> --Sandy, speaking as clumsy wg co-chair
>>>
>>> ________________________________________
>>> From: [e-mail] [[e-mail]] on behalf of Murphy,
>>> Sandra [[e-mail]]
>>> Sent: Wednesday, March 07, 2012 5:40 PM
>>> To: [e-mail]
>>> Subject: [sidr] wg adoption call for draft-ymbk-bgpsec-rtr-rekeying-00.txt
>>>
>>> The following request has been made for wg adoption of
>>> draft-ymbk-bgpsec-rtr-rekeying-00.txt.
>>>
>>> The draft is available at
>>> http://tools.ietf.org/html/draft-ymbk-rpki-rtr-impl-01.
>>>
>>> Please respond to the list to say whether you accept this draft as a
>>> working group draft and are willing to work on it. Remember that you do not
>>> need to accept all content in a draft to adopt, as draft editors are
>>> required to reflect the consensus of the working group.
>>>
>>> This call will end 21 Mar 2012.
>>>
>>> --Sandy, speaking as wg co-chair
>>>
>>>
>>> ________________________________________
>>> From: [e-mail] [[e-mail]] on behalf of Randy
>>> Bush [[e-mail]]
>>> Sent: Monday, March 05, 2012 8:54 PM
>>> To: sidr wg list
>>> Subject: [sidr] draft-ymbk-bgpsec-rtr-rekeying-00.txt
>>>
>>> chairs, please consider as a wg work item.  thanks.
>>>
>>> randy
>>>
>>> ---
>>>
>>> From: [e-mail]
>>> Subject: New Version Notification for
>>> draft-ymbk-bgpsec-rtr-rekeying-00.txt
>>>
>>> A new version of I-D, draft-ymbk-bgpsec-rtr-rekeying-00.txt has been
>>> succes=
>>> sfully submitted by Sean Turner and posted to the IETF repository.
>>>
>>> Filename:        draft-ymbk-bgpsec-rtr-rekeying
>>> Revision:        00
>>> Title:           Router Keying for BGPsec
>>> Creation date:   2012-03-05
>>> WG ID:           Individual Submission
>>> Number of pages: 7
>>>
>>> Abstract:
>>>     BGPsec-speaking routers must be provisioned with private keys and the
>>>     corresponding public key must be published in the global Resource
>>>     PKI.  This document describes two ways of doing so, router-driven and
>>>     operator-driven.
>>> _______________________________________________
>>> sidr mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/sidr
>>> _______________________________________________
>>> sidr mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/sidr
>>> _______________________________________________
>>> sidr mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/sidr
>>>
>> _______________________________________________
>> sidr mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/sidr
> _______________________________________________
> sidr mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/sidr