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

Willie Gillespie <wgillespie+ietf@es2eng.com> Mon, 07 July 2008 21:52 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 ADB903A6B6A; Mon, 7 Jul 2008 14:52:17 -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 9B37A3A6B69 for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 14:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Pg80W9pMzSB6 for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 14:52:15 -0700 (PDT)
Received: from smtp157.sat.emailsrvr.com (smtp157.sat.emailsrvr.com [66.216.121.157]) by core3.amsl.com (Postfix) with ESMTP id 472883A67CE for <ietf@ietf.org>; Mon, 7 Jul 2008 14:52:10 -0700 (PDT)
Received: from relay5.relay.sat.mlsrvr.com (localhost [127.0.0.1]) by relay5.relay.sat.mlsrvr.com (SMTP Server) with ESMTP id 5744823CED2; Mon, 7 Jul 2008 17:52:17 -0400 (EDT)
Received: by relay5.relay.sat.mlsrvr.com (Authenticated sender: willie.gillespie-AT-es2eng.com) with ESMTP id BFC5723CEF3; Mon, 7 Jul 2008 17:52:14 -0400 (EDT)
Message-ID: <487290FA.8020702@es2eng.com>
Date: Mon, 07 Jul 2008 15:56:10 -0600
From: Willie Gillespie <wgillespie+ietf@es2eng.com>
Organization: Engineering System Solutions
User-Agent: Thunderbird 2.0.0.14 (X11/20080505)
MIME-Version: 1.0
To: Theodore Tso <tytso@MIT.EDU>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
References: <20080707133210.AWH55905@m1.imap-partners.net> <20080707203828.GC2300@zod.isi.edu> <20080707210130.GT31490@mit.edu> <20080707211347.GB2222@zod.isi.edu> <20080707214214.GX31490@mit.edu>
In-Reply-To: <20080707214214.GX31490@mit.edu>
Cc: 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Theodore Tso wrote:
> On Mon, Jul 07, 2008 at 02:13:47PM -0700, Ted Faber wrote:
>> On Mon, Jul 07, 2008 at 05:01:30PM -0400, Theodore Tso wrote:
>>> On Mon, Jul 07, 2008 at 01:38:28PM -0700, Ted Faber wrote:
>>>> On Mon, Jul 07, 2008 at 01:32:10PM -0700, moore@network-heretics.com wrote:
>>>>> If you can cite verifiable evidence that even a single case that works
>>>>> reliably now, will cease to work, I'll concede that there is at least
>>>     ^^^^^^^^
>>>>> a hint of merit to your argument.   e.g. an actual email address or
>>>>> URL that uses a single-label domain name.
>>>> zod:~$ ping hk
>>>> PING hk (203.119.2.28): 56 data bytes
>>>> 64 bytes from 203.119.2.28: icmp_seq=0 ttl=243 time=183.582 ms
>>> % ping hk.
>>> PING hk (203.119.2.28) 56(84) bytes of data.
>>> 64 bytes from www.hkdnr.hk (203.119.2.28): icmp_seq=1 ttl=238 time=265 ms
>>> 64 bytes from www.hkdnr.hk (203.119.2.28): icmp_seq=2 ttl=238 time=265 ms
>>>
>>> Not very reliably, I think.  :-)
> 
> Sorry, I cut and paste the wrong example.  What I had meant to cut and
> paste:
> 
> 5% ping hk
> PING hk.ibm.com (9.190.250.244) 56(84) bytes of data.
> ...
> 
> 							- Ted

With your hk.ibm.com example, do you have any search lines in your 
/etc/resolv.conf file that would be automatically appending?
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf