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

Mark Andrews <Mark_Andrews@isc.org> Tue, 08 July 2008 00:18 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 9EBB73A6B4D; Mon, 7 Jul 2008 17:18:24 -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 5E16C3A6B4D for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 17:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.616
X-Spam-Level:
X-Spam-Status: No, score=-2.616 tagged_above=-999 required=5 tests=[AWL=-0.017, 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 nqFHqMRd4cal for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 17:18:22 -0700 (PDT)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) by core3.amsl.com (Postfix) with ESMTP id 814CA3A6881 for <ietf@ietf.org>; Mon, 7 Jul 2008 17:18:21 -0700 (PDT)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.2/8.14.2) with ESMTP id m680IPi1016117; Tue, 8 Jul 2008 10:18:25 +1000 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <200807080018.m680IPi1016117@drugs.dv.isc.org>
To: Ted Faber <faber@ISI.EDU>
From: Mark Andrews <Mark_Andrews@isc.org>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
In-reply-to: Your message of "Mon, 07 Jul 2008 14:13:47 MST." <20080707211347.GB2222@zod.isi.edu>
Date: Tue, 08 Jul 2008 10:18:25 +1000
Cc: Theodore Tso <tytso@MIT.EDU>, moore@network-heretics.com, 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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

> 
> --===============1515233305==
> Content-Type: multipart/signed; micalg=pgp-sha1;
> 	protocol="application/pgp-signature"; boundary="tsOsTdHNUZQcU9Ye"
> Content-Disposition: inline
> 
> 
> --tsOsTdHNUZQcU9Ye
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> 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 wr=
> ote:
> > > > 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.
> > >=20
> > > zod:~$ ping hk
> > > PING hk (203.119.2.28): 56 data bytes
> > > 64 bytes from 203.119.2.28: icmp_seq=3D0 ttl=3D243 time=3D183.582 ms
> >=20
> > % 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=3D1 ttl=3D238 time=3D=
> 265 ms
> > 64 bytes from www.hkdnr.hk (203.119.2.28): icmp_seq=3D2 ttl=3D238 time=3D=
> 265 ms
> >=20
> > Not very reliably, I think.  :-)
> 
> Umm, hk. resolves to the same address from both our machines and is
> pingable (modulo a single packet loss from yours, depending on how your
> ping counts) from both.  http://hk pulls up a web page on a machine with
> the same address.  (www.hkdnr.hk is an alias for hk. - the same machine;
> you're not being redirected.)
> 
> That's at least as reliable as my (multi-dotted) home domain. :-)
> 
> I'm not sure what's not to like here.  But then again, I may be blind.

	The point is that it is NOT reliable.  Whether it works
	depends apon what names are matched in the search list.  It
	does work for some people some of the time.  It does not
	work for all of the world all of the time.  "hk" is not
	globally unique.

bsdi# ping hk
PING hk.dv.isc.org (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.148 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.170 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.172 ms
^C
--- hk.dv.isc.org ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.148/0.163/0.172/0.011 ms
bsdi# 


> --=20
> Ted Faber
> http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.=
> asc
> Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#=
> SIG
> 
> --tsOsTdHNUZQcU9Ye
> Content-Type: application/pgp-signature
> Content-Disposition: inline
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (FreeBSD)
> 
> iEYEARECAAYFAkhyhwsACgkQaUz3f+Zf+Xu/JQCg0bBCl+ufJrXaLx7X+qsE3Jfk
> nhUAoKdEtfZ+47v4Uu+MCHng2R+A5anJ
> =Xp3s
> -----END PGP SIGNATURE-----
> 
> --tsOsTdHNUZQcU9Ye--
> 
> --===============1515233305==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> --===============1515233305==--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf