RFC 2874 on IPv6 DNS

RFC Editor <rfc-ed@ISI.EDU> Wed, 19 July 2000 23:09 UTC

Message-Id: <200007192255.PAA13526@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2874 on IPv6 DNS
Cc: rfc-ed@ISI.EDU, ipng@sunroof.eng.sun.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 19 Jul 2000 15:55:30 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2874

        Title:	    DNS Extensions to Support IPv6 Address Aggregation
                    and Renumbering
        Author(s):  M. Crawford, C. Huitema, S. Thomson
        Status:     Standards Track
	Date:       July 2000
        Mailbox:    crawdad@fnal.gov, huitema@research.telcordia.com,
                    set@research.telcordia.com 
        Pages:      20
        Characters: 44204
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-ipngwg-dns-lookups-08.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2874.txt


This document defines changes to the Domain Name System to support
renumberable and aggregatable IPv6 addressing.  The changes include
a new resource record type to store an IPv6 address in a manner
which expedites network renumbering and updated definitions of
existing query types that return Internet addresses as part of
additional section processing.
 
For lookups keyed on IPv6 addresses (often called reverse lookups),
this document defines a new zone structure which allows a zone to be
used without modification for parallel copies of an address space
(as for a multihomed provider or site) and across network
renumbering events.

This document is a product of the IPNG Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc2874.txt"><ftp://ftp.isi.edu/in-notes/rfc2874.txt>

RFC 2874 on IPv6 DNS RFC Editor