RFC 5158 on 6to4 Reverse DNS Delegation Specification
rfc-editor@rfc-editor.org Thu, 06 March 2008 22:00 UTC
Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC76128CA97; Thu, 6 Mar 2008 14:00:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.505
X-Spam-Level:
X-Spam-Status: No, score=-100.505 tagged_above=-999 required=5 tests=[AWL=-0.068, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7kyfYMNANEiz; Thu, 6 Mar 2008 14:00:23 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 60DEE3A6ABF; Thu, 6 Mar 2008 13:57:40 -0800 (PST)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAFD928C89A for <ietf-announce@core3.amsl.com>; Thu, 6 Mar 2008 13:57:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7493fQMtJGZK for <ietf-announce@core3.amsl.com>; Thu, 6 Mar 2008 13:57:38 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 99F4628C50C for <ietf-announce@ietf.org>; Thu, 6 Mar 2008 13:57:37 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 87DA11186AB; Thu, 6 Mar 2008 13:57:27 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5158 on 6to4 Reverse DNS Delegation Specification
From: rfc-editor@rfc-editor.org
Message-Id: <20080306215727.87DA11186AB@bosco.isi.edu>
Date: Thu, 06 Mar 2008 13:57:27 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 5158
Title: 6to4 Reverse DNS Delegation Specification
Author: G. Huston
Status: Informational
Date: March 2008
Mailbox: gih@apnic.net
Pages: 12
Characters: 25536
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-huston-6to4-reverse-dns-07.txt
URL: http://www.rfc-editor.org/rfc/rfc5158.txt
This memo describes the service mechanism for entering a delegation
of DNS servers that provide reverse lookup of 6to4 IPv6 addresses
into the 6to4 reverse zone file. The mechanism is based on a
conventional DNS delegation service interface, allowing the service
client to enter the details of a number of DNS servers for the
delegated domain. In the context of a 6to4 reverse delegation, the
client is primarily authenticated by its source address used in the
delegation request, and is authorized to use the function if its IPv6
address prefix corresponds to an address from within the requested
6to4 delegation address block. This memo provides information for the Internet community.
INFORMATIONAL: 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.
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.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce