BCP 49, RFC 3152 on Delegation of IP6.ARPA

RFC Editor <rfc-ed@ISI.EDU> Fri, 19 October 2001 23:51 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06221; Fri, 19 Oct 2001 19:51:43 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA08498 for ietf-123-outbound.10@ietf.org; Fri, 19 Oct 2001 19:45:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA07196 for <all-ietf@loki.ietf.org>; Fri, 19 Oct 2001 18:12:32 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02930 for <all-ietf@ietf.org>; Fri, 19 Oct 2001 18:12:27 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id f9JMCUH26180; Fri, 19 Oct 2001 15:12:30 -0700 (PDT)
Message-Id: <200110192212.f9JMCUH26180@gamma.isi.edu>
To: IETF-Announce:;
Subject: BCP 49, RFC 3152 on Delegation of IP6.ARPA
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 19 Oct 2001 15:12:30 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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.


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.
ftp://ftp.isi.edu/in-notes/rfc3152.txt"><ftp://ftp.isi.edu/in-notes/rfc3152.txt>