Skip to main content

Delegation of IP6.ARPA
draft-ymbk-ip6-arpa-delegation-02

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3152.
Author Randy Bush
Last updated 2013-03-02 (Latest revision 2001-03-02)
RFC stream Legacy stream
Formats
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 3152 (Best Current Practice)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-ymbk-ip6-arpa-delegation-02
A new Request for Comments is now available in online RFC libraries.

        BCP 49
        RFC 3152

        Title:      Delegation of IP6.ARPA
        Author(s):  R. Bush
        Status:     Best Current Practice
        Date:       August 2001
        Mailbox:    randy@psg.com
        Pages:      4
        Characters: 5727
        Updates:    2874, 2772, 2766, 2553, 1886
        See Also:   BCP 49

        I-D Tag:    draft-ymbk-ip6-arpa-delegation-02.txt

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

This document discusses the need for delegation of the IP6.ARPA DNS
zone, and specifies a plan for the technical operation thereof.

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