Re: Update of RFC 2606 based on the recent ICANN changes ?

"James Seng" <james@seng.sg> Tue, 08 July 2008 01:36 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44A3D3A6B9F; Mon, 7 Jul 2008 18:36:52 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 72E9628C3A6 for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 18:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 E-E1vkO4Co3m for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 18:36:50 -0700 (PDT)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.191]) by core3.amsl.com (Postfix) with ESMTP id 9BDA13A6B9F for <ietf@ietf.org>; Mon, 7 Jul 2008 18:36:50 -0700 (PDT)
Received: by ti-out-0910.google.com with SMTP id a6so875035tib.25 for <ietf@ietf.org>; Mon, 07 Jul 2008 18:36:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=FGaKbCQEMyrfSHMHMf9qxMtT87cTNld4E175kihQOvQ=; b=PsipP133LoTCKpCMnj3Z6zEDQWRvevWzXvTLREJfPoAhnoxMeZcfYn7fZyv4Iw1ujq u5JQ+d5fitI0nKbkZx1Gz04jnEm7SXyaiKdN5+CZnO5breD8ZRd4U12ZrkZ8CmyzvFRL D6CtHS1bcb4+O/q0eJ8jfVX9k+YY+W+XS9/G8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=LTznCiM+Lvf+jjlRIpO69vEXOHI8mvNiFSaRlq3BT3myMPCIA8AY39/ht71zySwivJ aL6Q6dPHurIp4xbsdkGaOs19tHJRopdCDO6KNCxIxbjHwImpN5bj/r1ORtj2KslNc+pe h/BtLjW+/dTs5qFN3xhncoQH0vb1P5jZhgc0Y=
Received: by 10.110.46.14 with SMTP id t14mr3080370tit.22.1215481017800; Mon, 07 Jul 2008 18:36:57 -0700 (PDT)
Received: by 10.110.10.7 with HTTP; Mon, 7 Jul 2008 18:36:57 -0700 (PDT)
Message-ID: <558a39a60807071836s38244439g4054b1175a976454@mail.gmail.com>
Date: Tue, 8 Jul 2008 09:36:57 +0800
From: "James Seng" <james@seng.sg>
To: "Dave Crocker" <dcrocker@bbiw.net>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
In-Reply-To: <4872BF88.5040706@bbiw.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <200807022323.m62NNwVJ034275@drugs.dv.isc.org> <BLU137-W18376D2DBA85C8F712C06F93980@phx.gbl> <8953A1CE-E953-409F-A692-BD12DF4ADE61@acm.org> <48724347.6020500@dcrocker.net> <18BA25DED8BFD9F794A10E84@p3.JCK.COM> <4872BF88.5040706@bbiw.net>
X-Google-Sender-Auth: 9ed4d68d483ae41c
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

> And all of the questions I asked 10 years ago said that TLDs on that latter
> scale would be problematic to the root.

Was that pre-Anycast or post-Anycast?

-James Seng
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf