Browse Prior Art Database

Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6) (RFC3364)

IP.com Disclosure Number: IPCOM000009357D
Original Publication Date: 2002-Aug-01
Included in the Prior Art Database: 2002-Aug-20
Document File: 12 page(s) / 27K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Austein: AUTHOR

Abstract

The IETF has two different proposals on the table for how to do DNS support for IPv6, and has thus far failed to reach a clear consensus on which approach is better. This note attempts to examine the pros and cons of each approach, in the hope of clarifying the debate so that we can reach closure and move on.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 11% of the total text.

Network Working Group� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � R. Austein

Request for Comments: 3364� � � � � � � � � � � � � � � � � � � � � � � � � � Bourgeois Dilettant

Updates: 2673, 2874� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � August 2002

Category: Informational

� � � � � � � � � � � � Tradeoffs in Domain Name System (DNS) Support

� � � � � � � � � � � � � � � � for Internet Protocol version 6 (IPv6)

Status of this Memo

� � This memo provides information for the Internet community.� It does

� � not specify an Internet standard of any kind.� Distribution of this

� � memo is unlimited.

Copyright Notice

� � Copyright (C) The Internet Society (2002).� All Rights Reserved.

Abstract

� � The IETF has two different proposals on the table for how to do DNS

� � support for IPv6, and has thus far failed to reach a clear consensus

� � on which approach is better.� This note attempts to examine the pros

� � and cons of each approach, in the hope of clarifying the debate so

� � that we can reach closure and move on.

Introduction

� � RFC 1886 [RFC1886] specified straightforward mechanisms to support

� � IPv6 addresses in the DNS.� These mechanisms closely resemble the

� � mechanisms used to support IPv4, with a minor improvement to the

� � reverse mapping mechanism based on experience with CIDR.� RFC 1886 is

� � currently listed as a Proposed Standard.

� � RFC 2874 [RFC2874] specified enhanced mechanisms to support IPv6

� � addresses in the DNS.� These mechanisms provide new features that

� � make it possible for an IPv6 address stored in the DNS to be broken

� � up into multiple DNS resource records in ways that can reflect the

� � network topology underlying the address, thus making it possible for

� � the data stored in the DNS to reflect certain kinds of network

� � topology changes or routing architectures that are either impossible

� � or more difficult to represent without these mechanisms.� RFC 2874 is

� � also currently listed as a Proposed Standard.

Austein� � � � � � � � � � � � � � � � � � � � � Informational� � � � � � � � � � � � � � � � � � � � � [Page 1]

RFC 3364� � � � � � � � � � Tradeoffs in DNS Support for IPv6� � � � � � � � August 2002

� � Both of these Proposed Standards were the output of the IPNG Working

� � Group.� Both have been implemented, although implementation of

� � [RFC1886] is more widespread, both because it was specified earlier

� � and because it's simpler to implement.

� � There's little question that the mechanisms proposed in [RFC2874] are

� � more general than the mechanisms proposed in [RFC1886], and that

� � these enhanced mechanisms might be valuable if IPv6's evolution goes

� � in certain directions.� The questions are whether we really need the

� � more general mechanism, what new usage problems might come along with

� � the enhanced mechanisms, and what effect all this will have on IPv6

� � deployment.

� � The one thing on whic...