All, 
  we have submitted a new draft that will be presented at the Paris IETF 
meeting.  
Please take the time to send any comments and suggestions regarding this idea 
on naming CIDR address blocks in the Reverse DNS.

Best regards,
   - Joe Gersch and Dan Massey


Begin forwarded message:

> From: internet-dra...@ietf.org
> Date: February 16, 2012 5:09:18 PM MST
> To: joe.ger...@secure64.com
> Cc: joe.ger...@secure64.com, mas...@cs.colostate.edu
> Subject: New Version Notification for draft-gersch-dnsop-revdns-cidr-00.txt
> 
> A new version of I-D, draft-gersch-dnsop-revdns-cidr-00.txt has been 
> successfully submitted by Joe Gersch and posted to the IETF repository.
> 
> Filename:      draft-gersch-dnsop-revdns-cidr
> Revision:      00
> Title:                 Reverse DNS Naming Convention for CIDR Address Blocks
> Creation date:         2012-02-14
> WG ID:                 Individual Submission
> Number of pages: 19
> 
> Abstract:
>   The current reverse DNS naming method is used to specify a complete
>   IP address.  It has not been used to handle address ranges; for
>   example, there is no formal mechanism for specifying a reverse DNS
>   name for the block of addresses specified by the IPv4 prefix
>   129.82.0.0/16.  Defining such a reverse DNS naming convention would
>   be useful for a number of applications.  These include applications
>   for secure BGP routing, and applications that need host-information
>   for a device owning a complete IPv6 address block.  This draft
>   proposes a naming convention for encoding CIDR address blocks in the
>   reverse DNS.
> 
> 
> 
> 
> The IETF Secretariat

Joseph Gersch
Chief Operating Officer
Secure64 Software Corporation



Attachment: smime.p7s
Description: S/MIME cryptographic signature

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

Reply via email to