[dnsext] How to bring discussion to a close (was: I-D Action:draft-ietf-dnsext-aliasing-requirements-00.txt)

Andrew Sullivan <ajs@shinkuro.com> Mon, 28 February 2011 18:53 UTC

Return-Path: <ajs@shinkuro.com>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2B5043A6C5C for <dnsext@core3.amsl.com>; Mon, 28 Feb 2011 10:53:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.607
X-Spam-Level:
X-Spam-Status: No, score=-102.607 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, 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 4Qqvd7Db8P0H for <dnsext@core3.amsl.com>; Mon, 28 Feb 2011 10:53:45 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 20A293A6C4C for <dnsext@ietf.org>; Mon, 28 Feb 2011 10:53:45 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 581E31ECB41D for <dnsext@ietf.org>; Mon, 28 Feb 2011 18:54:45 +0000 (UTC)
Date: Mon, 28 Feb 2011 13:54:43 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: dnsext@ietf.org
Message-ID: <20110228185442.GN80597@shinkuro.com>
References: <20110227191542.6824.qmail@joyce.lan> <335963D7-3440-45E6-843C-38F419462792@cisco.com> <Pine.SGI.4.61.1102281223360.6967049@shell01.TheWorld.com> <E8CA84A3163505355F6D3ACF@Ximines.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E8CA84A3163505355F6D3ACF@Ximines.local>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: [dnsext] How to bring discussion to a close (was: I-D Action:draft-ietf-dnsext-aliasing-requirements-00.txt)
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 18:53:49 -0000

On Mon, Feb 28, 2011 at 06:46:32PM +0000, Alex Bligh wrote:

> I believe every possibility (including doing nothing) has been
> rejected at least once, so on that basis +1 to this being (re)considered
> at least to the extent of being included in the draft as a possibility.

I can't speak for others, but I have not rejected every possibility at
least once; I have rather attempted to encourage some exploration of
possiblities in the interests of getting the problem statement
correct.

The editors of the problem statement are in earnest request of text,
so if you have observations that you think could be turned into useful
parts of that document, I urge you to send it.

I am told by the editors that there will be a -01 before IETF 80.

Consistent with what we said when raising the possibility of not
requesting a session at the Prague meeting, your chairs are eager to
wind up discussion on the problem analysis.  The only reason we
requested the session in Prague was the renewed discussion of this
topic.  

So we are quite keen to finish laying out the issues, ideally after
the Prague session.  At that point, we can ask properly whether we
have proposals that will solve the problem as we understand it.

Best,

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.