[rfc-dist] BCP 80, RFC 3681 on Delegation of E.F.F.3.IP6.ARPA

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Tue, 20 Jan 2004 12:43:01 -0800


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

        BCP 80
        RFC 3681

        Title:      Delegation of E.F.F.3.IP6.ARPA
        Author(s):  R. Bush, R. Fink
        Status:     Best Current Practice
        Date:       January 2004
        Mailbox:    randy@psg.com, bob@thefinks.com
        Pages:      4
        Characters: 7137
        SeeAlso:    BCP 80

        I-D Tag:    draft-ymbk-6bone-arpa-delegation-01.txt

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

This document discusses the need for delegation of the
E.F.F.3.IP6.ARPA DNS zone in order to enable reverse lookups for
6bone addresses, and makes specific recommendations for the process
needed to accomplish this.

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

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.

Content-Type: Multipart/Alternative; Boundary="OtherAccess"

Content-Type:  Message/External-body;

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

DOC-ID: rfc3681

Content-Type:   Message/External-body;

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