The authors request below that the wg adopt this work as a work item.

The draft is available at 
http://tools.ietf.org/html/draft-rogaglia-sidr-bgpsec-rollover.

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 26 Jun 2012.

--Sandy, speaking as wg co-chair



From: sidr-boun...@ietf.org [sidr-boun...@ietf.org] on behalf of Roque Gagliano 
(rogaglia) [rogag...@cisco.com]

Sent: Tuesday, June 05, 2012 8:05 AM

To: sidr@ietf.org

Subject: [sidr] Fwd: New Version Notification for 
draft-rogaglia-sidr-bgpsec-rollover-01.txt





Dear WG,



We submitted a new version of this draft based on the feedback from our last 
meeting in Paris.



As mentioned during Brian's presentation we would like to ask for WG adoption.



Regards,
Roque




Begin forwarded message:



From: <internet-dra...@ietf.org>



Date: June 5, 2012 1:58:52 PM GMT+02:00



To: <rogag...@cisco.com>



Cc: <keyup...@cisco.com>,
 <b...@cisco.com>



Subject: New Version Notification for draft-rogaglia-sidr-bgpsec-rollover-01.txt




A new version of I-D, draft-rogaglia-sidr-bgpsec-rollover-01.txt has been 
successfully submitted by Roque Gagliano and posted to the IETF repository.



Filename: draft-rogaglia-sidr-bgpsec-rollover

Revision: 01

Title: BGPSEC router key rollover as an alternative to beaconing

Creation date: 2012-06-05

WG ID: Individual Submission

Number of pages: 15



Abstract:

  The current BGPSEC draft documents do not specifies a key rollover

  process for routers.  This document describes a possible key rollover

  process and explores its impact to mitigate replay attacks and

  eliminate the need for beaconing in BGPSEC.









The IETF Secretariat










_______________________________________________
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to