Network Working Group J. Gersch
Internet-Draft Secure64 SW Corp
Intended status: Informational D. Massey
Expires: August 29, 2013 Colorado State University
E. Osterweil
Verisign
C. Olschanowsky
Colorado State University
February 25, 2013
Reverse DNS Naming Convention for CIDR Address Blocks
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.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 29, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
Gersch, et al. Expires August 29, 2013 [Page 1]
Internet-Draft Reverse DNS CIDR February 2013
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Aligning the DNS and IP Hierarchies . . . . . . . . . . . 4
1.2. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
2. Conventions Used In This Document . . . . . . . . . . . . . . 7
3. Design Requirements . . . . . . . . . . . . . . . . . . . . . 8
4. Reverse DNS CIDR Name Specification . . . . . . . . . . . . . 9
4.1. IPv4 Address Block Naming . . . . . . . . . . . . . . . . 9
4.2. IPv6 Address Block Naming . . . . . . . . . . . . . . . . 11
4.3. Maintaining one-to-one mapping . . . . . . . . . . . . . . 11
5. Related Work . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.1. Naming via RFC 1101 . . . . . . . . . . . . . . . . . . . 12
5.2. CIDR Naming via RFC 2317 . . . . . . . . . . . . . . . . . 13
5.3. Prior Work on CIDR Names for Routing . . . . . . . . . . . 14
6. Additional Considerations . . . . . . . . . . . . . . . . . . 16
6.1. Splitting a /16 into two /17s . . . . . . . . . . . . . . 16
6.2. Allocating a /16 and then assigning the /16 . . . . . . . 16
6.3. Delegations that Span Octet boundaries . . . . . . . . . . 16
6.4. Legacy Behavior at Octet Boundaries . . . . . . . . . . . 17
6.5. The Naming Convention and Zone Structures . . . . . . . . 17
6.6. Separation of Prefix Data and PTR Records . . . . . . . . 17
6.7. Prefix Enumeration . . . . . . . . . . . . . . . . . . . . 18
6.8. Finding Longest Matches . . . . . . . . . . . . . . . . . 19
7. Security Considerations . . . . . . . . . . . . . . . . . . . 20
datatracker.ietf.org