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

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: sidr-bounces@ietf.org [sidr-bounces@ietf.org] on behalf of Murphy, Sandra [Sandra.Murphy@sparta.com]
> Sent: Wednesday, March 07, 2012 5:40 PM
> To: sidr@ietf.org
> 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: sidr-bounces@ietf.org [sidr-bounces@ietf.org] on behalf of Randy Bush [randy@psg.com]
> 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: internet-drafts@ietf.org
> 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
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>