RFC 4472 on Operational Considerations and Issues with IPv6 DNS

rfc-editor@rfc-editor.org Mon, 17 April 2006 17:28 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FVXWo-0006F9-DW; Mon, 17 Apr 2006 13:28:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FVXWm-0006F4-Nk for ietf-announce@ietf.org; Mon, 17 Apr 2006 13:28:44 -0400
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVXWm-0001xA-Cp for ietf-announce@ietf.org; Mon, 17 Apr 2006 13:28:44 -0400
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k3HHSh0U032513; Mon, 17 Apr 2006 10:28:43 -0700
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k3HHShAm032512; Mon, 17 Apr 2006 10:28:43 -0700
Date: Mon, 17 Apr 2006 10:28:43 -0700
Message-Id: <200604171728.k3HHShAm032512@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: dnsop@lists.uoregon.edu, rfc-editor@rfc-editor.org
Subject: RFC 4472 on Operational Considerations and Issues with IPv6 DNS
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
Status: O

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

        
        RFC 4472

        Title:      Operational Considerations and Issues with 
                    IPv6 DNS 
        Author:     A. Durand, J. Ihren,
                    P. Savola
        Status:     Informational
        Date:       April 2006
        Mailbox:    Alain_Durand@cable.comcast.com, 
                    johani@autonomica.se, 
                    psavola@funet.fi
        Pages:      29
        Characters: 68882
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnsop-ipv6-dns-issues-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4472.txt

This memo presents operational considerations and issues with IPv6
Domain Name System (DNS), including a summary of special IPv6
addresses, documentation of known DNS implementation misbehavior,
recommendations and considerations on how to perform DNS naming for
service provisioning and for DNS resolver IPv6 support,
considerations for DNS updates for both the forward and reverse
trees, and miscellaneous issues.  This memo is aimed to include a
summary of information about IPv6 DNS considerations for those who
have experience with IPv4 DNS.  This memo provides information for the Internet community.

This document is a product of the Domain Name System Operations
Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community. 
It does not specify an Internet standard of any kind. 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.

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

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce