[rfc-dist] BCP 91, RFC 3901 on DNS IPv6 Transport Operational Guidelines

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Fri Sep 24 09:30:50 PDT 2004


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


        BCP 91
        RFC 3901

        Title:      DNS IPv6 Transport Operational Guidelines
        Author(s):  A. Durand, J. Ihren
        Status:     Best Current Practice
        Date:       September 2004
        Mailbox:    Alain.Durand at sun.com, johani at autonomica.se
        Pages:      5
        Characters: 10025
        SeeAlso:    BCP 91

        I-D Tag:    draft-ietf-dnsop-ipv6-transport-guidelines-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3901.txt


This memo provides guidelines and Best Current Practice for operating
DNS in a world where queries and responses are carried in a mixed
environment of IPv4 and IPv6 networks.

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

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

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

        To: rfc-info at 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 at 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 at 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.
-------------- next part --------------
Skipped content of type multipart/alternative


More information about the rfc-dist mailing list