Re: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))

Keith Moore <moore@cs.utk.edu> Wed, 02 April 2003 17:07 UTC

Received: from ran.ietf.org (ran.ietf.org [10.27.6.60]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18615; Wed, 2 Apr 2003 12:07:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 190lsk-00019v-00 for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 12:18:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 190lsD-00015D-00 for ietf@ran.ietf.org; Wed, 02 Apr 2003 12:18:05 -0500
Received: from astro.cs.utk.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18307 for <ietf@ietf.org>; Wed, 2 Apr 2003 12:01:13 -0500 (EST)
Received: from astro.cs.utk.edu (localhost [127.0.0.1]) by astro.cs.utk.edu (cf 8.9.3) with SMTP id h32H3bA00658; Wed, 2 Apr 2003 12:03:38 -0500 (EST)
Date: Wed, 02 Apr 2003 12:03:37 -0500
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <john-ietf@jck.com>
Cc: moore@cs.utk.edu, bmanning@ISI.EDU, ietf@ietf.org
Subject: Re: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))
Message-Id: <20030402120337.7284bb8f.moore@cs.utk.edu>
In-Reply-To: <406328249.1049284342@p3.JCK.COM>
References: <20030402080933.608a4a9d.moore@cs.utk.edu> <200304021612.h32GCaU25262@boreas.isi.edu> <20030402112356.2c156f87.moore@cs.utk.edu> <406328249.1049284342@p3.JCK.COM>
X-Mailer: Sylpheed version 0.8.9 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> 	(i) RFC 2821 can be read (and was intended to be read)
> 	to prohibit the use of an address literal in a HELO or
> 	EHLO command unless the relevant host has no DNS name.
> 	(sections 3.6, 4.1.1.1, 4.1.4)

these days it's sort of odd to think that a host has a distinguished DNS
name - hosts quite ordinarily have either an emphemeral DNS name,
multiple DNS names, or no DNS name.

> 	(ii) The use of address literals is described as a
> 	mechanism to bypass a barrier, not one for normal use
> 	(RFC2821, section 4.1.3)

right.  about the only reasonable use of an address literal is for
testing, or to reach the postmaster at a particular host associated with
a particular address (since "postmaster" is the only address that is
guaranteed to be valid when associated with an address literal - and
even this is often not true in practice)

> 	(iii) On the other hand, the address literal "should"
> 	still be provided in the From clause of a Received
> 	field.  Received field information is expected to not be
> 	picked up by other software and protocols, but the
> 	inclusion of address information there is very
> 	leak-friendly.

this is different than using address literals in addresses.  email
addresses are defined relative to DNS names because you cannot properly
send mail to an email address without an MX lookup.  OTOH MTAs are
still expected to be hosts with addresses.

> > of course it is possible to write apps that do not use DNS,
> > but this is rarely done.
> 
> Yep.  And as pointed out earlier, we have pushed back strongly 
> against such protocol proposals and implementations.

many apps that are used in practice are not standardized; we need to be
careful about believing that what's good for standard apps is good for
every app.

I could certainly make a case for some apps to have their own naming
systems and their own name-to-address lookup mechanisms independent of
DNS, or more generally, for alternate means of mapping resource names
(say URNs) to IP addresses that did not involve DNS names or DNS
queries.  But it's difficult to believe that such apps would not employ
DNS names at all - if nothing else, for initial configuration.