Subject: [GROW] Fwd: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt

From: Joseph Gersch <[email-masked]>
Date: Tue, 28 Feb 2012 13:58:41 -0700

All, 
  we have submitted a new draft that we would like to present at the Paris IETF meeting.  
Please take the time to send any comments and suggestions regarding this idea on using records in  the reverse DNS to help secure BGP route origins.

Best regards,
   - Joe Gersch, Dan Massey, Eric Osterweil and Lixia Zhang

Begin forwarded message:

> From: [email-masked]
> Subject: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
> Date: February 28, 2012 1:51:59 PM MST
> To: [email-masked]
> Cc: [email-masked], [email-masked], [email-masked]
> 
> A new version of I-D, draft-gersch-grow-revdns-bgp-00.txt has been successfully submitted by Joe Gersch and posted to the IETF repository.
> 
> Filename:	 draft-gersch-grow-revdns-bgp
> Revision:	 00
> Title:		 DNS Resource Records for BGP Routing Data
> Creation date:	 2012-02-29
> WG ID:		 Individual Submission
> Number of pages: 22
> 
> Abstract:
>   This draft proposes the creation of two DNS record types for storing
>   BGP routing information in the reverse DNS.  The RLOCK record allows
>   prefix owners to indicate whether the DNS is being used to publish
>   routing data.  The SRO record allows operators to indicate whether an
>   IPv4 or IPv6 prefix ought to appear in global routing tables and
>   identifies authorized origin Autonomous System Number(s) for that
>   prefix.  The published data can be used in a variety of contexts and
>   can be extended to include additional information.  This work is part
>   of an on-going effort and is accessible in an active testbed.
> 
> 
> 
> 
> The IETF Secretariat

Joseph Gersch
Chief Operating Officer
Secure64 Software Corporation