Subject: [DNSOP] Fwd: New Version Notification for draft-gersch-dnsop-revdns-cidr-03.txt

From: Joseph Gersch <[email-masked]>
Date: Tue, 2 Oct 2012 17:41:42 -0600

DNSOP group,

     We have submitted a 3rd draft of the reverse-DNS naming convention for CIDR address blocks.  The new draft has added material to augment and clarify issues raised during discussions on the mailing list, at the IETF and at other meetings, as well as providing a historical context with RFC's 1101 and 2317.  
 
     This document was first submitted at the Paris IETF meeting and was voted as being relevant to the DNSOP working group.  We would like to continue the discussion on the mailing list and also at the upcoming Atlanta IETF meeting.   We appreciate any feedback and comments, and would like to propose evolving this document from draft status to a working group document during our discussions in Atlanta.

Best regards,
   - Joe Gersch and Dan Massey 

Begin forwarded message:

> From: [email-masked]
> Subject: New Version Notification for draft-gersch-dnsop-revdns-cidr-03.txt
> Date: October 2, 2012 5:33:22 PM MDT
> To: [email-masked]
> Cc: [email-masked], [email-masked], [email-masked]
> 
> 
> A new version of I-D, draft-gersch-dnsop-revdns-cidr-03.txt
> has been successfully submitted by Joe Gersch and posted to the
> IETF repository.
> 
> Filename:	 draft-gersch-dnsop-revdns-cidr
> Revision:	 03
> Title:		 Reverse DNS Naming Convention for CIDR Address Blocks
> Creation date:	 2012-10-02
> WG ID:		 Individual Submission
> Number of pages: 31
> URL:             http://www.ietf.org/internet-drafts/draft-gersch-dnsop-revdns-cidr-03.txt
> Status:          http://datatracker.ietf.org/doc/draft-gersch-dnsop-revdns-cidr
> Htmlized:        http://tools.ietf.org/html/draft-gersch-dnsop-revdns-cidr-03
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-gersch-dnsop-revdns-cidr-03
> 
> Abstract:
>   This draft proposes a naming convention for encoding CIDR address
>   blocks into the reverse DNS namespace.  The reverse DNS naming method
>   is commonly used to specify a complete IP address.  This document
>   describes how to encode an IPv4 or IPv6 CIDR address block such as
>   129.82.0.0/16.  By defining a common naming convention, one can
>   associate information with a prefix.  The convention builds on past
>   work in RFC 1101 that associates network names with prefixes.
>   However, this previous work pre-dated the introduction of CIDR and
>   has several critical ambiguities.  This convention corrects the
>   ambiguities and enables new applications ranging from routing
>   information to geolocation.
> 
> 
> 
> 
> The IETF Secretariat
>