[prev in list] [next in list] [prev in thread] [next in thread] 

List:       namedroppers
Subject:    RFC 3363 on Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System (DNS
From:       rfc-editor () rfc-editor ! org
Date:       2002-08-21 22:58:51
[Download RAW message or body]

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

        RFC 3363

        Title:	    Representing Internet Protocol version 6 (IPv6)
                    Addresses in the Domain Name System (DNS)
        Author(s):  R. Bush, A. Durand, B. Fink, O. Gudmundsson,
                    T. Hain 
        Status:	    Informational
	Date:       August 2002
        Mailbox:    randy@psg.com, alain.durand@sun.com, fink@es.net,
                    ogud@ogud.com, hain@tndh.net
        Pages:      6
        Characters: 11055
        Updates:  2673, 2874

        I-D Tag:    draft-ietf-dnsext-ipv6-addresses-02.txt

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


This document clarifies and updates the standards status of RFCs that
define direct and reverse map of IPv6 addresses in DNS.  This document
moves the A6 and Bit label specifications to experimental status.

This document is a product of the DNS Extensions Working Group of the
IETF.

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.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.

[Attachment #3 (Multipart/Alternative)]

[Attachment #5 (unknown)]

Content-Type: text/plain
Content-ID: <020821155708.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3363

["rfc3363.txt" (rfc3363.txt)]

Content-Type: text/plain
Content-ID: <020821155708.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>

[prev in list] [next in list] [prev in thread] [next in thread]