Re: [apps-discuss] ICANN Variant Issues Project case study reports
Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 11 October 2011 15:19 UTC
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FBE321F8E14 for <apps-discuss@ietfa.amsl.com>; Tue, 11 Oct 2011 08:19:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level:
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599]
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 y8m1ih2cS5oL for <apps-discuss@ietfa.amsl.com>; Tue, 11 Oct 2011 08:19:35 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 0592D21F8DF5 for <apps-discuss@ietf.org>; Tue, 11 Oct 2011 08:19:35 -0700 (PDT)
Received: from shinkuro.com (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id B7A781ECB41C for <apps-discuss@ietf.org>; Tue, 11 Oct 2011 15:19:17 +0000 (UTC)
Date: Tue, 11 Oct 2011 11:19:22 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: apps-discuss@ietf.org
Message-ID: <20111011151921.GK97086@shinkuro.com>
References: <20111011151240.GG97086@shinkuro.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20111011151240.GG97086@shinkuro.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [apps-discuss] ICANN Variant Issues Project case study reports
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2011 15:19:35 -0000
Because I am a moron, I forgot to include the links to the reports. Here they are: Arabic: <http://www.icann.org/en/announcements/announcement-3-07oct11-en.htm> Chinese: <http://www.icann.org/en/announcements/announcement-03oct11-en.htm> Cyrillic: <http://www.icann.org/en/announcements/announcement-06oct11-en.htm> Devanagari: <http://www.icann.org/en/announcements/announcement-2-03oct11-en.htm> Greek: <http://www.icann.org/en/announcements/announcement-07oct11-en.htm> Latin: <http://www.icann.org/en/announcements/announcement-2-07oct11-en.htm> On Tue, Oct 11, 2011 at 11:12:40AM -0400, Andrew Sullivan wrote: > No hat. > > Dear colleagues, > > I'm going to send related messages to four IETF lists where I suspect > there might be people who are interested: dnsext, dnsop, apps-discuss, > and idna-update. My apologies to those of you who get it more than > once. > > For those of you who have been following or otherwise interested in > the ICANN Variant Issues Project, the case study reports are up. The > public comment period is open until 14 November. The Project is aimed > at sorting out, for some scripts, what people mean when they talk > about "variant names" in the DNS. > > I bring this to the attention of the Applications Area, because of the > interest the discussion about DNS aliasing evinced when we raised it > in the Area meeting some time ago. In my reading, two of the reports > are quite clearly in favour of some sort of technique to make > different DNS names apparently act as one; another is non-committal, > but appears to have use of those techniques as one possible > consequence. In my view, these reports do not make strong technical > recommendations, but they outline the reasons why these behaviours are > desirable. > > As a matter of full disclosure, I point out that I have been involved > with these reports, providing some observations about the (technical) > feasibility of various things people wanted to do. I provided advice, > but of course the teams actually responsible for the reports were free > to do as they wished with my advice (including ignore it). > > I encourage those of you who are interested in the topic to read the > reports and make any comments you think are useful in the public > comment forum, or (for that matter) by discussing things on the open > ICANN list devoted to the project > (https://mm.icann.org/mailman/listinfo/vip). Note that the usual > ICANN processes don't include the discussion on the mailing list as > public comments, so if you want your comments to be considered > formally, you'll need to post them in the appropriate area. > > Best regards, > > Andrew > > -- > Andrew Sullivan > ajs@anvilwalrusden.com > _______________________________________________ > apps-discuss mailing list > apps-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/apps-discuss -- Andrew Sullivan ajs@crankycanuck.ca
- Re: [apps-discuss] ICANN Variant Issues Project c… Andrew Sullivan
- [apps-discuss] ICANN Variant Issues Project case … Andrew Sullivan