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

"James Seng" <james@seng.sg> Wed, 02 July 2008 15:39 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 522DC3A6BCD; Wed, 2 Jul 2008 08:39:08 -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 8DFE73A6C04 for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 15:41:28 -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 79RoKpch4wbt for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 15:41:27 -0700 (PDT)
Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.233]) by core3.amsl.com (Postfix) with ESMTP id A665C3A6A89 for <ietf@ietf.org>; Tue, 1 Jul 2008 15:41:27 -0700 (PDT)
Received: by qb-out-0506.google.com with SMTP id c7so29028qbc.9 for <ietf@ietf.org>; Tue, 01 Jul 2008 15:41:38 -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=fdv/Hc4dch4tfwXoH58i/VXMYYLUo+5AjqZsgGEmS8M=; b=G/u45EM9yobDx2l+T+6R48sTwgHGqR88IIscGf8du8n66HQrRfSDhWjc17aAXAUiuX IY4Qi9tUne45nc6Pbo8zifwYZMKZ4m0jV7geGFcQQRsAWpWcewBReLpw/WsLkYX7NvOR oFqArl1EIb0Wa8ENQYUwlbkpZ0f/qMVKpNgbI=
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=a4u9EZ3dOjwFdM4aWly90EKWmD/qzhG25nVfHkLGFjZ1jx2uesXvSW0cC8bhdtTv9G poSlDl2XTqJGDj6irs+3X2QHmCuiHWzlT7Zfv6/7DKKsFExkUARksd2i3gAUkAXwncc/ 0rgOGWGqmyowcqUloDg+OAdydlmlsttJISP2E=
Received: by 10.142.134.17 with SMTP id h17mr2700662wfd.346.1214952097730; Tue, 01 Jul 2008 15:41:37 -0700 (PDT)
Received: by 10.142.73.17 with HTTP; Tue, 1 Jul 2008 15:41:37 -0700 (PDT)
Message-ID: <558a39a60807011541je1fbefbk118983456d596dba@mail.gmail.com>
Date: Wed, 2 Jul 2008 06:41:37 +0800
From: "James Seng" <james@seng.sg>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
In-Reply-To: <2788466ED3E31C418E9ACC5C316615572FF95F@mou1wnexmb09.vcorp.ad.vrsn.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <4C0AE13D-4CA6-4989-A6B0-555A014DE464@multicasttech.com> <6F1CFDA0-A6E2-4257-8C72-0FCD1E117290@virtualized.org> <6.2.5.6.2.20080628201322.02e43268@resistor.net> <FBBF3BB9-D231-494A-AFBE-7F816DD1180C@virtualized.org> <20080630064127.GA5829@sources.org> <3B2E8E96-ACAA-4A13-BBE2-33DC80DDADC6@virtualized.org> <20080630190153.GB31520@sources.org> <alpine.LSU.1.10.0807011737360.30078@hermes-1.csi.cam.ac.uk> <486A5F01.90306@dcrocker.net> <2788466ED3E31C418E9ACC5C316615572FF95F@mou1wnexmb09.vcorp.ad.vrsn.com>
X-Google-Sender-Auth: 761b822425540abc
X-Mailman-Approved-At: Wed, 02 Jul 2008 08:39:07 -0700
Cc: dcrocker@bbiw.net, 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

Which brings up a question can a TLD be used like a domain name?

not just http://microsoft/ but bill.gate@microsoft will likely to fail to.

james

2008/7/2 Hallam-Baker, Phillip <pbaker@verisign.com>om>:
> Another like restriction that might be investigated is whether
> http://microsoft/ or other similar corporate TLDs would work as intended
> with deployed legacy browsers.
>
> I suspect (but have not tried) that if you simply type 'Microsoft' into the
> address bar of some browsers you might have the keyword immediately
> interpreted as a search term, not an address to visit.
>
>
> I also suspect that if we actually read the technical specs being proposed
> we might find that some of these issues have already been anticipated in
> them and addressed.
>
>
> ________________________________
> From: ietf-bounces@ietf.org on behalf of Dave Crocker
> Sent: Tue 7/1/2008 12:44 PM
> To: Tony Finch
> Cc: IETF Discussion
> Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
>
>
>
> Tony Finch wrote:
>>>> Speaking technically, how would you distinguish the top-level domain
>>>> "127.0.0.1" from the IP address 127.0.0.1?
>>> A word while passing here: is there a document (RFC, Posix standard,
>>> whatever) which says which is the right result in such a case?
>>
>> RFC 1123 section 2.1, especially the last sentence.
>
> Interesting.
>
> I hadn't noticed the implication of that, before, but it seems to be a
> pretty
> clear technical specification that a top-level domain is not allowed to be a
> decimal number.  Ever.
>
> That's a concrete constraint on what ICANN is permitted to authorize.
>
> d/
> --
>
>    Dave Crocker
>    Brandenburg InternetWorking
>    bbiw.net
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf