Reverse DNS Naming Convention for CIDR Address Blocks
draft-gersch-dnsop-revdns-cidr-04

 
Document Type Expired Internet-Draft (individual)
Last updated 2013-08-29 (latest revision 2013-02-25)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-gersch-dnsop-revdns-cidr-04.txt

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.128.0/17. 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.

Authors

Joe Gersch (joe.gersch@secure64.com)
Dan Massey (massey@cs.colostate.edu)
Eric Osterweil (eosterweil@verisign.com)
Cathie Olschanowsky (cathie@cs.colostate.edu)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)