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

Ted Faber <faber@ISI.EDU> Tue, 08 July 2008 00:15 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 5B3E128C370; Mon, 7 Jul 2008 17:15:31 -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 327CE28C36B for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 17:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.21
X-Spam-Level:
X-Spam-Status: No, score=-2.21 tagged_above=-999 required=5 tests=[AWL=0.389, 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 1UNkdyVpi-aE for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 17:15:29 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 50B2328C368 for <ietf@ietf.org>; Mon, 7 Jul 2008 17:15:29 -0700 (PDT)
Received: from zod.isi.edu (zod.isi.edu [128.9.168.221]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m680EwK6024949 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 7 Jul 2008 17:14:59 -0700 (PDT)
Received: (from faber@localhost) by zod.isi.edu (8.14.2/8.14.2/Submit) id m680EwIe011190; Mon, 7 Jul 2008 17:14:58 -0700 (PDT) (envelope-from faber)
Date: Mon, 07 Jul 2008 17:14:58 -0700
From: Ted Faber <faber@ISI.EDU>
To: Bill Manning <bmanning@ISI.EDU>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Message-ID: <20080708001457.GA10677@zod.isi.edu>
References: <20080707133210.AWH55905@m1.imap-partners.net> <20080707203828.GC2300@zod.isi.edu> <20080707204428.GD2300@zod.isi.edu> <20080707210431.GA17533@boreas.isi.edu> <20080707212531.GC2222@zod.isi.edu> <20080707224953.GA18872@boreas.isi.edu>
Mime-Version: 1.0
In-Reply-To: <20080707224953.GA18872@boreas.isi.edu>
User-Agent: Mutt/1.4.2.3i
X-url: http://www.isi.edu/~faber
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: faber@zod.isi.edu
Cc: 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>
Content-Type: multipart/mixed; boundary="===============0147112014=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Mon, Jul 07, 2008 at 03:49:53PM -0700, Bill Manning wrote:
> 	so... the point i was tryig to make was/is:
> 
> 	simple queries only help if you know:
> 		) the version of software running on your caching server
> 		and
> 		) the search list defined by your "resolv.conf" 

Fair enough.   (I did include the resolv.conf in the first example, but
hadn't considered the caching server.)

And I understand how a DNS name without a dot in it can be confusing.
Even with a dot in there, DNS admins (or DHCP spoofers) can put you into
a walled garden pretty easily, though.

I'm not sure I see any great benefit to using the undotted names - the
dot really indicates the "Internet brand" pretty strongly - but it seems
to function in the environments I have easy access to.  I was primarily
responding to the fellow who doubted the practicality of the idea, not
endorsing it.

-- 
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
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf