[v6ops] Document Action: 'Considerations for Transitioning Content to IPv6' to Informational RFC (draft-ietf-v6ops-v6-aaaa-whitelisting-implications-11.txt)

The IESG <iesg-secretary@ietf.org> Mon, 27 February 2012 17:23 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CECF21F87B2; Mon, 27 Feb 2012 09:23:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0AlUmT9cVM-g; Mon, 27 Feb 2012 09:23:08 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E19D21F87B9; Mon, 27 Feb 2012 09:23:07 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.00
Message-ID: <20120227172307.10420.40865.idtracker@ietfa.amsl.com>
Date: Mon, 27 Feb 2012 09:23:07 -0800
Cc: v6ops mailing list <v6ops@ietf.org>, v6ops chair <v6ops-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [v6ops] Document Action: 'Considerations for Transitioning Content to IPv6' to Informational RFC (draft-ietf-v6ops-v6-aaaa-whitelisting-implications-11.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2012 17:23:09 -0000

The IESG has approved the following document:
- 'Considerations for Transitioning Content to IPv6'
  (draft-ietf-v6ops-v6-aaaa-whitelisting-implications-11.txt) as an
Informational RFC

This document is the product of the IPv6 Operations Working Group.

The IESG contact persons are Ronald Bonica and Dan Romascanu.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-implications/




 Technical Summary
 
   The objective of this document is to describe what the whitelisting
   of DNS AAAA resource records is, hereafter referred to as DNS
   whitelisting, as well as the implications of this emerging practice
   and what alternatives may exist.  The audience for this document is
   the Internet community generally, including the IETF and IPv6
   implementers.
 
 Working Group Summary
 
   During the WGLC, Doug Barton captured the major criticism of the
   document thusly:

	However I return to my main premise which is:
	1. 99.9% of the organizations who have chose this solution
 	already understand these issues, and
 	2. The 0.1% who don't, don't care.
 
   While I think that's a valid concern I'm not sure that it results in
   a lack of utility for the information present. Consensus squarely
   favors publication and we feel that the document will be 	
   informative and useful in it's present form.
 
 Document Quality
 
   There are implementers of V6 AAAA whitelisting who have weighed in
  with their plans and comments on the content of the document.
  significant effort has gone into obtaining community involvement
   given the concerns that the document raises. The acknowledgments
   include several deep reviews of the document.

Personel

   Joel Jaegli is document shepherd