[DNSOP] FWD: RFC 5158 on 6to4 Reverse DNS Delegation Specification

Peter Koch <pk@DENIC.DE> Fri, 07 March 2008 17:43 UTC

Return-Path: <dnsop-bounces@ietf.org>
X-Original-To: ietfarch-dnsop-archive@core3.amsl.com
Delivered-To: ietfarch-dnsop-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5CC3F3A6EA8; Fri, 7 Mar 2008 09:43:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.626
X-Spam-Level:
X-Spam-Status: No, score=-101.626 tagged_above=-999 required=5 tests=[AWL=-1.189, 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 bWKG4Z0ac9SP; Fri, 7 Mar 2008 09:43:24 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 598FB3A6B97; Fri, 7 Mar 2008 09:43:24 -0800 (PST)
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5C763A6C81 for <dnsop@core3.amsl.com>; Fri, 7 Mar 2008 09:43:22 -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 szjTNHzWI3n7 for <dnsop@core3.amsl.com>; Fri, 7 Mar 2008 09:43:22 -0800 (PST)
Received: from denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id 0BAED3A68A5 for <dnsop@ietf.org>; Fri, 7 Mar 2008 09:43:21 -0800 (PST)
Received: by unknown.office.denic.de (Postfix, from userid 501) id 9F81D5FB117; Fri, 7 Mar 2008 18:43:05 +0100 (CET)
Date: Fri, 07 Mar 2008 18:43:05 +0100
From: Peter Koch <pk@DENIC.DE>
To: IETF DNSOP WG <dnsop@ietf.org>
Message-ID: <20080307174305.GG19070@unknown.office.denic.de>
Mime-Version: 1.0
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Subject: [DNSOP] FWD: RFC 5158 on 6to4 Reverse DNS Delegation Specification
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsop-bounces@ietf.org
Errors-To: dnsop-bounces@ietf.org

Since draft-huston-6to4-reverse-dns-XX.txt was kind of a foster child of
this WG, here's the publication note.  Thanks to Geoff and especially to our
AD for getting this through the IESG!

-Peter

----- Forwarded message from rfc-editor@rfc-editor.org -----

From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Cc: rfc-editor@rfc-editor.org
Subject: RFC 5158 on 6to4 Reverse DNS Delegation Specification
Date: Thu, 6 Mar 2008 13:57:27 -0800

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.

[....]
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop