From owner-ietf@ietf.org  Tue Apr  1 00:11:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12103;
	Tue, 1 Apr 2003 00:11:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190E8a-0004DK-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 00:16:44 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190E88-0004B1-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 00:16:16 -0500
Received: from snipe.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10604
	for <ietf@ietf.org>; Mon, 31 Mar 2003 23:59:45 -0500 (EST)
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by snipe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 190DuJ-0004NQ-00; Mon, 31 Mar 2003 21:01:59 -0800
Date: Mon, 31 Mar 2003 23:56:55 -0500
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, dhc2@dcrocker.net, mrw@windriver.com, ietf@ietf.org
Subject: site locals are bankrupt
Message-Id: <20030331235655.4fea9698.moore@cs.utk.edu>
In-Reply-To: <07e401c2f7f6$79715080$ee1a4104@eagleswings>
References: <3186787045.20030331164435@brandenburg.com>
	<07e401c2f7f6$79715080$ee1a4104@eagleswings>
X-Mailer: Sylpheed version 0.8.10 (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

Tony,

You are wasting our time.  There is clear consensus to deprecate SLs.  They
were a bad idea, and people realize that now.  Your attempt to justify the
burdens they place on the network, on apps (including DNS), on routing hasn't
made them look any more attractive.  The best justification you've been able
to produce for keeping them is that they're supposedly already deployed.  Of
course that deployment is insignificant compared to the future use of IPv6. 
At any rate, nothing is likely to stop legacy products from using SLs if they
want to -- the point is to make certain that future products (especially apps)
don't have to deal with them. 

What you have totally failed to do is explain why site locals and the burdens
and complexity and unreliability that come with it are in the best interests
of the Internet as a whole, as opposed to the interests of some company that
wants to sell crippled products to its customers.

Site locals had their chance, and failed to justify themselves.  Taking them
away results in a vast improvement to IPv6.  It's time to move forward.

Keith



From owner-ietf@ietf.org  Tue Apr  1 01:18:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14541;
	Tue, 1 Apr 2003 01:18:21 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190FFA-00075i-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 01:27:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190FEV-00073O-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 01:26:55 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14424
	for <ietf@ietf.org>; Tue, 1 Apr 2003 01:10:23 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 190F0c-0006hI-00; Tue, 01 Apr 2003 01:12:34 -0500
Date: Tue, 01 Apr 2003 01:12:34 -0500
From: John C Klensin <john-ietf@jck.com>
To: Dave Crocker <dhc2@dcrocker.net>, Tony Hain <alh-ietf@tndh.net>
cc: "'Margaret Wasserman'" <mrw@windriver.com>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Thinking differently about names and addresses
Message-ID: <281541845.1049159553@p3.JCK.COM>
In-Reply-To: <3186787045.20030331164435@brandenburg.com>
References: <079601c2f7d5$32d01e70$ee1a4104@eagleswings>
 <3186787045.20030331164435@brandenburg.com>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Monday, 31 March, 2003 16:44 -0800 Dave Crocker 
<dhc2@dcrocker.net> wrote:

> Tony,
>
>>> Let's assume that there is a FooBar server in SiteA.  If
>>> another node in SiteA (NodeA) is communicating via a
>>> multi-party application to a node in SiteB (NodeB), and
>>> wants  to refer NodeB to the FooBar server in SiteA, what
>>> does it do?
>
> TH> Send a name.
>...
> In any event, please note that the suggestion that
> applications are required to use names, rather than IP
> addresses, is new.
>
> Completely new.
>
> As in, it has not been part of the Internet architecture for
> the past 25 years.
>
> So we all should be a tad careful about claiming that failure
> to use that enhancement represents a failure.  A new idea that
> is good is good, but failure to use that idea previously is
> not "broken".

Hmm.  Maybe some clarification is in order, since at least three 
different, and contradictory, claims have been made about this 
principle.

The "use names and not addresses to facilitate the transition to 
IPv6" principle was articulated some years ago, I'm pretty sure 
back when I was still Apps AD.   It was discussed at the time, 
and should not now come as a surprise to anyone.   However, my 
understanding --then and now-- was that what we agreed to was to 
try to move away from the presentation form of IP addresses on 
the user interface side of applications.  For example, we wanted 
to strongly discourage the use of addresses in URLs, we wanted 
to see an address in a telnet command or in setting up an FTP 
command channel only for debugging (if that) and so on.

Today's implied claim that the principle extends to use of names 
within and between applications is new to me.  There are all 
sorts of reasons why I think it is impractical. Certainly it is 
not something I would have consciously agreed to at any time in 
the last decade or so.  In addition to the reasons that have 
been given, there is the small matter that DNS resolvers use 
timeout logic that is measured in seconds -- tolerable for 
one-time use when an application starts up, and maybe every 
half-hour or so thereafter, but almost inconceivable each time 
an application needs to look at an address or pass an address 
reference to a machine with which it is already conducting a 
dialogue.  Worse, some applications are likely to get very 
confused if they go back to the DNS a second time and get very 
different address information (or even a different ordering of a 
set of addresses) to be used in conjunction with connections 
that are already open.

Now, this may suggest that we need new facilities.  Or perhaps 
we just need a way to say "use this address, but the same prefix 
you already have for me" or "look the name up again, and pick 
the address you get back that matches the prefix you see for 
me".  I don't know.  I am pretty sure that no one has discussed 
those issues with the applications area at any time since IPv6 
started to gell.

I'm equally concerned about statements like:

TH> Any app that sends topology locator information without 
understanding
TH> the topology is broken.

and

> That is not clear, but in any case the deployed Internet is
> not the same as it was 25 years ago. From RFC 791;

> 	A distinction is made between names, addresses, and
> 	routes [4].   A name indicates what we seek.  An address
> 	indicates where it is.  A route indicates how to get
> 	there.  The internet protocol deals primarily with
> 	addresses.  It is the task of higher level (i.e.,
> 	host-to-host or application) protocols to make the
> 	mapping from names to addresses.   The internet module
> 	maps internet addresses to local net addresses.  It is
> 	the task of lower level (i.e., local net or gateways)
> 	procedures to make the mapping from local net addresses
> 	to routes.

> Mapping names to addresses is a simple task. One could argue
> that it was so simple that apps took the shortcut of using the
> 'where' to also define the 'what'. That does not mean the
> requirement for apps to keep a clear context for 'what' is a
> new requirement.

Tony, I agree with the first statement.  I'd almost suggest that 
it is self-evidently true, which may be the point you are trying 
to make. But we get different meanings from the RFC 791 quote, 
and that may be a lot of the difference in perspective here.  At 
the time 791 was written, addresses were not routes, or bound to 
routes.  Consequently, it would have been inappropriate to refer 
to them as "topology locators".  They were just addresses. 
Routes, and hence topology and topology locators, were 
invisible, not only to the applications, but even to TCP.  An 
application that uses addresses in the 791 sense isn't involved 
with topology at all and has no clue about network topology. 
Even the "here" and "not here" implied by testing whether an 
address was on the same network was, and remains, invisible to 
most applications.

When we introduced subnetting and then CIDR and, more 
specifically, route aggregation, we changed the character of 
that name/ address/ route separation.  For the first time, an 
address manifestly implied more about topology than "same 
network or not".  In the process, we effectively introduced the 
notions of PI and PD space, and made multihoming nearly 
impossible for anyone but very large enterprises plus those with 
the financial resources to bully their way in.  But, even then, 
I suggest that calling an address a "topology locator" is 
something of a stretch, so, while your statement is true about 
"topology locators", it is not clear to me that it applies to IP 
addresses, at least in IPv4.

The IPng effort started off with a number of problems to be 
solved.   More address space was one.  My recollection is that 
getting multihoming back was another and that we knew that we 
had a route-scaling problem as well as an address-scaling one. 
This multiple-prefix-per-host stuff is dandy in theory, but 
we've yet to see it work to permit widespread multihoming 
without exploding the routing tables.  My own sense is that it 
will not work unless we end up dividing the world up into a 
handful of super-ISPs with local ISPs organized in strict 
hierarchy.  To overdramatize things a bit (I hope), if the IPv6 
architecture requires that business model in order to keep 
routing working, IPv6 will fail and, probably, so will the 
Internet.

My hope continues to be that we will eventually devise, and 
evolve to, a routing architecture with much better scaling 
properties than full-knowledge link state models and Dijkstra, 
or Dijkstra-equivalent, calculations performed on each state 
change.  While there hasn't been much visible motion, I don't 
believe the IETF community has given up on that class of change. 
To decide that IPv6 addresses are locators that are bound to the 
topology of the network, and doing applications design on that 
basis, runs the risk of precluding such routing options.    I 
haven't seen where or when the community has agreed that "IPv6 
Address == topological locator" as a matter of architecture and 
I'm fairly relieved by that.

And, as Dave Crocker pointed out (if I interpret his remarks 
correctly), if IPv6 addresses are topology locators, then we are 
going to need identifiers that have the appropriate binding 
properties to those addresses.  The DNS won't do it: it is too 
slow, updates take too long, inconsistent responses from 
different servers while updates propagate are the norm, and it 
isn't tightly enough bound to the addressing mechanism to be 
able to yield "best address for purpose" information.

My own guess is that the principle behind the statement you 
quote from 791 is correct, but the terminology may need to be 
adjusted.  Today, I would say that there is an important 
separation between name, address-identifier, and 
topology-locator.  If IPv6 addresses are the topology-locators 
of the IPv6 universe, then there isn't going to be much real 
progress on application upgrading and deployment until we invent 
address-identifiers.  On the other hand, if IPv6 addresses are 
to serve as address-identifiers (as IPv4 addresses have done 
since the 70s), then we shouldn't expect applications to either 
understand any hidden topology semantics they might have or to 
refrain from using the addresses because those topology 
semantics exist.

  regards,
    john





From owner-ietf@ietf.org  Tue Apr  1 08:18:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09266;
	Tue, 1 Apr 2003 08:18:31 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190Lk3-0001BP-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 08:23:55 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190LiR-000158-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 08:22:15 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08763
	for <ietf@ietf.org>; Tue, 1 Apr 2003 08:05:39 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 24A716238A; Tue,  1 Apr 2003 15:08:06 +0200 (CEST)
Date: Tue, 01 Apr 2003 15:08:06 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dave Crocker <dhc2@dcrocker.net>
Cc: ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
Message-ID: <125950000.1049202486@askvoll.hjemme.alvestrand.no>
In-Reply-To: <3186787045.20030331164435@brandenburg.com>
References: <079601c2f7d5$32d01e70$ee1a4104@eagleswings>
 <3186787045.20030331164435@brandenburg.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On mandag, mars 31, 2003 16:44:35 -0800 Dave Crocker <dhc2@dcrocker.net> 
wrote:

> In any event, please note that the suggestion that applications are
> required to use names, rather than IP addresses, is new.
>
> Completely new.
>
> As in, it has not been part of the Internet architecture for the past 25
> years.

RFC 1958, June 1996:

4. Name and address issues

   4.1 Avoid any design that requires addresses to be hard coded or
   stored on non-volatile storage (except of course where this is an
   essential requirement as in a name server or configuration server).
   In general, user applications should use names rather than addresses.

yes, "required" is new, and IMHO unspportable.

                    Harald




From owner-ietf@ietf.org  Tue Apr  1 10:08:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17020;
	Tue, 1 Apr 2003 10:08:38 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190NY2-0002P6-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 10:19:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1906hR-0002rF-00
	for ietf@ran.ietf.org; Mon, 31 Mar 2003 16:20:13 -0500
Received: from carwash.centive.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA24467
	for <ietf@ietf.org>; Mon, 31 Mar 2003 16:03:48 -0500 (EST)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (NAVGW 2.5.2.11) with SMTP id M2003033116104622650
 for <ietf@ietf.org>; Mon, 31 Mar 2003 16:10:46 -0500
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 31 Mar 2003 16:04:02 -0500
Message-ID: <3E88AD42.3090000@centive.com>
Date: Mon, 31 Mar 2003 16:04:02 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Thinking differently about the site local problem (was:  RE:
 site local addresses (was Re: Fw: Welcome to the InterNAT...))
References: <077601c2f7be$e0fcdc70$ee1a4104@eagleswings>
In-Reply-To: <077601c2f7be$e0fcdc70$ee1a4104@eagleswings>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Mar 2003 21:04:02.0923 (UTC) FILETIME=[0ED6A3B0:01C2F7C9]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony Hain wrote:

>Margaret Wasserman wrote:
>  
>
>>Of course, in the case of site-local addresses, you don't 
>>know for sure that you reached the _correct_ peer, unless you 
>>know for sure that the node you want to reach is in your 
>>site.  
>>    
>>
>
>Since the address block is ambiguous, routing will assure that if you
>reach a node it is the correct one.
>
That's backwards: Since the address block is ambiguous, routing *cannot* 
assure that if you reach a node it is the correct one.  Nobody can, 
because we equate addresses with identities.

Consider a  peer-to-peer conferencing session, with three participants 
A, B, and C.  A and B are at the same site; C is at a separate site; 
both sites use the same range of site-local addresses.  Each has two 
addresses, AG, BG, CG and AL, BL, CL (Global and Local).  A initiates 
the session by connecting to B and C (assume for the moment that this is 
not a problem).  B and C provide A with their addresses; to complete the 
mesh, A tells B to connect to C at CG or CL.  Now, B isn't going to 
connect to *both*, so it'll have some heuristic to pick one.  Suppose it 
picks CL (*).  But, whoops, B's site has some host D, with DL==CL.  So B 
winds up connecting to the wrong host, and doesn't realize it.

(*) Not an unreasonable supposition.  If the app is looking at the 
addresses, it might well notice that CL is on a locally attached subnet, 
and use that.  Or the app might connect to both in parallel 
(non-blocking connect()), and use the address it reaches first, as a 
first cut at discovering the most efficient path (that's what I did when 
I implemented this some time back).  Being on the same network, D will 
probably respond before C.

-- 
/============================================================\
|John Stracke      |jstracke@centive.com                     |
|Principal Engineer|http://www.centive.com                   |
|Centive           |My opinions are my own.                  |
|============================================================|
|"God does not play games with His loyal servants." "Whoo-ee,|
|where have you *been*?" --_Good Omens_                      |
\============================================================/







From owner-ietf@ietf.org  Tue Apr  1 10:08:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17068;
	Tue, 1 Apr 2003 10:08:41 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190NW6-0000Tv-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 10:17:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1905K9-0006dp-00
	for ietf@ran.ietf.org; Mon, 31 Mar 2003 14:52:05 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20185
	for <ietf@ietf.org>; Mon, 31 Mar 2003 14:35:40 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19056O-00057i-00; Mon, 31 Mar 2003 14:37:52 -0500
Date: Mon, 31 Mar 2003 14:37:52 -0500
From: John C Klensin <john@jck.com>
To: Bill Manning <bmanning@ISI.EDU>, Margaret Wasserman <mrw@windriver.com>
cc: "alh-ietf@tndh.net" <alh-ietf@tndh.net>, "ietf@ietf.org" <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: <243461298.1049121472@p3.JCK.COM>
In-Reply-To: <200303311701.h2VH1h615515@boreas.isi.edu>
References:  <200303311701.h2VH1h615515@boreas.isi.edu>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Monday, 31 March, 2003 09:01 -0800 Bill Manning 
<bmanning@ISI.EDU> wrote:

> 	Is may be worth noting that RIRs have -NEVER- made
> presumptions 	on routability of the delegations they make.

I believe that, although I remember some arguments within ARIN 
back when I was on the AC about whether it was legitimate or 
rational to make allocations that were believed to be 
unroutable.   But I've gotten several private notes that lead me 
to believe that a lot of the community doesn't believe this or, 
more specifically, believes that everyone will fall into line 
and route any delegation that an RIR makes directly and, hence, 
that any RIR allocation will, de facto, become routable.

     john









From owner-ietf@ietf.org  Tue Apr  1 10:19:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19145;
	Tue, 1 Apr 2003 10:19:45 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190Nje-0007CV-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 10:31:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190Niz-0006vq-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 10:30:57 -0500
Received: from tndh.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18438
	for <ietf@ietf.org>; Tue, 1 Apr 2003 10:14:13 -0500 (EST)
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S23AB3> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 01 Apr 2003 07:16:37 -0800
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'John C Klensin'" <john-ietf@jck.com>,
        "'Dave Crocker'" <dhc2@dcrocker.net>
Cc: "'Margaret Wasserman'" <mrw@windriver.com>, <ietf@ietf.org>
Subject: RE: Thinking differently about names and addresses
Date: Tue, 1 Apr 2003 07:16:38 -0800
Message-ID: <085d01c2f861$b0fbbfc0$ee1a4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <281541845.1049159553@p3.JCK.COM>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA19145

John,

I am not going to comment on each point, but your general perspective
highlights the problem at hand. The discussions on the multi6 mail list
have basically been about how the routing community believes the address
is the topology locator, while your & Dave's comments show the app
community believes it is an identifier. Where the two communities agree
is that the DNS as currently deployed and operated is not up to the task
of handling the identifier role. My point is that this is due more to
implementation & operation than architecture. Also I believe the multi6
discussion about creating a new identifier, to get the app community to
stop camping on the topology locator, will end up creating a distributed
database infrastructure almost identical to DNS. We don't need two of
those, so we should fix DNS.

I disagree with the perspective that subnetting or CIDR changed the
character of the address. It continues to indicate on the local network
or not, and anything not is handed to a node tasked to figure out the
next hop. I think what has changed since RFC 791 is the geographic scope
of the local network, not the architectural concepts.

Tony


> -----Original Message-----
> From: John C Klensin [mailto:john-ietf@jck.com] 
> Sent: Monday, March 31, 2003 10:13 PM
> To: Dave Crocker; Tony Hain
> Cc: 'Margaret Wasserman'; ietf@ietf.org
> Subject: Re: Thinking differently about names and addresses
> 
> 
> --On Monday, 31 March, 2003 16:44 -0800 Dave Crocker 
> <dhc2@dcrocker.net> wrote:
> 
> > Tony,
> >
> >>> Let's assume that there is a FooBar server in SiteA.  If another 
> >>> node in SiteA (NodeA) is communicating via a multi-party 
> application 
> >>> to a node in SiteB (NodeB), and wants  to refer NodeB to 
> the FooBar 
> >>> server in SiteA, what does it do?
> >
> > TH> Send a name.
> >...
> > In any event, please note that the suggestion that  
> applications are 
> >required to use names, rather than IP  addresses, is new.
> >
> > Completely new.
> >
> > As in, it has not been part of the Internet architecture 
> for the past 
> > 25 years.
> >
> > So we all should be a tad careful about claiming that 
> failure to use 
> > that enhancement represents a failure.  A new idea that is good is 
> > good, but failure to use that idea previously is not "broken".
> 
> Hmm.  Maybe some clarification is in order, since at least three 
> different, and contradictory, claims have been made about this 
> principle.
> 
> The "use names and not addresses to facilitate the transition to 
> IPv6" principle was articulated some years ago, I'm pretty sure 
> back when I was still Apps AD.   It was discussed at the time, 
> and should not now come as a surprise to anyone.   However, my 
> understanding --then and now-- was that what we agreed to was to 
> try to move away from the presentation form of IP addresses on 
> the user interface side of applications.  For example, we wanted 
> to strongly discourage the use of addresses in URLs, we wanted 
> to see an address in a telnet command or in setting up an FTP 
> command channel only for debugging (if that) and so on.
> 
> Today's implied claim that the principle extends to use of names 
> within and between applications is new to me.  There are all 
> sorts of reasons why I think it is impractical. Certainly it is 
> not something I would have consciously agreed to at any time in 
> the last decade or so.  In addition to the reasons that have 
> been given, there is the small matter that DNS resolvers use 
> timeout logic that is measured in seconds -- tolerable for 
> one-time use when an application starts up, and maybe every 
> half-hour or so thereafter, but almost inconceivable each time 
> an application needs to look at an address or pass an address 
> reference to a machine with which it is already conducting a 
> dialogue.  Worse, some applications are likely to get very 
> confused if they go back to the DNS a second time and get very 
> different address information (or even a different ordering of a 
> set of addresses) to be used in conjunction with connections 
> that are already open.
> 
> Now, this may suggest that we need new facilities.  Or perhaps 
> we just need a way to say "use this address, but the same prefix 
> you already have for me" or "look the name up again, and pick 
> the address you get back that matches the prefix you see for 
> me".  I don't know.  I am pretty sure that no one has discussed 
> those issues with the applications area at any time since IPv6 
> started to gell.
> 
> I'm equally concerned about statements like:
> 
> TH> Any app that sends topology locator information without
> understanding
> TH> the topology is broken.
> 
> and
> 
> > That is not clear, but in any case the deployed Internet is not the 
> > same as it was 25 years ago. From RFC 791;
> 
> > 	A distinction is made between names, addresses, and
> > 	routes [4].   A name indicates what we seek.  An address
> > 	indicates where it is.  A route indicates how to get
> > 	there.  The internet protocol deals primarily with
> > 	addresses.  It is the task of higher level (i.e.,
> > 	host-to-host or application) protocols to make the
> > 	mapping from names to addresses.   The internet module
> > 	maps internet addresses to local net addresses.  It is
> > 	the task of lower level (i.e., local net or gateways)
> > 	procedures to make the mapping from local net addresses
> > 	to routes.
> 
> > Mapping names to addresses is a simple task. One could 
> argue that it 
> > was so simple that apps took the shortcut of using the 
> 'where' to also 
> > define the 'what'. That does not mean the requirement for 
> apps to keep 
> > a clear context for 'what' is a new requirement.
> 
> Tony, I agree with the first statement.  I'd almost suggest that 
> it is self-evidently true, which may be the point you are trying 
> to make. But we get different meanings from the RFC 791 quote, 
> and that may be a lot of the difference in perspective here.  At 
> the time 791 was written, addresses were not routes, or bound to 
> routes.  Consequently, it would have been inappropriate to refer 
> to them as "topology locators".  They were just addresses. 
> Routes, and hence topology and topology locators, were 
> invisible, not only to the applications, but even to TCP.  An 
> application that uses addresses in the 791 sense isn't involved 
> with topology at all and has no clue about network topology. 
> Even the "here" and "not here" implied by testing whether an 
> address was on the same network was, and remains, invisible to 
> most applications.
> 
> When we introduced subnetting and then CIDR and, more 
> specifically, route aggregation, we changed the character of 
> that name/ address/ route separation.  For the first time, an 
> address manifestly implied more about topology than "same 
> network or not".  In the process, we effectively introduced the 
> notions of PI and PD space, and made multihoming nearly 
> impossible for anyone but very large enterprises plus those with 
> the financial resources to bully their way in.  But, even then, 
> I suggest that calling an address a "topology locator" is 
> something of a stretch, so, while your statement is true about 
> "topology locators", it is not clear to me that it applies to IP 
> addresses, at least in IPv4.
> 
> The IPng effort started off with a number of problems to be 
> solved.   More address space was one.  My recollection is that 
> getting multihoming back was another and that we knew that we 
> had a route-scaling problem as well as an address-scaling one. 
> This multiple-prefix-per-host stuff is dandy in theory, but 
> we've yet to see it work to permit widespread multihoming 
> without exploding the routing tables.  My own sense is that it 
> will not work unless we end up dividing the world up into a 
> handful of super-ISPs with local ISPs organized in strict 
> hierarchy.  To overdramatize things a bit (I hope), if the IPv6 
> architecture requires that business model in order to keep 
> routing working, IPv6 will fail and, probably, so will the 
> Internet.
> 
> My hope continues to be that we will eventually devise, and 
> evolve to, a routing architecture with much better scaling 
> properties than full-knowledge link state models and Dijkstra, 
> or Dijkstra-equivalent, calculations performed on each state 
> change.  While there hasn't been much visible motion, I don't 
> believe the IETF community has given up on that class of change. 
> To decide that IPv6 addresses are locators that are bound to the 
> topology of the network, and doing applications design on that 
> basis, runs the risk of precluding such routing options.    I 
> haven't seen where or when the community has agreed that "IPv6 
> Address == topological locator" as a matter of architecture and 
> I'm fairly relieved by that.
> 
> And, as Dave Crocker pointed out (if I interpret his remarks 
> correctly), if IPv6 addresses are topology locators, then we are 
> going to need identifiers that have the appropriate binding 
> properties to those addresses.  The DNS won't do it: it is too 
> slow, updates take too long, inconsistent responses from 
> different servers while updates propagate are the norm, and it 
> isn't tightly enough bound to the addressing mechanism to be 
> able to yield "best address for purpose" information.
> 
> My own guess is that the principle behind the statement you 
> quote from 791 is correct, but the terminology may need to be 
> adjusted.  Today, I would say that there is an important 
> separation between name, address-identifier, and 
> topology-locator.  If IPv6 addresses are the topology-locators 
> of the IPv6 universe, then there isn't going to be much real 
> progress on application upgrading and deployment until we invent 
> address-identifiers.  On the other hand, if IPv6 addresses are 
> to serve as address-identifiers (as IPv4 addresses have done 
> since the 70s), then we shouldn't expect applications to either 
> understand any hidden topology semantics they might have or to 
> refrain from using the addresses because those topology 
> semantics exist.
> 
>   regards,
>     john
> 
> 




From owner-ietf@ietf.org  Tue Apr  1 10:35:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20771;
	Tue, 1 Apr 2003 10:35:45 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190Nz9-0001Kt-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 10:47:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19070B-0004mR-00
	for ietf@ran.ietf.org; Mon, 31 Mar 2003 16:39:35 -0500
Received: from carwash.centive.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA25189
	for <ietf@ietf.org>; Mon, 31 Mar 2003 16:23:10 -0500 (EST)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (NAVGW 2.5.2.11) with SMTP id M2003033116300112687
 for <ietf@ietf.org>; Mon, 31 Mar 2003 16:30:01 -0500
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 31 Mar 2003 16:23:18 -0500
Message-ID: <3E88B1C6.3080403@centive.com>
Date: Mon, 31 Mar 2003 16:23:18 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Thinking differently about the site local problem (was:  RE:
 site local addresses (was Re: Fw: Welcome to the InterNAT...))
References: <077601c2f7be$e0fcdc70$ee1a4104@eagleswings> <3E88A268.4010309@cisco.com> <012101c2f7c9$9a9a5d10$93b58742@ssprunk>
In-Reply-To: <012101c2f7c9$9a9a5d10$93b58742@ssprunk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Mar 2003 21:23:18.0288 (UTC) FILETIME=[BF7D5900:01C2F7CB]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Stephen Sprunk wrote:

>I've dealt with many companies interconnecting where both use RFC1918
>space -- NAT is the first thing discussed.  You forget, these people are
>connecting for a _business reason_ and there is real money to be lost if
>they mess up.
>  
>
And how much real money do they lose by having to work around those NATs?

-- 
/============================================================\
|John Stracke      |jstracke@centive.com                     |
|Principal Engineer|http://www.centive.com                   |
|Centive           |My opinions are my own.                  |
|============================================================|
|"God does not play games with His loyal servants." "Whoo-ee,|
|where have you *been*?" --_Good Omens_                      |
\============================================================/







From owner-ietf@ietf.org  Tue Apr  1 10:44:09 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21544;
	Tue, 1 Apr 2003 10:44:08 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190O15-0001Xx-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 10:49:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1907tu-00068V-00
	for ietf@ran.ietf.org; Mon, 31 Mar 2003 17:37:10 -0500
Received: from ginger.lcs.mit.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28172
	for <ietf@ietf.org>; Mon, 31 Mar 2003 17:20:44 -0500 (EST)
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h2VMN9tU029073;
	Mon, 31 Mar 2003 17:23:09 -0500
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h2VMN9GY029072;
	Mon, 31 Mar 2003 17:23:09 -0500
Date: Mon, 31 Mar 2003 17:23:09 -0500
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200303312223.h2VMN9GY029072@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Keith Moore <moore@cs.utk.edu>

    > actually it's bad to force all apps to use DNS names - which are often
    > less reliable, slower, less correct, and more ambiguous than IP
    > addresses.

This is like saying it's bad to force people to use cars/busses/whatever
because they occasionally break, and everyone should walk everytime they need
to go anywhere, because that's more reliable. That works in an agrarian
society, but not an industrialized one.

We have multiple namespaces, each with different characteristics for the
names, for very good reasons. If we really need a name with characteristic A,
and we instead wind up using one with characteristic ~A "because it's more
reliable", then that's not good.

If we have a need for a name, and the optimal characteristics for that name
are those of an address (i.e. the topological location of an interface to the
network), then fine, use an address. If not, don't.

If the system for mapping from one namespace to another has problems, we
ought to fix it, not say "oh, we'll just stop using it".

Don't try and make everything into a nail because the hammer is the most
reliable tool you have.

	Noel





From owner-ietf@ietf.org  Tue Apr  1 10:44:09 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21541;
	Tue, 1 Apr 2003 10:44:08 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190O16-0001YK-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 10:49:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190ARp-0002gf-00
	for ietf@ran.ietf.org; Mon, 31 Mar 2003 20:20:21 -0500
Received: from carmen.ipv6.tilab.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05286
	for <ietf@ietf.org>; Mon, 31 Mar 2003 20:03:52 -0500 (EST)
Received: from carmen.ipv6.tilab.com (localhost [IPv6:::1])
	by carmen.ipv6.tilab.com (8.12.8/8.12.3) with ESMTP id h31131EI016104
	for <ietf@ietf.org>; Tue, 1 Apr 2003 03:03:01 +0200 (MEST)
Received: (from root@localhost)
	by carmen.ipv6.tilab.com (8.12.8/8.12.3/Submit) id h31131TE016103
	for ietf@ietf.org; Tue, 1 Apr 2003 03:03:01 +0200 (MEST)
Date: Tue, 1 Apr 2003 03:03:01 +0200 (MEST)
From: Super-User <root@carmen.ipv6.tilab.com>
Message-Id: <200304010103.h31131TE016103@carmen.ipv6.tilab.com>
To: ietf@ietf.org
Subject: The IETF_Censored mailing list
Sender: owner-ietf@ietf.org
Precedence: bulk


                        The IETF_Censored mailing list
                                       
   At times, the IETF list is subject to debates that have little to do
   with the purposes for which the IETF list was created. Some people
   would appreciate a "quieter" forum for the relevant debates that take
   place, but the IETF's policy of openness has so far prevented the IETF
   from imposing any censorship policy on the IETF@ietf.org list.
   
   To give people an alternative, there is a list called
   "ietf_censored@carmen.ipv6.cselt.it".
   
   This list is a sublist (that is, it gets the same messages as) the
   open IETF discussion list. However, this list will not forward all
   messages; in particular, the filters have been set so that persons and
   discussions that are, in the view of Raffaele D'Albenzio, irrelevant
   to the IETF list are not forwarded.
   
   Because this filter is automated, the criteria include:
     * Well known troublemakers
     * Well known crosspostings
     * Subjects that have led to recent non-conclusive exchanges
     * Some ways to say "unsubscribe"
     * Some "out-of-office-reply" messages
       
   To join the list, send the word "subscribe" in the BODY of a message
   to ietf_censored-request@carmen.ipv6.cselt.it (the URL here is an RFC
   2368 mailto URL that does the Right Thing).
   
   To unsubscribe, send the word "unsubscribe" in the BODY of a message
   to ietf_censored-request@carmen.ipv6.cselt.it. Do not send to the list
   - your message will be filtered!
   (members of the main IETF list itself must follow instructions for
   that list, of course. You are only a member of ietf_censored if there
   is a comment on the bottom of your IETF list mail saying that the
   message has been sent through the ietf_censored list.)
   
   For fun, there is a special list for the rejected messages:
   ietf_censored-rejects@carmen.ipv6.cselt.it - subscribe in the same
   fashion, by mail to ietf_censored-rejects-request@carmen.ipv6.cselt.it
   
   By public request, the current set of filters are listed at
   http://vesuvio.ipv6.tilab.com/cgi-bin/ietf_censored-filters
   
   This page is http://carmen.ipv6.cselt.it/ietf_censored.html, and is
   posted monthly in text form to ietf@ietf.org
     _________________________________________________________________
   
   Raffaele D'Albenzio < root@carmen.ipv6.cselt.it>





From owner-ietf@ietf.org  Tue Apr  1 10:44:09 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21542;
	Tue, 1 Apr 2003 10:44:08 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190O15-0001YE-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 10:49:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190909-0004DG-00
	for ietf@ran.ietf.org; Mon, 31 Mar 2003 18:47:41 -0500
Received: from ginger.lcs.mit.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02332
	for <ietf@ietf.org>; Mon, 31 Mar 2003 18:31:15 -0500 (EST)
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h2VNXdtU029393;
	Mon, 31 Mar 2003 18:33:39 -0500
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h2VNXdaA029392;
	Mon, 31 Mar 2003 18:33:39 -0500
Date: Mon, 31 Mar 2003 18:33:39 -0500
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200303312333.h2VNXdaA029392@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Valdis.Kletnieks@vt.edu

    >> Effectively this could be resolved by having one globally
    >> unique identifier per node.

    > Paging Noel Chiappa.... Paging Noel Chiappa.... ;)

Ah, one moment, if I may:

  "his books, he always said, contained the teachings of his master,
  Socrates; ... what [Plato] had to teach could only be learned as fire is
  kindled, by the touch of the flame itself."

	- Mary Renault, 'Fire From Heaven'

The heart of all my knowledge on this matter I got from Jerry Saltzer, in
particular the paper that was reprinted as RFC-1498, "On the Naming and
Binding of Network Destinations". I have merely been repeating what seemed to
me a good idea.

	Noel





From owner-ietf@ietf.org  Tue Apr  1 10:49:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22635;
	Tue, 1 Apr 2003 10:49:34 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190O8s-0002JN-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 10:57:42 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190B2t-0004dg-00
	for ietf@ran.ietf.org; Mon, 31 Mar 2003 20:58:39 -0500
Received: from as.vix.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06490
	for <ietf@ietf.org>; Mon, 31 Mar 2003 20:42:12 -0500 (EST)
Received: by as.vix.com (Postfix, from userid 716)
	id 65634379EF4; Tue,  1 Apr 2003 01:44:37 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Fw: Welcome to the InterNAT...
References: <Pine.GSO.4.50.0303281505210.10366-100000@artemis.ee.surrey.ac.uk>
From: Paul Vixie <vixie@vix.com>
Date: 01 Apr 2003 01:44:37 +0000
In-Reply-To: <Pine.GSO.4.50.0303281505210.10366-100000@artemis.ee.surrey.ac.uk>
Message-ID: <g3wuifat4q.fsf@as.vix.com>
Lines: 17
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> > heck, TCP breaks if you change an address out from under it, so it's
> > hardly surprising that apps using TCP break under similar conditions.
> ...
> hosts could advertise static loopback addresses. Bind TCP to the
> static loopback address.

we do this.  however, it only works inside a routing domain of a /32 (or /128)
route.  in our case we can move hosts anywhere we want within what i think is
being called here a "site", without changing dns or upsetting tcp.  (i often
move my laptop from location to location within the routing domain, without
having to restart any of my suspended tcp sessions.  once we even moved a 
server from redwood city to palo alto, since it was alone on its UPS.)

injecting /32 (or /128) routes into the internet core to make tcp portability
work world wide seems like it wouldn't scale very well.
-- 
Paul Vixie





From owner-ietf@ietf.org  Tue Apr  1 11:19:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25734;
	Tue, 1 Apr 2003 11:19:23 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190Oat-0008I9-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 11:26:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190OZs-0008B9-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 11:25:36 -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 LAA24336
	for <ietf@ietf.org>; Tue, 1 Apr 2003 11:08:59 -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 h31GBHA17755;
        Tue, 1 Apr 2003 11:11:18 -0500 (EST)
Date: Tue, 1 Apr 2003 11:11:17 -0500
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, john-ietf@jck.com, dhc2@dcrocker.net, mrw@windriver.com,
        ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
Message-Id: <20030401111117.47900bcb.moore@cs.utk.edu>
In-Reply-To: <085d01c2f861$b0fbbfc0$ee1a4104@eagleswings>
References: <281541845.1049159553@p3.JCK.COM>
	<085d01c2f861$b0fbbfc0$ee1a4104@eagleswings>
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 am not going to comment on each point, but your general perspective
> highlights the problem at hand. The discussions on the multi6 mail
> list have basically been about how the routing community believes the
> address is the topology locator, while your & Dave's comments show the
> app community believes it is an identifier.

it's clear that it is both of these, and furthermore that this was a
deliberate design compromise for the sake of reduced complexity.

> Where the two communities
> agree is that the DNS as currently deployed and operated is not up to
> the task of handling the identifier role. My point is that this is due
> more to implementation & operation than architecture.

disagree.  it's largely a consequence of the design decision to make the
DNS namespace federated and the lookup widely distributed across the
network.  if DNS didn't work this way, it wouldn't be nearly as usable
for the things we use DNS for.  the fact that DNS doesn't solve all
naming problems shouldn't bother us any more than the fact that IP
doesn't solve all naming problems.

> Also I believe
> the multi6 discussion about creating a new identifier, to get the app
> community to stop camping on the topology locator, will end up
> creating a distributed database infrastructure almost identical to
> DNS. 

if what you claim is true (I haven't followed multi6) it's clearly
unworkable.

to ease transition, any new identifier needs to use the same structure
as an IP address; and indirection is far better handled as a side-effect
of sending a packet than by requiring an explicit lookup.  also,
proactive propagation of updates (replication) is far better at
producing reliable results than retroactive propagation (cacheing). IOW,
mobile IP is a lot closer to a reasonable solution to this problem than
DNS.

> We don't need two of those, so we should fix DNS.

DNS could certainly be improved in various ways, but you can't fix DNS
to serve the purpose you want it to serve.

Keith




From owner-ietf@ietf.org  Tue Apr  1 11:26:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26303;
	Tue, 1 Apr 2003 11:26:50 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190Ome-0002mc-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 11:38:48 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190OmM-0002ht-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 11:38:30 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25982
	for <ietf@ietf.org>; Tue, 1 Apr 2003 11:21:53 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h31GO0831567;
	Tue, 1 Apr 2003 08:24:01 -0800
Date: Tue, 1 Apr 2003 08:22:35 -0800
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <5854435704.20030401082235@brandenburg.com>
To: "Tony Hain" <alh-ietf@tndh.net>
CC: ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
In-Reply-To: <085d01c2f861$b0fbbfc0$ee1a4104@eagleswings>
References: <085d01c2f861$b0fbbfc0$ee1a4104@eagleswings>
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

Tony,

TH>  The discussions on the multi6 mail list
TH> have basically been about how the routing community believes the address
TH> is the topology locator, while your & Dave's comments show the app
TH> community believes it is an identifier.

By definition, an address is a topology indicator.  Always.

The point that I was trying to make is that the uniqueness of an
address's bits permits its use as an uninterrupted label, ie, a name.
(Up a few layers, this is the basis for including URL's in the set of
URI's.)

So this is not about competing definitions of the bits, but different
USES of them.  IP needs to interpret those bits.  Hence, it MUST handle
them as topological indicators.  Apps that use IP addresses use them as
simple labels.


TH>  Where the two communities agree
TH> is that the DNS as currently deployed and operated is not up to the task
TH> of handling the identifier role. My point is that this is due more to
TH> implementation & operation than architecture.

Responding to this point takes us into the world of solutions. I suspect
we will all find this topic more productive (and probably more pleasant)
when we move into that mode.


TH> Also I believe the multi6
TH> discussion about creating a new identifier, to get the app community to
TH> stop camping on the topology locator, will end up creating a distributed
TH> database infrastructure almost identical to DNS. We don't need two of
TH> those, so we should fix DNS.

That was my own view roughly 10 years ago, when Noel Chiappa was pushing
for use of an end-point identifier, as part of what is now IPv6.

At this stage, I would want to hear the requirements (or probably
better, the desired usage scenarios) before being certain that a
modified DNS is the answer.


TH> I disagree with the perspective that subnetting or CIDR changed the
TH> character of the address.

Before:  IP addresses contained no topological information.

After:   IP addresses contained quite a bit of topological information
AND that information was (is) used quite heavily.

A change that permits a routing table to be reduced massively
necessarily involves changing the character of something.

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Tue Apr  1 11:26:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26305;
	Tue, 1 Apr 2003 11:26:51 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190Ome-0002mi-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 11:38:48 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190OmN-0002hv-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 11:38:31 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25985
	for <ietf@ietf.org>; Tue, 1 Apr 2003 11:21:54 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h31GNx831563;
	Tue, 1 Apr 2003 08:23:59 -0800
Date: Tue, 1 Apr 2003 08:08:59 -0800
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <17053620201.20030401080859@brandenburg.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: Dave Crocker <dhc2@dcrocker.net>, ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
In-Reply-To: <125950000.1049202486@askvoll.hjemme.alvestrand.no>
References: <079601c2f7d5$32d01e70$ee1a4104@eagleswings>
 <3186787045.20030331164435@brandenburg.com>
 <125950000.1049202486@askvoll.hjemme.alvestrand.no>
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

Harald,

>> In any event, please note that the suggestion that applications are
>> required to use names, rather than IP addresses, is new.
...
>> As in, it has not been part of the Internet architecture for the past 25
>> years.

HTA> RFC 1958, June 1996:

HTA> 4. Name and address issues

HTA> yes, "required" is new, and IMHO unspportable.

whimsical:  ok, so only *20* years...

serious: the "required" was intended as the only significant point.
(this is worth emphasizing, since it is key to the question of whether
apps are "broken" or whether we have a new problem to solve.)

Obviously, names have been a part of the Internet architecture dating
back before there was an Internet architecture. (My decrepit memory
thinks Hosts.txt was present in 1972. If not, it was certainly very
quickly thereafter.)

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Tue Apr  1 11:29:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26838;
	Tue, 1 Apr 2003 11:29:01 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190OpQ-00032S-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 11:41:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190OoD-0002rP-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 11:40:25 -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 LAA26057
	for <ietf@ietf.org>; Tue, 1 Apr 2003 11:23:47 -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 h31GQCA17960;
        Tue, 1 Apr 2003 11:26:13 -0500 (EST)
Date: Tue, 1 Apr 2003 11:26:12 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: Thinking differently about the site local problem (was: RE:
 site local addresses (was Re: Fw: Welcome to the InterNAT...))
Message-Id: <20030401112612.052a0c4d.moore@cs.utk.edu>
In-Reply-To: <200303312223.h2VMN9GY029072@ginger.lcs.mit.edu>
References: <200303312223.h2VMN9GY029072@ginger.lcs.mit.edu>
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

>     > actually it's bad to force all apps to use DNS names - which are
>     > often less reliable, slower, less correct, and more ambiguous
>     > than IP addresses.
> 
> This is like saying it's bad to force people to use
> cars/busses/whatever because they occasionally break, and everyone
> should walk everytime they need to go anywhere, because that's more
> reliable.

Nope.  Forcing apps to use DNS names is like telling people that they
must always give taxi drivers the names of the places where they want
to go, rather than the addresses of those places, and that those people
shouldn't mind when the taxi drivers take them to the wrong places, or
run up fares and delays looking for those places.

> We have multiple namespaces, each with different characteristics for
> the names, for very good reasons. If we really need a name with
> characteristic A, and we instead wind up using one with characteristic
> ~A "because it's more reliable", then that's not good.

Indeed, but let's look at this more closely.  We essentially have two
name spaces of concern here: DNS and IP.  DNS is slow, imprecise, not
terribly reliable, not always available, not always in sync with
reality. IP is fast, precise, reliable, but tied to location, which is
often the wrong thing in theory and occasionally the wrong thing in
practice. I suspect we agree that neither one is well-adapted for naming
connection endpoints, and that in an ideal world there would be a
separate namespace for this that provided fast, precise, reliable,
secure indirection that was not tied to location(assuming, of course,
that the cost of maintaining a separate name space and the extra mapping
layers would be justified by the additional utility - something that has
not been demonstrated).  But Tony's argument is that we should *always*
use DNS instead of IP even when IP works better for our purposes -
merely in order to preserve a dubious feature of IPv6.

> If we have a need for a name, and the optimal characteristics for that
> name are those of an address (i.e. the topological location of an
> interface to the network), then fine, use an address. If not, don't.
>
> If the system for mapping from one namespace to another has problems,
> we ought to fix it, not say "oh, we'll just stop using it".
>
> Don't try and make everything into a nail because the hammer is the
> most reliable tool you have.

That applies equally to DNS and IP.  Just because IP is not ideal for
some purpose does not mean that DNS is the right tool for the job, or
that it's appropriate or even feasible to "fix" it for that job. 
And based on consideration of various factors, I'm firmly convinced that
endpoint identifers should look like IP addresses instead of DNS names.



From owner-ietf@ietf.org  Tue Apr  1 11:46:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28415;
	Tue, 1 Apr 2003 11:46:48 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190P12-00054e-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 11:53:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190P0Q-0004zr-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 11:53:02 -0500
Received: from yxa.extundo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27362
	for <ietf@ietf.org>; Tue, 1 Apr 2003 11:34:36 -0500 (EST)
Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.12.9/8.12.9) with ESMTP id h31GaxXK005713
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK);
	Tue, 1 Apr 2003 18:37:01 +0200
To: ietf@ietf.org
Cc: Rick McGowan <rick@unicode.org>
Subject: draft-rmcgowan-unicode-procs-02.txt
X-Payment: hashcash 1.2 0:030401:ietf@ietf.org:11daeb8cf5039635
X-Hashcash: 0:030401:ietf@ietf.org:11daeb8cf5039635
X-Payment: hashcash 1.2 0:030401:rick@unicode.org:60726b12bee05123
X-Hashcash: 0:030401:rick@unicode.org:60726b12bee05123
From: Simon Josefsson <jas@extundo.com>
Date: Tue, 01 Apr 2003 18:36:59 +0200
Message-ID: <ilu65pyuqc4.fsf@latte.josefsson.org>
User-Agent: Gnus/5.090017 (Oort Gnus v0.17) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=-6.3 required=5.0
	tests=USER_AGENT_GNUS_UA
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-ietf@ietf.org
Precedence: bulk

One topic that is important to some people appears to be missing from
this document: what licensing scheme the Unicode Consortium uses for
their standards.  It would be useful to include a discussion on the
differences between how the Unicode standard and IETF documents can be
(re-)distributed and used by implementors.

Specifically: Some parts of the Unicode standards cannot be
redistributed, which has consequences for some implementors that want
to support Unicode with CJK in IETF protocols.




From owner-ietf@ietf.org  Tue Apr  1 13:40:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07441;
	Tue, 1 Apr 2003 13:40:25 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190QkS-0005hK-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 13:44:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190QiS-0005Wz-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 13:42:36 -0500
Received: from tndh.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06658
	for <ietf@ietf.org>; Tue, 1 Apr 2003 13:25:51 -0500 (EST)
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S23B24> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 01 Apr 2003 10:28:16 -0800
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dave Crocker'" <dhc2@dcrocker.net>
Cc: <ietf@ietf.org>
Subject: RE: Thinking differently about names and addresses
Date: Tue, 1 Apr 2003 10:28:14 -0800
Message-ID: <087201c2f87c$778a4a20$ee1a4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <5854435704.20030401082235@brandenburg.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA07441

Dave Crocker wrote:
> TH>  The discussions on the multi6 mail list
> TH> have basically been about how the routing community believes the 
> TH> address is the topology locator, while your & Dave's 
> comments show 
> TH> the app community believes it is an identifier.
> 
> By definition, an address is a topology indicator.  Always.
> 
> The point that I was trying to make is that the uniqueness of 
> an address's bits permits its use as an uninterrupted label, 
> ie, a name. (Up a few layers, this is the basis for including 
> URL's in the set of
> URI's.)

And my point is that when you take that uninterpreted label out of its
context of uniqueness, it can't be used as a meaningful name. The real
problem that the app community has with 1918 & SL is that they validly
want a single namespace, but they also want to insist on using addresses
as names. The disjoint nature of the deployed address space precludes
both of those actions at the same time. 

> 
> So this is not about competing definitions of the bits, but 
> different USES of them.  IP needs to interpret those bits.  
> Hence, it MUST handle them as topological indicators.  Apps 
> that use IP addresses use them as simple labels.

Which I would call competing definitions, but that is not the point.
What the app community is indirectly saying is that we use topology
locators as names, we have to have a single rooted name space, therefore
the locators have to point at a unified topology. The reality of
deployed networks is that there will be routing filters, therefore we
have a disjoint views of the address space. In addition, the app
community expects their use of the topology locator as a name to be
stable over a long period, while the routing community wants the
flexibility to change the locator as needed for significant* topology
changes. These 'USES' are clearly at odds.

* I define significant in this context as disruption of an ISP/customer
interconnect, that would cause a prefix to become unusable. These are
relatively infrequent in relation to overall topology changes, but more
frequent than current procedures for DNS changes.

> 
> 
> TH>  Where the two communities agree
> TH> is that the DNS as currently deployed and operated is not 
> up to the 
> TH> task of handling the identifier role. My point is that 
> this is due 
> TH> more to implementation & operation than architecture.
> 
> Responding to this point takes us into the world of 
> solutions. I suspect we will all find this topic more 
> productive (and probably more pleasant) when we move into that mode.
> 
> 
> TH> Also I believe the multi6
> TH> discussion about creating a new identifier, to get the 
> app community 
> TH> to stop camping on the topology locator, will end up creating a 
> TH> distributed database infrastructure almost identical to DNS. We 
> TH> don't need two of those, so we should fix DNS.
> 
> That was my own view roughly 10 years ago, when Noel Chiappa 
> was pushing for use of an end-point identifier, as part of 
> what is now IPv6.
> 
> At this stage, I would want to hear the requirements (or 
> probably better, the desired usage scenarios) before being 
> certain that a modified DNS is the answer.

We agree that we need to understand the requirements before starting on
a design.

> 
> 
> TH> I disagree with the perspective that subnetting or CIDR 
> changed the 
> TH> character of the address.
> 
> Before:  IP addresses contained no topological information.
> 
> After:   IP addresses contained quite a bit of topological information
> AND that information was (is) used quite heavily.
> 
> A change that permits a routing table to be reduced massively 
> necessarily involves changing the character of something.
> 

You cut off the significant part. Since at least RFC 791, IP addresses
have always indicated the topology significance of local or remote
networks. What subnetting did was add structure as the definition of
'local' was reduced in geographic scope. What CIDR did was add structure
to the network identifier part to reduce the effort of finding the
proper next hop as the number of remote networks grew. Neither of those
acts changed the architectural nature of the address, just the bit
positions.  

Clearly the app community has taken advantage of using the 'where'
identifier as a 'what' identifier. This worked fine until ~1987 when
people started putting in routing filters which fragmented views of the
'where' space. The fragmented views became more widespread as sites that
had squatted on unallocated space interconnected without injecting
global routes. With 1597/1918, the fragmentation was formalized and the
market demand for squatting disappeared. What the anti-SL camp is
arguing is that if we only take one step back, we will rid ourselves of
the problem of fragmented views. What they miss is that reintroduces the
market demand for squatting, because we offer no alternative, as well as
the point that it doesn't really remove the original issue of filtering
causing differing views. 

We really need a big-picture perspective here before any knee-jerk
reactions. I have one alternative for how to preallocate space to deal
with the squatting issue, but even that doesn't solve the disconnect
between the app community view of a unified 'where' space to be used as
'whats', when the network managers will continue to install route
filters and fragment the 'where' space. 

Tony 




From owner-ietf@ietf.org  Tue Apr  1 14:26:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09176;
	Tue, 1 Apr 2003 14:26:37 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190RZi-0003hr-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 14:37:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190RXh-0003Wq-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 14:35:33 -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 OAA08699
	for <ietf@ietf.org>; Tue, 1 Apr 2003 14:18:44 -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 h31JK6A18435;
        Tue, 1 Apr 2003 14:20:06 -0500 (EST)
Date: Tue, 1 Apr 2003 14:20:06 -0500
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, dhc2@dcrocker.net, ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
Message-Id: <20030401142006.1dbdb6f3.moore@cs.utk.edu>
In-Reply-To: <087201c2f87c$778a4a20$ee1a4104@eagleswings>
References: <5854435704.20030401082235@brandenburg.com>
	<087201c2f87c$778a4a20$ee1a4104@eagleswings>
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

> And my point is that when you take that uninterpreted label out of its
> context of uniqueness, it can't be used as a meaningful name.

which is why addresses need to be unique.

> The real problem that the app community has with 1918 & SL is that
> they validly want a single namespace, but they also want to insist on
> using addresses as names. 

not exactly.  there are valid cases for apps using addresses even when
names exist.  sometimes you really do want to talk to a host that is at
a particular network location.  

as for 'apps insist on using addresses as names' - this is because the
architecture doesn't provide names that are good enough to use as
endpoint identifiers for all or even most cases.  you might think this
is unfortunate, and I might agree, but it doesn't follow that we should
force all apps to use DNS.  and fixing the architecture to have a
reliable endpoint identifier is a pipe dream.  nobody has demonstrated
how to make it workable.

also re: 'using addresses as names' -  this is a bogus distinction,
addresses *are* names to a large degree.  the prefix of an address is an
arbitrary bit pattern (i.e. a name), the suffix is an arbitrary bit
pattern. only the bits in the middle have anything to do with topology. 
maybe they're closer to names of locations than to names of hosts, but
they're still names.

> What the app community is indirectly saying is that we use topology
> locators as names, we have to have a single rooted name space,
> therefore the locators have to point at a unified topology. 

at least in the current IP architecture, and we're nowhere close to
having a workable new architecture that separates locators from names.

> The reality of deployed networks is that there will be routing
> filters, therefore we have a disjoint views of the address space. In
> addition, the app community expects their use of the topology locator
> as a name to be stable over a long period,

not just the app community.  TCP expects this; it cannot recover from
address changes. or does the routing community think that it's okay to
interrupt TCP connections at a whim?

> while the routing community
> wants the flexibility to change the locator as needed for significant*
> topology changes. These 'USES' are clearly at odds.

yes, there are competing concerns.  this calls for a compromise about
how stable addresses need to be, not for having infinitely stable
addresses nor for having addresses change at a whim. 

> > At this stage, I would want to hear the requirements (or 
> > probably better, the desired usage scenarios) before being 
> > certain that a modified DNS is the answer.
> 
> We agree that we need to understand the requirements before starting
> on a design.

the new namespace:

a) must to work underneath transport and other protocols, so that
those protocols' associations can survive address changes.
b) must provide quick, secure, reliable indirection
c) must provide for timely update and/or the ability to recover from
stale mapping information quickly and transparently to the application
d) must have appropriate granularity/precision - generally that of
a host/port, so that connections from multiple sources to the same
endpoint identifier reach the same process 
e) requirement c notwithstanding, there's some need for ability to do
redirects at connection setup time and possibly later, to support
process mobility and/or fanout within server farms
f) must have global scope so that referrals work

> Clearly the app community has taken advantage of using the 'where'
> identifier as a 'what' identifier. This worked fine until ~1987 when
> people started putting in routing filters which fragmented views of
> the'where' space. 

no, it still works fine in a global address space.  you are confusing 
address scope with address reachability.  apps aren't expected to be
able to reach hosts when there are explicit filters in place, so the
fact that those filters break apps is considered a feature.  however
apps are expected to accomodate private addresses, and the fact that
many apps cannot reasonably do this is considered a bug in the app.

> What the
> anti-SL camp is arguing is that if we only take one step back, we will
> rid ourselves of the problem of fragmented views.

what the consensus is arguing is that private addresses were a mistake.

> What they miss is
> that reintroduces the market demand for squatting, because we offer no
> alternative,

there is no demand for squatting until addresses are scarce.  v6
addresses are not scarce.

> We really need a big-picture perspective here before any knee-jerk
> reactions. I have one alternative for how to preallocate space to deal
> with the squatting issue, but even that doesn't solve the disconnect
> between the app community view of a unified 'where' space to be used
> as'whats', when the network managers will continue to install route
> filters and fragment the 'where' space. 

the route filters do not fragment the where space, so this is not a
problem.

Keith



From owner-ietf@ietf.org  Tue Apr  1 14:30:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09466;
	Tue, 1 Apr 2003 14:30:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190ReZ-00042m-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 14:42:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190Rds-0003yr-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 14:41:56 -0500
Received: from boreas.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09125
	for <ietf@ietf.org>; Tue, 1 Apr 2003 14:25:16 -0500 (EST)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h31JRYQ07127;
	Tue, 1 Apr 2003 11:27:34 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200304011927.h31JRYQ07127@boreas.isi.edu>
Subject: Re: Thinking differently
In-Reply-To: <243461298.1049121472@p3.JCK.COM> from John C Klensin at "Mar 31, 3 02:37:52 pm"
To: john@jck.com (John C Klensin)
Date: Tue, 1 Apr 2003 11:27:34 -0800 (PST)
Cc: bmanning@ISI.EDU, mrw@windriver.com, alh-ietf@tndh.net, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
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

% 
% 
% --On Monday, 31 March, 2003 09:01 -0800 Bill Manning 
% <bmanning@ISI.EDU> wrote:
% 
% > 	Is may be worth noting that RIRs have -NEVER- made
% > presumptions 	on routability of the delegations they make.
% 
% I believe that, although I remember some arguments within ARIN 
% back when I was on the AC about whether it was legitimate or 
% rational to make allocations that were believed to be 
% unroutable.   But I've gotten several private notes that lead me 
% to believe that a lot of the community doesn't believe this or, 
% more specifically, believes that everyone will fall into line 
% and route any delegation that an RIR makes directly and, hence, 
% that any RIR allocation will, de facto, become routable.
% 
%      john

	Mass Delusion is just that. Witness the 69/8 debacle.
	presumptions of routability are in the eye of the 
	router configuration.


--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).



From owner-ietf@ietf.org  Tue Apr  1 14:38:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09939;
	Tue, 1 Apr 2003 14:37:59 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190RkO-0005CV-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 14:48:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190Rjq-00053W-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 14:48:07 -0500
Received: from boreas.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09610
	for <ietf@ietf.org>; Tue, 1 Apr 2003 14:31:26 -0500 (EST)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h31JXk214322;
	Tue, 1 Apr 2003 11:33:46 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200304011933.h31JXk214322@boreas.isi.edu>
Subject: Re: Thinking differently about the site local problem (was:   RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))
In-Reply-To: <004701c2f7d7$6ec46830$210d640a@unfix.org> from Jeroen Massar at "Apr 1, 3 00:46:55 am"
To: jeroen@unfix.org (Jeroen Massar)
Date: Tue, 1 Apr 2003 11:33:46 -0800 (PST)
Cc: alh-ietf@tndh.net, mrw@windriver.com, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
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

% > > Let's assume that there is a FooBar server in SiteA.  If 
% > > another node in SiteA (NodeA) is communicating via a 
% > > multi-party application to a node in SiteB (NodeB), and wants 
% > > to refer NodeB to the FooBar server in SiteA, what does it do?
% > 
% > Send a name.
% 
% Not all addresses are published in DNS.
% DNS isn't a requirement for IP either.
% 
% Greets,
%  Jeroen

	Quoth Steve... "There are no urgent DNS problems"

	Are the apps for which IPv6 is enabled that -can not-
	use address literals?  If so, then Steve is wrong and 
	the DNS has become critical infrastructure to the working
	of the Internet.  Otherwise, we should trapese down the
	path of separation of topology locator from stack identifier.

	and then revisit the DNS to see if its best used as a lookup
	service between these two things... :)


--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).



From owner-ietf@ietf.org  Tue Apr  1 14:54:46 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10724;
	Tue, 1 Apr 2003 14:54:46 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190S15-0006pl-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 15:05:55 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190Qfa-0005MA-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 13:39:38 -0500
Received: from ginger.lcs.mit.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06406
	for <ietf@ietf.org>; Tue, 1 Apr 2003 13:22:56 -0500 (EST)
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h31IPMtU004997;
	Tue, 1 Apr 2003 13:25:23 -0500
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h31IPMrK004994;
	Tue, 1 Apr 2003 13:25:22 -0500
Date: Tue, 1 Apr 2003 13:25:22 -0500
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200304011825.h31IPMrK004994@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: RE: Thinking differently about names and addresses
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: "Tony Hain" <alh-ietf@tndh.net>

    > your general perspective highlights the problem at hand. ..
    > the routing community believes the address is the topology locator,
    > while your & Dave's comments show the app community believes it is an
    > identifier.

To paraphrase Clint Eastwood (in 'Unforgiven'), "Belief's got nothing to do
with it".

The address field is absolutely required in order to get the packets to where
they are going. Therefore, it has to contain information that is organized in
such a way as to make the routing work.

If the characteristics of that information are such that it's not what the
application community want, they really don't have any other choice but to
find something else.

(I shouldn't need to point out that unless the routing works, the packets
won't get there at all, and if the packets won't get there at all, all other
debates are moot.)


    > I believe the multi6 discussion about creating a new identifier, to get
    > the app community to stop camping on the topology locator, will end up
    > creating a distributed database infrastructure almost identical to DNS.
    > We don't need two of those, so we should fix DNS.

This point was bounced around in the NSRG fairly extensively. I used to
believe as you did, that we could use the DNS as a namespace for naming
end-end entities. I got a lot of pushback on that from knowledgeable parties,
which I am sure they will be happy to rehearse (I'll leave it to them, as they
can do a better job of it); I have no religion about the answer.

I will also note that the DNS does "name" things other than end-end entities;
e.g. some individual names (for popular services) get translated into the
addresses of many different end-end entities.


    > I disagree with the perspective that subnetting or CIDR changed the
    > character of the address.

Absolutely - not at this level. It only had to do with how it was organized
to make the routing work (see above).

	Noel





From owner-ietf@ietf.org  Tue Apr  1 14:56:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10905;
	Tue, 1 Apr 2003 14:56:52 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190S4A-00073d-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 15:09:06 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190S1j-0006rH-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 15:06:35 -0500
Received: from bartok.sidn.nl (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10566
	for <ietf@ietf.org>; Tue, 1 Apr 2003 14:49:55 -0500 (EST)
Received: from bartok.sidn.nl (localhost.sidn.nl [127.0.0.1])
	by bartok.sidn.nl (8.12.9/8.12.9) with ESMTP id h31JqKZ8011965;
	Tue, 1 Apr 2003 21:52:21 +0200 (CEST)
	(envelope-from jaap@bartok.sidn.nl)
Message-Id: <200304011952.h31JqKZ8011965@bartok.sidn.nl>
To: Bill Manning <bmanning@ISI.EDU>
cc: ietf@ietf.org
Subject: Re: Thinking differently 
In-reply-to: Your message of Tue, 01 Apr 2003 11:27:34 -0800.
             <200304011927.h31JRYQ07127@boreas.isi.edu> 
Date: Tue, 01 Apr 2003 21:52:20 +0200
From: Jaap Akkerhuis <jaap@sidn.nl>
Sender: owner-ietf@ietf.org
Precedence: bulk


    
    	Mass Delusion is just that. Witness the 69/8 debacle.
    
During this discussion I've seen references to the "69/8 debacle".
Can anybody explain what the debacle is/was? Is this a magic phrase
for real insiders? Is is something that happened only on a local
net? If not, why don't you explain to the rest of the world? What
IS the argument hinted to with mentioning the "69/8 debacle".

	jaap



From owner-ietf@ietf.org  Tue Apr  1 15:05:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11437;
	Tue, 1 Apr 2003 15:05:25 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190SAV-0000pd-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 15:15:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190SAG-0000kE-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 15:15:24 -0500
Received: from boreas.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11042
	for <ietf@ietf.org>; Tue, 1 Apr 2003 14:58:44 -0500 (EST)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h31K13o15242;
	Tue, 1 Apr 2003 12:01:03 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200304012001.h31K13o15242@boreas.isi.edu>
Subject: Re: Thinking differently
In-Reply-To: <200304011952.h31JqKZ8011965@bartok.sidn.nl> from Jaap Akkerhuis at "Apr 1, 3 09:52:20 pm"
To: jaap@sidn.nl (Jaap Akkerhuis)
Date: Tue, 1 Apr 2003 12:01:03 -0800 (PST)
Cc: bmanning@ISI.EDU, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
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

%     	Mass Delusion is just that. Witness the 69/8 debacle.
%     
% During this discussion I've seen references to the "69/8 debacle".
% Can anybody explain what the debacle is/was? Is this a magic phrase
% for real insiders? Is is something that happened only on a local
% net? If not, why don't you explain to the rest of the world? What
% IS the argument hinted to with mentioning the "69/8 debacle".
% 
% 	jaap


	So sorry. Its an ARIN "insider" story.
	The IANA recently delegated 69.0.0.0/8 to ARIN.
	ARIN started subdelegations to its members from this space.
	A number of ISPs, some of whom are recognized as significant
	transit providers, had this address space filtered, e.g.
	drop all packets in this prefix range.  ARINs members 
	fussed and asked ARIN for routable space.  ARIN reiterated
	that the address blocks they delegate have no inherent
	routability.  Members continued to fuss and argue that
	things like major search engines and TLD/root nameservers
	be periodically renumbered into "new" ranges to encourage
	ISPs to adjust their filters. 

	This is not the first time, nor will it be the last that
	ISPs are unwilling to do for themselves. Unfortunately, the
	RIRs can not enforce routablity, -UNLESS- every ISP 
	of their own freewill and volition, transfer all circuits,
	routers and other IP transmission infrastructure to the
	RIRs, thus giving the RIRs total control of both the
	addressing and transmission of all IP datagrams.


--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).



From owner-ietf@ietf.org  Tue Apr  1 15:13:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12514;
	Tue, 1 Apr 2003 15:13:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190SKF-00063f-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 15:25:43 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190SGJ-0004SH-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 15:21:39 -0500
Received: from stl-smtpout-01.boeing.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11390
	for <ietf@ietf.org>; Tue, 1 Apr 2003 15:04:58 -0500 (EST)
Received: from stl-av-02.boeing.com ([192.76.190.7])
	by stl-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id OAA25603;
	Tue, 1 Apr 2003 14:07:21 -0600 (CST)
Received: from stl-hub-01.boeing.com (localhost [127.0.0.1])
	by stl-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id OAA02674;
	Tue, 1 Apr 2003 14:07:21 -0600 (CST)
Received: from XCH-NWBH-01.nw.nos.boeing.com (xch-nwbh-01.nw.nos.boeing.com [192.33.62.231])
	by stl-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id h31K7K622878;
	Tue, 1 Apr 2003 14:07:20 -0600 (CST)
Received: from XCH-NW-09.nw.nos.boeing.com ([192.42.226.84]) by XCH-NWBH-01.nw.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 1 Apr 2003 12:07:12 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6334.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Thinking differently about names and addresses
Date: Tue, 1 Apr 2003 12:07:12 -0800
Message-ID: <5B58696DB20B9140AD20E0685C573A641908EC@XCH-NW-09.nw.nos.boeing.com>
Thread-Topic: Thinking differently about names and addresses
Thread-Index: AcL4iRfHI/NIm0wQQyCNtPE5KhmuGwAAIvrA
From: "Fleischman, Eric" <eric.w.fleischman@boeing.com>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, <ietf@ietf.org>
X-OriginalArrivalTime: 01 Apr 2003 20:07:12.0891 (UTC) FILETIME=[48B6CCB0:01C2F88A]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA12514

Egads. This list is still talking about the Identity Problem (i.e., that IP addresses are semantically overloaded in that they simultaneously indicate (network interface) routing topology and (node) identity). I just can't believe how we can continually talk about this problem and then not embrace solutions to it such as Bob Moskowitz's HIP (Host Identity Payload). 

All this reminds me of the famous Mark Twain quote where he said "Everybody continually talks about the weather but nobody does anything about it!!"

-----Original Message-----
From: J. Noel Chiappa [mailto:jnc@ginger.lcs.mit.edu]
Sent: Tuesday, April 01, 2003 10:25 AM
To: ietf@ietf.org
Cc: jnc@ginger.lcs.mit.edu
Subject: RE: Thinking differently about names and addresses


    > From: "Tony Hain" <alh-ietf@tndh.net>

    > your general perspective highlights the problem at hand. ..
    > the routing community believes the address is the topology locator,
    > while your & Dave's comments show the app community believes it is an
    > identifier.

To paraphrase Clint Eastwood (in 'Unforgiven'), "Belief's got nothing to do
with it".

The address field is absolutely required in order to get the packets to where
they are going. Therefore, it has to contain information that is organized in
such a way as to make the routing work.

If the characteristics of that information are such that it's not what the
application community want, they really don't have any other choice but to
find something else.

(I shouldn't need to point out that unless the routing works, the packets
won't get there at all, and if the packets won't get there at all, all other
debates are moot.)


    > I believe the multi6 discussion about creating a new identifier, to get
    > the app community to stop camping on the topology locator, will end up
    > creating a distributed database infrastructure almost identical to DNS.
    > We don't need two of those, so we should fix DNS.

This point was bounced around in the NSRG fairly extensively. I used to
believe as you did, that we could use the DNS as a namespace for naming
end-end entities. I got a lot of pushback on that from knowledgeable parties,
which I am sure they will be happy to rehearse (I'll leave it to them, as they
can do a better job of it); I have no religion about the answer.

I will also note that the DNS does "name" things other than end-end entities;
e.g. some individual names (for popular services) get translated into the
addresses of many different end-end entities.


    > I disagree with the perspective that subnetting or CIDR changed the
    > character of the address.

Absolutely - not at this level. It only had to do with how it was organized
to make the routing work (see above).

	Noel






From owner-ietf@ietf.org  Tue Apr  1 15:34:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13825;
	Tue, 1 Apr 2003 15:34:21 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190SdW-0002A0-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 15:45:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190SdE-000269-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 15:45:20 -0500
Received: from psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13602
	for <ietf@ietf.org>; Tue, 1 Apr 2003 15:28:39 -0500 (EST)
Received: from localhost ([127.0.0.1] helo=roam.psg.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 190SPT-000Ay1-00; Tue, 01 Apr 2003 12:31:07 -0800
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.12)
	id 190SPS-000AsD-00; Tue, 01 Apr 2003 12:31:06 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 1 Apr 2003 12:31:06 -0800
To: Jaap Akkerhuis <jaap@sidn.nl>
Cc: ietf@ietf.org
Subject: Re: Thinking differently 
References: <200304011927.h31JRYQ07127@boreas.isi.edu>
	<200304011952.h31JqKZ8011965@bartok.sidn.nl>
Message-Id: <E190SPS-000AsD-00@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> During this discussion I've seen references to the "69/8 debacle".
> Can anybody explain what the debacle is/was? Is this a magic phrase
> for real insiders? Is is something that happened only on a local
> net? If not, why don't you explain to the rest of the world? What
> IS the argument hinted to with mentioning the "69/8 debacle".

idiot isps who configured route filters but did not bother to maintain
them.  darwin at work.  the subject is uninteresting, as the study
of stupidity is an exceedingly target-rich environment.

randy




From owner-ietf@ietf.org  Tue Apr  1 15:55:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14713;
	Tue, 1 Apr 2003 15:55:58 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190Swt-0004EK-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 16:05:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190Sw7-00049b-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 16:04:51 -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 PAA14499
	for <ietf@ietf.org>; Tue, 1 Apr 2003 15:48:12 -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 h31Ko8A18526;
        Tue, 1 Apr 2003 15:50:08 -0500 (EST)
Date: Tue, 1 Apr 2003 15:50:08 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "Fleischman, Eric" <eric.w.fleischman@boeing.com>
Cc: moore@cs.utk.edu, jnc@ginger.lcs.mit.edu, ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
Message-Id: <20030401155008.2ffe0fcc.moore@cs.utk.edu>
In-Reply-To: <5B58696DB20B9140AD20E0685C573A641908EC@XCH-NW-09.nw.nos.boeing.com>
References: <5B58696DB20B9140AD20E0685C573A641908EC@XCH-NW-09.nw.nos.boeing.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

> Egads. This list is still talking about the Identity Problem (i.e.,
> that IP addresses are semantically overloaded in that they
> simultaneously indicate (network interface) routing topology and
> (node) identity). I just can't believe how we can continually talk
> about this problem and then not embrace solutions to it such as Bob
> Moskowitz's HIP (Host Identity Payload). 

HIP only solves part of the problem.  It lets you use something besides
an address as a host identity, but it doesn't provide any way of mapping
between that identity and an address where you can reach the host.

Keith



From owner-ietf@ietf.org  Tue Apr  1 16:17:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15550;
	Tue, 1 Apr 2003 16:17:22 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190TJn-0006IS-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 16:29:19 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190TDW-0005uq-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 16:22:50 -0500
Received: from edison.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15123
	for <ietf@ietf.org>; Tue, 1 Apr 2003 16:06:10 -0500 (EST)
Received: from cisco.com (dhcp-171-71-194-128.cisco.com [171.71.194.128]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id NAA14007; Tue, 1 Apr 2003 13:08:26 -0800 (PST)
Message-ID: <3E89FFCA.9010802@cisco.com>
Date: Tue, 01 Apr 2003 13:08:26 -0800
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: "Fleischman, Eric" <eric.w.fleischman@boeing.com>, jnc@ginger.lcs.mit.edu,
        ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
References: <5B58696DB20B9140AD20E0685C573A641908EC@XCH-NW-09.nw.nos.boeing.com> <20030401155008.2ffe0fcc.moore@cs.utk.edu>
In-Reply-To: <20030401155008.2ffe0fcc.moore@cs.utk.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:
> HIP only solves part of the problem.  It lets you use something besides
> an address as a host identity, but it doesn't provide any way of mapping
> between that identity and an address where you can reach the host.

That's not entirely true.  It doesn't give you a very scalable way to do 
a reverse lookup, but forward lookups are quite possible with DNS.




From owner-ietf@ietf.org  Tue Apr  1 16:33:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16124;
	Tue, 1 Apr 2003 16:33:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190TYq-0007n6-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 16:44:52 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190TV8-0007Xk-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 16:41:02 -0500
Received: from ginger.lcs.mit.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15796
	for <ietf@ietf.org>; Tue, 1 Apr 2003 16:24:22 -0500 (EST)
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h31LQmtU006089;
	Tue, 1 Apr 2003 16:26:48 -0500
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h31LQlPW006088;
	Tue, 1 Apr 2003 16:26:47 -0500
Date: Tue, 1 Apr 2003 16:26:47 -0500
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200304012126.h31LQlPW006088@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Keith Moore <moore@cs.utk.edu>

    > HIP only solves part of the problem ... it doesn't provide any way of
    > mapping between that identity and an address where you can reach the
    > host.

A system doesn't have to provide mechanisms to look up mappings from
<any-name> to <any-other-name> to be useful; just because I can't (in general)
look up the mapping from an Ethernet address to an IP address doesn't mean
there's a fatal flaw in IPv4.

A directorized mapping need only exist *when you need to look up that mapping
for some good reason*. If you construct the protocol interactions such that
you don't *need* to be able to look up the "identity->address" mapping (which
is what HIP does - in general, by providing the identity->address mapping
used in any given transaction as part of the initiation thereof), there's no
problem.

Now, maybe what you meant to say is "there are cases A, B and C in the use of
HIP that I have identified where you need to be able to look up that mapping,
having only the identity in hand", that would be something to examine.

But to merely say "the system doesn't provide all possible mappings" is, as
we can see from my inital example above, not really a useful critique.

	Noel



From owner-ietf@ietf.org  Tue Apr  1 17:04:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17654;
	Tue, 1 Apr 2003 17:04:17 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190Tyl-0001zN-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 17:11:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190TyU-0001uc-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 17:11:22 -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 QAA17116
	for <ietf@ietf.org>; Tue, 1 Apr 2003 16:54:42 -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 h31LuvA18606;
        Tue, 1 Apr 2003 16:56:57 -0500 (EST)
Date: Tue, 1 Apr 2003 16:56:57 -0500
From: Keith Moore <moore@cs.utk.edu>
To: Eliot Lear <lear@cisco.com>
Cc: moore@cs.utk.edu, eric.w.fleischman@boeing.com, jnc@ginger.lcs.mit.edu,
        ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
Message-Id: <20030401165657.54150862.moore@cs.utk.edu>
In-Reply-To: <3E89FFCA.9010802@cisco.com>
References: <5B58696DB20B9140AD20E0685C573A641908EC@XCH-NW-09.nw.nos.boeing.com>
	<20030401155008.2ffe0fcc.moore@cs.utk.edu>
	<3E89FFCA.9010802@cisco.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

On Tue, 01 Apr 2003 13:08:26 -0800
Eliot Lear <lear@cisco.com> wrote:

> Keith Moore wrote:
> > HIP only solves part of the problem.  It lets you use something
> > besides an address as a host identity, but it doesn't provide any
> > way of mapping between that identity and an address where you can
> > reach the host.
> 
> That's not entirely true.  It doesn't give you a very scalable way to
> do a reverse lookup, but forward lookups are quite possible with DNS.

nope.  DNS doesn't give you a way to map a HIP identifier into an IP
address.

Keith



From owner-ietf@ietf.org  Tue Apr  1 17:04:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17656;
	Tue, 1 Apr 2003 17:04:18 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190U0h-0002Dt-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 17:13:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190Tzy-00028l-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 17:12:54 -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 QAA17141
	for <ietf@ietf.org>; Tue, 1 Apr 2003 16:56:14 -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 h31LwYA18613;
        Tue, 1 Apr 2003 16:58:34 -0500 (EST)
Date: Tue, 1 Apr 2003 16:58:33 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: Thinking differently about names and addresses
Message-Id: <20030401165833.4cec836f.moore@cs.utk.edu>
In-Reply-To: <200304012126.h31LQlPW006088@ginger.lcs.mit.edu>
References: <200304012126.h31LQlPW006088@ginger.lcs.mit.edu>
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

On Tue, 1 Apr 2003 16:26:47 -0500
"J. Noel Chiappa" <jnc@ginger.lcs.mit.edu> wrote:

>     > From: Keith Moore <moore@cs.utk.edu>
> 
>     > HIP only solves part of the problem ... it doesn't provide any
>     > way of mapping between that identity and an address where you
>     > can reach the host.
> 
> A system doesn't have to provide mechanisms to look up mappings from
> <any-name> to <any-other-name> to be useful; 

agreed.  but it does need to provide such mechanisms in order to provide
useful endpoint identifiers.  without a mechanism to map the endpoint
identifier to an IP address, such identifiers are useless in referrals
between application components.

Keith



From owner-ietf@ietf.org  Tue Apr  1 18:20:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21194;
	Tue, 1 Apr 2003 18:20:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190VBI-0005oa-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 18:28:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190VB6-0005gZ-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 18:28:28 -0500
Received: from ginger.lcs.mit.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20609
	for <ietf@ietf.org>; Tue, 1 Apr 2003 18:11:47 -0500 (EST)
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h31NEDtU006545;
	Tue, 1 Apr 2003 18:14:13 -0500
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h31NED6a006544;
	Tue, 1 Apr 2003 18:14:13 -0500
Date: Tue, 1 Apr 2003 18:14:13 -0500
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200304012314.h31NED6a006544@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Keith Moore <moore@cs.utk.edu>

    > it does need to provide such mechanisms in order to provide useful
    > endpoint identifiers.

I don't think you can make such a blanket statement without some more
analysis. For example:

    > without a mechanism to map the endpoint identifier to an IP address,
    > such identifiers are useless in referrals between application
    > components. 

This is not so. Read again what I said before:

  If you construct the protocol interactions such that you don't *need* to
  be able to look up the "identity->address" mapping (which is what HIP
  does - in general, by providing the identity->address mapping used in any
  given transaction as part of the initiation thereof), there's no problem.

So if I have a system which doesn't provide a directory of mappings from
endpoint identifier to addresses, then in the case you cite, when I refer one
application component to another, all I need to do is either:

- i) provide some other name, one that can be mapped into both identifier and
  address, or
- ii) pass the other party both the identifier and a current, working address
  for that endpoint.


This is not to say I *advocate* a system which doesn't have such a directory
of identifier->address mappings; I don't have any religion one way or the
other on that. Maybe it's a good idea overall, maybe it's not.

I can't think of an example offhand of a complete transaction where I *have*
to have it, though.

	Noel



From owner-ietf@ietf.org  Tue Apr  1 18:30:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21625;
	Tue, 1 Apr 2003 18:30:22 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190VNr-0000MG-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 18:41:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190VNH-0000Gg-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 18:41:03 -0500
Received: from goose.ehsco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21482
	for <ietf@ietf.org>; Tue, 1 Apr 2003 18:24:21 -0500 (EST)
Received: from [207.65.3.26] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 4.0)
  with ESMTP-TLS id 200379; Tue, 01 Apr 2003 17:25:54 -0600
Message-ID: <3E8A2035.2060308@ehsco.com>
Date: Tue, 01 Apr 2003 17:26:45 -0600
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: Bill Manning <bmanning@ISI.EDU>
CC: Margaret Wasserman <mrw@windriver.com>, john@jck.com, alh-ietf@tndh.net,
        ietf@ietf.org
Subject: Re: Thinking differently about the site local problem (was:  RE:
 site local addresses (was Re: Fw: Welcome to the  InterNAT...))
References: <200303311701.h2VH1h615515@boreas.isi.edu>
In-Reply-To: <200303311701.h2VH1h615515@boreas.isi.edu>
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


on 3/31/2003 11:01 AM Bill Manning wrote:
> 	Is may be worth noting that RIRs have -NEVER- made presumptions
> 	on routability of the delegations they make.

Probably more accurate to say that they have never guaranteed routability.

They make all kinds of presumptions about routability. One of the reasons
they claim to refuse (say) private /24 is that it isn't going to be widely
routable. By default, this implies that larger delegations are presumed to
be routable, or else they wouldn't assign them either.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-ietf@ietf.org  Tue Apr  1 19:20:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22908;
	Tue, 1 Apr 2003 19:20:49 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190Vqt-0002tl-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 19:11:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190Vo2-0002hS-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 19:08:42 -0500
Received: from flamingo.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22132
	for <ietf@ietf.org>; Tue, 1 Apr 2003 18:52:00 -0500 (EST)
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by flamingo.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 190Va8-0007OF-00; Tue, 01 Apr 2003 15:54:20 -0800
Date: Tue, 1 Apr 2003 18:49:13 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: Thinking differently about names and addresses
Message-Id: <20030401184913.6879bc7b.moore@cs.utk.edu>
In-Reply-To: <200304012314.h31NED6a006544@ginger.lcs.mit.edu>
References: <200304012314.h31NED6a006544@ginger.lcs.mit.edu>
X-Mailer: Sylpheed version 0.8.10 (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

>     > without a mechanism to map the endpoint identifier to an IP address,
>     > such identifiers are useless in referrals between application
>     > components. 
> 
> This is not so. Read again what I said before:
> 
>   If you construct the protocol interactions such that you don't *need* to
>   be able to look up the "identity->address" mapping (which is what HIP
>   does - in general, by providing the identity->address mapping used in any
>   given transaction as part of the initiation thereof), there's no problem.

that's like saying that if I write my protocols so that I never use referrals,
then there's no problem with the inability to do referrals.

of course, writing my protocols so that I never use referrals drastically
limits what I can do with the network.   for instance, DNS could not exist.
but never mind the lost functionality, we can at least pretend we have a clean
model.

> So if I have a system which doesn't provide a directory of mappings from
> endpoint identifier to addresses, then in the case you cite, when I refer
> one application component to another, all I need to do is either:
> 
> - i) provide some other name, one that can be mapped into both identifier
> and address, or

thus reducing the problem to a different unsolved problem.

> - ii) pass the other party both the identifier and a current, working
> address for that endpoint.

thus requiring me to continue to use IP addresses in referrals.

Keith



From owner-ietf@ietf.org  Tue Apr  1 22:43:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27150;
	Tue, 1 Apr 2003 22:43:57 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190ZFp-0003Di-00
	for ietf-list@ran.ietf.org; Tue, 01 Apr 2003 22:49:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190ZDA-000390-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 22:46:52 -0500
Received: from noxmail.sandelman.ottawa.on.ca (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26913
	for <ietf@ietf.org>; Tue, 1 Apr 2003 22:30:08 -0500 (EST)
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca [192.139.46.20])
	by noxmail.sandelman.ottawa.on.ca (8.11.6/8.11.6) with ESMTP id h323WXc20741
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK)
	for <ietf@ietf.org>; Tue, 1 Apr 2003 22:32:34 -0500 (EST)
Received: from marajade.sandelman.ottawa.on.ca (marajade [127.0.0.1] (may be forged))
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian -4) with ESMTP id h323WWa4012142
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Tue, 1 Apr 2003 22:32:33 -0500
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by marajade.sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-5) with ESMTP id h323WWFv012138
	for <ietf@ietf.org>; Tue, 1 Apr 2003 22:32:32 -0500
Message-Id: <200304020332.h323WWFv012138@marajade.sandelman.ottawa.on.ca>
To: ietf@ietf.org
Subject: Re: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...)) 
In-reply-to: Your message of "Tue, 01 Apr 2003 11:33:46 PST."
             <200304011933.h31JXk214322@boreas.isi.edu> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 01 Apr 2003 22:32:31 -0500
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-ietf@ietf.org
Precedence: bulk

-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Bill" == Bill Manning <bmanning@isi.edu> writes:
    Bill> 	Are the apps for which IPv6 is enabled that -can not-
    Bill> 	use address literals?  If so, then Steve is wrong and 

  yes.
  Both IPv4 and IPv6 web browsers behave differently if you do,
for instance:
    http://192.139.46.2/
vs  http://www.sandelman.ca/

  A different Host: header is sent, and therefore one gets a different 
(virtual) web site. Of course, we have no need of this in IPv6, since
2^64 web sites per LAN is plenty, but the protocol still exists to do it.
  Can we change this in IPv6? Maybe.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBPopZtIqHRg3pndX9AQEc+wQA7lhFyoHXkIMopiYnh295B9R+8fpJxESt
dUGdIlbNUA6QwefQoHMkLo77teXn4cc2CxDI6RaE2t93FRxMOeJQUfgdT022UmQ/
co+cVhkyRXnweJb6DfwGfu3YHK/j+J7ScLw0TQ0FSAPFwGXHRbOmAppVD138hUJG
UXkPMLHDA/s=
=JyhG
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Wed Apr  2 01:36:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01358;
	Wed, 2 Apr 2003 01:36:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190bxE-0001F7-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 01:42:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190bwO-0001D2-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 01:41:44 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01170
	for <ietf@ietf.org>; Wed, 2 Apr 2003 01:24:56 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 0CCAF6223F; Wed,  2 Apr 2003 08:27:19 +0200 (CEST)
Date: Wed, 02 Apr 2003 08:27:19 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Randy Bush <randy@psg.com>, Jaap Akkerhuis <jaap@sidn.nl>
Cc: ietf@ietf.org
Subject: Evolution in action (Re: Thinking differently)
Message-ID: <179730000.1049264839@askvoll.hjemme.alvestrand.no>
In-Reply-To: <E190SPS-000AsD-00@roam.psg.com>
References: <200304011927.h31JRYQ07127@boreas.isi.edu>
 <200304011952.h31JqKZ8011965@bartok.sidn.nl>
 <E190SPS-000AsD-00@roam.psg.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, april 01, 2003 12:31:06 -0800 Randy Bush <randy@psg.com> 
wrote:

>> During this discussion I've seen references to the "69/8 debacle".
>> Can anybody explain what the debacle is/was? Is this a magic phrase
>> for real insiders? Is is something that happened only on a local
>> net? If not, why don't you explain to the rest of the world? What
>> IS the argument hinted to with mentioning the "69/8 debacle".
>
> idiot isps who configured route filters but did not bother to maintain
> them.  darwin at work.  the subject is uninteresting, as the study
> of stupidity is an exceedingly target-rich environment.

for those of us who are endlessly fascinated by watching evolution in 
action - what was the previous usage of 69/8 that led to those filters 
being installed?

(parenthesis: similar things have reportedly happened to people using .info 
for email - there turns out to be a number of MTAs in the world who have 
hardcoded all the non-2-letter TLDs, assuming "there will be no more", and 
routinely toss mail from/to the newer ones. They, too, deserve the pain 
they get; unfortunately they, like the route filterers, don't get all the 
pain they cause.)

                  Harald




From owner-ietf@ietf.org  Wed Apr  2 01:44:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01627;
	Wed, 2 Apr 2003 01:44:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190c8r-00020C-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 01:54:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190c85-0001x8-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 01:53:49 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01470
	for <ietf@ietf.org>; Wed, 2 Apr 2003 01:37:03 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 9905A623D1; Wed,  2 Apr 2003 08:39:30 +0200 (CEST)
Date: Wed, 02 Apr 2003 08:39:30 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Keith Moore <moore@cs.utk.edu>, "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: ietf@ietf.org
Subject: addresses in referrals (Re: Thinking differently about names and
 addresses)
Message-ID: <181660000.1049265570@askvoll.hjemme.alvestrand.no>
In-Reply-To: <20030401184913.6879bc7b.moore@cs.utk.edu>
References: <200304012314.h31NED6a006544@ginger.lcs.mit.edu>
 <20030401184913.6879bc7b.moore@cs.utk.edu>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, april 01, 2003 18:49:13 -0500 Keith Moore <moore@cs.utk.edu> 
wrote:

>> - ii) pass the other party both the identifier and a current, working
>> address for that endpoint.
>
> thus requiring me to continue to use IP addresses in referrals.

actually this is a fairly common tactic; the X.500 directory used to have 
that (binding a PSAP with the distinguished name of a remote MTA), and the 
DNS does it (delivering an A record, often derived from "glue", as 
additional data when sending back an NS record as a referral).

when done with care, the recipient of such a referral can handle all 3 
cases:

- this is an identity I know, and have communication with. Forget the 
address; I don't need it.

- this is an identity I know, where my current communication address 
doesn't work. Contact at the new address, and verify that you've reached 
the right endpoint.

- this is an identity I don't know. Contact at the given address, and 
verify.

I liked HIP the first time I saw it (a long time ago). I'm still waiting to 
see an application that uses it; if it's good enough to be successful at 
all, it should be able to be successful in a small market niche; if it's 
successful in a market niche, it could possibly take over the Internet.

but that first application can be a high hurdle.....

                      Harald




From owner-ietf@ietf.org  Wed Apr  2 01:53:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01901;
	Wed, 2 Apr 2003 01:53:17 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190cIW-0002pw-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 02:04:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190cIJ-0002nt-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 02:04:23 -0500
Received: from netcore.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01797
	for <ietf@ietf.org>; Wed, 2 Apr 2003 01:47:36 -0500 (EST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h326njZ23314;
	Wed, 2 Apr 2003 09:49:45 +0300
Date: Wed, 2 Apr 2003 09:49:45 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Bill Manning <bmanning@ISI.EDU>
cc: Jeroen Massar <jeroen@unfix.org>, <alh-ietf@tndh.net>, <mrw@windriver.com>,
        <ietf@ietf.org>
Subject: Re: Thinking differently about the site local problem (was:   RE:
 site local addresses (was Re: Fw: Welcome to the InterNAT...))
In-Reply-To: <200304011933.h31JXk214322@boreas.isi.edu>
Message-ID: <Pine.LNX.4.44.0304020948100.23191-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 1 Apr 2003, Bill Manning wrote:
> 	Are the apps for which IPv6 is enabled that -can not-
> 	use address literals?

There are a few.

Mostly cauzed by lazy porting, and optimizing at the first stage for the 
masses only (ie., changing the API to use getaddrinfo, but if there are 
some internal address-manually-typed-is-ok checks, those may or may not 
be modified).

> If so, then Steve is wrong and 
> 	the DNS has become critical infrastructure to the working
> 	of the Internet.  Otherwise, we should trapese down the
> 	path of separation of topology locator from stack identifier.
> 
> 	and then revisit the DNS to see if its best used as a lookup
> 	service between these two things... :)



-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From owner-ietf@ietf.org  Wed Apr  2 02:00:02 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02170;
	Wed, 2 Apr 2003 02:00:02 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190cQH-0003Vk-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 02:12:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190cPN-0003TP-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 02:11:41 -0500
Received: from netcore.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02037
	for <ietf@ietf.org>; Wed, 2 Apr 2003 01:54:54 -0500 (EST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h326vEr23387;
	Wed, 2 Apr 2003 09:57:14 +0300
Date: Wed, 2 Apr 2003 09:57:14 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: Randy Bush <randy@psg.com>, Jaap Akkerhuis <jaap@sidn.nl>, <ietf@ietf.org>
Subject: Re: Evolution in action (Re: Thinking differently)
In-Reply-To: <179730000.1049264839@askvoll.hjemme.alvestrand.no>
Message-ID: <Pine.LNX.4.44.0304020955190.23191-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 2 Apr 2003, Harald Tveit Alvestrand wrote:
> --On tirsdag, april 01, 2003 12:31:06 -0800 Randy Bush <randy@psg.com> 
> wrote:
> >> During this discussion I've seen references to the "69/8 debacle".
> >> Can anybody explain what the debacle is/was? Is this a magic phrase
> >> for real insiders? Is is something that happened only on a local
> >> net? If not, why don't you explain to the rest of the world? What
> >> IS the argument hinted to with mentioning the "69/8 debacle".
> >
> > idiot isps who configured route filters but did not bother to maintain
> > them.  darwin at work.  the subject is uninteresting, as the study
> > of stupidity is an exceedingly target-rich environment.
> 
> for those of us who are endlessly fascinated by watching evolution in 
> action - what was the previous usage of 69/8 that led to those filters 
> being installed?

No such use.

Some folks just consider blocking *all* unallocated address ranges a good
idea to try reduce DoS attacks which forge addresses and the like.

An incredibly bad idea if you don't maintain them properly, really..

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings





From owner-ietf@ietf.org  Wed Apr  2 02:50:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29595;
	Wed, 2 Apr 2003 02:50:18 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190d8n-0003f6-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 02:58:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190d6r-0003Xm-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 02:56:37 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29354
	for <ietf@ietf.org>; Wed, 2 Apr 2003 02:39:50 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id C8ACA6223F; Wed,  2 Apr 2003 09:42:17 +0200 (CEST)
Date: Wed, 02 Apr 2003 09:42:17 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Bill Manning <bmanning@ISI.EDU>
Cc: 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: <192240000.1049269337@askvoll.hjemme.alvestrand.no>
In-Reply-To: <200304011933.h31JXk214322@boreas.isi.edu>
References:  <200304011933.h31JXk214322@boreas.isi.edu>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, april 01, 2003 11:33:46 -0800 Bill Manning <bmanning@ISI.EDU> 
wrote:

> 	Are the apps for which IPv6 is enabled that -can not-
> 	use address literals?  If so, then Steve is wrong and
> 	the DNS has become critical infrastructure to the working
> 	of the Internet.

anyone who believes that the DNS is not critical infrastructure for just 
about every single purpose the Internet is used for is either living in a 
fantasy world or has redefined the "Internet" to be something that's 
strictly at layer 3 and below.

there are advantages to being able to keep the layer 3 infrastructure 
running for a while (hours, I think) without referring to the DNS.
But for end-user purposes, the DNS being down equates to the Internet being 
down.

Infrastructure doesn't get much more critical than that.

              Harald



From owner-ietf@ietf.org  Wed Apr  2 06:25:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03733;
	Wed, 2 Apr 2003 06:25:16 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190gSt-0000HN-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 06:31:35 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190gOM-0000DH-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 06:26:54 -0500
Received: from purgatory.unfix.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03418
	for <ietf@ietf.org>; Wed, 2 Apr 2003 06:10:05 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id BB1268F16; Wed,  2 Apr 2003 13:12:29 +0200 (CEST)
Received: from limbo (limbo.unfix.org [10.100.13.33])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 27D4E89B2; Wed,  2 Apr 2003 13:12:23 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Michael Richardson'" <mcr@sandelman.ottawa.on.ca>, <ietf@ietf.org>
Subject: RE: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...)) 
Date: Wed, 2 Apr 2003 13:13:31 +0200
Organization: Unfix
Message-ID: <002901c2f908$e5d1ed30$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <200304020332.h323WWFv012138@marajade.sandelman.ottawa.on.ca>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-Virus-Scanned: by AMaViS @ purgatory.unfix.org
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Michael Richardson wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> 
> 
> >>>>> "Bill" == Bill Manning <bmanning@isi.edu> writes:
>     Bill> 	Are the apps for which IPv6 is enabled that -can not-
>     Bill> 	use address literals?  If so, then Steve is wrong and 
> 
>   yes.
>   Both IPv4 and IPv6 web browsers behave differently if you do,
> for instance:
>     http://192.139.46.2/
> vs  http://www.sandelman.ca/
> 
>   A different Host: header is sent, and therefore one gets a 
> different 
> (virtual) web site.

Configure your server better than :) (eg use _default_ )
HTTP goes by name, not by IP. Also there is a RFC which
says to never use IPv6 IP's in URL's... That's also why
IE in XP doesn't support it. "Host" is now an integral
part of HTTP/1.1 and one can't even do without it anymore.

> Of course, we have no need of this in IPv6, since
> 2^64 web sites per LAN is plenty, but the protocol still 
> exists to do it.
>   Can we change this in IPv6? Maybe.

I don't think many hosters will like configuring 2^64 addresses
on their webservers, even though it is possible.

One neat thing about this is HTTPS though, as there are now enough
addresses for that. But fortunatly there are propositions for
enabling the "Host" header for different SSL sites even while
using the same IP (v4+v6 ofcourse).

Greets,
 Jeroen




From owner-ietf@ietf.org  Wed Apr  2 08:00:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07477;
	Wed, 2 Apr 2003 08:00:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190hzl-0003IL-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 08:09:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190hzf-0003Fb-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 08:09:31 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07366
	for <ietf@ietf.org>; Wed, 2 Apr 2003 07:52:41 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 190hlh-000BgU-00; Wed, 02 Apr 2003 07:55:05 -0500
Date: Wed, 02 Apr 2003 07:55:05 -0500
From: John C Klensin <john-ietf@jck.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Evolution in action (Re: Thinking differently)
Message-ID: <392091738.1049270105@p3.JCK.COM>
In-Reply-To: <179730000.1049264839@askvoll.hjemme.alvestrand.no>
References: <200304011927.h31JRYQ07127@boreas.isi.edu>
 <200304011952.h31JqKZ8011965@bartok.sidn.nl>
 <E190SPS-000AsD-00@roam.psg.com>
 <179730000.1049264839@askvoll.hjemme.alvestrand.no>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Wednesday, 02 April, 2003 08:27 +0200 Harald Tveit 
Alvestrand <harald@alvestrand.no> wrote:

>>...
>> idiot isps who configured route filters but did not bother to
>> maintain them.  darwin at work.  the subject is
>> uninteresting, as the study of stupidity is an exceedingly
>> target-rich environment.
>
> for those of us who are endlessly fascinated by watching
> evolution in action - what was the previous usage of 69/8 that
> led to those filters being installed?
>
> (parenthesis: similar things have reportedly happened to
> people using .info for email - there turns out to be a number
> of MTAs in the world who have hardcoded all the non-2-letter
> TLDs, assuming "there will be no more", and routinely toss
> mail from/to the newer ones. They, too, deserve the pain they
> get; unfortunately they, like the route filterers, don't get
> all the pain they cause.)

See draft-klensin-name-filters-00.txt for a longer explanation 
of this issue and some cases other than mail-tossing.   I'm 
working on a version that fills in the empty sections and 
clarifies anything that I can find that isn't clear;  comments 
and suggestions welcome.

The evolutionary implications of this one are, however, somewhat 
less clear than those of the 69/8 case.  In the 69/8 case, the 
ISPs who did the filtering were ultimately subject to attack by 
their own customers who, presumably, would sooner or later go 
elsewhere (or cause other harm to the ISP) if the problem wasn't 
fixed.  An MTA-operator whom I'm paying to receive and deliver 
my mail is (or should be) subject to roughly the same pressures. 
But, in the TLD case, the victims are mostly those who have 
registered in the new domains and the help desks of registrars 
and unrelated servers, neither of whom have significant leverage 
on the offending ISPs in the non-MTA cases.

It might also be part of a good case for not creating new gTLDs 
except where they are needed for technical reasons (pretty much 
a null set), but please hold any discussion on that subject on 
the whining-at-ICANN list of your choice.  Spending excessive 
time on that one of course leads to another example of evolution 
in action :-(.

    john





From owner-ietf@ietf.org  Wed Apr  2 08:19:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08053;
	Wed, 2 Apr 2003 08:19:01 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190iI8-0004Fw-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 08:28:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190iCe-00042j-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 08:22:56 -0500
Received: from web10903.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA07737
	for <ietf@ietf.org>; Wed, 2 Apr 2003 08:06:05 -0500 (EST)
Message-ID: <20030402130833.67087.qmail@web10903.mail.yahoo.com>
Received: from [12.237.229.250] by web10903.mail.yahoo.com via HTTP; Wed, 02 Apr 2003 05:08:33 PST
Date: Wed, 2 Apr 2003 05:08:33 -0800 (PST)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: RE: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...)) 
To: ietf@ietf.org
In-Reply-To: <002901c2f908$e5d1ed30$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi, Jeroen,

Are you talking about
ftp://ftp.rfc-editor.org/in-notes/rfc2732.txt (PS)? 

My quick read of this RFC is that it says "don't use IPv6
literals without enclosing them in brackets", as in

      host          = hostname | IPv4address | IPv6reference
      ipv6reference = "[" IPv6address "]"

But that's not quite the same thing you said: "never use IPv6
IP's in URL's".

If you're talking about another reference, could you provide it?
A quick RFC search for "IPv6 URL" turned up only this RFC...

Thanks,

Spencer

--- Jeroen Massar <jeroen@unfix.org> wrote:
> Also there is a RFC which
> says to never use IPv6 IP's in URL's... That's also why
> IE in XP doesn't support it. "Host" is now an integral
> part of HTTP/1.1 and one can't even do without it anymore.



From owner-ietf@ietf.org  Wed Apr  2 08:19:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08137;
	Wed, 2 Apr 2003 08:19:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190iIA-0004GT-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 08:28:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190iG5-00047r-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 08:26:29 -0500
Received: from flamingo.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07846
	for <ietf@ietf.org>; Wed, 2 Apr 2003 08:09:39 -0500 (EST)
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by flamingo.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 190i26-0005QH-00; Wed, 02 Apr 2003 05:12:02 -0800
Date: Wed, 2 Apr 2003 08:06:53 -0500
From: Keith Moore <moore@cs.utk.edu>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: moore@cs.utk.edu, jnc@ginger.lcs.mit.edu, ietf@ietf.org
Subject: Re: addresses in referrals (Re: Thinking differently about names
 and addresses)
Message-Id: <20030402080653.29a5a322.moore@cs.utk.edu>
In-Reply-To: <181660000.1049265570@askvoll.hjemme.alvestrand.no>
References: <200304012314.h31NED6a006544@ginger.lcs.mit.edu>
	<20030401184913.6879bc7b.moore@cs.utk.edu>
	<181660000.1049265570@askvoll.hjemme.alvestrand.no>
X-Mailer: Sylpheed version 0.8.10 (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

> >> - ii) pass the other party both the identifier and a current, working
> >> address for that endpoint.
> >
> > thus requiring me to continue to use IP addresses in referrals.
> 
> actually this is a fairly common tactic;

indeed.  or at least, this isn't the first time it's been seen (and my
now-expired I-D describing the best way for apps to deal with NATs mentioned
something similar).  but it doesn't really solve the problems associated with
ambiguous addresses.  it still doesn't provide a reliable way to talk to that
host in the presence of ambiguous addresses.  it only keeps you from
mistakenly talking to the wrong host when two hosts use the same address.






From owner-ietf@ietf.org  Wed Apr  2 08:30:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08580;
	Wed, 2 Apr 2003 08:30:59 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190iOK-0004YX-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 08:35:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190iIf-0004HJ-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 08:29:09 -0500
Received: from avocet.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07889
	for <ietf@ietf.org>; Wed, 2 Apr 2003 08:12:18 -0500 (EST)
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 190i4g-0000IW-00; Wed, 02 Apr 2003 05:14:42 -0800
Date: Wed, 2 Apr 2003 08:09:33 -0500
From: Keith Moore <moore@cs.utk.edu>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
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: <20030402080933.608a4a9d.moore@cs.utk.edu>
In-Reply-To: <192240000.1049269337@askvoll.hjemme.alvestrand.no>
References: <200304011933.h31JXk214322@boreas.isi.edu>
	<192240000.1049269337@askvoll.hjemme.alvestrand.no>
X-Mailer: Sylpheed version 0.8.10 (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

> > 	Are the apps for which IPv6 is enabled that -can not-
> > 	use address literals?  If so, then Steve is wrong and
> > 	the DNS has become critical infrastructure to the working
> > 	of the Internet.
> 
> anyone who believes that the DNS is not critical infrastructure for just 
> about every single purpose the Internet is used for is either living in a 
> fantasy world or has redefined the "Internet" to be something that's 
> strictly at layer 3 and below.

agreed.  but there's a difference between saying that DNS is critical
infrastructure and that it's appropriate to use DNS every time an address is
needed.  DNS is necessary, not sufficient.

Keith



From owner-ietf@ietf.org  Wed Apr  2 10:23:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13475;
	Wed, 2 Apr 2003 10:23:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190kEC-00017i-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 10:32:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190kDi-0000xa-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 10:32:10 -0500
Received: from purgatory.unfix.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13148
	for <ietf@ietf.org>; Wed, 2 Apr 2003 10:15:18 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id 7AD0B8F1E; Wed,  2 Apr 2003 17:17:45 +0200 (CEST)
Received: from limbo (limbo.unfix.org [10.100.13.33])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id BA7AD8F19; Wed,  2 Apr 2003 17:17:39 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Spencer Dawkins'" <spencer_dawkins@yahoo.com>, <ietf@ietf.org>
Cc: "'IPv6 Feedback Alias'" <ipv6-fb@microsoft.com>
Subject: RE: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...)) 
Date: Wed, 2 Apr 2003 17:18:31 +0200
Organization: Unfix
Message-ID: <006a01c2f92b$1f5c7c60$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <20030402130833.67087.qmail@web10903.mail.yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-Virus-Scanned: by AMaViS @ purgatory.unfix.org
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA13475

Spencer Dawkins wrote:

> Hi, Jeroen,
> 
> Are you talking about
> ftp://ftp.rfc-editor.org/in-notes/rfc2732.txt (PS)? 
> 
> My quick read of this RFC is that it says "don't use IPv6
> literals without enclosing them in brackets", as in
> 
>       host          = hostname | IPv4address | IPv6reference
>       ipv6reference = "[" IPv6address "]"
> 
> But that's not quite the same thing you said: "never use IPv6
> IP's in URL's".
> 
> If you're talking about another reference, could you provide it?
> A quick RFC search for "IPv6 URL" turned up only this RFC...

Yes, though I can't seem to google up any references. Except for:
http://www.microsoft.com/windowsxp/pro/techinfo/administration/ipv6/defa
ult.asp

"Q: How can I force IPv6 connections using my Web browser?"
<SNIP>
"For applications other than Internet Explorer: Connect using a literal
IPv6 address. URLs that use the format for literal IPv6 addresses
described in RFC 2732, "Format for Literal IPv6 Addresses in URLs," are
not supported by the version of Internet Explorer provided with Windows
XP."

There was some discussion about this deprecation as the
Techpreviews (Win2k/NT4) did support literal url's.
The XP version and up though won't support it to overcome
one major 'problem': website 'designers' embedding IP's
inside websites to 'speed things up' (go figure).
And there where a number of other reasons for deciding so.
Unfortunatly I can't find the messages which where sent
to a mailinglist about this discussion which also contained
why they decided this. Note that wininet.dll doesn't support
it that's why IE doesn't either...

MS CC'd, they can best explain the rationale behind it.

Greets,
 Jeroen

PS: Is 'google' already an official english verb? :)




From owner-ietf@ietf.org  Wed Apr  2 11:20:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15748;
	Wed, 2 Apr 2003 11:20:34 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190l5M-0004Mh-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 11:27:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190l4t-0004Ju-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 11:27:07 -0500
Received: from boreas.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15235
	for <ietf@ietf.org>; Wed, 2 Apr 2003 11:10:15 -0500 (EST)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h32GCaU25262;
	Wed, 2 Apr 2003 08:12:36 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200304021612.h32GCaU25262@boreas.isi.edu>
Subject: Re: Thinking differently about the site local problem (was:   RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))
In-Reply-To: <20030402080933.608a4a9d.moore@cs.utk.edu> from Keith Moore at "Apr 2, 3 08:09:33 am"
To: moore@cs.utk.edu (Keith Moore)
Date: Wed, 2 Apr 2003 08:12:36 -0800 (PST)
Cc: harald@alvestrand.no, moore@cs.utk.edu, bmanning@ISI.EDU, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
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

% > > 	Are the apps for which IPv6 is enabled that -can not-
% > > 	use address literals?  If so, then Steve is wrong and
% > > 	the DNS has become critical infrastructure to the working
% > > 	of the Internet.
% > 
% > anyone who believes that the DNS is not critical infrastructure for just 
% > about every single purpose the Internet is used for is either living in a 
% > fantasy world or has redefined the "Internet" to be something that's 
% > strictly at layer 3 and below.
% 
% agreed.  but there's a difference between saying that DNS is critical
% infrastructure and that it's appropriate to use DNS every time an address is
% needed.  DNS is necessary, not sufficient.
% 
% Keith

	to pass bits, in the IPv4 world, DNS is -NOT- critical.
	no application forbids address literals and every app
	will allow address literals to be used.  Couple this with
	the fact that IPv4 addresses are within the scope of human
	comprehension, i.e. I can remember 128.9.160.160

	with IPv6, the addresses are long enough to not be human
	friendly, e.g.  2001:0478:6: is about as much as I remember
	on my own...  I must use the DNS or my little yellow sticky note
	to complete the address.  And there are intimations that some
	applications now forbid the use of address literals, even
	if bracketed.  

	Sounds like you both are arguing that the DNS has become
	"embedded" and the applications that use IP are unusable 
	without a working DNS.  This assertion, if true, has ramifcations
	beyond a simple requirement to have the latency of an extra
	lookup against a third party.  (Can you say "Death to e2e!...
	sure you can :)
	

--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).



From owner-ietf@ietf.org  Wed Apr  2 11:27:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15988;
	Wed, 2 Apr 2003 11:27:04 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190lG1-0005Im-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 11:38:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190lFp-0005GE-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 11:38:25 -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 LAA15799
	for <ietf@ietf.org>; Wed, 2 Apr 2003 11:21:33 -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 h32GNuA00300;
        Wed, 2 Apr 2003 11:23:57 -0500 (EST)
Date: Wed, 2 Apr 2003 11:23:56 -0500
From: Keith Moore <moore@cs.utk.edu>
To: Bill Manning <bmanning@ISI.EDU>
Cc: moore@cs.utk.edu, harald@alvestrand.no, 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: <20030402112356.2c156f87.moore@cs.utk.edu>
In-Reply-To: <200304021612.h32GCaU25262@boreas.isi.edu>
References: <20030402080933.608a4a9d.moore@cs.utk.edu>
	<200304021612.h32GCaU25262@boreas.isi.edu>
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

> 	Sounds like you both are arguing that the DNS has become
> 	"embedded" and the applications that use IP are unusable 
> 	without a working DNS.  

as a practical matter, this was true even in IPv4.  yes, you can
often use address literals in either v4 or v6 apps, but this isn't
practical for ordinary users on an ordinary basis.  and in both v4 and
v6, several essential apps (e.g. email, the web) have explicit
dependencies on DNS.  yes you can use address literals in email
addresses and URLs but there is no assurance that an email address or
URL with an address literal is equivalent to the same address or URL
with a domain instead of the address. Both email and the web define
their resources in relation to a DNS name, not relative to a host or
address.

of course it is possible to write apps that do not use DNS, but this is
rarely done.

Keith



From owner-ietf@ietf.org  Wed Apr  2 11:34:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16502;
	Wed, 2 Apr 2003 11:34:23 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190lO4-0005yg-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 11:46:56 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190lGm-0005Ix-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 11:39:24 -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 LAA15833
	for <ietf@ietf.org>; Wed, 2 Apr 2003 11:22:32 -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 h32GOuA00304;
        Wed, 2 Apr 2003 11:24:56 -0500 (EST)
Date: Wed, 2 Apr 2003 11:24:56 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "Jeroen Massar" <jeroen@unfix.org>
Cc: moore@cs.utk.edu, spencer_dawkins@yahoo.com, ietf@ietf.org,
        ipv6-fb@microsoft.com
Subject: Re: Thinking differently about the site local problem (was: RE:
 site local addresses (was Re: Fw: Welcome to the InterNAT...))
Message-Id: <20030402112456.63b5dac6.moore@cs.utk.edu>
In-Reply-To: <006a01c2f92b$1f5c7c60$210d640a@unfix.org>
References: <20030402130833.67087.qmail@web10903.mail.yahoo.com>
	<006a01c2f92b$1f5c7c60$210d640a@unfix.org>
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

> There was some discussion about this deprecation as the
> Techpreviews (Win2k/NT4) did support literal url's.
> The XP version and up though won't support it to overcome
> one major 'problem': website 'designers' embedding IP's
> inside websites to 'speed things up' (go figure).

perfectly reasonable thing to do.  browsers that don't support it are
broken.



From owner-ietf@ietf.org  Wed Apr  2 11:41:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16957;
	Wed, 2 Apr 2003 11:41:18 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190lTc-0006e4-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 11:52:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190lSJ-0006Gj-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 11:51:19 -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 LAA16526
	for <ietf@ietf.org>; Wed, 2 Apr 2003 11:34:27 -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 h32GapA00453;
        Wed, 2 Apr 2003 11:36:51 -0500 (EST)
Date: Wed, 2 Apr 2003 11:36:51 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "Jeroen Massar" <jeroen@unfix.org>
Cc: moore@cs.utk.edu, spencer_dawkins@yahoo.com, ietf@ietf.org,
        ipv6-fb@microsoft.com
Subject: Re: Thinking differently about the site local problem (was: RE:
 site local addresses (was Re: Fw: Welcome to the InterNAT...))
Message-Id: <20030402113651.68eaf277.moore@cs.utk.edu>
In-Reply-To: <00a401c2f935$c1146f40$210d640a@unfix.org>
References: <20030402112456.63b5dac6.moore@cs.utk.edu>
	<00a401c2f935$c1146f40$210d640a@unfix.org>
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

> > > There was some discussion about this deprecation as the
> > > Techpreviews (Win2k/NT4) did support literal url's.
> > > The XP version and up though won't support it to overcome
> > > one major 'problem': website 'designers' embedding IP's
> > > inside websites to 'speed things up' (go figure).
> > 
> > perfectly reasonable thing to do.  browsers that don't support it
> > are broken.
> 
> It's perfectly reasonable to not support RFC2732? or?

it's perfectly reasonable for sites to use address literals in URLs
referenced by their web pages.



From owner-ietf@ietf.org  Wed Apr  2 11:41:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16988;
	Wed, 2 Apr 2003 11:41:26 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190lTb-0006d5-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 11:52:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190lPQ-00066c-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 11:48:20 -0500
Received: from purgatory.unfix.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16360
	for <ietf@ietf.org>; Wed, 2 Apr 2003 11:31:28 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id 67AEC8F2F; Wed,  2 Apr 2003 18:33:54 +0200 (CEST)
Received: from limbo (limbo.unfix.org [10.100.13.33])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 666238F2C; Wed,  2 Apr 2003 18:33:47 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <spencer_dawkins@yahoo.com>, <ietf@ietf.org>, <ipv6-fb@microsoft.com>
Subject: RE: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))
Date: Wed, 2 Apr 2003 18:34:37 +0200
Organization: Unfix
Message-ID: <00a401c2f935$c1146f40$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <20030402112456.63b5dac6.moore@cs.utk.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-Virus-Scanned: by AMaViS @ purgatory.unfix.org
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA16988

Keith Moore [mailto:moore@cs.utk.edu] wrote:

> > There was some discussion about this deprecation as the
> > Techpreviews (Win2k/NT4) did support literal url's.
> > The XP version and up though won't support it to overcome
> > one major 'problem': website 'designers' embedding IP's
> > inside websites to 'speed things up' (go figure).
> 
> perfectly reasonable thing to do.  browsers that don't support it are
> broken.

It's perfectly reasonable to not support RFC2732? or?

Greets,
 Jeroen




From owner-ietf@ietf.org  Wed Apr  2 11:56:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17905;
	Wed, 2 Apr 2003 11:56:18 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190li6-0000CP-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 12:07:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190lhJ-00009N-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 12:06:49 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17639
	for <ietf@ietf.org>; Wed, 2 Apr 2003 11:49:57 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 190lTK-000CNR-00; Wed, 02 Apr 2003 11:52:22 -0500
Date: Wed, 02 Apr 2003 11:52:22 -0500
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@cs.utk.edu>
cc: Bill Manning <bmanning@ISI.EDU>, "ietf@ietf.org" <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: <406328249.1049284342@p3.JCK.COM>
In-Reply-To: <20030402112356.2c156f87.moore@cs.utk.edu>
References: <20030402080933.608a4a9d.moore@cs.utk.edu>
 	<200304021612.h32GCaU25262@boreas.isi.edu>
 <20030402112356.2c156f87.moore@cs.utk.edu>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Wednesday, 02 April, 2003 11:23 -0500 Keith Moore 
<moore@cs.utk.edu> wrote:

>> 	Sounds like you both are arguing that the DNS has become
>> 	"embedded" and the applications that use IP are unusable
>> 	without a working DNS.
>
> as a practical matter, this was true even in IPv4.  yes, you
> can often use address literals in either v4 or v6 apps, but
> this isn't practical for ordinary users on an ordinary basis.
> and in both v4 and v6, several essential apps (e.g. email, the
> web) have explicit dependencies on DNS.  yes you can use
> address literals in email addresses and URLs but there is no
> assurance that an email address or URL with an address literal
> is equivalent to the same address or URL with a domain instead
> of the address. Both email and the web define their resources
> in relation to a DNS name, not relative to a host or address.

At least in the case of email, it is important to be precise 
about this, because we have a clear evolutionary trend:

	(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)
	
	(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)
	
	(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.

Contrast this with RFC 821, which doesn't seem to strongly argue 
that explicit address use is undesirable.


> 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.

     john






From owner-ietf@ietf.org  Wed Apr  2 12:04:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18349;
	Wed, 2 Apr 2003 12:04:08 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190lqn-00010s-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 12:16:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190lqd-0000xt-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 12:16:27 -0500
Received: from purgatory.unfix.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18164
	for <ietf@ietf.org>; Wed, 2 Apr 2003 11:59:35 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id 198388F2F; Wed,  2 Apr 2003 19:01:59 +0200 (CEST)
Received: from limbo (limbo.unfix.org [10.100.13.33])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 7C2B58F1D; Wed,  2 Apr 2003 19:01:53 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Keith Moore'" <moore@cs.utk.edu>, "'Bill Manning'" <bmanning@ISI.EDU>
Cc: <harald@alvestrand.no>, <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...))
Date: Wed, 2 Apr 2003 19:02:39 +0200
Organization: Unfix
Message-ID: <00bc01c2f939$abffb7f0$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <20030402112356.2c156f87.moore@cs.utk.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-Virus-Scanned: by AMaViS @ purgatory.unfix.org
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA18349

Keith Moore wrote:

> > 	Sounds like you both are arguing that the DNS has become
> > 	"embedded" and the applications that use IP are unusable 
> > 	without a working DNS.  
> 
> as a practical matter, this was true even in IPv4.  yes, you can
> often use address literals in either v4 or v6 apps, but this isn't
> practical for ordinary users on an ordinary basis.  and in both v4 and
> v6, several essential apps (e.g. email, the web) have explicit
> dependencies on DNS.  yes you can use address literals in email
> addresses and URLs but there is no assurance that an email address or
> URL with an address literal is equivalent to the same address or URL
> with a domain instead of the address. Both email and the web define
> their resources in relation to a DNS name, not relative to a host or
> address.
> 
> of course it is possible to write apps that do not use DNS, 
> but this is rarely done.

Fortunatly we still all are humans and like names, not numbers :)
We'll let the numbers to computers (big fast math machines)
Our brains are more advanced and just can't cope with numbers any more
;)

Greets,
 Jeroen




From owner-ietf@ietf.org  Wed Apr  2 12:07:36 2003
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, 2 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.



From owner-ietf@ietf.org  Wed Apr  2 12:09:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18781;
	Wed, 2 Apr 2003 12:09:23 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190lw4-0001dm-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 12:22:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190luF-0001CY-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 12:20:11 -0500
Received: from ran.psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18339
	for <ietf@ietf.org>; Wed, 2 Apr 2003 12:03:18 -0500 (EST)
Received: from localhost ([127.0.0.1] helo=ran.psg.com)
	by ran.psg.com with esmtp (Exim 4.12)
	id 190lgE-0003y0-00; Wed, 02 Apr 2003 09:05:43 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 2 Apr 2003 09:05:42 -0800
To: Keith Moore <moore@cs.utk.edu>
Cc: Bill Manning <bmanning@ISI.EDU>, harald@alvestrand.no, ietf@ietf.org
Subject: Re: Thinking differently about the site local problem (was:   RE:
 site local addresses (was Re: Fw: Welcome to the InterNAT...))
References: <20030402080933.608a4a9d.moore@cs.utk.edu>
	<200304021612.h32GCaU25262@boreas.isi.edu>
	<20030402112356.2c156f87.moore@cs.utk.edu>
Message-Id: <E190lgE-0003y0-00@ran.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> of course it is possible to write apps that do not use DNS, but this is
> rarely done.

why not just embed the ip addresses in the data payloads?  death to
nats!  :-)




From owner-ietf@ietf.org  Wed Apr  2 12:12:07 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19123;
	Wed, 2 Apr 2003 12:12:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190lwb-0001ia-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 12:22:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190lvk-0001Vm-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 12:21:44 -0500
Received: from tndh.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18471
	for <ietf@ietf.org>; Wed, 2 Apr 2003 12:04:51 -0500 (EST)
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S23D5C> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 02 Apr 2003 09:07:15 -0800
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Jeroen Massar'" <jeroen@unfix.org>,
        "'Michael Richardson'" <mcr@sandelman.ottawa.on.ca>, <ietf@ietf.org>
Subject: RE: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...)) 
Date: Wed, 2 Apr 2003 09:07:12 -0800
Message-ID: <099501c2f93a$4e62c370$ee1a4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <002901c2f908$e5d1ed30$210d640a@unfix.org>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jeroen Massar wrote:
> ... That's also why IE in XP doesn't support it. 

Making claims that you know nothing about, only exposes your lack of
clue.

Tony





From owner-ietf@ietf.org  Wed Apr  2 12:13:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19320;
	Wed, 2 Apr 2003 12:13:50 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190lzV-0002Dy-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 12:25:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190lyi-0001va-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 12:24:48 -0500
Received: from garlic.amaranth.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18658
	for <ietf@ietf.org>; Wed, 2 Apr 2003 12:07:55 -0500 (EST)
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226])
	(authenticated (0 bits))
	by garlic.amaranth.net (8.11.7/8.11.7) with ESMTP id h32HALo13663
	(using TLSv1/SSLv3 with cipher DES-CBC3-SHA (168 bits) verified NO)
	for <ietf@ietf.org>; Wed, 2 Apr 2003 12:10:22 -0500
Message-Id: <5.2.0.9.2.20030402120246.01b20eb8@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 02 Apr 2003 12:09:15 -0500
To: <ietf@ietf.org>
From: Daniel Senie <dts@senie.com>
Subject: RE: Thinking differently about the site local problem (was:
  RE: site local addresses (was Re: Fw: Welcome to the InterNAT...)) 
In-Reply-To: <006a01c2f92b$1f5c7c60$210d640a@unfix.org>
References: <20030402130833.67087.qmail@web10903.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:18 AM 4/2/2003, Jeroen Massar wrote:
>Spencer Dawkins wrote:
>
> > Hi, Jeroen,
> >
> > Are you talking about
> > ftp://ftp.rfc-editor.org/in-notes/rfc2732.txt (PS)?
> >
> > My quick read of this RFC is that it says "don't use IPv6
> > literals without enclosing them in brackets", as in
> >
> >       host          = hostname | IPv4address | IPv6reference
> >       ipv6reference = "[" IPv6address "]"
> >
> > But that's not quite the same thing you said: "never use IPv6
> > IP's in URL's".
> >
> > If you're talking about another reference, could you provide it?
> > A quick RFC search for "IPv6 URL" turned up only this RFC...
>
>Yes, though I can't seem to google up any references. Except for:
>http://www.microsoft.com/windowsxp/pro/techinfo/administration/ipv6/defa
>ult.asp
>
>"Q: How can I force IPv6 connections using my Web browser?"
><SNIP>
>"For applications other than Internet Explorer: Connect using a literal
>IPv6 address. URLs that use the format for literal IPv6 addresses
>described in RFC 2732, "Format for Literal IPv6 Addresses in URLs," are
>not supported by the version of Internet Explorer provided with Windows
>XP."
>
>There was some discussion about this deprecation as the
>Techpreviews (Win2k/NT4) did support literal url's.
>The XP version and up though won't support it to overcome
>one major 'problem': website 'designers' embedding IP's
>inside websites to 'speed things up' (go figure).
>And there where a number of other reasons for deciding so.
>Unfortunatly I can't find the messages which where sent
>to a mailinglist about this discussion which also contained
>why they decided this. Note that wininet.dll doesn't support
>it that's why IE doesn't either...
>
>MS CC'd, they can best explain the rationale behind it.

This line of reasoning troubles me. One of the ways in which numeric IP 
addresses are useful in URLs is for talking to systems which are not yet 
fully configured (e.g. configuring routers and such). I'm sure Microsoft's 
answer to this is "Use UPNP" but that may not be a universally sufficient 
answer. Others will say "Use Zeroconf" which may also not be sufficient. I 
guess I'm just really uncomfortable requiring name spaces in temporary and 
disconnected networks as an absolute requirement.

Ad-hoc networks are another similar case, where two machines are connected 
via ad-hoc wireless, bluetooth, firewire, or similar. I'd think it might be 
useful to be able to serve web pages between two laptops on a train without 
requiring a naming service to be present. Perhaps that won't be an issue in 
the brave new world.

It just seems to me there is some utility in having this capability (and 
others must have thought so since we have an RFC describing the 
formatting). Let's think hard before deciding we are sure there are no 
useful cases left.





From owner-ietf@ietf.org  Wed Apr  2 12:55:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20573;
	Wed, 2 Apr 2003 12:55:21 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190mbe-00050g-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 13:05:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190maF-0004tk-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 13:03:35 -0500
Received: from purgatory.unfix.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20382
	for <ietf@ietf.org>; Wed, 2 Apr 2003 12:46:43 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id 3149D8F32; Wed,  2 Apr 2003 19:49:07 +0200 (CEST)
Received: from limbo (limbo.unfix.org [10.100.13.33])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 94E918F25; Wed,  2 Apr 2003 19:48:58 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Keith Moore'" <moore@cs.utk.edu>, "'John C Klensin'" <john-ietf@jck.com>
Cc: <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...))
Date: Wed, 2 Apr 2003 19:49:41 +0200
Organization: Unfix
Message-ID: <00c401c2f940$3d3a9db0$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <20030402120337.7284bb8f.moore@cs.utk.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-Virus-Scanned: by AMaViS @ purgatory.unfix.org
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA20573

Keith Moore wrote:

<Large snip>

> 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.

You might almost forget about SMB/CIFS :)
No DNS in there and most people use it daily without even realising it.

Greets,
 Jeroen




From owner-ietf@ietf.org  Wed Apr  2 14:00:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23146;
	Wed, 2 Apr 2003 14:00:34 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190nbB-0000Ig-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 14:08:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190nUV-0008Rv-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 14:01:43 -0500
Received: from purgatory.unfix.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22656
	for <ietf@ietf.org>; Wed, 2 Apr 2003 13:44:49 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id 29D458F33; Wed,  2 Apr 2003 20:47:16 +0200 (CEST)
Received: from limbo (limbo.unfix.org [10.100.13.33])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 24C378B6F; Wed,  2 Apr 2003 20:47:09 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Daniel Senie'" <dts@senie.com>, <ietf@ietf.org>
Subject: RE: Thinking differently about the site local problem (was:  RE: site local addresses (was Re: Fw: Welcome to the InterNAT...)) 
Date: Wed, 2 Apr 2003 20:47:47 +0200
Organization: Unfix
Message-ID: <00e401c2f948$5b372f60$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <5.2.0.9.2.20030402120246.01b20eb8@mail.amaranth.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-Virus-Scanned: by AMaViS @ purgatory.unfix.org
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Daniel Senie wrote:

<big SNIP>

> Ad-hoc networks are another similar case, where two machines 
> are connected via ad-hoc wireless, bluetooth, firewire,
> or similar. I'd think it might be useful to be able to
> serve web pages between two laptops on a train without 
> requiring a naming service to be present. Perhaps that won't 
> be an issue in the brave new world.

Your naming service will probably be of the broadcast kind
In any other way do you like remembering and typing over 128bit
addresses?? :)
Most OS's require a (unique) hostname to be entered/automatically
generated on install to identify the host to the rest of the
system/network/users. This note can also be used to identify
it over your file sharing protocol. SMB/CIFS comes with it's
own version for example. Most Gnutella/* I don't know what
filesharing protocols also have a naming system based on
the users login name etc. Heck even your bluetooth cellphone
nicely announces it's name + address around the room when
you accidentally forget to turn it off. Last weekend some
unnamed person was even spamming all the people at the
national ISP Karting competition over bluetooth. Good guess
to try and spam there as most ISP people are fond of geek
tools but also forget to turn their toys off/protect them :)

> It just seems to me there is some utility in having this 
> capability (and  others must have thought so since we have
> an RFC describing the formatting). Let's think hard before
> deciding we are sure there are no useful cases left.

Ofcourse there is a need for this, but like SL there are some
ways of solving the current ways of doing it. Better clean
up now than be sorry in the end. Eg alcatel adsl modems have a
web&telnet-interface for configuring them, then again being
a SOHO product it should be capable of autoconfiguration.
One thing that's for sure is that you can't use two of those
devices in the same network as the IP's will always be 10.0.0.138
with no other way to change it than by serial or the network.
As we did invent DAD there is no such 'defacto' IP for those
boxes to configure themselves with any more... 
We could use ping6 ff02::1%eth0, but tell that to a homeuser...

Greets,
 Jeroen




From owner-ietf@ietf.org  Wed Apr  2 14:46:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25202;
	Wed, 2 Apr 2003 14:46:43 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190oNZ-0002vB-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 14:58:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190oJp-0002lD-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 14:54:45 -0500
Received: from purgatory.unfix.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24633
	for <ietf@ietf.org>; Wed, 2 Apr 2003 14:37:51 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id B34768F34; Wed,  2 Apr 2003 21:40:17 +0200 (CEST)
Received: from limbo (limbo.unfix.org [10.100.13.33])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id A49F389CD; Wed,  2 Apr 2003 21:40:06 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: <alh-ietf@tndh.net>, <ietf@ietf.org>
Subject: RE: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...)) 
Date: Wed, 2 Apr 2003 21:40:42 +0200
Organization: Unfix
Message-ID: <00ee01c2f94f$c0712b90$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <099501c2f93a$4e62c370$ee1a4104@eagleswings>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-Virus-Scanned: by AMaViS @ purgatory.unfix.org
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA25202

Tony Hain [mailto:alh-ietf@tndh.net] wrote:

> Jeroen Massar wrote:
> > ... That's also why IE in XP doesn't support it. 
> 
> Making claims that you know nothing about, only exposes your lack of
> clue.

Fortunatly I don't have to resolve to personal accusations
to get my point across. I cc:'d the people who really
know how the stuff works so they could comment on these statements. :)

Greets,
 Jeroen




From owner-ietf@ietf.org  Wed Apr  2 15:19:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07043;
	Wed, 2 Apr 2003 15:19:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190oge-000671-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 15:18:20 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190ofk-0005Oz-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 15:17:24 -0500
Received: from tndh.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25857
	for <ietf@ietf.org>; Wed, 2 Apr 2003 15:00:29 -0500 (EST)
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S23DC6> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 02 Apr 2003 12:02:56 -0800
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Jeroen Massar'" <jeroen@unfix.org>, <ietf@ietf.org>
Subject: RE: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...)) 
Date: Wed, 2 Apr 2003 12:02:53 -0800
Message-ID: <09b701c2f952$d92aa3c0$ee1a4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <00ee01c2f94f$c0712b90$210d640a@unfix.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA07043

Jeroen Massar wrote:
> Tony Hain [mailto:alh-ietf@tndh.net] wrote:
> 
> > Jeroen Massar wrote:
> > > ... That's also why IE in XP doesn't support it.
> > 
> > Making claims that you know nothing about, only exposes 
> your lack of 
> > clue.
> 
> Fortunatly I don't have to resolve to personal accusations
> to get my point across. I cc:'d the people who really
> know how the stuff works so they could comment on these statements. :)

I was the IPv6 program manager for what ended up shipping in XP, and
literals in wininet didn't make it for lack of testing resources. 

Tony






From owner-ietf@ietf.org  Wed Apr  2 17:56:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13694;
	Wed, 2 Apr 2003 17:56:26 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190rKZ-00056o-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 18:07:43 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190UR6-0005NE-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 17:40:56 -0500
Received: from carwash.centive.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA18432
	for <ietf@ietf.org>; Tue, 1 Apr 2003 17:24:16 -0500 (EST)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (NAVGW 2.5.2.11) with SMTP id M2003040117311421515
 for <ietf@ietf.org>; Tue, 01 Apr 2003 17:31:14 -0500
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 1 Apr 2003 17:24:27 -0500
Message-ID: <3E8A119B.5060905@centive.com>
Date: Tue, 01 Apr 2003 17:24:27 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
References: <200304012126.h31LQlPW006088@ginger.lcs.mit.edu> <20030401165833.4cec836f.moore@cs.utk.edu>
In-Reply-To: <20030401165833.4cec836f.moore@cs.utk.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Apr 2003 22:24:27.0951 (UTC) FILETIME=[75313BF0:01C2F89D]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:

>>    > From: Keith Moore <moore@cs.utk.edu>
>>
>>    > HIP only solves part of the problem ... it doesn't provide any
>>    > way of mapping between that identity and an address where you
>>    > can reach the host.
>>
>without a mechanism to map the endpoint
>identifier to an IP address, such identifiers are useless in referrals
>between application components.
>  
>
Not completely useless; they would prevent the problem of reaching the 
*wrong* endpoint.  This isn't much help if you have only one address for 
the endpoint you want; but, if you have a global and a local address for 
it, and you get the wrong HIP from the host that answers when you use 
the local address, then you know not to use that one.

-- 
/============================================================\
|John Stracke      |jstracke@centive.com                     |
|Principal Engineer|http://www.centive.com                   |
|Centive           |My opinions are my own.                  |
|============================================================|
|"God does not play games with His loyal servants." "Whoo-ee,|
|where have you *been*?" --_Good Omens_                      |
\============================================================/







From owner-ietf@ietf.org  Wed Apr  2 17:57:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13879;
	Wed, 2 Apr 2003 17:57:23 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190rKb-00057b-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 18:07:45 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190ntH-0001XT-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 14:27:19 -0500
Received: from carwash.centive.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA23588
	for <ietf@ietf.org>; Wed, 2 Apr 2003 14:10:25 -0500 (EST)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (NAVGW 2.5.2.11) with SMTP id M2003040214172513292
 for <ietf@ietf.org>; Wed, 02 Apr 2003 14:17:25 -0500
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 2 Apr 2003 14:10:41 -0500
Message-ID: <3E8B35B1.7030906@centive.com>
Date: Wed, 02 Apr 2003 14:10:41 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Thinking differently about the site local problem (was:  RE:
 site local addresses (was Re: Fw: Welcome to the InterNAT...))
References: <00e401c2f948$5b372f60$210d640a@unfix.org>
In-Reply-To: <00e401c2f948$5b372f60$210d640a@unfix.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Apr 2003 19:10:41.0376 (UTC) FILETIME=[8DA06E00:01C2F94B]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jeroen Massar wrote:

>>Ad-hoc networks are another similar case, where two machines 
>>are connected via ad-hoc wireless, bluetooth, firewire,
>>or similar.
>>    
>>
>In any other way do you like remembering and typing over 128bit
>addresses?? :)
>
:: is your friend.  If you're building an ad hoc, point-to-point 
network, you can pick convenient addresses.

>Most OS's require a (unique) hostname to be entered/automatically
>generated on install
>
False.

-- 
/============================================================\
|John Stracke      |jstracke@centive.com                     |
|Principal Engineer|http://www.centive.com                   |
|Centive           |My opinions are my own.                  |
|============================================================|
|"God does not play games with His loyal servants." "Whoo-ee,|
|where have you *been*?" --_Good Omens_                      |
\============================================================/







From owner-ietf@ietf.org  Wed Apr  2 17:56:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13724;
	Wed, 2 Apr 2003 17:56:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190rKa-00057B-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 18:07:44 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190VML-0000BS-00
	for ietf@ran.ietf.org; Tue, 01 Apr 2003 18:40:05 -0500
Received: from thrintun.hactrn.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21452
	for <ietf@ietf.org>; Tue, 1 Apr 2003 18:23:23 -0500 (EST)
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 8F34318EC
	for <ietf@ietf.org>; Tue,  1 Apr 2003 18:25:49 -0500 (EST)
Date: Tue, 01 Apr 2003 18:25:49 -0500
From: Rob Austein <sra@hactrn.net>
To: ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
In-Reply-To: <20030401165833.4cec836f.moore@cs.utk.edu>
References: <200304012126.h31LQlPW006088@ginger.lcs.mit.edu>
	<20030401165833.4cec836f.moore@cs.utk.edu>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030401232549.8F34318EC@thrintun.hactrn.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

At Tue, 1 Apr 2003 16:58:33 -0500, Keith Moore wrote:
> 
> On Tue, 1 Apr 2003 16:26:47 -0500
> "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu> wrote:
> 
> >     > From: Keith Moore <moore@cs.utk.edu>
> > 
> >     > HIP only solves part of the problem ... it doesn't provide any
> >     > way of mapping between that identity and an address where you
> >     > can reach the host.
> > 
> > A system doesn't have to provide mechanisms to look up mappings from
> > <any-name> to <any-other-name> to be useful; 
> 
> agreed.  but it does need to provide such mechanisms in order to provide
> useful endpoint identifiers.  without a mechanism to map the endpoint
> identifier to an IP address, such identifiers are useless in referrals
> between application components.

Correct, if you assume that there will be situations in which you only
have the endpoint identifier and you need the IP address.  That's not
the only conceivable way of passing around a referal, it's just the
one that's closest to being a drop-in replacement for a referal
mechanism based on raw IP addresess.

In other words, whether you need this particular mapping depends on
precisely how you intend to use the endpoint identifiers, which is
what I think Noel was saying.





From owner-ietf@ietf.org  Wed Apr  2 18:09:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14580;
	Wed, 2 Apr 2003 18:09:43 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190rX4-0007nI-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 18:20:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190rW9-0007k1-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 18:19:41 -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 SAA14379
	for <ietf@ietf.org>; Wed, 2 Apr 2003 18:02:46 -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 h32N59A01698;
        Wed, 2 Apr 2003 18:05:10 -0500 (EST)
Date: Wed, 2 Apr 2003 18:05:09 -0500
From: Keith Moore <moore@cs.utk.edu>
To: Rob Austein <sra@hactrn.net>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
Message-Id: <20030402180509.60a56bed.moore@cs.utk.edu>
In-Reply-To: <20030401232549.8F34318EC@thrintun.hactrn.net>
References: <200304012126.h31LQlPW006088@ginger.lcs.mit.edu>
	<20030401165833.4cec836f.moore@cs.utk.edu>
	<20030401232549.8F34318EC@thrintun.hactrn.net>
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

> > > A system doesn't have to provide mechanisms to look up mappings
> > > from<any-name> to <any-other-name> to be useful; 
> > 
> > agreed.  but it does need to provide such mechanisms in order to
> > provide useful endpoint identifiers.  without a mechanism to map the
> > endpoint identifier to an IP address, such identifiers are useless
> > in referrals between application components.
> 
> Correct, if you assume that there will be situations in which you only
> have the endpoint identifier and you need the IP address.  That's not
> the only conceivable way of passing around a referal, it's just the
> one that's closest to being a drop-in replacement for a referal
> mechanism based on raw IP addresess.

well, we've had people saying that you shouldn't pass around the IP
address.  obviously the new identifier doesn't help you avoid passing
around the IP address if you can't get the IP address from the
identifier.



From owner-ietf@ietf.org  Wed Apr  2 18:14:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14961;
	Wed, 2 Apr 2003 18:14:19 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190rcw-00087X-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 18:26:42 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190rbd-0007yD-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 18:25:21 -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 SAA14489
	for <ietf@ietf.org>; Wed, 2 Apr 2003 18:08:25 -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 h32NAmA01710;
        Wed, 2 Apr 2003 18:10:48 -0500 (EST)
Date: Wed, 2 Apr 2003 18:10:48 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "Brian Zill" <bzill@microsoft.com>
Cc: moore@cs.utk.edu, jeroen@unfix.org, spencer_dawkins@yahoo.com,
        ietf@ietf.org, ipv6-fb@microsoft.com
Subject: Re: Thinking differently about the site local problem (was: RE:
 site local addresses (was Re: Fw: Welcome to the InterNAT...))
Message-Id: <20030402181048.61182ceb.moore@cs.utk.edu>
In-Reply-To: <CB7153628BD3724096258CBFD70AA8910753BD5B@red-msg-04.redmond.corp.microsoft.com>
References: <CB7153628BD3724096258CBFD70AA8910753BD5B@red-msg-04.redmond.corp.microsoft.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

> The lack of IPv6 literal address support in the version of wininet.dll
> that shipped with Windows XP was for reasons of engineering
> expediency, 

in other words, MS deliberately shipped a broken product.

> I do, however, also remember a discussion on one of the IPv6 mailing
> lists about this, and it seemed that there were several members of the
> IPv6 community at large who thought it was great that we weren't
> currently supporting them.  Apparently there are those who think
> hard-coding IP addresses (of any version) in URLs is a bad idea.

yes, there are those who think that it's desirable to force all apps to
suffer the delays and unreliability of DNS every time a connection is
established. they are deluded.

Keith



From owner-ietf@ietf.org  Wed Apr  2 18:11:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14750;
	Wed, 2 Apr 2003 18:11:31 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190rbM-0007yB-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 18:25:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190rak-0007uY-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 18:24:26 -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 SAA14458
	for <ietf@ietf.org>; Wed, 2 Apr 2003 18:07:30 -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 h32N7vA01703;
        Wed, 2 Apr 2003 18:07:57 -0500 (EST)
Date: Wed, 2 Apr 2003 18:07:56 -0500
From: Keith Moore <moore@cs.utk.edu>
To: John Stracke <jstracke@centive.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Thinking differently about names and addresses
Message-Id: <20030402180756.4e7775a6.moore@cs.utk.edu>
In-Reply-To: <3E8A119B.5060905@centive.com>
References: <200304012126.h31LQlPW006088@ginger.lcs.mit.edu>
	<20030401165833.4cec836f.moore@cs.utk.edu>
	<3E8A119B.5060905@centive.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

> >without a mechanism to map the endpoint
> >identifier to an IP address, such identifiers are useless in
> >referrals between application components.
> >
> Not completely useless; they would prevent the problem of reaching the
> *wrong* endpoint.  This isn't much help if you have only one address
> for the endpoint you want; but, if you have a global and a local
> address for it, and you get the wrong HIP from the host that answers
> when you use the local address, then you know not to use that one.

true.  but requiring apps to determine which of several potentially
ambiguous (or obsolete) addresses is the one that reaches the intended
peer by trial-and-error does not strike me as an efficient or
desirable strategy. 



From owner-ietf@ietf.org  Wed Apr  2 17:56:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13693;
	Wed, 2 Apr 2003 17:56:26 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190rKb-00057R-00
	for ietf-list@ran.ietf.org; Wed, 02 Apr 2003 18:07:45 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190mm5-0005wr-00
	for ietf@ran.ietf.org; Wed, 02 Apr 2003 13:15:49 -0500
Received: from mail4.microsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20761
	for <ietf@ietf.org>; Wed, 2 Apr 2003 12:58:55 -0500 (EST)
Received: from inet-vrs-04.redmond.corp.microsoft.com ([157.54.8.149]) by mail4.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Wed, 2 Apr 2003 10:01:19 -0800
Received: from 157.54.5.25 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 02 Apr 2003 10:01:18 -0800
Received: from red-msg-04.redmond.corp.microsoft.com ([157.54.12.196]) by inet-hub-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3788.0);
	 Wed, 2 Apr 2003 10:01:14 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.6895.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...)) 
Date: Wed, 2 Apr 2003 10:00:52 -0800
Message-ID: <CB7153628BD3724096258CBFD70AA8910753BD5B@red-msg-04.redmond.corp.microsoft.com>
Thread-Topic: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...)) 
Thread-Index: AcL5Kwlb9wFKMXNiSlmkJ4jBNP0mHgAFK3pw
From: "Brian Zill" <bzill@microsoft.com>
To: "Jeroen Massar" <jeroen@unfix.org>,
        "Spencer Dawkins" <spencer_dawkins@yahoo.com>, <ietf@ietf.org>
Cc: "IPv6 Feedback Alias" <ipv6-fb@microsoft.com>
X-OriginalArrivalTime: 02 Apr 2003 18:01:14.0503 (UTC) FILETIME=[D9FA1170:01C2F941]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA13693

Hi Jeroen,

The lack of IPv6 literal address support in the version of wininet.dll
that shipped with Windows XP was for reasons of engineering expediency,
and not any political policy decision.  To the best of my knowledge,
Microsoft hasn't said one way or another as to whether or not we plan to
support IPv6 literal addresses in URLs in future releases.

I do, however, also remember a discussion on one of the IPv6 mailing
lists about this, and it seemed that there were several members of the
IPv6 community at large who thought it was great that we weren't
currently supporting them.  Apparently there are those who think
hard-coding IP addresses (of any version) in URLs is a bad idea.
Perhaps this is the discussion you are remembering.

--Brian

> -----Original Message-----
> From: Jeroen Massar [mailto:jeroen@unfix.org] 
> Sent: Wednesday, 02 April, 2003 07:19
> To: 'Spencer Dawkins'; ietf@ietf.org
> Cc: IPv6 Feedback Alias
> Subject: RE: Thinking differently about the site local 
> problem (was: RE: site local addresses (was Re: Fw: Welcome 
> to the InterNAT...)) 
> 
> 
> Spencer Dawkins wrote:
> 
> > Hi, Jeroen,
> > 
> > Are you talking about ftp://ftp.rfc-editor.org/in-notes/rfc2732.txt 
> > (PS)?
> > 
> > My quick read of this RFC is that it says "don't use IPv6 literals 
> > without enclosing them in brackets", as in
> > 
> >       host          = hostname | IPv4address | IPv6reference
> >       ipv6reference = "[" IPv6address "]"
> > 
> > But that's not quite the same thing you said: "never use 
> IPv6 IP's in 
> > URL's".
> > 
> > If you're talking about another reference, could you provide it? A 
> > quick RFC search for "IPv6 URL" turned up only this RFC...
> 
> Yes, though I can't seem to google up any references. Except 
> for: 
> http://www.microsoft.com/windowsxp/pro/techinfo/administration
/ipv6/defa
ult.asp

"Q: How can I force IPv6 connections using my Web browser?" <SNIP> "For
applications other than Internet Explorer: Connect using a literal IPv6
address. URLs that use the format for literal IPv6 addresses described
in RFC 2732, "Format for Literal IPv6 Addresses in URLs," are not
supported by the version of Internet Explorer provided with Windows XP."

There was some discussion about this deprecation as the Techpreviews
(Win2k/NT4) did support literal url's. The XP version and up though
won't support it to overcome one major 'problem': website 'designers'
embedding IP's inside websites to 'speed things up' (go figure). And
there where a number of other reasons for deciding so. Unfortunatly I
can't find the messages which where sent to a mailinglist about this
discussion which also contained why they decided this. Note that
wininet.dll doesn't support it that's why IE doesn't either...

MS CC'd, they can best explain the rationale behind it.

Greets,
 Jeroen

PS: Is 'google' already an official english verb? :)






From owner-ietf@ietf.org  Thu Apr  3 02:16:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08327;
	Thu, 3 Apr 2003 02:16:41 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 190ydM-0007G0-00
	for ietf-list@ran.ietf.org; Thu, 03 Apr 2003 01:55:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 190ydB-0007EU-00
	for ietf@ran.ietf.org; Thu, 03 Apr 2003 01:55:25 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26160
	for <ietf@ietf.org>; Thu, 3 Apr 2003 01:38:24 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP id A937B6238C
	for <ietf@ietf.org>; Thu,  3 Apr 2003 08:40:51 +0200 (CEST)
Date: Thu, 03 Apr 2003 08:40:51 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: A plea for calm
Message-ID: <255900000.1049352051@askvoll.hjemme.alvestrand.no>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

the debate that was triggered by the site-local debate has touched on a lot 
of topics that are at the very heart of the design of the Internet, and for 
which we have to make important decisions in the near future.

This is a good and proper discussion to have on this mailing list.

The debate has also touched on the site-local decision of the IPv6 working 
group, a subject to which there are strong emotions attached.
The technical debates on that specific topic belong in the IPv6 WG's 
mailing list; the larger architectural issues belong (IMHO) here.

However, I must ask participants to try to remember the guidelines for 
conduct for the IETF, RFC 3184. In particular:

   1. IETF participants extend respect and courtesy to their colleagues
      at all times.

      IETF participants come from diverse origins and backgrounds and
      are equipped with multiple capabilities and ideals.  Regardless of
      these individual differences, participants treat their colleagues
      with respect as persons--especially when it is difficult to agree
      with them.

   2. IETF participants develop and test ideas impartially, without
      finding fault with the colleague proposing the idea.

      We dispute ideas by using reasoned argument, rather than through
      intimidation or ad hominem attack.  Or, said in a somewhat more
      IETF-like way:

            "Reduce the heat and increase the light"

I'm sure we all want to. And I'm also sure we all find it hard to adhere to 
at times. But we need it in order to get work done.

One more point: An argument does not become stronger by being repeated more 
often.
Of the 175 senders to this list last month, 20 of us contributed more than 
half the list traffic. If we have made our position clear, the argument is, 
I think, stronger if it is not repeated - and silence allows other voices 
to be heard.

Yours for a thoughtful debate,

                     Harald Alvestrand




From owner-ietf@ietf.org  Thu Apr  3 06:00:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13535;
	Thu, 3 Apr 2003 06:00:37 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1912YF-0004fp-00
	for ietf-list@ran.ietf.org; Thu, 03 Apr 2003 06:06:35 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1912XQ-0004ec-00
	for ietf@ran.ietf.org; Thu, 03 Apr 2003 06:05:44 -0500
Received: from mailhost.packetfront.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13078
	for <ietf@ietf.org>; Thu, 3 Apr 2003 05:48:39 -0500 (EST)
Received: from [192.168.1.11] (helo=Mtw10)
	by mailhost.packetfront.com with esmtp (Exim 3.35 #1 (Debian))
	id 1912J2-00088t-00; Thu, 03 Apr 2003 12:50:52 +0200
From: "Fredrik Nyman" <fredrik@packetfront.com>
Organization: PacketFront Sweden AB
To: Keith Moore <moore@cs.utk.edu>
Date: Thu, 3 Apr 2003 12:50:44 +0200
MIME-Version: 1.0
Subject: Re: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))
Reply-to: fredrik@packetfront.com
CC: moore@cs.utk.edu, jeroen@unfix.org, spencer_dawkins@yahoo.com,
        ietf@ietf.org, ipv6-fb@microsoft.com
Message-ID: <3E8C2E24.19318.51AB705@localhost>
In-reply-to: <20030402181048.61182ceb.moore@cs.utk.edu>
References: <CB7153628BD3724096258CBFD70AA8910753BD5B@red-msg-04.redmond.corp.microsoft.com>
X-mailer: Pegasus Mail for Windows (v4.01)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

On 2 Apr 2003 at 18:10, Keith Moore wrote:

> > The lack of IPv6 literal address support in the version of wininet.dll
> > that shipped with Windows XP was for reasons of engineering
> > expediency, 
> 
> in other words, MS deliberately shipped a broken product.

Oh, look, release notes, known issue statements, bugtracker entries...

Seems like everybody is deliberately shipping broken products...

-- 
Fredrik Nyman
PacketFront Sweden AB
http://www.packetfront.com/




From owner-ietf@ietf.org  Thu Apr  3 07:17:53 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17070;
	Thu, 3 Apr 2003 07:17:53 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1913nf-00059I-00
	for ietf-list@ran.ietf.org; Thu, 03 Apr 2003 07:26:35 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1913n2-000584-00
	for ietf@ran.ietf.org; Thu, 03 Apr 2003 07:25:56 -0500
Received: from purgatory.unfix.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16830
	for <ietf@ietf.org>; Thu, 3 Apr 2003 07:08:52 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id 8C1DC8992; Thu,  3 Apr 2003 14:11:17 +0200 (CEST)
Received: from limbo (limbo.unfix.org [10.100.13.33])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 5E3C678B2; Thu,  3 Apr 2003 14:11:12 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'John Stracke'" <jstracke@centive.com>, <ietf@ietf.org>
Subject: RE: Thinking differently about the site local problem (was:  RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))
Date: Thu, 3 Apr 2003 14:12:22 +0200
Organization: Unfix
Message-ID: <004f01c2f9da$48370fb0$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <3E8B35B1.7030906@centive.com>
X-Virus-Scanned: by AMaViS @ purgatory.unfix.org
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John Stracke wrote:
> Jeroen Massar wrote:
> 
> >>Ad-hoc networks are another similar case, where two machines 
> >>are connected via ad-hoc wireless, bluetooth, firewire,
> >>or similar.
> >>    
> >>
> >In any other way do you like remembering and typing over 128bit
> >addresses?? :)
> >
> :: is your friend.  If you're building an ad hoc, point-to-point 
> network, you can pick convenient addresses.

:: as in all 0's which corresponds to 'not bound'?
I don't see how you are going to communicate between
two hosts with a unbound IP. Especially in a ad-hoc
network where everything should be configured automatically.

> >Most OS's require a (unique) hostname to be entered/automatically
> >generated on install
> >
> False.

And is there any reasoned argument instead of the simple 'false'?

Greets,
 Jeroen





From owner-ietf@ietf.org  Thu Apr  3 07:50:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18089;
	Thu, 3 Apr 2003 07:50:20 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191491-0006uZ-00
	for ietf-list@ran.ietf.org; Thu, 03 Apr 2003 07:48:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19148v-0006q7-00
	for ietf@ran.ietf.org; Thu, 03 Apr 2003 07:48:33 -0500
Received: from mail.wrs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17454
	for <ietf@ietf.org>; Thu, 3 Apr 2003 07:31:29 -0500 (EST)
Received: from IDLEWYLDE.windriver.com ([147.11.233.1])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id EAA01548;
	Thu, 3 Apr 2003 04:30:50 -0800 (PST)
Message-Id: <5.1.0.14.2.20030403072514.037aefe0@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 03 Apr 2003 07:29:33 -0500
To: "Jeroen Massar" <jeroen@unfix.org>
From: Margaret Wasserman <mrw@windriver.com>
Subject: RE: Thinking differently about the site local problem (was: 
  RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))
Cc: "'John Stracke'" <jstracke@centive.com>, <ietf@ietf.org>
In-Reply-To: <004f01c2f9da$48370fb0$210d640a@unfix.org>
References: <3E8B35B1.7030906@centive.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk


Hi Jeroen,

> > >Most OS's require a (unique) hostname to be entered/automatically
> > >generated on install
> > >
> > False.
>
>And is there any reasoned argument instead of the simple 'false'?

Some examples certainly would have been helpful...

I can give one common example.  Special-purpose client systems
(consumer devices, car infotainment systems, etc.) seldom require
or configure a DNS name.

In most IPv4 situations, though, these types of systems would
receive their addresses through DHCP, usually through an ISPs
DHCP server.  In many cases, ISPs provide generic (e.g.
hostNNNNNNN.isp.com) host names for all of the addresses in their
DHCP pool, so that reverse lookups will work, etc.

But the operating system and TCP/IP stack on the device do
not actually require that a hostname be configured.

Margaret






From owner-ietf@ietf.org  Thu Apr  3 07:50:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18151;
	Thu, 3 Apr 2003 07:50:53 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1914MY-0007IF-00
	for ietf-list@ran.ietf.org; Thu, 03 Apr 2003 08:02:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1914H7-000790-00
	for ietf@ran.ietf.org; Thu, 03 Apr 2003 07:57:01 -0500
Received: from purgatory.unfix.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17729
	for <ietf@ietf.org>; Thu, 3 Apr 2003 07:39:57 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id F08908999; Thu,  3 Apr 2003 14:42:23 +0200 (CEST)
Received: from limbo (limbo.unfix.org [10.100.13.33])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id E288B8992; Thu,  3 Apr 2003 14:42:18 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Margaret Wasserman'" <mrw@windriver.com>
Cc: "'John Stracke'" <jstracke@centive.com>, <ietf@ietf.org>
Subject: RE: Thinking differently about the site local problem (was:   RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))
Date: Thu, 3 Apr 2003 14:43:28 +0200
Organization: Unfix
Message-ID: <006701c2f9de$a0c61ff0$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To: <5.1.0.14.2.20030403072514.037aefe0@mail.windriver.com>
X-Virus-Scanned: by AMaViS @ purgatory.unfix.org
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA18151

Margaret Wasserman [mailto:mrw@windriver.com] wrote:

> Hi Jeroen,
> 
> > > >Most OS's require a (unique) hostname to be entered/automatically
> > > >generated on install
> > > >
> > > False.
> >
> >And is there any reasoned argument instead of the simple 'false'?
> 
> Some examples certainly would have been helpful...
> 
> I can give one common example.  Special-purpose client systems
> (consumer devices, car infotainment systems, etc.) seldom require
> or configure a DNS name.
> 
> In most IPv4 situations, though, these types of systems would
> receive their addresses through DHCP, usually through an ISPs
> DHCP server.  In many cases, ISPs provide generic (e.g.
> hostNNNNNNN.isp.com) host names for all of the addresses in their
> DHCP pool, so that reverse lookups will work, etc.
> 
> But the operating system and TCP/IP stack on the device do
> not actually require that a hostname be configured.

My thought went out from both the manual page of a typical Unix box:
8<-------
 Hostname is used to either set or display the current
 host or domain name of the system. This name is used
 by many of the networking programs to identify the
 machine. The domain name is also used by NIS/YP.
------->8

And the fact that windows boxes nowadays also
autogenerate a hostname based on some of the
properties of the machine to overcome clashes
in the SMB/CIFS namespace. Note that this still
has nothing to with IP.

Phones and other devices that could be used
for transfering files usually autogenerate a
hostname based on their cellphonenumber.

But indeed there are bound to be apparatus which 
don't have such a feature, thus one will have to
type the full IP then if you want to do something.
Fortunatly finding out all the hosts on a subnet
isn't that trivial anymore ff02::1 ;)
But I wonder how consumer friendly that is...

Greets,
 Jeroen





From owner-ietf@ietf.org  Thu Apr  3 08:23:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19033;
	Thu, 3 Apr 2003 08:23:41 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1914qQ-0000fd-00
	for ietf-list@ran.ietf.org; Thu, 03 Apr 2003 08:33:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1914iO-0000VU-00
	for ietf@ran.ietf.org; Thu, 03 Apr 2003 08:25:12 -0500
Received: from carwash.centive.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA18715
	for <ietf@ietf.org>; Thu, 3 Apr 2003 08:08:07 -0500 (EST)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (NAVGW 2.5.2.11) with SMTP id M2003040308150712935
 for <ietf@ietf.org>; Thu, 03 Apr 2003 08:15:07 -0500
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 3 Apr 2003 08:08:23 -0500
Message-ID: <3E8C3247.8010105@centive.com>
Date: Thu, 03 Apr 2003 08:08:23 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Thinking differently about the site local problem (was:  RE:
 site local addresses (was Re: Fw: Welcome to the InterNAT...))
References: <004f01c2f9da$48370fb0$210d640a@unfix.org>
In-Reply-To: <004f01c2f9da$48370fb0$210d640a@unfix.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Apr 2003 13:08:23.0509 (UTC) FILETIME=[1B42E850:01C2F9E2]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jeroen Massar wrote:

>John Stracke wrote:
>  
>
>>Jeroen Massar wrote:
>>
>>    
>>
>>>>Ad-hoc networks are another similar case, where two machines 
>>>>are connected via ad-hoc wireless, bluetooth, firewire,
>>>>or similar.
>>>>   
>>>>
>>>>        
>>>>
>>>In any other way do you like remembering and typing over 128bit
>>>addresses?? :)
>>>
>>>      
>>>
>>:: is your friend.  If you're building an ad hoc, point-to-point 
>>network, you can pick convenient addresses.
>>    
>>
>
>:: as in all 0's which corresponds to 'not bound'?
>
No, as in a string of 0s.  If you set up your own isolated network, you 
can make one host be 1::1 and the other 1::2.

>>>Most OS's require a (unique) hostname to be entered/automatically
>>>generated on install
>>>      
>>>
>>False.
>>    
>>
>And is there any reasoned argument instead of the simple 'false'?
>  
>
It seems pretty obvious: no OS can require a unique hostname at install 
time, because it has no way of checking uniqueness.  The Unices I've 
installed (various versions of Solaris and Linux), even if they prompt 
for a hostname, will accept the default of "localhost.localdomain".  In 
addition, many, many machines (especially those bought preinstalled) are 
installed from standardized images, and have standardized hostnames.

-- 
/============================================================\
|John Stracke      |jstracke@centive.com                     |
|Principal Engineer|http://www.centive.com                   |
|Centive           |My opinions are my own.                  |
|============================================================|
|"God does not play games with His loyal servants." "Whoo-ee,|
|where have you *been*?" --_Good Omens_                      |
\============================================================/





From owner-ietf@ietf.org  Thu Apr  3 10:02:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22371;
	Thu, 3 Apr 2003 10:02:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1916JV-0004ij-00
	for ietf-list@ran.ietf.org; Thu, 03 Apr 2003 10:07:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1916Ip-0004gL-00
	for ietf@ran.ietf.org; Thu, 03 Apr 2003 10:06:55 -0500
Received: from falcon.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21813
	for <ietf@ietf.org>; Thu, 3 Apr 2003 09:49:48 -0500 (EST)
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by falcon.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19164Z-000235-00; Thu, 03 Apr 2003 06:52:11 -0800
Date: Thu, 3 Apr 2003 09:46:58 -0500
From: Keith Moore <moore@cs.utk.edu>
To: fredrik@packetfront.com
Cc: moore@cs.utk.edu, jeroen@unfix.org, spencer_dawkins@yahoo.com,
        ietf@ietf.org, ipv6-fb@microsoft.com
Subject: Re: Thinking differently about the site local problem (was: RE:
 site local addresses (was Re: Fw: Welcome to the InterNAT...))
Message-Id: <20030403094658.259cf9d6.moore@cs.utk.edu>
In-Reply-To: <3E8C2E24.19318.51AB705@localhost>
References: <CB7153628BD3724096258CBFD70AA8910753BD5B@red-msg-04.redmond.corp.microsoft.com>
	<3E8C2E24.19318.51AB705@localhost>
X-Mailer: Sylpheed version 0.8.10 (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

> > > The lack of IPv6 literal address support in the version of wininet.dll
> > > that shipped with Windows XP was for reasons of engineering
> > > expediency, 
> > 
> > in other words, MS deliberately shipped a broken product.
> 
> Oh, look, release notes, known issue statements, bugtracker entries...
> 
> Seems like everybody is deliberately shipping broken products...

Yeah, I was chastised in private mail for shooting the messenger, and
appropriately so.

It is a bit difficult for me to understand how support for address literals
could be considered such a low priority that it could be omitted from a
shipping product.  Recently when I wrote an app that used v6 and urls, the
first routine I wrote was one that would take either an address literal
or a DNS name, plus a port number, and return a properly filled-in sockaddr
structure  (no, getaddrinfo by itself isn't sufficient), and the second 
one I wrote was one that would parse a URL and extract either a DNS name or
address literal from that.  Writing both routines, and the test cases, and
testing the routines on several different platforms took about 2 hours.

Admittedly I'm a bit biased.  I've measured the percentage of email delivery
failures due to various reasons and discovered that DNS misconfiguration was
high on the list (MTA miscnfiguration was also high). I've also attempted to
measure the amount of delay caused by DNS lookups.  So I understand better
than most why it's important - for both diagnostic and performance reasons -
to support address literals.  

That and I suspect there's a philosophical difference in writing APIs.  I
believe in thinking hard about what an API needs to do before writing it, so
that the API once implemented will be able to be used for a wide set of
purposes.  That and I try hard to only have to implement the API once, because
the overhead in context switching my brain back to the API when I need to add
functionality to it is almost certainly larger that the effort required to
completely implement the API the first time.  If it's too difficult to
implement it completely, there's probably something wrong with the design.  I
do understand and use stubbing, but I regard that as a technique to be used
for quick prototypes that are going to be discarded anyway.  I also understand
the notion of biasing the testing toward the most frequently-used features on
the assumption that such testing will uncover the most common bugs.  But there
are important features that are not frequently used, and there are bugs that
are important to fix even though they are in seldom-used code.  Features used
for diagnostics, and security bugs are good examples of these.

Then there's the problem that when a 800-pound gorilla ships code, that
code largely defines expectations for what will and will not work in practice
- often moreso than the standards themselves.  So if MS ships code that
doesn't support address literals, then nobody will attempt to use address
literals unless they can detect that the client isn't using MS code.  For this
and other reasons, I believe that 800-pound gorillas have a greater
responsibility than their competitors to ship code that works properly.

OTOH, servers that take the trouble to recognize that the client isn't a
MS client can provide their clients with significantly better response time by
giving those clients address literals in internal references (either in HTTP
referrals or in HTML).



From owner-ietf@ietf.org  Thu Apr  3 10:51:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26278;
	Thu, 3 Apr 2003 10:51:16 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19179k-0006S0-00
	for ietf-list@ran.ietf.org; Thu, 03 Apr 2003 11:01:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19178G-0006Na-00
	for ietf@ran.ietf.org; Thu, 03 Apr 2003 11:00:04 -0500
Received: from carwash.centive.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA25753
	for <ietf@ietf.org>; Thu, 3 Apr 2003 10:42:57 -0500 (EST)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (NAVGW 2.5.2.11) with SMTP id M2003040310492411687
 ; Thu, 03 Apr 2003 10:49:24 -0500
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 3 Apr 2003 10:42:41 -0500
Message-ID: <3E8C5670.3070207@centive.com>
Date: Thu, 03 Apr 2003 10:42:40 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
CC: fredrik@packetfront.com, ipv6-fb@microsoft.com
Subject: Re: Thinking differently about the site local problem (was: RE: site
 local addresses (was Re: Fw: Welcome to the InterNAT...))
References: <CB7153628BD3724096258CBFD70AA8910753BD5B@red-msg-04.redmond.corp.microsoft.com>	<3E8C2E24.19318.51AB705@localhost> <20030403094658.259cf9d6.moore@cs.utk.edu>
In-Reply-To: <20030403094658.259cf9d6.moore@cs.utk.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Apr 2003 15:42:41.0024 (UTC) FILETIME=[A92B9800:01C2F9F7]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:

>Then there's the problem that when a 800-pound gorilla ships code, that
>code largely defines expectations for what will and will not work in practice
>- often moreso than the standards themselves.
>  
>
Strange as I feel defending Microsoft, I actually think it's commendable 
that they implemented IPv6 at all; it's not as if there's a lot of 
market demand for it yet.  From that viewpoint, it's not surprising that 
they gave IPv6 address literals a low priority.

(Personally, I would've implemented address literals *first*, so that, 
if I ran into a bug, I could isolate whether it was in DNS lookup or 
not.  Would've saved time in the long run, since debugging takes longer 
than coding.)

-- 
/============================================================\
|John Stracke      |jstracke@centive.com                     |
|Principal Engineer|http://www.centive.com                   |
|Centive           |My opinions are my own.                  |
|============================================================|
|"God does not play games with His loyal servants." "Whoo-ee,|
|where have you *been*?" --_Good Omens_                      |
\============================================================/





From owner-ietf@ietf.org  Thu Apr  3 12:03:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29859;
	Thu, 3 Apr 2003 12:03:48 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1918FV-0003oF-00
	for ietf-list@ran.ietf.org; Thu, 03 Apr 2003 12:11:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1918Ev-0003lx-00
	for ietf@ran.ietf.org; Thu, 03 Apr 2003 12:11:01 -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 LAA29401
	for <ietf@ietf.org>; Thu, 3 Apr 2003 11:53:52 -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 h33GsJA09159;
        Thu, 3 Apr 2003 11:54:19 -0500 (EST)
Date: Thu, 3 Apr 2003 11:54:18 -0500
From: Keith Moore <moore@cs.utk.edu>
To: John Stracke <jstracke@centive.com>
Cc: moore@cs.utk.edu, ietf@ietf.org, fredrik@packetfront.com,
        ipv6-fb@microsoft.com
Subject: v6 support (was Re: Thinking differently about the site local
 problem (was: RE: site local addresses (was Re: Fw: Welcome to the
 InterNAT...)))
Message-Id: <20030403115418.1681dd9f.moore@cs.utk.edu>
In-Reply-To: <3E8C5670.3070207@centive.com>
References: <CB7153628BD3724096258CBFD70AA8910753BD5B@red-msg-04.redmond.corp.microsoft.com>
	<3E8C2E24.19318.51AB705@localhost>
	<20030403094658.259cf9d6.moore@cs.utk.edu>
	<3E8C5670.3070207@centive.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

> >Then there's the problem that when a 800-pound gorilla ships code,
> >that code largely defines expectations for what will and will not
> >work in practice- often moreso than the standards themselves.
> >  
> >
> Strange as I feel defending Microsoft, I actually think it's
> commendable that they implemented IPv6 at all; it's not as if there's
> a lot of market demand for it yet. 

I'm certainly glad that they've done so; however most of their
competitors are shipping v6 also, and some have been doing so for
considerably longer than MS.  About the only major vendor that isn't
shipping v6 seems to be Palm (shame on them!). 



From owner-ietf@ietf.org  Thu Apr  3 15:02:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09378;
	Thu, 3 Apr 2003 15:02:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191B1k-0007xP-00
	for ietf-list@ran.ietf.org; Thu, 03 Apr 2003 15:09:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191B1Z-0007vo-00
	for ietf@ran.ietf.org; Thu, 03 Apr 2003 15:09:25 -0500
Received: from mail-pink.research.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09012
	for <ietf@ietf.org>; Thu, 3 Apr 2003 14:52:16 -0500 (EST)
Received: from bigmail.research.att.com (H-135-207-30-101.research.att.com [135.207.30.101])
	by mail-pink.research.att.com (Postfix) with ESMTP
	id 134285822E; Thu,  3 Apr 2003 14:43:18 -0500 (EST)
Received: from berkshire.research.att.com (raptor.research.att.com [135.207.23.32])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h33Jsie23627;
	Thu, 3 Apr 2003 14:54:44 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id 9EC8A7B4D; Thu,  3 Apr 2003 12:34:10 -0500 (EST)
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: Keith Moore <moore@cs.utk.edu>
Cc: John Stracke <jstracke@centive.com>, ietf@ietf.org,
        fredrik@packetfront.com, ipv6-fb@microsoft.com
Subject: Re: v6 support (was Re: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))) 
In-Reply-To: Your message of "Thu, 03 Apr 2003 11:54:18 EST."
             <20030403115418.1681dd9f.moore@cs.utk.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 03 Apr 2003 12:34:10 -0500
Message-Id: <20030403173410.9EC8A7B4D@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <20030403115418.1681dd9f.moore@cs.utk.edu>, Keith Moore writes:
>> >Then there's the problem that when a 800-pound gorilla ships code,
>> >that code largely defines expectations for what will and will not
>> >work in practice- often moreso than the standards themselves.
>> >  
>> >
>> Strange as I feel defending Microsoft, I actually think it's
>> commendable that they implemented IPv6 at all; it's not as if there's
>> a lot of market demand for it yet. 
>
>I'm certainly glad that they've done so; however most of their
>competitors are shipping v6 also, and some have been doing so for
>considerably longer than MS.  About the only major vendor that isn't
>shipping v6 seems to be Palm (shame on them!). 
>
Keith, I can't get upset about Microsoft declining to ship 
poorly-tested code.  Given how many security holes are due to buggy, 
poorly-tested programs, I applaud anyone who takes that seriously.


		--Steve Bellovin, http://www.research.att.com/~smb (me)
		http://www.wilyhacker.com (2nd edition of "Firewalls" book)





From owner-ietf@ietf.org  Thu Apr  3 15:47:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13035;
	Thu, 3 Apr 2003 15:47:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191Bo8-0000LC-00
	for ietf-list@ran.ietf.org; Thu, 03 Apr 2003 15:59:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191Bms-0000Hw-00
	for ietf@ran.ietf.org; Thu, 03 Apr 2003 15:58:18 -0500
Received: from rtp-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12747
	for <ietf@ietf.org>; Thu, 3 Apr 2003 15:41:08 -0500 (EST)
Received: from cisco.com (erosen-u10.cisco.com [161.44.134.50])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h33Kf4do010409;
	Thu, 3 Apr 2003 15:41:04 -0500 (EST)
Message-Id: <200304032041.h33Kf4do010409@rtp-core-1.cisco.com>
To: "Steven M. Bellovin" <smb@research.att.com>
cc: Keith Moore <moore@cs.utk.edu>, John Stracke <jstracke@centive.com>,
        ietf@ietf.org, fredrik@packetfront.com, ipv6-fb@microsoft.com
Subject: Re: v6 support (was Re: Thinking differently about the site local problem (was: RE: site local addresses (was Re: Fw: Welcome to the InterNAT...))) 
In-reply-to: Your message of Thu, 03 Apr 2003 12:34:10 -0500.
             <20030403173410.9EC8A7B4D@berkshire.research.att.com> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2
 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 03 Apr 2003 15:41:04 -0500
From: Eric Rosen <erosen@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


Steve> I  can't get upset  about Microsoft  declining to  ship poorly-tested
Steve> code.  Given how many security  holes are due to buggy, poorly-tested
Steve> programs, I applaud anyone who takes that seriously. 

Well, suppose they were to ship IPv6 without IPsec, on the grounds that they
didn't have the testing resources  for IPsec.  Would you still be applauding
them?  Or would you be questioning whether they have their priorities right? 

Features always fall off due to the inability to allocate sufficient testing
resources,  but a vendor  does have  some choice  over which  features those
are. 







From owner-ietf@ietf.org  Thu Apr  3 16:58:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16400;
	Thu, 3 Apr 2003 16:58:49 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191Cuy-0006vh-00
	for ietf-list@ran.ietf.org; Thu, 03 Apr 2003 17:10:44 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191CuE-0006tj-00
	for ietf@ran.ietf.org; Thu, 03 Apr 2003 17:09:58 -0500
Received: from nmh.informatik.uni-bremen.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15990
	for <ietf@ietf.org>; Thu, 3 Apr 2003 16:52:46 -0500 (EST)
Received: from tzi.org (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.12.9/8.10.1) with ESMTP id h33LtDx2025438;
	Thu, 3 Apr 2003 23:55:13 +0200 (MEST)
Date: Thu, 3 Apr 2003 23:55:12 +0200
Subject: Re: A plea for calm
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: Carsten Bormann <cabo@tzi.org>, ietf@ietf.org
To: Harald Tveit Alvestrand <harald@alvestrand.no>
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <255900000.1049352051@askvoll.hjemme.alvestrand.no>
Message-Id: <F1C805F7-661E-11D7-BA9D-00039390397C@tzi.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> One more point: An argument does not become stronger by being repeated 
> more often.
> Of the 175 senders to this list last month, 20 of us contributed more 
> than half the list traffic. If we have made our position clear, the 
> argument is, I think, stronger if it is not repeated - and silence 
> allows other voices to be heard.

Harald,

while I strongly agree with this entire message, there is also a danger 
of a "silent majority" in a mailing list.
I believe the approach cited works best with a moderator that 
periodically attempts summaries of the results of the discussion.
In WG mailing lists, this can be done by the working group chair.
It's not clear who is playing this role in this list.
(And I'm not trying to imply you should.)

Gruesse, Carsten




From owner-ietf@ietf.org  Fri Apr  4 04:37:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12326;
	Fri, 4 Apr 2003 04:37:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191Ndg-0007Pt-00
	for ietf-list@ran.ietf.org; Fri, 04 Apr 2003 04:37:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191Nd1-0007O7-00
	for ietf@ran.ietf.org; Fri, 04 Apr 2003 04:36:55 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11895
	for <ietf@ietf.org>; Fri, 4 Apr 2003 04:19:33 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 20E9B625A0; Fri,  4 Apr 2003 11:22:02 +0200 (CEST)
Date: Fri, 04 Apr 2003 11:22:02 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Carsten Bormann <cabo@tzi.org>
Cc: ietf@ietf.org
Subject: A modertor for the IETF list? (Re: A plea for calm)
Message-ID: <335590000.1049448122@askvoll.hjemme.alvestrand.no>
In-Reply-To: <F1C805F7-661E-11D7-BA9D-00039390397C@tzi.org>
References:  <F1C805F7-661E-11D7-BA9D-00039390397C@tzi.org>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Carsten,

you seem to suggest that we should get someone to act as "secretary" for 
debates on the IETF list - now that's a novel and interesting concept!

(I've seen "moderator" used in 2 ways - the "summarize and state consensus" 
role Carsten mentions below, and the "sanction inappropriate behaviour" 
role that is commonly used with "mailing list moderator" - these roles 
don't have to be done by the same person....)

Two questions for the community:

- Is this a good idea?
- Does the person exist who could do a good job and is willing to do it?

Food for thought indeed!

                  Harald


--On torsdag, april 03, 2003 23:55:12 +0200 Carsten Bormann <cabo@tzi.org> 
wrote:

>> One more point: An argument does not become stronger by being repeated
>> more often.
>> Of the 175 senders to this list last month, 20 of us contributed more
>> than half the list traffic. If we have made our position clear, the
>> argument is, I think, stronger if it is not repeated - and silence
>> allows other voices to be heard.
>
> Harald,
>
> while I strongly agree with this entire message, there is also a danger
> of a "silent majority" in a mailing list. I believe the approach cited
> works best with a moderator that periodically attempts summaries of the
> results of the discussion. In WG mailing lists, this can be done by the
> working group chair. It's not clear who is playing this role in this list.
> (And I'm not trying to imply you should.)
>
> Gruesse, Carsten
>
>





From owner-ietf@ietf.org  Fri Apr  4 05:24:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12325;
	Fri, 4 Apr 2003 04:37:31 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191NYq-0007Gi-00
	for ietf-list@ran.ietf.org; Fri, 04 Apr 2003 04:32:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191NYd-0007Ex-00
	for ietf@ran.ietf.org; Fri, 04 Apr 2003 04:32:23 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11859
	for <ietf@ietf.org>; Fri, 4 Apr 2003 04:14:58 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 9D165625A0; Fri,  4 Apr 2003 11:17:27 +0200 (CEST)
Date: Fri, 04 Apr 2003 11:17:27 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: Chastisement (A plea for calm)
Message-ID: <334900000.1049447847@askvoll.hjemme.alvestrand.no>
In-Reply-To: <Pine.LNX.4.44.0304031845070.32357-100000@commander.av8.net>
References:  <Pine.LNX.4.44.0304031845070.32357-100000@commander.av8.net>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dean,

if you really want me to pursue this topic, raise a process complaint.
Note that:

- The namedroppers issue has been dealt with extensively before.
- The DNSOPS list is not moderated.
- Since you asked, I have scanned both your comments and Rob's comments on 
DNSOP; by my count, you repeated the same argument with no additional 
information in approximately 12 out of the 35 messages you sent to the list 
over the last month.

For anyone who wants to check:

The list archive is at http://www.cafax.se/dnsop/maillist/
Rob's note to you is at 
http://www.cafax.se/dnsop/maillist/2003-04/msg00002.html

               Harald


--On torsdag, april 03, 2003 19:01:26 -0500 Dean Anderson <dean@av8.com> 
wrote:

> Sometimes the moderator has their own axe to grind.
>
> This has happened with Dan Bernstein on namedroppers to the extent where
> his address was posted for unauthorized unsubscriptions, his messages were
> blocked, and handled in ways that were inappropriately unique. Others have
> also experienced this. Randy Bush is a frequent abuser.
>
> I have just seen this on DNSOP, where Rob Austein asked for a discussion
> topic to stop, and then asked for the polar opposite to be re-introduced
> "from oblivion". He refused to chastise several blatant ad hominems
> containing foul language, and instead publicly chastised me without cause,
> only because I was on the opposite side.  Randy Bush was an abuser in this
> case as well. In fact, Bush only contributed ad hominems to the
> discussion.
>
> See my message to DNSOP dated Tue, 1 Apr 2003 18:55:49 -0500 (EST)
>
> Quoting myself:
>   "Instead of using your authority to bias discussion around proposals you
>    personally support, you should chastise those making ad hominem
> attacks,    or otherwise unprofessional posts, to keep discussion on a
> professional    level, and work to clarify arguments and objections, so
> that rational    decisions can be made."
>
> There is much discouragement when faced with such obvious bias toward
> leader's personal pet projects, and the failure to police the abuse of
> "chums" in the leadership.
>
> 		--Dean




From owner-ietf@ietf.org  Fri Apr  4 07:40:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19788;
	Fri, 4 Apr 2003 07:40:57 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191Qbx-0008P6-00
	for ietf-list@ran.ietf.org; Fri, 04 Apr 2003 07:48:01 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191QHb-0002LH-00
	for ietf@ran.ietf.org; Fri, 04 Apr 2003 07:26:59 -0500
Received: from web10904.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA18114
	for <ietf@ietf.org>; Fri, 4 Apr 2003 07:09:38 -0500 (EST)
Message-ID: <20030404121208.68882.qmail@web10904.mail.yahoo.com>
Received: from [12.237.229.250] by web10904.mail.yahoo.com via HTTP; Fri, 04 Apr 2003 04:12:08 PST
Date: Fri, 4 Apr 2003 04:12:08 -0800 (PST)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Re: A modertor for the IETF list? (Re: A plea for calm)
To: ietf@ietf.org
In-Reply-To: <335590000.1049448122@askvoll.hjemme.alvestrand.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Dear Harald,

No, the person you're describing does not exist (for the entire
ietf general mailing list), it's a challenge for people to
summarize working group mailing list threads!

BUT ...

A more scalable request might be 

"does the person exist who would recognize a thread that is
active and repetitive, who could post a REQUEST for someone to
summarize, and 

does the person exist who is willing to summarize a specific
thread that is (1) of interest to the summarizer, and (2) in
danger of ratholing unproductively with no resolution?"

I think this is more likely to be realistic (I don't even read
the uncensored IETF list, much less have time to write the
summary for all active threads, but I bet someone would be
willing to summarize site-local to make it go away/back to the
IPV6 list!)

And, yes, making threads either resolve or go away from the IETF
list is definitely a good thing. I used to be surprised at the
number of active participants who don't subscribe to the IETF
list; honestly, I'm more surprised these days at the number of
people who DO subscribe! and anything that makes it easier for
us to have multi-WG and even multi-area discussions is A Good
Thing.

Spencer

--- Harald Tveit Alvestrand <harald@alvestrand.no> wrote:
> Carsten,
> 
> you seem to suggest that we should get someone to act as
> "secretary" for 
> debates on the IETF list - now that's a novel and interesting
> concept!
> 
> (I've seen "moderator" used in 2 ways - the "summarize and
> state consensus" 
> role Carsten mentions below, and the "sanction inappropriate
> behaviour" 
> role that is commonly used with "mailing list moderator" -
> these roles 
> don't have to be done by the same person....)
> 
> Two questions for the community:
> 
> - Is this a good idea?
> - Does the person exist who could do a good job and is willing
> to do it?
> 
> Food for thought indeed!
> 
>                   Harald



From owner-ietf@ietf.org  Fri Apr  4 07:41:05 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19823;
	Fri, 4 Apr 2003 07:41:05 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191Qc1-0008Qo-00
	for ietf-list@ran.ietf.org; Fri, 04 Apr 2003 07:48:05 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191QMv-0003gY-00
	for ietf@ran.ietf.org; Fri, 04 Apr 2003 07:32:29 -0500
Received: from nmh.informatik.uni-bremen.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18418
	for <ietf@ietf.org>; Fri, 4 Apr 2003 07:15:08 -0500 (EST)
Received: from tzi.org (IDENT:eahZ8yGoA1wvFcNktfu527WyIxuCtfq4@roman.informatik.uni-bremen.de [134.102.218.120])
	by nmh.informatik.uni-bremen.de (8.12.9/8.10.1) with ESMTP id h34CHaYP027309;
	Fri, 4 Apr 2003 14:17:36 +0200 (MEST)
Date: Fri, 4 Apr 2003 12:52:29 +0200
Subject: Re: A modertor for the IETF list? (Re: A plea for calm)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: Carsten Bormann <cabo@tzi.org>, ietf@ietf.org
To: Harald Tveit Alvestrand <harald@alvestrand.no>
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <335590000.1049448122@askvoll.hjemme.alvestrand.no>
Message-Id: <87990EC3-668B-11D7-BA9D-00039390397C@tzi.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> (I've seen "moderator" used in 2 ways - the "summarize and state 
> consensus" role Carsten mentions below, and the "sanction 
> inappropriate behaviour" role that is commonly used with "mailing list 
> moderator" - these roles don't have to be done by the same person....)

Ah, words.

Moderator in the sense of "control rod in a nuclear power station" 
(i.e., your second meaning) -- this is something the IETF chair has the 
authority to do, and has done in the past.  (You may of course choose 
to delegate some of this work.)

Given the prevalence of the mailing list moderator concept on the net, 
we may need a different term for "role that facilitates generating 
consensus", which is often called moderator in meeting management.  
Secretary somehow implies "administrative assistant", at least to my 
cultural background, unless it's called "secretary general" or such 
(somehow Kofi Annan comes to mind as a good example of such a 
moderator, but this example may be lost on US/UK people at the moment). 
  "Facilitator" may focus too much on making things possible, but at 
least it's not taken yet on the net.

If we want the latter role, I believe it needs to be somebody the IETF 
would be comfortable to have in the IAB (though not necessarily a 
[current] IAB member).
I also believe this role is best separated from the first role, 
although this may vary with the topic at hand.
All of this, of course assumes that we do have useful discussion on the 
IETF list, which has not happened too often in the recent past, but 
could increase with the establishment of this role.

Gruesse, Carsten




From owner-ietf@ietf.org  Fri Apr  4 09:57:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24074;
	Fri, 4 Apr 2003 09:57:56 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191Sm7-0001LL-00
	for ietf-list@ran.ietf.org; Fri, 04 Apr 2003 10:06:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191Ewv-00018H-00
	for ietf@ran.ietf.org; Thu, 03 Apr 2003 19:20:53 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20841
	for <ietf@ietf.org>; Thu, 3 Apr 2003 19:03:42 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA18538;
	Thu, 3 Apr 2003 19:01:26 -0500
Date: Thu, 3 Apr 2003 19:01:26 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Carsten Bormann <cabo@tzi.org>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>
Subject: Re: A plea for calm
In-Reply-To: <F1C805F7-661E-11D7-BA9D-00039390397C@tzi.org>
Message-ID: <Pine.LNX.4.44.0304031845070.32357-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Sometimes the moderator has their own axe to grind.

This has happened with Dan Bernstein on namedroppers to the extent where
his address was posted for unauthorized unsubscriptions, his messages were
blocked, and handled in ways that were inappropriately unique. Others have
also experienced this. Randy Bush is a frequent abuser.

I have just seen this on DNSOP, where Rob Austein asked for a discussion
topic to stop, and then asked for the polar opposite to be re-introduced
"from oblivion". He refused to chastise several blatant ad hominems
containing foul language, and instead publicly chastised me without cause,
only because I was on the opposite side.  Randy Bush was an abuser in this
case as well. In fact, Bush only contributed ad hominems to the
discussion.

See my message to DNSOP dated Tue, 1 Apr 2003 18:55:49 -0500 (EST)

Quoting myself:
  "Instead of using your authority to bias discussion around proposals you
   personally support, you should chastise those making ad hominem attacks,
   or otherwise unprofessional posts, to keep discussion on a professional
   level, and work to clarify arguments and objections, so that rational
   decisions can be made."

There is much discouragement when faced with such obvious bias toward
leader's personal pet projects, and the failure to police the abuse of
"chums" in the leadership.

		--Dean


On Thu, 3 Apr 2003, Carsten Bormann wrote:

> > One more point: An argument does not become stronger by being repeated
> > more often.
> > Of the 175 senders to this list last month, 20 of us contributed more
> > than half the list traffic. If we have made our position clear, the
> > argument is, I think, stronger if it is not repeated - and silence
> > allows other voices to be heard.
>
> Harald,
>
> while I strongly agree with this entire message, there is also a danger
> of a "silent majority" in a mailing list.
> I believe the approach cited works best with a moderator that
> periodically attempts summaries of the results of the discussion.
> In WG mailing lists, this can be done by the working group chair.
> It's not clear who is playing this role in this list.
> (And I'm not trying to imply you should.)
>
> Gruesse, Carsten
>
>
>








From owner-ietf@ietf.org  Fri Apr  4 17:06:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09992;
	Fri, 4 Apr 2003 17:06:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191ZRK-0006Pu-00
	for ietf-list@ran.ietf.org; Fri, 04 Apr 2003 17:13:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191ZOX-0006Ff-00
	for ietf@ran.ietf.org; Fri, 04 Apr 2003 17:10:45 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09454
	for <ietf@ietf.org>; Fri, 4 Apr 2003 16:53:20 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id QAA23895;
	Fri, 4 Apr 2003 16:54:50 -0500
Date: Fri, 4 Apr 2003 16:54:51 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: Chastisement (A plea for calm)
In-Reply-To: <334900000.1049447847@askvoll.hjemme.alvestrand.no>
Message-ID: <Pine.LNX.4.44.0304041654330.19441-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Which 12 were repeated?

		--Dean

On Fri, 4 Apr 2003, Harald Tveit Alvestrand wrote:

> Dean,
>
> if you really want me to pursue this topic, raise a process complaint.
> Note that:
>
> - The namedroppers issue has been dealt with extensively before.
> - The DNSOPS list is not moderated.
> - Since you asked, I have scanned both your comments and Rob's comments on
> DNSOP; by my count, you repeated the same argument with no additional
> information in approximately 12 out of the 35 messages you sent to the list
> over the last month.
>
> For anyone who wants to check:
>
> The list archive is at http://www.cafax.se/dnsop/maillist/
> Rob's note to you is at
> http://www.cafax.se/dnsop/maillist/2003-04/msg00002.html
>
>                Harald
>
>
> --On torsdag, april 03, 2003 19:01:26 -0500 Dean Anderson <dean@av8.com>
> wrote:
>
> > Sometimes the moderator has their own axe to grind.
> >
> > This has happened with Dan Bernstein on namedroppers to the extent where
> > his address was posted for unauthorized unsubscriptions, his messages were
> > blocked, and handled in ways that were inappropriately unique. Others have
> > also experienced this. Randy Bush is a frequent abuser.
> >
> > I have just seen this on DNSOP, where Rob Austein asked for a discussion
> > topic to stop, and then asked for the polar opposite to be re-introduced
> > "from oblivion". He refused to chastise several blatant ad hominems
> > containing foul language, and instead publicly chastised me without cause,
> > only because I was on the opposite side.  Randy Bush was an abuser in this
> > case as well. In fact, Bush only contributed ad hominems to the
> > discussion.
> >
> > See my message to DNSOP dated Tue, 1 Apr 2003 18:55:49 -0500 (EST)
> >
> > Quoting myself:
> >   "Instead of using your authority to bias discussion around proposals you
> >    personally support, you should chastise those making ad hominem
> > attacks,    or otherwise unprofessional posts, to keep discussion on a
> > professional    level, and work to clarify arguments and objections, so
> > that rational    decisions can be made."
> >
> > There is much discouragement when faced with such obvious bias toward
> > leader's personal pet projects, and the failure to police the abuse of
> > "chums" in the leadership.
> >
> > 		--Dean
>
>




From owner-ietf@ietf.org  Fri Apr  4 17:35:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10664;
	Fri, 4 Apr 2003 17:35:56 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191ZwO-0000Wb-00
	for ietf-list@ran.ietf.org; Fri, 04 Apr 2003 17:45:44 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191ZrX-00009s-00
	for ietf@ran.ietf.org; Fri, 04 Apr 2003 17:40:43 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10472
	for <ietf@ietf.org>; Fri, 4 Apr 2003 17:23:17 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA30245;
	Fri, 4 Apr 2003 17:24:06 -0500
Date: Fri, 4 Apr 2003 17:23:59 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: Chastisement (A plea for calm)
In-Reply-To: <334900000.1049447847@askvoll.hjemme.alvestrand.no>
Message-ID: <Pine.LNX.4.44.0304041708050.19441-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 4 Apr 2003, Harald Tveit Alvestrand wrote:

> Dean,
>
> if you really want me to pursue this topic, raise a process complaint.

Where is the procedure for that?

> Note that:
>
> - The namedroppers issue has been dealt with extensively before.

Yes, there has been previous problems, and changes to the administration
of namedroppers as a result. However, the previous alterations have been
unsuccessful at stopping the abuse of Dan Bernstein by Randy Bush. The
most recent new complaints involving Dan Bernstein and Randy Bush have not
yet been dealt with.

> - The DNSOPS list is not moderated.

It is not moderated, however the chairs should not be permitting or
encouraging personal attacks, foul language, and unprofessional behavior,
while chastising professional behavior, in order to promote their pet
projects.

> The list archive is at http://www.cafax.se/dnsop/maillist/
> Rob's note to you is at
> http://www.cafax.se/dnsop/maillist/2003-04/msg00002.html

And one should also look at

My response to Rob, asking him to clarify his complaint:
http://www.cafax.se/dnsop/maillist/2003-04/msg00003.html

Rob's response, indicating his charges of "loaded terminology":
http://www.cafax.se/dnsop/maillist/2003-04/msg00004.html

My response, refuting Rob's charges, and detailing his own inappropriate
behavior: http://www.cafax.se/dnsop/maillist/2003-04/msg00012.html





From owner-ietf@ietf.org  Sat Apr  5 11:30:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10287;
	Sat, 5 Apr 2003 11:30:52 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191qHU-0002ym-00
	for ietf-list@ran.ietf.org; Sat, 05 Apr 2003 11:12:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191qGm-0002wn-00
	for ietf@ran.ietf.org; Sat, 05 Apr 2003 11:11:52 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09629
	for <ietf@ietf.org>; Sat, 5 Apr 2003 10:54:16 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 6E8BC621FB; Sat,  5 Apr 2003 17:56:46 +0200 (CEST)
Date: Sat, 05 Apr 2003 17:56:46 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: Chastisement (A plea for calm)
Message-ID: <442880000.1049558206@askvoll.hjemme.alvestrand.no>
In-Reply-To: <Pine.LNX.4.44.0304041708050.19441-100000@commander.av8.net>
References:  <Pine.LNX.4.44.0304041708050.19441-100000@commander.av8.net>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On fredag, april 04, 2003 17:23:59 -0500 Dean Anderson <dean@av8.com> 
wrote:

> On Fri, 4 Apr 2003, Harald Tveit Alvestrand wrote:
>
>> Dean,
>>
>> if you really want me to pursue this topic, raise a process complaint.
>
> Where is the procedure for that?

RFC 2026 section 6.5





From owner-ietf@ietf.org  Sat Apr  5 11:30:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10288;
	Sat, 5 Apr 2003 11:30:52 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 191qdk-0003iU-00
	for ietf-list@ran.ietf.org; Sat, 05 Apr 2003 11:35:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 191qcy-0003eD-00
	for ietf@ran.ietf.org; Sat, 05 Apr 2003 11:34:48 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09994
	for <ietf@ietf.org>; Sat, 5 Apr 2003 11:17:12 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 31DEC621FB; Sat,  5 Apr 2003 18:19:42 +0200 (CEST)
Date: Sat, 05 Apr 2003 18:19:42 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: Chastisement (A plea for calm)
Message-ID: <445410000.1049559582@askvoll.hjemme.alvestrand.no>
In-Reply-To: <Pine.LNX.4.44.0304041654330.19441-100000@commander.av8.net>
References:  <Pine.LNX.4.44.0304041654330.19441-100000@commander.av8.net>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On fredag, april 04, 2003 16:54:51 -0500 Dean Anderson <dean@av8.com> 
wrote:

> Which 12 were repeated?
>
The following essentially tell me nothing more than "as I have said before, 
I think reverse mapping in the DNS is useless".

http://www.cafax.se/dnsop/maillist/2003-04/msg00027.html
http://www.cafax.se/dnsop/maillist/2003-04/msg00000.html
http://www.cafax.se/dnsop/maillist/2003-04/msg00001.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00147.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00144.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00142.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00140.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00129.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00128.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00122.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00113.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00098.html

This goes back to March 19.

slightly more informative messages from you in the same debate, which I did 
not count among the 12 repeats:

http://www.cafax.se/dnsop/maillist/2003-04/msg00052.html
http://www.cafax.se/dnsop/maillist/2003-04/msg00051.html
http://www.cafax.se/dnsop/maillist/2003-04/msg00049.html
http://www.cafax.se/dnsop/maillist/2003-04/msg00046.html
http://www.cafax.se/dnsop/maillist/2003-04/msg00031.html
http://www.cafax.se/dnsop/maillist/2003-04/msg00003.html
http://www.cafax.se/dnsop/maillist/2003-04/msg00019.html
http://www.cafax.se/dnsop/maillist/2003-04/msg00014.html
http://www.cafax.se/dnsop/maillist/2003-04/msg00012.html
http://www.cafax.se/dnsop/maillist/2003-04/msg00011.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00196.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00194.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00184.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00180.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00170.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00163.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00158.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00155.html
http://www.cafax.se/dnsop/maillist/2003-03/msg00146.html

(at this point, I did not bother copying any more URLs, so you may have 
made more arguments that I did not count as repeats before March 22)

                         Harald



From owner-ietf@ietf.org  Sun Apr  6 19:57:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09901;
	Sun, 6 Apr 2003 19:57:56 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 192Jqi-0000bU-00
	for ietf-list@ran.ietf.org; Sun, 06 Apr 2003 19:46:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 192Jnl-0000XP-00
	for ietf@ran.ietf.org; Sun, 06 Apr 2003 19:43:53 -0400
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09447
	for <ietf@ietf.org>; Sun, 6 Apr 2003 19:25:52 -0400 (EDT)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h36NRx811865;
	Sun, 6 Apr 2003 16:28:00 -0700
Date: Sat, 5 Apr 2003 15:00:08 -0800
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/4) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <1671533294.20030405150008@brandenburg.com>
To: Carsten Bormann <cabo@tzi.org>
CC: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: A plea for calm
In-Reply-To: <F1C805F7-661E-11D7-BA9D-00039390397C@tzi.org>
References: <F1C805F7-661E-11D7-BA9D-00039390397C@tzi.org>
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

Carsten,

CB>  there is also a danger
CB> of a "silent majority" in a mailing list.

1.  the IETF is based on active participation.  if a person does not
express their views, the views do not count.  literally does not count.

one might wish the ietf were conducted on a different basis, such as
ensuring that each participant were individually queried.  however
that is not the ietf culture and the culture has had notable success.

so the real responsibility for being heard rests with the participant.

in other words, in the ietf, "silent majority" is an oxymoron.


now, having said that...

CB> I believe the approach cited works best with a moderator that 
CB> periodically attempts summaries of the results of the discussion.

2,  you are absolutely correct.  it is key for consensus to be
assessed explicitly.  there are many ways to do it, but it relies on an
"event" taking place in which the assessment is done, or is at least
claimed.

after everyone has had there say, it is important to have the
collection of statements summarized and rough consensus evaluated.
d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Mon Apr  7 17:25:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06362;
	Mon, 7 Apr 2003 17:25:05 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 192eDI-0004C5-00
	for ietf-list@ran.ietf.org; Mon, 07 Apr 2003 17:31:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 192eDD-0004BE-00
	for ietf@ran.ietf.org; Mon, 07 Apr 2003 17:31:31 -0400
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06172
	for <ietf@ietf.org>; Mon, 7 Apr 2003 17:13:22 -0400 (EDT)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA04949;
	Mon, 7 Apr 2003 17:12:20 -0400
Date: Mon, 7 Apr 2003 17:12:25 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: Chastisement (A plea for calm)
In-Reply-To: <445410000.1049559582@askvoll.hjemme.alvestrand.no>
Message-ID: <Pine.LNX.4.44.0304071646070.19441-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 5 Apr 2003, Harald Tveit Alvestrand wrote:
> > Which 12 were repeated?
> >
> The following essentially tell me nothing more than "as I have said before,
> I think reverse mapping in the DNS is useless".

Actually, the messages contain explanations of why various theories about
the dependability of reverse mapping can't be relied on, and other schemes
which were brought up to show its usefulness. Many such schemes were
brought up, and refuted. That doesn't make the refutations
repetitive--though one might wonder why people keep proposing schemes that
aren't really substantially different. Suppressing the refutations doesn't
make such schemes any more workable.  However, as was also shown, Rob
Austein has a history of promoting the use of reverse for authentication,
and in doing so, participated in causing the BSD r-command exploits, and
the myth of open-relay abuse, and other problems which trace themselves to
inappropriate trust placed in in-addr.  Rob doesn't seem to have learned
much from these experiences, and continues to promote the same position he
held in 1986.

I don't think you understood the messages, or the issues being complained
about: Neither Rob's complaint, nor my complaint.  Perhaps you could take
some more time to investigate and fully understand the issues.

> http://www.cafax.se/dnsop/maillist/2003-04/msg00027.html
The message above is unique. It offers a new statement for the
in-addr-required draft, after the issue was restarted inappropriately by
Rob Austein.  According to Rob, the in-addr-required draft is a "new
topic" unrelated to the previous topic of dropping support for reverse.
(This is in my complaint, which it seems you haven't read.)

> http://www.cafax.se/dnsop/maillist/2003-04/msg00000.html
The message above is a complaint that Rob re-started the debate with a new
angle--It is not a repetition.  You will note that 27 messages were made
on the list between these posts.

The remaining messages do not need to be individually addressed.

		--Dean




From owner-ietf@ietf.org  Tue Apr  8 17:59:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04066;
	Tue, 8 Apr 2003 17:59:54 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1931Gi-0006al-00
	for ietf-list@ran.ietf.org; Tue, 08 Apr 2003 18:08:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1931GY-0006Z5-00
	for ietf@ran.ietf.org; Tue, 08 Apr 2003 18:08:30 -0400
Received: from tomts5-srv.bellnexxia.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03681
	for <ietf@ietf.org>; Tue, 8 Apr 2003 17:50:05 -0400 (EDT)
Received: from ORANO5 ([64.229.53.104]) by tomts5-srv.bellnexxia.net
          (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with SMTP
          id <20030408215237.MJDS1594.tomts5-srv.bellnexxia.net@ORANO5>
          for <ietf@ietf.org>; Tue, 8 Apr 2003 17:52:37 -0400
Message-ID: <015301c2fe19$207f5b10$3701090a@ORANO5>
From: "Peering" <peering@orano.on.ca>
To: <ietf@ietf.org>
Subject: BGP Black hole Community
Date: Tue, 8 Apr 2003 17:52:19 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

These days Remote trigger black hole routing is a very hot issue and each
provider is configuring the network individually. This technique is used to
mitigate the Denial of Service (DoS) Attack. We are also using this
technique and providing this service only to our customers. So if a customer
advertise prefix attached with a special community (for example ASN:9999)
then we take the following actions:

- Set the next hop IP for this prefix to 192.0.2.1

- Already configured static route for 192.0.2.0/24 and the next hop is set
to Null0

  ip route 192.0.2.0 255.255.255.0 null0

- Null0 interface is already configured to not acknowledge ICMP packets.

    interface null0
     no ip unreachable

- Advertise this prefix to all other routers inside our backbone.

Each Service provider has defined their own community for this purpose (due
to the unavailability of a well known community). Few service providers are
trying to exchange this community from other peering members other than
customers.

I think we should have a well known community attribute for this purpose,
for example "DISCARD". This community attribute could be additive with other
exisiting well known communities (NOEXPORT, NOADVERTISE and INTERNET) to
control the advertisment of the prefix.

Even though, this is never explicitly mentioned that  well-known communities
trigger actions in BGP without further user configuration, we may or may not
choose  to set an action for this community. An action could be defined to
discard the traffic.

As I mentioned above this new community could be used with other well known
communites. For example if DISCARD and NOEXPORT  attached with a prefix, it
means the traffic destined for that prefix will be discarded locally on that
router and will not get advertised to any External BGP peer.

Comments ??????

Cheers,
Shahid Ajaz




From owner-ietf@ietf.org  Tue Apr  8 18:33:53 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06560;
	Tue, 8 Apr 2003 18:33:53 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1931sQ-00069j-00
	for ietf-list@ran.ietf.org; Tue, 08 Apr 2003 18:47:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1931rk-00067f-00
	for ietf@ran.ietf.org; Tue, 08 Apr 2003 18:46:56 -0400
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06434
	for <ietf@ietf.org>; Tue, 8 Apr 2003 18:28:30 -0400 (EDT)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id SAA28935;
	Tue, 8 Apr 2003 18:26:30 -0400
Date: Tue, 8 Apr 2003 18:26:36 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Peering <peering@orano.on.ca>
cc: ietf@ietf.org
Subject: Re: BGP Black hole Community
In-Reply-To: <015301c2fe19$207f5b10$3701090a@ORANO5>
Message-ID: <Pine.LNX.4.44.0304081825440.27097-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

How do you prevent this from being used as a DOS attack by itself?

		--Dean

On Tue, 8 Apr 2003, Peering wrote:

> These days Remote trigger black hole routing is a very hot issue and each
> provider is configuring the network individually. This technique is used to
> mitigate the Denial of Service (DoS) Attack. We are also using this
> technique and providing this service only to our customers. So if a customer
> advertise prefix attached with a special community (for example ASN:9999)
> then we take the following actions:
>
> - Set the next hop IP for this prefix to 192.0.2.1
>
> - Already configured static route for 192.0.2.0/24 and the next hop is set
> to Null0
>
>   ip route 192.0.2.0 255.255.255.0 null0
>
> - Null0 interface is already configured to not acknowledge ICMP packets.
>
>     interface null0
>      no ip unreachable
>
> - Advertise this prefix to all other routers inside our backbone.
>
> Each Service provider has defined their own community for this purpose (due
> to the unavailability of a well known community). Few service providers are
> trying to exchange this community from other peering members other than
> customers.
>
> I think we should have a well known community attribute for this purpose,
> for example "DISCARD". This community attribute could be additive with other
> exisiting well known communities (NOEXPORT, NOADVERTISE and INTERNET) to
> control the advertisment of the prefix.
>
> Even though, this is never explicitly mentioned that  well-known communities
> trigger actions in BGP without further user configuration, we may or may not
> choose  to set an action for this community. An action could be defined to
> discard the traffic.
>
> As I mentioned above this new community could be used with other well known
> communites. For example if DISCARD and NOEXPORT  attached with a prefix, it
> means the traffic destined for that prefix will be discarded locally on that
> router and will not get advertised to any External BGP peer.
>
> Comments ??????
>
> Cheers,
> Shahid Ajaz
>
>
>




From owner-ietf@ietf.org  Tue Apr  8 20:33:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09616;
	Tue, 8 Apr 2003 20:33:42 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1933hm-0001yC-00
	for ietf-list@ran.ietf.org; Tue, 08 Apr 2003 20:44:46 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1933hR-0001wY-00
	for ietf@ran.ietf.org; Tue, 08 Apr 2003 20:44:25 -0400
Received: from buffoon.automagic.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA09465
	for <ietf@ietf.org>; Tue, 8 Apr 2003 20:26:00 -0400 (EDT)
Received: (qmail 14238 invoked by uid 0); 9 Apr 2003 00:28:32 -0000
Received: from localhost.automagic.org (HELO isc.org) (root@127.0.0.1)
  by localhost.automagic.org with SMTP; 9 Apr 2003 00:28:32 -0000
Date: Tue, 8 Apr 2003 20:28:40 -0400
Subject: Re: BGP Black hole Community
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Peering <peering@orano.on.ca>, ietf@ietf.org
To: Dean Anderson <dean@av8.com>
From: Joe Abley <jabley@isc.org>
In-Reply-To: <Pine.LNX.4.44.0304081825440.27097-100000@commander.av8.net>
Message-Id: <36838540-6A22-11D7-BFDC-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Tuesday, Apr 8, 2003, at 18:26 Canada/Eastern, Dean Anderson wrote:

> How do you prevent this from being used as a DOS attack by itself?

If you filter prefixes sent to your network from customers, and ensure 
that the next-hop-blackhole policy can only happen on a customer 
session, then the only DoS that can happen is by a customer on 
themselves. The utility of such a mechanism for a customer who is 
paying for delivered bandwidth is that inbound traffic directed at a 
particular customer address or netblock can be discarded before it gets 
close to the pipe over which the dollar meter runs.

Shahid: you can make this more effective in your network by configuring 
the null interface on every edge router, and not just in one place. 
That way traffic will be discarded as early as possible (you might also 
consider setting no-export on the "blackhole me" prefixes sent by 
customers to avoid accidentally leaking them to peers).

It is difficult to see how such a well-known community could be 
implemented by vendors without also specifying a well-known "discard" 
next-hop address. In the absense of any other configuration by a 
network operator, what do you propose a router should do when it 
receives a prefix with this community?


Joe




From owner-ietf@ietf.org  Wed Apr  9 09:59:05 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28091;
	Wed, 9 Apr 2003 09:59:05 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 193GFi-0005pR-00
	for ietf-list@ran.ietf.org; Wed, 09 Apr 2003 10:08:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 193GF1-0005n7-00
	for ietf@ran.ietf.org; Wed, 09 Apr 2003 10:07:55 -0400
Received: from tomts22-srv.bellnexxia.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27697
	for <ietf@ietf.org>; Wed, 9 Apr 2003 09:49:13 -0400 (EDT)
Received: from ORANO5 ([64.229.52.30]) by tomts22-srv.bellnexxia.net
          (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with SMTP
          id <20030409135146.FEOV25567.tomts22-srv.bellnexxia.net@ORANO5>;
          Wed, 9 Apr 2003 09:51:46 -0400
Message-ID: <004601c2fe9f$1d03d200$3701090a@ORANO5>
From: "Peering" <peering@orano.on.ca>
To: <ietf@ietf.org>
Cc: "Joe Abley" <jabley@isc.org>, "Dean Anderson" <dean@av8.com>
References: <36838540-6A22-11D7-BFDC-00039312C852@isc.org>
Subject: Re: BGP Black hole Community
Date: Wed, 9 Apr 2003 09:51:25 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Shahid: you can make this more effective in your network by configuring
> the null interface on every edge router, and not just in one place.

It was implicit -:)

> In the absense of any other configuration by a
> network operator, what do you propose a router should do when it
> receives a prefix with this community?

A suggested action could be this: when a prefix is received with a DISCARD
community additive to INTERNET  the router should advertise this prefix to
all of its IBGP/EBGP peers. Also, in its forwarding table the next hop for
this route should be pointed to discard bin, for example NULL0 in Cisco.

For DISCARD + NOEXPORT will be advertised to all IBGP peers only.

Although it is not mandatory to set an action with the well known community,
however, not setting an action by default this community may loose its
purpose.

As Network Operators can always manipulate action attributes.

Cheers,
Shahid Ajaz



----- Original Message -----
From: "Joe Abley" <jabley@isc.org>
To: "Dean Anderson" <dean@av8.com>
Cc: "Peering" <peering@orano.on.ca>; <ietf@ietf.org>
Sent: Tuesday, April 08, 2003 8:28 PM
Subject: Re: BGP Black hole Community


>
> On Tuesday, Apr 8, 2003, at 18:26 Canada/Eastern, Dean Anderson wrote:
>
> > How do you prevent this from being used as a DOS attack by itself?
>
> If you filter prefixes sent to your network from customers, and ensure
> that the next-hop-blackhole policy can only happen on a customer
> session, then the only DoS that can happen is by a customer on
> themselves. The utility of such a mechanism for a customer who is
> paying for delivered bandwidth is that inbound traffic directed at a
> particular customer address or netblock can be discarded before it gets
> close to the pipe over which the dollar meter runs.
>
> Shahid: you can make this more effective in your network by configuring
> the null interface on every edge router, and not just in one place.
> That way traffic will be discarded as early as possible (you might also
> consider setting no-export on the "blackhole me" prefixes sent by
> customers to avoid accidentally leaking them to peers).
>
> It is difficult to see how such a well-known community could be
> implemented by vendors without also specifying a well-known "discard"
> next-hop address. In the absense of any other configuration by a
> network operator, what do you propose a router should do when it
> receives a prefix with this community?
>
>
> Joe
>




From owner-ietf@ietf.org  Wed Apr  9 12:07:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04262;
	Wed, 9 Apr 2003 12:07:08 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 193IIU-0002aa-00
	for ietf-list@ran.ietf.org; Wed, 09 Apr 2003 12:19:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 193IHz-0002YA-00
	for ietf@ran.ietf.org; Wed, 09 Apr 2003 12:19:07 -0400
Received: from buffoon.automagic.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA03896
	for <ietf@ietf.org>; Wed, 9 Apr 2003 12:00:06 -0400 (EDT)
Received: (qmail 76459 invoked by uid 0); 9 Apr 2003 16:02:40 -0000
Received: from localhost.automagic.org (HELO isc.org) (root@127.0.0.1)
  by localhost.automagic.org with SMTP; 9 Apr 2003 16:02:40 -0000
Date: Wed, 9 Apr 2003 12:02:49 -0400
Subject: Re: BGP Black hole Community
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <ietf@ietf.org>, "Dean Anderson" <dean@av8.com>
To: "Peering" <peering@orano.on.ca>
From: Joe Abley <jabley@isc.org>
In-Reply-To: <004601c2fe9f$1d03d200$3701090a@ORANO5>
Message-Id: <B63D1B54-6AA4-11D7-BFDC-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Wednesday, Apr 9, 2003, at 09:51 Canada/Eastern, Peering wrote:

> A suggested action could be this: when a prefix is received with a 
> DISCARD
> community additive to INTERNET  the router should advertise this 
> prefix to
> all of its IBGP/EBGP peers. Also, in its forwarding table the next hop 
> for
> this route should be pointed to discard bin, for example NULL0 in 
> Cisco.
>
> For DISCARD + NOEXPORT will be advertised to all IBGP peers only.
>
> Although it is not mandatory to set an action with the well known 
> community,
> however, not setting an action by default this community may loose its
> purpose.
>
> As Network Operators can always manipulate action attributes.

If this was to be generic, well-known behaviour you would want 
additional semantics for enabling/accepting it, in order to malicious 
(or accidental) injection of DISCARD-equipped routes from peers. 
Something like disabling the functionality by default, and requiring 
explicit configuration to enable it (e.g. per EBGP session, so you 
could turn it on specifically for customer sessions).


Joe




From owner-ietf@ietf.org  Wed Apr  9 16:28:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13103;
	Wed, 9 Apr 2003 16:28:34 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 193MM6-000406-00
	for ietf-list@ran.ietf.org; Wed, 09 Apr 2003 16:39:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 193ML6-0003wh-00
	for ietf@ran.ietf.org; Wed, 09 Apr 2003 16:38:36 -0400
Received: from tomts25-srv.bellnexxia.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12880
	for <ietf@ietf.org>; Wed, 9 Apr 2003 16:19:58 -0400 (EDT)
Received: from ORANO5 ([64.229.52.30]) by tomts25-srv.bellnexxia.net
          (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with SMTP
          id <20030409202231.STJV6158.tomts25-srv.bellnexxia.net@ORANO5>
          for <ietf@ietf.org>; Wed, 9 Apr 2003 16:22:31 -0400
Message-ID: <010601c2fed5$b3494d90$3701090a@ORANO5>
From: "Peering" <peering@orano.on.ca>
To: <ietf@ietf.org>
Subject: Re: BGP Black hole Community
Date: Wed, 9 Apr 2003 16:22:10 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Joe,

> Something like disabling the functionality by default, and requiring
> explicit configuration to enable it (e.g. per EBGP session, so you
> could turn it on specifically for customer sessions).

By default it should be enabled, IMO default behaviour should be as follows:

If
 {
   Globally DISCARD is Enable
     {
        then  Per-peer = DISCARD enable (can be disabled explicitly)
       }
   }
Else
  {
    Per-peer = DISCARD Disable (can be enabled explicitly)
  }

This imposes the  least configuration changes.

If you don't want to accept DISCARD routes (for any reason) from any
specific neighbor (if DISCARD is enable globally) then simply you can define
route map for this purpose, in Cisco it will be look like that:

----------------------------------
router bgp xxx
 neighbor x.x.x.x route-map deny-discard-routes in
!
route-map deny-discard-routes deny 10
 match community 10
!
route-map deny-discard-routes permit 20
!
ip community-list 10 permit DISCARD
!
------------------------------------

It won't be any issue to configure above commands on other vendors.

-Shahid

----- Original Message -----
From: "Peering" <peering@orano.on.ca>
To: <ietf@ietf.org>
Cc: "Joe Abley" <jabley@isc.org>; "Dean Anderson" <dean@av8.com>
Sent: Wednesday, April 09, 2003 9:51 AM
Subject: Re: BGP Black hole Community


> > Shahid: you can make this more effective in your network by configuring
> > the null interface on every edge router, and not just in one place.
>
> It was implicit -:)
>
> > In the absense of any other configuration by a
> > network operator, what do you propose a router should do when it
> > receives a prefix with this community?
>
> A suggested action could be this: when a prefix is received with a DISCARD
> community additive to INTERNET  the router should advertise this prefix to
> all of its IBGP/EBGP peers. Also, in its forwarding table the next hop for
> this route should be pointed to discard bin, for example NULL0 in Cisco.
>
> For DISCARD + NOEXPORT will be advertised to all IBGP peers only.
>
> Although it is not mandatory to set an action with the well known
community,
> however, not setting an action by default this community may loose its
> purpose.
>
> As Network Operators can always manipulate action attributes.
>
> Cheers,
> Shahid Ajaz
>
>
>
> ----- Original Message -----
> From: "Joe Abley" <jabley@isc.org>
> To: "Dean Anderson" <dean@av8.com>
> Cc: "Peering" <peering@orano.on.ca>; <ietf@ietf.org>
> Sent: Tuesday, April 08, 2003 8:28 PM
> Subject: Re: BGP Black hole Community
>
>
> >
> > On Tuesday, Apr 8, 2003, at 18:26 Canada/Eastern, Dean Anderson wrote:
> >
> > > How do you prevent this from being used as a DOS attack by itself?
> >
> > If you filter prefixes sent to your network from customers, and ensure
> > that the next-hop-blackhole policy can only happen on a customer
> > session, then the only DoS that can happen is by a customer on
> > themselves. The utility of such a mechanism for a customer who is
> > paying for delivered bandwidth is that inbound traffic directed at a
> > particular customer address or netblock can be discarded before it gets
> > close to the pipe over which the dollar meter runs.
> >
> > Shahid: you can make this more effective in your network by configuring
> > the null interface on every edge router, and not just in one place.
> > That way traffic will be discarded as early as possible (you might also
> > consider setting no-export on the "blackhole me" prefixes sent by
> > customers to avoid accidentally leaking them to peers).
> >
> > It is difficult to see how such a well-known community could be
> > implemented by vendors without also specifying a well-known "discard"
> > next-hop address. In the absense of any other configuration by a
> > network operator, what do you propose a router should do when it
> > receives a prefix with this community?
> >
> >
> > Joe
> >
>




From owner-ietf@ietf.org  Wed Apr  9 16:43:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13675;
	Wed, 9 Apr 2003 16:43:44 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 193MeT-0005Br-00
	for ietf-list@ran.ietf.org; Wed, 09 Apr 2003 16:58:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 193Mdh-0005AM-00
	for ietf@ran.ietf.org; Wed, 09 Apr 2003 16:57:49 -0400
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13581
	for <ietf@ietf.org>; Wed, 9 Apr 2003 16:39:11 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h39Kf3Sf008290;
	Wed, 9 Apr 2003 16:41:03 -0400
Message-Id: <200304092041.h39Kf3Sf008290@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/02/2003 with nmh-1.0.4+dev
To: "Rasheeduddin, Tariq" <Tariq.Rasheeduddin@attcanada.com>
Cc: "'Joe Abley'" <jabley@isc.org>, Peering <peering@orano.on.ca>,
        ietf@ietf.org, Dean Anderson <dean@av8.com>
Subject: Re: BGP Black hole Community 
In-Reply-To: Your message of "Wed, 09 Apr 2003 14:19:51 MDT."
             <3D7C088D6CCFD31190A5009027D30E9102B70450@torex004.att-intra.com> 
References: <3D7C088D6CCFD31190A5009027D30E9102B70450@torex004.att-intra.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_824596200P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 09 Apr 2003 16:41:03 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_824596200P
Content-Type: text/plain; charset=us-ascii

On Wed, 09 Apr 2003 14:19:51 MDT, "Rasheeduddin, Tariq" said:
> > If this was to be generic, well-known behaviour you would want 
> > additional semantics for enabling/accepting it, in order to malicious 
> > or accidental) injection of DISCARD-equipped routes from peers. 
> 
> As the threat exists regardless to this functionality, this discussion
> should be out-of-scope.

Correct. Those who didn't learn from AS7007 (yes, AS7007 screwed up - but how
many *other* AS believed it as gospel truth?) will shoot themselves in the foot
eventually, with or without this function.



--==_Exmh_824596200P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+lIVfcC3lWbTT17ARAgP8AKCBGZyhbgtVxPNUxUwC3j/DGDdEYQCg3XLB
3P1y+8mD3fy/Xt7UL81xE9Q=
=sCLY
-----END PGP SIGNATURE-----

--==_Exmh_824596200P--



From owner-ietf@ietf.org  Wed Apr  9 16:56:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14257;
	Wed, 9 Apr 2003 16:56:06 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 193Mq7-0005x4-00
	for ietf-list@ran.ietf.org; Wed, 09 Apr 2003 17:10:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 193Mp7-0005ug-00
	for ietf@ran.ietf.org; Wed, 09 Apr 2003 17:09:37 -0400
Received: from carwash.centivinc.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA14000
	for <ietf@ietf.org>; Wed, 9 Apr 2003 16:51:00 -0400 (EDT)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003040916581317948
 for <ietf@ietf.org>; Wed, 09 Apr 2003 16:58:13 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 9 Apr 2003 16:51:20 -0400
Message-ID: <3E9487C8.6040603@centive.com>
Date: Wed, 09 Apr 2003 16:51:20 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: BGP Black hole Community
References: <3D7C088D6CCFD31190A5009027D30E9102B70450@torex004.att-intra.com> <200304092041.h39Kf3Sf008290@turing-police.cc.vt.edu>
In-Reply-To: <200304092041.h39Kf3Sf008290@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Apr 2003 20:51:20.0492 (UTC) FILETIME=[C61CA6C0:01C2FED9]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Valdis.Kletnieks@vt.edu wrote:

>Correct. Those who didn't learn from AS7007 (yes, AS7007 screwed up - but how
>many *other* AS believed it as gospel truth?) will shoot themselves in the foot
>eventually, with or without this function.
>  
>
Well, yes; but just because it's possible to shoot yourself in the foot 
doesn't mean you want to make it easy for other people to shoot you in 
the foot--which would be the effect of enabling this blackhole feature 
by default.

-- 
/============================================================\
|John Stracke      |jstracke@centive.com                     |
|Principal Engineer|http://www.centive.com                   |
|Centive           |My opinions are my own.                  |
|============================================================|
|"God does not play games with His loyal servants." "Whoo-ee,|
|where have you *been*?" --_Good Omens_                      |
\============================================================/





From owner-ietf@ietf.org  Wed Apr  9 17:15:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13102;
	Wed, 9 Apr 2003 16:28:33 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 193MK9-0003vI-00
	for ietf-list@ran.ietf.org; Wed, 09 Apr 2003 16:37:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 193MK1-0003tw-00
	for ietf@ran.ietf.org; Wed, 09 Apr 2003 16:37:29 -0400
Received: from caluxsmtp.attcanada.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12790
	for <ietf@ietf.org>; Wed, 9 Apr 2003 16:18:50 -0400 (EDT)
Received: from CALVS002.att-intra.com ([10.1.1.46])
          by caluxsmtp.attcanada.com (Post.Office MTA v3.5.3 release 223
          ID# 0-0U10L2S100V35) with SMTP id com for <ietf@ietf.org>;
          Wed, 9 Apr 2003 14:24:07 -0600
Received: FROM calex001.metronet.ca BY CALVS002.att-intra.com ; Wed Apr 09 14:21:14 2003 -0600
Received: by calex001.metronet.ca with Internet Mail Service (5.5.2653.19)
	id <2DCG84YM>; Wed, 9 Apr 2003 14:21:17 -0600
Message-ID: <3D7C088D6CCFD31190A5009027D30E9102B70450@torex004.att-intra.com>
From: "Rasheeduddin, Tariq" <Tariq.Rasheeduddin@attcanada.com>
To: "'Joe Abley'" <jabley@isc.org>, Peering <peering@orano.on.ca>
Cc: ietf@ietf.org, Dean Anderson <dean@av8.com>
Subject: RE: BGP Black hole Community
Date: Wed, 9 Apr 2003 14:19:51 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

> If this was to be generic, well-known behaviour you would want 
> additional semantics for enabling/accepting it, in order to malicious 
> or accidental) injection of DISCARD-equipped routes from peers. 

As the threat exists regardless to this functionality, this discussion
should be out-of-scope.

Tariq



From owner-ietf@ietf.org  Wed Apr  9 17:19:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15138;
	Wed, 9 Apr 2003 17:19:04 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 193NCO-0007i1-00
	for ietf-list@ran.ietf.org; Wed, 09 Apr 2003 17:33:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 193NBp-0007fv-00
	for ietf@ran.ietf.org; Wed, 09 Apr 2003 17:33:05 -0400
Received: from mail-green.research.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14987
	for <ietf@ietf.org>; Wed, 9 Apr 2003 17:14:27 -0400 (EDT)
Received: by mail-green.research.att.com (Postfix, from userid 612)
	id 69E9E1D742E; Wed,  9 Apr 2003 17:22:34 -0400 (EDT)
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-green.research.att.com (Postfix) with ESMTP
	id C7ED21D72C7; Wed,  9 Apr 2003 17:22:33 -0400 (EDT)
Received: from berkshire.research.att.com (raptor.research.att.com [135.207.23.32])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h39LH0V22643;
	Wed, 9 Apr 2003 17:17:00 -0400 (EDT)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id C0B757B4D; Wed,  9 Apr 2003 17:16:59 -0400 (EDT)
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: John Stracke <jstracke@centive.com>
Cc: ietf@ietf.org
Subject: Re: BGP Black hole Community 
In-Reply-To: Your message of "Wed, 09 Apr 2003 16:51:20 EDT."
             <3E9487C8.6040603@centive.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 09 Apr 2003 17:16:59 -0400
Message-Id: <20030409211659.C0B757B4D@berkshire.research.att.com>
X-Spam-Status: No, hits=-116.1 required=5.0
	tests=BAYES_00,EMAIL_ATTRIBUTION,IN_REP_TO,USER_IN_WHITELIST
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <3E9487C8.6040603@centive.com>, John Stracke writes:
>Valdis.Kletnieks@vt.edu wrote:
>
>>Correct. Those who didn't learn from AS7007 (yes, AS7007 screwed up - but how
>>many *other* AS believed it as gospel truth?) will shoot themselves in the fo
>ot
>>eventually, with or without this function.
>>  
>>
>Well, yes; but just because it's possible to shoot yourself in the foot 
>doesn't mean you want to make it easy for other people to shoot you in 
>the foot--which would be the effect of enabling this blackhole feature 
>by default.
>

Agreed.  The function itself is reasonable, but it should only be used 
in private by consenting adult ISPs.


		--Steve Bellovin, http://www.research.att.com/~smb (me)
		http://www.wilyhacker.com (2nd edition of "Firewalls" book)





From owner-ietf@ietf.org  Thu Apr 10 16:31:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05679;
	Thu, 10 Apr 2003 16:31:04 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 193ipd-0001vX-00
	for ietf-list@ran.ietf.org; Thu, 10 Apr 2003 16:39:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 193ip7-0001uE-00
	for ietf@ran.ietf.org; Thu, 10 Apr 2003 16:39:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05437
	for <ietf@ietf.org>; Thu, 10 Apr 2003 16:20:09 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 193iGg-00048C-00
	for ietf@ietf.org; Thu, 10 Apr 2003 16:03:30 -0400
Received: from tomts26.bellnexxia.net ([209.226.175.189] helo=tomts26-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 193iGg-000489-00
	for ietf@ietf.org; Thu, 10 Apr 2003 16:03:30 -0400
Received: from ORANO5 ([64.229.52.30]) by tomts26-srv.bellnexxia.net
          (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with SMTP
          id <20030410202242.WOPB13343.tomts26-srv.bellnexxia.net@ORANO5>
          for <ietf@ietf.org>; Thu, 10 Apr 2003 16:22:42 -0400
Message-ID: <012901c2ff9e$e37e0e00$3701090a@ORANO5>
From: "Peering" <peering@orano.on.ca>
To: <ietf@ietf.org>
References: <20030409211659.C0B757B4D@berkshire.research.att.com>
Subject: Re: BGP Black hole Community 
Date: Thu, 10 Apr 2003 16:22:20 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Agreed.  The function itself is reasonable, but it should only be used
> in private by consenting adult ISPs.

If a Network operator is not acknowledging the DISCARD community (due to any
reason) and accepting the advertisment, then simply he will forward the
traffic to the sender BGP neighbor (won't hurt anything) and the sender will
forward the traffic eventually to the discard bin. The receiving BGP
neighbor may or may not change the DISCARD community when forward the prefix
to other peers. Again, it won't be any issue.

Am I missing anything here or any threat/issue?

Obviously wherever possible, a network operator does prefix filtering
otherwise just leave open to accept everything (e.g., from Transit/ISP
link.... 125,000 routes today). As Tariq mentioned the threat exists
regardless to this functionality. For example, a peer can advertise a specif
prefix for someone else aggregate prefix without DISCARD community as
follows:

1. Prefix 2.10.0.0/16 belongs to AS#abc
2. Prefix 2.10.0.0/17 and 2.10.128.0/17 advertise from another AS#xyz (just
an attack). Is there any way to NOT accept this prefix if coming from
Transit link (without prefix filtering)? Due to longest match rule all the
traffic will forward to AS#xyz (assume 2.10.0.0/16 is the only aggregate
prefix advertisng from AS#abc).

So IMO, this new community will not create any loophole or potential threat.

If globally disabled, then what should be the default behaviour (a) Do not
accept prefix if DISCARD community is attached or (b) Do not take any action
by default (setting next hop for those prefix to discard bin)?

We could define a set of rules to use this community properly (like today's
Inetnet network, an external peer normally accept /24 or smaller prefix).




From owner-ietf@ietf.org  Fri Apr 11 03:54:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02767;
	Fri, 11 Apr 2003 03:54:26 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 193tWW-0000zd-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 04:04:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 193tVz-0000yb-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 04:04:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02535
	for <ietf@ietf.org>; Fri, 11 Apr 2003 03:45:03 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 193sxV-0007cA-00
	for ietf@ietf.org; Fri, 11 Apr 2003 03:28:25 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 193sxU-0007c6-00
	for ietf@ietf.org; Fri, 11 Apr 2003 03:28:24 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 2AD3D621FB; Fri, 11 Apr 2003 09:47:08 +0200 (CEST)
Date: Fri, 11 Apr 2003 09:47:08 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: poised@lists.tislabs.com, ietf@ietf.org
Subject: I-D ACTION:draft-iesg-charter-02.txt (fwd)
Message-ID: <936220000.1050047228@askvoll.hjemme.alvestrand.no>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="==========1656105387=========="
Sender: owner-ietf@ietf.org
Precedence: bulk

--==========1656105387==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Another version is ready for your comments and criticisms.

Important changes based on the discussion:

- Clarified liaison positions on IESG
- Added a lot more words on IESG decision procedures
- Added another discussion about privacy of IESG conversations (as opposed 
to IESG decisions, which are public)
- Added an acknowledgements section (woefully incomplete, as usual)
- Added an "intended status" para saying that this goes for Info, not BCP
- Added a description of "responsible AD" for documents in general
  (this is borderline to "procedure", but got mentioned many times)
- Lots of small wording changes.

Important non-changes:

- Did not add a change log..... sorry... if someone wants to review the 500 
lines of diff of the XML, I can send that....

as usual, discussion of details on the poised mailing list; if you want to 
discuss issues that have wider policy implications, it's possible to use 
the ietf list for a wider audience.

Have fun!

                  Harald


---------- Forwarded Message ----------
Date: torsdag, april 10, 2003 07:53:39 -0400
From: Internet-Drafts@ietf.org
To: IETF-Announce
Cc: iesg@ietf.org
Subject: I-D ACTION:draft-iesg-charter-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories. This draft is a work item of the Internet Engineering Steering
Group Working Group of the IETF.

	Title		: An IESG charter
	Author(s)	: H. Alvestrand
	Filename	: draft-iesg-charter-02.txt
	Pages		: 17
	Date		: 2003-4-9
	
This memo gives a charter for the Internet Engineering Steering Group
(IESG), a management function of the Internet Engineering Task Force
(IETF).
It is meant to document the charter of the IESG as presently
understood.
Discussion of this memo is encouraged on the POISED mailing list
<poised@lists.tislabs.com>
STATUS NOTE (to be removed from RFC):
This document is intended for publication as an Informational
document, detailing the instructions to the IESG that the IESG thinks
it has been operating under.  It does not claim to represent
consensus of the IETF that this is the right set of instructions to
the IESG.  At this time (spring 2003), the structure of the IETF is
undergoing reevaluation, and the result is likely to include changes
to the IESG's role; spending time to get IETF consensus that this
document represents the IETF consensus on what the IESG should do,
which a BCP publication would indicate, seems like a less than useful
exercise.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-iesg-charter-02.txt

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-iesg-charter-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-iesg-charter-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

---------- End Forwarded Message ----------


--==========1656105387==========
Content-Type: message/rfc822; name="I-D ACTION:draft-iesg-charter-02.txt"

Return-Path: <iesg-admin@ietf.org>
Received: from eikenes.alvestrand.no ([unix socket])
	by eikenes.alvestrand.no (Cyrus v2.1.11-Mandrake-RPM-2.1.11-1mdk) with LMTP; Thu, 10 Apr 2003 13:58:32 +0200
X-Sieve: CMU Sieve 2.2
Received: from www1.ietf.org (ietf.org [132.151.1.19])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 5471362207
	for <Harald@alvestrand.no>; Thu, 10 Apr 2003 13:58:32 +0200 (CEST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3AC21803196;
	Thu, 10 Apr 2003 08:02:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3ABxo803079
	for <iesg@optimus.ietf.org>; Thu, 10 Apr 2003 07:59:50 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15946;
	Thu, 10 Apr 2003 07:53:39 -0400 (EDT)
Message-Id: <200304101153.HAA15946@ietf.org>
To: IETF-Announce: ;
Cc: iesg@ietf.org
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-iesg-charter-02.txt
Date: Thu, 10 Apr 2003 07:53:39 -0400
Sender: iesg-admin@ietf.org
Errors-To: iesg-admin@ietf.org
X-BeenThere: iesg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/iesg>,
	<mailto:iesg-request@ietf.org?subject=unsubscribe>
List-Id: <iesg.ietf.org>
List-Post: <mailto:iesg@ietf.org>
List-Help: <mailto:iesg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/iesg>,
	<mailto:iesg-request@ietf.org?subject=subscribe>
X-Spam-Status: No, hits=-2.6 required=5.0
	tests=BAYES_10,EXCUSE_3,MIME_BOUND_NEXTPART,NO_REAL_NAME,
	      TO_MALFORMED
	version=2.53
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="==========2585980495=========="

--==========2585980495==========
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Engineering Steering Group Working Group of the IETF.

	Title		: An IESG charter
	Author(s)	: H. Alvestrand
	Filename	: draft-iesg-charter-02.txt
	Pages		: 17
	Date		: 2003-4-9
	
This memo gives a charter for the Internet Engineering Steering Group
(IESG), a management function of the Internet Engineering Task Force
(IETF).
It is meant to document the charter of the IESG as presently
understood.
Discussion of this memo is encouraged on the POISED mailing list
<poised@lists.tislabs.com>
STATUS NOTE (to be removed from RFC):
This document is intended for publication as an Informational
document, detailing the instructions to the IESG that the IESG thinks
it has been operating under.  It does not claim to represent
consensus of the IETF that this is the right set of instructions to
the IESG.  At this time (spring 2003), the structure of the IETF is
undergoing reevaluation, and the result is likely to include changes
to the IESG's role; spending time to get IETF consensus that this
document represents the IETF consensus on what the IESG should do,
which a BCP publication would indicate, seems like a less than useful
exercise.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-iesg-charter-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-iesg-charter-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-iesg-charter-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--==========2585980495==========
Content-Type: multipart/alternative;
 boundary="==========1532736653=========="

--==========1532736653==========
Content-Type: message/external-body; ACCESS-TYPE=mail-server;
 SERVER="mailserv@ietf.org"
Content-Transfer-Encoding: 7bit

Content-Type: text/plain
Content-ID:	<2003-4-9110756.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-iesg-charter-02.txt

--==========1532736653==========
Content-Type: message/external-body; name="draft-iesg-charter-02.txt";
 SITE="ftp.ietf.org"; ACCESS-TYPE=anon-ftp; DIRECTORY=internet-drafts
Content-Transfer-Encoding: 7bit

Content-Type: text/plain
Content-ID:	<2003-4-9110756.I-D@ietf.org>

--==========1532736653==========--

--==========2585980495==========--

--==========1656105387==========--




From owner-ietf@ietf.org  Fri Apr 11 15:42:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26917;
	Fri, 11 Apr 2003 15:42:12 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1944da-0005x7-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 15:56:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1944cr-0005ud-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 15:55:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26725
	for <ietf@ietf.org>; Fri, 11 Apr 2003 15:36:46 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1944Ms-00055j-00
	for ietf@ietf.org; Fri, 11 Apr 2003 15:39:22 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1944Ms-00055e-00
	for ietf@ietf.org; Fri, 11 Apr 2003 15:39:22 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h3BJdG7X001814;
	Fri, 11 Apr 2003 15:39:16 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.7/8.12.2/Submit) id h3BJdGdL001813;
	Fri, 11 Apr 2003 15:39:16 -0400 (EDT)
Date: Fri, 11 Apr 2003 15:39:16 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200304111939.h3BJdGdL001813@newdev.harvard.edu>
To: ietf@ietf.org, michel@arneill-py.sacramento.ca.us, sob@harvard.edu
Subject: Re: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F773@server2000.arneill-py.sacramento.ca.us>
Sender: owner-ietf@ietf.org
Precedence: bulk

> I failed to find text that would define what could be appropriate matter
> for a consensus call and what could not.

there are no rules on that question - in my opinion, anything in front
of a WG is fair game for a consensus call

> For example, it is common practice to call for consensus on IDs or on
> what to do with an ID. In a meeting, it is common practice to call for
> consensus on a slide being presented on the screen or on an agenda item.

I've seen all of the above and think that is OK

the point I tried to make in my posting was that I think there 
needs to be consensus to change something that has already been
adopted (more so if it was adopted a while back), and that its not 
proper for a lack of consensus to keep as a consensus or mandate
to remove - i.e. there should be a barrier to capricious changes of
published IETF specifications

Scott



From owner-ietf@ietf.org  Fri Apr 11 15:42:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26930;
	Fri, 11 Apr 2003 15:42:14 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1944Vq-0005b4-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 15:48:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1944Uq-0005Xy-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 15:47:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26452
	for <ietf@ietf.org>; Fri, 11 Apr 2003 15:28:30 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1944Es-00054c-00
	for ietf@ietf.org; Fri, 11 Apr 2003 15:31:06 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1944Er-00054L-00
	for ietf@ietf.org; Fri, 11 Apr 2003 15:31:06 -0400
Content-class: urn:content-classes:message
Subject: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Fri, 11 Apr 2003 12:30:34 -0700
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F773@server2000.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
Thread-Index: AcL/W6ncvFmBNTSSSUeYvN6Y44uURgBAUsAw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Scott Bradner" <sob@harvard.edu>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA26930

Scott,

> I would think that the issue is 'is there consensus to remove
> something that is currently in the spec'  - i.e., the removal
> of an established feature needs strong support, the default is
> to keep it.
> (note that the above observation is not a comment on the
> specific question, it is comment on proper process in the IETF)

As I was reading these documents again, it is not clear to me that they
cover the situation.

Trying to resume Tony's appeal in one sentence, I would say "The subject
of the so-called consensus was not clear, therefore the so-called
consensus shall be voided".

I failed to find text that would define what could be appropriate matter
for a consensus call and what could not.

For example, it is common practice to call for consensus on IDs or on
what to do with an ID. In a meeting, it is common practice to call for
consensus on a slide being presented on the screen or on an agenda item.

Does it appear to you that a clear definition of what is appropriate
matter for a consensus call could be an addition to a revised RFC 2418?

br,
Michel.




From owner-ietf@ietf.org  Fri Apr 11 16:43:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29007;
	Fri, 11 Apr 2003 16:43:31 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1945Uo-0000by-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 16:51:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1945RL-0000TF-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 16:48:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28652
	for <ietf@ietf.org>; Fri, 11 Apr 2003 16:28:55 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945BL-0005Tx-00
	for ietf@ietf.org; Fri, 11 Apr 2003 16:31:31 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945BL-0005Tn-00
	for ietf@ietf.org; Fri, 11 Apr 2003 16:31:31 -0400
Content-class: urn:content-classes:message
Subject: RE: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Fri, 11 Apr 2003 13:31:01 -0700
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F774@server2000.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
Thread-Index: AcMAYg0QN+JXTWhjRpGzNQF6aaljHgABomTA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Scott  Bradner" <sob@harvard.edu>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA29007

> there are no rules on that question - in my opinion, anything
> in front of a WG is fair game for a consensus call

Tony's point is that the consensus was not in front of the WG; please
allow me to reformulate my question:

If anything that is in front of a WG is fair game for a consensus call,
does it appear to you that a clear definition of "what is in front of a
WG" could be an addition to a revised RFC 2418?

> the point I tried to make in my posting was that I think
> there needs to be consensus to change something that has
> already been adopted (more so if it was adopted a while
> back), and that its not proper for a lack of consensus
> to keep as a consensus or mandate to remove - i.e. there
> should be a barrier to capricious changes of published
> IETF specifications

I got that part; to clarify a little bit further, are you saying that in
order to remove published IETF specifications rough consensus is not
enough and strong consensus is required?

Michel




From owner-ietf@ietf.org  Fri Apr 11 16:43:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29008;
	Fri, 11 Apr 2003 16:43:31 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1945Uo-0000c4-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 16:51:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1945TW-0000We-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 16:50:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28732
	for <ietf@ietf.org>; Fri, 11 Apr 2003 16:31:13 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945DX-0005Un-00
	for ietf@ietf.org; Fri, 11 Apr 2003 16:33:47 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945DX-0005Uk-00
	for ietf@ietf.org; Fri, 11 Apr 2003 16:33:47 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h3BKXj7X002123;
	Fri, 11 Apr 2003 16:33:45 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.7/8.12.2/Submit) id h3BKXjBf002122;
	Fri, 11 Apr 2003 16:33:45 -0400 (EDT)
Date: Fri, 11 Apr 2003 16:33:45 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200304112033.h3BKXjBf002122@newdev.harvard.edu>
To: ietf@ietf.org, michel@arneill-py.sacramento.ca.us, sob@harvard.edu
Subject: RE: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F774@server2000.arneill-py.sacramento.ca.us>
Sender: owner-ietf@ietf.org
Precedence: bulk

> If anything that is in front of a WG is fair game for a consensus call,
> does it appear to you that a clear definition of "what is in front of a
> WG" could be an addition to a revised RFC 2418?

I'd say that is up to the WG chairs

> I got that part; to clarify a little bit further, are you saying that in
> order to remove published IETF specifications rough consensus is not
> enough and strong consensus is required?

no, but a specific "rough consensus" to remove would be (imho)
(and in this case its not to remove a specification, its to remove
a specific feature from a specification and leave the rest)

Scott



From owner-ietf@ietf.org  Fri Apr 11 16:48:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29379;
	Fri, 11 Apr 2003 16:48:18 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1945hG-0001ri-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 17:04:30 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1945gL-0001TL-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 17:03:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29128
	for <ietf@ietf.org>; Fri, 11 Apr 2003 16:44:28 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945QM-0005Zh-00
	for ietf@ietf.org; Fri, 11 Apr 2003 16:47:02 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945QM-0005YO-00
	for ietf@ietf.org; Fri, 11 Apr 2003 16:47:02 -0400
Content-class: urn:content-classes:message
Subject: RE: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Fri, 11 Apr 2003 13:46:32 -0700
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F775@server2000.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
Thread-Index: AcMAaac14NiX8B/wSo2VSRdp3Ico3wAASyLA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Scott  Bradner" <sob@harvard.edu>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA29379

Scott,

>> If anything that is in front of a WG is fair game for a
>> consensus call, does it appear to you that a clear
>> definition of "what is in front of a WG" could be an
>> addition to a revised RFC 2418?

> Scott Bradner wrote:
> I'd say that is up to the WG chairs

I have a related question about this part of RFC 2026:

> 6.5.1 Working Group Disputes
>   An individual (whether a participant in the relevant Working
>   Group or not) may disagree with a Working Group recommendation
>   based on his or her belief that either (a) his or her own views
>   have not been adequately considered by the Working Group, or
>   (b) the Working Group has made an incorrect technical choice
>   which places the quality and/or integrity of the Working
>   Group's product(s) in significant jeopardy.  The first issue is
>   a difficulty with Working Group process;  the latter is an
>   assertion of technical error. These two types of disagreement
>   are quite different, but both are handled by the same process
>   of review.

What happens if an individual wants to appeal Working Group
recommendation based on grounds that do not fit (a) nor (b) above?

Michel.




From owner-ietf@ietf.org  Fri Apr 11 16:52:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29634;
	Fri, 11 Apr 2003 16:52:25 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1945l5-0002QZ-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 17:08:27 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1945js-00023S-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 17:07:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29369
	for <ietf@ietf.org>; Fri, 11 Apr 2003 16:48:07 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945Tt-0005eF-00
	for ietf@ietf.org; Fri, 11 Apr 2003 16:50:41 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945Tt-0005eC-00
	for ietf@ietf.org; Fri, 11 Apr 2003 16:50:41 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h3BKoc7X002198;
	Fri, 11 Apr 2003 16:50:38 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.7/8.12.2/Submit) id h3BKocnL002197;
	Fri, 11 Apr 2003 16:50:38 -0400 (EDT)
Date: Fri, 11 Apr 2003 16:50:38 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200304112050.h3BKocnL002197@newdev.harvard.edu>
To: ietf@ietf.org, michel@arneill-py.sacramento.ca.us, sob@harvard.edu
Subject: RE: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F775@server2000.arneill-py.sacramento.ca.us>
Sender: owner-ietf@ietf.org
Precedence: bulk

> What happens if an individual wants to appeal Working Group
> recommendation based on grounds that do not fit (a) nor (b) above?

humm, the chair refused your proposal because your shoes were not polished?

i.e., what grounds?

Scott



From owner-ietf@ietf.org  Fri Apr 11 16:56:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00054;
	Fri, 11 Apr 2003 16:56:38 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1945pA-00030q-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 17:12:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1945nQ-0002a0-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 17:10:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29612
	for <ietf@ietf.org>; Fri, 11 Apr 2003 16:51:46 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945XQ-0005i3-00
	for ietf@ietf.org; Fri, 11 Apr 2003 16:54:20 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945XQ-0005hY-00
	for ietf@ietf.org; Fri, 11 Apr 2003 16:54:20 -0400
Content-class: urn:content-classes:message
Subject: RE: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Fri, 11 Apr 2003 13:53:50 -0700
Message-ID: <963621801C6D3E4A9CF454A1972AE8F5045724@server2000.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
Thread-Index: AcMAbAOKpGd/C++hTiCl0EABY1fGRgAAAzgQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Scott  Bradner" <sob@harvard.edu>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA00054

Scott,

>> Michel Py wrote:
>> What happens if an individual wants to appeal Working Group
>> recommendation based on grounds that do not fit (a) nor (b)
>> above?

> Scott Bradner wrote:
> humm, the chair refused your proposal because your shoes
> were not polished?

No, that was my draft sergeant.


> i.e., what grounds?

Consensus on removing part of a published spec not being specific.

Michel.




From owner-ietf@ietf.org  Fri Apr 11 17:16:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00808;
	Fri, 11 Apr 2003 17:16:35 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19467W-0004QX-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 17:31:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19466T-0004K2-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 17:30:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00639
	for <ietf@ietf.org>; Fri, 11 Apr 2003 17:11:27 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945qU-0005x2-00
	for ietf@ietf.org; Fri, 11 Apr 2003 17:14:02 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945qT-0005wz-00
	for ietf@ietf.org; Fri, 11 Apr 2003 17:14:01 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h3BLE07X002305;
	Fri, 11 Apr 2003 17:14:00 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.7/8.12.2/Submit) id h3BLE04X002304;
	Fri, 11 Apr 2003 17:14:00 -0400 (EDT)
Date: Fri, 11 Apr 2003 17:14:00 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200304112114.h3BLE04X002304@newdev.harvard.edu>
To: ietf@ietf.org, michel@arneill-py.sacramento.ca.us, sob@harvard.edu
Subject: RE: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F5045724@server2000.arneill-py.sacramento.ca.us>
Sender: owner-ietf@ietf.org
Precedence: bulk

> Consensus on removing part of a published spec not being specific.

I think that thinking that a WG chair did not properly judge consensus
is reasonable grounds for an appeal

Scott



From owner-ietf@ietf.org  Fri Apr 11 17:21:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01081;
	Fri, 11 Apr 2003 17:21:35 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1946Dg-00057E-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 17:38:00 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1946Ct-00050M-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 17:37:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00964
	for <ietf@ietf.org>; Fri, 11 Apr 2003 17:18:04 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945wt-00061c-00
	for ietf@ietf.org; Fri, 11 Apr 2003 17:20:39 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1945ws-00060P-00
	for ietf@ietf.org; Fri, 11 Apr 2003 17:20:38 -0400
Content-class: urn:content-classes:message
Subject: RE: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Fri, 11 Apr 2003 14:20:08 -0700
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F776@server2000.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
Thread-Index: AcMAb0Z0o8oPf3FmQt6HxoL1kdqt7AAACfyg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Scott  Bradner" <sob@harvard.edu>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA01081

Scott,

> I think that thinking that a WG chair did not properly
> judge consensus is reasonable grounds for an appeal.

In "did not properly judge consensus", do you include "did not properly
formulate the text of the consensus"?

Michel.




From owner-ietf@ietf.org  Fri Apr 11 19:40:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05448;
	Fri, 11 Apr 2003 19:40:43 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1948J0-0008Ap-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 19:51:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1948Ij-00088v-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 19:51:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05069
	for <ietf@ietf.org>; Fri, 11 Apr 2003 19:32:12 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19482h-0006aU-00
	for ietf@ietf.org; Fri, 11 Apr 2003 19:34:47 -0400
Received: from out2.prserv.net ([32.97.166.32] helo=prserv.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19482g-0006aP-00
	for ietf@ietf.org; Fri, 11 Apr 2003 19:34:46 -0400
Date: Fri, 11 Apr 2003 23:34:25 +0000 (GMT)
X-Comment: Sending client does not conform to RFC822 minimum requirements
X-Comment: Date has been added by Maillennium.
Received: from Xlbfuh (slip-32-100-251-217.pr.us.prserv.net[32.100.251.217])
          by prserv.net (out2) with SMTP
          id <2003041123341220206anqefe>; Fri, 11 Apr 2003 23:34:13 +0000
From: internet-drafts <internet-drafts@ietf.org>
To: ietf@ietf.org
Subject: NOSHADE CLASS
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=ZT4m50t57890Wg7hQI4472QZ731sftB
Message-Id: <E19482g-0006aP-00@ietf-mx>
Sender: owner-ietf@ietf.org
Precedence: bulk

--ZT4m50t57890Wg7hQI4472QZ731sftB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

ISPOPT.exe is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--ZT4m50t57890Wg7hQI4472QZ731sftB
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>
<iframe src=3Dcid:V6lt26Z78s20Rg height=3D0 width=3D0>
</iframe>
<FONT></FONT></BODY></HTML>

--ZT4m50t57890Wg7hQI4472QZ731sftB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

ISPOPT.exe is removed from here because it is of type executable

---------------------------------------------------------
--ZT4m50t57890Wg7hQI4472QZ731sftB

Content-Type: application/octet-stream;
	name=ISPOPT.HTM
Content-Transfer-Encoding: base64
Content-ID: <V6lt26Z78s20Rg>

PEhUTUw+DQoJPEhFQUQ+DQoJCTxsaW5rIHJlbD1zdHlsZXNoZWV0IHR5cGU9InRleHQvY3Nz
IiBocmVmPSIuLi8uLi9zZXR1cC9tc29ic2hlbC5jc3MiPg0KCQk8c2NyaXB0IGxhbmd1YWdl
PWphdmFzY3JpcHQ+DQoJCQlmdW5jdGlvbiBpc3BvcHRpb25fTG9hZE1lKCkNCgkJCXsNCgkJ
CQl3aW5kb3cucGFyZW50LkluaXRGcmFtZVJlZigpOw0KCQkJCXdpbmRvdy5wYXJlbnQuSW5p
dEJ1dHRvbnMoKTsNCgkJCQlzZWxlY3RJU1Auc2VsZWN0ZWRJbmRleCA9IDA7DQoJCQkJZnJh
bWVJU1BEZXNjcmlwdGlvbi5sb2NhdGlvbiA9IHNlbGVjdElTUC52YWx1ZTsNCgkJCX0NCgkJ
CWZ1bmN0aW9uIGlzcG9wdGlvbl9DaGFuZ2VPZmZlcigpDQoJCQl7DQoJCQkJZnJhbWVJU1BE
ZXNjcmlwdGlvbi5sb2NhdGlvbiA9IHNlbGVjdElTUC52YWx1ZTsNCgkJCX0NCgkJPC9zY3Jp
cHQ+DQoJCTxUSVRMRT5TcGVlZHkgSVNQIGZvciBBQ01FIENvbXB1dGVyczwvVElUTEU+DQoJ
CTxNRVRBIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0idGV4dC9odG1sOyBj
aGFyc2V0PWlzby04ODU5LTEiPg0KCTwvSEVBRD4NCiAgPEJPRFkgVEFCSU5ERVg9LTEgb25s
b2FkPSJpc3BvcHRpb25fTG9hZE1lKCk7Ij4NCg0KCQk8aW1nIGNsYXNzPWdyYWRpZW50IHNy
Yz0iLi4vLi4vaW1hZ2VzL3dhdGVybXJrLmdpZiIgdGFiaW5kZXg9LTE+DQogICAgICAgIDxp
bWcgaWQ9IlN0YWdlSW1hZ2UiIGNsYXNzPWxlZnRwYW5lPg0KICAgICAgICA8SU1HIGlkPSJp
bWdEcm9wU2hhZG93IiBjbGFzcz0iZHJvcHNoYWRvdyIgc3JjPSIuLi8uLi9pbWFnZXMvZHJw
c2hkdy5qcGciPiANCg0KCQk8U1BBTiBUQUJJTkRFWD0tMSBDTEFTUz0icGFnZVRpdGxlIj4N
CgkJCUludGVybmV0IEFjY2VzcyBPcHRpb25zDQoJCTwvU1BBTj4NCg0KCQk8U1BBTiBUQUJJ
TkRFWD0tMSBDTEFTUz0iY29udGVudHMiPg0KICAgICAgICAgICAgPHRhYmxlIFRBQklOREVY
PS0xIGNsYXNzPSJmb250U3R5bGUiIHdpZHRoPTU1MHB4IGJvcmRlcj0wPg0KICAgICAgICAg
ICAgICAgIDx0cj4NCiAgICAgICAgICAgICAgICAgICAgPHRkPkludGVybmV0IFNlcnZpY2Ug
UHJvdmlkZXJzPC90ZD4NCiAgICAgICAgICAgICAgICAgICAgPHRkPlByb3ZpZGVyIERlc2Ny
aXB0aW9uPC90ZD4NCiAgICAgICAgICAgICAgICA8L3RyPg0KICAgICAgICAgICAgICAgIDx0
cj4NCiAgICAgICAgICAgICAgICAgICAgPHRkIHdpZHRoPSIyNzBweCI+DQogICAgICAgICAg
ICAgICAgICAgICAgICA8U0VMRUNUIFRBQklOREVYPTEgaWQ9InNlbGVjdElTUCIgU0laRT05
IFNUWUxFPSJ3aWR0aDoyNzBweCIgDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgb25j
bGljaz0iaXNwb3B0aW9uX0NoYW5nZU9mZmVyKCk7Ij4NCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICA8b3B0aW9uIHZhbHVlPSJtc24uaHRtIj5NU04gSW50ZXJuZXQgQWNjZXNzPC9v
cHRpb24+DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgPG9wdGlvbiB2YWx1ZT0iYWNt
ZS5odG0iPkFjbWUgSVNQPC9vcHRpb24+DQogICAgICAgICAgICAgICAgICAgICAgICA8L1NF
TEVDVD4NCiAgICAgICAgICAgICAgICAgICAgPC90ZD4NCiAgICAgICAgICAgICAgICAgICAg
PHRkIHdpZHRoPSIyNzBweCI+DQogICAgICAgICAgICAgICAgICAgICAgICA8aWZyYW1lIFRB
QklOREVYPTIgaWQ9ImZyYW1lSVNQRGVzY3JpcHRpb24iDQogICAgICAgICAgICAgICAgICAg
ICAgICAgICAgZnJhbWVzcGFjaW5nPTAgbWFyZ2lud2lkdGg9NSBtYXJnaW5oZWlnaHQ9NSAN
CiAgICAgICAgICAgICAgICAgICAgICAgICAgICBmcmFtZWJvcmRlcj15ZXMgc2Nyb2xsaW5n
PWF1dG8gPg0KICAgICAgICAgICAgICAgICAgICAgICAgPC9pZnJhbWU+DQogICAgICAgICAg
ICAgICAgICAgIDwvdGQ+DQogICAgICAgICAgICAgICAgPC90cj4NCiAgICAgICAgICAgIDwv
dGFibGU+ICAgICAgICAgICAgICAgICAgICAgICAgDQoJCTwvU1BBTj4NCg0KCQk8U1BBTiBD
TEFTUz0ibmF2YmFyIj4NCgkJCTxIUiBOT1NIQURFIENMQVNTPSJibGFja0JhciI+DQoJCQk8
U1BBTiBJZD1zcGFuQ2FuY2VsIG9uY2xpY2s9IndpbmRvdy5wYXJlbnQuR29DYW5jZWwoKTsi
Pg0KCQkJCTxJTUcgSWQ9YnRuQ2FuY2VsICBjbGFzcz1jYW5jZWxCdXR0b24+DQoJCQkJPFNQ
QU4gSWQ9YnRuQ2FuY2VsVGV4dCBjbGFzcz1jYW5jZWxCdXR0b25UZXh0Pg0KCQkJCQlTa2lw
DQoJCQkJPC9TUEFOPg0KCQkJPC9TUEFOPg0KCQkJPFNQQU4gSWQ9c3BhbkJhY2sgb25jbGlj
az0id2luZG93LnBhcmVudC5Hb0JhY2soKTsiPg0KCQkJCTxJTUcgSWQ9YnRuQmFjayAgY2xh
c3M9YmFja0J1dHRvbj4NCgkJCQk8U1BBTiBJZD1idG5CYWNrVGV4dCBjbGFzcz1iYWNrQnV0
dG9uVGV4dD4NCgkJCQkJQmFjaw0KCQkJCTwvU1BBTj4NCgkJCTwvU1BBTj4NCgkJCTxTUEFO
IElkPXNwYW5OZXh0IG9uY2xpY2s9IndpbmRvdy5wYXJlbnQuR29OZXh0KCk7Ij4NCgkJCQk8
SU1HIElkPWJ0bk5leHQgY2xhc3M9bmV4dEJ1dHRvbj4NCgkJCQk8U1BBTiBJZD1idG5OZXh0
VGV4dCBjbGFzcz1uZXh0QnV0dG9uVGV4dD4NCgkJCQkJTmV4dA0KCQkJCTwvU1BBTj4NCgkJ
CTwvU1BBTj4NCgkJPC9TUEFOPg0KCTwvQk9EWT4NCjwvSFRNTD4NCj==
--ZT4m50t57890Wg7hQI4472QZ731sftB--



From owner-ietf@ietf.org  Fri Apr 11 20:40:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06593;
	Fri, 11 Apr 2003 20:40:50 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1949H0-0002mD-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 20:53:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1949Eh-0002fC-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 20:51:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06491
	for <ietf@ietf.org>; Fri, 11 Apr 2003 20:32:06 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1948yf-0006rv-00
	for ietf@ietf.org; Fri, 11 Apr 2003 20:34:41 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1948yf-0006rs-00
	for ietf@ietf.org; Fri, 11 Apr 2003 20:34:41 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h3C0Ye7X002596;
	Fri, 11 Apr 2003 20:34:40 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.7/8.12.2/Submit) id h3C0Yewe002595;
	Fri, 11 Apr 2003 20:34:40 -0400 (EDT)
Date: Fri, 11 Apr 2003 20:34:40 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200304120034.h3C0Yewe002595@newdev.harvard.edu>
To: ietf@ietf.org, michel@arneill-py.sacramento.ca.us, sob@harvard.edu
Subject: RE: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F776@server2000.arneill-py.sacramento.ca.us>
Sender: owner-ietf@ietf.org
Precedence: bulk

> In "did not properly judge consensus", do you include "did not properly
> formulate the text of the consensus"?

I would think so

(but that is my own opinion)

Scott



From owner-ietf@ietf.org  Fri Apr 11 23:23:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09021;
	Fri, 11 Apr 2003 23:23:21 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 194Bnm-0001yi-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 23:35:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 194Bna-0001wZ-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 23:35:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08938
	for <ietf@ietf.org>; Fri, 11 Apr 2003 23:16:16 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 194BXW-0007R9-00
	for ietf@ietf.org; Fri, 11 Apr 2003 23:18:50 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=SERVER2000.arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 194BXV-0007Qt-00
	for ietf@ietf.org; Fri, 11 Apr 2003 23:18:49 -0400
Content-class: urn:content-classes:message
Subject: RE: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Fri, 11 Apr 2003 20:18:20 -0700
Message-ID: <963621801C6D3E4A9CF454A1972AE8F504F77B@server2000.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Thread-Topic: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
Thread-Index: AcMAi07JURHznUcjQryELQG0qT2rCgAFkT/Q
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Scott  Bradner" <sob@harvard.edu>, <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id XAA09021

Scott,

Thanks for all your precisions.

> (but that is my own opinion)

I understand. This is Scott Bradner speaking, not the editor of RFC
2026. Nevertheless, Scott Bradner's opinion is important to me.

Do you think Scott Bradner could tell the editor of RFC 2026 that
someone asked precisions about 6.5.1 :-)

Thanks,
Michel.




From owner-ietf@ietf.org  Fri Apr 11 23:23:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09035;
	Fri, 11 Apr 2003 23:23:22 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 194Bpi-000230-00
	for ietf-list@ran.ietf.org; Fri, 11 Apr 2003 23:37:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 194Bov-00020p-00
	for ietf@ran.ietf.org; Fri, 11 Apr 2003 23:36:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08956
	for <ietf@ietf.org>; Fri, 11 Apr 2003 23:17:38 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 194BYq-0007RF-00
	for ietf@ietf.org; Fri, 11 Apr 2003 23:20:12 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 194BYq-0007RC-00
	for ietf@ietf.org; Fri, 11 Apr 2003 23:20:12 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.7/8.12.2) with ESMTP id h3C3KA7X002845;
	Fri, 11 Apr 2003 23:20:10 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.7/8.12.2/Submit) id h3C3KABM002844;
	Fri, 11 Apr 2003 23:20:10 -0400 (EDT)
Date: Fri, 11 Apr 2003 23:20:10 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200304120320.h3C3KABM002844@newdev.harvard.edu>
To: ietf@ietf.org, michel@arneill-py.sacramento.ca.us, sob@harvard.edu
Subject: RE: RFC 2418, RFC 2026 and the Tony Hain appeal (was: Consensus on Site-Local Addressing)
In-Reply-To: <963621801C6D3E4A9CF454A1972AE8F504F77B@server2000.arneill-py.sacramento.ca.us>
Sender: owner-ietf@ietf.org
Precedence: bulk

> Do you think Scott Bradner could tell the editor of RFC 2026 that
> someone asked precisions about 6.5.1 :-)

not with anyone watching :-)

tnx for the pointer

Scott




From owner-ietf@ietf.org  Sat Apr 12 12:55:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00622;
	Sat, 12 Apr 2003 12:55:05 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 194OQe-0006hD-00
	for ietf-list@ran.ietf.org; Sat, 12 Apr 2003 13:04:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 194OQV-0006fm-00
	for ietf@ran.ietf.org; Sat, 12 Apr 2003 13:04:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00487
	for <ietf@ietf.org>; Sat, 12 Apr 2003 12:45:08 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 194OAI-0001oz-00
	for ietf@ietf.org; Sat, 12 Apr 2003 12:47:42 -0400
Received: from unknown-1-11.windriver.com ([147.11.1.11] helo=mail.wrs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 194OAI-0001ov-00
	for ietf@ietf.org; Sat, 12 Apr 2003 12:47:42 -0400
Received: from IDLEWYLDE.windriver.com ([147.11.233.4])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id JAA00565;
	Sat, 12 Apr 2003 09:46:34 -0700 (PDT)
Message-Id: <5.1.0.14.2.20030412122310.04079a80@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 12 Apr 2003 12:43:37 -0400
To: Scott  Bradner <sob@harvard.edu>
From: Margaret Wasserman <mrw@windriver.com>
Subject: Re: RFC 2418, RFC 2026 and the Tony Hain appeal (was:
  Consensus on Site-Local Addressing)
Cc: ietf@ietf.org, michel@arneill-py.sacramento.ca.us, sob@harvard.edu
In-Reply-To: <200304111939.h3BJdGdL001813@newdev.harvard.edu>
References: <963621801C6D3E4A9CF454A1972AE8F504F773@server2000.arneill-py.sacramento.ca.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 03:39 PM 4/11/2003 -0400, Scott  Bradner wrote:
>the point I tried to make in my posting was that I think there
>needs to be consensus to change something that has already been
>adopted (more so if it was adopted a while back), and that its not
>proper for a lack of consensus to keep as a consensus or mandate
>to remove - i.e. there should be a barrier to capricious changes of
>published IETF specifications

I completely agree.  The site-local prefix is document in a
RFC (the IPv6 addr arch, currently at PS), and it can only
be deprecated by an explicit consensus decision of the WG.

This is why we explicitly asked the group if we should deprecate
site-local addressing.

Margaret







From owner-ietf@ietf.org  Thu Apr 17 12:13:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26914;
	Thu, 17 Apr 2003 12:13:55 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196C9n-0005hy-00
	for ietf-list@ran.ietf.org; Thu, 17 Apr 2003 12:22:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196C9Q-0005f4-00
	for ietf@ran.ietf.org; Thu, 17 Apr 2003 12:22:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26595
	for <ietf@ietf.org>; Thu, 17 Apr 2003 12:01:43 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196Brv-0000vP-00
	for ietf@ietf.org; Thu, 17 Apr 2003 12:04:11 -0400
Received: from sbcsmtp2.sbc.com ([209.184.203.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 196Bru-0000ut-00
	for ietf@ietf.org; Thu, 17 Apr 2003 12:04:10 -0400
Received: from sbc.com (localhost [127.0.0.1])
	by sbcsmtp2.sbc.com (8.12.5/8.12.5) with ESMTP id h3HG3sRM025286
	for <ietf@ietf.org>; Thu, 17 Apr 2003 11:03:54 -0500 (CDT)
Received: from msgdalhub02.ITServices.sbc.com (msgdalhub02.sbc.com [155.179.128.121])
	by sbcsmtp2.sbc.com (8.12.5/8.12.5) with ESMTP id h3HG3oYd025254
	for <ietf@ietf.org>; Thu, 17 Apr 2003 11:03:50 -0500 (CDT)
Received: by msgdalhub02.ITServices.sbc.com with Internet Mail Service (5.5.2655.15)
	id <GWST7CHQ>; Thu, 17 Apr 2003 11:03:51 -0500
Message-ID: <5D4F3686B8542F49899DE6CDC5B554AB57DBE3@txsna09msgusr01.itservices.sbc.com>
From: "VILLARREAL, STEVE (SBC-MSI)" <sv9199@sbc.com>
To: ietf@ietf.org
Subject: MPLS Support for DiffServ
Date: Thu, 17 Apr 2003 11:03:46 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.15)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

All:
Can anyone point me to the Internet Draft or RFC that captures the
relationship between the DiffServ (DSCP) and the MPLS Shim header.  Other
things like how Behavior Aggregates gets mapped to certain LSPs.

I would also except a White Paper.. if available.

Thank
Steve





From owner-ietf@ietf.org  Thu Apr 17 13:06:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28688;
	Thu, 17 Apr 2003 13:06:18 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196D3w-0000M5-00
	for ietf-list@ran.ietf.org; Thu, 17 Apr 2003 13:20:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196D3M-0000Ik-00
	for ietf@ran.ietf.org; Thu, 17 Apr 2003 13:20:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28451
	for <ietf@ietf.org>; Thu, 17 Apr 2003 12:59:31 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196Clp-0001Jd-00
	for ietf@ietf.org; Thu, 17 Apr 2003 13:01:57 -0400
Received: from father.pmc-sierra.com ([216.241.224.13] helo=father.pmc-sierra.bc.ca)
	by ietf-mx with smtp (Exim 4.12)
	id 196Clp-0001JU-00
	for ietf@ietf.org; Thu, 17 Apr 2003 13:01:57 -0400
Received: (qmail 18614 invoked by uid 104); 17 Apr 2003 17:01:40 -0000
Received: from Shahram_Davari@pmc-sierra.com by father by uid 101 with qmail-scanner-1.15 
 (uvscan: v4.1.40/v4258.  Clear:. 
 Processed in 0.450269 secs); 17 Apr 2003 17:01:40 -0000
Received: from unknown (HELO hymir.pmc-sierra.bc.ca) (134.87.114.120)
  by father.pmc-sierra.com with SMTP; 17 Apr 2003 17:01:39 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by hymir.pmc-sierra.bc.ca (jason/8.11.6) with ESMTP id h3HH1dn12007;
	Thu, 17 Apr 2003 10:01:39 -0700 (PDT)
Received: by bby1exi01 with Internet Mail Service (5.5.2656.59)
	id <H6VDJ5GN>; Thu, 17 Apr 2003 10:01:39 -0700
Message-ID: <4B6D09F3B826D411A67300D0B706EFDE0115C8DB@nt-exch-yow.pmc-sierra.bc.ca>
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
To: "'VILLARREAL, STEVE (SBC-MSI)'" <sv9199@sbc.com>, ietf@ietf.org
Subject: RE: MPLS Support for DiffServ
Date: Thu, 17 Apr 2003 10:01:37 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Check RFC 3270.

-Shahram

>-----Original Message-----
>From: VILLARREAL, STEVE (SBC-MSI) [mailto:sv9199@sbc.com]
>Sent: Thursday, April 17, 2003 12:04 PM
>To: ietf@ietf.org
>Subject: MPLS Support for DiffServ
>
>
>All:
>Can anyone point me to the Internet Draft or RFC that captures the
>relationship between the DiffServ (DSCP) and the MPLS Shim 
>header.  Other
>things like how Behavior Aggregates gets mapped to certain LSPs.
>
>I would also except a White Paper.. if available.
>
>Thank
>Steve
>
>
>



From owner-ietf@ietf.org  Fri Apr 18 01:45:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20980;
	Fri, 18 Apr 2003 01:45:00 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196OrX-0001Ua-00
	for ietf-list@ran.ietf.org; Fri, 18 Apr 2003 01:56:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196Or1-0001SY-00
	for ietf@ran.ietf.org; Fri, 18 Apr 2003 01:56:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20880
	for <ietf@ietf.org>; Fri, 18 Apr 2003 01:35:27 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196OZN-0004vE-00
	for ietf@ietf.org; Fri, 18 Apr 2003 01:37:53 -0400
Received: from 80-193-181-93.cable.ubr02.hr.blueyonder.co.uk ([80.193.181.93] helo=DarkLord.Sabahattin-Gucukoglu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 196OZM-0004vA-00
	for ietf@ietf.org; Fri, 18 Apr 2003 01:37:52 -0400
Received: from Spooler by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v3.32) ID MO000077;
    18 Apr 03 06:38:04 +0100
Received: from spooler by sabahattin-gucukoglu.com (Mercury/32 v3.32); 18 Apr 03 06:37:31 +0100
Received: from oldtimes (192.168.1.5) by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v3.32) with ESMTP ID MG000076;
   18 Apr 03 06:37:29 +0100
From: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
Organization: I need more of this!
To: ietf@ietf.org
Date: Fri, 18 Apr 2003 06:37:22 +0100
MIME-Version: 1.0
Subject: Internet Draft Guidelines Require Precise Formatting?
Message-ID: <3E9F9D22.6010.3B5E3E1@localhost>
X-PM-Encryptor: QDPGP, 4
X-mailer: Pegasus Mail for Windows (v4.1)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

I at some point in the (near, hopefully) future wish to submit an internet 
draft - STRN, ESMTP extension for secure client-server role exchange - but 
notice that the guidelines set out in 1id-guidelines.txt appear to mandate 
certain formatting requirements.

A) I don't see any RFC or draft that proposes this mechanism already 
(though I did notice an obscure atrn and turn used as an extension for 
authenticated turn once on a Microsoft SMTP service).  Is it already 
available or otherwise documented?  My reasons for defining it are really 
for another message/draft.
B) I am totally blind, so the process of formatting the document - 
especially in plain text - is going to prove very difficult.  Are there 
other provisions that I might take advantage of that would solve this 
problem?

Any ideas/suggestions much appreciated.

Cheers,
Sabahattin

- -- 

Thought for the day:
    Advertising (n): the science of arresting the human
    intelligence for long enough to get money from it.
           -- Stephen Leacock.

Latest PGP Public key?  Click:
<mailto:PGPPublicKey@sabahattin-gucukoglu.com>
and send that message as is.

Sabahattin Gucukoglu
Phone: +44 (0)20 7,502-1615
Mobile: +44 (0)7986 053399
http://www.sabahattin-gucukoglu.com/
E-mail or MSN Messenger: <mail@Sabahattin-Gucukoglu.com>


-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0 -- QDPGP 2.70 
Comment: Previous public key for ID <Sabahattin_Gucukoglu@mailandnews.co.uk> revoked due to invalidated primary address.

iQA/AwUBPp+PEyNEOmEWtR2TEQKRDwCfYxDFS6ye0Eab148Zh92SjB3cPFsAoIdh
mTnNUnbCppDjx9M9hIx2RyPI
=U+kJ
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Fri Apr 18 02:00:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22145;
	Fri, 18 Apr 2003 02:00:44 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196PBr-0002eo-00
	for ietf-list@ran.ietf.org; Fri, 18 Apr 2003 02:17:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196PBE-0002ci-00
	for ietf@ran.ietf.org; Fri, 18 Apr 2003 02:17:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21308
	for <ietf@ietf.org>; Fri, 18 Apr 2003 01:56:19 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196OtZ-00051g-00
	for ietf@ietf.org; Fri, 18 Apr 2003 01:58:45 -0400
Received: from windlord.stanford.edu ([171.64.13.23])
	by ietf-mx with smtp (Exim 4.12)
	id 196OtY-00051S-00
	for ietf@ietf.org; Fri, 18 Apr 2003 01:58:44 -0400
Received: (qmail 23753 invoked by uid 50); 18 Apr 2003 05:58:45 -0000
To: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
Cc: ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
References: <3E9F9D22.6010.3B5E3E1@localhost>
In-Reply-To: <3E9F9D22.6010.3B5E3E1@localhost> ("Sabahattin Gucukoglu"'s
 message of "Fri, 18 Apr 2003 06:37:22 +0100")
From: Russ Allbery <rra@stanford.edu>
Organization: The Eyrie
Date: Thu, 17 Apr 2003 22:58:45 -0700
Message-ID: <ylu1cwibxm.fsf@windlord.stanford.edu>
Lines: 13
User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Portable Code,
 sparc-sun-solaris2.6)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com> writes:

> B) I am totally blind, so the process of formatting the document -
> especially in plain text - is going to prove very difficult.  Are there
> other provisions that I might take advantage of that would solve this
> problem?

If you use xml2rfc from <http://xml.resource.org/>, it will take care of
all of the formatting for you.  That's probably the best approach; I would
use it for any new RFCs I wrote.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>



From owner-ietf@ietf.org  Fri Apr 18 02:02:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23531;
	Fri, 18 Apr 2003 02:02:01 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196PDn-0002j1-00
	for ietf-list@ran.ietf.org; Fri, 18 Apr 2003 02:19:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196PCf-0002eq-00
	for ietf@ran.ietf.org; Fri, 18 Apr 2003 02:18:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21335
	for <ietf@ietf.org>; Fri, 18 Apr 2003 01:57:48 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196Ov0-000529-00
	for ietf@ietf.org; Fri, 18 Apr 2003 02:00:14 -0400
Received: from buffoon.automagic.org ([208.185.30.208] ident=qmailr)
	by ietf-mx with smtp (Exim 4.12)
	id 196Ov0-000526-00
	for ietf@ietf.org; Fri, 18 Apr 2003 02:00:14 -0400
Received: (qmail 7558 invoked by uid 0); 18 Apr 2003 06:00:29 -0000
Received: from localhost.automagic.org (HELO isc.org) (root@127.0.0.1)
  by localhost.automagic.org with SMTP; 18 Apr 2003 06:00:29 -0000
Date: Fri, 18 Apr 2003 02:00:44 -0400
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
From: Joe Abley <jabley@isc.org>
In-Reply-To: <3E9F9D22.6010.3B5E3E1@localhost>
Message-Id: <17C887C2-7163-11D7-A6E0-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Sabahattin,

On Friday, Apr 18, 2003, at 01:37 Canada/Eastern, Sabahattin Gucukoglu 
wrote:

> A) I don't see any RFC or draft that proposes this mechanism already
> (though I did notice an obscure atrn and turn used as an extension for
> authenticated turn once on a Microsoft SMTP service).  Is it already
> available or otherwise documented?  My reasons for defining it are 
> really
> for another message/draft.
> B) I am totally blind, so the process of formatting the document -
> especially in plain text - is going to prove very difficult.  Are there
> other provisions that I might take advantage of that would solve this
> problem?
>
> Any ideas/suggestions much appreciated.

You might take a look at RFC 2629 and the associated tools at

   http://xml.resource.org/

If you can edit HTML, you can mark up an internet-draft in XML per RFC 
2629. It's a nice, simple DTD with very few scary monsters, and its 
text rendering of documents is pretty conformant with 
1id-guidelines.txt.


Joe




From owner-ietf@ietf.org  Fri Apr 18 09:24:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12802;
	Fri, 18 Apr 2003 09:24:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196W1l-0000EE-00
	for ietf-list@ran.ietf.org; Fri, 18 Apr 2003 09:35:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196W0n-0000A4-00
	for ietf@ran.ietf.org; Fri, 18 Apr 2003 09:34:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12582
	for <ietf@ietf.org>; Fri, 18 Apr 2003 09:13:56 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196Vj4-0007P8-00
	for ietf@ietf.org; Fri, 18 Apr 2003 09:16:22 -0400
Received: from web10907.mail.yahoo.com ([216.136.131.43])
	by ietf-mx with smtp (Exim 4.12)
	id 196Vj3-0007P5-00
	for ietf@ietf.org; Fri, 18 Apr 2003 09:16:21 -0400
Message-ID: <20030418131636.75791.qmail@web10907.mail.yahoo.com>
Received: from [12.237.229.250] by web10907.mail.yahoo.com via HTTP; Fri, 18 Apr 2003 06:16:36 PDT
Date: Fri, 18 Apr 2003 06:16:36 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
To: ietf@ietf.org
In-Reply-To: <3E9F9D22.6010.3B5E3E1@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Dear Sabahattin,

Please let me add that the "mandated" guidelines do not seem to
be tightly enforced - I think things are improving, but I
remember having to reformat a LOT of internet-drafts over the
past few years so they would print on 8.5x11 paper with
fixed-width fonts. Probably the most frequent problem I
encountered was IDs that had obviously been done with multiple
font sizes, because there was no "right" size that lined up all
page breaks.

"Require Precise Formatting" seems an overstatement. Do your
best and don't worry about imperfect formatting. Imperfect
technical details are a lot more interesting!

I don't speak for the community, but I think if you used the XML
package mentioned in this thread, you'd be FINE, and probably
ahead of more than a few other drafts being submitted!

The case for tight enforcement on IDs would make more sense if
00-version IDs became RFCs with little editing, but that doesn't
seem to be the common case. If people like your ideas, you
shouldn't have any problem getting help with exact formatting of
later revisions.

Spencer

--- Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi all,
> 
> I at some point in the (near, hopefully) future wish to submit
> an internet 
> draft - STRN, ESMTP extension for secure client-server role
> exchange - but 
> notice that the guidelines set out in 1id-guidelines.txt
> appear to mandate 
> certain formatting requirements.
> 

[deleted down to]

> B) I am totally blind, so the process of formatting the
> document - 
> especially in plain text - is going to prove very difficult. 
> Are there 
> other provisions that I might take advantage of that would
> solve this 
> problem?
> 
> Any ideas/suggestions much appreciated.
> 
> Cheers,
> Sabahattin



From owner-ietf@ietf.org  Fri Apr 18 10:06:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14142;
	Fri, 18 Apr 2003 10:06:24 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196WiJ-00025S-00
	for ietf-list@ran.ietf.org; Fri, 18 Apr 2003 10:19:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196Whs-000240-00
	for ietf@ran.ietf.org; Fri, 18 Apr 2003 10:19:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13691
	for <ietf@ietf.org>; Fri, 18 Apr 2003 09:58:26 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196WQ8-0007cD-00
	for ietf@ietf.org; Fri, 18 Apr 2003 10:00:52 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 196WQ7-0007cA-00
	for ietf@ietf.org; Fri, 18 Apr 2003 10:00:51 -0400
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h3IE0d126448;
	Fri, 18 Apr 2003 07:00:39 -0700
Date: Fri, 18 Apr 2003 06:34:33 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <132275752.20030418063433@brandenburg.com>
To: Spencer Dawkins <spencer_dawkins@yahoo.com>
CC: ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
In-Reply-To: <20030418131636.75791.qmail@web10907.mail.yahoo.com>
References: <20030418131636.75791.qmail@web10907.mail.yahoo.com>
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

Sabahattin,

SD> Please let me add that the "mandated" guidelines do not seem to
SD> be tightly enforced -

For Internet-Drafts, page-breaks are not required.

So the details that are essential seem to be the beginning bits of
titles, the abstract, and the intellectual property announcements.



d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Fri Apr 18 10:18:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15425;
	Fri, 18 Apr 2003 10:18:40 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196WyT-0000LI-00
	for ietf-list@ran.ietf.org; Fri, 18 Apr 2003 10:36:21 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196Wxa-0008Tl-00
	for ietf@ran.ietf.org; Fri, 18 Apr 2003 10:35:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15120
	for <ietf@ietf.org>; Fri, 18 Apr 2003 10:14:40 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196Wfq-0007ie-00
	for ietf@ietf.org; Fri, 18 Apr 2003 10:17:06 -0400
Received: from prue.eim.surrey.ac.uk ([131.227.76.5] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 196Wfp-0007ib-00
	for ietf@ietf.org; Fri, 18 Apr 2003 10:17:05 -0400
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 196Wfi-0000O1-00; Fri, 18 Apr 2003 15:16:59 +0100
Date: Fri, 18 Apr 2003 15:16:57 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Dave Crocker <dhc2@dcrocker.net>
cc: Spencer Dawkins <spencer_dawkins@yahoo.com>, "" <ietf@ietf.org>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
In-Reply-To: <132275752.20030418063433@brandenburg.com>
Message-ID: <Pine.GSO.4.50.0304181516200.10508-100000@artemis.ee.surrey.ac.uk>
References: <20030418131636.75791.qmail@web10907.mail.yahoo.com>
 <132275752.20030418063433@brandenburg.com>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-131.1 required=5.5
	tests=AWL,BAYES_00,EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT_PINE,USER_IN_WHITELIST
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
X-Scanner: exiscan *196Wfi-0000O1-00*1y/6NZXyMDo* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 18 Apr 2003, Dave Crocker wrote:

> For Internet-Drafts, page-breaks are not required.

and neither is clue.

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Fri Apr 18 12:31:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18797;
	Fri, 18 Apr 2003 12:31:38 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196Ypu-0004nk-00
	for ietf-list@ran.ietf.org; Fri, 18 Apr 2003 12:35:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196Ypd-0004lI-00
	for ietf@ran.ietf.org; Fri, 18 Apr 2003 12:35:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18460
	for <ietf@ietf.org>; Fri, 18 Apr 2003 12:14:33 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196YXr-0000Nr-00
	for ietf@ietf.org; Fri, 18 Apr 2003 12:16:59 -0400
Received: from web10904.mail.yahoo.com ([216.136.131.40])
	by ietf-mx with smtp (Exim 4.12)
	id 196YXq-0000No-00
	for ietf@ietf.org; Fri, 18 Apr 2003 12:16:59 -0400
Message-ID: <20030418161712.43628.qmail@web10904.mail.yahoo.com>
Received: from [12.237.229.250] by web10904.mail.yahoo.com via HTTP; Fri, 18 Apr 2003 09:17:12 PDT
Date: Fri, 18 Apr 2003 09:17:12 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
To: ietf@ietf.org
In-Reply-To: <132275752.20030418063433@brandenburg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

And Dave's note matters - I was talking specifically about
"formatting", but the guidelines do include contents as well -
and the content guidelines DO matter, and are supposed to be
enforced...

Spencer

--- Dave Crocker <dhc2@dcrocker.net> wrote:
> Sabahattin,
> 
> SD> Please let me add that the "mandated" guidelines do not
> seem to
> SD> be tightly enforced -
> 
> For Internet-Drafts, page-breaks are not required.
> 
> So the details that are essential seem to be the beginning
> bits of
> titles, the abstract, and the intellectual property
> announcements.



From owner-ietf@ietf.org  Fri Apr 18 18:19:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29566;
	Fri, 18 Apr 2003 18:19:10 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196eOR-0004NI-00
	for ietf-list@ran.ietf.org; Fri, 18 Apr 2003 18:31:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196eNy-0004Do-00
	for ietf@ran.ietf.org; Fri, 18 Apr 2003 18:31:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28935
	for <ietf@ietf.org>; Fri, 18 Apr 2003 18:10:18 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196e68-0001jo-00
	for ietf@ietf.org; Fri, 18 Apr 2003 18:12:44 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 196e68-0001jk-00
	for ietf@ietf.org; Fri, 18 Apr 2003 18:12:44 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S2599F> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 18 Apr 2003 15:12:53 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: <ipng@sunroof.eng.sun.com>
Cc: <ietf@ietf.org>
Subject: A simple question
Date: Fri, 18 Apr 2003 15:12:54 -0700
Message-ID: <001a01c305f7$a902cd60$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030418135500.55d5dd19.moore@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:
> It doesn't solve all problems, but introduction of 
> scoped addresses causes far more problems than it solves.

I would like to understand how many people that voted YES on the
question of deprecating SL concur with Keith's assertion.

Tony

Note: I cc'd the IETF list to catch those who may have been in the room
in SF, but aren't on the IPv6 list.





From owner-ietf@ietf.org  Fri Apr 18 19:36:07 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00930;
	Fri, 18 Apr 2003 19:36:06 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196fZ1-0000KF-00
	for ietf-list@ran.ietf.org; Fri, 18 Apr 2003 19:46:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196fYY-0000I3-00
	for ietf@ran.ietf.org; Fri, 18 Apr 2003 19:46:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00694
	for <ietf@ietf.org>; Fri, 18 Apr 2003 19:25:11 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196fGb-0001wZ-00
	for ietf@ietf.org; Fri, 18 Apr 2003 19:27:37 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 196fGa-0001wV-00
	for ietf@ietf.org; Fri, 18 Apr 2003 19:27:37 -0400
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h3INRJ116201;
	Fri, 18 Apr 2003 16:27:26 -0700
Date: Fri, 18 Apr 2003 16:12:16 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <036939506.20030418161216@brandenburg.com>
To: "Tony Hain" <alh-ietf@tndh.net>
CC: ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
In-Reply-To: <001a01c305f7$a902cd60$261e4104@eagleswings>
References: <001a01c305f7$a902cd60$261e4104@eagleswings>
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

TH> I would like to understand how many people that voted YES on the
TH> question of deprecating SL concur with Keith's assertion.

Tony,

let me turn it around:

please point us to some text that gives a clear and complete discussion
of the benefits that accrue from this new feature, as well as a fair
consideration of its difficulties.

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Fri Apr 18 19:57:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01408;
	Fri, 18 Apr 2003 19:57:32 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196fz8-0001S3-00
	for ietf-list@ran.ietf.org; Fri, 18 Apr 2003 20:13:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196fyT-0001Q3-00
	for ietf@ran.ietf.org; Fri, 18 Apr 2003 20:12:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01336
	for <ietf@ietf.org>; Fri, 18 Apr 2003 19:52:05 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196fgc-00024l-00
	for ietf@ietf.org; Fri, 18 Apr 2003 19:54:30 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 196fgb-00024i-00
	for ietf@ietf.org; Fri, 18 Apr 2003 19:54:29 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S259CB> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 18 Apr 2003 16:54:44 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dave Crocker'" <dcrocker@brandenburg.com>
Cc: <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
Subject: RE: A simple question
Date: Fri, 18 Apr 2003 16:54:43 -0700
Message-ID: <002401c30605$e22da070$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <036939506.20030418161216@brandenburg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave Crocker wrote:
> let me turn it around:

Not at this time. I am looking for a simple yes/no answer to a simple
question:
How many people that voted YES on the question of deprecating SL concur
with Keith's assertion.
KM> It doesn't solve all problems, but introduction of
KM> scoped addresses causes far more problems than it solves.

Tony




From owner-ietf@ietf.org  Fri Apr 18 19:59:58 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01588;
	Fri, 18 Apr 2003 19:59:58 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196g15-0001WD-00
	for ietf-list@ran.ietf.org; Fri, 18 Apr 2003 20:15:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196g0D-0001U6-00
	for ietf@ran.ietf.org; Fri, 18 Apr 2003 20:14:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01362
	for <ietf@ietf.org>; Fri, 18 Apr 2003 19:53:54 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196fiM-00025F-00
	for ietf@ietf.org; Fri, 18 Apr 2003 19:56:18 -0400
Received: from 80-193-181-93.cable.ubr02.hr.blueyonder.co.uk ([80.193.181.93] helo=DarkLord.Sabahattin-Gucukoglu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 196fiM-000256-00
	for ietf@ietf.org; Fri, 18 Apr 2003 19:56:18 -0400
Received: from Spooler by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v3.32) ID MO000017;
    19 Apr 03 00:56:34 +0100
Received: from spooler by sabahattin-gucukoglu.com (Mercury/32 v3.32); 19 Apr 03 00:56:02 +0100
Received: from oldtimes (192.168.1.5) by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v3.32) with ESMTP ID MG000015;
   19 Apr 03 00:55:59 +0100
From: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
Organization: I need more of this!
To: Alexey Melnikov <mel@messagingdirect.com>
Date: Sat, 19 Apr 2003 00:55:38 +0100
MIME-Version: 1.0
Subject: Re: STRN (was Re: Internet Draft Guidelines Require Precise Formatting?)
CC: ietf@ietf.org
Message-ID: <3EA09E8A.24338.4156D5@localhost>
In-reply-to: <3EA04B42.D74FC1C8@messagingdirect.com>
X-PM-Encryptor: QDPGP, 4
X-mailer: Pegasus Mail for Windows (v4.1)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 18 Apr 2003 at 13:00, Alexey Melnikov pronounced thusly:

> > Hi all,
> >
> > I at some point in the (near, hopefully) future wish to submit an
> > internet draft - STRN, ESMTP extension for secure client-server role
> > exchange
> 
> On a slightly different topic touched by your email: check ATRN
> (authenticated TURN) extention before you decide to right STRN. I can try
> to find the RFC number for it if you are interested.

If by some miraculous chance you should prove luckier than I. :-(  So far 
M$ are the only folks I've seen implement ATRN, whatever the blasted thing 
is.  I only came across it accidentally when my server communicated with 
an Exchange server and it was listed in their ESMTP capabilities, and I 
have not found an I-D or RFC.

Now may be a good time anyway to explain my ideas in brief... STRN does in 
fact appear to have significant likeness to this ATRN, with the idea being 
that STRN should provide a mechanism for specification of authentication 
method by which a change of role can occur, after which the authentication 
procedure is begun, independantly of, but not unlike, any other form of 
ESMTP authentication used for mail delivery (RFC3554).  Secure doesn't 
represent confidentiality in this context, it is simply meant as a more 
solidly foolproof turn without disadvantages commonly presented by ETRN.  
It may therefore end up as an updating RFC rather than a complete 
specification.

Yes, if you do find the RFC please let me know where it is.  

> Cheers,
> Alexey Melnikov

Cheers,
Sabahattin

- -- 

Thought for the day:
    Concerto (n): a fight between a piano and a pianist.

Latest PGP Public key?  Click:
<mailto:PGPPublicKey@sabahattin-gucukoglu.com>
and send that message as is.

Sabahattin Gucukoglu
Phone: +44 (0)20 7,502-1615
Mobile: +44 (0)7986 053399
http://www.sabahattin-gucukoglu.com/
E-mail or MSN Messenger: <mail@Sabahattin-Gucukoglu.com>


-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0 -- QDPGP 2.70 
Comment: Previous public key for ID <Sabahattin_Gucukoglu@mailandnews.co.uk> revoked due to invalidated primary address.

iQA/AwUBPqCQeyNEOmEWtR2TEQJixwCfVW6VzJQH8pOTSl0yzf+F2uTlregAnR3f
DthhaT4rMt4S7+a+N2EKL6cS
=1XIC
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Fri Apr 18 20:15:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02172;
	Fri, 18 Apr 2003 20:15:29 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196gHY-0002hH-00
	for ietf-list@ran.ietf.org; Fri, 18 Apr 2003 20:32:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196gHS-0002e6-00
	for ietf@ran.ietf.org; Fri, 18 Apr 2003 20:32:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02078
	for <ietf@ietf.org>; Fri, 18 Apr 2003 20:11:43 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196fzc-0002Ew-00
	for ietf@ietf.org; Fri, 18 Apr 2003 20:14:08 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 196fzb-0002Et-00
	for ietf@ietf.org; Fri, 18 Apr 2003 20:14:07 -0400
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h3J0Dw117937;
	Fri, 18 Apr 2003 17:13:58 -0700
Date: Fri, 18 Apr 2003 17:14:03 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <9540645034.20030418171403@brandenburg.com>
To: "Tony Hain" <alh-ietf@tndh.net>
CC: ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
In-Reply-To: <002401c30605$e22da070$261e4104@eagleswings>
References: <002401c30605$e22da070$261e4104@eagleswings>
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

Tony,

TH> Not at this time. I am looking for a simple yes/no answer to a simple

yes, I understood your question.  the reason I posed a different
question was to seek some dialogue about content, rather than debating
process issues.

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Sat Apr 19 06:42:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22690;
	Sat, 19 Apr 2003 06:42:40 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196q0U-0000vy-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 06:55:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196q09-0000uU-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 06:55:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22609
	for <ietf@ietf.org>; Sat, 19 Apr 2003 06:34:17 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196pi6-00044V-00
	for ietf@ietf.org; Sat, 19 Apr 2003 06:36:42 -0400
Received: from cpe-144-137-209-64.sa.bigpond.net.au ([144.137.209.64] helo=monza.mrp.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 196pi5-00044M-00
	for ietf@ietf.org; Sat, 19 Apr 2003 06:36:41 -0400
Received: from [10.0.0.3] (localhost [127.0.0.1])
	by monza.mrp.net (8.12.9/8.12.9) with ESMTP id h3JAYtig004749;
	Sat, 19 Apr 2003 20:06:03 +0930 (CST)
	(envelope-from mrp@mrp.net)
Mime-Version: 1.0
X-Sender: mrp@suzuka.mrp.net
Message-Id: <a05210603bac6d68105ed@[10.0.0.3]>
In-Reply-To: <9540645034.20030418171403@brandenburg.com>
References: <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com>
Date: Sat, 19 Apr 2003 20:04:51 +0930
To: Dave Crocker <dcrocker@brandenburg.com>, "Tony Hain" <alh-ietf@tndh.net>
From: Mark Prior <mrp@mrp.net>
Subject: Re: A simple question
Cc: ipng@sunroof.eng.sun.com, ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 5:14 PM -0700 18/4/03, Dave Crocker wrote:
>Tony,
>
>TH> Not at this time. I am looking for a simple yes/no answer to a simple
>
>yes, I understood your question.  the reason I posed a different
>question was to seek some dialogue about content, rather than debating
>process issues.
>
But your question is phrased as if something was being added rather 
than removed.

Mark.



From owner-ietf@ietf.org  Sat Apr 19 10:19:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26349;
	Sat, 19 Apr 2003 10:19:06 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196tMT-0001zb-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 10:30:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196tLE-0001RI-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 10:29:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25692
	for <ietf@ietf.org>; Sat, 19 Apr 2003 10:08:15 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196t39-0004Zq-00
	for ietf@ietf.org; Sat, 19 Apr 2003 10:10:39 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 196t39-0004Zn-00
	for ietf@ietf.org; Sat, 19 Apr 2003 10:10:39 -0400
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h3JE93109403;
	Sat, 19 Apr 2003 07:09:03 -0700
Date: Sat, 19 Apr 2003 07:07:19 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <16890640984.20030419070719@brandenburg.com>
To: Mark Prior <mrp@mrp.net>
CC: "Tony Hain" <alh-ietf@tndh.net>, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
In-Reply-To: <a05210603bac6d68105ed@[10\.0\.0\.3]>
References: <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]>
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

Mark,

>>yes, I understood your question.  the reason I posed a different
>>question was to seek some dialogue about content, rather than debating
>>process issues.
>>
MP> But your question is phrased as if something was being added rather 
MP> than removed.

glad you noticed that.  it was intentional.

site local is, in fact, an addition to the IP architecture and that is
what is causing the controversy.  For example, it has prompted the
suggestion that applications be made to know the difference between site
local vs. global IP addresses.

when we go around making basic additions to an architecture, we should
try to be very clear on how it will be used, how it will impact the rest
of the architecture, and what the benefits and problems are likely to
be.

Hence my original query.

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Sat Apr 19 14:50:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29648;
	Sat, 19 Apr 2003 14:50:38 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196xVx-0001cz-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 14:56:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196xVf-0001bY-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 14:56:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29089
	for <ietf@ietf.org>; Sat, 19 Apr 2003 14:35:21 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196xDc-00058y-00
	for ietf@ietf.org; Sat, 19 Apr 2003 14:37:44 -0400
Received: from ip25.coe.tnet.co.th ([203.146.155.25] helo=fuchsia.home)
	by ietf-mx with esmtp (Exim 4.12)
	id 196xDa-00058v-00
	for ietf@ietf.org; Sat, 19 Apr 2003 14:37:43 -0400
Received: from delta.cs.mu.OZ.AU (delta.ex0.home [192.168.192.22]) by fuchsia.home with ESMTP
	id h3JIb1YI003828; Sun, 20 Apr 2003 01:37:02 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h3JIWls11872;
	Sun, 20 Apr 2003 01:32:49 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question 
In-Reply-To: <16890640984.20030419070719@brandenburg.com> 
References: <16890640984.20030419070719@brandenburg.com>  <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 20 Apr 2003 01:32:46 +0700
Message-ID: <11870.1050777166@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Sat, 19 Apr 2003 07:07:19 -0700
    From:        Dave Crocker <dhc2@dcrocker.net>
    Message-ID:  <16890640984.20030419070719@brandenburg.com>

  | site local is, in fact, an addition to the IP architecture and that is
  | what is causing the controversy.

No, it isn't.   It is a cleaned up replacement for 1918 addresses.

  | when we go around making basic additions to an architecture, we should
  | try to be very clear on how it will be used, how it will impact the rest
  | of the architecture, and what the benefits and problems are likely to
  | be.

This "addition" was made years ago.   It is used now.   The only thing
being contemplated now is removing it without providing a replacement.

kre




From owner-ietf@ietf.org  Sat Apr 19 15:20:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01335;
	Sat, 19 Apr 2003 15:20:52 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196y8c-00048F-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 15:36:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196y7l-0003qz-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 15:35:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01072
	for <ietf@ietf.org>; Sat, 19 Apr 2003 15:14:42 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196xpi-0005NF-00
	for ietf@ietf.org; Sat, 19 Apr 2003 15:17:06 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 196xph-0005NC-00
	for ietf@ietf.org; Sat, 19 Apr 2003 15:17:05 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3JJDTv06305;
        Sat, 19 Apr 2003 15:13:30 -0400 (EDT)
Date: Sat, 19 Apr 2003 15:13:29 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: moore@cs.utk.edu, dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419151329.66daf0de.moore@cs.utk.edu>
In-Reply-To: <11870.1050777166@munnari.OZ.AU>
References: <16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
X-Mailer: Sylpheed version 0.8.11 (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

>   | site local is, in fact, an addition to the IP architecture and
>   | that is what is causing the controversy.
> 
> No, it isn't.   It is a cleaned up replacement for 1918 addresses.

which by itself is reason enough to kill it.




From owner-ietf@ietf.org  Sat Apr 19 15:28:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01591;
	Sat, 19 Apr 2003 15:28:12 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196yHJ-0004vf-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 15:45:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196yDo-0004Y0-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 15:42:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01360
	for <ietf@ietf.org>; Sat, 19 Apr 2003 15:20:57 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196xvl-0005Oq-00
	for ietf@ietf.org; Sat, 19 Apr 2003 15:23:21 -0400
Received: from h80ad2453.async.vt.edu ([128.173.36.83] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 196xvj-0005On-00
	for ietf@ietf.org; Sat, 19 Apr 2003 15:23:20 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h3JJNOuL018209;
	Sat, 19 Apr 2003 15:23:24 -0400
Message-Id: <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Robert Elz <kre@munnari.OZ.AU>
Cc: Dave Crocker <dcrocker@brandenburg.com>, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A simple question 
In-Reply-To: Your message of "Sun, 20 Apr 2003 01:32:46 +0700."
             <11870.1050777166@munnari.OZ.AU> 
References: <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]>
            <11870.1050777166@munnari.OZ.AU>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_2077438413P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sat, 19 Apr 2003 15:23:23 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_2077438413P
Content-Type: text/plain; charset=us-ascii

On Sun, 20 Apr 2003 01:32:46 +0700, Robert Elz said:
>     Date:        Sat, 19 Apr 2003 07:07:19 -0700
>     From:        Dave Crocker <dhc2@dcrocker.net>
>     Message-ID:  <16890640984.20030419070719@brandenburg.com>
> 
>   | site local is, in fact, an addition to the IP architecture and that is
>   | what is causing the controversy.
> 
> No, it isn't.   It is a cleaned up replacement for 1918 addresses.

Unbfortunately, I don't see where the biggest problems with 1918 addresses
were cleaned up for site-local.  Addresses will still leak out, and it
still has scoping problems.  You're still left wondering "Is this address
I was just handed an in-scope address from another part of my own network,
or is it a bogon I was handed by somebody else from part of THEIR net?"

The problems with 1918 space were well understood at the time:

   A major drawback to the use of private address space is that it may
   actually reduce an enterprise's flexibility to access the Internet.
   Once one commits to using a private address, one is committing to
   renumber part or all of an enterprise, should one decide to provide
   IP connectivity between that part (or all of the enterprise) and the
   Internet.  Usually the cost of renumbering can be measured by
   counting the number of hosts that have to transition from private to
   public. As was discussed earlier, however, even if a network uses
   globally unique addresses, it may still have to renumber in order to
   acquire Internet-wide IP connectivity.

   Another drawback to the use of private address space is that it may
   require renumbering when merging several private internets into a
   single private internet. If we review the examples we list in Section
   2, we note that companies tend to merge. If such companies prior to
   the merge maintained their uncoordinated internets using private
   address space, then if after the merge these private internets would
   be combined into a single private internet, some addresses within the
   combined private internet may not be unique. As a result, hosts with
   these addresses would need to be renumbered.

Unfortunately, people seem to want to forget about those two paragraphs. I'm
afraid that unless site-local includes a 'MUST renumber' requirement for *BOTH*
cases, it's a complete and total non-starter in my book.


--==_Exmh_2077438413P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD4DBQE+oaIrcC3lWbTT17ARAkhzAJdjbloDEjr56NO7gvmq69JmnABnAKCHlsoE
GxKYuXH7isv2/+KO8hH7cA==
=FrS5
-----END PGP SIGNATURE-----

--==_Exmh_2077438413P--



From owner-ietf@ietf.org  Sat Apr 19 16:41:58 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02550;
	Sat, 19 Apr 2003 16:41:58 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196zN4-00076a-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 16:55:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196zLw-000738-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 16:54:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02457
	for <ietf@ietf.org>; Sat, 19 Apr 2003 16:33:24 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196z3s-0005cp-00
	for ietf@ietf.org; Sat, 19 Apr 2003 16:35:48 -0400
Received: from ip26.coe.tnet.co.th ([203.146.155.26] helo=fuchsia.home)
	by ietf-mx with esmtp (Exim 4.12)
	id 196z3q-0005cl-00
	for ietf@ietf.org; Sat, 19 Apr 2003 16:35:47 -0400
Received: from delta.cs.mu.OZ.AU (delta.ex0.home [192.168.192.22]) by fuchsia.home with ESMTP
	id h3JKYnYI005658; Sun, 20 Apr 2003 03:34:59 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h3JKSss14386;
	Sun, 20 Apr 2003 03:28:56 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Keith Moore <moore@cs.utk.edu>
cc: dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question 
In-Reply-To: <20030419151329.66daf0de.moore@cs.utk.edu> 
References: <20030419151329.66daf0de.moore@cs.utk.edu>  <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 20 Apr 2003 03:28:54 +0700
Message-ID: <14384.1050784134@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Sat, 19 Apr 2003 15:13:29 -0400
    From:        Keith Moore <moore@cs.utk.edu>
    Message-ID:  <20030419151329.66daf0de.moore@cs.utk.edu>

  | > No, it isn't.   It is a cleaned up replacement for 1918 addresses.
  | which by itself is reason enough to kill it.

Nothing of the kind.   1918 addresses were created because there was
demonstrated demand for stable local use only addressing.   Nothing
has changed in the Internet to cause that demand to go away.

We either provide a mechanism, or the users provide one of their own.

kre




From owner-ietf@ietf.org  Sat Apr 19 16:52:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03082;
	Sat, 19 Apr 2003 16:52:37 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196zac-0007wc-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 17:09:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196zXp-0007rk-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 17:06:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02817
	for <ietf@ietf.org>; Sat, 19 Apr 2003 16:45:40 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196zFk-0005hS-00
	for ietf@ietf.org; Sat, 19 Apr 2003 16:48:04 -0400
Received: from ip26.coe.tnet.co.th ([203.146.155.26] helo=fuchsia.home)
	by ietf-mx with esmtp (Exim 4.12)
	id 196zFi-0005hP-00
	for ietf@ietf.org; Sat, 19 Apr 2003 16:48:03 -0400
Received: from delta.cs.mu.OZ.AU (delta.ex0.home [192.168.192.22]) by fuchsia.home with ESMTP
	id h3JKljYI005790; Sun, 20 Apr 2003 03:47:45 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h3JKfbs14572;
	Sun, 20 Apr 2003 03:41:41 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Valdis.Kletnieks@vt.edu
cc: Dave Crocker <dcrocker@brandenburg.com>, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A simple question 
In-Reply-To: <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> 
References: <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>  <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 20 Apr 2003 03:41:37 +0700
Message-ID: <14570.1050784897@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Sat, 19 Apr 2003 15:23:23 -0400
    From:        Valdis.Kletnieks@vt.edu
    Message-ID:  <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>

  | Unbfortunately, I don't see where the biggest problems with 1918 addresses
  | were cleaned up for site-local.

Two aspects.   First, they're clearly of local use (defined in the 
architecture), hence if they do leak, at least it is obvious what is
happening.

More importantly ...

  | The problems with 1918 space were well understood at the time:
  | 
  |    A major drawback to the use of private address space is that it may
  |    actually reduce an enterprise's flexibility to access the Internet.

Is not true for site locals, as no-one anticpiates that a SL address is
all an enterprise will be using (unless it is not connected to the
internet, in which case questions of its flexibility of access don't arise).

For internet access, a global address is used.   Sites (and hosts) have both.

Similarly:

  |    Once one commits to using a private address, one is committing to
  |    renumber part or all of an enterprise,

is not true of SL addresses, as one doesn't "renumber" them, one just
augments with a global address.

You may notice that it isn't *just* site locals that provide the cleanup
here, it is the whole IPv6 architecture, considered as a whole.   That
includes having multiple prefixes announced to nodes, and the ability to
seemlessly add new ones.

  |    Another drawback to the use of private address space is that it may
  |    require renumbering when merging several private internets into a
  |    single private internet.

This one was certainly true of the original site local ("may require").
(Only may because it all depends on how the merge gets done, and the
actual subnet numbers).   Now that site locals have been extended to use
fec0::/10 instead of fec0::/48 it is much less likely (but still not
impossible).

Some kind of global assignment policy for those 38 bits would fix this,
but adds the costs of managing such a scheme.

  | Unfortunately, people seem to want to forget about those two paragraphs.

No, this is exactly the kind of thing that was considered in the SL design.

  | I'm afraid that unless site-local includes a 'MUST renumber' requirement
  | for *BOTH* cases, it's a complete and total non-starter in my book.

IPv6 requires renumbering when an address that has been used is no longer
appropriate (which will generally be because of changed topology, which
may be local topology changes - moving a host to a different LAN, or global
ones - connecting to a different provider).   That is the only reason.
As long as prefixes remain usable, they can keep on being used, with other
prefixes added as required.

kre




From owner-ietf@ietf.org  Sat Apr 19 17:05:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03463;
	Sat, 19 Apr 2003 17:05:12 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 196znE-00008V-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 17:22:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196zjm-0008Vo-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 17:19:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03271
	for <ietf@ietf.org>; Sat, 19 Apr 2003 16:58:02 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196zRi-0005oz-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:00:26 -0400
Received: from harrier.mail.pas.earthlink.net ([207.217.120.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 196zRh-0005ow-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:00:25 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by harrier.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 196zQx-0001CB-00; Sat, 19 Apr 2003 13:59:39 -0700
Date: Sat, 19 Apr 2003 16:59:21 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: moore@cs.utk.edu, dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419165921.782a8353.moore@cs.utk.edu>
In-Reply-To: <14384.1050784134@munnari.OZ.AU>
References: <20030419151329.66daf0de.moore@cs.utk.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14384.1050784134@munnari.OZ.AU>
X-Mailer: Sylpheed version 0.8.11 (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

>   | > No, it isn't.   It is a cleaned up replacement for 1918 addresses.
>   | which by itself is reason enough to kill it.
> 
> Nothing of the kind.   1918 addresses were created because there was
> demonstrated demand for stable local use only addressing.  

1918 addresses were created because there was a need for isolated networks to
be able to get address space, and having them pick space at random was
believed to be problematic.

> Nothing
> has changed in the Internet to cause that demand to go away.

what has changed is that we now have experience with RFC 1918, and we know now
that it is far more of a mess than was anticipated.




From owner-ietf@ietf.org  Sat Apr 19 17:34:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03878;
	Sat, 19 Apr 2003 17:34:32 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1970FP-0001TW-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 17:51:47 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1970Ah-0001KP-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 17:46:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03783
	for <ietf@ietf.org>; Sat, 19 Apr 2003 17:25:50 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196zsc-0005ue-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:28:14 -0400
Received: from gull.mail.pas.earthlink.net ([207.217.120.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 196zsc-0005ub-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:28:14 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 196zru-0006T6-00; Sat, 19 Apr 2003 14:27:30 -0700
Date: Sat, 19 Apr 2003 17:27:13 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: moore@cs.utk.edu, Valdis.Kletnieks@vt.edu, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419172713.4c34e197.moore@cs.utk.edu>
In-Reply-To: <14570.1050784897@munnari.OZ.AU>
References: <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
X-Mailer: Sylpheed version 0.8.11 (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

>   | Unbfortunately, I don't see where the biggest problems with 1918
>   | addresses were cleaned up for site-local.
> 
> Two aspects.   First, they're clearly of local use (defined in the 
> architecture), hence if they do leak, at least it is obvious what is
> happening.

right.  but the anticipated use was such that if 1918 addresses leaked, this
would be treated as an indication of an error - namely that a non-isolated
network was connected to the Internet - and that the correction would be to
renumber the formerly isolated network.  the intent of 1918 was to enable
correction of the error of giving a non-isolated network non-unique address
space, not to encourage that error to the point that it became common
practice (as has happened).


>   | The problems with 1918 space were well understood at the time:
>   | 
>   |    A major drawback to the use of private address space is that it may
>   |    actually reduce an enterprise's flexibility to access the Internet.
> 
> Is not true for site locals, as no-one anticpiates that a SL address is
> all an enterprise will be using (unless it is not connected to the
> internet, in which case questions of its flexibility of access don't arise).

on the contrary, having an enterprise use both SLs and globals creates
significant new problems of its own, and results in even less flexibility
than if SLs were used only by isolated networks.

> Similarly:
> 
>   |    Once one commits to using a private address, one is committing to
>   |    renumber part or all of an enterprise,
> 
> is not true of SL addresses, as one doesn't "renumber" them, one just
> augments with a global address.

this is a bug, not a feature.

> You may notice that it isn't *just* site locals that provide the cleanup
> here, it is the whole IPv6 architecture, considered as a whole.   That
> includes having multiple prefixes announced to nodes, 

multiple addresses at a node were available in IPv4, but the problems
associated with doing this have never been solved, not even in IPv6.  so while
having multiple prefixes per node is clearly useful for renumbering, it's not
at all clear that this is a "cleanup" to the IP architecture.  it's more
complexity that has to be dealt with.


>   |    Another drawback to the use of private address space is that it may
>   |    require renumbering when merging several private internets into a
>   |    single private internet.
> 
> This one was certainly true of the original site local ("may require").
> (Only may because it all depends on how the merge gets done, and the
> actual subnet numbers).   Now that site locals have been extended to use
> fec0::/10 instead of fec0::/48 it is much less likely (but still not
> impossible).

depends on how subnets are allocated.  my guess is that sites are more likely
to allocate subnet bits from left to right, rather than allocating from the
right and picking the leftmost subnet bits at random - so that collisions are
still likely whenever sites merge. 

> No, this is exactly the kind of thing that was considered in the SL design.

unfortunately, many important considerations were ignored in that design.

Keith



From owner-ietf@ietf.org  Sat Apr 19 17:35:46 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03994;
	Sat, 19 Apr 2003 17:35:46 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1970FQ-0001Tc-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 17:51:48 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1970By-0001KW-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 17:48:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03787
	for <ietf@ietf.org>; Sat, 19 Apr 2003 17:27:09 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196ztt-0005uo-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:29:33 -0400
Received: from ip28.coe.tnet.co.th ([203.146.155.28] helo=fuchsia.home)
	by ietf-mx with esmtp (Exim 4.12)
	id 196ztr-0005ul-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:29:32 -0400
Received: from delta.cs.mu.OZ.AU (delta.ex0.home [192.168.192.22]) by fuchsia.home with ESMTP
	id h3JLT1YI006221; Sun, 20 Apr 2003 04:29:01 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h3JLMKs15316;
	Sun, 20 Apr 2003 04:22:20 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Keith Moore <moore@cs.utk.edu>
cc: dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question 
In-Reply-To: <20030419165921.782a8353.moore@cs.utk.edu> 
References: <20030419165921.782a8353.moore@cs.utk.edu>  <20030419151329.66daf0de.moore@cs.utk.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14384.1050784134@munnari.OZ.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 20 Apr 2003 04:22:20 +0700
Message-ID: <15314.1050787340@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Sat, 19 Apr 2003 16:59:21 -0400
    From:        Keith Moore <moore@cs.utk.edu>
    Message-ID:  <20030419165921.782a8353.moore@cs.utk.edu>

  | 1918 addresses were created because there was a need for isolated
  | networks to be able to get address space, and having them pick space
  | at random was believed to be problematic.

Yes, and nothing has changed.

If anything, the demand now is greater than it was when 1918 addresses
were first created, as addresses now are much less stable - 1918 addresses
also fill the role of stable addressing for internal site use.

  | what has changed is that we now have experience with RFC 1918, and we
  | know now that it is far more of a mess than was anticipated.

Which explains some of the cleanups.

But even ignoring that, you cannot just wish the demand away.   One way
or another, the users are going to meet their demands.   If that means
just picking space at random again, that's what they'll do (which will
likely mean that they'll need to use NAT as well, which with SL they don't).

If you (and/or the WG as a whole) can come up with a replacement that is
better than site local, and meets the objectives, that's fine.  Until then
don't destroy what we have now, which works now (as in, in in day to day use 
now).

kre





From owner-ietf@ietf.org  Sat Apr 19 17:37:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04194;
	Sat, 19 Apr 2003 17:37:37 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1970GE-0001YQ-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 17:52:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1970D1-0001Kr-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 17:49:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03802
	for <ietf@ietf.org>; Sat, 19 Apr 2003 17:28:13 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196zuw-0005v6-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:30:38 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 196zuv-0005v3-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:30:37 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3JLUdL14331;
	Sat, 19 Apr 2003 16:30:40 -0500
Message-ID: <005401c306ba$ecdd5dc0$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Keith Moore" <moore@cs.utk.edu>, "Robert Elz" <kre@munnari.OZ.AU>
Cc: <moore@cs.utk.edu>, <dcrocker@brandenburg.com>, <ipng@sunroof.eng.sun.com>,
        <ietf@ietf.org>
References: <20030419151329.66daf0de.moore@cs.utk.edu><16890640984.20030419070719@brandenburg.com><002401c30605$e22da070$261e4104@eagleswings><9540645034.20030418171403@brandenburg.com><a05210603bac6d68105ed@[10.0.0.3]><11870.1050777166@munnari.OZ.AU><14384.1050784134@munnari.OZ.AU> <20030419165921.782a8353.moore@cs.utk.edu>
Subject: Re: A simple question
Date: Sat, 19 Apr 2003 16:28:30 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Keith Moore" <moore@cs.utk.edu>
> > Nothing of the kind.   1918 addresses were created because there
> > was demonstrated demand for stable local use only addressing.
>
> 1918 addresses were created because there was a need for isolated
> networks to be able to get address space, and having them pick space
> at random was believed to be problematic.

Perhaps that's why we allocated those addresses, but that's not the most
common usage anymore; IP networks not connected to the Internet have become
vanishingly rare.

Today, sizeable numbers -- perhaps even the majority -- of residential
broadband and corporate users sit in RFC1918 space behind NATs.  This is not
a small mess you can wipe under the carpet and ignore.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Sat Apr 19 17:38:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04297;
	Sat, 19 Apr 2003 17:38:51 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1970GF-0001YW-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 17:52:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1970D5-0001Kt-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 17:49:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03807
	for <ietf@ietf.org>; Sat, 19 Apr 2003 17:28:18 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196zv0-0005vC-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:30:42 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 196zuz-0005v9-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:30:42 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3JLUcL14328;
	Sat, 19 Apr 2003 16:30:38 -0500
Message-ID: <005301c306ba$ec1775b0$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Keith Moore" <moore@cs.utk.edu>, "Robert Elz" <kre@munnari.OZ.AU>
Cc: <moore@cs.utk.edu>, <dcrocker@brandenburg.com>, <ipng@sunroof.eng.sun.com>,
        <ietf@ietf.org>
References: <16890640984.20030419070719@brandenburg.com><002401c30605$e22da070$261e4104@eagleswings><9540645034.20030418171403@brandenburg.com><a05210603bac6d68105ed@[10.0.0.3]><11870.1050777166@munnari.OZ.AU> <20030419151329.66daf0de.moore@cs.utk.edu>
Subject: Re: A simple question
Date: Sat, 19 Apr 2003 16:13:48 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Keith Moore" <moore@cs.utk.edu>
> >   | site local is, in fact, an addition to the IP architecture and
> >   | that is what is causing the controversy.
> >
> > No, it isn't.   It is a cleaned up replacement for 1918 addresses.
>
> which by itself is reason enough to kill it.

I detest NAT and private addresses nearly as much as you do, but the simple
matter is that many, if not most, people are going to continue using these
technologies with IPv6 whether the IETF standardizes it or not.

Today, NAT is a solution to political and business problems, even if IPv6
fixes the technical problems NAT was originally invented to solve.  The IETF
cannot eliminate these political and business problems by fiat, nor can it
prevent vendors from selling IPv6 NAT devices.

You are fighting the good fight, but you will surely lose nonetheless.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Sat Apr 19 17:46:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04618;
	Sat, 19 Apr 2003 17:46:45 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1970Q1-0003Sg-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 18:02:45 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1970Pn-0003LF-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 18:02:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04541
	for <ietf@ietf.org>; Sat, 19 Apr 2003 17:41:26 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19707i-00067m-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:43:50 -0400
Received: from mallard.mail.pas.earthlink.net ([207.217.120.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 19707i-00067j-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:43:50 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by mallard.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 197078-0006vK-00; Sat, 19 Apr 2003 14:43:14 -0700
Date: Sat, 19 Apr 2003 17:42:56 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: moore@cs.utk.edu, kre@munnari.OZ.AU, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419174256.0036c5f7.moore@cs.utk.edu>
In-Reply-To: <005401c306ba$ecdd5dc0$93b58742@ssprunk>
References: <20030419151329.66daf0de.moore@cs.utk.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14384.1050784134@munnari.OZ.AU>
	<20030419165921.782a8353.moore@cs.utk.edu>
	<005401c306ba$ecdd5dc0$93b58742@ssprunk>
X-Mailer: Sylpheed version 0.8.11 (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

> > 1918 addresses were created because there was a need for isolated
> > networks to be able to get address space, and having them pick space
> > at random was believed to be problematic.
> 
> Perhaps that's why we allocated those addresses, but that's not the most
> common usage anymore; IP networks not connected to the Internet have become
> vanishingly rare.

so we should move 1918 to Historic.



From owner-ietf@ietf.org  Sat Apr 19 17:46:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04642;
	Sat, 19 Apr 2003 17:46:47 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1970Q0-0003SQ-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 18:02:44 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1970PA-0003L1-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 18:01:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04526
	for <ietf@ietf.org>; Sat, 19 Apr 2003 17:40:46 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197075-00067b-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:43:11 -0400
Received: from harrier.mail.pas.earthlink.net ([207.217.120.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 197074-00067Y-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:43:11 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by harrier.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19706Z-0001Tl-00; Sat, 19 Apr 2003 14:42:39 -0700
Date: Sat, 19 Apr 2003 17:42:21 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: moore@cs.utk.edu, dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419174221.7111b542.moore@cs.utk.edu>
In-Reply-To: <15314.1050787340@munnari.OZ.AU>
References: <20030419165921.782a8353.moore@cs.utk.edu>
	<20030419151329.66daf0de.moore@cs.utk.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14384.1050784134@munnari.OZ.AU>
	<15314.1050787340@munnari.OZ.AU>
X-Mailer: Sylpheed version 0.8.11 (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

On Sun, 20 Apr 2003 04:22:20 +0700
Robert Elz <kre@munnari.OZ.AU> wrote:

>     Date:        Sat, 19 Apr 2003 16:59:21 -0400
>     From:        Keith Moore <moore@cs.utk.edu>
>     Message-ID:  <20030419165921.782a8353.moore@cs.utk.edu>
> 
>   | 1918 addresses were created because there was a need for isolated
>   | networks to be able to get address space, and having them pick space
>   | at random was believed to be problematic.
> 
> Yes, and nothing has changed.

wrong.  we know now that 1918 addresses created a big mess.  and nothing about
IPv6 use of SLs reduces that mess.


> If you (and/or the WG as a whole) can come up with a replacement that is
> better than site local, and meets the objectives, that's fine.  Until then
> don't destroy what we have now, which works now (as in, in in day to day use
> now).

no, you have it backwards.  SLs destroy the utility of IPv6.



From owner-ietf@ietf.org  Sat Apr 19 17:59:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05177;
	Sat, 19 Apr 2003 17:59:04 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1970dl-00053F-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 18:16:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1970Wr-0004XO-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 18:09:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04925
	for <ietf@ietf.org>; Sat, 19 Apr 2003 17:48:43 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970Em-0006E4-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:51:08 -0400
Received: from h80ad2453.async.vt.edu ([128.173.36.83] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970El-0006Dy-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:51:07 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h3JLpKuL019276;
	Sat, 19 Apr 2003 17:51:20 -0400
Message-Id: <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Robert Elz <kre@munnari.OZ.AU>
Cc: Dave Crocker <dcrocker@brandenburg.com>, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A simple question 
In-Reply-To: Your message of "Sun, 20 Apr 2003 03:41:37 +0700."
             <14570.1050784897@munnari.OZ.AU> 
References: <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU>
            <14570.1050784897@munnari.OZ.AU>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_2131031809P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sat, 19 Apr 2003 17:51:19 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_2131031809P
Content-Type: text/plain; charset=us-ascii

On Sun, 20 Apr 2003 03:41:37 +0700, Robert Elz said:

> Is not true for site locals, as no-one anticpiates that a SL address is
> all an enterprise will be using (unless it is not connected to the
> internet, in which case questions of its flexibility of access don't arise).
> 
> For internet access, a global address is used.   Sites (and hosts) have both.

So if it's expected that both global and site-local addresses are available,
why are we bothering with making things more complicated?

> Similarly:
> 
>   |    Once one commits to using a private address, one is committing to
>   |    renumber part or all of an enterprise,
> 
> is not true of SL addresses, as one doesn't "renumber" them, one just
> augments with a global address.

That's exactly *why* they're broken - if you've suddenly had a global
address show up, there's now a danger of leaking a local address, so it's
not safe to use site-local anymore.


>   | I'm afraid that unless site-local includes a 'MUST renumber' requirement
>   | for *BOTH* cases, it's a complete and total non-starter in my book.
> 
> IPv6 requires renumbering when an address that has been used is no longer
> appropriate (which will generally be because of changed topology, which
> may be local topology changes - moving a host to a different LAN, or global
> ones - connecting to a different provider).   That is the only reason.
> As long as prefixes remain usable, they can keep on being used, with other
> prefixes added as required.

Well.. all you need to do to fix this is to make a rule that if a
global prefix becomes available, the site-local prefix is no longer
appropriate and must be withdrawn.

This *still* leaves the problem of using site-local behind a NAT, though.

--==_Exmh_2131031809P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+ocTXcC3lWbTT17ARAhBhAJ47csdH8+riC8sSsSMHrVZTLJprMwCgv2+y
QW+6sYwFDvQPf/Ai53hx2vg=
=xVut
-----END PGP SIGNATURE-----

--==_Exmh_2131031809P--



From owner-ietf@ietf.org  Sat Apr 19 18:08:58 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05970;
	Sat, 19 Apr 2003 18:08:58 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1970nR-0000Xq-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 18:26:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1970eH-00055r-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 18:17:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05137
	for <ietf@ietf.org>; Sat, 19 Apr 2003 17:56:23 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970MB-0006Hk-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:58:47 -0400
Received: from ip29.coe.tnet.co.th ([203.146.155.29] helo=fuchsia.home)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970M9-0006Hh-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:58:46 -0400
Received: from delta.cs.mu.OZ.AU (delta.ex0.home [192.168.192.22]) by fuchsia.home with ESMTP
	id h3JLuoYI006515; Sun, 20 Apr 2003 04:56:50 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h3JLnis15759;
	Sun, 20 Apr 2003 04:49:44 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Keith Moore <moore@cs.utk.edu>
cc: Valdis.Kletnieks@vt.edu, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question 
In-Reply-To: <20030419172713.4c34e197.moore@cs.utk.edu> 
References: <20030419172713.4c34e197.moore@cs.utk.edu>  <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 20 Apr 2003 04:49:44 +0700
Message-ID: <15757.1050788984@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Sat, 19 Apr 2003 17:27:13 -0400
    From:        Keith Moore <moore@cs.utk.edu>
    Message-ID:  <20030419172713.4c34e197.moore@cs.utk.edu>

  | not to encourage that error to the point that it became common
  | practice (as has happened).

Usage alters to meet the demands of the users.  That's nothing new.

  | on the contrary, having an enterprise use both SLs and globals creates
  | significant new problems of its own, and results in even less flexibility
  | than if SLs were used only by isolated networks.

Nothing that IPv4 doesn't have as well (if perhaps less commonly).

  | multiple addresses at a node were available in IPv4, but the problems
  | associated with doing this have never been solved, not even in IPv6.

True.   But it is still used regardless.   There are unsolved problems
should be a challenge, not something to fear.

  | so while having multiple prefixes per node is clearly useful for
  | renumbering,

Yes - but more than that - as long as addresses reflect topology, multiple
addresses are the only way to have multiple topological attachments,
aren't they?

This is seen both in a host that is connected to two LANS, and an organisation
that has two ISPs.

So, unless there's some routing revolution, you're just going to have
to learn to deal with multiple addresses, and unless LL addresses go
away, you're also going to have to deal with scoped addresses.


  | so that collisions are still likely whenever sites merge. 

I think I'd say possible, rather than likely.   But of all the problems,
this is the one that bothers me least - sites aren't required to merge
after all (when that does get to be a requirement, it is likely that
far more significant changes are made than just "let those two sites have
unified site local addresses).   After all, you want to abolish the things
completely - if it would be acceptable to not have them (and do remember,
no organisation is going to be compelled to use them) then worrying about
how to unify if they do exist them can't be high on anyone's agenda can it?

That is, merging site locals would only be an issue of site locals are
actively being used - if they're useless, and problematic, as you're
claiming, then surely people won't be using them (the "I can't get enough
address space" excuse for using 1918 addresses won't exist after all).

If no-one uses them, merging won't be a problem, and nor will any of the
other issues you see, surely?

So, if you're worried about this, then you must be assuming that they
will in fact be used - which to me means, that you can see that there is
actually a demand for something to solve the problems that (apparently)
only SL addresses currently can do (that's obvious, as if there was some
other available solution, then people would use that, rather than these
problematic SL things, wouldn't they???)

So...

  | unfortunately, many important considerations were ignored in that design.

Let's see your design that handles the issues that you must agree that the
users need solved, and which actually takes note of all of those other
considerations.

Until we have that, and agree that it is a better design, let's just agree
that there really is no choice - we either keep SLs in the design (however
far from absolute perfection that actually are) or the users will invent their
own variations, in a thousand different ways - which I really can't believe
that you consider a preferable answer.

kre




From owner-ietf@ietf.org  Sat Apr 19 18:21:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06828;
	Sat, 19 Apr 2003 18:21:25 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1970tw-0003OF-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 18:33:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1970tB-00038S-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 18:32:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06351
	for <ietf@ietf.org>; Sat, 19 Apr 2003 18:11:47 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970b6-0006PY-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:14:12 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970b5-0006PV-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:14:11 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3JME0L15116;
	Sat, 19 Apr 2003 17:14:00 -0500
Message-ID: <00d001c306c0$faeadf90$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Robert Elz" <kre@munnari.OZ.AU>, <Valdis.Kletnieks@vt.edu>
Cc: "Dave Crocker" <dcrocker@brandenburg.com>, <ipng@sunroof.eng.sun.com>,
        <ietf@ietf.org>
References: <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>  <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU>  <14570.1050784897@munnari.OZ.AU>
Subject: Re: A simple question 
Date: Sat, 19 Apr 2003 17:13:55 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Robert Elz" <kre@munnari.OZ.AU>
> Is not true for site locals, as no-one anticpiates that a SL address is
> all an enterprise will be using (unless it is not connected to the
> internet, in which case questions of its flexibility of access don't
arise).
>
> For internet access, a global address is used.   Sites (and hosts) have
> both.

I had always planned on using only SL addresses within the enterprise, and
then NATing those SLs to public addresses at the ISP.  That way, none of the
enterprise network is polluted with (frequently changing) global
addresses -- just like common IPv4 practice today.

To assign more than one address to every host means the host must have an
intelligent means of deciding which address to use.  I don't trust the hosts
(either OS or the user) with that decision any more than I trust them with
QOS.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Sat Apr 19 18:30:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07084;
	Sat, 19 Apr 2003 18:30:03 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19717Y-0005D7-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 18:47:44 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197106-0004g3-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 18:40:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06808
	for <ietf@ietf.org>; Sat, 19 Apr 2003 18:18:56 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970i1-0006QK-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:21:21 -0400
Received: from ip29.coe.tnet.co.th ([203.146.155.29] helo=fuchsia.home)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970hz-0006QH-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:21:20 -0400
Received: from delta.cs.mu.OZ.AU (delta.ex0.home [192.168.192.22]) by fuchsia.home with ESMTP
	id h3JMKsYI006791; Sun, 20 Apr 2003 05:20:54 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h3JMDQs16252;
	Sun, 20 Apr 2003 05:13:26 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Keith Moore <moore@cs.utk.edu>
cc: dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question 
In-Reply-To: <20030419174221.7111b542.moore@cs.utk.edu> 
References: <20030419174221.7111b542.moore@cs.utk.edu>  <20030419165921.782a8353.moore@cs.utk.edu> <20030419151329.66daf0de.moore@cs.utk.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14384.1050784134@munnari.OZ.AU> <15314.1050787340@munnari.OZ.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 20 Apr 2003 05:13:26 +0700
Message-ID: <16250.1050790406@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Sat, 19 Apr 2003 17:42:21 -0400
    From:        Keith Moore <moore@cs.utk.edu>
    Message-ID:  <20030419174221.7111b542.moore@cs.utk.edu>

  | wrong.  we know now that 1918 addresses created a big mess.

No, we don't know that, because that's incorrect.   1918 addresses
are just numbers, they can't have created the mess.   The mess was created
by the demands of the users that led to the creation of the 1918 addresses.
That is, the mess would still have been there, but worse, had 1918 never
existed.

  | and nothing about IPv6 use of SLs reduces that mess.

I think it does, but even if you're right, the mess is there anyway.
It isn't going away, whatever you do with SLs.

This is just like not liking shit, so you're going to ban the sewer system.
Great plan.

  | no, you have it backwards.  SLs destroy the utility of IPv6.

There's a quote I remember that seems apt, I'm sure someone will
remember who it was said this ...

	"yawn.  I'm tired of baseless assertions."

kre






From owner-ietf@ietf.org  Sat Apr 19 18:30:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07143;
	Sat, 19 Apr 2003 18:30:35 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19717d-0005HM-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 18:47:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19716y-00059u-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 18:47:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07031
	for <ietf@ietf.org>; Sat, 19 Apr 2003 18:26:01 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970os-0006U9-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:28:26 -0400
Received: from mallard.mail.pas.earthlink.net ([207.217.120.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 1970os-0006U6-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:28:26 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by mallard.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1970oL-00023W-00; Sat, 19 Apr 2003 15:27:53 -0700
Date: Sat, 19 Apr 2003 18:27:35 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Valdis.Kletnieks@vt.edu
Cc: moore@cs.utk.edu, kre@munnari.OZ.AU, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419182735.425cd6fd.moore@cs.utk.edu>
In-Reply-To: <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu>
References: <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
	<200304192151.h3JLpKuL019276@turing-police.cc.vt.edu>
X-Mailer: Sylpheed version 0.8.11 (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


> > IPv6 requires renumbering when an address that has been used is no longer
> > appropriate (which will generally be because of changed topology, which
> > may be local topology changes - moving a host to a different LAN, or
> > global ones - connecting to a different provider).   That is the only
> > reason. As long as prefixes remain usable, they can keep on being used,
> > with other prefixes added as required.
> 
> Well.. all you need to do to fix this is to make a rule that if a
> global prefix becomes available, the site-local prefix is no longer
> appropriate and must be withdrawn.

this only solves one of several problems with site-locals, and it removes one
of the few supposed benefits of site-locals - that such addresses will be
stable across prefix changes.



From owner-ietf@ietf.org  Sat Apr 19 18:32:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04617;
	Sat, 19 Apr 2003 17:46:45 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1970Px-0003Ps-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 18:02:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1970NW-00031p-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 18:00:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04368
	for <ietf@ietf.org>; Sat, 19 Apr 2003 17:39:05 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19705R-00064R-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:41:29 -0400
Received: from falcon.mail.pas.earthlink.net ([207.217.120.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 19705Q-00064G-00
	for ietf@ietf.org; Sat, 19 Apr 2003 17:41:29 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by falcon.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19704o-0000bR-00; Sat, 19 Apr 2003 14:40:50 -0700
Date: Sat, 19 Apr 2003 17:40:32 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: moore@cs.utk.edu, kre@munnari.OZ.AU, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419174032.034ebf1d.moore@cs.utk.edu>
In-Reply-To: <005301c306ba$ec1775b0$93b58742@ssprunk>
References: <16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<20030419151329.66daf0de.moore@cs.utk.edu>
	<005301c306ba$ec1775b0$93b58742@ssprunk>
X-Mailer: Sylpheed version 0.8.11 (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 detest NAT and private addresses nearly as much as you do, but the simple
> matter is that many, if not most, people are going to continue using these
> technologies with IPv6 whether the IETF standardizes it or not.

yawn.  I'm tired of baseless assertions.

many of the reasons for using NAT do not apply to IPv6.   if you're going
to use NAT, you may as well use IPv4.  a big reason to move to IPv6 is to
get away from the problems that are caused by NATted IPv4 networks.

Keith



From owner-ietf@ietf.org  Sat Apr 19 18:34:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07457;
	Sat, 19 Apr 2003 18:34:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1971AO-0005g8-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 18:50:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19718y-0005V5-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 18:49:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07058
	for <ietf@ietf.org>; Sat, 19 Apr 2003 18:28:05 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970qs-0006UN-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:30:30 -0400
Received: from ip29.coe.tnet.co.th ([203.146.155.29] helo=fuchsia.home)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970qq-0006UK-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:30:29 -0400
Received: from delta.cs.mu.OZ.AU (delta.ex0.home [192.168.192.22]) by fuchsia.home with ESMTP
	id h3JMUDYI006890; Sun, 20 Apr 2003 05:30:13 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h3JMMbs16390;
	Sun, 20 Apr 2003 05:22:37 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Valdis.Kletnieks@vt.edu
cc: Dave Crocker <dcrocker@brandenburg.com>, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A simple question 
In-Reply-To: <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> 
References: <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu>  <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 20 Apr 2003 05:22:37 +0700
Message-ID: <16388.1050790957@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Sat, 19 Apr 2003 17:51:19 -0400
    From:        Valdis.Kletnieks@vt.edu
    Message-ID:  <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu>

  | So if it's expected that both global and site-local addresses are available,
  | why are we bothering with making things more complicated?

Because we need stable addresses for local use.

Something tells me you've never actually lived in an environment where your
global address changes moderately frequently.   If you had, you wouldn't
be so quick to ignore this need.

  | That's exactly *why* they're broken - if you've suddenly had a global
  | address show up, there's now a danger of leaking a local address, so it's
  | not safe to use site-local anymore.

What is the danger here, and why do I, the user, care?   What I know is
that I want me local communications to just keep on working smoothly,
whatever happens to external connectivity and the addresses I get from
there.

  | Well.. all you need to do to fix this is to make a rule that if a
  | global prefix becomes available, the site-local prefix is no longer
  | appropriate and must be withdrawn.

Can't possibly work.

  | This *still* leaves the problem of using site-local behind a NAT, though.

First, while I can imagine people existing who would be stupid enough to
do that, I find it hard to figure out what their reasoning would be.

But if you assume that there are people (and there most probably are) who
are so sold on the "benefits" of NAT, that they're going to use NAT no
matter how much you show them that there is in fact no benefit at all
(which for a site with an IPv6 global /48, and site locals, is certainly
true) then why would you care what address they're using behind the NAT?
That is, whether it is SL, LL, or some random "global" prefix they calculated
by tossing coins.

I find it almost inconceivable to believe that anyone is deciding the fate
of SL addressing by reference to NAT - that's simply too ludicrous (and sad)
to contemplate.

kre




From owner-ietf@ietf.org  Sat Apr 19 18:40:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07698;
	Sat, 19 Apr 2003 18:40:40 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1971H9-00075x-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 18:57:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1971E4-0006ag-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 18:54:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07445
	for <ietf@ietf.org>; Sat, 19 Apr 2003 18:33:22 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970vz-0006ax-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:35:47 -0400
Received: from garlic.amaranth.net ([208.254.46.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1970vy-0006au-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:35:46 -0400
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226])
	(authenticated (0 bits))
	by garlic.amaranth.net (8.11.7/8.11.7) with ESMTP id h3JMa2809672
	(using TLSv1/SSLv3 with cipher RC4-SHA (128 bits) verified NO);
	Sat, 19 Apr 2003 18:36:03 -0400
Message-Id: <5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Sat, 19 Apr 2003 18:35:11 -0400
To: "Stephen Sprunk" <stephen@sprunk.org>
From: Daniel Senie <dts@senie.com>
Subject: Re: A simple question
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
In-Reply-To: <005401c306ba$ecdd5dc0$93b58742@ssprunk>
References: <20030419151329.66daf0de.moore@cs.utk.edu>
 <16890640984.20030419070719@brandenburg.com>
 <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com>
 <a05210603bac6d68105ed@[10.0.0.3]>
 <11870.1050777166@munnari.OZ.AU>
 <14384.1050784134@munnari.OZ.AU>
 <20030419165921.782a8353.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 05:28 PM 4/19/2003, you wrote:
>IP networks not connected to the Internet have become
>vanishingly rare.

Umm, how do you know? If they're not connected, you may just not be aware 
of them. Please let's not base standards work on unquantified assumptions.

Example of usage: I use RFC 1918 space for private networks within server 
farms. There's no connection to the public network from this private 
segment. Servers connect to both public and private networks. Backups, NFS 
mounts, SNMP and SQL data flows over the private network. The isolated 
network segment keeps traffic off the public network for performance reasons.

In my experience it's common to find configurations of this sort in server 
farms. Often the setups use several levels of isolated networks, with VPN 
access for administrative users. Sometimes it's done as a 
belt-and-suspenders, providing a measure of additional protection (if you 
can't route packets, they won't come) beyond whatever protections are in 
firewall and server configurations, but more often it's for performance 
reasons.

All the world of private addressing is not NAT, regardless of how many 
times people say it is.

Now back to the IPv6 discussion.

I am saddened by the fact that Tony's simple question could not be 
addressed. Site local addressing in IPv6 is a concept which has been 
mentioned in RFC 1884, 2373 and 3513, the progression of Proposed 
Standards. This is a string of documents dating back to 1995. For eight 
years this concept was apparently considered a good thing. The discussion 
on the mailing lists makes it sound like site-local addressing is a new 
idea. I'd like to know why it's taken eight years for folks to decide it's 
bad. Is it that folks are just now implementing IPv6? Is it because the 
documents these eight years never made the concept clear, and now it 
appears too hard to implement? In all those years, has no vendor 
implemented site local? Are there any other features we should reconsider 
as long as we're ripping the documents open?

It is not unprecedented to change or remove a feature as a document 
advances through the standards track. Such changes, however, can have 
significant impact on already-implemented and deployed solutions. Such 
matters should be considered carefully in that light. Perhaps removal of 
features should receive substantially more scrutiny after publication on 
the standards track.






From owner-ietf@ietf.org  Sat Apr 19 18:43:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07879;
	Sat, 19 Apr 2003 18:43:04 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1971HA-00076E-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 18:57:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1971FC-0006hB-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 18:55:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07492
	for <ietf@ietf.org>; Sat, 19 Apr 2003 18:34:32 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970x6-0006b7-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:36:56 -0400
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1970x6-0006b3-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:36:56 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1970wP-00077q-00; Sat, 19 Apr 2003 15:36:14 -0700
Date: Sat, 19 Apr 2003 18:35:55 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: moore@cs.utk.edu, Valdis.Kletnieks@vt.edu, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419183555.2ce07295.moore@cs.utk.edu>
In-Reply-To: <15757.1050788984@munnari.OZ.AU>
References: <20030419172713.4c34e197.moore@cs.utk.edu>
	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
	<15757.1050788984@munnari.OZ.AU>
X-Mailer: Sylpheed version 0.8.11 (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

>   | not to encourage that error to the point that it became common
>   | practice (as has happened).
> 
> Usage alters to meet the demands of the users.  That's nothing new.
> 
>   | on the contrary, having an enterprise use both SLs and globals creates
>   | significant new problems of its own, and results in even less
>   | flexibility than if SLs were used only by isolated networks.
> 
> Nothing that IPv4 doesn't have as well (if perhaps less commonly).

there's a reason that most v4 hosts don't have multiple addresses with varying
scopes - it doesn't work well, and it creates problems for apps.  putting
sitelocals in v6 is trying to impose those problems on all host.

>   | multiple addresses at a node were available in IPv4, but the problems
>   | associated with doing this have never been solved, not even in IPv6.
> 
> True.   But it is still used regardless.   There are unsolved problems
> should be a challenge, not something to fear.

by that logic we should make the architecture as 'challenging' as possible.
personally I think getting the network to work well is enough of a challenge
without adding needless complexity.

>   | so while having multiple prefixes per node is clearly useful for
>   | renumbering,
> 
> Yes - but more than that - as long as addresses reflect topology, multiple
> addresses are the only way to have multiple topological attachments,
> aren't they?

yes there are other justifications for multiple prefixes.  I think that
overall they are valuable enough that I'm not suggesting that we get rid of
them.  what we need to do is to get rid of the idea that it matters which
address you use.

> So, unless there's some routing revolution, you're just going to have
> to learn to deal with multiple addresses, and unless LL addresses go
> away, you're also going to have to deal with scoped addresses.

LL use can and should be reserved for bootstrapping and diagnostics.

> That is, merging site locals would only be an issue of site locals are
> actively being used - if they're useless, and problematic, as you're
> claiming, then surely people won't be using them (the "I can't get enough
> address space" excuse for using 1918 addresses won't exist after all).

SLs aren't useless - it's just that their use causes so many problems
that we're better off providing that functionality in other ways.

> So, if you're worried about this, then you must be assuming that they
> will in fact be used - which to me means, that you can see that there is
> actually a demand for something to solve the problems that (apparently)
> only SL addresses currently can do (that's obvious, as if there was some
> other available solution, then people would use that, rather than these
> problematic SL things, wouldn't they???)

no, it's the other way around - the expectation of using SLs thus far has
pre-empted development of better solutions.  (by your logic the network
already works as well as it possibly can, if a better network were possible
then it would exist, wouldn't it?)

> Until we have that, and agree that it is a better design, let's just agree
> that there really is no choice - we either keep SLs in the design 

we've already agreed to get rid of them.  it's just that some people are in
denial about that.



From owner-ietf@ietf.org  Sat Apr 19 18:43:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07947;
	Sat, 19 Apr 2003 18:43:58 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1971HA-00076j-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 18:57:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1971Fb-0006pj-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 18:56:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07516
	for <ietf@ietf.org>; Sat, 19 Apr 2003 18:34:56 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1970xV-0006bo-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:37:21 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1970xU-0006bj-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:37:20 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h3JMbblv027870
	for ietf@ietf.org env-from <vjs>;
	Sat, 19 Apr 2003 16:37:37 -0600 (MDT)
Date: Sat, 19 Apr 2003 16:37:37 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200304192237.h3JMbblv027870@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: A simple question
References: <14384.1050784134@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Robert Elz <kre@munnari.OZ.AU>
> To: Keith Moore <moore@cs.utk.edu>

>   | > No, it isn't.   It is a cleaned up replacement for 1918 addresses.
>   | which by itself is reason enough to kill it.
>
> Nothing of the kind.   1918 addresses were created because there was
> demonstrated demand for stable local use only addressing.   Nothing
> has changed in the Internet to cause that demand to go away.
>
> We either provide a mechanism, or the users provide one of their own.

There's something about this long controversy I don't udnerstand.
Why do you need to provide any mechanism that does not already exist?
Do you want to prevent people from using RFC 1918 addresses mapped to
IPv6 addresses in the usual way?  Could you prevent that use of RFC 1918
addresses if you wanted to?

What about the new IPv4 site-local, automatically allocated addresses?
Do you want to prevent their use as IPv6 mapped addresses?  Could you?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sat Apr 19 18:50:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08251;
	Sat, 19 Apr 2003 18:50:13 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1971Qt-0000Px-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 19:07:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1971P7-00006A-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 19:05:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08085
	for <ietf@ietf.org>; Sat, 19 Apr 2003 18:44:47 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197171-0006lT-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:47:11 -0400
Received: from falcon.mail.pas.earthlink.net ([207.217.120.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 197171-0006lQ-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:47:11 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by falcon.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19716R-00025Q-00; Sat, 19 Apr 2003 15:46:35 -0700
Date: Sat, 19 Apr 2003 18:46:17 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: moore@cs.utk.edu, kre@munnari.OZ.AU, Valdis.Kletnieks@vt.edu,
        dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419184617.1e8e5a60.moore@cs.utk.edu>
In-Reply-To: <00d001c306c0$faeadf90$93b58742@ssprunk>
References: <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
	<00d001c306c0$faeadf90$93b58742@ssprunk>
X-Mailer: Sylpheed version 0.8.11 (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 had always planned on using only SL addresses within the enterprise, and
> then NATing those SLs to public addresses at the ISP. 

we can't stop you from screwing up your network.  just don't expect us to
endorse such practices, and don't expect apps to work across your network
boundary.

> That way, none of the
> enterprise network is polluted with (frequently changing) global
> addresses -- just like common IPv4 practice today.

and the network is dysfunctional, just like common IPv4 practice today.



From owner-ietf@ietf.org  Sat Apr 19 18:50:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08252;
	Sat, 19 Apr 2003 18:50:13 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1971N0-0007tr-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 19:03:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1971Ml-0007o2-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 19:03:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07872
	for <ietf@ietf.org>; Sat, 19 Apr 2003 18:42:21 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19714f-0006hq-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:44:45 -0400
Received: from albatross.mail.pas.earthlink.net ([207.217.120.120])
	by ietf-mx with esmtp (Exim 4.12)
	id 19714f-0006hn-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:44:45 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by albatross.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 197145-0003TF-00; Sat, 19 Apr 2003 15:44:09 -0700
Date: Sat, 19 Apr 2003 18:43:51 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: moore@cs.utk.edu, dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419184351.55785a28.moore@cs.utk.edu>
In-Reply-To: <16250.1050790406@munnari.OZ.AU>
References: <20030419174221.7111b542.moore@cs.utk.edu>
	<20030419165921.782a8353.moore@cs.utk.edu>
	<20030419151329.66daf0de.moore@cs.utk.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14384.1050784134@munnari.OZ.AU>
	<15314.1050787340@munnari.OZ.AU>
	<16250.1050790406@munnari.OZ.AU>
X-Mailer: Sylpheed version 0.8.11 (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

>   | wrong.  we know now that 1918 addresses created a big mess.
> 
> No, we don't know that, because that's incorrect.   1918 addresses
> are just numbers, they can't have created the mess.   The mess was created
> by the demands of the users that led to the creation of the 1918 addresses.
> That is, the mess would still have been there, but worse, had 1918 never
> existed.

not clear.  as someone pointed out, the intended use case for 1918 has all but
disappeared, so maybe we wouldn't have had such a mess afterall. 

of course we would have had to have some kind of scoped addresses by now
anyway due to the address shortage in v4.  that doesn't justify putting them
in v6.

>   | and nothing about IPv6 use of SLs reduces that mess.
> 
> I think it does, but even if you're right, the mess is there anyway.
> It isn't going away, whatever you do with SLs.
> 
> This is just like not liking shit, so you're going to ban the sewer system.

well, the damage caused by SLs spreads to every aspect of the network from
apps on down.  so having SLs in v6 is like saying that since we are going to
have shit no matter what we do, we might as well spread it everywhere rather
than try to promote any kind of sanitation.

Keith



From owner-ietf@ietf.org  Sat Apr 19 18:52:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08517;
	Sat, 19 Apr 2003 18:52:00 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1971Sn-0000Zm-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 19:09:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1971SR-0000Va-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 19:09:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08236
	for <ietf@ietf.org>; Sat, 19 Apr 2003 18:48:12 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1971AL-0006oN-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:50:37 -0400
Received: from ip29.coe.tnet.co.th ([203.146.155.29] helo=fuchsia.home)
	by ietf-mx with esmtp (Exim 4.12)
	id 1971AJ-0006oK-00
	for ietf@ietf.org; Sat, 19 Apr 2003 18:50:36 -0400
Received: from delta.cs.mu.OZ.AU (delta.ex0.home [192.168.192.22]) by fuchsia.home with ESMTP
	id h3JMoKYI007107; Sun, 20 Apr 2003 05:50:20 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h3JMgNs16764;
	Sun, 20 Apr 2003 05:42:26 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: "Stephen Sprunk" <stephen@sprunk.org>
cc: Valdis.Kletnieks@vt.edu, "Dave Crocker" <dcrocker@brandenburg.com>,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question 
In-Reply-To: <00d001c306c0$faeadf90$93b58742@ssprunk> 
References: <00d001c306c0$faeadf90$93b58742@ssprunk>  <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 20 Apr 2003 05:42:23 +0700
Message-ID: <16762.1050792143@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Sat, 19 Apr 2003 17:13:55 -0500
    From:        "Stephen Sprunk" <stephen@sprunk.org>
    Message-ID:  <00d001c306c0$faeadf90$93b58742@ssprunk>

  | To assign more than one address to every host means the host must have an
  | intelligent means of deciding which address to use.

Yes, but the amount of intelligence actually needed is pretty minimal.
(It is actually harder to decide between multiple available global
prefixes, than to decide between global and site local - the former is
a difficult problem, the latter is almost trivial).

  | I don't trust the hosts (either OS or the user) with that decision
  | any more than I trust them with QOS.

But you do trust them to select a suitable outgoing interface, to
pick a usable router, and to choose amongst several different possible
addresses for the destination (over which you most often have no control).

This all seems rather arbitrary.

Forcing NAT on hosts & users because you're afraid that the OS/app
designers can't tell what's global and what is site local seems rather
heavy handed.   I'm sure glad I don't have to live with your policies.

kre





From owner-ietf@ietf.org  Sat Apr 19 19:21:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09195;
	Sat, 19 Apr 2003 19:21:15 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1971tm-0003DW-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 19:37:34 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1971pt-0002xF-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 19:33:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09071
	for <ietf@ietf.org>; Sat, 19 Apr 2003 19:12:25 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1971Xm-00070G-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:14:50 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1971Xm-00070D-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:14:50 -0400
Received: (from braden@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h3JNBj206700;
	Sat, 19 Apr 2003 16:11:45 -0700 (PDT)
Date: Sat, 19 Apr 2003 16:11:45 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Message-Id: <200304192311.h3JNBj206700@boreas.isi.edu>
To: moore@cs.utk.edu, kre@munnari.OZ.AU
Subject: Re: A simple question
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


There are no simple questions.

Bob Braden



From owner-ietf@ietf.org  Sat Apr 19 19:32:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09622;
	Sat, 19 Apr 2003 19:32:34 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19725V-0004UP-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 19:49:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1971wB-0003SS-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 19:40:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09157
	for <ietf@ietf.org>; Sat, 19 Apr 2003 19:18:56 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1971e5-00071i-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:21:21 -0400
Received: from gull.mail.pas.earthlink.net ([207.217.120.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 1971e4-00071f-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:21:20 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1971dS-0000dM-00; Sat, 19 Apr 2003 16:20:42 -0700
Date: Sat, 19 Apr 2003 19:20:24 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: moore@cs.utk.edu, stephen@sprunk.org, Valdis.Kletnieks@vt.edu,
        dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419192024.440d3773.moore@cs.utk.edu>
In-Reply-To: <16762.1050792143@munnari.OZ.AU>
References: <00d001c306c0$faeadf90$93b58742@ssprunk>
	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
	<16762.1050792143@munnari.OZ.AU>
X-Mailer: Sylpheed version 0.8.11 (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

>   | To assign more than one address to every host means the host must have
>   | an intelligent means of deciding which address to use.
> 
> Yes, but the amount of intelligence actually needed is pretty minimal.
> (It is actually harder to decide between multiple available global
> prefixes, than to decide between global and site local - the former is
> a difficult problem, the latter is almost trivial).

disagree.  the app can choose any global prefix and reasonably expect it to
work, modulo link failures. but when choosing between a global and a site
local the app needs to know whether the site local address will be valid for
the hosts that need to use it, and it has no way to know this.   the app may
also have to choose which interface to use with the site-local prefix,
and it has no good way to know this either.



From owner-ietf@ietf.org  Sat Apr 19 19:32:58 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09664;
	Sat, 19 Apr 2003 19:32:58 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19725V-0004UV-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 19:49:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1971xC-0003Sf-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 19:41:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09172
	for <ietf@ietf.org>; Sat, 19 Apr 2003 19:19:59 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1971f5-00071u-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:22:23 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 1971f5-00071r-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:22:23 -0400
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h3JNM0gE027832;
	Sat, 19 Apr 2003 16:22:01 -0700 (PDT)
Received: (from otroan@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id AAA04888;
	Sun, 20 Apr 2003 00:22:00 +0100 (BST)
X-Authentication-Warning: mrwint.cisco.com: otroan set sender to ot@cisco.com using -f
To: Keith Moore <moore@cs.utk.edu>
Cc: Robert Elz <kre@munnari.OZ.AU>, Valdis.Kletnieks@vt.edu,
        dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
From: Ole Troan <ot@cisco.com>
Date: Sun, 20 Apr 2003 00:22:00 +0100
In-Reply-To: <20030419183555.2ce07295.moore@cs.utk.edu> (Keith Moore's
 message of "Sat, 19 Apr 2003 18:35:55 -0400")
Message-ID: <7t5y926844n.fsf@mrwint.cisco.com>
User-Agent: Gnus/5.090019 (Oort Gnus v0.19) Emacs/21.2.95 (usg-unix-v)
References: <20030419172713.4c34e197.moore@cs.utk.edu>
	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU> <15757.1050788984@munnari.OZ.AU>
	<20030419183555.2ce07295.moore@cs.utk.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

[...]

>> So, unless there's some routing revolution, you're just going to have
>> to learn to deal with multiple addresses, and unless LL addresses go
>> away, you're also going to have to deal with scoped addresses.
>
> LL use can and should be reserved for bootstrapping and diagnostics.

LL is used in applications already. e.g LL addresses are commonly used
to address BGP endpoints on exchanges. so unless you suggest to remove
LL addresses (and MPLS VPNs) implementations will need to handle
ambiguous and topologically scoped addresses, even without
site-locals.

/ot



From owner-ietf@ietf.org  Sat Apr 19 19:33:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09745;
	Sat, 19 Apr 2003 19:33:39 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19725c-0004aP-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 19:49:48 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19723z-0004Hl-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 19:48:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09547
	for <ietf@ietf.org>; Sat, 19 Apr 2003 19:27:00 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1971lt-00078G-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:29:25 -0400
Received: from out005pub.verizon.net ([206.46.170.143] helo=out005.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1971ls-00078D-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:29:24 -0400
Received: from earthlink.com ([4.65.93.176]) by out005.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030419232911.RWPM25152.out005.verizon.net@earthlink.com>;
          Sat, 19 Apr 2003 18:29:11 -0500
Message-ID: <3EA1DAE4.8D2A7433@earthlink.com>
Date: Sat, 19 Apr 2003 16:25:24 -0700
From: Peter Deutsch <pdeutsch@earthlink.com>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Bob Braden <braden@ISI.EDU>
CC: moore@cs.utk.edu, kre@munnari.OZ.AU, ietf@ietf.org
Subject: Re: A simple question
References: <200304192311.h3JNBj206700@boreas.isi.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from [4.65.93.176] at Sat, 19 Apr 2003 18:29:11 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Bob Braden wrote:
> 
> There are no simple questions.

Sure there are. There are just no simple answers....



		- peterd (except maybe "42"...)



-- 

---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software


  "It is inhumane, in my opinion, to force people who have a
   genuine medical need for coffee to wait in line behind people
   who apparently view it as some kind of recreational activity."

                                        -- Dave Barry

---------------------------------------------------------------------



From owner-ietf@ietf.org  Sat Apr 19 19:52:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10418;
	Sat, 19 Apr 2003 19:52:44 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1972Mw-00072O-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 20:07:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1972Mn-0006xG-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 20:07:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10356
	for <ietf@ietf.org>; Sat, 19 Apr 2003 19:46:25 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19724g-0007LO-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:48:50 -0400
Received: from h80ad2453.async.vt.edu ([128.173.36.83] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19724f-0007LL-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:48:49 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h3JNmxuL020301;
	Sat, 19 Apr 2003 19:48:59 -0400
Message-Id: <200304192348.h3JNmxuL020301@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Robert Elz <kre@munnari.OZ.AU>
Cc: Dave Crocker <dcrocker@brandenburg.com>, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A simple question 
In-Reply-To: Your message of "Sun, 20 Apr 2003 05:22:37 +0700."
             <16388.1050790957@munnari.OZ.AU> 
References: <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU>
            <16388.1050790957@munnari.OZ.AU>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-2117529098P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sat, 19 Apr 2003 19:48:58 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-2117529098P
Content-Type: text/plain; charset=us-ascii

On Sun, 20 Apr 2003 05:22:37 +0700, Robert Elz said:
> What is the danger here, and why do I, the user, care?   What I know is
> that I want me local communications to just keep on working smoothly,
> whatever happens to external connectivity and the addresses I get from
> there.

Right.  You the user *don't* care.  

Users are almost never network admins.  And the network admins presumably
care (although with the amount of 1918 leakage we see, that's a dubious
assertion as well).

>   | Well.. all you need to do to fix this is to make a rule that if a
>   | global prefix becomes available, the site-local prefix is no longer
>   | appropriate and must be withdrawn.
> 
> Can't possibly work.

How is it any different than any *other* prefix becoming not appropriate
and being withdrawn?

There's this big assumption on the part of the pro-site-local crew that
we "need" a stable address.  I posit that this is a crock, and that
what we *need* to do is iron out the rough edges of IPv6 renumbering
so hosts don't care *what* they have, as long as they have *some*
prefix.


--==_Exmh_-2117529098P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+oeBqcC3lWbTT17ARAu7AAJ9We8v30HpTPRZVEaA1av1h352/NgCguJce
0HEpwkIMRBh14iiVrTTSg04=
=v0y3
-----END PGP SIGNATURE-----

--==_Exmh_-2117529098P--



From owner-ietf@ietf.org  Sat Apr 19 19:59:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10664;
	Sat, 19 Apr 2003 19:59:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1972Vd-0008Kf-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 20:16:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1972VX-0008Fj-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 20:16:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10595
	for <ietf@ietf.org>; Sat, 19 Apr 2003 19:55:27 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972DQ-0007P8-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:57:52 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972DP-0007P4-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:57:52 -0400
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h3JNvp129130;
	Sat, 19 Apr 2003 16:57:51 -0700
Date: Sat, 19 Apr 2003 16:37:00 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <58124822595.20030419163700@brandenburg.com>
To: ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A simple question
In-Reply-To: <14570.1050784897@munnari.OZ.AU>
References: <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
 <16890640984.20030419070719@brandenburg.com>
 <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]>
 <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU>
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

Folks,

RE> First, they're clearly of local use (defined in the
RE> architecture), hence if they do leak, at least it is obvious what is
RE> happening.

And, yes, that sounds like 1918, for which there are no new
requirements.

oh. but wait. we *have* been given new requirements, including the
suggestion that applications now need to know about different kinds of
addresses.

Forgive me, but I do not recall that requirement being imposed in the
days of 1918, and could have sworn that it was something new. Such a
requirement only comes from a significant change to the architecture,
and that was my original contention.

(I really do wish folks would check their various *-bashing arguments at
the door.  I have no desire to re-live diatribes against NATs or even
1918, though it's worth noting that those caveats in 1918 only got there
because a few of us put up a fuss at the time.  At any rate, the
question at hand is about new-vs-old architecture, so could we please
focus on it?)


RE> Is not true for site locals, as no-one anticpiates that a SL address is
RE> all an enterprise will be using

And since that was also true in IPv4, we have nothing new, right?

Oh.

You mean SLs are only interesting because they derive from a very new
architectural feature, and we are only now trying to think through the
implications, and those implications are turning out to be widespread?

So, folks, could we please return to the content issue I tried to raise:

DC> site local is, in fact, an addition to the IP architecture and that is
DC> what is causing the controversy.  For example, it has prompted the
DC> suggestion that applications be made to know the difference between site
DC> local vs. global IP addresses.
DC>
DC> When we go around making basic additions to an architecture, we should
DC> try to be very clear on how it will be used, how it will impact the rest
DC> of the architecture, and what the benefits and problems are likely to
DC> be.



RE> is not true of SL addresses, as one doesn't "renumber" them, one just
RE> augments with a global address.

I like the "just". As in, one "just" re-design the Internet's applications.


RE> You may notice that it isn't *just* site locals that provide the cleanup
RE> here, it is the whole IPv6 architecture, considered as a whole.

Dandy.  Glad to move my query to the "as a whole".  Any relevant list of
benefits and detriments will be a constructive start.

However not just idealized, conceptual benefits, but thinking that shows
some dirt under the fingernails, from foraging through the messy details
of making this stuff work in a real-world system.

My own guess is that the implications have *not* been drawn. Hence
roughly 9 years years after the first draft of IPv6, we get broad
suggestions to make applications know about different kinds of
addresses.

The other requirement for differential address handling -- local-net vs.
routed -- is handled at the IP layer and is invisible to applications.
It is computationally cheap and offers a very, very big benefit, by
avoiding the choke-point hop through the local router.

Someone needs to provide a similar analysis for SLs, or any other sort
of major change to the architecture.

For example, note that dropping header checksums from IPv6 was, shall we
say, a rather astonishing suggestion, but Deering readily produced very
solid arguments for the benefits and very solid arguments showing a lack
of detriments.

Why is it unreasonable to expect the same for other such changes?


d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Sat Apr 19 19:59:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10720;
	Sat, 19 Apr 2003 19:59:39 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1972Ve-0008Kl-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 20:16:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1972VY-0008Fl-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 20:16:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10599
	for <ietf@ietf.org>; Sat, 19 Apr 2003 19:55:28 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972DR-0007PD-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:57:53 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972DQ-0007P5-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:57:52 -0400
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h3JNvq129134;
	Sat, 19 Apr 2003 16:57:53 -0700
Date: Sat, 19 Apr 2003 16:47:12 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <70125434335.20030419164712@brandenburg.com>
To: ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Architectural Considerations section in specs
In-Reply-To: <5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
References: <20030419151329.66daf0de.moore@cs.utk.edu>
 <16890640984.20030419070719@brandenburg.com>
 <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]>
 <11870.1050777166@munnari.OZ.AU> <14384.1050784134@munnari.OZ.AU>
 <20030419165921.782a8353.moore@cs.utk.edu>
 <5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
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

Folks,

DS> I am saddened by the fact that Tony's simple question could not be
DS> addressed. Site local addressing in IPv6 is a concept which has been
DS> mentioned in RFC 1884, 2373 and 3513, the progression of Proposed 
DS> Standards. This is a string of documents dating back to 1995. For eight
DS> years this concept was apparently considered a good thing.

The problem appears to have been that no one bothered to draw the
necessary implications and circulate them for explicit consideration. So
folks scanned a spec, didn't see anything that looked egregious, and
only now are realizing how extensive the impact is.

We have a very basic, very serious problem with coordination among
different parts of the IETF.  Our tendency is to task various folks with
doing a better "monitoring" job.

My guess is that, instead, we *all* need to do a better job of noticing
when we are specifying something that has an architectural impact, by
which I mean something that affects other parts of the Internet service.

Once upon a time, the Security Considerations section was pro forma.
These days, it is taken seriously, and specifications are required to
develop this section carefully.

More recently we have added IANA Considerations sections, to make sure
that administrative issues are handled more easily.

Perhaps it is time to require specifications to make explicit statements
about the impact the spec's features will have on architectural
providers and consumers. That is, the features of a specification draw
on system Internet services "below" and give services to parts of the
system "above".

Any specification that creates interesting features should be required
to specify its requirements on providers and its impact on consumers.

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Sat Apr 19 20:04:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10998;
	Sat, 19 Apr 2003 20:04:42 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1972bB-00010a-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 20:22:25 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1972ZO-0000EW-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 20:20:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10700
	for <ietf@ietf.org>; Sat, 19 Apr 2003 19:59:26 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972HH-0007QL-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:01:51 -0400
Received: from swan.mail.pas.earthlink.net ([207.217.120.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1972HH-0007QH-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:01:51 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by swan.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1972Ga-0005Pw-00; Sat, 19 Apr 2003 17:01:08 -0700
Date: Sat, 19 Apr 2003 20:00:49 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Ole Troan <ot@cisco.com>
Cc: moore@cs.utk.edu, kre@munnari.OZ.AU, Valdis.Kletnieks@vt.edu,
        dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419200049.2b0dd5f2.moore@cs.utk.edu>
In-Reply-To: <7t5y926844n.fsf@mrwint.cisco.com>
References: <20030419172713.4c34e197.moore@cs.utk.edu>
	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
	<15757.1050788984@munnari.OZ.AU>
	<20030419183555.2ce07295.moore@cs.utk.edu>
	<7t5y926844n.fsf@mrwint.cisco.com>
X-Mailer: Sylpheed version 0.8.11 (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

> > LL use can and should be reserved for bootstrapping and diagnostics.
> 
> LL is used in applications already. e.g LL addresses are commonly used
> to address BGP endpoints on exchanges. 

I don't think of BGP as operating at level 7.

I don't have a problem with LL being used for a few special-purpose things
that can deal with it, so long as we don't expect LL to work for all or even
most apps.




From owner-ietf@ietf.org  Sat Apr 19 20:07:05 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11178;
	Sat, 19 Apr 2003 20:07:05 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1972dS-0001K4-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 20:24:46 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1972d1-0001Ew-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 20:24:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10976
	for <ietf@ietf.org>; Sat, 19 Apr 2003 20:03:11 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972Ku-0007Vf-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:05:36 -0400
Received: from buffoon.automagic.org ([208.185.30.208] ident=qmailr)
	by ietf-mx with smtp (Exim 4.12)
	id 1972Kt-0007Vc-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:05:35 -0400
Received: (qmail 76034 invoked by uid 0); 20 Apr 2003 00:05:53 -0000
Received: from localhost.automagic.org (HELO isc.org) (root@127.0.0.1)
  by localhost.automagic.org with SMTP; 20 Apr 2003 00:05:53 -0000
Date: Sat, 19 Apr 2003 20:06:10 -0400
Subject: Re: A simple question
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Keith Moore <moore@cs.utk.edu>, Robert Elz <kre@munnari.OZ.AU>,
        Valdis.Kletnieks@vt.edu, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
To: Ole Troan <ot@cisco.com>
From: Joe Abley <jabley@isc.org>
In-Reply-To: <7t5y926844n.fsf@mrwint.cisco.com>
Message-Id: <E46D2CB2-72C3-11D7-A6E0-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Saturday, Apr 19, 2003, at 19:22 Canada/Eastern, Ole Troan wrote:

> [...]
>
>>> So, unless there's some routing revolution, you're just going to have
>>> to learn to deal with multiple addresses, and unless LL addresses go
>>> away, you're also going to have to deal with scoped addresses.
>>
>> LL use can and should be reserved for bootstrapping and diagnostics.
>
> LL is used in applications already. e.g LL addresses are commonly used
> to address BGP endpoints on exchanges.

What exchanges do that?


Joe




From owner-ietf@ietf.org  Sat Apr 19 20:07:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09193;
	Sat, 19 Apr 2003 19:21:15 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1971uA-0003I3-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 19:37:58 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1971qS-00033Z-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 19:34:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09078
	for <ietf@ietf.org>; Sat, 19 Apr 2003 19:12:48 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1971Y9-00070M-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:15:13 -0400
Received: from pintail.mail.pas.earthlink.net ([207.217.120.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1971Y9-00070J-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:15:13 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by pintail.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1971YL-0001C3-00; Sat, 19 Apr 2003 16:15:25 -0700
Date: Sat, 19 Apr 2003 19:15:07 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Daniel Senie <dts@senie.com>
Cc: moore@cs.utk.edu, stephen@sprunk.org, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A simple question
Message-Id: <20030419191507.75dfcc39.moore@cs.utk.edu>
In-Reply-To: <5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
References: <20030419151329.66daf0de.moore@cs.utk.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14384.1050784134@munnari.OZ.AU>
	<20030419165921.782a8353.moore@cs.utk.edu>
	<5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
X-Mailer: Sylpheed version 0.8.11 (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

>  Site local addressing in IPv6 is a concept which has been 
> mentioned in RFC 1884, 2373 and 3513, the progression of Proposed 
> Standards. This is a string of documents dating back to 1995. For eight 
> years this concept was apparently considered a good thing. 

it is indeed unfortunate that it took several years before there was serious
consideration to the impact of site-local on networks, DNS, and applications. 
I view this as an indication of serious failures in our process - IPv6 was
approved (under pressure, it must be said) by the working group and IESG
despite serious technical omissions.  fortunately proposed standards are not
carved in stone, and these particular omissions are easy to fix.

> I'd like to know why it's taken eight years for folks to decide it's 
> bad.

because few serious applications people were in the discussion, and there
wasn't enough review by those people during Last Call.  most apps people
probably assumed that the changes between IPv4 and IPv6 would be transparent
to them, other than having to use a different size for the address.

also IPv6 took so long getting out the door that it was widely viewed as
on a distant horizon - something that could be dealt with when it finally
arrived (if that ever happened).

> Is it that folks are just now implementing IPv6?

no, but most of the early apps that were ported to IPv6 were two-party apps,
often apps that were used in conjunction with either a v4-v6 translator or
proxy.  many problems with SLs don't show up for these apps; they show up for
multi-party apps.  also, even though there were v6 stacks there were probably
not many early networks that made heavy use of both SLs and globals.

> It is not unprecedented to change or remove a feature as a document 
> advances through the standards track. Such changes, however, can have 
> significant impact on already-implemented and deployed solutions. Such 
> matters should be considered carefully in that light. Perhaps removal of 
> features should receive substantially more scrutiny after publication on 
> the standards track.

I don't disagree.  but surely the months of discussion on this topic qualify
as a substantial amount of scrutiny.  and surely you'd agree that features in
published documents that appear to cause problems should also receive a
substantial amount of scrutiny before advancing those documents?



From owner-ietf@ietf.org  Sat Apr 19 20:13:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11433;
	Sat, 19 Apr 2003 20:13:22 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1972fW-0001rY-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 20:26:54 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1972eb-0001Uu-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 20:25:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11023
	for <ietf@ietf.org>; Sat, 19 Apr 2003 20:04:49 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972MU-0007Vu-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:07:14 -0400
Received: from buffoon.automagic.org ([208.185.30.208] ident=qmailr)
	by ietf-mx with smtp (Exim 4.12)
	id 1972MT-0007Vq-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:07:13 -0400
Received: (qmail 76153 invoked by uid 0); 20 Apr 2003 00:07:31 -0000
Received: from localhost.automagic.org (HELO isc.org) (root@127.0.0.1)
  by localhost.automagic.org with SMTP; 20 Apr 2003 00:07:31 -0000
Date: Sat, 19 Apr 2003 19:05:10 -0400
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Valdis.Kletnieks@vt.edu, Dave Crocker <dcrocker@brandenburg.com>,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: Re: A simple question 
From: Joe Abley <jabley@isc.org>
To: Robert Elz <kre@munnari.OZ.AU>
Content-Transfer-Encoding: 7bit
Message-Id: <1F622487-72C4-11D7-A6E0-00039312C852@isc.org>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Saturday, Apr 19, 2003, at 18:22 Canada/Eastern, Robert Elz wrote:

>     Date:        Sat, 19 Apr 2003 17:51:19 -0400
>     From:        Valdis.Kletnieks@vt.edu
>     Message-ID:  <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu>
>
>   | So if it's expected that both global and site-local addresses are 
> available,
>   | why are we bothering with making things more complicated?
>
> Because we need stable addresses for local use.
>
> Something tells me you've never actually lived in an environment where 
> your
> global address changes moderately frequently.   If you had, you 
> wouldn't
> be so quick to ignore this need.

The rhetoric would have us believe that frequent renumbering with IPv6 
is seamless and effortless. I don't personally buy that, but there are 
some assumptions there that perhaps should be challenged more directly 
rather than in this oblique fashion.

If we accept the premise that frequent renumbering in IPv6 is not 
seamless and is in fact painful and worth avoiding, then rather than 
hiding the source of the pain behind a NAT perhaps we should try to 
eliminate it: find a mechanism which facilitates pervasive multi-homing 
with some stable view of layer-3 addressing from the layer above, 
across re-homing events.

That would solve multi-homing, session stability across renumbering 
events and changing providers all in one hit.

There's a party going on in multi6, and you're all invited. (well, 
we're all in the kitchen at the moment, but we'll move out onto the 
deck if more people show up).


Joe




From owner-ietf@ietf.org  Sat Apr 19 20:18:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11623;
	Sat, 19 Apr 2003 20:18:15 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1972o6-0003Ge-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 20:35:46 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1972m2-0002jb-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 20:33:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11419
	for <ietf@ietf.org>; Sat, 19 Apr 2003 20:12:31 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972Tv-0007d6-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:14:55 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 1972Tu-0007d0-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:14:54 -0400
Received: from cisco.com (mrwint.cisco.com [64.103.71.48])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h3K0EWgE020505;
	Sat, 19 Apr 2003 17:14:32 -0700 (PDT)
Received: (from otroan@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id BAA05646;
	Sun, 20 Apr 2003 01:14:31 +0100 (BST)
X-Authentication-Warning: mrwint.cisco.com: otroan set sender to ot@cisco.com using -f
To: Keith Moore <moore@cs.utk.edu>
Cc: kre@munnari.OZ.AU, Valdis.Kletnieks@vt.edu, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
From: Ole Troan <ot@cisco.com>
Date: Sun, 20 Apr 2003 01:14:30 +0100
In-Reply-To: <20030419200049.2b0dd5f2.moore@cs.utk.edu> (Keith Moore's
 message of "Sat, 19 Apr 2003 20:00:49 -0400")
Message-ID: <7t5vfxa81p5.fsf@mrwint.cisco.com>
User-Agent: Gnus/5.090019 (Oort Gnus v0.19) Emacs/21.2.95 (usg-unix-v)
References: <20030419172713.4c34e197.moore@cs.utk.edu>
	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU> <15757.1050788984@munnari.OZ.AU>
	<20030419183555.2ce07295.moore@cs.utk.edu>
	<7t5y926844n.fsf@mrwint.cisco.com>
	<20030419200049.2b0dd5f2.moore@cs.utk.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

>> > LL use can and should be reserved for bootstrapping and diagnostics.
>> 
>> LL is used in applications already. e.g LL addresses are commonly used
>> to address BGP endpoints on exchanges. 
>
> I don't think of BGP as operating at level 7.

well, BGP uses TCP as transport and most of the implementations I've
seen use POSIX socket API just like any other application. the socket
API needs let the application choose zone, and pick a suitable source
address accordingly.

> I don't have a problem with LL being used for a few special-purpose things
> that can deal with it, so long as we don't expect LL to work for all or even
> most apps.

that is a big change in the IPv6 architecture. throwing all the cards
up in the air every second year or so (anyone recorded what the
frequency is for old and closed discussions reappearing on the ipng
list?) gets rather trying after a while. perhaps about time to shut
the IPv6 W.G down?

/ot



From owner-ietf@ietf.org  Sat Apr 19 20:25:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11857;
	Sat, 19 Apr 2003 20:25:19 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1972tq-0004C7-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 20:41:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1972sR-0003wF-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 20:40:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11698
	for <ietf@ietf.org>; Sat, 19 Apr 2003 20:19:09 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972aK-0007ho-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:21:32 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972aJ-0007hh-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:21:31 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3K0LFL16921;
	Sat, 19 Apr 2003 19:21:15 -0500
Message-ID: <005e01c306d2$c1f3e030$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Robert Elz" <kre@munnari.OZ.AU>, <Valdis.Kletnieks@vt.edu>
Cc: "Dave Crocker" <dcrocker@brandenburg.com>, <ipng@sunroof.eng.sun.com>,
        <ietf@ietf.org>
References: <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu>  <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU>  <16388.1050790957@munnari.OZ.AU>
Subject: Re: A simple question 
Date: Sat, 19 Apr 2003 19:11:28 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Robert Elz" <kre@munnari.OZ.AU>
> | So if it's expected that both global and site-local addresses are
> | available, why are we bothering with making things more complicated?
>
> Because we need stable addresses for local use.

Any unique global address will work fine for local use, even if you're
disconnected from the Net.  Or do you expect your global prefix(es) to be
withdrawn from hosts every time your upstream connection flaps?

> Something tells me you've never actually lived in an environment where
> your global address changes moderately frequently.   If you had, you
> wouldn't be so quick to ignore this need.

But haven't you heard?  With IPv6, renumbering will be so easy you'll do it
for fun!  </sarcasm>

The pain renumbering is one of the main motivators for NAT today, and I have
yet to see any reason to believe it'll be easier in IPv6.

>   | Well.. all you need to do to fix this is to make a rule that if a
>   | global prefix becomes available, the site-local prefix is no longer
>   | appropriate and must be withdrawn.
>
> Can't possibly work.

If site-locals and globals are to coexist, the obvious solution is to
specify that when the destination is SL, an SL should be preferred as
source, and likewise for globals.

Of course, that doesn't fix the case where you have multiple globals, or
multiple interfaces.  We haven't figured out how to fix that with IPv4
either, except for specific cases like "backside networks".

>   | This *still* leaves the problem of using site-local behind a NAT,
though.
>
> First, while I can imagine people existing who would be stupid enough to
> do that, I find it hard to figure out what their reasoning would be.

Avoiding renumbering, avoiding exposing internal identities, etc.

It's all the same reasons you might use IPv4 NAT, with the possible
exception of address shortages.  I know several very large corps that use
legacy class B space inside and NAT to provider-assigned CIDR space
outside -- they're obviously not doing it because of address shortages,
they're doing it for administrative and scoping reasons.

> I find it almost inconceivable to believe that anyone is deciding the fate
> of SL addressing by reference to NAT - that's simply too ludicrous
> (and sad) to contemplate.

Well, IPv6 NAT proponents expected to use the SL prefix as their private
addressing, so eliminating SL will require another prefix for that purpose.
I don't see any other direct connection, however.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Sat Apr 19 20:25:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11883;
	Sat, 19 Apr 2003 20:25:24 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1972ts-0004D1-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 20:41:44 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1972sf-00040s-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 20:40:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11744
	for <ietf@ietf.org>; Sat, 19 Apr 2003 20:19:23 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972aY-0007il-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:21:46 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972aX-0007iW-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:21:45 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3K0LHL16924;
	Sat, 19 Apr 2003 19:21:17 -0500
Message-ID: <005f01c306d2$c33cdaf0$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Keith Moore" <moore@cs.utk.edu>, "Robert Elz" <kre@munnari.OZ.AU>
Cc: <moore@cs.utk.edu>, <Valdis.Kletnieks@vt.edu>, <dcrocker@brandenburg.com>,
        <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
References: <00d001c306c0$faeadf90$93b58742@ssprunk><200304191923.h3JJNOuL018209@turing-police.cc.vt.edu><16890640984.20030419070719@brandenburg.com><002401c30605$e22da070$261e4104@eagleswings><9540645034.20030418171403@brandenburg.com><a05210603bac6d68105ed@[10.0.0.3]><11870.1050777166@munnari.OZ.AU><14570.1050784897@munnari.OZ.AU><16762.1050792143@munnari.OZ.AU> <20030419192024.440d3773.moore@cs.utk.edu>
Subject: Re: A simple question
Date: Sat, 19 Apr 2003 19:19:30 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Keith Moore" <moore@cs.utk.edu>
> >   | To assign more than one address to every host means the host
> >   | must have an intelligent means of deciding which address to use.
> >
> > Yes, but the amount of intelligence actually needed is pretty minimal.
> > (It is actually harder to decide between multiple available global
> > prefixes, than to decide between global and site local - the former is
> > a difficult problem, the latter is almost trivial).
>
> disagree.  the app can choose any global prefix and reasonably expect
> it to work, modulo link failures.

Nit: the vast majority of apps today bind to INADDR_ANY (or its IPv6
equivalent), so it's really the OS which is choosing the source address.  If
the app binds a specific source address, it is invariably user-configurable
and thus not an application problem.

> but when choosing between a global and a site local the app needs to
> know whether the site local address will be valid for the hosts that need
> to use it, and it has no way to know this.

Well, since one can easily determine whether the destination address is SL
or not, picking a source address of the correct class is trivial.

> the app may also have to choose which interface to use with the site-
> local prefix, and it has no good way to know this either.

Ah, but it'll have a different SL address on each interface, so that's no
worse than having multiple global addresses.  The truly interesting case is
connecting to a LL address with multiple interfaces.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Sat Apr 19 20:30:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12260;
	Sat, 19 Apr 2003 20:30:52 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19730E-0005Ou-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 20:48:18 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1972yH-0004Zs-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 20:46:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11850
	for <ietf@ietf.org>; Sat, 19 Apr 2003 20:25:11 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972gA-0007kA-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:27:34 -0400
Received: from turkey.mail.pas.earthlink.net ([207.217.120.126])
	by ietf-mx with esmtp (Exim 4.12)
	id 1972g9-0007k7-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:27:34 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by turkey.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1972fX-000164-00; Sat, 19 Apr 2003 17:26:55 -0700
Date: Sat, 19 Apr 2003 20:26:37 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Ole Troan <ot@cisco.com>
Cc: moore@cs.utk.edu, kre@munnari.OZ.AU, Valdis.Kletnieks@vt.edu,
        dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419202637.7828bb08.moore@cs.utk.edu>
In-Reply-To: <7t5vfxa81p5.fsf@mrwint.cisco.com>
References: <20030419172713.4c34e197.moore@cs.utk.edu>
	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
	<15757.1050788984@munnari.OZ.AU>
	<20030419183555.2ce07295.moore@cs.utk.edu>
	<7t5y926844n.fsf@mrwint.cisco.com>
	<20030419200049.2b0dd5f2.moore@cs.utk.edu>
	<7t5vfxa81p5.fsf@mrwint.cisco.com>
X-Mailer: Sylpheed version 0.8.11 (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 don't have a problem with LL being used for a few special-purpose things
> > that can deal with it, so long as we don't expect LL to work for all or
> > even most apps.
> 
> that is a big change in the IPv6 architecture. 

anyone who ever thought that scoped addresses were generally applicable was
deluded.



From owner-ietf@ietf.org  Sat Apr 19 20:35:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12492;
	Sat, 19 Apr 2003 20:35:24 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19730F-0005PL-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 20:48:19 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1972yV-0004eH-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 20:46:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11892
	for <ietf@ietf.org>; Sat, 19 Apr 2003 20:25:25 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972gO-0007kH-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:27:48 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1972gN-0007kE-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:27:47 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h3K0OdY06518;
	Sat, 19 Apr 2003 17:24:39 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200304200024.h3K0OdY06518@boreas.isi.edu>
Subject: Re: A simple question
In-Reply-To: <E46D2CB2-72C3-11D7-A6E0-00039312C852@isc.org> from Joe Abley at "Apr 19, 3 08:06:10 pm"
To: jabley@isc.org (Joe Abley)
Date: Sat, 19 Apr 2003 17:24:39 -0700 (PDT)
Cc: moore@cs.utk.edu, kre@munnari.OZ.AU, Valdis.Kletnieks@vt.edu,
        dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com, ietf@ietf.org,
        ot@cisco.com
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
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

% >>> So, unless there's some routing revolution, you're just going to have
% >>> to learn to deal with multiple addresses, and unless LL addresses go
% >>> away, you're also going to have to deal with scoped addresses.
% >>
% >> LL use can and should be reserved for bootstrapping and diagnostics.
% >
% > LL is used in applications already. e.g LL addresses are commonly used
% > to address BGP endpoints on exchanges.
% 
% What exchanges do that?
% 
% 
% Joe


	Akira Kato and I had a draft out on how this could be done
	and had working, inter-operable implementations (zebra, cisco)
	in two locations, NSPIXP3 and LAIIX.  The IDR wg chose another
	method and so this technique is not likely to be widely 
	endorsed as an IETF approved method. It is still supported in
	the code and some folks still use it.


--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).



From owner-ietf@ietf.org  Sat Apr 19 20:40:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12671;
	Sat, 19 Apr 2003 20:40:21 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19739H-00073q-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 20:57:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19737o-0006c1-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 20:56:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12469
	for <ietf@ietf.org>; Sat, 19 Apr 2003 20:35:01 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972ph-00006d-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:37:25 -0400
Received: from mallard.mail.pas.earthlink.net ([207.217.120.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 1972pg-00006a-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:37:24 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by mallard.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1972oi-000751-00; Sat, 19 Apr 2003 17:36:24 -0700
Date: Sat, 19 Apr 2003 20:36:06 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: moore@cs.utk.edu, kre@munnari.OZ.AU, Valdis.Kletnieks@vt.edu,
        dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030419203606.2b6cdabc.moore@cs.utk.edu>
In-Reply-To: <005f01c306d2$c33cdaf0$93b58742@ssprunk>
References: <00d001c306c0$faeadf90$93b58742@ssprunk>
	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
	<16762.1050792143@munnari.OZ.AU>
	<20030419192024.440d3773.moore@cs.utk.edu>
	<005f01c306d2$c33cdaf0$93b58742@ssprunk>
X-Mailer: Sylpheed version 0.8.11 (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

> > > (It is actually harder to decide between multiple available global
> > > prefixes, than to decide between global and site local - the former is
> > > a difficult problem, the latter is almost trivial).
> >
> > disagree.  the app can choose any global prefix and reasonably expect
> > it to work, modulo link failures.
> 
> Nit: the vast majority of apps today bind to INADDR_ANY (or its IPv6
> equivalent), so it's really the OS which is choosing the source address.

one of the problems introduced by scoped addresses is that this is no longer
sufficient for some kinds of apps.

> If the app binds a specific source address, it is invariably
> user-configurable and thus not an application problem.

or to put it more clearly, the only way an app can choose reasonably
between multiple addresses of varying scopes is to be explicitly configured as
to how to do so.  otherwise, the app has no idea whether one scope or another
is more suitable for its purposes.   any assumptions about whether, for
instance, site-locals are more secure or more stable than globals, or
whether the app will need to communicate with off-site nodes, need to be
explicitly configured.

of course, if the app weren't being forced to choose between addresses of
differing scopes then it wouldn't need to bind to specific source addresses
(no more than v4 apps do), and such configuration would not be necessary.

> > but when choosing between a global and a site local the app needs to
> > know whether the site local address will be valid for the hosts that need
> > to use it, and it has no way to know this.
> 
> Well, since one can easily determine whether the destination address is SL
> or not, picking a source address of the correct class is trivial.

wrong again.  it's not reasonable to assume that the source address will not
be used by off site nodes.  (of course, specific apps can make that
assumption, but the architecture should not)

> > the app may also have to choose which interface to use with the site-
> > local prefix, and it has no good way to know this either.
> 
> Ah, but it'll have a different SL address on each interface, so that's no
> worse than having multiple global addresses. 

depends on what is driving the selection -  I don't think it's reasonable
to assume that all interfaces on a host are within a single site.

Keith



From owner-ietf@ietf.org  Sat Apr 19 20:42:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12854;
	Sat, 19 Apr 2003 20:42:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1973BH-0007MA-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 20:59:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1973Ao-0007G3-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 20:59:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12646
	for <ietf@ietf.org>; Sat, 19 Apr 2003 20:38:08 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972sh-00009U-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:40:31 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1972sg-00009R-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:40:30 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3K0cBL17288;
	Sat, 19 Apr 2003 19:38:11 -0500
Message-ID: <008e01c306d5$1f192c50$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Robert Elz" <kre@munnari.OZ.AU>
Cc: <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
References: <00d001c306c0$faeadf90$93b58742@ssprunk>  <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU>  <16762.1050792143@munnari.OZ.AU>
Subject: Re: A simple question 
Date: Sat, 19 Apr 2003 19:27:38 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Robert Elz" <kre@munnari.OZ.AU>
>   | To assign more than one address to every host means the host must
>   | have an intelligent means of deciding which address to use.
>
> Yes, but the amount of intelligence actually needed is pretty minimal.
> (It is actually harder to decide between multiple available global
> prefixes, than to decide between global and site local - the former is
> a difficult problem, the latter is almost trivial).

Agreed.  But the former is a problem nobody has solved after a couple
decades' effort.  Choosing a source address today is a problem only for
dual-homed hosts, which are fairly rare; I see no compelling reason to bring
this afflication to every IPv6 host until the problem is solved.

>   | I don't trust the hosts (either OS or the user) with that decision
>   | any more than I trust them with QOS.
>
> But you do trust them to select a suitable outgoing interface, to pick
> a usable router, and to choose amongst several different possible
> addresses for the destination (over which you most often have no
> control).

Most hosts have one interface, one source address, and one default gateway
(or two that are equally valid).  Recall the KISS principle.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Sat Apr 19 21:09:58 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13353;
	Sat, 19 Apr 2003 21:09:57 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1973Wx-0001Em-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 21:22:07 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1973Oy-00010e-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 21:13:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13091
	for <ietf@ietf.org>; Sat, 19 Apr 2003 20:52:45 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 19736q-0000Gr-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:55:09 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19736q-0000Gn-00
	for ietf@ietf.org; Sat, 19 Apr 2003 20:55:08 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3K0sdL17597;
	Sat, 19 Apr 2003 19:54:39 -0500
Message-ID: <00c101c306d7$6c9698d0$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <Valdis.Kletnieks@vt.edu>, "Robert Elz" <kre@munnari.OZ.AU>
Cc: "Dave Crocker" <dcrocker@brandenburg.com>, <ipng@sunroof.eng.sun.com>,
        <ietf@ietf.org>
References: <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU>            <16388.1050790957@munnari.OZ.AU> <200304192348.h3JNmxuL020301@turing-police.cc.vt.edu>
Subject: Re: A simple question 
Date: Sat, 19 Apr 2003 19:51:54 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake <Valdis.Kletnieks@vt.edu>
> There's this big assumption on the part of the pro-site-local crew that
> we "need" a stable address.  I posit that this is a crock, and that
> what we *need* to do is iron out the rough edges of IPv6 renumbering
> so hosts don't care *what* they have, as long as they have *some*
> prefix.

Changing the address on a host's interface is easy -- too bad there's a lot
more involved in renumbering.

For one thing, we need a TCP that can support address changes during a
session, and it can't rely on a deprecation period.  Beyond that, we'll need
widespread deployment of DDNS, which scares the heck out of most DNS admins
I know, with or without PKI.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Sat Apr 19 23:31:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15719;
	Sat, 19 Apr 2003 23:31:43 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1975jw-0004rA-00
	for ietf-list@ran.ietf.org; Sat, 19 Apr 2003 23:43:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1975jD-0004ke-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 23:42:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15405
	for <ietf@ietf.org>; Sat, 19 Apr 2003 23:21:46 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1975R4-0000j1-00
	for ietf@ietf.org; Sat, 19 Apr 2003 23:24:10 -0400
Received: from guelah.shrubbery.net ([198.58.5.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1975R3-0000iy-00
	for ietf@ietf.org; Sat, 19 Apr 2003 23:24:09 -0400
Received: by guelah.shrubbery.net (Postfix, from userid 7053)
	id 8C48217CFE2; Sun, 20 Apr 2003 03:24:26 +0000 (UTC)
Date: Sat, 19 Apr 2003 20:24:26 -0700
From: john heasley <heas@shrubbery.net>
To: Bill Manning <bmanning@ISI.EDU>
Cc: Joe Abley <jabley@isc.org>, moore@cs.utk.edu, kre@munnari.OZ.AU,
        Valdis.Kletnieks@vt.edu, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org, ot@cisco.com
Subject: Re: A simple question
Message-ID: <20030420032426.GA9713@shrubbery.net>
References: <E46D2CB2-72C3-11D7-A6E0-00039312C852@isc.org> <200304200024.h3K0OdY06518@boreas.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200304200024.h3K0OdY06518@boreas.isi.edu>
User-Agent: Mutt/1.4i
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: awe, not the good cheek
Sender: owner-ietf@ietf.org
Precedence: bulk

Sat, Apr 19, 2003 at 05:24:39PM -0700, Bill Manning:
> % >>> So, unless there's some routing revolution, you're just going to have
> % >>> to learn to deal with multiple addresses, and unless LL addresses go
> % >>> away, you're also going to have to deal with scoped addresses.
> % >>
> % >> LL use can and should be reserved for bootstrapping and diagnostics.
> % >
> % > LL is used in applications already. e.g LL addresses are commonly used
> % > to address BGP endpoints on exchanges.
> % 
> % What exchanges do that?
> % 
> % 
> % Joe
> 
> 
> 	Akira Kato and I had a draft out on how this could be done
> 	and had working, inter-operable implementations (zebra, cisco)
> 	in two locations, NSPIXP3 and LAIIX.

but, why?



From owner-ietf@ietf.org  Sun Apr 20 00:33:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16894;
	Sun, 20 Apr 2003 00:33:52 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1976kr-00021X-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 00:48:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1976kT-0001wY-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 00:48:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16800
	for <ietf@ietf.org>; Sun, 20 Apr 2003 00:27:07 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1976SJ-00010r-00
	for ietf@ietf.org; Sun, 20 Apr 2003 00:29:31 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1976SJ-00010o-00
	for ietf@ietf.org; Sun, 20 Apr 2003 00:29:31 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h3K4Pxw19463;
	Sat, 19 Apr 2003 21:25:59 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200304200425.h3K4Pxw19463@boreas.isi.edu>
Subject: Re: A simple question
In-Reply-To: <20030420032426.GA9713@shrubbery.net> from john heasley at "Apr 19, 3 08:24:26 pm"
To: heas@shrubbery.net (john heasley)
Date: Sat, 19 Apr 2003 21:25:59 -0700 (PDT)
Cc: bmanning@ISI.EDU, jabley@isc.org, moore@cs.utk.edu, kre@munnari.OZ.AU,
        Valdis.Kletnieks@vt.edu, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org, ot@cisco.com
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
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

% Sat, Apr 19, 2003 at 05:24:39PM -0700, Bill Manning:
% > % >>> So, unless there's some routing revolution, you're just going to have
% > % >>> to learn to deal with multiple addresses, and unless LL addresses go
% > % >>> away, you're also going to have to deal with scoped addresses.
% > % >>
% > % >> LL use can and should be reserved for bootstrapping and diagnostics.
% > % >
% > % > LL is used in applications already. e.g LL addresses are commonly used
% > % > to address BGP endpoints on exchanges.
% > % 
% > % What exchanges do that?
% > % 
% > % 
% > % Joe
% > 
% > 
% > 	Akira Kato and I had a draft out on how this could be done
% > 	and had working, inter-operable implementations (zebra, cisco)
% > 	in two locations, NSPIXP3 and LAIIX.
% 
% but, why?

	why not?  back in the day, the pier wg identified several 
	apps that did not take to renumbering well.  BGP was one.
	couple that with the oddities of small bits of address 
	space that are needed at exchanges (and do not play well 
	w/ the (non)compelling arguements for aggregation) and it 
	seemed reasonable that, if massive aggregation was an 
	inevitable feature of IPv6, that moving exchange point 
	communications to linklocal addresses would make many 
	things simpler. No "special-use" ranges in v6 land
	for exchanges.  But it was not to be.  Check the IDR
	archives for details.

	we now have special blocks of IPv6 space that are not
	supposed to be aggregated for things like exchanges.
	massive aggregation is expected, except for these "special
	prefixes".  One more administrative thing to track. :(


--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).



From owner-ietf@ietf.org  Sun Apr 20 00:58:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17222;
	Sun, 20 Apr 2003 00:58:13 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1977Az-0004Rv-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 01:15:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1977AQ-0004Mj-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 01:15:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17203
	for <ietf@ietf.org>; Sun, 20 Apr 2003 00:53:56 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1976sG-00016F-00
	for ietf@ietf.org; Sun, 20 Apr 2003 00:56:20 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1976sG-000165-00
	for ietf@ietf.org; Sun, 20 Apr 2003 00:56:20 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 3682A13997; Sun, 20 Apr 2003 04:56:08 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: A simple question
References: <200304200024.h3K0OdY06518@boreas.isi.edu>
	<20030420032426.GA9713@shrubbery.net>
From: Paul Vixie <vixie@vix.com>
Date: 20 Apr 2003 04:56:08 +0000
In-Reply-To: <20030420032426.GA9713@shrubbery.net>
Message-ID: <g3u1ctwyvr.fsf@sa.vix.com>
Lines: 43
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

i'm sorry to come into this late.  something went by a while ago that's
quite interesting.  sherman, set the wayback machine for...

> > % >>> So, unless there's some routing revolution, you're just going to
> > % >>> have to learn to deal with multiple addresses, and unless LL
> > % >>> addresses go away, you're also going to have to deal with scoped
> > % >>> addresses.

having recently done some work to describe and differentiate what i now
call a "dns-aware application", the above statement strikes me as more
relevant than most of the discussion that has followed it.

an application which has to be aware of ip address content in any way is
a different beast altogether than one which treats them as opaque.  from
a C programmer's point of view, the difference can be determined by
searching the module's source for "s6_addr" and "sin6_".  if neither
appears then you're probably not dealing with an "address aware" module.
if either appears, then you'll need to look carefully at it to find out.

an "address aware" program (module, library, application, whatever) has
to know about things like LL scopes, and currently, about SL issues.  any
other, non-"address aware" program, just receives "address blobs" from one
place and carries them around opaquely until it's time to offer them up on
some other altar, never knowing or caring what's "in the bag."

that being the case, i think it's "just plain wierd" that anybody is
arguing about the conceptual or architectural or complexity cost of SL
since the number of "address aware" programs is expected to remain quite
low in v6, perhaps lower as an overall share than in v4.  and for those
few programs, LL scopes and SL issues will not be a noticeable share of
the overall cost or complexity of the program.

this is not to paint myself as a supporter (nor detractor) of SL.  it's
possible that SL is as bad as people say, or as misunderstood, or whatever.
i just don't think it's reasonable to use application complexity as an
indicator of SL's cost:benefit ratio, since most applications Just Won't
Care.

(when i first heard of SL i thought, oh good, it's like rfc1918 but at the
campus level rather than at the autonomous system level.  them someone told
me it wasn't really like that, so now i'm opinionless.)
-- 
Paul Vixie



From owner-ietf@ietf.org  Sun Apr 20 03:15:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00600;
	Sun, 20 Apr 2003 03:15:29 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1979Fr-0004NV-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 03:28:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1979AT-0004HH-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 03:23:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00456
	for <ietf@ietf.org>; Sun, 20 Apr 2003 03:02:06 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1978sH-0001jz-00
	for ietf@ietf.org; Sun, 20 Apr 2003 03:04:29 -0400
Received: from tomts14.bellnexxia.net ([209.226.175.35] helo=tomts14-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1978sH-0001js-00
	for ietf@ietf.org; Sun, 20 Apr 2003 03:04:29 -0400
Received: from yahoo.com ([65.93.184.238]) by tomts14-srv.bellnexxia.net
          (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP
          id <20030420070443.VRNT4232.tomts14-srv.bellnexxia.net@yahoo.com>;
          Sun, 20 Apr 2003 03:04:43 -0400
Date: Sun, 20 Apr 2003 03:04:41 -0400
Subject: Re: A simple question 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Robert Elz <kre@munnari.OZ.AU>, Valdis.Kletnieks@vt.edu,
        Dave Crocker <dcrocker@brandenburg.com>, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
To: Joe Abley <jabley@isc.org>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <1F622487-72C4-11D7-A6E0-00039312C852@isc.org>
Message-Id: <5BB96FB4-72FE-11D7-9819-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Simply to say that renumbering is bad, does not therefore imply that 
site-local is good.

SL may be sufficient to work around the renumbering problem but is it 
necessary? There is not substantial basis as yet in this discussion for 
anyone to make that claim.

simon

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Sun Apr 20 10:01:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04953;
	Sun, 20 Apr 2003 10:01:34 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197FYe-000717-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 10:12:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197FWl-0006vA-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 10:10:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04728
	for <ietf@ietf.org>; Sun, 20 Apr 2003 09:49:28 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197FEV-0002WQ-00
	for ietf@ietf.org; Sun, 20 Apr 2003 09:51:51 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 197FEV-0002WN-00
	for ietf@ietf.org; Sun, 20 Apr 2003 09:51:51 -0400
Received: from edison.cisco.com (edison.cisco.com [171.70.144.164])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h3KDpbgE027959;
	Sun, 20 Apr 2003 06:51:37 -0700 (PDT)
Received: from cisco.com (sjc-vpn2-421.cisco.com [10.21.113.165]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id GAA22432; Sun, 20 Apr 2003 06:51:33 -0700 (PDT)
Message-ID: <3EA2A5E4.3020304@cisco.com>
Date: Sun, 20 Apr 2003 06:51:32 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Daniel Senie <dts@senie.com>
CC: Stephen Sprunk <stephen@sprunk.org>, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A simple question
References: <20030419151329.66daf0de.moore@cs.utk.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14384.1050784134@munnari.OZ.AU> <20030419165921.782a8353.moore@cs.utk.edu> <5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
In-Reply-To: <5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

Daniel Senie wrote:
> Example of usage: I use RFC 1918 space for private networks within 
> server farms. There's no connection to the public network from this 
> private segment. Servers connect to both public and private networks. 
> Backups, NFS mounts, SNMP and SQL data flows over the private network. 
> The isolated network segment keeps traffic off the public network for 
> performance reasons.

This has become an acceptable use of RFC 1918 addresses.  On the other 
hand, there is no need to support this sort of use in the v6 
architecture.  The address space is simply too vast for people to have 
to economize like this.

> All the world of private addressing is not NAT, regardless of how many 
> times people say it is.

My major concern that does drive NAT is the expressed desire on the IPng 
list to isolate sites from having to renumber.  That use of SLs requires 
NAT or proxy.  Rob may call it crazy, but the demand is there right now.

> I am saddened by the fact that Tony's simple question could not be 
> addressed. Site local addressing in IPv6 is a concept which has been 
> mentioned in RFC 1884, 2373 and 3513, the progression of Proposed 
> Standards. This is a string of documents dating back to 1995. For eight 
> years this concept was apparently considered a good thing. The 
> discussion on the mailing lists makes it sound like site-local 
> addressing is a new idea. I'd like to know why it's taken eight years 
> for folks to decide it's bad. Is it that folks are just now implementing 
> IPv6? Is it because the documents these eight years never made the 
> concept clear, and now it appears too hard to implement? In all those 
> years, has no vendor implemented site local? Are there any other 
> features we should reconsider as long as we're ripping the documents open?

Quite simply it is something we seem to have forgotten about: learning 
from operational experience.  Since 1995 the use of private address 
space has changed, as has been said.  Also, I don't think people fully 
understood the ramifications of SLs.  I certainly didn't, initially.  We 
also learned that using EUI-64s as end identifiers has certain privacy 
considerations, so this is not a first.  I think we do have to take some 
care when making changes to the addressing architecture.  If the 
decision of the group holds, it seems to me that those of us who voted 
"YES" have the burden to now provide an alternative that addresses the 
real requirements that SLs attempt to tackle.

> It is not unprecedented to change or remove a feature as a document 
> advances through the standards track. Such changes, however, can have 
> significant impact on already-implemented and deployed solutions. Such 
> matters should be considered carefully in that light. Perhaps removal of 
> features should receive substantially more scrutiny after publication on 
> the standards track.

I agree.  The vote was for deprecation.  That means we need to deprecate 
in favor of something better.

Happy holidays,

Eliot





From owner-ietf@ietf.org  Sun Apr 20 10:22:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06540;
	Sun, 20 Apr 2003 10:22:40 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197Fxp-0006jS-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 10:38:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197FxK-0006gF-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 10:38:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06444
	for <ietf@ietf.org>; Sun, 20 Apr 2003 10:16:55 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197Ff4-0002dw-00
	for ietf@ietf.org; Sun, 20 Apr 2003 10:19:18 -0400
Received: from hawk.mail.pas.earthlink.net ([207.217.120.22])
	by ietf-mx with esmtp (Exim 4.12)
	id 197Ff3-0002dt-00
	for ietf@ietf.org; Sun, 20 Apr 2003 10:19:17 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by hawk.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 197FfH-0004rE-00; Sun, 20 Apr 2003 07:19:31 -0700
Date: Sun, 20 Apr 2003 10:19:11 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Paul Vixie <vixie@vix.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030420101911.09a143fb.moore@cs.utk.edu>
In-Reply-To: <g3u1ctwyvr.fsf@sa.vix.com>
References: <200304200024.h3K0OdY06518@boreas.isi.edu>
	<20030420032426.GA9713@shrubbery.net>
	<g3u1ctwyvr.fsf@sa.vix.com>
X-Mailer: Sylpheed version 0.8.11 (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

> that being the case, i think it's "just plain wierd" that anybody is
> arguing about the conceptual or architectural or complexity cost of SL
> since the number of "address aware" programs is expected to remain quite
> low in v6, perhaps lower as an overall share than in v4.  and for those
> few programs, LL scopes and SL issues will not be a noticeable share of
> the overall cost or complexity of the program.

the existence of scoped addresses in v6 forces a greater percentage of
programs to be address aware.  some programs that could avoid being
address aware in ipv4 cannot do so in v6 and provide the same functionality.



From owner-ietf@ietf.org  Sun Apr 20 11:33:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07860;
	Sun, 20 Apr 2003 11:33:35 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197H3W-00019t-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 11:48:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197H3C-00017g-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 11:48:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07789
	for <ietf@ietf.org>; Sun, 20 Apr 2003 11:27:02 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197Gkv-0002ud-00
	for ietf@ietf.org; Sun, 20 Apr 2003 11:29:25 -0400
Received: from burp.tkv.asdf.org ([212.16.99.49] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 197Gku-0002ua-00
	for ietf@ietf.org; Sun, 20 Apr 2003 11:29:24 -0400
Received: from burp.tkv.asdf.org (msa@localhost [127.0.0.1])
	by burp.tkv.asdf.org (8.12.3/8.12.3/Debian-6.3) with ESMTP id h3KFTcXa007248;
	Sun, 20 Apr 2003 18:29:38 +0300
Received: (from msa@localhost)
	by burp.tkv.asdf.org (8.12.3/8.12.3/Debian-6.3) id h3KFTXar007244;
	Sun, 20 Apr 2003 18:29:33 +0300
Date: Sun, 20 Apr 2003 18:29:33 +0300
Message-Id: <200304201529.h3KFTXar007244@burp.tkv.asdf.org>
From: Markku Savela <msa@burp.tkv.asdf.org>
To: moore@cs.utk.edu
CC: vixie@vix.com, moore@cs.utk.edu, ietf@ietf.org
In-reply-to: <20030420101911.09a143fb.moore@cs.utk.edu> (message from Keith
	Moore on Sun, 20 Apr 2003 10:19:11 -0400)
Subject: Re: A simple question
References: <200304200024.h3K0OdY06518@boreas.isi.edu>
	<20030420032426.GA9713@shrubbery.net>
	<g3u1ctwyvr.fsf@sa.vix.com> <20030420101911.09a143fb.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk


> the existence of scoped addresses in v6 forces a greater percentage of
> programs to be address aware.  some programs that could avoid being
> address aware in ipv4 cannot do so in v6 and provide the same functionality.

I want to see an existing sample of an application that fails with
sitelocals (or to make it even more simple, an application that fails
on IPv4 link locals, will do also).

However, theoretical examples wont do. I want to see a program name
and an URL where I can download source for a study. Surely, if many
applications fail with site locals, there can be at least one existing
open source application?

Just ONE such example, please?




From owner-ietf@ietf.org  Sun Apr 20 11:43:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08040;
	Sun, 20 Apr 2003 11:43:46 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197HCE-0001j1-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 11:57:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197H9Y-0001L9-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 11:54:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07873
	for <ietf@ietf.org>; Sun, 20 Apr 2003 11:33:36 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197GrH-0002vX-00
	for ietf@ietf.org; Sun, 20 Apr 2003 11:36:00 -0400
Received: from snipe.mail.pas.earthlink.net ([207.217.120.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 197GrH-0002vU-00
	for ietf@ietf.org; Sun, 20 Apr 2003 11:35:59 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by snipe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 197GrT-0001qh-00; Sun, 20 Apr 2003 08:36:11 -0700
Date: Sun, 20 Apr 2003 11:35:50 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Markku Savela <msa@burp.tkv.asdf.org>
Cc: moore@cs.utk.edu, vixie@vix.com, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030420113550.65d5813f.moore@cs.utk.edu>
In-Reply-To: <200304201529.h3KFTXar007244@burp.tkv.asdf.org>
References: <200304200024.h3K0OdY06518@boreas.isi.edu>
	<20030420032426.GA9713@shrubbery.net>
	<g3u1ctwyvr.fsf@sa.vix.com>
	<20030420101911.09a143fb.moore@cs.utk.edu>
	<200304201529.h3KFTXar007244@burp.tkv.asdf.org>
X-Mailer: Sylpheed version 0.8.11 (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 want to see an existing sample of an application that fails with
> sitelocals (or to make it even more simple, an application that fails
> on IPv4 link locals, will do also).

NetSolve  	http://icl.cs.utk.edu/netsolve/
PVM		http://www.epm.ornl.gov/pvm/pvm_home.html

either of these will fail if run on nodes with a mixture of scoped and global
addresses.  

for that matter, so will SIP.




From owner-ietf@ietf.org  Sun Apr 20 13:10:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09260;
	Sun, 20 Apr 2003 13:10:20 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197IaM-0005QQ-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 13:26:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197Ia4-0005O7-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 13:26:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09123
	for <ietf@ietf.org>; Sun, 20 Apr 2003 13:05:02 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197IHm-0003Ce-00
	for ietf@ietf.org; Sun, 20 Apr 2003 13:07:26 -0400
Received: from gull.mail.pas.earthlink.net ([207.217.120.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 197IHl-0003Cb-00
	for ietf@ietf.org; Sun, 20 Apr 2003 13:07:25 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 197II0-0004pP-00; Sun, 20 Apr 2003 10:07:40 -0700
Date: Sun, 20 Apr 2003 13:07:19 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Terry Gray <gray@washington.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030420130719.580be874.moore@cs.utk.edu>
In-Reply-To: <Pine.WNT.4.55.0304200844040.1280@TGX200>
References: <200304200024.h3K0OdY06518@boreas.isi.edu>
	<20030420032426.GA9713@shrubbery.net>
	<g3u1ctwyvr.fsf@sa.vix.com>
	<20030420101911.09a143fb.moore@cs.utk.edu>
	<Pine.WNT.4.55.0304200844040.1280@TGX200>
X-Mailer: Sylpheed version 0.8.11 (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

> > the existence of scoped addresses in v6 forces a greater percentage of
> > programs to be address aware.  some programs that could avoid being
> > address aware in ipv4 cannot do so in v6 and provide the same
> > functionality.
> 
> Keith,
> For the benefit of us uninformed lurkers who learn best by example,
> could you provide one?

Already done, see my previous message.

> Also, I'm wondering how the SL/1918 address-scoping debate plays in
> the context of firewalls.  Don't firewalls provide an even more random
> form of address scoping that apps must cope with?  Or not?

It's a separation of function issue.  Ideally, apps try to send messages to
their peers; the network makes a best effort to deliver them there, modulo
policy.  That way, the apps can concentrate on their intended purposes, and
the network concentrates on its intended purpose - neither needs to absorb
the complexity required to second-guess the other.  Each has a clear set of
expectations, there's an obvious separation between the two, and if something
fails the problem is clearly on one side or the other.  Separation of function
minimizes complexity and improves robustness. also, there's less incentive for
an arms race between apps and the network, which also helps to keep complexity
down.

Specifically, in a world where all addresses used by apps are global, if a
firewall blocks traffic from host A to host B, there's nothing that an app on
host A can or should be expected to do about it.  The app may not be able to
tell whether it's due to a network failure or a firewall, but it doesn't
matter too much - the most the app can do is retry at a later time. (I'd argue
that ICMP should allow the app to distinguish the two, for the sake of error
reporting, and to distinguish permanent failures due to policy based filtering
from temporary failures due to link outages.  But it appears that we need
fixes to both firewalls and APIs to make this work well.)

Scoped addresses muddy this picture, because experience indicates that apps
will be expected to cope with a mixture of scoped and global addresses.  Once
scoped addresses are introduced, the app has to perform functions
traditionally performed by the network. If host A cannot reach host B, it
might be due to policy or a network failure, or it might be that the address
that A has for B is not valid in the scope that A is using.  There's no way
that A can know this.  A might need to try sending to B from a different
interface.  Or it might need to try to route the message through a peer that
does have access to B's scope.  Or it might need to be able to try multiple
addresses for B.  Or all of the above.  But since A doesn't have access to the
network topology information anyway (unless it's explicitly configured to know
such things), this involves something between trial-and-error and network
probing.  Basically the app is expected to absorb a lot of complexity just to
function in these cases, and even then, the app is not likely to function
reliably. For that matter, since apps now have more reason to try to route
traffic to their destination by any means available (including
application-level tunneling), it becomes much more difficult to make effecitve
firewalls.  Even "legitimate" programs will be forced to employ such tactics.

So scoped addresses increase complexity of both apps and networks. 



From owner-ietf@ietf.org  Sun Apr 20 13:10:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09259;
	Sun, 20 Apr 2003 13:10:20 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197IXa-0005AX-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 13:23:46 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197IU9-00054v-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 13:20:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09000
	for <ietf@ietf.org>; Sun, 20 Apr 2003 12:58:56 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197IBs-0003BZ-00
	for ietf@ietf.org; Sun, 20 Apr 2003 13:01:20 -0400
Received: from atalanta.ctd.anl.gov ([146.137.194.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 197IBr-0003BS-00
	for ietf@ietf.org; Sun, 20 Apr 2003 13:01:19 -0400
Received: from nomad.ctd.anl.gov (localhost [127.0.0.1])
      by atalanta.ctd.anl.gov (8.9.1a/8.9.1) with ESMTP id MAA24085;
     Sun, 20 Apr 2003 12:01:08 -0500 (CDT)
Message-Id: <5.1.1.5.2.20030420115012.009f0260@atalanta.ctd.anl.gov>
X-Sender: b30118@atalanta.ctd.anl.gov (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Sun, 20 Apr 2003 12:00:55 -0500
To: ipng@sunroof.eng.sun.com
From: Richard Carlson <RACarlson@anl.gov>
Subject: Re: A simple question
Cc: ietf@ietf.org
In-Reply-To: <20030419192024.440d3773.moore@cs.utk.edu>
References: <16762.1050792143@munnari.OZ.AU>
 <00d001c306c0$faeadf90$93b58742@ssprunk>
 <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
 <16890640984.20030419070719@brandenburg.com>
 <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com>
 <a05210603bac6d68105ed@[10.0.0.3]>
 <11870.1050777166@munnari.OZ.AU>
 <14570.1050784897@munnari.OZ.AU>
 <16762.1050792143@munnari.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 07:20 PM 4/19/03 -0400, Keith Moore wrote:
> >   | To assign more than one address to every host means the host must have
> >   | an intelligent means of deciding which address to use.
> >
> > Yes, but the amount of intelligence actually needed is pretty minimal.
> > (It is actually harder to decide between multiple available global
> > prefixes, than to decide between global and site local - the former is
> > a difficult problem, the latter is almost trivial).
>
>disagree.  the app can choose any global prefix and reasonably expect it to
>work,

I completely disagree with this assumption.  Firewalls and address filters 
mean that no app can make any reasonable assumption.  Some addresses will 
work and others will fail.  The app is left with no clues as to why the 
connection failed.  Assuming it's just a link failure and retrying sometime 
in the future things will work is a receipt for user frustration.

>modulo link failures. but when choosing between a global and a site
>local the app needs to know whether the site local address will be valid for
>the hosts that need to use it, and it has no way to know this.   the app may
>also have to choose which interface to use with the site-local prefix,
>and it has no good way to know this either.

The decision process is not forced on the app/host by the existence of the 
site-local prefix.  It is due to the emergence of firewalls and address 
filters.  The reality is that non-global routing scopes exist today.  The 
question is - how do we provide some feedback to apps that they are trying 
to cross a scope boundary that it's a permanent error condition (5xx in 
SMTP verbiage)?  One proposed notification method is the site-local 
prefix.  Other methods can be created, but something needs to be done and 
simply killing site-locals and ignoring the underlying scoping issue is a 
non-starter.

Rich

------------------------------------

Richard A. Carlson                              e-mail: RACarlson@anl.gov
Network Research Section                        phone:  (630) 252-7289
Argonne National Laboratory                     fax:    (630) 252-4021
9700 Cass Ave. S.
Argonne,  IL 60439




From owner-ietf@ietf.org  Sun Apr 20 14:25:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10420;
	Sun, 20 Apr 2003 14:25:59 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197Jk0-0000EF-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 14:40:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197JfK-00008x-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 14:35:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10325
	for <ietf@ietf.org>; Sun, 20 Apr 2003 14:14:31 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197JN1-0003TJ-00
	for ietf@ietf.org; Sun, 20 Apr 2003 14:16:55 -0400
Received: from garlic.amaranth.net ([208.254.46.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 197JN0-0003TG-00
	for ietf@ietf.org; Sun, 20 Apr 2003 14:16:54 -0400
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226])
	(authenticated (0 bits))
	by garlic.amaranth.net (8.11.7/8.11.7) with ESMTP id h3KIHB820687
	(using TLSv1/SSLv3 with cipher RC4-SHA (128 bits) verified NO);
	Sun, 20 Apr 2003 14:17:12 -0400
Message-Id: <5.2.1.1.2.20030420140541.0290fb00@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Sun, 20 Apr 2003 14:16:12 -0400
To: Richard Carlson <RACarlson@anl.gov>, ipng@sunroof.eng.sun.com
From: Daniel Senie <dts@senie.com>
Subject: Re: A simple question
Cc: ietf@ietf.org
In-Reply-To: <5.1.1.5.2.20030420115012.009f0260@atalanta.ctd.anl.gov>
References: <20030419192024.440d3773.moore@cs.utk.edu>
 <16762.1050792143@munnari.OZ.AU>
 <00d001c306c0$faeadf90$93b58742@ssprunk>
 <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
 <16890640984.20030419070719@brandenburg.com>
 <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com>
 <a05210603bac6d68105ed@[10.0.0.3]>
 <11870.1050777166@munnari.OZ.AU>
 <14570.1050784897@munnari.OZ.AU>
 <16762.1050792143@munnari.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 01:00 PM 4/20/2003, Richard Carlson wrote:
>At 07:20 PM 4/19/03 -0400, Keith Moore wrote:
>> >   | To assign more than one address to every host means the host must have
>> >   | an intelligent means of deciding which address to use.
>> >
>> > Yes, but the amount of intelligence actually needed is pretty minimal.
>> > (It is actually harder to decide between multiple available global
>> > prefixes, than to decide between global and site local - the former is
>> > a difficult problem, the latter is almost trivial).
>>
>>disagree.  the app can choose any global prefix and reasonably expect it to
>>work,
>
>I completely disagree with this assumption.  Firewalls and address filters 
>mean that no app can make any reasonable assumption.  Some addresses will 
>work and others will fail.  The app is left with no clues as to why the 
>connection failed.  Assuming it's just a link failure and retrying 
>sometime in the future things will work is a receipt for user frustration.
>
>>modulo link failures. but when choosing between a global and a site
>>local the app needs to know whether the site local address will be valid for
>>the hosts that need to use it, and it has no way to know this.   the app may
>>also have to choose which interface to use with the site-local prefix,
>>and it has no good way to know this either.
>
>The decision process is not forced on the app/host by the existence of the 
>site-local prefix.  It is due to the emergence of firewalls and address 
>filters.  The reality is that non-global routing scopes exist today.  The 
>question is - how do we provide some feedback to apps that they are trying 
>to cross a scope boundary that it's a permanent error condition (5xx in 
>SMTP verbiage)?  One proposed notification method is the site-local 
>prefix.  Other methods can be created, but something needs to be done and 
>simply killing site-locals and ignoring the underlying scoping issue is a 
>non-starter.

You mean aside from applications understaning that an ICMP Destination 
Unreachable / Administratively Prohibited response from the site firewall?

For that matter, IPv6 machines arguably could try their Site Local address 
and be given that same feedback from the border router or firewall, and use 
the response as an indication to go use their assigned global address. It's 
not clear to me that the host or application need contain the intelligence 
(nor is there any way to determine scoping unassisted, IMO), however 
through use of ICMP responses it certainly should be possible to determine 
reachability or lack thereof. It may be useful to expand the responses 
routers and firewalls give to hosts within sites to help accomplish this.

We have the problem of scoped addresses whether the "site local" mechanism 
is retained or not. Providing guidance on the responses an application is 
to receive in response to scoping controls (firewalls) would be useful 
regardless. If this problem is worth solving for the already-common case of 
firewalls, solving it for site-local addressing does not seem to be too 
much of a stretch. 




From owner-ietf@ietf.org  Sun Apr 20 14:53:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10993;
	Sun, 20 Apr 2003 14:53:56 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197K98-0001jI-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 15:06:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197K8B-0001gz-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 15:05:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10916
	for <ietf@ietf.org>; Sun, 20 Apr 2003 14:44:20 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197Jps-0003bS-00
	for ietf@ietf.org; Sun, 20 Apr 2003 14:46:44 -0400
Received: from turkey.mail.pas.earthlink.net ([207.217.120.126])
	by ietf-mx with esmtp (Exim 4.12)
	id 197Jps-0003bP-00
	for ietf@ietf.org; Sun, 20 Apr 2003 14:46:44 -0400
Received: from h-68-165-68-234.snvacaid.covad.net ([68.165.68.234] helo=oemcomputer)
	by turkey.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 197JqB-0002xk-00
	for ietf@ietf.org; Sun, 20 Apr 2003 11:47:03 -0700
Message-ID: <005701c3076d$6d626320$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <20030418131636.75791.qmail@web10907.mail.yahoo.com> <132275752.20030418063433@brandenburg.com>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
Date: Sun, 20 Apr 2003 11:48:26 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi -

> From: "Dave Crocker" <dhc2@dcrocker.net>
> To: "Spencer Dawkins" <spencer_dawkins@yahoo.com>
> Cc: <ietf@ietf.org>
> Sent: Friday, April 18, 2003 6:34 AM
> Subject: Re: Internet Draft Guidelines Require Precise Formatting?
...

> For Internet-Drafts, page-breaks are not required.
...

If this is true, when can we expect
http://www.ietf.org/ietf/1id-guidelines.txt
to be updated to reflect this change?

Randy





From owner-ietf@ietf.org  Sun Apr 20 14:57:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11150;
	Sun, 20 Apr 2003 14:57:41 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197KIM-0002Nn-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 15:16:10 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197KHV-00023H-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 15:15:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11018
	for <ietf@ietf.org>; Sun, 20 Apr 2003 14:54:00 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197JzC-0003ck-00
	for ietf@ietf.org; Sun, 20 Apr 2003 14:56:22 -0400
Received: from atalanta.ctd.anl.gov ([146.137.194.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 197JzC-0003cb-00
	for ietf@ietf.org; Sun, 20 Apr 2003 14:56:22 -0400
Received: from nomad.ctd.anl.gov (localhost [127.0.0.1])
      by atalanta.ctd.anl.gov (8.9.1a/8.9.1) with ESMTP id NAA29339;
     Sun, 20 Apr 2003 13:56:10 -0500 (CDT)
Message-Id: <5.1.1.5.2.20030420134939.00a3f840@atalanta.ctd.anl.gov>
X-Sender: b30118@atalanta.ctd.anl.gov (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Sun, 20 Apr 2003 13:55:56 -0500
To: Daniel Senie <dts@senie.com>, ipng@sunroof.eng.sun.com
From: Richard Carlson <RACarlson@anl.gov>
Subject: Re: A simple question
Cc: ietf@ietf.org
In-Reply-To: <5.2.1.1.2.20030420140541.0290fb00@mail.amaranth.net>
References: <5.1.1.5.2.20030420115012.009f0260@atalanta.ctd.anl.gov>
 <20030419192024.440d3773.moore@cs.utk.edu>
 <16762.1050792143@munnari.OZ.AU>
 <00d001c306c0$faeadf90$93b58742@ssprunk>
 <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
 <16890640984.20030419070719@brandenburg.com>
 <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com>
 <a05210603bac6d68105ed@[10.0.0.3]>
 <11870.1050777166@munnari.OZ.AU>
 <14570.1050784897@munnari.OZ.AU>
 <16762.1050792143@munnari.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 02:16 PM 4/20/03 -0400, Daniel Senie wrote:
>At 01:00 PM 4/20/2003, Richard Carlson wrote:
>>At 07:20 PM 4/19/03 -0400, Keith Moore wrote:
>>> >   | To assign more than one address to every host means the host must 
>>> have
>>> >   | an intelligent means of deciding which address to use.
>>> >
>>> > Yes, but the amount of intelligence actually needed is pretty minimal.
>>> > (It is actually harder to decide between multiple available global
>>> > prefixes, than to decide between global and site local - the former is
>>> > a difficult problem, the latter is almost trivial).
>>>
>>>disagree.  the app can choose any global prefix and reasonably expect it to
>>>work,
>>
>>I completely disagree with this assumption.  Firewalls and address 
>>filters mean that no app can make any reasonable assumption.  Some 
>>addresses will work and others will fail.  The app is left with no clues 
>>as to why the connection failed.  Assuming it's just a link failure and 
>>retrying sometime in the future things will work is a receipt for user 
>>frustration.
>>
>>>modulo link failures. but when choosing between a global and a site
>>>local the app needs to know whether the site local address will be valid for
>>>the hosts that need to use it, and it has no way to know this.   the app may
>>>also have to choose which interface to use with the site-local prefix,
>>>and it has no good way to know this either.
>>
>>The decision process is not forced on the app/host by the existence of 
>>the site-local prefix.  It is due to the emergence of firewalls and 
>>address filters.  The reality is that non-global routing scopes exist 
>>today.  The question is - how do we provide some feedback to apps that 
>>they are trying to cross a scope boundary that it's a permanent error 
>>condition (5xx in SMTP verbiage)?  One proposed notification method is 
>>the site-local prefix.  Other methods can be created, but something needs 
>>to be done and simply killing site-locals and ignoring the underlying 
>>scoping issue is a non-starter.
>
>You mean aside from applications understaning that an ICMP Destination 
>Unreachable / Administratively Prohibited response from the site firewall?

An ICMP message is one way of providing this information.  There may be 
others, I don't know by folks are free to develop them.

>For that matter, IPv6 machines arguably could try their Site Local address 
>and be given that same feedback from the border router or firewall, and 
>use the response as an indication to go use their assigned global address. 
>It's not clear to me that the host or application need contain the 
>intelligence (nor is there any way to determine scoping unassisted, IMO), 
>however through use of ICMP responses it certainly should be possible to 
>determine reachability or lack thereof. It may be useful to expand the 
>responses routers and firewalls give to hosts within sites to help 
>accomplish this.
>
>We have the problem of scoped addresses whether the "site local" mechanism 
>is retained or not. Providing guidance on the responses an application is 
>to receive in response to scoping controls (firewalls) would be useful 
>regardless. If this problem is worth solving for the already-common case 
>of firewalls, solving it for site-local addressing does not seem to be too 
>much of a stretch.

Exactly, the only thing an address with a site-local prefix tell me is that 
a filtering router or firewall is guaranteed to be in some arbitrary 
path.  I'm mystified as to why an app would treat it any differently that 
an IPv6 address generated with any other prefix.

Rich




------------------------------------

Richard A. Carlson                              e-mail: RACarlson@anl.gov
Network Research Section                        phone:  (630) 252-7289
Argonne National Laboratory                     fax:    (630) 252-4021
9700 Cass Ave. S.
Argonne,  IL 60439




From owner-ietf@ietf.org  Sun Apr 20 15:13:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12330;
	Sun, 20 Apr 2003 15:13:08 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197KWM-00006x-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 15:30:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197KVo-0008N5-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 15:30:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11936
	for <ietf@ietf.org>; Sun, 20 Apr 2003 15:08:46 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197KDV-0003kZ-00
	for ietf@ietf.org; Sun, 20 Apr 2003 15:11:09 -0400
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 197KDU-0003kW-00
	for ietf@ietf.org; Sun, 20 Apr 2003 15:11:08 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 197KDg-0003JE-00; Sun, 20 Apr 2003 12:11:20 -0700
Date: Sun, 20 Apr 2003 15:10:59 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Daniel Senie <dts@senie.com>
Cc: moore@cs.utk.edu, RACarlson@anl.gov, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030420151059.1f400738.moore@cs.utk.edu>
In-Reply-To: <5.2.1.1.2.20030420140541.0290fb00@mail.amaranth.net>
References: <20030419192024.440d3773.moore@cs.utk.edu>
	<16762.1050792143@munnari.OZ.AU>
	<00d001c306c0$faeadf90$93b58742@ssprunk>
	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
	<16762.1050792143@munnari.OZ.AU>
	<5.2.1.1.2.20030420140541.0290fb00@mail.amaranth.net>
X-Mailer: Sylpheed version 0.8.11 (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

> You mean aside from applications understaning that an ICMP Destination 
> Unreachable / Administratively Prohibited response from the site firewall?
> 
> For that matter, IPv6 machines arguably could try their Site Local address 
> and be given that same feedback from the border router or firewall

how does any party - the host, border router or firewall - know whether the SL
address is from that site or some other site?  SLs are inherently ambiguous.

> , and use 
> the response as an indication to go use their assigned global address. 

if the destination has a global address, it should *always* be used in
preference to the site local, at least in the absence of external
configuration.

> We have the problem of scoped addresses whether the "site local" mechanism 
> is retained or not. 

I disagree, or at least, I think it's misleading to use  the term "scoped
addresses" to cover all filtering, because this is conflating two things - use
of filtering on one hand and use of ambiguous addresses on the other.  It's
useful to be able to refer to a host even if you can't send traffic there.

Keith



From owner-ietf@ietf.org  Sun Apr 20 15:35:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13088;
	Sun, 20 Apr 2003 15:35:34 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197Kpj-0003O4-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 15:50:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197Kkg-0003Eo-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 15:45:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12982
	for <ietf@ietf.org>; Sun, 20 Apr 2003 15:24:08 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197KSN-0003qY-00
	for ietf@ietf.org; Sun, 20 Apr 2003 15:26:31 -0400
Received: from harrier.mail.pas.earthlink.net ([207.217.120.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 197KSM-0003qV-00
	for ietf@ietf.org; Sun, 20 Apr 2003 15:26:30 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by harrier.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 197KSb-00041b-00; Sun, 20 Apr 2003 12:26:45 -0700
Date: Sun, 20 Apr 2003 15:26:24 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Richard Carlson <RACarlson@anl.gov>
Cc: moore@cs.utk.edu, dts@senie.com, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030420152624.153c95ff.moore@cs.utk.edu>
In-Reply-To: <5.1.1.5.2.20030420134939.00a3f840@atalanta.ctd.anl.gov>
References: <5.1.1.5.2.20030420115012.009f0260@atalanta.ctd.anl.gov>
	<20030419192024.440d3773.moore@cs.utk.edu>
	<16762.1050792143@munnari.OZ.AU>
	<00d001c306c0$faeadf90$93b58742@ssprunk>
	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
	<16762.1050792143@munnari.OZ.AU>
	<5.1.1.5.2.20030420134939.00a3f840@atalanta.ctd.anl.gov>
X-Mailer: Sylpheed version 0.8.11 (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

> >We have the problem of scoped addresses whether the "site local" mechanism 
> >is retained or not. Providing guidance on the responses an application is 
> >to receive in response to scoping controls (firewalls) would be useful 
> >regardless. If this problem is worth solving for the already-common case 
> >of firewalls, solving it for site-local addressing does not seem to be too 
> >much of a stretch.
> 
> Exactly, the only thing an address with a site-local prefix tell me is that 
> a filtering router or firewall is guaranteed to be in some arbitrary 
> path. 

but you don't know which paths, so you don't know how to use that.

> I'm mystified as to why an app would treat it any differently that 
> an IPv6 address generated with any other prefix.

some people believe that SLs would be more secure than globals, even though
this is an unwarranted assumption.  some people believe they would  be more
stable than globals, but providing stable local addresses isn't a good
solution to the renumbering problem - it's not as if all of the important
apps affected by renumbering are local.  some people believe SLs would be more
efficient.  some apps writers would avoid using SLs whenever possible because
they're not portable (and they'll lose when SLs are all that are available),
some apps writers will use them in preference to globals (and they'll lose
when they're expected to communicate across site boundaries), and other apps
writers will try to deal with all cases (adding a lot of complexity and still
not able to avoid the app failing for apparently arbitrary reasons). any of
these makes the behavior of apps less predictable.

Keith



From owner-ietf@ietf.org  Sun Apr 20 15:57:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13673;
	Sun, 20 Apr 2003 15:57:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197L5D-0004aV-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 16:06:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197L4w-0004Xt-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 16:06:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13575
	for <ietf@ietf.org>; Sun, 20 Apr 2003 15:45:04 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197Kmd-0003wJ-00
	for ietf@ietf.org; Sun, 20 Apr 2003 15:47:27 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 197Kmc-0003wG-00
	for ietf@ietf.org; Sun, 20 Apr 2003 15:47:26 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3KJlgL32049;
	Sun, 20 Apr 2003 14:47:42 -0500
Message-ID: <003101c30775$b55db050$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Keith Moore" <moore@cs.utk.edu>, "Terry Gray" <gray@washington.edu>
Cc: <moore@cs.utk.edu>, <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
References: <200304200024.h3K0OdY06518@boreas.isi.edu><20030420032426.GA9713@shrubbery.net><g3u1ctwyvr.fsf@sa.vix.com><20030420101911.09a143fb.moore@cs.utk.edu><Pine.WNT.4.55.0304200844040.1280@TGX200> <20030420130719.580be874.moore@cs.utk.edu>
Subject: Re: A simple question
Date: Sun, 20 Apr 2003 14:44:21 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Keith Moore" <moore@cs.utk.edu>
> > Also, I'm wondering how the SL/1918 address-scoping debate
> > plays in the context of firewalls.  Don't firewalls provide an even
> > more random form of address scoping that apps must cope with?
> > Or not?
>
> ...
> Scoped addresses muddy this picture, because experience indicates
> that apps will be expected to cope with a mixture of scoped and
> global addresses.  Once scoped addresses are introduced, the app
> has to perform functions traditionally performed by the network. If
> host A cannot reach host B, it might be due to policy or a network
> failure, or it might be that the address that A has for B is not valid in
> the scope that A is using.

So you're not arguing against scoped addresses per se, you're arguing
against having both scoped and global addresses on the same host?  I see the
same problem occuring if a host has two global addresses which are treated
differently by the firewall(s), so it's not truly a problem with SL.

The only SL-specific problem is when naughty applications pass network-layer
addresses across site boundaries; such applications must be "address aware"
anyways, so understanding SL isn't much of an incremental burden.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Sun Apr 20 15:58:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13831;
	Sun, 20 Apr 2003 15:58:58 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197LEs-0004tz-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 16:16:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197LBz-0004bo-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 16:13:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13617
	for <ietf@ietf.org>; Sun, 20 Apr 2003 15:52:20 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197Ktf-0003wz-00
	for ietf@ietf.org; Sun, 20 Apr 2003 15:54:43 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 197Kte-0003ww-00
	for ietf@ietf.org; Sun, 20 Apr 2003 15:54:42 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3KJsnL32258;
	Sun, 20 Apr 2003 14:54:49 -0500
Message-ID: <003d01c30776$b38af6b0$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Richard Carlson" <RACarlson@anl.gov>, "Daniel Senie" <dts@senie.com>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
References: <20030419192024.440d3773.moore@cs.utk.edu> <16762.1050792143@munnari.OZ.AU> <00d001c306c0$faeadf90$93b58742@ssprunk> <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU> <16762.1050792143@munnari.OZ.AU> <5.2.1.1.2.20030420140541.0290fb00@mail.amaranth.net>
Subject: Re: A simple question
Date: Sun, 20 Apr 2003 14:50:00 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Daniel Senie" <dts@senie.com>
> At 01:00 PM 4/20/2003, Richard Carlson wrote:
> >The question is - how do we provide some feedback to apps that
> >they are trying to cross a scope boundary that it's a permanent error
> >condition (5xx in SMTP verbiage)?  One proposed notification
> >method is the site-local prefix.  Other methods can be created, but
> >something needs to be done and simply killing site-locals and
> >ignoring the underlying scoping issue is a non-starter.
>
> You mean aside from applications understaning that an ICMP
> Destination Unreachable / Administratively Prohibited response from
> the site firewall?

Many firewalls simply drop packets which are prohibited without sending ICMP
responses, not to mention all the places that filter all ICMP
indiscriminately.

> For that matter, IPv6 machines arguably could try their Site Local
> address and be given that same feedback from the border router or
> firewall, and use the response as an indication to go use their assigned
> global address.

The vast majority of applications do not pick their source address, nor is
there a compelling reason for them to do so.  A large number of applications
don't even handle multiple destination addresses properly, so expecting this
additional intelligence for the source address is irrational.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Sun Apr 20 16:02:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14048;
	Sun, 20 Apr 2003 16:02:08 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197LHo-0005PU-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 16:19:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197LHV-0005KK-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 16:19:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13742
	for <ietf@ietf.org>; Sun, 20 Apr 2003 15:58:03 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197KzB-0003z7-00
	for ietf@ietf.org; Sun, 20 Apr 2003 16:00:25 -0400
Received: from conure.mail.pas.earthlink.net ([207.217.120.54])
	by ietf-mx with esmtp (Exim 4.12)
	id 197KzB-0003yx-00
	for ietf@ietf.org; Sun, 20 Apr 2003 16:00:25 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by conure.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 197KzM-0000Kp-00; Sun, 20 Apr 2003 13:00:36 -0700
Date: Sun, 20 Apr 2003 16:00:15 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: moore@cs.utk.edu, gray@washington.edu, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A simple question
Message-Id: <20030420160015.71849057.moore@cs.utk.edu>
In-Reply-To: <003101c30775$b55db050$93b58742@ssprunk>
References: <200304200024.h3K0OdY06518@boreas.isi.edu>
	<20030420032426.GA9713@shrubbery.net>
	<g3u1ctwyvr.fsf@sa.vix.com>
	<20030420101911.09a143fb.moore@cs.utk.edu>
	<Pine.WNT.4.55.0304200844040.1280@TGX200>
	<20030420130719.580be874.moore@cs.utk.edu>
	<003101c30775$b55db050$93b58742@ssprunk>
X-Mailer: Sylpheed version 0.8.11 (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

> So you're not arguing against scoped addresses per se, you're arguing
> against having both scoped and global addresses on the same host?

it turns out that this doesn't solve the problem.  the addresses will still
leak.  apps will still be expected to cope with the mixture of ambiguous and
unambiguous addresses.

> I see the
> same problem occuring if a host has two global addresses which are treated
> differently by the firewall(s),

I see that as a different problem - in particular, in that case there's no
need for apps to cope with ambiguous IP addresses.  as a result it's much
clearer that it's unreasonable to expect apps to talk to the nodes whose
traffic is being filtered.

> The only SL-specific problem is when naughty applications pass network-layer
> addresses across site boundaries

which is a perfectly healthy and reasonable thing for apps to do.
(not that they can tell where those site boundaries are anyway)

> ; such applications must be "address aware"
> anyways, so understanding SL isn't much of an incremental burden.

using an address as an opaque identifier doesn't require address awareness.

Keith



From owner-ietf@ietf.org  Sun Apr 20 16:05:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14221;
	Sun, 20 Apr 2003 16:05:59 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197LMJ-0006KG-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 16:24:19 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197LL9-0005wm-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 16:23:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14039
	for <ietf@ietf.org>; Sun, 20 Apr 2003 16:01:49 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197L2p-00043w-00
	for ietf@ietf.org; Sun, 20 Apr 2003 16:04:11 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 197L2p-00043t-00
	for ietf@ietf.org; Sun, 20 Apr 2003 16:04:11 -0400
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h3KK48129034;
	Sun, 20 Apr 2003 13:04:08 -0700
Date: Sun, 20 Apr 2003 12:35:05 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <4196703714.20030420123505@brandenburg.com>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>
CC: ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
In-Reply-To: <005701c3076d$6d626320$7f1afea9@oemcomputer>
References: <20030418131636.75791.qmail@web10907.mail.yahoo.com>
 <132275752.20030418063433@brandenburg.com>
 <005701c3076d$6d626320$7f1afea9@oemcomputer>
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


RP> If this is true, when can we expect
RP> http://www.ietf.org/ietf/1id-guidelines.txt
RP> to be updated to reflect this change?

Probably not.

1.  There are bigger things to spend our staff resources on

2.  It is typical for formal documents to state requirements that are
more stringent than actually practised.  In this case, the deviation is
small and the benefit of following the formal requirement is real.




d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Sun Apr 20 16:28:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14687;
	Sun, 20 Apr 2003 16:28:27 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197Lgx-0007eH-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 16:45:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197LdO-0007U9-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 16:41:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14540
	for <ietf@ietf.org>; Sun, 20 Apr 2003 16:20:39 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197LL4-0004CB-00
	for ietf@ietf.org; Sun, 20 Apr 2003 16:23:02 -0400
Received: from pintail.mail.pas.earthlink.net ([207.217.120.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 197LL3-0004C8-00
	for ietf@ietf.org; Sun, 20 Apr 2003 16:23:02 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by pintail.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 197LLH-0006xA-00; Sun, 20 Apr 2003 13:23:15 -0700
Date: Sun, 20 Apr 2003 16:22:54 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: moore@cs.utk.edu, RACarlson@anl.gov, dts@senie.com, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A simple question
Message-Id: <20030420162254.6b74e8d0.moore@cs.utk.edu>
In-Reply-To: <003d01c30776$b38af6b0$93b58742@ssprunk>
References: <20030419192024.440d3773.moore@cs.utk.edu>
	<16762.1050792143@munnari.OZ.AU>
	<00d001c306c0$faeadf90$93b58742@ssprunk>
	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
	<16762.1050792143@munnari.OZ.AU>
	<5.2.1.1.2.20030420140541.0290fb00@mail.amaranth.net>
	<003d01c30776$b38af6b0$93b58742@ssprunk>
X-Mailer: Sylpheed version 0.8.11 (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

> The vast majority of applications do not pick their source address, nor is
> there a compelling reason for them to do so. 

not in IPv4.  if IPv6 has site locals more applications will need to do so.

> A large number of applications
> don't even handle multiple destination addresses properly, so expecting this
> additional intelligence for the source address is irrational.

again, you're trying to extrapolate from ipv4 experience to ipv6, but such 
experience isn't necessarily a good indicator when ipv6 presents a more 
challenging environment than ipv4.  then again, if dealing with multiple
addresses for a host was hard in ipv4, it's not going to be easier in ipv6.



From owner-ietf@ietf.org  Sun Apr 20 20:25:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19586;
	Sun, 20 Apr 2003 20:25:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197PLO-0007GB-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 20:39:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197PKY-0007Dg-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 20:38:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19488
	for <ietf@ietf.org>; Sun, 20 Apr 2003 20:17:24 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197P2B-0004yh-00
	for ietf@ietf.org; Sun, 20 Apr 2003 20:19:48 -0400
Received: from garlic.amaranth.net ([208.254.46.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 197P2B-0004ye-00
	for ietf@ietf.org; Sun, 20 Apr 2003 20:19:47 -0400
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226])
	(authenticated (0 bits))
	by garlic.amaranth.net (8.11.7/8.11.7) with ESMTP id h3L0K3801502
	(using TLSv1/SSLv3 with cipher RC4-SHA (128 bits) verified NO);
	Sun, 20 Apr 2003 20:20:04 -0400
Message-Id: <5.2.1.1.2.20030420201343.02a336c0@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Sun, 20 Apr 2003 20:19:03 -0400
To: "Stephen Sprunk" <stephen@sprunk.org>,
        "Richard Carlson" <RACarlson@anl.gov>
From: Daniel Senie <dts@senie.com>
Subject: Re: A simple question
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
In-Reply-To: <003d01c30776$b38af6b0$93b58742@ssprunk>
References: <20030419192024.440d3773.moore@cs.utk.edu>
 <16762.1050792143@munnari.OZ.AU>
 <00d001c306c0$faeadf90$93b58742@ssprunk>
 <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
 <16890640984.20030419070719@brandenburg.com>
 <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com>
 <a05210603bac6d68105ed@[10.0.0.3]>
 <11870.1050777166@munnari.OZ.AU>
 <14570.1050784897@munnari.OZ.AU>
 <16762.1050792143@munnari.OZ.AU>
 <5.2.1.1.2.20030420140541.0290fb00@mail.amaranth.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 03:50 PM 4/20/2003, Stephen Sprunk wrote:
>Thus spake "Daniel Senie" <dts@senie.com>
> > At 01:00 PM 4/20/2003, Richard Carlson wrote:
> > >The question is - how do we provide some feedback to apps that
> > >they are trying to cross a scope boundary that it's a permanent error
> > >condition (5xx in SMTP verbiage)?  One proposed notification
> > >method is the site-local prefix.  Other methods can be created, but
> > >something needs to be done and simply killing site-locals and
> > >ignoring the underlying scoping issue is a non-starter.
> >
> > You mean aside from applications understaning that an ICMP
> > Destination Unreachable / Administratively Prohibited response from
> > the site firewall?
>
>Many firewalls simply drop packets which are prohibited without sending ICMP
>responses, not to mention all the places that filter all ICMP
>indiscriminately.

Agreed, however: a) on the "protected" side of a firewall (for those 
firewalls that are configured for an "inside" and an "outside") this might 
not be the case as often, and b) if there's a strong need for appropriate 
ICMP responses to make IPv6 function well, then an RFC stating as much 
could be published. Firewall vendors could choose whether to implement 
such, but if that's an enabler for functionality then customers of such 
vendors will raise their voices.


> > For that matter, IPv6 machines arguably could try their Site Local
> > address and be given that same feedback from the border router or
> > firewall, and use the response as an indication to go use their assigned
> > global address.
>
>The vast majority of applications do not pick their source address, nor is
>there a compelling reason for them to do so.  A large number of applications
>don't even handle multiple destination addresses properly, so expecting this
>additional intelligence for the source address is irrational.

At which point they might as well just select their global address unless 
the destination address for a service is site local. This decision could 
(should?) be in the hands of the IP stack, unless the application 
specifically asks for such control.




From owner-ietf@ietf.org  Sun Apr 20 22:20:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21332;
	Sun, 20 Apr 2003 22:20:18 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197R6k-0003sj-00
	for ietf-list@ran.ietf.org; Sun, 20 Apr 2003 22:32:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197R6g-0003qJ-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 22:32:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21130
	for <ietf@ietf.org>; Sun, 20 Apr 2003 22:11:12 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197QoI-0005Jd-00
	for ietf@ietf.org; Sun, 20 Apr 2003 22:13:34 -0400
Received: from turkey.mail.pas.earthlink.net ([207.217.120.126])
	by ietf-mx with esmtp (Exim 4.12)
	id 197QoH-0005JZ-00
	for ietf@ietf.org; Sun, 20 Apr 2003 22:13:33 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by turkey.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 197QoP-0001vR-00; Sun, 20 Apr 2003 19:13:41 -0700
Date: Sun, 20 Apr 2003 22:13:19 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Daniel Senie <dts@senie.com>
Cc: moore@cs.utk.edu, stephen@sprunk.org, RACarlson@anl.gov, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A simple question
Message-Id: <20030420221319.62964599.moore@cs.utk.edu>
In-Reply-To: <5.2.1.1.2.20030420201343.02a336c0@mail.amaranth.net>
References: <20030419192024.440d3773.moore@cs.utk.edu>
	<16762.1050792143@munnari.OZ.AU>
	<00d001c306c0$faeadf90$93b58742@ssprunk>
	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
	<16762.1050792143@munnari.OZ.AU>
	<5.2.1.1.2.20030420140541.0290fb00@mail.amaranth.net>
	<5.2.1.1.2.20030420201343.02a336c0@mail.amaranth.net>
X-Mailer: Sylpheed version 0.8.11 (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

> b) if there's a strong need for appropriate 
> ICMP responses to make IPv6 function well, then an RFC stating as much 
> could be published.

like, for instance, a need for path mtu discovery to work reliably?
(since v6 routers don't fragment packets)

> >The vast majority of applications do not pick their source address, nor is
> >there a compelling reason for them to do so.  A large number of
> >applications don't even handle multiple destination addresses properly, so
> >expecting this additional intelligence for the source address is
> >irrational.
> 
> At which point they might as well just select their global address unless 
> the destination address for a service is site local. This decision could 
> (should?) be in the hands of the IP stack, unless the application 
> specifically asks for such control.

I disagree that the IP stack can supply reasonable defaults in the face of
multiple scopes.  The criteria for choosing a source address varies widely
from one application to another.  Some applications need stable addresses,
others need addresses usable from all of their potential peers, others need to
choose the source address that results in the best performance (where there is
more than one meaning of 'best performance').  The default address selection
rules are at best a guess.  

We should let the network do routing, so that hosts and apps aren't expected
to make routing decisions.



From owner-ietf@ietf.org  Mon Apr 21 01:22:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23639;
	Mon, 21 Apr 2003 01:22:24 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197Txq-0002xa-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 01:35:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197Txa-0002vG-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 01:35:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23546
	for <ietf@ietf.org>; Mon, 21 Apr 2003 01:13:57 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197TfA-0005mr-00
	for ietf@ietf.org; Mon, 21 Apr 2003 01:16:20 -0400
Received: from tomts14-srv.bellnexxia.net ([209.226.175.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 197TfA-0005mo-00
	for ietf@ietf.org; Mon, 21 Apr 2003 01:16:20 -0400
Received: from yahoo.com ([65.93.186.59]) by tomts14-srv.bellnexxia.net
          (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP
          id <20030421051636.YAYE4232.tomts14-srv.bellnexxia.net@yahoo.com>;
          Mon, 21 Apr 2003 01:16:36 -0400
Date: Mon, 21 Apr 2003 01:16:34 -0400
Subject: Re: A simple question
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Markku Savela <msa@burp.tkv.asdf.org>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <200304201529.h3KFTXar007244@burp.tkv.asdf.org>
Message-Id: <6B5035F2-73B8-11D7-BF62-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Sunday, April 20, 2003, at 11:29  AM, Markku Savela wrote:

> However, theoretical examples wont do. I want to see a program name
> and an URL where I can download source for a study. Surely, if many
> applications fail with site locals, there can be at least one existing
> open source application?
>
> Just ONE such example, please?

ohPhoneX

http://xmeeting.sourceforge.net/

Uses the H.323 stack for VoIP.

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Mon Apr 21 07:40:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10022;
	Mon, 21 Apr 2003 07:40:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197Zre-0007CN-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 07:53:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197Zld-00074I-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 07:47:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09520
	for <ietf@ietf.org>; Mon, 21 Apr 2003 07:25:57 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197ZT9-0006qM-00
	for ietf@ietf.org; Mon, 21 Apr 2003 07:28:19 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 197ZT9-0006qJ-00
	for ietf@ietf.org; Mon, 21 Apr 2003 07:28:19 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 197ZTP-0008Wr-00; Mon, 21 Apr 2003 06:28:35 -0500
Date: Mon, 21 Apr 2003 07:28:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@cs.utk.edu>
cc: "ietf@ietf.org" <ietf@ietf.org>,
        "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>
Subject: Re: A simple question
Message-ID: <70757023.1050910115@p3.JCK.COM>
In-Reply-To: <20030420221319.62964599.moore@cs.utk.edu>
References: <20030419192024.440d3773.moore@cs.utk.edu>
 	<16762.1050792143@munnari.OZ.AU>
 	<00d001c306c0$faeadf90$93b58742@ssprunk>
 	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
 	<16890640984.20030419070719@brandenburg.com>
 	<002401c30605$e22da070$261e4104@eagleswings>
 	<9540645034.20030418171403@brandenburg.com>
 	<a05210603bac6d68105ed@[10.0.0.3]>
 	<11870.1050777166@munnari.OZ.AU>	<14570.1050784897@munnari.OZ.AU>
 	<16762.1050792143@munnari.OZ.AU>
 	<5.2.1.1.2.20030420140541.0290fb00@mail.amaranth.net>
 	<5.2.1.1.2.20030420201343.02a336c0@mail.amaranth.net>
 <20030420221319.62964599.moore@cs.utk.edu>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Sunday, 20 April, 2003 22:13 -0400 Keith Moore 
<moore@cs.utk.edu> wrote:

>> At which point they might as well just select their global
>> address unless  the destination address for a service is site
>> local. This decision could  (should?) be in the hands of the
>> IP stack, unless the application  specifically asks for such
>> control.
>
> I disagree that the IP stack can supply reasonable defaults in
> the face of multiple scopes.  The criteria for choosing a
> source address varies widely from one application to another.
> Some applications need stable addresses, others need addresses
> usable from all of their potential peers, others need to
> choose the source address that results in the best performance
> (where there is more than one meaning of 'best performance').
> The default address selection rules are at best a guess.
>
> We should let the network do routing, so that hosts and apps
> aren't expected to make routing decisions.

Keith,

I don't understand your point here, and would like to.  It seems 
to me that your first paragraph ("I disagree...") suggests that 
the applications need to specify the addresses/interfaces 
because they know their needs and the stack can't figure it out. 
And the second argues for pushing the decisions onto the 
network, which has no information at all (and, if it had it, 
could probably apply it only by changing addresses mid-flight -- 
NAT-like or worse).  That suggests to me a conclusion of "not 
application, not stack, not network either" which leaves very 
few options.

If I ignore that apparent contradiction, I'm left with the 
conclusion that we need some new addressing and routing 
abstractions so that the applications can tell the stack (and 
the stack might tell, or negotiate with, the network) what 
considerations they need optimized and do so without specifying 
specific addresses or inspecting components of addresses.  It 
seems to me that such abstractions would also eliminate one of 
the arguments against site local: having an application able to 
tell the stack:

	* I need a local address
	
	* I need an appropriate address for routing to <DNS name>
	
	* I need a completely-global address

Are all far more reasonable than having the application itself 
recognize particular addresses or prefixes and trying to figure 
out which ones make sense in its context.  It also _might_ 
suggest that we need to reexamine ICMP in the IPv6 context to be 
sure that, if the stack needs information from the network to 
make satisfactory choices along these lines, it can ask them 
without, e.g., trying to set up one or more TCP connections (or 
sending UDP packet using an unspecified protocol) and waiting 
for the responses or timeouts.

Is that really where we need to be headed and, if so, is anyone 
doing the work rather than being stuck on "local-good / 
local-bad", "scope-necessary / scope-bad", types of arguments?

      john




From owner-ietf@ietf.org  Mon Apr 21 13:28:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23154;
	Mon, 21 Apr 2003 13:28:11 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197fIS-0005J0-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 13:41:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197fHZ-0005FH-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 13:40:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22767
	for <ietf@ietf.org>; Mon, 21 Apr 2003 13:19:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197ez1-0001fY-00
	for ietf@ietf.org; Mon, 21 Apr 2003 13:21:35 -0400
Received: from albatross.mail.pas.earthlink.net ([207.217.120.120])
	by ietf-mx with esmtp (Exim 4.12)
	id 197ez1-0001fE-00
	for ietf@ietf.org; Mon, 21 Apr 2003 13:21:35 -0400
Received: from h-68-164-29-68.snvacaid.covad.net ([68.164.29.68] helo=oemcomputer)
	by albatross.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 197eye-0007ih-00
	for ietf@ietf.org; Mon, 21 Apr 2003 10:21:12 -0700
Message-ID: <000801c3082a$9bad9980$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <20030418131636.75791.qmail@web10907.mail.yahoo.com> <132275752.20030418063433@brandenburg.com> <005701c3076d$6d626320$7f1afea9@oemcomputer> <4196703714.20030420123505@brandenburg.com>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
Date: Mon, 21 Apr 2003 10:22:38 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi -

> From: "Dave Crocker" <dhc2@dcrocker.net>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: <ietf@ietf.org>
> Sent: Sunday, April 20, 2003 12:35 PM
> Subject: Re: Internet Draft Guidelines Require Precise Formatting?
>

>
> RP> If this is true, when can we expect
> RP> http://www.ietf.org/ietf/1id-guidelines.txt
> RP> to be updated to reflect this change?
>
> Probably not.
>
> 1.  There are bigger things to spend our staff resources on
>
> 2.  It is typical for formal documents to state requirements that are
> more stringent than actually practised.  In this case, the deviation is
> small and the benefit of following the formal requirement is real.
...

Ok, let me ask another way:
Who has the list of which items from
http://www.ietf.org/ietf/1id-guidelines.txt
that can be ignored, particularly when we're
reviewing documents before giving them to the IESG?

Randy






From owner-ietf@ietf.org  Mon Apr 21 14:10:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24628;
	Mon, 21 Apr 2003 14:10:32 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197g01-00089d-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 14:26:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197fuk-0007xb-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 14:21:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24407
	for <ietf@ietf.org>; Mon, 21 Apr 2003 13:59:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197fcA-00022r-00
	for ietf@ietf.org; Mon, 21 Apr 2003 14:02:02 -0400
Received: from h-135-207-24-32.research.att.com ([135.207.24.32] helo=mailman.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 197fc9-00022T-00
	for ietf@ietf.org; Mon, 21 Apr 2003 14:02:01 -0400
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mailman.research.att.com (8.12.8/8.12.8) with ESMTP id h3LHxJ7a007344;
	Mon, 21 Apr 2003 13:59:29 -0400
Received: from berkshire.research.att.com (raptor.research.att.com [135.207.23.32])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h3LI1IV00176;
	Mon, 21 Apr 2003 14:01:18 -0400 (EDT)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id 9934C7B4D; Mon, 21 Apr 2003 14:01:17 -0400 (EDT)
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>
Cc: ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting? 
In-Reply-To: Your message of "Sun, 20 Apr 2003 11:48:26 PDT."
             <005701c3076d$6d626320$7f1afea9@oemcomputer> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 21 Apr 2003 14:01:17 -0400
Message-Id: <20030421180117.9934C7B4D@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <005701c3076d$6d626320$7f1afea9@oemcomputer>, "Randy Presuhn" writes
:
>Hi -
>
>> From: "Dave Crocker" <dhc2@dcrocker.net>
>> To: "Spencer Dawkins" <spencer_dawkins@yahoo.com>
>> Cc: <ietf@ietf.org>
>> Sent: Friday, April 18, 2003 6:34 AM
>> Subject: Re: Internet Draft Guidelines Require Precise Formatting?
>...
>
>> For Internet-Drafts, page-breaks are not required.
>...
>
>If this is true, when can we expect
>http://www.ietf.org/ietf/1id-guidelines.txt
>to be updated to reflect this change?
>

Page breaks are highly desirable for I-Ds, because it makes it easier 
for people to print them out.  They're much less necessary when things 
are moving to the RFC stage, because the RFC editor is going to strip 
all the formatting from the I-D and start from there.

		--Steve Bellovin, http://www.research.att.com/~smb (me)
		http://www.wilyhacker.com (2nd edition of "Firewalls" book)





From owner-ietf@ietf.org  Mon Apr 21 15:05:53 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26960;
	Mon, 21 Apr 2003 15:05:53 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197gfv-0001W1-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 15:09:59 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197gVp-0001CR-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 14:59:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25669
	for <ietf@ietf.org>; Mon, 21 Apr 2003 14:37:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197gDG-0002Gw-00
	for ietf@ietf.org; Mon, 21 Apr 2003 14:40:22 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 197gDF-0002Gt-00
	for ietf@ietf.org; Mon, 21 Apr 2003 14:40:21 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 197gDV-000AHM-00; Mon, 21 Apr 2003 13:40:37 -0500
Date: Mon, 21 Apr 2003 14:40:37 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Steven M. Bellovin" <smb@research.att.com>,
        Randy Presuhn <randy_presuhn@mindspring.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Internet Draft Guidelines Require Precise
 Formatting?
Message-ID: <96678326.1050936037@p3.JCK.COM>
In-Reply-To: <20030421180117.9934C7B4D@berkshire.research.att.com>
References:  <20030421180117.9934C7B4D@berkshire.research.att.com>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Monday, 21 April, 2003 14:01 -0400 "Steven M. Bellovin" 
<smb@research.att.com> wrote:

> In message <005701c3076d$6d626320$7f1afea9@oemcomputer>,
> "Randy Presuhn" writes :

>...
>>> For Internet-Drafts, page-breaks are not required.
>> ...
>>
>> If this is true, when can we expect
>> http://www.ietf.org/ietf/1id-guidelines.txt
>> to be updated to reflect this change?
>
> Page breaks are highly desirable for I-Ds, because it makes it
> easier  for people to print them out.  They're much less
> necessary when things  are moving to the RFC stage, because
> the RFC editor is going to strip  all the formatting from the
> I-D and start from there.

Steve,

Interesting you say that.  I know of very few systems and modern 
printers these days that handle "printing things out" which 
cannot generate the page breaks for printing in a dynamic way. 
Those devices and their drivers, and print-preparation programs, 
even tend to know how to differentiate between 8.5x11 and A4 
paper, and two-up arrangements, and how to do the right thing. 
That was less the case when most printing was done on 
continuous-form paper and pagination tended to keep printed 
lines off the perforations.  But I doubt that many of us are 
dependent on those sorts of devices today and those who are 
still don't have paginating drivers, or "pr" or equivalent 
pipes, available.

The I-D administrator does prefer that documents be paginated 
because the IESG has told the secretariat that I-D announcements 
should show the number of pages in the I-D.   Maybe some 
adjustment there would be in order.

By contrast, the RFC Editor has, on at least some recent 
documents, complained about lack of pagination, lack of a table 
of contents with filled-in page numbers, etc.   Like you, I 
would have assumed that they would be better off without those 
things on the grounds that they would just have to strip them 
off, making extra work, but that seems to not be the case.

     john




From owner-ietf@ietf.org  Mon Apr 21 15:05:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26975;
	Mon, 21 Apr 2003 15:05:54 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197grI-0003tu-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 15:21:44 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197gqm-0003ku-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 15:21:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26271
	for <ietf@ietf.org>; Mon, 21 Apr 2003 14:59:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197gYD-0002Ps-00
	for ietf@ietf.org; Mon, 21 Apr 2003 15:02:01 -0400
Received: from mail.proper.com ([208.184.76.45] helo=above.proper.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 197gYC-0002Pg-00
	for ietf@ietf.org; Mon, 21 Apr 2003 15:02:00 -0400
Received: from [63.202.92.152] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	by above.proper.com (8.12.8p1/8.12.8) with ESMTP id h3LJ2Jt3058487
	for <ietf@ietf.org>; Mon, 21 Apr 2003 12:02:19 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05210622bac9f0404d48@[63.202.92.152]>
In-Reply-To: <20030421180117.9934C7B4D@berkshire.research.att.com>
References: <20030421180117.9934C7B4D@berkshire.research.att.com>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Mon, 21 Apr 2003 12:02:17 -0700
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

>Page breaks are highly desirable for I-Ds, because it makes it easier
>for people to print them out.

Um, which software that takes a long text file *doesn't* put in page 
breaks as it sends it to the printer? This has been a standard part 
of nearly every word processing and text editing program for two 
decades now...

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Mon Apr 21 15:17:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28528;
	Mon, 21 Apr 2003 15:17:37 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197h47-0001xm-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 15:34:59 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197h3N-0001UA-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 15:34:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28016
	for <ietf@ietf.org>; Mon, 21 Apr 2003 15:12:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197gko-0002cW-00
	for ietf@ietf.org; Mon, 21 Apr 2003 15:15:02 -0400
Received: from spitfire.law.miami.edu ([129.171.187.10] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 197gkn-0002cT-00
	for ietf@ietf.org; Mon, 21 Apr 2003 15:15:01 -0400
Received: from spitfire.law.miami.edu (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id 20D165C3AF3; Mon, 21 Apr 2003 15:15:23 -0400 (EDT)
Received: by spitfire.law.miami.edu (Postfix, from userid 1113)
	id CA9215C3AF3; Mon, 21 Apr 2003 15:15:22 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id BD4005D3D0C; Mon, 21 Apr 2003 15:15:22 -0400 (EDT)
Date: Mon, 21 Apr 2003 15:15:22 -0400 (EDT)
From: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
To: Paul Hoffman / IMC <phoffman@imc.org>
Cc: ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
In-Reply-To: <p05210622bac9f0404d48@[63.202.92.152]>
Message-ID: <Pine.LNX.4.10.10304211513330.12064-100000@spitfire.law.miami.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

While right-thinking people no doubt cite to paragraph and section
numbers, the world is not entirely composed of right-thinking people.  
Having consistent canonical page numbers eliminates a source of potential
confusion especially when dealing with groups outside the IETF...

On Mon, 21 Apr 2003, Paul Hoffman / IMC wrote:

> >Page breaks are highly desirable for I-Ds, because it makes it easier
> >for people to print them out.
> 
> Um, which software that takes a long text file *doesn't* put in page 
> breaks as it sends it to the printer? This has been a standard part 
> of nearly every word processing and text editing program for two 
> decades now...
> 
> --Paul Hoffman, Director
> --Internet Mail Consortium
> 
> 

-- 
		Please visit http://www.icannwatch.org
A. Michael Froomkin   |    Professor of Law    |   froomkin@law.tm
U. Miami School of Law, P.O. Box 248087, Coral Gables, FL 33124 USA
+1 (305) 284-4285  |  +1 (305) 284-6506 (fax)  |  http://www.law.tm
                        -->It's warm here.<--




From owner-ietf@ietf.org  Mon Apr 21 16:38:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01182;
	Mon, 21 Apr 2003 16:38:35 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197iHJ-0001xa-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 16:52:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197iGb-0001pT-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 16:51:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00908
	for <ietf@ietf.org>; Mon, 21 Apr 2003 16:30:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197hy0-00033o-00
	for ietf@ietf.org; Mon, 21 Apr 2003 16:32:44 -0400
Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 197hxz-00033l-00
	for ietf@ietf.org; Mon, 21 Apr 2003 16:32:44 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h3LKTvc15824;
	Mon, 21 Apr 2003 22:29:57 +0200
Message-ID: <3EA454C5.4050609@it.su.se>
Date: Mon, 21 Apr 2003 22:29:57 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Daniel Senie <dts@senie.com>, stephen@sprunk.org, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A simple question
References: <20030419151329.66daf0de.moore@cs.utk.edu>	<16890640984.20030419070719@brandenburg.com>	<002401c30605$e22da070$261e4104@eagleswings>	<9540645034.20030418171403@brandenburg.com>	<a05210603bac6d68105ed@[10.0.0.3]>	<11870.1050777166@munnari.OZ.AU>	<14384.1050784134@munnari.OZ.AU>	<20030419165921.782a8353.moore@cs.utk.edu>	<5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net> <20030419191507.75dfcc39.moore@cs.utk.edu>
In-Reply-To: <20030419191507.75dfcc39.moore@cs.utk.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:

>because few serious applications people were in the discussion, and there
>wasn't enough review by those people during Last Call.  most apps people
>probably assumed that the changes between IPv4 and IPv6 would be transparent
>to them, other than having to use a different size for the address.
>
>  
>
I believe this is essentially correct.




From owner-ietf@ietf.org  Mon Apr 21 16:48:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01729;
	Mon, 21 Apr 2003 16:48:35 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197iVL-00032y-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 17:07:11 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197iQl-0002xg-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 17:02:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01348
	for <ietf@ietf.org>; Mon, 21 Apr 2003 16:40:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197i8B-00038p-00
	for ietf@ietf.org; Mon, 21 Apr 2003 16:43:15 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 197i8A-00038m-00
	for ietf@ietf.org; Mon, 21 Apr 2003 16:43:14 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 197i8V-000AkY-00; Mon, 21 Apr 2003 15:43:35 -0500
Date: Mon, 21 Apr 2003 16:43:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Internet Draft Guidelines Require Precise
 Formatting?
Message-ID: <104056845.1050943415@p3.JCK.COM>
In-Reply-To: <Pine.LNX.4.10.10304211513330.12064-100000@spitfire.law.miami.edu>
References:  <Pine.LNX.4.10.10304211513330.12064-100000@spitfire.l
 aw.miami.edu>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Michael,

We have "consistent canonical page numbers" in RFCs, which are 
stable documents.   Citations to page numbers in I-Ds are just 
an invitation to trouble and confusion, since an external page 
reference to some particular material in, e.g., draft-...-01 is 
unlikely to be stable into draft-...-03 and draft-...01 is 
unlikely to be readily available.  Of course, this is also one 
of the reasons why our formal position is that I-Ds are not to 
be referenced or cited: when someone violates that rule, they 
are on their own, and neither page numbers nor paragraph/ 
section numbers are going to help them much.

     john


--On Monday, 21 April, 2003 15:15 -0400 "Michael Froomkin - 
U.Miami School of Law" <froomkin@law.miami.edu> wrote:

> While right-thinking people no doubt cite to paragraph and
> section numbers, the world is not entirely composed of
> right-thinking people.   Having consistent canonical page
> numbers eliminates a source of potential confusion especially
> when dealing with groups outside the IETF...
>
> On Mon, 21 Apr 2003, Paul Hoffman / IMC wrote:
>
>> > Page breaks are highly desirable for I-Ds, because it makes
>> > it easier for people to print them out.
>>
>> Um, which software that takes a long text file *doesn't* put
>> in page  breaks as it sends it to the printer? This has been
>> a standard part  of nearly every word processing and text
>> editing program for two  decades now...
>>
>> --Paul Hoffman, Director
>> --Internet Mail Consortium
>>
>>
>
> --
> 		Please visit http://www.icannwatch.org
> A. Michael Froomkin   |    Professor of Law    |
> froomkin@law.tm U. Miami School of Law, P.O. Box 248087, Coral
> Gables, FL 33124 USA +1 (305) 284-4285  |  +1 (305) 284-6506
> (fax)  |  http://www.law.tm                         -->It's
> warm here.<--
>
>







From owner-ietf@ietf.org  Mon Apr 21 16:55:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02071;
	Mon, 21 Apr 2003 16:55:22 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197ibd-0004Bv-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 17:13:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197ibK-00047T-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 17:13:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01993
	for <ietf@ietf.org>; Mon, 21 Apr 2003 16:51:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197iIk-0003Hs-00
	for ietf@ietf.org; Mon, 21 Apr 2003 16:54:10 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 197iIj-0003Ha-00
	for ietf@ietf.org; Mon, 21 Apr 2003 16:54:09 -0400
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h3LKrbgE024038;
	Mon, 21 Apr 2003 13:53:37 -0700 (PDT)
Received: (ole@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) id NAA20565; Mon, 21 Apr 2003 13:53:37 -0700 (PDT)
X-Authentication-Warning: wells.cisco.com: ole set sender to ole@cisco.com using -f
Date: Mon, 21 Apr 2003 13:53:37 -0700 (PDT)
From: "Ole J. Jacobsen" <ole@cisco.com>
Reply-To: Ole Jacobsen <ole@cisco.com>
To: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
cc: Paul Hoffman / IMC <phoffman@imc.org>, <ietf@ietf.org>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
In-Reply-To: <Pine.LNX.4.10.10304211513330.12064-100000@spitfire.law.miami.edu>
Message-ID: <Pine.HPX.4.44.0304211353100.16806-100000@wells.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Isn't it LINE numbers you lawyers want?  :-)

Ole



Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj



On Mon, 21 Apr 2003, Michael Froomkin - U.Miami School of Law wrote:

> While right-thinking people no doubt cite to paragraph and section
> numbers, the world is not entirely composed of right-thinking people.
> Having consistent canonical page numbers eliminates a source of potential
> confusion especially when dealing with groups outside the IETF...
>
> On Mon, 21 Apr 2003, Paul Hoffman / IMC wrote:
>
> > >Page breaks are highly desirable for I-Ds, because it makes it easier
> > >for people to print them out.
> >
> > Um, which software that takes a long text file *doesn't* put in page
> > breaks as it sends it to the printer? This has been a standard part
> > of nearly every word processing and text editing program for two
> > decades now...
> >
> > --Paul Hoffman, Director
> > --Internet Mail Consortium
> >
> >
>
> --
> 		Please visit http://www.icannwatch.org
> A. Michael Froomkin   |    Professor of Law    |   froomkin@law.tm
> U. Miami School of Law, P.O. Box 248087, Coral Gables, FL 33124 USA
> +1 (305) 284-4285  |  +1 (305) 284-6506 (fax)  |  http://www.law.tm
>                         -->It's warm here.<--
>
>




From owner-ietf@ietf.org  Mon Apr 21 17:24:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03100;
	Mon, 21 Apr 2003 17:24:03 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197j1m-0006EK-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 17:40:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197j0W-00066w-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 17:39:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02936
	for <ietf@ietf.org>; Mon, 21 Apr 2003 17:17:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197ihw-0003UA-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:20:12 -0400
Received: from spitfire.law.miami.edu ([129.171.187.10] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 197ihv-0003U7-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:20:11 -0400
Received: from spitfire.law.miami.edu (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id A0A965C3B37; Mon, 21 Apr 2003 17:20:33 -0400 (EDT)
Received: by spitfire.law.miami.edu (Postfix, from userid 1113)
	id 704215C3B37; Mon, 21 Apr 2003 17:20:33 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id 61F4A5D3D0C; Mon, 21 Apr 2003 17:20:33 -0400 (EDT)
Date: Mon, 21 Apr 2003 17:20:33 -0400 (EDT)
From: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
To: "Ole J. Jacobsen" <ole@cisco.com>
Cc: Paul Hoffman / IMC <phoffman@imc.org>, ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
In-Reply-To: <Pine.HPX.4.44.0304211353100.16806-100000@wells.cisco.com>
Message-ID: <Pine.LNX.4.10.10304211717390.12064-100000@spitfire.law.miami.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Can't hurt!

But seriously, that's only found in documents designed to be submitted to
courts, presumably so the written transcript is clear as to what is being
discussed ("Mr. X, I direct your attention to exibit A32, page 912, line
6, did you or did you not say that....")

Meanwhile John K. explains to me that since no one is supposed to cite
ID's it shouldn't be made easy.  Maybe he shoulda been a lawyer?

On Mon, 21 Apr 2003, Ole J. Jacobsen wrote:

> Isn't it LINE numbers you lawyers want?  :-)
> 
> Ole
> 
> 
> 
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Tel: +1 408-527-8972   GSM: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> 
> 
> 
> On Mon, 21 Apr 2003, Michael Froomkin - U.Miami School of Law wrote:
> 
> > While right-thinking people no doubt cite to paragraph and section
> > numbers, the world is not entirely composed of right-thinking people.
> > Having consistent canonical page numbers eliminates a source of potential
> > confusion especially when dealing with groups outside the IETF...
> >
> > On Mon, 21 Apr 2003, Paul Hoffman / IMC wrote:
> >
> > > >Page breaks are highly desirable for I-Ds, because it makes it easier
> > > >for people to print them out.
> > >
> > > Um, which software that takes a long text file *doesn't* put in page
> > > breaks as it sends it to the printer? This has been a standard part
> > > of nearly every word processing and text editing program for two
> > > decades now...
> > >
> > > --Paul Hoffman, Director
> > > --Internet Mail Consortium
> > >
> > >
> >
> > --
> > 		Please visit http://www.icannwatch.org
> > A. Michael Froomkin   |    Professor of Law    |   froomkin@law.tm
> > U. Miami School of Law, P.O. Box 248087, Coral Gables, FL 33124 USA
> > +1 (305) 284-4285  |  +1 (305) 284-6506 (fax)  |  http://www.law.tm
> >                         -->It's warm here.<--
> >
> >
> 
> 

-- 
		Please visit http://www.icannwatch.org
A. Michael Froomkin   |    Professor of Law    |   froomkin@law.tm
U. Miami School of Law, P.O. Box 248087, Coral Gables, FL 33124 USA
+1 (305) 284-4285  |  +1 (305) 284-6506 (fax)  |  http://www.law.tm
                        -->It's warm here.<--




From owner-ietf@ietf.org  Mon Apr 21 17:24:05 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03126;
	Mon, 21 Apr 2003 17:24:05 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197j1n-0006EQ-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 17:40:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197j1g-00069k-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 17:40:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02948
	for <ietf@ietf.org>; Mon, 21 Apr 2003 17:19:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197ij6-0003UN-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:21:24 -0400
Received: from h-135-207-24-32.research.att.com ([135.207.24.32] helo=mailman.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 197ij5-0003UD-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:21:23 -0400
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mailman.research.att.com (8.12.8/8.12.8) with ESMTP id h3LLHt7a015689;
	Mon, 21 Apr 2003 17:18:10 -0400
Received: from berkshire.research.att.com (guard.research.att.com [135.207.1.20])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h3LLJrV15269;
	Mon, 21 Apr 2003 17:19:53 -0400 (EDT)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id B63157B4D; Mon, 21 Apr 2003 17:19:52 -0400 (EDT)
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: Ole Jacobsen <ole@cisco.com>
Cc: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>,
        Paul Hoffman / IMC <phoffman@imc.org>, ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting? 
In-Reply-To: Your message of "Mon, 21 Apr 2003 13:53:37 PDT."
             <Pine.HPX.4.44.0304211353100.16806-100000@wells.cisco.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 21 Apr 2003 17:19:52 -0400
Message-Id: <20030421211952.B63157B4D@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <Pine.HPX.4.44.0304211353100.16806-100000@wells.cisco.com>, "Ole J. 
Jacobsen" writes:
>Isn't it LINE numbers you lawyers want?  :-)
>

In places; elsewhere, it's page number.  A typical case citation is 
something like 60 F.2d 737, which means "page 737 of volume 60 of the 
Federal Reporter, Second Series".  In other words, the page number in 
the physical volume *is* a canonical references.  This has led to some 
interesting copyright litigation; opinions, being government documents, 
aren't copyrightable, but what about the physical layout done by the 
authorized publisher, which is the only thing that can be cited?  (I 
don't recall how those cases were resolved.)

		--Steve Bellovin, http://www.research.att.com/~smb (me)
		http://www.wilyhacker.com (2nd edition of "Firewalls" book)





From owner-ietf@ietf.org  Mon Apr 21 17:51:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03968;
	Mon, 21 Apr 2003 17:51:33 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197jPz-0008Ad-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 18:05:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197jN4-0007wu-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 18:02:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03725
	for <ietf@ietf.org>; Mon, 21 Apr 2003 17:41:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197j4T-0003fI-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:43:29 -0400
Received: from ns.live.com ([66.80.62.34])
	by ietf-mx with esmtp (Exim 4.12)
	id 197j4S-0003fF-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:43:28 -0400
Received: from ns.live.com (localhost.live.com [127.0.0.1])
	by ns.live.com (8.12.9/8.12.5) with ESMTP id h3LLhn1d073942
	for <ietf@ietf.org>; Mon, 21 Apr 2003 14:43:49 -0700 (PDT)
	(envelope-from rsf@ns.live.com)
Received: (from rsf@localhost)
	by ns.live.com (8.12.9/8.12.3/Submit) id h3LLhnCB073941;
	Mon, 21 Apr 2003 14:43:49 -0700 (PDT)
Message-Id: <4.3.1.1.20030421143850.00b7b340@laptop-localhost>
X-Sender: rsf@laptop-localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Mon, 21 Apr 2003 14:42:52 -0700
To: ietf@ietf.org
From: Ross Finlayson <finlayson@live.com>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
In-Reply-To: <p05210622bac9f0404d48@[63.202.92.152]>
References: <20030421180117.9934C7B4D@berkshire.research.att.com>
 <20030421180117.9934C7B4D@berkshire.research.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:02 PM 4/21/03, Paul Hoffman / IMC wrote:
>>Page breaks are highly desirable for I-Ds, because it makes it easier
>>for people to print them out.
>
>Um, which software that takes a long text file *doesn't* put in page 
>breaks as it sends it to the printer? This has been a standard part of 
>nearly every word processing and text editing program for two decades now...

Indeed.  Why continue this archaic mid-20th century nonsense?

I, personally, will never waste a second of my own time inserting page 
breaks in any I-D that I write.

         Ross.




From owner-ietf@ietf.org  Mon Apr 21 17:53:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04114;
	Mon, 21 Apr 2003 17:53:20 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197jUn-0000i3-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 18:10:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197jU9-0000dz-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 18:10:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03883
	for <ietf@ietf.org>; Mon, 21 Apr 2003 17:48:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197jBY-0003ht-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:50:48 -0400
Received: from router.boolean.net
	([198.144.206.49] helo=pretender.boolean.net ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 197jBX-0003hp-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:50:47 -0400
Received: from nomad.OpenLDAP.org (kurt@localhost [127.0.0.1])
	by pretender.boolean.net (8.12.8/8.12.8) with ESMTP id h3LLoxDV027138;
	Mon, 21 Apr 2003 21:51:00 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <5.2.0.9.0.20030421143516.0258dd00@127.0.0.1>
X-Sender: kurt@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 21 Apr 2003 14:48:41 -0700
To: Leif Johansson <leifj@it.su.se>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: A simple question
Cc: Keith Moore <moore@cs.utk.edu>, Daniel Senie <dts@senie.com>,
        stephen@sprunk.org, ietf@ietf.org, ipng@sunroof.eng.sun.com
In-Reply-To: <3EA454C5.4050609@it.su.se>
References: <20030419191507.75dfcc39.moore@cs.utk.edu>
 <20030419151329.66daf0de.moore@cs.utk.edu>
 <16890640984.20030419070719@brandenburg.com>
 <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com>
 <a05210603bac6d68105ed@[10.0.0.3]>
 <11870.1050777166@munnari.OZ.AU>
 <14384.1050784134@munnari.OZ.AU>
 <20030419165921.782a8353.moore@cs.utk.edu>
 <5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
 <20030419191507.75dfcc39.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 01:29 PM 4/21/2003, Leif Johansson wrote:
>Keith Moore wrote:
>
>>because few serious applications people were in the discussion, and there
>>wasn't enough review by those people during Last Call.  most apps people
>>probably assumed that the changes between IPv4 and IPv6 would be transparent
>>to them, other than having to use a different size for the address.
>>
>> 
>I believe this is essentially correct. 

s/applications/applications and security/

PKI ipAddress [RFC 3280, 4.2.1.7] altSubject name is
a good example of how application and security folks
have/haven't dealt with IPv6 addressing issues.

Kurt 




From owner-ietf@ietf.org  Mon Apr 21 18:14:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05537;
	Mon, 21 Apr 2003 18:14:01 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197jp9-0007PU-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 18:31:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197joL-00073r-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 18:30:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05082
	for <ietf@ietf.org>; Mon, 21 Apr 2003 18:09:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197jVj-0003t2-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:11:39 -0400
Received: from mail.cdt.org ([206.112.85.61])
	by ietf-mx with esmtp (Exim 4.12)
	id 197jVj-0003sf-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:11:39 -0400
Received: from [10.0.1.12] (66.safeclick.net [63.119.245.66])
	by mail.cdt.org (Postfix) with ESMTP
	id 2B53249005E; Mon, 21 Apr 2003 17:58:38 -0400 (EDT)
Mime-Version: 1.0
X-Sender: john@mail.cdt.org
Message-Id: <a05200f0abaca130b6bba@[10.0.1.12]>
In-Reply-To: 
 <Pine.LNX.4.10.10304211513330.12064-100000@spitfire.law.miami.edu>
References: 
 <Pine.LNX.4.10.10304211513330.12064-100000@spitfire.law.miami.edu>
Date: Mon, 21 Apr 2003 18:11:28 -0400
To: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
From: John Morris <jmorris@cdt.org>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 3:15 PM -0400 4/21/03, Michael Froomkin - U.Miami School of Law wrote:
>While right-thinking people no doubt cite to paragraph and section
>numbers, the world is not entirely composed of right-thinking people. 
>Having consistent canonical page numbers eliminates a source of potential
>confusion especially when dealing with groups outside the IETF...

Certainly agreed.  But it is also true that the formatting 
requirements for I-Ds are one of many obstacles to "outside" 
participation in the IETFprocess.   Although it may seem silly to 
some (and some of you may not want to hear from them anyway), the 
IETF's formatting rules do present a (relatively small) hurdle to 
public policy advocates and other outsiders.

I personally think that there is value in allowing those less 
familiar with the IETF an easier way to express their views in a 
standard format acceptable to the IETF.  And frankly, it would give 
the often seen reaction (blowoff?) "write it up and submit it as an 
I-D" more power if the I-D route was a little easier for non-IETFers.

So at the risk of heresy, I would consider expressly allowing an 
OPTIONAL "more lenient" format for "individual" I-Ds.  Specifically, 
I would suggest a rule saying that the lenient format CANNOT be used 
for:
   - any WG-chartered I-D
   - any individual I-D which is proposed to move RFC status
   - any I-D for which formal IESG/IAB review is sought for any other purpose

So basically the lenient format could be used to raise initial ideas 
and express initial input to the IETF community.  Any document that 
is intended to proceed through the formal editing and review 
processes of the IETF, however, would need to be in the stricter 
format (thereby facilitating debate and discussion using page 
references).

To be clear, I do not think there is a need to reduce the substantive 
requirements (e.g., IPR statement, security considerations, etc.) -- 
those can be included in a "lenient" template, and sometimes they (in 
theory) increase the intellectual rigor of the document.

If there is interest in this idea, then I would want to see if we 
could arrive at a lenient format that would be (a) easily producable 
with standard word processing software (even if one has to, for 
example, "print to file" using a generic printer driver), and (b) 
would still be close enough to pure ASCII so that it would be easily 
and correctly readable (and printable) with the full range of OS's 
out there.  Yes, I am aware that the I-D page offers a MS Word 
template, but it is still a multistep process that might be able to 
be simplified if the formating constraints were lower.  And yes I 
know that there are challenges due to the different line termination 
rules on different OSs.  So I admit that my two goals may not be 
achievable, but is there value in trying?

John Morris

-- 
----------------------------------------
John B. Morris, Jr.
Director, Internet Standards, Technology
    & Policy Project
Center for Democracy and Technology
1634 I Street NW, Suite 1100
Washington, DC 20006
(202) 637-9800
(202) 637-0968 fax
jmorris@cdt.org
http://www.cdt.org
----------------------------------------



From owner-ietf@ietf.org  Mon Apr 21 18:28:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06031;
	Mon, 21 Apr 2003 18:28:49 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197k3c-0001px-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 18:46:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197jrX-00089b-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 18:34:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05400
	for <ietf@ietf.org>; Mon, 21 Apr 2003 18:12:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197jYw-0003ta-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:14:58 -0400
Received: from buffoon.automagic.org ([208.185.30.208] ident=qmailr)
	by ietf-mx with smtp (Exim 4.12)
	id 197jYv-0003tX-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:14:57 -0400
Received: (qmail 55348 invoked by uid 0); 21 Apr 2003 22:15:19 -0000
Received: from localhost.automagic.org (HELO isc.org) (root@127.0.0.1)
  by localhost.automagic.org with SMTP; 21 Apr 2003 22:15:19 -0000
Date: Mon, 21 Apr 2003 18:15:39 -0400
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Ross Finlayson <finlayson@live.com>
From: Joe Abley <jabley@isc.org>
In-Reply-To: <4.3.1.1.20030421143850.00b7b340@laptop-localhost>
Message-Id: <C8A486ED-7446-11D7-A6E0-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Monday, Apr 21, 2003, at 17:42 Canada/Eastern, Ross Finlayson wrote:

> At 12:02 PM 4/21/03, Paul Hoffman / IMC wrote:
>>> Page breaks are highly desirable for I-Ds, because it makes it easier
>>> for people to print them out.
>>
>> Um, which software that takes a long text file *doesn't* put in page 
>> breaks as it sends it to the printer? This has been a standard part 
>> of nearly every word processing and text editing program for two 
>> decades now...
>
> Indeed.  Why continue this archaic mid-20th century nonsense?
>
> I, personally, will never waste a second of my own time inserting page 
> breaks in any I-D that I write.

Do people really mark up internet drafts by hand instead of using tools 
like nroff or Dr Rose's rfc2629 tools?

If so, why?

If not, why does this list contain a thread about page breaks?


Joe




From owner-ietf@ietf.org  Mon Apr 21 18:33:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06254;
	Mon, 21 Apr 2003 18:33:39 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197k3d-0001qs-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 18:46:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197jte-0000ZV-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 18:36:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05652
	for <ietf@ietf.org>; Mon, 21 Apr 2003 18:14:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197jb2-0003v1-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:17:08 -0400
Received: from darkwing.uoregon.edu ([128.223.142.13] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 197jb2-0003uw-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:17:08 -0400
Received: from twin.uoregon.edu (twin.uoregon.edu [128.223.214.27])
	by darkwing.uoregon.edu (8.12.9/8.12.9) with ESMTP id h3LMHS0o023164
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <ietf@ietf.org>; Mon, 21 Apr 2003 15:17:28 -0700 (PDT)
Date: Mon, 21 Apr 2003 15:14:01 -0700 (PDT)
From: Joel Jaeggli <joelja@darkwing.uoregon.edu>
X-X-Sender: joelja@twin.uoregon.edu
To: ietf@ietf.org
Subject: Availability of recorded IETF 56 sessions...
Message-ID: <Pine.LNX.4.44.0304211511110.4641-100000@twin.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

I am pleased to announce the availability of the meetings recorded during
the week of IETF56. They are available at:

http://videolab.uoregon.edu/events/ietf/ietf56.html#archive

or

ftp://limestone.uoregon.edu/pub/videolab/video/ietf56

-- 
-------------------------------------------------------------------------- 
Joel Jaeggli	      Academic User Services   joelja@darkwing.uoregon.edu    
--    PGP Key Fingerprint: 1DE9 8FCA 51FB 4195 B42A 9C32 A30D 121E      --
  In Dr. Johnson's famous dictionary patriotism is defined as the last
  resort of the scoundrel.  With all due respect to an enlightened but
  inferior lexicographer I beg to submit that it is the first.
	   	            -- Ambrose Bierce, "The Devil's Dictionary"





From owner-ietf@ietf.org  Mon Apr 21 18:46:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06601;
	Mon, 21 Apr 2003 18:46:21 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197kL3-0003K1-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 19:04:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197kIx-00038J-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 19:02:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06542
	for <ietf@ietf.org>; Mon, 21 Apr 2003 18:40:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197k0L-00048l-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:43:17 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 197k0K-00048i-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:43:17 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h3LMhbo24098;
	Mon, 21 Apr 2003 15:43:37 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200304212243.h3LMhbo24098@boreas.isi.edu>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
In-Reply-To: <C8A486ED-7446-11D7-A6E0-00039312C852@isc.org> from Joe Abley at "Apr 21, 3 06:15:39 pm"
To: jabley@isc.org (Joe Abley)
Date: Mon, 21 Apr 2003 15:43:37 -0700 (PDT)
Cc: ietf@ietf.org, finlayson@live.com
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
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, personally, will never waste a second of my own time inserting page 
% > breaks in any I-D that I write.
% 
% Do people really mark up internet drafts by hand instead of using tools 
% like nroff or Dr Rose's rfc2629 tools?
% 
% If so, why?
% If not, why does this list contain a thread about page breaks?
% 
% Joe

	Most of the IDs that I have ever written have no page breaks.
	They are short enough that page breaks are superfluous and most
	were written before massive inclusion of CYA-boilerplate was 
	required.

	With CYA-boilerplate and novel-sized IDs, (the OSPF drafts were
	notorious) page breaks are useful.

	I expect that any new IDs that I write will be hand crafted.


--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).



From owner-ietf@ietf.org  Mon Apr 21 18:46:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06631;
	Mon, 21 Apr 2003 18:46:24 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197kKE-0003Cl-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 19:03:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197kH2-00037r-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 19:00:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06474
	for <ietf@ietf.org>; Mon, 21 Apr 2003 18:38:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197jyR-00047h-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:41:19 -0400
Received: from mail.proper.com ([208.184.76.45] helo=above.proper.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 197jyQ-00047e-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:41:18 -0400
Received: from [63.202.92.152] (adsl-66-125-125-92.dsl.pltn13.pacbell.net [66.125.125.92])
	by above.proper.com (8.12.8p1/8.12.8) with ESMTP id h3LMfbt3063959;
	Mon, 21 Apr 2003 15:41:37 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05210634baca23ee292c@[63.202.92.152]>
In-Reply-To: <C8A486ED-7446-11D7-A6E0-00039312C852@isc.org>
References: <C8A486ED-7446-11D7-A6E0-00039312C852@isc.org>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Mon, 21 Apr 2003 15:41:34 -0700
To: Joe Abley <jabley@isc.org>, Ross Finlayson <finlayson@live.com>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 6:15 PM -0400 4/21/03, Joe Abley wrote:
>Do people really mark up internet drafts by hand instead of using 
>tools like nroff or Dr Rose's rfc2629 tools?

You forgot the third choice: no markup. Just use a text editor that 
can create paragraphs easily. There are many on most platforms.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Mon Apr 21 18:47:05 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06726;
	Mon, 21 Apr 2003 18:47:05 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197kL4-0003K7-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 19:04:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197kJb-00038e-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 19:03:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06560
	for <ietf@ietf.org>; Mon, 21 Apr 2003 18:41:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197k0z-000498-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:43:57 -0400
Received: from buffoon.automagic.org ([208.185.30.208] ident=qmailr)
	by ietf-mx with smtp (Exim 4.12)
	id 197k0z-000495-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:43:57 -0400
Received: (qmail 57312 invoked by uid 0); 21 Apr 2003 22:44:19 -0000
Received: from localhost.automagic.org (HELO isc.org) (root@127.0.0.1)
  by localhost.automagic.org with SMTP; 21 Apr 2003 22:44:19 -0000
Date: Mon, 21 Apr 2003 18:44:39 -0400
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Ross Finlayson <finlayson@live.com>, ietf@ietf.org
To: Paul Hoffman / IMC <phoffman@imc.org>
From: Joe Abley <jabley@isc.org>
In-Reply-To: <p05210634baca23ee292c@[63.202.92.152]>
Message-Id: <D60B42F4-744A-11D7-A6E0-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Monday, Apr 21, 2003, at 18:41 Canada/Eastern, Paul Hoffman / IMC 
wrote:

> At 6:15 PM -0400 4/21/03, Joe Abley wrote:
>> Do people really mark up internet drafts by hand instead of using 
>> tools like nroff or Dr Rose's rfc2629 tools?
>
> You forgot the third choice: no markup. Just use a text editor that 
> can create paragraphs easily. There are many on most platforms.

Actually I didn't forget the third choice; I just should have said 
"generate" instead of "mark up".

So, if you generate I-Ds by hand, why do you do that? Surely it's more 
hassle than just formatting paragraphs (section numbers, 
cross-references, tables of contents, pagination, etc).


Joe




From owner-ietf@ietf.org  Mon Apr 21 18:48:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06933;
	Mon, 21 Apr 2003 18:48:09 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197kL4-0003KD-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 19:04:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197kK4-00038l-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 19:03:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06564
	for <ietf@ietf.org>; Mon, 21 Apr 2003 18:42:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197k1S-00049F-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:44:26 -0400
Received: from zydeco.netbusters.com ([66.92.86.178])
	by ietf-mx with esmtp (Exim 4.12)
	id 197k1S-00049C-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:44:26 -0400
Received: by zydeco.netbusters.com (Postfix, from userid 513)
	id 71E76B63B1; Mon, 21 Apr 2003 22:44:48 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by zydeco.netbusters.com (Postfix) with ESMTP id 708327EC1D
	for <ietf@ietf.org>; Mon, 21 Apr 2003 18:44:48 -0400 (EDT)
Date: Mon, 21 Apr 2003 18:44:48 -0400 (EDT)
From: Donald Eastlake 3rd <dee3@torque.pothole.com>
X-X-Sender: dee3@zydeco.netbusters.com
To: ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
In-Reply-To: <C8A486ED-7446-11D7-A6E0-00039312C852@isc.org>
Message-ID: <Pine.LNX.4.44.0304211841080.18496-100000@zydeco.netbusters.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Most versions of nroff do not make it particularly easy to insert form
feeds but its trivial to do with a step of post-processing. I use nroff
and submit all my IDs with FFs.

Thanks,
Donald
======================================================================
 Donald E. Eastlake 3rd                       dee3@torque.pothole.com
 155 Beaver Street              +1-508-634-2066(h) +1-508-851-8280(w)
 Milford, MA 01757 USA                   Donald.Eastlake@motorola.com

On Mon, 21 Apr 2003, Joe Abley wrote:

> Date: Mon, 21 Apr 2003 18:15:39 -0400
> From: Joe Abley <jabley@isc.org>
> To: Ross Finlayson <finlayson@live.com>
> Cc: ietf@ietf.org
> Subject: Re: Internet Draft Guidelines Require Precise Formatting?
> 
> On Monday, Apr 21, 2003, at 17:42 Canada/Eastern, Ross Finlayson wrote:
> 
> > At 12:02 PM 4/21/03, Paul Hoffman / IMC wrote:
> >>> Page breaks are highly desirable for I-Ds, because it makes it easier
> >>> for people to print them out.
> >>
> >> Um, which software that takes a long text file *doesn't* put in page 
> >> breaks as it sends it to the printer? This has been a standard part 
> >> of nearly every word processing and text editing program for two 
> >> decades now...
> >
> > Indeed.  Why continue this archaic mid-20th century nonsense?
> >
> > I, personally, will never waste a second of my own time inserting page 
> > breaks in any I-D that I write.
> 
> Do people really mark up internet drafts by hand instead of using tools 
> like nroff or Dr Rose's rfc2629 tools?
> 
> If so, why?
> 
> If not, why does this list contain a thread about page breaks?
> 
> 
> Joe
> 
> 
> 




From owner-ietf@ietf.org  Mon Apr 21 19:02:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07617;
	Mon, 21 Apr 2003 19:02:43 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197kZN-0005un-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 19:19:29 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197kVM-0005lR-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 19:15:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07277
	for <ietf@ietf.org>; Mon, 21 Apr 2003 18:53:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197kCl-0004Ln-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:56:07 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 197kCk-0004Lk-00
	for ietf@ietf.org; Mon, 21 Apr 2003 18:56:06 -0400
Received: from BBFUJIP (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h3LMu8118059;
	Mon, 21 Apr 2003 15:56:08 -0700
Date: Mon, 21 Apr 2003 15:57:13 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/4) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <102021636.20030421155713@brandenburg.com>
To: John Morris <jmorris@cdt.org>
CC: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>,
        ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
In-Reply-To: <a05200f0abaca130b6bba@[10\.0\.1\.12]>
References: <Pine.LNX.4.10.10304211513330.12064-100000@spitfire.law.miami.edu>
 <a05200f0abaca130b6bba@[10.0.1.12]>
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

John,

JM>    Although it may seem silly to
JM> some (and some of you may not want to hear from them anyway), the 
JM> IETF's formatting rules do present a (relatively small) hurdle to 
JM> public policy advocates and other outsiders.

well, this is an unexpected benefit of our formatting rules...

the IETF is a technical body, not a place for public policy debates.

and to the extent you want to pursue the matter seriously, there are
at least two critical items to remembers:

1.  The format requirements are easy to satisfy, with support for MS
Word and XML-based documents readily available;

2.  Technical standards bodies typically have some sort of format
standard. Within my limited experience, the IETF requirements are
easily the easiest.

d/
JM> I personally think that there is value in allowing those less


d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Mon Apr 21 19:46:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08528;
	Mon, 21 Apr 2003 19:46:30 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197lFB-0000Yo-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 20:02:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197lCZ-0000G5-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 19:59:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08436
	for <ietf@ietf.org>; Mon, 21 Apr 2003 19:38:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197ktx-0004hA-00
	for ietf@ietf.org; Mon, 21 Apr 2003 19:40:45 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 197ktw-0004h7-00
	for ietf@ietf.org; Mon, 21 Apr 2003 19:40:44 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h3LNf5sj001409
	for ietf@ietf.org env-from <vjs>;
	Mon, 21 Apr 2003 17:41:05 -0600 (MDT)
Date: Mon, 21 Apr 2003 17:41:05 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200304212341.h3LNf5sj001409@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
References: <a05200f0abaca130b6bba@[10.0.1.12]>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: John Morris <jmorris@cdt.org>

>               ...  But it is also true that the formatting 
> requirements for I-Ds are one of many obstacles to "outside" 
> participation in the IETFprocess.  ...

I cannot imagine how a reasonable person who subscribes to the IETF
announce mailing list or who maintains a private library of RFCs and
so has the faintest idea about what the IETF has been producing for
the last 10 years would fewer instead of more obstacles to "outside"
participation in The IETF Process.

Never mind that in ANSI committees I learned to beware of managers,
sales people, and other committee go-ers bearing gifts whenever I
heard a phrase like "The Standards Process."


> Director, Internet Standards, Technology
>     & Policy Project
> Center for Democracy and Technology

What does democracy have to do with technical standards or other
information in general and the IETF in particular?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Mon Apr 21 19:50:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08701;
	Mon, 21 Apr 2003 19:50:22 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197lK1-0001An-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 20:07:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197lJO-000171-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 20:07:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08504
	for <ietf@ietf.org>; Mon, 21 Apr 2003 19:45:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197l0m-0004ic-00
	for ietf@ietf.org; Mon, 21 Apr 2003 19:47:48 -0400
Received: from mail.cdt.org ([206.112.85.61])
	by ietf-mx with esmtp (Exim 4.12)
	id 197l0m-0004iT-00
	for ietf@ietf.org; Mon, 21 Apr 2003 19:47:48 -0400
Received: from [10.0.1.12] (66.safeclick.net [63.119.245.66])
	by mail.cdt.org (Postfix) with ESMTP
	id 2FCF14900FC; Mon, 21 Apr 2003 19:34:47 -0400 (EDT)
Mime-Version: 1.0
X-Sender: john@mail.cdt.org
Message-Id: <a05200f0bbaca2c244da1@[10.0.1.12]>
In-Reply-To: <102021636.20030421155713@brandenburg.com>
References: 
 <Pine.LNX.4.10.10304211513330.12064-100000@spitfire.law.miami.edu>
 <a05200f0abaca130b6bba@[10.0.1.12]>
 <102021636.20030421155713@brandenburg.com>
Date: Mon, 21 Apr 2003 19:47:34 -0400
To: Dave Crocker <dcrocker@brandenburg.com>
From: John Morris <jmorris@cdt.org>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
Cc: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>,
        ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

Dave,

At 3:57 PM -0700 4/21/03, Dave Crocker wrote:
>John,
>
>JM>    Although it may seem silly to
>JM> some (and some of you may not want to hear from them anyway), the
>JM> IETF's formatting rules do present a (relatively small) hurdle to
>JM> public policy advocates and other outsiders.
>
>well, this is an unexpected benefit of our formatting rules...
>
>the IETF is a technical body, not a place for public policy debates.

Not to start an extended debate (especially in a thread on 
formatting), but as much as the IETF would like to avoid public 
policy debates (for good reasons that I appreciate), there are times 
when _technical_ decisions have significant impact on public policy 
concerns.  I believe that neither the IETF nor the public are well 
served by ignoring (or being unaware of) those potential impacts. 
Thus, I think that there are times where public policy input into the 
IETF is a healthy, constructive thing, especially if the input is 
provided in a constructive matter (and yes, in a widely readable 
format).   To promote constructive, non-time-wasting input, I've 
encouraged policy advocates to (a) learn about the procedures, 
structure, and culture of the IETF before participating, (b) read and 
review the relevant lists before participating, and (c) use the modes 
of communication accepted by the community for their input.  It is on 
this last point that I-D formatting is relevant.

>and to the extent you want to pursue the matter seriously, there are
>at least two critical items to remembers:
>
>1.  The format requirements are easy to satisfy, with support for MS
>Word and XML-based documents readily available;

Can the requirements be satisfied using MS Word and the multistep 
production/post-processing procedures?   Absolutely.  There is even 
evidence that some lawyers can do it.  But it is not "easy" to 
non-techies who seldom work within the standards world.  And although 
XML and Marshall's utility are great (separately and together), that 
is way beyond what can reasonably be asked of a non-techie today.

I appreciate that the IETF is set in its ways (and more often than 
not I appreciate those ways).  A pitched battle to change the 
formatting requirements is not one that I personally feel the need to 
wage right now.  But if on the other hand there is any broader 
recognizition by the community that thoughtful and constructive 
outside input can sometimes be valuable, then I would be happy to 
participate in an effort to facilitate such input, or at least reduce 
non-critical barriers to such input.

John



From owner-ietf@ietf.org  Mon Apr 21 20:15:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09302;
	Mon, 21 Apr 2003 20:15:10 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197laU-0002Tt-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 20:24:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197lZ4-0002LL-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 20:23:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09070
	for <ietf@ietf.org>; Mon, 21 Apr 2003 20:01:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197lGR-0004rX-00
	for ietf@ietf.org; Mon, 21 Apr 2003 20:03:59 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 197lGR-0004rU-00
	for ietf@ietf.org; Mon, 21 Apr 2003 20:03:59 -0400
Received: from BBFUJIP (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h3M041120726;
	Mon, 21 Apr 2003 17:04:01 -0700
Date: Mon, 21 Apr 2003 17:05:32 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/4) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <1666120140.20030421170532@brandenburg.com>
To: John Morris <jmorris@cdt.org>
CC: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>,
        ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
In-Reply-To: <a05200f0bbaca2c244da1@[10\.0\.1\.12]>
References: <Pine.LNX.4.10.10304211513330.12064-100000@spitfire.law.miami.edu>
 <a05200f0abaca130b6bba@[10.0.1.12]> <102021636.20030421155713@brandenburg.com>
 <a05200f0bbaca2c244da1@[10.0.1.12]>
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

JM>  there are times
JM> when _technical_ decisions have significant impact on public policy
JM> concerns.  I believe that neither the IETF nor the public are well
JM> served by ignoring (or being unaware of) those potential impacts.

1.  it is hard to imagine that the minimal formatting requirements in
force for ietf documents pose a meaningful barrier to serious input of
any kind.

2.  whether, and when, the ietf should participate in public policy
debates is, itself, a matter of debate.  possibly even a worthy one.


JM> Can the requirements be satisfied using MS Word and the multistep
JM> production/post-processing procedures?   Absolutely.  There is even
JM> evidence that some lawyers can do it.  But it is not "easy" to 
JM> non-techies who seldom work within the standards world.

1. c.f., your statement above about acquiring some of the appearance of a
natural inhabitant, to blend into the environment.

2. anyone who thinks the ietf formatting requirements are not easy has
not had to deal with very interesting formatting requirements.


d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Mon Apr 21 20:18:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09527;
	Mon, 21 Apr 2003 20:18:31 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197llG-00039L-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 20:35:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197ldx-0002qL-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 20:28:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09120
	for <ietf@ietf.org>; Mon, 21 Apr 2003 20:06:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197lLL-0004sV-00
	for ietf@ietf.org; Mon, 21 Apr 2003 20:09:03 -0400
Received: from spitfire.law.miami.edu ([129.171.187.10] ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 197lLK-0004sS-00
	for ietf@ietf.org; Mon, 21 Apr 2003 20:09:03 -0400
Received: from spitfire.law.miami.edu (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id 31BE25C3AC6; Mon, 21 Apr 2003 20:09:25 -0400 (EDT)
Received: by spitfire.law.miami.edu (Postfix, from userid 1113)
	id 80E135C3AD2; Mon, 21 Apr 2003 20:09:24 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by spitfire.law.miami.edu (Postfix) with ESMTP
	id 721F85D3D0D; Mon, 21 Apr 2003 20:09:24 -0400 (EDT)
Date: Mon, 21 Apr 2003 20:09:24 -0400 (EDT)
From: "Michael Froomkin - U.Miami School of Law" <froomkin@law.miami.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
In-Reply-To: <200304212341.h3LNf5sj001409@calcite.rhyolite.com>
Message-ID: <Pine.LNX.4.10.10304212008450.12064-100000@spitfire.law.miami.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 21 Apr 2003, Vernon Schryver wrote:
> 
> What does democracy have to do with technical standards or other
> information in general and the IETF in particular?

http://www.law.miami.edu/~froomkin/discourse/ils.pdf

;>

-- 
		Please visit http://www.icannwatch.org
A. Michael Froomkin   |    Professor of Law    |   froomkin@law.tm
U. Miami School of Law, P.O. Box 248087, Coral Gables, FL 33124 USA
+1 (305) 284-4285  |  +1 (305) 284-6506 (fax)  |  http://www.law.tm
                        -->It's warm here.<--




From owner-ietf@ietf.org  Mon Apr 21 20:35:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10116;
	Mon, 21 Apr 2003 20:35:53 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197m1Z-0004mI-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 20:52:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197lv9-0004WB-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 20:46:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09850
	for <ietf@ietf.org>; Mon, 21 Apr 2003 20:24:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197lcX-00053N-00
	for ietf@ietf.org; Mon, 21 Apr 2003 20:26:49 -0400
Received: from h-135-207-24-16.research.att.com ([135.207.24.16] helo=linux.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 197lcW-000537-00
	for ietf@ietf.org; Mon, 21 Apr 2003 20:26:49 -0400
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by linux.research.att.com (8.12.8/8.12.8) with ESMTP id h3M0QlCN027085;
	Mon, 21 Apr 2003 20:26:47 -0400
Received: from berkshire.research.att.com (guard.research.att.com [135.207.1.20])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h3M0QbV05325;
	Mon, 21 Apr 2003 20:26:37 -0400 (EDT)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id 4326A7B4D; Mon, 21 Apr 2003 20:26:37 -0400 (EDT)
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting? 
In-Reply-To: Your message of "Mon, 21 Apr 2003 17:41:05 MDT."
             <200304212341.h3LNf5sj001409@calcite.rhyolite.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 21 Apr 2003 20:26:37 -0400
Message-Id: <20030422002637.4326A7B4D@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <200304212341.h3LNf5sj001409@calcite.rhyolite.com>, Vernon Schryver 
writes:

>
>> Director, Internet Standards, Technology
>>     & Policy Project
>> Center for Democracy and Technology
>
>What does democracy have to do with technical standards or other
>information in general and the IETF in particular?
>

Among the many public policy issues that the IETF has been involved
in -- i.e., that affect out "technical" standards -- are privacy,
wiretapping, crypto export, and IPR.  We won't even go into the
whole ICANN space.  (John Morris, to whom that comment was addressed, 
is an author of at least three WG drafts.  I, for one, am glad to have 
him around the IETF.)

		--Steve Bellovin, http://www.research.att.com/~smb (me)
		http://www.wilyhacker.com (2nd edition of "Firewalls" book)





From owner-ietf@ietf.org  Mon Apr 21 20:40:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10338;
	Mon, 21 Apr 2003 20:40:19 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197m7J-0005pC-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 20:58:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197m6G-0005SP-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 20:57:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10129
	for <ietf@ietf.org>; Mon, 21 Apr 2003 20:35:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197lnd-00057D-00
	for ietf@ietf.org; Mon, 21 Apr 2003 20:38:17 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 197lnc-000578-00
	for ietf@ietf.org; Mon, 21 Apr 2003 20:38:17 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 197lny-000BfB-00; Mon, 21 Apr 2003 19:38:38 -0500
Date: Mon, 21 Apr 2003 20:38:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joe Abley <jabley@isc.org>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Internet Draft Guidelines Require Precise
 Formatting?
Message-ID: <118159053.1050957518@p3.JCK.COM>
In-Reply-To: <D60B42F4-744A-11D7-A6E0-00039312C852@isc.org>
References:  <D60B42F4-744A-11D7-A6E0-00039312C852@isc.org>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Monday, 21 April, 2003 18:44 -0400 Joe Abley 
<jabley@isc.org> wrote:

> On Monday, Apr 21, 2003, at 18:41 Canada/Eastern, Paul Hoffman
> / IMC wrote:
>
>> At 6:15 PM -0400 4/21/03, Joe Abley wrote:
>>> Do people really mark up internet drafts by hand instead of
>>> using  tools like nroff or Dr Rose's rfc2629 tools?
>>
>> You forgot the third choice: no markup. Just use a text
>> editor that  can create paragraphs easily. There are many on
>> most platforms.
>
> Actually I didn't forget the third choice; I just should have
> said "generate" instead of "mark up".
>
> So, if you generate I-Ds by hand, why do you do that? Surely
> it's more hassle than just formatting paragraphs (section
> numbers, cross-references, tables of contents, pagination,
> etc).

Actually, no, it is not more hassle.   I've been using straight 
emacs and its clones as my main I-D production/generation tool 
for years.  Paragraphs are easy, pasting in boilerplate is easy, 
indention is easy, keeping track of section numbers and 
references is a major (but necessary) annoyance, but pagination 
(and per-page headers and footers are a significant annoyance 
that involve little payoff.  And there are huge advantages to 
editing on exactly the document form the WG is looking at, 
rather than having to transpose comments into some other 
formatting setup that then generates the I-D format.

I've also tried using the MS Word tools with complex documents 
where I wanted to do extensive change-tracking and annotation. 
MS Word (especially Word XP) is very good at that, but getting 
heavily-annotated, cross-referenced, and precisely formatted 
documents from Word format into RFC (or I-D) format using RFC 
3285 and its template setups is, well, a learning experience... 
and not one that I can recommend to others.

       john







From owner-ietf@ietf.org  Mon Apr 21 21:37:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11486;
	Mon, 21 Apr 2003 21:37:44 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197mxc-0000yj-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 21:52:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197mwv-0000v5-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 21:51:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11350
	for <ietf@ietf.org>; Mon, 21 Apr 2003 21:30:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197meH-0005S3-00
	for ietf@ietf.org; Mon, 21 Apr 2003 21:32:41 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 197meG-0005Rx-00
	for ietf@ietf.org; Mon, 21 Apr 2003 21:32:41 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.9/8.12.9) id h3M1X19L021368
	for ietf@ietf.org env-from <vjs>;
	Mon, 21 Apr 2003 19:33:01 -0600 (MDT)
Date: Mon, 21 Apr 2003 19:33:01 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200304220133.h3M1X19L021368@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
References: <20030422002637.4326A7B4D@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "Steven M. Bellovin" <smb@research.att.com>

> >> Director, Internet Standards, Technology
> >>     & Policy Project
> >> Center for Democracy and Technology
> >
> >What does democracy have to do with technical standards or other
> >information in general and the IETF in particular?
>
> Among the many public policy issues that the IETF has been involved
> in -- i.e., that affect out "technical" standards -- are privacy,
> wiretapping, crypto export, and IPR.  We won't even go into the
> whole ICANN space.  (John Morris, to whom that comment was addressed, 
> is an author of at least three WG drafts.  I, for one, am glad to have 
> him around the IETF.)

There is a very short and slick slope from due consideration for
non-technical aspects of technical standards to voting on the value
of pi.  Removing barriers to participation by "outsiders" would only
bring more contributions like
ftp://ftp.isi.edu/internet-drafts/draft-terrell-math-quant-new-para-redefi-bin-math-04.txt
without significantly helping people with something to say.

What the special interests, the mob and the kooks say they think is
not the most important consideration even when evaluating non-technical
ideas.  Dr. David Sternlight and Jim Flemming are the canonical "policy
analysts" for computers and the Internet.  That certainly doesn't mean
that non-technical issues are less important.  As you say, privacy
and other issues are more important than most protocol details.
However, it does mean that I'm very glad that most people who style
themselves as "policy analysts" and say they support "democratic values
in technology" are miles away from me.

As for ICANN...I thought you meant to disagree with me.


Vernon Schryver    vjs@rhyolite.com




From owner-ietf@ietf.org  Mon Apr 21 22:32:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12358;
	Mon, 21 Apr 2003 22:32:37 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197nqn-0004J1-00
	for ietf-list@ran.ietf.org; Mon, 21 Apr 2003 22:49:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197nm3-0004Ef-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 22:44:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12210
	for <ietf@ietf.org>; Mon, 21 Apr 2003 22:23:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197nTP-0005dt-00
	for ietf@ietf.org; Mon, 21 Apr 2003 22:25:31 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 197nTO-0005dq-00
	for ietf@ietf.org; Mon, 21 Apr 2003 22:25:30 -0400
Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h3M2PLgE011484
	for <ietf@ietf.org>; Mon, 21 Apr 2003 19:25:21 -0700 (PDT)
Received: from cisco.com (sjc-vpn1-834.cisco.com [10.21.99.66])
	by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with SMTP id AFP43682;
	Mon, 21 Apr 2003 19:17:10 -0700 (PDT)
Received: by cisco.com (sSMTP sendmail emulation); Mon, 21 Apr 2003 22:21:47 -0400
Date: Mon, 21 Apr 2003 22:21:47 -0400
From: Scott W Brim <swb@employees.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
Message-ID: <20030422022146.GW1612@sbrim-w2k>
Mail-Followup-To: Scott W Brim <swb@employees.org>,
	"ietf@ietf.org" <ietf@ietf.org>
References: <D60B42F4-744A-11D7-A6E0-00039312C852@isc.org> <118159053.1050957518@p3.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <118159053.1050957518@p3.JCK.COM>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Apr 21, 2003 08:38:38PM -0400, John C Klensin allegedly wrote:
> Actually, no, it is not more hassle.   I've been using straight 
> emacs and its clones as my main I-D production/generation tool 
> for years.  Paragraphs are easy, pasting in boilerplate is easy, 
> indention is easy, keeping track of section numbers and 
> references is a major (but necessary) annoyance, but pagination 
> (and per-page headers and footers are a significant annoyance 
> that involve little payoff.  And there are huge advantages to 
> editing on exactly the document form the WG is looking at, 
> rather than having to transpose comments into some other 
> formatting setup that then generates the I-D format.

I also get nothing out of ^Ls in our documents, or headers and footers.
I wouldn't mind seeing them go.  However, section numbers are critically
important, and I think getting them wrong is the main danger of doing it
all by hand.



From owner-ietf@ietf.org  Tue Apr 22 00:36:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14530;
	Tue, 22 Apr 2003 00:36:32 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197pk3-0002kB-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 00:50:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197pic-0002XL-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 00:49:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14394
	for <ietf@ietf.org>; Tue, 22 Apr 2003 00:27:44 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197pPx-0006BO-00
	for ietf@ietf.org; Tue, 22 Apr 2003 00:30:05 -0400
Received: from h80ad269c.async.vt.edu ([128.173.38.156] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 197pPv-0006BK-00
	for ietf@ietf.org; Tue, 22 Apr 2003 00:30:04 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h3M4UGTh002191;
	Tue, 22 Apr 2003 00:30:16 -0400
Message-Id: <200304220430.h3M4UGTh002191@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: John Morris <jmorris@cdt.org>
Cc: ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting? 
In-Reply-To: Your message of "Mon, 21 Apr 2003 18:11:28 EDT."
             <a05200f0abaca130b6bba@[10.0.1.12]> 
References: <Pine.LNX.4.10.10304211513330.12064-100000@spitfire.law.miami.edu>
            <a05200f0abaca130b6bba@[10.0.1.12]>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1865662912P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 22 Apr 2003 00:30:16 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1865662912P
Content-Type: text/plain; charset=us-ascii

On Mon, 21 Apr 2003 18:11:28 EDT, John Morris said:
> So basically the lenient format could be used to raise initial ideas 
> and express initial input to the IETF community.  Any document that 

I will posit that this list is the proper venue for that.  In fact,
inability to convince *anybody* with the technical ability to do an I-D
is probably indicative of either crankhood or such poor communication
skills that formatting is the *least* of your worries (and a good engineer
may not even bother to distinguish those two cases...)

Write it up, post it... the IETF list is so culturally biased against
dropping good ideas on the floor without discussion  that we can even chase
patently bad ideas around in circles (witness the extended debate on this
thread ;)

/Valdis


--==_Exmh_-1865662912P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+pMVYcC3lWbTT17ARAictAKCJZVRk2sg5BnxyNtpI1syEZxl6hACgrPHL
VCBQHWvPDMeGY8TZ8Gg2FuQ=
=GErn
-----END PGP SIGNATURE-----

--==_Exmh_-1865662912P--



From owner-ietf@ietf.org  Tue Apr 22 03:46:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29170;
	Tue, 22 Apr 2003 03:46:03 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197ser-0001JM-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 03:57:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197sdN-0001D9-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 03:56:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29031
	for <ietf@ietf.org>; Tue, 22 Apr 2003 03:34:26 -0400 (EDT)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197sKe-00079C-00
	for ietf@ietf.org; Tue, 22 Apr 2003 03:36:49 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 197sKd-000799-00
	for ietf@ietf.org; Tue, 22 Apr 2003 03:36:48 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h3M7b7718122
	for <ietf@ietf.org>; Tue, 22 Apr 2003 10:37:07 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T61c15b7e38ac158f21083@esvir01nok.ntc.nokia.com>;
 Tue, 22 Apr 2003 10:37:06 +0300
Received: from esebe004.NOE.Nokia.com ([172.21.138.44]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 22 Apr 2003 10:37:05 +0300
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebe004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 22 Apr 2003 10:37:05 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: A simple question
Date: Tue, 22 Apr 2003 10:36:55 +0300
Message-ID: <DADF50F5EC506B41A0F375ABEB3206360C1EF0@esebe023.ntc.nokia.com>
Thread-Topic: A simple question
Thread-Index: AcMIPAuwi+fj+x7kQP2Cd4Whg5g6YAAZDACw
To: <moore@cs.utk.edu>
Cc: <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 22 Apr 2003 07:37:05.0038 (UTC) FILETIME=[F89E32E0:01C308A1]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id DAA29170

Hi Keith,

One comment:

> > Usage alters to meet the demands of the users.  That's nothing new.
> > 
> >   | on the contrary, having an enterprise use both SLs and globals creates
> >   | significant new problems of its own, and results in even less
> >   | flexibility than if SLs were used only by isolated networks.
> > 
> > Nothing that IPv4 doesn't have as well (if perhaps less commonly).
> 
> there's a reason that most v4 hosts don't have multiple addresses with varying
> scopes - it doesn't work well, and it creates problems for apps.  putting
> sitelocals in v6 is trying to impose those problems on all host.

I'd suggest that there has not been much of demand for this kind of
functionality. Most hosts have had only a single interface, so there is
not a lot of reason to give a single interface multiple addresses.

Already we are seeing laptops with multiple interfaces (Ethernet, WLAN,
Bluetooth, etc.) - I think it is only a matter of time that applications
start to take advantage of this.  

One use case for this kind of functionality would be a cell phone that
has some sort of expensive cellular data connnection but also has WLAN / 
Bluetooth interfaces. In a WLAN hotspot, data could/should go over that
interface as opposed to the cellular interface.  However, the cellular
interface might be used to provide WAN coverage ...

A lot of this is OS / implementation specific stuff, but I don't understand
why this should not be supported in standards.

br,
John



From owner-ietf@ietf.org  Tue Apr 22 05:13:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00911;
	Tue, 22 Apr 2003 05:13:38 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197u4x-0006Y8-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 05:28:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197u44-0006VB-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 05:27:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00828
	for <ietf@ietf.org>; Tue, 22 Apr 2003 05:06:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197tlL-0007W5-00
	for ietf@ietf.org; Tue, 22 Apr 2003 05:08:27 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 197tlL-0007W2-00
	for ietf@ietf.org; Tue, 22 Apr 2003 05:08:27 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3M98gL05137;
	Tue, 22 Apr 2003 04:08:42 -0500
Message-ID: <023c01c308ae$c6252280$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <john.loughney@nokia.com>, <moore@cs.utk.edu>
Cc: <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
References: <DADF50F5EC506B41A0F375ABEB3206360C1EF0@esebe023.ntc.nokia.com>
Subject: Re: A simple question
Date: Tue, 22 Apr 2003 04:08:35 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake <john.loughney@nokia.com>
> Already we are seeing laptops with multiple interfaces (Ethernet,
> WLAN, Bluetooth, etc.) - I think it is only a matter of time that
> applications start to take advantage of this.

I see it as a failure of the network layer if applications need to
distinguish between multiple interfaces or address scopes.

While many don't see the distinction, this is the kind of stuff that
desperately needs to be in the OS/stack -- if anywhere.  Applications should
not know about network-level details unless they have a specific reason to
care, and if anything more than a small majority of applications care, there
is something wrong with our model.

Most applications today cannot even handle the case of multiple A records
for a destination host; do we really expect _tens of thousands_ of
applications to be updated with source-address-picking intelligence?

> A lot of this is OS / implementation specific stuff, but I don't
understand
> why this should not be supported in standards.

The approach to other problems, such as QOS, is to provide a common
architecture and terminology, then let the individual vendors provide their
own (often creative) solutions within those confines.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Tue Apr 22 06:58:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02217;
	Tue, 22 Apr 2003 06:58:40 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197viW-0003Cx-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 07:13:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197vfm-00037k-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 07:10:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02121
	for <ietf@ietf.org>; Tue, 22 Apr 2003 06:49:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197vN2-00002W-00
	for ietf@ietf.org; Tue, 22 Apr 2003 06:51:28 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197vN1-00002E-00
	for ietf@ietf.org; Tue, 22 Apr 2003 06:51:28 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h3MAokv07736;
	Tue, 22 Apr 2003 13:50:46 +0300
Date: Tue, 22 Apr 2003 13:50:45 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Bill Manning <bmanning@ISI.EDU>
cc: john heasley <heas@shrubbery.net>, <jabley@isc.org>, <moore@cs.utk.edu>,
        <kre@munnari.OZ.AU>, <Valdis.Kletnieks@vt.edu>,
        <dcrocker@brandenburg.com>, <ipng@sunroof.eng.sun.com>,
        <ietf@ietf.org>, <ot@cisco.com>
Subject: Re: A simple question
In-Reply-To: <200304200425.h3K4Pxw19463@boreas.isi.edu>
Message-ID: <Pine.LNX.4.44.0304221348370.5286-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 19 Apr 2003, Bill Manning wrote:
[...]
> 	we now have special blocks of IPv6 space that are not
> 	supposed to be aggregated for things like exchanges.
> 	massive aggregation is expected, except for these "special
> 	prefixes".  One more administrative thing to track. :(

Please stop this.  There is nothing of the kind.  The prefixes are not 
special.  They are not expected to be routable, so there are no additional 
administrative things to track.

Addressing for exchanges killed the need to using LL's with BGP, as simple 
as that.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From owner-ietf@ietf.org  Tue Apr 22 07:24:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02861;
	Tue, 22 Apr 2003 07:24:39 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197w9b-0004yb-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 07:41:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197w9R-0004vm-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 07:41:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02772
	for <ietf@ietf.org>; Tue, 22 Apr 2003 07:19:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197vqh-0000B0-00
	for ietf@ietf.org; Tue, 22 Apr 2003 07:22:07 -0400
Received: from mail15.speakeasy.net ([216.254.0.215] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 197vqg-0000Ax-00
	for ietf@ietf.org; Tue, 22 Apr 2003 07:22:06 -0400
Received: (qmail 25242 invoked from network); 22 Apr 2003 11:21:59 -0000
Received: from unknown (HELO Dave.invalid) ([66.92.168.196])
          (envelope-sender <davearonson@listen.to>)
          by mail15.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 22 Apr 2003 11:21:59 -0000
Content-Type: text/plain;
  charset="iso-8859-1"
From: Dave Aronson <dja2003@hotpop.com>
To: ietf@ietf.org
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
Date: Tue, 22 Apr 2003 07:23:35 -0400
X-Mailer: KMail [version 1.2]
References: <Pine.LNX.4.10.10304211513330.12064-100000@spitfire.law.miami.edu> <a05200f0abaca130b6bba@[10.0.1.12]>
In-Reply-To: <a05200f0abaca130b6bba@[10.0.1.12]>
MIME-Version: 1.0
Message-Id: <03042207233500.01177@Dave.invalid>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

On Monday 21 April 2003 18:11, John Morris wrote:

> I personally think that there is value in allowing those less
> familiar with the IETF an easier way to express their views in a
> standard format acceptable to the IETF.

The assorted mailing lists (this, and the WGs) can do for that.  You 
can't get much more "non-techie friendly" than email.

-- 
David J. Aronson, Software Engineer for hire in Washington DC area.
See http://destined.to/program/ for online resume, references, etc.



From owner-ietf@ietf.org  Tue Apr 22 08:38:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05990;
	Tue, 22 Apr 2003 08:38:03 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197xIP-00076s-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 08:54:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197xFw-0006tY-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 08:52:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05786
	for <ietf@ietf.org>; Tue, 22 Apr 2003 08:30:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197wxC-00013J-00
	for ietf@ietf.org; Tue, 22 Apr 2003 08:32:54 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 197wxB-000130-00
	for ietf@ietf.org; Tue, 22 Apr 2003 08:32:53 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 75CFD62571; Tue, 22 Apr 2003 14:32:46 +0200 (CEST)
Date: Tue, 22 Apr 2003 14:32:46 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: alh-ietf@tndh.net, ipng@sunroof.eng.sun.com
Cc: ietf@ietf.org
Subject: Re: A simple question
Message-ID: <438340000.1051014766@askvoll.hjemme.alvestrand.no>
In-Reply-To: <001a01c305f7$a902cd60$261e4104@eagleswings>
References:  <001a01c305f7$a902cd60$261e4104@eagleswings>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

just to provide a "simple" answer to a simple question:

NO - I do not agree with Keith's assertion as quoted.
YES - I agree with what I *believe* Keith wanted to say, which is that 
"introduction of *site-scoped* addresses causes far more problems than it 
solves".

I do NOT believe that introduction of link-local addresses causes far more 
problems than it solves.

My position on SL should be well known. I'll try to avoid repeating the 
rest of my arguments once again in this discussion tree.

                Harald


--On fredag, april 18, 2003 15:12:54 -0700 Tony Hain <alh-ietf@tndh.net> 
wrote:

> Keith Moore wrote:
>> It doesn't solve all problems, but introduction of
>> scoped addresses causes far more problems than it solves.
>
> I would like to understand how many people that voted YES on the
> question of deprecating SL concur with Keith's assertion.
>
> Tony
>
> Note: I cc'd the IETF list to catch those who may have been in the room
> in SF, but aren't on the IPv6 list.
>
>
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------
>





From owner-ietf@ietf.org  Tue Apr 22 08:59:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06995;
	Tue, 22 Apr 2003 08:59:37 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197xdi-0000WI-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 09:16:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1971fw-00024h-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 19:23:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08897
	for <ietf@ietf.org>; Sat, 19 Apr 2003 19:02:10 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1971Nq-0006y2-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:04:34 -0400
Received: from buffoon.automagic.org ([208.185.30.208] ident=qmailr)
	by ietf-mx with smtp (Exim 4.12)
	id 1971Nq-0006xz-00
	for ietf@ietf.org; Sat, 19 Apr 2003 19:04:34 -0400
Received: (qmail 71783 invoked by uid 0); 19 Apr 2003 23:04:52 -0000
Received: from localhost.automagic.org (HELO isc.org) (root@127.0.0.1)
  by localhost.automagic.org with SMTP; 19 Apr 2003 23:04:52 -0000
Date: Sat, 19 Apr 2003 19:05:10 -0400
Subject: Re: A simple question 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Valdis.Kletnieks@vt.edu, Dave Crocker <dcrocker@brandenburg.com>,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
To: Robert Elz <kre@munnari.OZ.AU>
From: Joe Abley <jabley@isc.org>
In-Reply-To: <16388.1050790957@munnari.OZ.AU>
Message-Id: <5EE9BDD1-72BB-11D7-A6E0-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Saturday, Apr 19, 2003, at 18:22 Canada/Eastern, Robert Elz wrote:

>     Date:        Sat, 19 Apr 2003 17:51:19 -0400
>     From:        Valdis.Kletnieks@vt.edu
>     Message-ID:  <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu>
>
>   | So if it's expected that both global and site-local addresses are 
> available,
>   | why are we bothering with making things more complicated?
>
> Because we need stable addresses for local use.
>
> Something tells me you've never actually lived in an environment where 
> your
> global address changes moderately frequently.   If you had, you 
> wouldn't
> be so quick to ignore this need.

The rhetoric would have us believe that frequent renumbering with IPv6 
is seamless and effortless. I don't personally buy that, but there are 
some assumptions there that perhaps should be challenged more directly 
rather than in this oblique fashion.

If we accept the premise that frequent renumbering in IPv6 is not 
seamless and is in fact painful and worth avoiding, then rather than 
hiding the source of the pain behind a NAT perhaps we should try to 
eliminate it: find a mechanism which facilitates pervasive multi-homing 
with some stable view of layer-3 addressing from the layer above, 
across re-homing events.

That would solve multi-homing, session stability across renumbering 
events and changing providers all in one hit.

There's a party going on in multi6, and you're all invited. (well, 
we're all in the kitchen at the moment, but we'll move out onto the 
deck if more people show up).


Joe






From owner-ietf@ietf.org  Tue Apr 22 08:59:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07026;
	Tue, 22 Apr 2003 08:59:40 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197xdi-0000W8-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 09:16:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 196hsl-0006JW-00
	for ietf@ran.ietf.org; Fri, 18 Apr 2003 22:15:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04124
	for <ietf@ietf.org>; Fri, 18 Apr 2003 21:54:18 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196hat-0002Zz-00
	for ietf@ietf.org; Fri, 18 Apr 2003 21:56:43 -0400
Received: from pheriche.sun.com ([192.18.98.34])
	by ietf-mx with esmtp (Exim 4.12)
	id 196has-0002Zw-00
	for ietf@ietf.org; Fri, 18 Apr 2003 21:56:42 -0400
Received: from esunmail ([129.147.58.120])
	by pheriche.sun.com (8.9.3p2+Sun/8.9.3) with ESMTP id TAA23504
	for <ietf@ietf.org>; Fri, 18 Apr 2003 19:56:58 -0600 (MDT)
Received: from xpa-fe1 ([129.147.58.198]) by edgemail1.Central.Sun.COM
 (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
 with ESMTP id <0HDK0034LIQXI0@edgemail1.Central.Sun.COM> for ietf@ietf.org;
 Fri, 18 Apr 2003 19:56:58 -0600 (MDT)
Received: from nifty-jr.west.sun.com ([129.153.12.95])
 by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
 with ESMTPSA id <0HDK0072SIQVS0@mail.sun.net> for ietf@ietf.org; Fri,
 18 Apr 2003 19:56:57 -0600 (MDT)
Date: Fri, 18 Apr 2003 18:55:12 -0700
From: Chris Newman <Chris.Newman@Sun.COM>
Subject: Re: STRN (was Re: Internet Draft Guidelines Require Precise
 Formatting?)
In-reply-to: <3EA09E8A.24338.4156D5@localhost>
To: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
Cc: Alexey Melnikov <mel@messagingdirect.com>, ietf@ietf.org
Message-id: <2147483647.1050692112@nifty-jr.west.sun.com>
MIME-version: 1.0
X-Mailer: Mulberry/3.0.3 (Mac OS X)
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-message-flag: Outlook: the best virus distribution system around
References: <3EA09E8A.24338.4156D5@localhost>
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

  <http://www.apps.ietf.org/rfc/rfc2645.html>

                - Chris

begin quotation by Sabahattin Gucukoglu on 2003/4/19 0:55 +0100:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 18 Apr 2003 at 13:00, Alexey Melnikov pronounced thusly:
>
>> > Hi all,
>> >
>> > I at some point in the (near, hopefully) future wish to submit an
>> > internet draft - STRN, ESMTP extension for secure client-server role
>> > exchange
>>
>> On a slightly different topic touched by your email: check ATRN
>> (authenticated TURN) extention before you decide to right STRN. I can try
>> to find the RFC number for it if you are interested.
>
> If by some miraculous chance you should prove luckier than I. :-(  So far
> M$ are the only folks I've seen implement ATRN, whatever the blasted thing
> is.  I only came across it accidentally when my server communicated with
> an Exchange server and it was listed in their ESMTP capabilities, and I
> have not found an I-D or RFC.
>
> Now may be a good time anyway to explain my ideas in brief... STRN does in
> fact appear to have significant likeness to this ATRN, with the idea being
> that STRN should provide a mechanism for specification of authentication
> method by which a change of role can occur, after which the authentication
> procedure is begun, independantly of, but not unlike, any other form of
> ESMTP authentication used for mail delivery (RFC3554).  Secure doesn't
> represent confidentiality in this context, it is simply meant as a more
> solidly foolproof turn without disadvantages commonly presented by ETRN.
> It may therefore end up as an updating RFC rather than a complete
> specification.
>
> Yes, if you do find the RFC please let me know where it is.
>
>> Cheers,
>> Alexey Melnikov
>
> Cheers,
> Sabahattin
>
> - --
>
> Thought for the day:
>     Concerto (n): a fight between a piano and a pianist.
>
> Latest PGP Public key?  Click:
> <mailto:PGPPublicKey@sabahattin-gucukoglu.com>
> and send that message as is.
>
> Sabahattin Gucukoglu
> Phone: +44 (0)20 7,502-1615
> Mobile: +44 (0)7986 053399
> http://www.sabahattin-gucukoglu.com/
> E-mail or MSN Messenger: <mail@Sabahattin-Gucukoglu.com>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 8.0 -- QDPGP 2.70
> Comment: Previous public key for ID <Sabahattin_Gucukoglu@mailandnews.co.uk>
> revoked due to invalidated primary address.
>
> iQA/AwUBPqCQeyNEOmEWtR2TEQJixwCfVW6VzJQH8pOTSl0yzf+F2uTlregAnR3f
> DthhaT4rMt4S7+a+N2EKL6cS
> =1XIC
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which is
> a sublist of ietf@ietf.org. Not all messages are passed. Decisions on what to
> pass are made solely by Raffaele D'Albenzio.









From owner-ietf@ietf.org  Tue Apr 22 09:05:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07375;
	Tue, 22 Apr 2003 09:05:22 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197xdi-0000WO-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 09:16:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1973vT-00043p-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 21:47:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13982
	for <ietf@ietf.org>; Sat, 19 Apr 2003 21:26:20 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1973dL-0000TX-00
	for ietf@ietf.org; Sat, 19 Apr 2003 21:28:43 -0400
Received: from vmmrnat.verisignmail.com ([216.168.230.187] helo=vmmr7.verisignmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1973dL-0000TU-00
	for ietf@ietf.org; Sat, 19 Apr 2003 21:28:43 -0400
Received: from ms1.verisignmail.com (ms1.verisignmail.com [216.168.230.167] (may be forged))
	by vmmr7.verisignmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id OUK66131;
	Sat, 19 Apr 2003 21:28:59 -0400 (EDT)
Received: from BOB.AppliedSNMP.com (pcp830034pcs.nrockv01.md.comcast.net [68.50.129.39])
	by ms1.verisignmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id AEE88939;
	Sat, 19 Apr 2003 21:28:57 -0400 (EDT)
Message-Id: <5.1.0.14.2.20030419212627.02109dc8@mail.AppliedSNMP.com>
X-Sender: Bob.Natale@AppliedSNMP.com@mail.AppliedSNMP.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 19 Apr 2003 21:40:03 -0400
To: Dave Crocker <dcrocker@brandenburg.com>
From: Bob Natale <Bob.Natale@AppliedSNMP.com>
Subject: Re: Architectural Considerations section in specs
Cc: ietf@ietf.org
In-Reply-To: <70125434335.20030419164712@brandenburg.com>
References: <5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
 <20030419151329.66daf0de.moore@cs.utk.edu>
 <16890640984.20030419070719@brandenburg.com>
 <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com>
 <a05210603bac6d68105ed@[10.0.0.3]>
 <11870.1050777166@munnari.OZ.AU>
 <14384.1050784134@munnari.OZ.AU>
 <20030419165921.782a8353.moore@cs.utk.edu>
 <5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 4/19/2003:07:47 PM, Dave Crocker wrote:

Hi Dave,

I regret that this is going to sound like I'm tooting
my horn or something like that, but I'm just noting it
for emphasis:  I made almost exactly the same argument
for an "Architectural Considerations" section on a par
with "Security Considerations" in IDs and RFCs on the
"problem statement" list in the early days of that list.
I am hopeful that your raising it will have more impact.

I seriously believe that lack of architectural coordination
across the IETF's many efforts casts a pall on our work
in subtle ways which have far more impact on many of the
larger constituencies for our work.

I would only add that the implications of your wording of
your last statement -- 

"Any specification that creates interesting features should be required
to specify its requirements on providers and its impact on consumers."

-- might be a bit too optimistic...I don't think it goes
quite far enough in noting that it will probably take
review by members of the small cadre of IETF architecture
experts to be sure that all relevant requirements and
impacts have been accounted for.  Many document authors
(like me, for instance) might not know enough about IP-wide
and Internet-wide architecture issues to do a thorough job
on their own.  (Of course, I guess that's true of the already
mandatory "Security Considerations" section too! :-)

Cheers,

BobN
- - - - -
>Folks,
>
>DS> I am saddened by the fact that Tony's simple question could not be
>DS> addressed. Site local addressing in IPv6 is a concept which has been
>DS> mentioned in RFC 1884, 2373 and 3513, the progression of Proposed 
>DS> Standards. This is a string of documents dating back to 1995. For eight
>DS> years this concept was apparently considered a good thing.
>
>The problem appears to have been that no one bothered to draw the
>necessary implications and circulate them for explicit consideration. So
>folks scanned a spec, didn't see anything that looked egregious, and
>only now are realizing how extensive the impact is.
>
>We have a very basic, very serious problem with coordination among
>different parts of the IETF.  Our tendency is to task various folks with
>doing a better "monitoring" job.
>
>My guess is that, instead, we *all* need to do a better job of noticing
>when we are specifying something that has an architectural impact, by
>which I mean something that affects other parts of the Internet service.
>
>Once upon a time, the Security Considerations section was pro forma.
>These days, it is taken seriously, and specifications are required to
>develop this section carefully.
>
>More recently we have added IANA Considerations sections, to make sure
>that administrative issues are handled more easily.
>
>Perhaps it is time to require specifications to make explicit statements
>about the impact the spec's features will have on architectural
>providers and consumers. That is, the features of a specification draw
>on system Internet services "below" and give services to parts of the
>system "above".
>
>Any specification that creates interesting features should be required
>to specify its requirements on providers and its impact on consumers.
>
>d/
>--
> Dave Crocker <mailto:dcrocker@brandenburg.com>
> Brandenburg InternetWorking <http://www.brandenburg.com>
> Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>
>
>
>_______________________________________________
>This message was passed through ietf_censored@carmen.ipv6.cselt.it, which is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on what to pass are made solely by Raffaele D'Albenzio. 






From owner-ietf@ietf.org  Tue Apr 22 09:05:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07402;
	Tue, 22 Apr 2003 09:05:26 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197xdj-0000WU-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 09:16:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1974Dz-0005p8-00
	for ietf@ran.ietf.org; Sat, 19 Apr 2003 22:06:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14246
	for <ietf@ietf.org>; Sat, 19 Apr 2003 21:45:27 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1973vr-0000W8-00
	for ietf@ietf.org; Sat, 19 Apr 2003 21:47:51 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1973vq-0000W5-00
	for ietf@ietf.org; Sat, 19 Apr 2003 21:47:50 -0400
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h3K1lg100596;
	Sat, 19 Apr 2003 18:47:42 -0700
Date: Sat, 19 Apr 2003 18:47:13 -0700
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dhc@dcrocker.net>
Organization: TribalWise
X-Priority: 3 (Normal)
Message-ID: <33132631323.20030419184713@dcrocker.net>
To: Bob Natale <Bob.Natale@AppliedSNMP.com>
CC: ietf@ietf.org
Subject: Re: Architectural Considerations section in specs
In-Reply-To: <5.1.0.14.2.20030419212627.02109dc8@mail.AppliedSNMP.com>
References: <5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
 <20030419151329.66daf0de.moore@cs.utk.edu>
 <16890640984.20030419070719@brandenburg.com>
 <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]>
 <11870.1050777166@munnari.OZ.AU> <14384.1050784134@munnari.OZ.AU>
 <20030419165921.782a8353.moore@cs.utk.edu>
 <5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
 <5.1.0.14.2.20030419212627.02109dc8@mail.AppliedSNMP.com>
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

Bob,

BN>  I made almost exactly the same argument
BN> for an "Architectural Considerations" section on a par

excellent. two, independent occurrences of a crazy idea by unrelated
lunatics probably means there is some merit to it. (by which i mean that
any desire to dismiss the idea because it is easy to dismiss the
proposer gets more difficult when there are multiple, independent
proposers. And, yes, it must be saturday night, for this kind of
writing.)


BN> "Any specification that creates interesting features should be required
BN> to specify its requirements on providers and its impact on consumers."

BN> -- might be a bit too optimistic...I don't think it goes
BN> quite far enough in noting that it will probably take
BN> review by members of the small cadre of IETF architecture
BN> experts to be sure that all relevant requirements and

that's fine.  the point of the exercise is to require specification
authors to pay significant attention to the question.  this actively
creates a dialogue on the issues, rather than hoping that some clever
architect notices this particular document.

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>






From owner-ietf@ietf.org  Tue Apr 22 09:05:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07432;
	Tue, 22 Apr 2003 09:05:38 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197xdj-0000Wk-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 09:16:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197HJc-0002Ar-00
	for ietf@ran.ietf.org; Sun, 20 Apr 2003 12:05:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08067
	for <ietf@ietf.org>; Sun, 20 Apr 2003 11:43:59 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 197H0S-0002yb-00
	for ietf@ietf.org; Sun, 20 Apr 2003 11:45:28 -0400
Received: from mxout4.cac.washington.edu ([140.142.33.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 197H0S-0002yY-00
	for ietf@ietf.org; Sun, 20 Apr 2003 11:45:28 -0400
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout4.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h3KFjiTc010799;
	Sun, 20 Apr 2003 08:45:44 -0700
Received: from TGX200.attbi.com (12-231-115-200.client.attbi.com [12.231.115.200])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h3KFji4t000397
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sun, 20 Apr 2003 08:45:44 -0700
Date: Sun, 20 Apr 2003 08:47:43 -0700 (Pacific Standard Time)
From: Terry Gray <gray@washington.edu>
To: Keith Moore <moore@cs.utk.edu>
cc: ietf@ietf.org
Subject: Re: A simple question
In-Reply-To: <20030420101911.09a143fb.moore@cs.utk.edu>
Message-ID: <Pine.WNT.4.55.0304200844040.1280@TGX200>
References: <200304200024.h3K0OdY06518@boreas.isi.edu> <20030420032426.GA9713@shrubbery.net>
 <g3u1ctwyvr.fsf@sa.vix.com> <20030420101911.09a143fb.moore@cs.utk.edu>
Slogan: "I get enough exercise just pushing my luck."
Organization: University of Washington;  Computing & Communications
X-X-Sender: gray@mailer23.u.washington.edu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


> the existence of scoped addresses in v6 forces a greater percentage of
> programs to be address aware.  some programs that could avoid being
> address aware in ipv4 cannot do so in v6 and provide the same functionality.

Keith,
For the benefit of us uninformed lurkers who learn best by example,
could you provide one?

Also, I'm wondering how the SL/1918 address-scoping debate plays in
the context of firewalls.  Don't firewalls provide an even more random
form of address scoping that apps must cope with?  Or not?

Thanks.

-teg





From owner-ietf@ietf.org  Tue Apr 22 09:07:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07687;
	Tue, 22 Apr 2003 09:07:37 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197xmP-0001qQ-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 09:25:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197itj-0005Y8-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 17:32:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02655
	for <ietf@ietf.org>; Mon, 21 Apr 2003 17:10:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197ib9-0003SF-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:13:11 -0400
Received: from [67.38.193.238] (helo=stewart.chicago.il.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 197ib8-0003S7-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:13:10 -0400
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1])
	by stewart.chicago.il.us (8.12.8p1/8.12.8) with ESMTP id h3LLCqac001212;
	Mon, 21 Apr 2003 16:12:52 -0500 (CDT)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <3EA45ED4.9060508@stewart.chicago.il.us>
Date: Mon, 21 Apr 2003 16:12:52 -0500
From: Randall Stewart <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021005
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Robert Elz <kre@munnari.OZ.AU>, stephen@sprunk.org,
        Valdis.Kletnieks@vt.edu, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
References: <00d001c306c0$faeadf90$93b58742@ssprunk>	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>	<16890640984.20030419070719@brandenburg.com>	<002401c30605$e22da070$261e4104@eagleswings>	<9540645034.20030418171403@brandenburg.com>	<a05210603bac6d68105ed@[10.0.0.3]>	<11870.1050777166@munnari.OZ.AU>	<14570.1050784897@munnari.OZ.AU>	<16762.1050792143@munnari.OZ.AU> <20030419192024.440d3773.moore@cs.utk.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:
>>  | To assign more than one address to every host means the host must have
>>  | an intelligent means of deciding which address to use.
>>
>>Yes, but the amount of intelligence actually needed is pretty minimal.
>>(It is actually harder to decide between multiple available global
>>prefixes, than to decide between global and site local - the former is
>>a difficult problem, the latter is almost trivial).
> 
> 
> disagree.  the app can choose any global prefix and reasonably expect it to
> work, modulo link failures. but when choosing between a global and a site
> local the app needs to know whether the site local address will be valid for
> the hosts that need to use it, and it has no way to know this.   the app may
> also have to choose which interface to use with the site-local prefix,
> and it has no good way to know this either.

Keith:

I agree 100%.. it is quite difficult to choose a site local... and a
real pain to be able to tell which interface to use or if the
peer host can really speak on that site local.... very very
ugly... and I say this with respect to trying to make things
work in the kame SCTP implementation.. As far as I am concerned
we could do with-OUT site-locals.. but of course I have
said this before too :>

R



> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------
> 
> 


-- 
Randall R. Stewart
randall@stewart.chicago.il.us 815-342-5222 (cell phone)






From owner-ietf@ietf.org  Tue Apr 22 09:11:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08032;
	Tue, 22 Apr 2003 09:11:39 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197xmP-0001qW-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 09:25:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197izx-00066q-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 17:38:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02920
	for <ietf@ietf.org>; Mon, 21 Apr 2003 17:17:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197ihM-0003Ts-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:19:36 -0400
Received: from mailhost.iprg.nokia.com ([205.226.5.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 197ihL-0003Th-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:19:35 -0400
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id OAA17865;
	Mon, 21 Apr 2003 14:19:22 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h3LLJLq14648;
	Mon, 21 Apr 2003 14:19:21 -0700
X-mProtect: <200304212119> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.2.67, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdMKReOG; Mon, 21 Apr 2003 14:19:20 PDT
Message-ID: <3EA460F9.9000204@iprg.nokia.com>
Date: Mon, 21 Apr 2003 14:22:01 -0700
From: "Fred L. Templin" <ftemplin@iprg.nokia.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Daniel Senie <dts@senie.com>, stephen@sprunk.org, RACarlson@anl.gov,
        ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A simple question
References: <20030419192024.440d3773.moore@cs.utk.edu>	<16762.1050792143@munnari.OZ.AU>	<00d001c306c0$faeadf90$93b58742@ssprunk>	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>	<16890640984.20030419070719@brandenburg.com>	<002401c30605$e22da070$261e
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:
>>b) if there's a strong need for appropriate 
>>ICMP responses to make IPv6 function well, then an RFC stating as much 
>>could be published.
> 
> 
> like, for instance, a need for path mtu discovery to work reliably?
> (since v6 routers don't fragment packets)

This is veering a bit off topic, but in the plpmtud bof at IETF 56
we were shown a method for determining path mtu that does not rely
on ICMPs. (ICMPs are untrustworthy and unreliable in any case, so
let's stop this red herring before it goes any farther.)

Thanks,

Fred
ftemplin@iprg.nokia.com








From owner-ietf@ietf.org  Tue Apr 22 09:11:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08034;
	Tue, 22 Apr 2003 09:11:39 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197xmP-0001qc-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 09:25:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197j7H-0006vc-00
	for ietf@ran.ietf.org; Mon, 21 Apr 2003 17:46:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03202
	for <ietf@ietf.org>; Mon, 21 Apr 2003 17:24:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197iog-0003Wy-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:27:10 -0400
Received: from [67.38.193.238] (helo=stewart.chicago.il.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 197iof-0003Wo-00
	for ietf@ietf.org; Mon, 21 Apr 2003 17:27:09 -0400
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1])
	by stewart.chicago.il.us (8.12.8p1/8.12.8) with ESMTP id h3LLRAac001237;
	Mon, 21 Apr 2003 16:27:10 -0500 (CDT)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <3EA4622E.9000900@stewart.chicago.il.us>
Date: Mon, 21 Apr 2003 16:27:10 -0500
From: Randall Stewart <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021005
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stephen Sprunk <stephen@sprunk.org>
CC: Keith Moore <moore@cs.utk.edu>, Robert Elz <kre@munnari.OZ.AU>,
        Valdis.Kletnieks@vt.edu, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
References: <00d001c306c0$faeadf90$93b58742@ssprunk><200304191923.h3JJNOuL018209@turing-police.cc.vt.edu><16890640984.20030419070719@brandenburg.com><002401c30605$e22da070$261e4104@eagleswings><9540645034.20030418171403@brandenburg.com><a05210603bac6d68105ed@[10.0.0.3]><11870.1050777166@munnari.OZ.AU><14570.1050784897@munnari.OZ.AU><16762.1050792143@munnari.OZ.AU> <20030419192024.440d3773.moore@cs.utk.edu> <005f01c306d2$c33cdaf0$93b58742@ssprunk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Stephen Sprunk wrote:
> Thus spake "Keith Moore" <moore@cs.utk.edu>
> 
>>>  | To assign more than one address to every host means the host
>>>  | must have an intelligent means of deciding which address to use.
>>>
>>>Yes, but the amount of intelligence actually needed is pretty minimal.
>>>(It is actually harder to decide between multiple available global
>>>prefixes, than to decide between global and site local - the former is
>>>a difficult problem, the latter is almost trivial).
>>
>>disagree.  the app can choose any global prefix and reasonably expect
>>it to work, modulo link failures.
> 
> 
> Nit: the vast majority of apps today bind to INADDR_ANY (or its IPv6
> equivalent), so it's really the OS which is choosing the source address.  If
> the app binds a specific source address, it is invariably user-configurable
> and thus not an application problem.
> 
> 
Nit2Nit :>

That may be.. but it sure does not help us poor kernel developers any
:-<

>>but when choosing between a global and a site local the app needs to
>>know whether the site local address will be valid for the hosts that need
>>to use it, and it has no way to know this.
> 
> 
> Well, since one can easily determine whether the destination address is SL
> or not, picking a source address of the correct class is trivial.
> 

I don't know if that is true.. if a host has multiple sites
on it and each site is multi-homed... aka

-------Intf-A---+----------+----Intf-D------
                 |          |
-------Intf-B---+----------+----Intf-C------

Say Intf-A/Intf-B are on one site
and
Intf-C/Intf-D are on another site..



Then if the SCTP stack is told to send a INIT -> out to a SL
address on Intf-A selecting the source address is somewhat ok
if the routing is set up.. but what other addresses do I list
in my INIT?

Ideally I would like to list the address for A and B. This way
my peer could take advantage of my multi-homing.. but instead
I can't... since when the peer receives the INIT it would have
no way of knowing the scope for the address and what interface
the address went with...

Other more complicated scenario's can also be imagined with
the above.. multiple sites on each host.. some shared some
not.. aakk... yuck...


It seems to me that with all the available address space having
a SL is just a waste.. If an enterprise is worried about
security put up something that is real aka a firewall.. not a
NAT...It does not really add anything but it does drag
along an ugly abomination that was needed as a stop-gap measure
for the  address shortfall.. Now we have the solution we are
dragging the old junk along.. how silly...

This SL thing seems to me like a un-needed complication..


> 
>>the app may also have to choose which interface to use with the site-
>>local prefix, and it has no good way to know this either.
> 
> 
> Ah, but it'll have a different SL address on each interface, so that's no
> worse than having multiple global addresses.  The truly interesting case is
> connecting to a LL address with multiple interfaces.
> 
> S
> 
> Stephen Sprunk         "God does not play dice."  --Albert Einstein
> CCIE #3723         "God is an inveterate gambler, and He throws the
> K5SSS        dice at every possible opportunity." --Stephen Hawking
> 
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------
> 
> 


-- 
Randall R. Stewart
randall@stewart.chicago.il.us 815-342-5222 (cell phone)






From owner-ietf@ietf.org  Tue Apr 22 09:43:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09009;
	Tue, 22 Apr 2003 09:43:18 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197yJf-0004Nv-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 10:00:11 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197yG6-00046S-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 09:56:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08860
	for <ietf@ietf.org>; Tue, 22 Apr 2003 09:34:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197xxL-0001kR-00
	for ietf@ietf.org; Tue, 22 Apr 2003 09:37:07 -0400
Received: from grouse.mail.pas.earthlink.net ([207.217.120.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 197xxK-0001kH-00
	for ietf@ietf.org; Tue, 22 Apr 2003 09:37:06 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by grouse.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 197xxV-0004I8-00; Tue, 22 Apr 2003 06:37:17 -0700
Date: Tue, 22 Apr 2003 09:36:49 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: moore@cs.utk.edu, alh-ietf@tndh.net, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030422093649.644d0eef.moore@cs.utk.edu>
In-Reply-To: <438340000.1051014766@askvoll.hjemme.alvestrand.no>
References: <001a01c305f7$a902cd60$261e4104@eagleswings>
	<438340000.1051014766@askvoll.hjemme.alvestrand.no>
X-Mailer: Sylpheed version 0.8.11 (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

> just to provide a "simple" answer to a simple question:
> 
> NO - I do not agree with Keith's assertion as quoted.
> YES - I agree with what I *believe* Keith wanted to say, which is that 
> "introduction of *site-scoped* addresses causes far more problems than it 
> solves".
> 
> I do NOT believe that introduction of link-local addresses causes far more 
> problems than it solves.

I see scoped addressing as a general problem, of which v6 site-locals and v4
link-locals are both examples.  That said, I think v6 link-locals as "mostly
harmless" provided that we use them only for things like router discovery.
If we started expecting ordinary applications to be able to use them, I'd move
them back to the "harmful" category - they'd have most of the problems of
site-locals.



From owner-ietf@ietf.org  Tue Apr 22 10:09:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10411;
	Tue, 22 Apr 2003 10:09:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 197yYg-0005t5-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 10:15:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 197yY6-0005oK-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 10:15:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09325
	for <ietf@ietf.org>; Tue, 22 Apr 2003 09:53:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197yFL-0001ra-00
	for ietf@ietf.org; Tue, 22 Apr 2003 09:55:43 -0400
Received: from web10902.mail.yahoo.com ([216.136.131.38])
	by ietf-mx with smtp (Exim 4.12)
	id 197yFK-0001rX-00
	for ietf@ietf.org; Tue, 22 Apr 2003 09:55:42 -0400
Message-ID: <20030422135604.52954.qmail@web10902.mail.yahoo.com>
Received: from [12.237.229.250] by web10902.mail.yahoo.com via HTTP; Tue, 22 Apr 2003 06:56:04 PDT
Date: Tue, 22 Apr 2003 06:56:04 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Re: Architectural Considerations section in specs
To: ietf@ietf.org
In-Reply-To: <33132631323.20030419184713@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Just one follow-on here - I'm seeing postings from others that
seem to imply that we need IESG review because that's where the
clue is, while Dave is pointing out that the IESG isn't the only
source of Internet architecture clue.

As I read Dave's note, this suggestion is an invitation for
people to develop clue before involving IESG folk, rather than
another black hole to absorb IESG time and effort (no matter how
noble the effort)...

Better for scaling, no?

SPencer

--- Dave Crocker <dhc@dcrocker.net> wrote:
> 
> BN> -- might be a bit too optimistic...I don't think it goes
> BN> quite far enough in noting that it will probably take
> BN> review by members of the small cadre of IETF architecture
> BN> experts to be sure that all relevant requirements and
> 
> that's fine.  the point of the exercise is to require
> specification
> authors to pay significant attention to the question.  this
> actively
> creates a dialogue on the issues, rather than hoping that some
> clever
> architect notices this particular document.



From owner-ietf@ietf.org  Tue Apr 22 13:13:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16597;
	Tue, 22 Apr 2003 13:13:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1981Ud-0000P4-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 13:23:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19807U-0002lT-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 11:55:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13797
	for <ietf@ietf.org>; Tue, 22 Apr 2003 11:34:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 197zoi-0002aN-00
	for ietf@ietf.org; Tue, 22 Apr 2003 11:36:20 -0400
Received: from vmmrnat.verisignmail.com ([216.168.230.187] helo=vmmr9.verisignmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 197zoh-0002aK-00
	for ietf@ietf.org; Tue, 22 Apr 2003 11:36:19 -0400
Received: from ms1.verisignmail.com (ms1.verisignmail.com [216.168.230.167] (may be forged))
	by vmmr9.verisignmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id PEB36407;
	Tue, 22 Apr 2003 11:31:53 -0400 (EDT)
Received: from BOB.AppliedSNMP.com (pcp830034pcs.nrockv01.md.comcast.net [68.50.129.39])
	by ms1.verisignmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id AEJ75575;
	Tue, 22 Apr 2003 11:31:52 -0400 (EDT)
Message-Id: <5.1.0.14.2.20030422112535.020f7130@mail.AppliedSNMP.com>
X-Sender: Bob.Natale@AppliedSNMP.com@mail.AppliedSNMP.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 22 Apr 2003 11:42:57 -0400
To: Spencer Dawkins <spencer_dawkins@yahoo.com>
From: Bob Natale <Bob.Natale@AppliedSNMP.com>
Subject: Re: Architectural Considerations section in specs
Cc: ietf@ietf.org
In-Reply-To: <20030422135604.52954.qmail@web10902.mail.yahoo.com>
References: <33132631323.20030419184713@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 4/22/2003:09:56 AM, Spencer Dawkins wrote:

Hi Spencer,

Yes, you are right that inviting people to "develop
clue" before involving the IESG would be more scalable
(or at least it would reduce the workload in terms of
submitted documents! :-).  But I am doubtful about the
results of such an approach in terms of near-term quality
and productivity (e.g., "re-work" by some reviewing
body).

My own initial view was that *review* (and possible
revision) of such an "Architecture Considerations"
section should be done by the IAB.  I realize that
suggestion might be impractical from organizational
and/or procedural aspects that I am unfamiliar with
or have not fully considered.  But I was expecting
we'd need more "top down" control in this area...at
least in the beginning.

Speaking as a member of the hoi polloi, I am often
dismayed at how much I *don't* know about Internet-
wide architecture (e.g., mobile IP implications,
internationalization considerations, multi-media
transfer protocols, etc.) when thinking about the
*few* things I do understand a bit. :-(  On the
positive side, I comfort myself with the thought
that no *one* person knows it all...and am thankful
that groups like the IAB and IESG are out there
to protect the 'net from me!  :-)

Cheers,

BobN

>Just one follow-on here - I'm seeing postings from others that
>seem to imply that we need IESG review because that's where the
>clue is, while Dave is pointing out that the IESG isn't the only
>source of Internet architecture clue.
>
>As I read Dave's note, this suggestion is an invitation for
>people to develop clue before involving IESG folk, rather than
>another black hole to absorb IESG time and effort (no matter how
>noble the effort)...
>
>Better for scaling, no?
>
>SPencer
>
>--- Dave Crocker <dhc@dcrocker.net> wrote:
>> 
>> BN> -- might be a bit too optimistic...I don't think it goes
>> BN> quite far enough in noting that it will probably take
>> BN> review by members of the small cadre of IETF architecture
>> BN> experts to be sure that all relevant requirements and
>> 
>> that's fine.  the point of the exercise is to require
>> specification
>> authors to pay significant attention to the question.  this
>> actively
>> creates a dialogue on the issues, rather than hoping that some
>> clever
>> architect notices this particular document.
>
>_______________________________________________
>This message was passed through ietf_censored@carmen.ipv6.cselt.it, which is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on what to pass are made solely by Raffaele D'Albenzio. 






From owner-ietf@ietf.org  Tue Apr 22 13:18:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16943;
	Tue, 22 Apr 2003 13:18:02 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1981gT-0001A0-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 13:35:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1981fG-0000gP-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 13:34:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16587
	for <ietf@ietf.org>; Tue, 22 Apr 2003 13:12:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1981MS-0003Ah-00
	for ietf@ietf.org; Tue, 22 Apr 2003 13:15:16 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1981MS-0003AJ-00
	for ietf@ietf.org; Tue, 22 Apr 2003 13:15:16 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id BBFBB1398B; Tue, 22 Apr 2003 17:15:08 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: A simple question
References: <16388.1050790957@munnari.OZ.AU>
	<5EE9BDD1-72BB-11D7-A6E0-00039312C852@isc.org>
From: Paul Vixie <vixie@vix.com>
Date: 22 Apr 2003 17:15:08 +0000
In-Reply-To: <5EE9BDD1-72BB-11D7-A6E0-00039312C852@isc.org>
Message-ID: <g3vfx63143.fsf@sa.vix.com>
Lines: 21
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> The rhetoric would have us believe that frequent renumbering with IPv6 
> is seamless and effortless. I don't personally buy that, but there are 
> some assumptions there that perhaps should be challenged more directly 
> rather than in this oblique fashion.

yesterday we had to change an AAAA RR and PTR RR because one of our
servers got a new GigE interface to replace the old FastE.  no part
of ipv6 renumbers seamlessly, from where i sit.

> If we accept the premise that frequent renumbering in IPv6 is not 
> seamless and is in fact painful and worth avoiding, then rather than 
> hiding the source of the pain behind a NAT perhaps we should try to 
> eliminate it: find a mechanism which facilitates pervasive multi-homing 
> with some stable view of layer-3 addressing from the layer above, 
> across re-homing events.

we did.  it was called A6.  now we're apparently on to something else,
like for example nothing, or for example pretending it's not a problem
after all.
-- 
Paul Vixie



From owner-ietf@ietf.org  Tue Apr 22 13:53:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18283;
	Tue, 22 Apr 2003 13:53:44 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1982BB-00049Y-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 14:07:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19829v-00041j-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 14:06:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17905
	for <ietf@ietf.org>; Tue, 22 Apr 2003 13:44:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1981r7-0003Vs-00
	for ietf@ietf.org; Tue, 22 Apr 2003 13:46:57 -0400
Received: from albatross.mail.pas.earthlink.net ([207.217.120.120])
	by ietf-mx with esmtp (Exim 4.12)
	id 1981r7-0003Vk-00
	for ietf@ietf.org; Tue, 22 Apr 2003 13:46:57 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by albatross.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1981rG-00043Z-00; Tue, 22 Apr 2003 10:47:07 -0700
Date: Tue, 22 Apr 2003 13:46:38 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Paul Vixie <vixie@vix.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: A simple question
Message-Id: <20030422134638.39c56917.moore@cs.utk.edu>
In-Reply-To: <g3vfx63143.fsf@sa.vix.com>
References: <16388.1050790957@munnari.OZ.AU>
	<5EE9BDD1-72BB-11D7-A6E0-00039312C852@isc.org>
	<g3vfx63143.fsf@sa.vix.com>
X-Mailer: Sylpheed version 0.8.11 (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

> we did.  it was called A6.  now we're apparently on to something else,
> like for example nothing, or for example pretending it's not a problem
> after all.

a6 wasn't even a start of a solution to the renumbering problem.
at best, it was a distraction, and a disaster waiting to happen.

note that a6 wouldn't have done anything to relieve the burden associated
with the case you cited - a host changing its network interface.



From owner-ietf@ietf.org  Tue Apr 22 14:04:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18859;
	Tue, 22 Apr 2003 14:04:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1982QW-0005rl-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 14:23:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1982J9-0004r3-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 14:15:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18319
	for <ietf@ietf.org>; Tue, 22 Apr 2003 13:54:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19820K-0003cA-00
	for ietf@ietf.org; Tue, 22 Apr 2003 13:56:28 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19820K-0003be-00
	for ietf@ietf.org; Tue, 22 Apr 2003 13:56:28 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id NAA26694;
	Tue, 22 Apr 2003 13:53:45 -0400
Date: Tue, 22 Apr 2003 13:54:03 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Paul Vixie <vixie@vix.com>
cc: ietf@ietf.org
Subject: Re: A simple question
In-Reply-To: <g3vfx63143.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0304221347180.16287-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Perhaps it would be easier without the PTR RR?

Then renumbering becomes a (possibly dynamic) update to the forward name.
Sounds pretty easy...

Regarding the second problem, Novell invented such a scheme many years
ago. It gave the host a separate network number and address from those of
the interfaces.  We approximate this scheme today in IPv4 using loopback
interfaces, frequently with /32 masks.  In this scheme, the interface
addresses are just part of the path to the host, but not actually the host
itself.

		--Dean

On 22 Apr 2003, Paul Vixie wrote:

> > The rhetoric would have us believe that frequent renumbering with IPv6
> > is seamless and effortless. I don't personally buy that, but there are
> > some assumptions there that perhaps should be challenged more directly
> > rather than in this oblique fashion.
>
> yesterday we had to change an AAAA RR and PTR RR because one of our
> servers got a new GigE interface to replace the old FastE.  no part
> of ipv6 renumbers seamlessly, from where i sit.
>
> > If we accept the premise that frequent renumbering in IPv6 is not
> > seamless and is in fact painful and worth avoiding, then rather than
> > hiding the source of the pain behind a NAT perhaps we should try to
> > eliminate it: find a mechanism which facilitates pervasive multi-homing
> > with some stable view of layer-3 addressing from the layer above,
> > across re-homing events.
>
> we did.  it was called A6.  now we're apparently on to something else,
> like for example nothing, or for example pretending it's not a problem
> after all.
> --
> Paul Vixie
>
>




From owner-ietf@ietf.org  Tue Apr 22 14:43:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19934;
	Tue, 22 Apr 2003 14:43:21 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1982zV-0000X6-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 14:59:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1982zQ-0000TB-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 14:59:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19826
	for <ietf@ietf.org>; Tue, 22 Apr 2003 14:37:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1982gb-00043d-00
	for ietf@ietf.org; Tue, 22 Apr 2003 14:40:09 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1982gb-00043P-00
	for ietf@ietf.org; Tue, 22 Apr 2003 14:40:09 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 3744B1398B; Tue, 22 Apr 2003 18:40:02 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: A simple question
References: <20030422134638.39c56917.moore@cs.utk.edu>
From: Paul Vixie <vixie@vix.com>
Date: 22 Apr 2003 18:40:02 +0000
In-Reply-To: <20030422134638.39c56917.moore@cs.utk.edu>
Message-ID: <g3r87u2x6l.fsf@sa.vix.com>
Lines: 16
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> a6 wasn't even a start of a solution to the renumbering problem.
> at best, it was a distraction, and a disaster waiting to happen.

i agree to disagree.

> note that a6 wouldn't have done anything to relieve the burden
> associated with the case you cited - a host changing its network
> interface.

true enough, but you can bet that if there were dns support for
the macroscopic problem, then i would be pushing some kind of dns
support for the microscopic problem as well.  as it is, there's
no foundation for it, other than campus-wide /128 "host" routes
which would scale poorly.
-- 
Paul Vixie



From owner-ietf@ietf.org  Tue Apr 22 15:22:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22524;
	Tue, 22 Apr 2003 15:22:13 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1983VR-0000b0-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 15:32:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1983S1-0007n2-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 15:29:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21403
	for <ietf@ietf.org>; Tue, 22 Apr 2003 15:07:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19839B-0004Il-00
	for ietf@ietf.org; Tue, 22 Apr 2003 15:09:41 -0400
Received: from dsl092-066-067.bos1.dsl.speakeasy.net ([66.92.66.67] helo=thrintun.hactrn.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19839B-0004IV-00
	for ietf@ietf.org; Tue, 22 Apr 2003 15:09:41 -0400
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id B63C418ED
	for <ietf@ietf.org>; Tue, 22 Apr 2003 15:09:34 -0400 (EDT)
Date: Tue, 22 Apr 2003 15:09:34 -0400
From: Rob Austein <sra+ietf@hactrn.net>
To: ietf@ietf.org
Subject: Re: A simple question
In-Reply-To: <Pine.WNT.4.55.0304200844040.1280@TGX200>
References: <200304200024.h3K0OdY06518@boreas.isi.edu>
	<20030420032426.GA9713@shrubbery.net>
	<g3u1ctwyvr.fsf@sa.vix.com>
	<20030420101911.09a143fb.moore@cs.utk.edu>
	<Pine.WNT.4.55.0304200844040.1280@TGX200>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030422190934.B63C418ED@thrintun.hactrn.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

At Sun, 20 Apr 2003 08:47:43 -0700 (Pacific Standard Time), Terry Gray wrote:
> 
> Also, I'm wondering how the SL/1918 address-scoping debate plays in
> the context of firewalls.  Don't firewalls provide an even more
> random form of address scoping that apps must cope with?  Or not?

To a first approximation, firewalls are an attempt to impose tighter
scoping on applications that (in the opinion of the entity operating
the firewall) cannot be trusted to make their own scope decisions.
Very different trust relationship from a situation in which the
applications themselves chose between multiple address scopes.



From owner-ietf@ietf.org  Tue Apr 22 16:16:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24386;
	Tue, 22 Apr 2003 16:16:37 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1984In-0005s0-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 16:23:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1984HT-0005hY-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 16:22:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23648
	for <ietf@ietf.org>; Tue, 22 Apr 2003 16:00:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1983yd-0004hU-00
	for ietf@ietf.org; Tue, 22 Apr 2003 16:02:51 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 1983yd-0004hP-00
	for ietf@ietf.org; Tue, 22 Apr 2003 16:02:51 -0400
Received: from psg.com ([147.28.0.62] helo=127.0.0.1)
	by psg.com with esmtp (Exim 3.36 #1)
	id 1983z0-0005BD-00; Tue, 22 Apr 2003 20:03:14 +0000
Date: Tue, 22 Apr 2003 13:02:17 -0700
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.62i) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <1488602489.20030422130217@psg.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
CC: Shahram Davari <Shahram_Davari@pmc-sierra.com>
Subject: Re: Last Call: Fast Reroute Extensions to RSVP-TE for LSP Tunnels  to Proposed Standard
In-Reply-To: <152134283229.20030327082759@psg.com>
References: 
 <4B6D09F3B826D411A67300D0B706EFDE0115C82A@nt-exch-yow.pmc-sierra.bc.ca>
 <152134283229.20030327082759@psg.com>
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


Sorry for a delay on this one.

The document is now back to the WG to address the issues brought up
during the IETF LC.

-- 
Alex
http://www.psg.com/~zinin/

Thursday, March 27, 2003, 9:27:59 AM, Alex Zinin wrote:
> Shahram,
> 
>   I'll follow up with the WG chairs on the issues you brought up here,
>   and will inform you and the list about the results.
> 
>   Thank you for reviewing the document.
> 
> -- 
> Alex
> 
> Tuesday, March 25, 2003, 2:45:35 PM, Shahram Davari wrote:
>> Since today is the last day of commenting, I just wanted to ask
>> what is the resolution to the comments raised. 
> 
>> Thanks,
>> Shahram Davari
>> PMC-Sierra
> 
> 
>>>>
>>>>
>>>>
>>>>The IESG has received a request from the Multiprotocol Label 
>>>Switching 
>>>>Working Group to consider Fast Reroute Extensions to RSVP-TE for LSP 
>>>>Tunnels <draft-ietf-mpls-rsvp-lsp-fastreroute-02.txt> as a Proposed 
>>>>Standard.  
>>>>
>>>>The IESG plans to make a decision in the next few weeks, and solicits
>>>>final comments on this action.  Please send any comments to the 
>>>>iesg@ietf.org or ietf@ietf.org mailing lists by 2003-3-25.
>>>>
>>>>Files can be obtained via 
>>>>http://www.ietf.org/internet-drafts/draft-ietf-mpls-rsvp-lsp-fa
>>>>streroute-02.txt
>>>>
>>>>
>>>>
>>>
>>>
>>>




From owner-ietf@ietf.org  Tue Apr 22 19:11:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00966;
	Tue, 22 Apr 2003 19:11:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198728-00009j-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 19:18:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19870H-0008Uf-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 19:16:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00720
	for <ietf@ietf.org>; Tue, 22 Apr 2003 18:54:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1986hQ-00068I-00
	for ietf@ietf.org; Tue, 22 Apr 2003 18:57:16 -0400
Received: from web10901.mail.yahoo.com ([216.136.131.37])
	by ietf-mx with smtp (Exim 4.12)
	id 1986hP-00068F-00
	for ietf@ietf.org; Tue, 22 Apr 2003 18:57:15 -0400
Message-ID: <20030422225739.78502.qmail@web10901.mail.yahoo.com>
Received: from [12.237.229.250] by web10901.mail.yahoo.com via HTTP; Tue, 22 Apr 2003 15:57:39 PDT
Date: Tue, 22 Apr 2003 15:57:39 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Re: A simple question
To: ietf@ietf.org
In-Reply-To: <20030422190934.B63C418ED@thrintun.hactrn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi, Rob,

I agree with your take from the network side, I'm thinking Terry
may be looking at it from the applications side (what's the
difference between one perfectly lovely address that fails
unpredictably and another perfectly lovely address that also
fails unpredictably? and the unknowable firewall topology is
probably within a first approximation of the unknowable site
topology).

But Terry can tell me I'm not thinking straight, if needed...

Spencer

--- Rob Austein <sra+ietf@hactrn.net> wrote:
> At Sun, 20 Apr 2003 08:47:43 -0700 (Pacific Standard Time),
> Terry Gray wrote:
> > 
> > Also, I'm wondering how the SL/1918 address-scoping debate
> plays in
> > the context of firewalls.  Don't firewalls provide an even
> more
> > random form of address scoping that apps must cope with?  Or
> not?
> 
> To a first approximation, firewalls are an attempt to impose
> tighter
> scoping on applications that (in the opinion of the entity
> operating
> the firewall) cannot be trusted to make their own scope
> decisions.
> Very different trust relationship from a situation in which
> the
> applications themselves chose between multiple address scopes.



From owner-ietf@ietf.org  Tue Apr 22 19:44:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01627;
	Tue, 22 Apr 2003 19:44:50 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1987hk-00034L-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 20:01:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1987fy-0002xC-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 19:59:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01472
	for <ietf@ietf.org>; Tue, 22 Apr 2003 19:37:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1987N6-0006Kn-00
	for ietf@ietf.org; Tue, 22 Apr 2003 19:40:20 -0400
Received: from 65-85-17-142.client.dsl.net ([65.85.17.142] helo=egate.xpasc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1987N5-0006KZ-00
	for ietf@ietf.org; Tue, 22 Apr 2003 19:40:19 -0400
Received: from localhost (dwm@localhost)
	by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id h3MNZVc16539
	for <ietf@ietf.org>; Tue, 22 Apr 2003 16:35:31 -0700
Date: Tue, 22 Apr 2003 16:35:31 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: <ietf@ietf.org>
Subject: Re: A simple question
In-Reply-To: <g3vfx63143.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.33.0304221633010.12011-100000@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On 22 Apr 2003, Paul Vixie wrote:

> > The rhetoric would have us believe that frequent renumbering with IPv6
> > is seamless and effortless. I don't personally buy that, but there are
> > some assumptions there that perhaps should be challenged more directly
> > rather than in this oblique fashion.
>
> yesterday we had to change an AAAA RR and PTR RR because one of our
> servers got a new GigE interface to replace the old FastE.  no part
> of ipv6 renumbers seamlessly, from where i sit.

IPV6 renumbering was guaranteed to always be problematic when the address
was defined to include the MAC address of the adapter. A mystery to me
from the day I first heard the design but since there is nothing I could
do to expect to change the design, I've not bothered to to try and
understand the rationale.




From owner-ietf@ietf.org  Tue Apr 22 23:19:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05304;
	Tue, 22 Apr 2003 23:19:54 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198Azw-0006Fz-00
	for ietf-list@ran.ietf.org; Tue, 22 Apr 2003 23:32:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198AzR-00069Y-00
	for ietf@ran.ietf.org; Tue, 22 Apr 2003 23:32:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05156
	for <ietf@ietf.org>; Tue, 22 Apr 2003 23:10:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198AgX-0007GD-00
	for ietf@ietf.org; Tue, 22 Apr 2003 23:12:37 -0400
Received: from flamingo.mail.pas.earthlink.net ([207.217.120.232])
	by ietf-mx with esmtp (Exim 4.12)
	id 198AgS-0007GA-00
	for ietf@ietf.org; Tue, 22 Apr 2003 23:12:32 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by flamingo.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 198Age-0002m2-00; Tue, 22 Apr 2003 20:12:44 -0700
Date: Tue, 22 Apr 2003 23:12:09 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <john-ietf@jck.com>
Cc: moore@cs.utk.edu, ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A simple question
Message-Id: <20030422231209.438176f7.moore@cs.utk.edu>
In-Reply-To: <70757023.1050910115@p3.JCK.COM>
References: <20030419192024.440d3773.moore@cs.utk.edu>
	<16762.1050792143@munnari.OZ.AU>
	<00d001c306c0$faeadf90$93b58742@ssprunk>
	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
	<16762.1050792143@munnari.OZ.AU>
	<5.2.1.1.2.20030420140541.0290fb00@mail.amaranth.net>
	<5.2.1.1.2.20030420201343.02a336c0@mail.amaranth.net>
	<20030420221319.62964599.moore@cs.utk.edu>
	<70757023.1050910115@p3.JCK.COM>
X-Mailer: Sylpheed version 0.8.11 (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

let me see if I can clarify this by restating it.

1. Apps know best what kinds of services they need.  The network doesn't know
this unless the app has some way of telling the network 
(e.g. TOS/QoS/diffserv/intserv/packet-class flavor-of-the-year).

2. The network knows best where hosts are located, and how to get packets from
here to there (if possible). The network also knows whether it's permitted to
send packets from here to there (perhaps limited by available routes or
policy, perhaps limited by packet filtering).  Most apps don't know these
things and shouldn't have to know them.  However it can be useful if the
network has some way to tell hosts and apps that it's not possible to get
packets from here to there, and the reason for that.  Traditionally ICMP has
fulfilled this role.

Now there are apps that have to know about network topology, such as network
management tools.  But in general we don't want to burden hosts and apps with
having to have this kind of knowledge, because there's no good way to get it
from the network, and to make it work reliably would require requiring the
network to feed routing and policy information to potentially all hosts.

3. Neither the kind of service being requested/provided nor information
about whether traffic is permitted should be wired into an IP address -
First because it forces a binding between policy and/or service and network
location which is inflexible and doesn't scale well; second because it
invites/begs/demands hosts and apps to know about network topology - i.e. to
second-guess the network.

4. Hosts shouldn't have to pick the "right" source or destination address in
order to get the network to do its job of getting the bits from here to there
(for some well-defined "here" and "there"), because hosts don't have the
requisite knowledge to do this, and because a requirement to pick the right
destination address means that addresses don't have a consistent meaning from
one source host to another.  To the extent that a host has to pick the "right"
interface, it needs to be possible to make the right choice from information
that the host normally has at hand (like matching prefix lengths).

Similarly, using address selection as a means to select a particular service
quality, or a particular security level, etc. is a best a stopgap measure 
because once again it requires apps to know about specific address ranges
and/or network topology.  

Note that scoped addresses make it difficult for each of the network, hosts,
and apps to do  their jobs - the network can't tell whether it can get the
traffic to the destination because the destination address is ambiguous (so
for instance, how can it tell the difference between "prohibited" and "no
route to destination" and "no such host" - and while it might have unambiguous
rules for how to route such addresses, that doesn't mean the traffic went to
the right place); hosts can't tell which interface to use to send the traffic;
and apps can't tell whether or not the address is usable to reach the desired
peer (either locally or by another peer).

--

Does any of the above mean that apps should never explicitly select source
and/or destination addresses or interfaces?  No, it means our network
architecture should not expect ordinary apps to make such selections
in order to sucessfully obtain services from the network. 

Now, because of mobile IP and privacy addresses, we're still going to have
situations where apps need to give their hosts an idea of what kinds of
addresses they need.  E.g. Does the app need an address that continues to work
as the host moves, or will the in-care-of address do?  Does it prefer an
address that is stably associated with the host, or is a temporary address
more appropriate?  But the answers to both of these questions *are* things
that the app can be expected to know.  Furthermore, unlike service quality or
security, these things inherently require address selection.  And unlike
site-local, these properties are essentially opaque to other hosts in the
network - thus we cannot expect/demand that other hosts use information
embedded in the address and behave differently for different kinds of
addresses.

And of course it will always be possible to set up or encounter situations
where apps that have knowledge about the network topology (or which
exhaustively try all known source/destination pairs) can succeed where apps
that don't go to extreme measures will fail.  In some ways this is an argument
about how we divide up the burden - which burdens we should place on hosts and
apps and which ones we should place on the network.  And the essence of the 
argument is:  don't expect either one to make decisions about things it
doesn't know about.  And this further argues for not having more addresses for
a host than necessary,  for not using multiple addresses as a mechanism to
provide different levels of access to a host, and for eschewing ambiguous
addresses.

Keith

> > I disagree that the IP stack can supply reasonable defaults in
> > the face of multiple scopes.  The criteria for choosing a
> > source address varies widely from one application to another.
> > Some applications need stable addresses, others need addresses
> > usable from all of their potential peers, others need to
> > choose the source address that results in the best performance
> > (where there is more than one meaning of 'best performance').
> > The default address selection rules are at best a guess.
> >
> > We should let the network do routing, so that hosts and apps
> > aren't expected to make routing decisions.
> 
> Keith,
> 
> I don't understand your point here, and would like to.  It seems 
> to me that your first paragraph ("I disagree...") suggests that 
> the applications need to specify the addresses/interfaces 
> because they know their needs and the stack can't figure it out. 
> And the second argues for pushing the decisions onto the 
> network, which has no information at all (and, if it had it, 
> could probably apply it only by changing addresses mid-flight -- 
> NAT-like or worse).  That suggests to me a conclusion of "not 
> application, not stack, not network either" which leaves very 
> few options.
> 
> If I ignore that apparent contradiction, I'm left with the 
> conclusion that we need some new addressing and routing 
> abstractions so that the applications can tell the stack (and 
> the stack might tell, or negotiate with, the network) what 
> considerations they need optimized and do so without specifying 
> specific addresses or inspecting components of addresses.  It 
> seems to me that such abstractions would also eliminate one of 
> the arguments against site local: having an application able to 
> tell the stack:
> 
> 	* I need a local address
> 	
> 	* I need an appropriate address for routing to <DNS name>
> 	
> 	* I need a completely-global address
> 
> Are all far more reasonable than having the application itself 
> recognize particular addresses or prefixes and trying to figure 
> out which ones make sense in its context.  It also _might_ 
> suggest that we need to reexamine ICMP in the IPv6 context to be 
> sure that, if the stack needs information from the network to 
> make satisfactory choices along these lines, it can ask them 
> without, e.g., trying to set up one or more TCP connections (or 
> sending UDP packet using an unspecified protocol) and waiting 
> for the responses or timeouts.
> 
> Is that really where we need to be headed and, if so, is anyone 
> doing the work rather than being stuck on "local-good / 
> local-bad", "scope-necessary / scope-bad", types of arguments?




From owner-ietf@ietf.org  Wed Apr 23 01:36:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08353;
	Wed, 23 Apr 2003 01:36:13 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198D9U-00060s-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 01:50:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198D7D-0005ks-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 01:48:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08186
	for <ietf@ietf.org>; Wed, 23 Apr 2003 01:26:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198CoH-00001q-00
	for ietf@ietf.org; Wed, 23 Apr 2003 01:28:45 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198CoG-00001M-00
	for ietf@ietf.org; Wed, 23 Apr 2003 01:28:45 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h3N5STb17386;
	Wed, 23 Apr 2003 08:28:29 +0300
Date: Wed, 23 Apr 2003 08:28:28 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: A simple question
In-Reply-To: <Pine.LNX.4.33.0304221633010.12011-100000@egate.xpasc.com>
Message-ID: <Pine.LNX.4.44.0304230825570.16945-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 22 Apr 2003, David Morris wrote:
> On 22 Apr 2003, Paul Vixie wrote:
> 
> > > The rhetoric would have us believe that frequent renumbering with IPv6
> > > is seamless and effortless. I don't personally buy that, but there are
> > > some assumptions there that perhaps should be challenged more directly
> > > rather than in this oblique fashion.
> >
> > yesterday we had to change an AAAA RR and PTR RR because one of our
> > servers got a new GigE interface to replace the old FastE.  no part
> > of ipv6 renumbers seamlessly, from where i sit.
> 
> IPV6 renumbering was guaranteed to always be problematic when the address
> was defined to include the MAC address of the adapter. A mystery to me
> from the day I first heard the design but since there is nothing I could
> do to expect to change the design, I've not bothered to to try and
> understand the rationale.

Who said IPv6 addresses based on MAC addresses should be used on servers?

We certainly don't.  Manually configuring is the thing.

FWIW, that process could be simpler too, though.  But that's mostly
implementation issues.  An example is using RA's for setting default route
but not configuring the address, and manually configuring only the EUI64
part but using the advertised /64.  If it comes to making renumbering
easier, I might document these as ways to make it easier.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From owner-ietf@ietf.org  Wed Apr 23 03:22:53 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06331;
	Wed, 23 Apr 2003 03:22:53 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198Eo6-00023w-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 03:36:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198EnR-00020S-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 03:36:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06177
	for <ietf@ietf.org>; Wed, 23 Apr 2003 03:14:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198EUU-0000w8-00
	for ietf@ietf.org; Wed, 23 Apr 2003 03:16:26 -0400
Received: from tomts5.bellnexxia.net ([209.226.175.25] helo=tomts5-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198EUT-0000w5-00
	for ietf@ietf.org; Wed, 23 Apr 2003 03:16:25 -0400
Received: from yahoo.com ([65.93.189.40]) by tomts5-srv.bellnexxia.net
          (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP
          id <20030423071644.PCPA25164.tomts5-srv.bellnexxia.net@yahoo.com>;
          Wed, 23 Apr 2003 03:16:44 -0400
Date: Wed, 23 Apr 2003 03:16:44 -0400
Subject: Re: A simple question
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Spencer Dawkins <spencer_dawkins@yahoo.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <20030422225739.78502.qmail@web10901.mail.yahoo.com>
Message-Id: <8986EB42-755B-11D7-89E4-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Tuesday, April 22, 2003, at 06:57  PM, Spencer Dawkins wrote:

> Hi, Rob,
>
> I agree with your take from the network side, I'm thinking Terry
> may be looking at it from the applications side (what's the
> difference between one perfectly lovely address that fails
> unpredictably and another perfectly lovely address that also
> fails unpredictably? and the unknowable firewall topology is
> probably within a first approximation of the unknowable site
> topology).

The differences:
- firewalls are a necessary evil for security, whereas site locals are 
(maybe) not
- firewalls are a simple on/off switch and easy to change, whereas site 
locals have complex state and are hard to change

Firewalls and NAT / site-locals might seem to be entangled, but it's 
just a coincidence. They both work best in the same place in the 
network, so many firewalls also do NAT.

simon

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Wed Apr 23 04:48:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07995;
	Wed, 23 Apr 2003 04:48:31 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198GAG-0007Sv-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 05:03:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198GAA-0007PM-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 05:03:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07795
	for <ietf@ietf.org>; Wed, 23 Apr 2003 04:41:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198FrC-0001Ld-00
	for ietf@ietf.org; Wed, 23 Apr 2003 04:43:58 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198FrB-0001La-00
	for ietf@ietf.org; Wed, 23 Apr 2003 04:43:57 -0400
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id JAA03258
	for <ietf@ietf.org>; Wed, 23 Apr 2003 09:44:21 +0100 (BST)
Received: from login.ecs.soton.ac.uk (login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3p2/8.9.3) with ESMTP id JAA14627
	for <ietf@ietf.org>; Wed, 23 Apr 2003 09:44:21 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h3N8iLj14939
	for ietf@ietf.org; Wed, 23 Apr 2003 09:44:21 +0100
Date: Wed, 23 Apr 2003 09:44:21 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: A simple question
Message-ID: <20030423084421.GG14323@login.ecs.soton.ac.uk>
References: <Pine.LNX.4.33.0304221633010.12011-100000@egate.xpasc.com> <Pine.LNX.4.44.0304230825570.16945-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0304230825570.16945-100000@netcore.fi>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Apr 23, 2003 at 08:28:28AM +0300, Pekka Savola wrote:
> 
> Who said IPv6 addresses based on MAC addresses should be used on servers?
> 
> We certainly don't.  Manually configuring is the thing.

although not with <prefix>::1, at least pick a random-ish 64-bit host
part to make the port scanners have to work rather harder...

tim



From owner-ietf@ietf.org  Wed Apr 23 06:01:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09540;
	Wed, 23 Apr 2003 06:01:30 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198HHw-0003PP-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 06:15:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198HHK-0003Lt-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 06:15:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09312
	for <ietf@ietf.org>; Wed, 23 Apr 2003 05:53:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198GyM-0001fV-00
	for ietf@ietf.org; Wed, 23 Apr 2003 05:55:26 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198GyL-0001fR-00
	for ietf@ietf.org; Wed, 23 Apr 2003 05:55:25 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h3N9sl319430;
	Wed, 23 Apr 2003 12:54:47 +0300
Date: Wed, 23 Apr 2003 12:54:47 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Tim Chown <tjc@ecs.soton.ac.uk>
cc: ietf@ietf.org
Subject: Re: A simple question
In-Reply-To: <20030423084421.GG14323@login.ecs.soton.ac.uk>
Message-ID: <Pine.LNX.4.44.0304231253010.19172-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 23 Apr 2003, Tim Chown wrote:
> On Wed, Apr 23, 2003 at 08:28:28AM +0300, Pekka Savola wrote:
> > 
> > Who said IPv6 addresses based on MAC addresses should be used on servers?
> > 
> > We certainly don't.  Manually configuring is the thing.
> 
> although not with <prefix>::1, at least pick a random-ish 64-bit host
> part to make the port scanners have to work rather harder...

Yep.  For example, we use a very simple numbering which makes all the
hosts within a site unique (so, there will not be an address collision
even if server A is moved from link 1 to link 2 where server B is).

Works Just Great (tm).  (Except implementation support could be better 
:-).

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From owner-ietf@ietf.org  Wed Apr 23 08:33:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15805;
	Wed, 23 Apr 2003 08:33:48 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198JYI-0006Cp-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 08:40:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198JUT-00061K-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 08:36:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15013
	for <ietf@ietf.org>; Wed, 23 Apr 2003 08:14:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198JBT-0003EQ-00
	for ietf@ietf.org; Wed, 23 Apr 2003 08:17:07 -0400
Received: from web10908.mail.yahoo.com ([216.136.131.44])
	by ietf-mx with smtp (Exim 4.12)
	id 198JBS-0003EN-00
	for ietf@ietf.org; Wed, 23 Apr 2003 08:17:06 -0400
Message-ID: <20030423121730.18200.qmail@web10908.mail.yahoo.com>
Received: from [12.237.229.250] by web10908.mail.yahoo.com via HTTP; Wed, 23 Apr 2003 05:17:30 PDT
Date: Wed, 23 Apr 2003 05:17:30 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Re: A simple question
To: ietf@ietf.org, ipng@sunroof.eng.sun.com
In-Reply-To: <20030422231209.438176f7.moore@cs.utk.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Dear Keith,

This posting was so helpful that we should probably change the
thread subject! 

I have a few questions/comments.

Spencer

--- Keith Moore <moore@cs.utk.edu> wrote:
> let me see if I can clarify this by restating it.
> 
> 1. Apps know best what kinds of services they need.  The
> network doesn't know
> this unless the app has some way of telling the network 
> (e.g. TOS/QoS/diffserv/intserv/packet-class
> flavor-of-the-year).

Agreed.

> 
> 2. The network knows best where hosts are located, and how to
> get packets from
> here to there (if possible). The network also knows whether
> it's permitted to
> send packets from here to there (perhaps limited by available
> routes or
> policy, perhaps limited by packet filtering).  Most apps don't
> know these
> things and shouldn't have to know them.  However it can be
> useful if the
> network has some way to tell hosts and apps that it's not
> possible to get
> packets from here to there, and the reason for that. 
> Traditionally ICMP has
> fulfilled this role.

Agreed.

I would be thrilled if we spent some time thinking about ICMP in
an architectural way - however beautiful it was before ICMP
black holing, what we have now isn't consistently usable today.
We're spending time on point solutions (Matt Mathis on non-ICMP
path MTU discovery as one example), but is this the best we can
do?
> 
> Now there are apps that have to know about network topology,
> such as network
> management tools.  But in general we don't want to burden
> hosts and apps with
> having to have this kind of knowledge, because there's no good
> way to get it
> from the network, and to make it work reliably would require
> requiring the
> network to feed routing and policy information to potentially
> all hosts.
> 

Agreed. We've been discouraging hosts from listening to routing
protocol exchanges for some time now.

> 3. Neither the kind of service being requested/provided nor
> information
> about whether traffic is permitted should be wired into an IP
> address -
> First because it forces a binding between policy and/or
> service and network
> location which is inflexible and doesn't scale well; second
> because it
> invites/begs/demands hosts and apps to know about network
> topology - i.e. to
> second-guess the network.
> 

Agreed.

> 4. Hosts shouldn't have to pick the "right" source or
> destination address in
> order to get the network to do its job of getting the bits
> from here to there
> (for some well-defined "here" and "there"), because hosts
> don't have the
> requisite knowledge to do this, and because a requirement to
> pick the right
> destination address means that addresses don't have a
> consistent meaning from
> one source host to another.  To the extent that a host has to
> pick the "right"
> interface, it needs to be possible to make the right choice
> from information
> that the host normally has at hand (like matching prefix
> lengths).
> 

Agreed.

> Similarly, using address selection as a means to select a
> particular service
> quality, or a particular security level, etc. is a best a
> stopgap measure 
> because once again it requires apps to know about specific
> address ranges
> and/or network topology.  
> 

Strongly agreed here.

> Note that scoped addresses make it difficult for each of the
> network, hosts,
> and apps to do  their jobs - the network can't tell whether it
> can get the
> traffic to the destination because the destination address is
> ambiguous (so
> for instance, how can it tell the difference between
> "prohibited" and "no
> route to destination" and "no such host" - and while it might
> have unambiguous
> rules for how to route such addresses, that doesn't mean the
> traffic went to
> the right place); hosts can't tell which interface to use to
> send the traffic;
> and apps can't tell whether or not the address is usable to
> reach the desired
> peer (either locally or by another peer).
> 

This was my point (perhaps I wasn't clear enough) about the
difference between site-local and firewalling - if your peer
isn't reachable because of an explicit decision from a network
operator (firewall), that's one class of problem; if your peer
isn't reachable because you have an address that doesn't work,
BUT YOU COULD HAVE BEEN GIVEN ANOTHER ADDRESS THAT WOULD HAVE
WORKED (site-local), that's a different class of problem.

The thing that bugs me is, I don't have any idea how the
application can tell that they have the second class of problem
- even ignoring ICMP Unreachable black-holing for a moment. Am I
missing something? (I don't think I'm a Genius of IPv6)

> --
> 
> Does any of the above mean that apps should never explicitly
> select source
> and/or destination addresses or interfaces?  No, it means our
> network
> architecture should not expect ordinary apps to make such
> selections
> in order to sucessfully obtain services from the network. 

Agree.

> 
> Now, because of mobile IP and privacy addresses, we're still
> going to have
> situations where apps need to give their hosts an idea of what
> kinds of
> addresses they need.  E.g. Does the app need an address that
> continues to work
> as the host moves, or will the in-care-of address do?  Does it
> prefer an
> address that is stably associated with the host, or is a
> temporary address
> more appropriate?  But the answers to both of these questions
> *are* things
> that the app can be expected to know.  Furthermore, unlike
> service quality or
> security, these things inherently require address selection. 
> And unlike
> site-local, these properties are essentially opaque to other
> hosts in the
> network - thus we cannot expect/demand that other hosts use
> information
> embedded in the address and behave differently for different
> kinds of
> addresses.
> 

From RFC 3344, the current Mobile IP spec:

1.1. Protocol Requirements

[deleted down to]

   A mobile node must be able to communicate with other nodes
that do
   not implement these mobility functions.  No protocol
enhancements are
   required in hosts or routers that are not acting as any of
the new
   architectural entities introduced in Section 1.5.

And I agree I'm extrapolating, but - I always thought language
like this said Mobile IP is a host IP networking thing, not a
host application thing.

I'm not sure I'm understanding what you're saying - are you
saying that my mobile host should know it's mobile (I believe
you), or that Mozilla on a mobile host should know it's mobile
(I'm struggling here)?

My understanding of Mobile IP was that the mobile host knows,
not Mozilla (or, at least, Mozilla works if it doesn't know).

Re: security - are you thinking of applications that prefer
site-local (in IPv4, probably NATed 1918 addresses) for
"security", or is there another common use of
addresses-for-security I don't know about?

> And of course it will always be possible to set up or
> encounter situations
> where apps that have knowledge about the network topology (or
> which
> exhaustively try all known source/destination pairs) can
> succeed where apps
> that don't go to extreme measures will fail.  In some ways
> this is an argument
> about how we divide up the burden - which burdens we should
> place on hosts and
> apps and which ones we should place on the network.  And the
> essence of the 
> argument is:  don't expect either one to make decisions about
> things it
> doesn't know about.  And this further argues for not having
> more addresses for
> a host than necessary,  for not using multiple addresses as a
> mechanism to
> provide different levels of access to a host, and for
> eschewing ambiguous
> addresses.

Agreed, because I think you're using "hosts" and "apps" almost
interchangeably here, to mean "not the network".

> 
> Keith



From owner-ietf@ietf.org  Wed Apr 23 10:44:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21336;
	Wed, 23 Apr 2003 10:44:52 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198Lkk-0007YF-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 11:01:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198LkU-0007T9-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 11:01:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21191
	for <ietf@ietf.org>; Wed, 23 Apr 2003 10:39:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198LRS-0004LG-00
	for ietf@ietf.org; Wed, 23 Apr 2003 10:41:46 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198LRS-0004LD-00
	for ietf@ietf.org; Wed, 23 Apr 2003 10:41:46 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26084> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 23 Apr 2003 07:42:08 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>,
        <ipng@sunroof.eng.sun.com>
Cc: <ietf@ietf.org>
Subject: A follow up question
Date: Wed, 23 Apr 2003 07:42:08 -0700
Message-ID: <032a01c309a6$84b1ece0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <438340000.1051014766@askvoll.hjemme.alvestrand.no>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA21336

Thank you, this was the only simple answer to the simple question. 

For the followup question: 
Do you believe that the IETF created the architectural concept of
addresses with a limited scope?

Tony


> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On 
> Behalf Of Harald Tveit Alvestrand
> Sent: Tuesday, April 22, 2003 5:33 AM
> To: alh-ietf@tndh.net; ipng@sunroof.eng.sun.com
> Cc: ietf@ietf.org
> Subject: Re: A simple question
> 
> 
> just to provide a "simple" answer to a simple question:
> 
> NO - I do not agree with Keith's assertion as quoted.
> YES - I agree with what I *believe* Keith wanted to say, 
> which is that 
> "introduction of *site-scoped* addresses causes far more 
> problems than it 
> solves".
> 
> I do NOT believe that introduction of link-local addresses 
> causes far more 
> problems than it solves.
> 
> My position on SL should be well known. I'll try to avoid 
> repeating the 
> rest of my arguments once again in this discussion tree.
> 
>                 Harald
> 
> 
> --On fredag, april 18, 2003 15:12:54 -0700 Tony Hain 
> <alh-ietf@tndh.net> 
> wrote:
> 
> > Keith Moore wrote:
> >> It doesn't solve all problems, but introduction of
> >> scoped addresses causes far more problems than it solves.
> >
> > I would like to understand how many people that voted YES on the 
> > question of deprecating SL concur with Keith's assertion.
> >
> > Tony
> >
> > Note: I cc'd the IETF list to catch those who may have been in the 
> > room in SF, but aren't on the IPv6 list.
> >
> >
> > --------------------------------------------------------------------
> > IETF IPng Working Group Mailing List
> > IPng Home Page:                      http://playground.sun.com/ipng
> > FTP archive:                      ftp://playground.sun.com/pub/ipng
> > Direct all administrative requests to majordomo@sunroof.eng.sun.com
> > --------------------------------------------------------------------
> >
> 
> 
> 




From owner-ietf@ietf.org  Wed Apr 23 11:04:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22302;
	Wed, 23 Apr 2003 11:04:22 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198M46-000178-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 11:21:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198M3X-000120-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 11:21:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22134
	for <ietf@ietf.org>; Wed, 23 Apr 2003 10:59:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198LkV-0004Xy-00
	for ietf@ietf.org; Wed, 23 Apr 2003 11:01:27 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198LkU-0004Xv-00
	for ietf@ietf.org; Wed, 23 Apr 2003 11:01:26 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26092> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 23 Apr 2003 08:01:51 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
Subject: RE: Architectural Considerations section in specs
Date: Wed, 23 Apr 2003 08:01:51 -0700
Message-ID: <033901c309a9$45d0f130$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <70125434335.20030419164712@brandenburg.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA22302

Dave Crocker wrote:
> Folks,
> 
> DS> I am saddened by the fact that Tony's simple question 
> could not be 
> DS> addressed. Site local addressing in IPv6 is a concept 
> which has been 
> DS> mentioned in RFC 1884, 2373 and 3513, the progression of Proposed 
> DS> Standards. This is a string of documents dating back to 1995. For 
> DS> eight years this concept was apparently considered a good thing.
> 
> The problem appears to have been that no one bothered to draw 
> the necessary implications and circulate them for explicit 
> consideration. So folks scanned a spec, didn't see anything 
> that looked egregious, and only now are realizing how 
> extensive the impact is.

What they are missing is that a defined prefix doesn't create the
problem that they are complaining about. Limiting the usable scope of
addresses is an operations decision. The mismatch between the
operational reality of limited scope addresses and the app developer
fantasy that there is a single flat routing space is the core problem
here.

Defining a prefix for those only made it *possible* for apps to
recognize which ones might be restricted. It does not *make* apps deal
with the problem of leaking addresses outside their scope of relevance
(unless you take the viewpoint that end users actually expect
applications to work right, and will require it once it is possible).
Applications are not required to understand topology, unless and until
they insist on passing around topology specific information. If any
process is going to pass around topology specific information, it MUST
understand the topology it is describing. 

There is no magic here, and defining a prefix didn't change the
architecture. Operational decisions established the architecture, and it
is our job to define the technologies that work within that
architectural reality. We can choose to continue to declare a
'flat-earth' and insist that applications and name resolution
infrastructure are free to arbitrarily pass around topology specific
objects, or we can choose to recognize the reality of the deployed
network and build the technologies that allow applications to operate
correctly within it. 

Tony




From owner-ietf@ietf.org  Wed Apr 23 11:04:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22331;
	Wed, 23 Apr 2003 11:04:25 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198M62-0001HJ-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 11:23:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198M55-0001CB-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 11:22:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22169
	for <ietf@ietf.org>; Wed, 23 Apr 2003 11:00:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198Lm3-0004YZ-00
	for ietf@ietf.org; Wed, 23 Apr 2003 11:03:03 -0400
Received: from smtp01.mrf.mail.rcn.net ([207.172.4.60])
	by ietf-mx with esmtp (Exim 4.12)
	id 198Lm2-0004YW-00
	for ietf@ietf.org; Wed, 23 Apr 2003 11:03:02 -0400
Received: from 208-59-250-55.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com ([208.59.250.55] helo=localhost)
	by smtp01.mrf.mail.rcn.net with smtp (Exim 3.35 #4)
	id 198LmR-0002rM-00; Wed, 23 Apr 2003 11:03:27 -0400
From: "Jeffrey Race" <jrace@attglobal.net>
To: "Jeffrey Race" <jrace@attglobal.net>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 23 Apr 2003 11:03:29 +0700
Reply-To: "Jeffrey Race" <jrace@attglobal.net>
X-Mailer: PMMail 1.96a For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
Message-Id: <E198LmR-0002rM-00@smtp01.mrf.mail.rcn.net>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Mon, 21 Apr 2003 17:05:32 -0700, Dave Crocker wrote:
>2. anyone who thinks the ietf formatting requirements are not easy has
>not had to deal with very interesting formatting requirements.


It may not be difficult but it is not trivial and it may well be beyond
the ability of most non-techies.   In my word-processor (don't ask)
there are two ways to embed form feeds and carriage returns in ASCII
text files.  I never even knew this.  I had to consult the gurus on
the ap's discussion list to get the details.  I still have to review,
test, view the resulting files in DEBUG, and finally format.  This is
MANY hours of work.

Not complaining, just so let it be written.

Jeffrey Race




From owner-ietf@ietf.org  Wed Apr 23 11:28:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23287;
	Wed, 23 Apr 2003 11:28:26 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198MQN-0003YC-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 11:44:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198MLU-00034S-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 11:39:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22964
	for <ietf@ietf.org>; Wed, 23 Apr 2003 11:17:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198M2S-0004k1-00
	for ietf@ietf.org; Wed, 23 Apr 2003 11:20:00 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 198M2R-0004jW-00
	for ietf@ietf.org; Wed, 23 Apr 2003 11:19:59 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003042311245009228
 for <ietf@ietf.org>; Wed, 23 Apr 2003 11:24:50 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 23 Apr 2003 11:17:38 -0400
Message-ID: <3EA6AE92.3020502@centive.com>
Date: Wed, 23 Apr 2003 11:17:38 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
References: <E198LmR-0002rM-00@smtp01.mrf.mail.rcn.net>
In-Reply-To: <E198LmR-0002rM-00@smtp01.mrf.mail.rcn.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Apr 2003 15:17:38.0142 (UTC) FILETIME=[79A4FFE0:01C309AB]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jeffrey Race wrote:

>On Mon, 21 Apr 2003 17:05:32 -0700, Dave Crocker wrote:
>  
>
>>2. anyone who thinks the ietf formatting requirements are not easy has
>>not had to deal with very interesting formatting requirements.
>>    
>>
>It may not be difficult but it is not trivial and it may well be beyond
>the ability of most non-techies.
>
OK, I'm going to say what many of us are thinking:

Sounds like a good filter to me.  Why would we want it non-techies 
writing Internet-Drafts? We already get a lot of borderline stuff; open 
it up to marketroids and we'll be swamped.

Maybe some people in large organizations want to turn their documents 
over to tech writers; but I'm not convinced that's a good idea for 
specs.  The more layers we have between the mind of the person 
implementing the spec and the minds of the people who conceived it, the 
more room there is for bugs to creep in.

-- 
/=============================================================\
|John Stracke      |jstracke@centive.com                      |
|Principal Engineer|http://www.centive.com                    |
|Centive           |My opinions are my own.                   |
|=============================================================|
|For an engineer, paranoia is not an affliction; it's a tool. |
\=============================================================/





From owner-ietf@ietf.org  Wed Apr 23 11:44:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23854;
	Wed, 23 Apr 2003 11:44:07 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198Mgo-00050f-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 12:01:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198MYE-0004jd-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 11:52:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23463
	for <ietf@ietf.org>; Wed, 23 Apr 2003 11:30:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198MFC-0004rg-00
	for ietf@ietf.org; Wed, 23 Apr 2003 11:33:10 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 198MFB-0004rA-00
	for ietf@ietf.org; Wed, 23 Apr 2003 11:33:09 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 64ECB622AF; Wed, 23 Apr 2003 17:33:03 +0200 (CEST)
Date: Wed, 23 Apr 2003 17:33:03 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: alh-ietf@tndh.net, ipng@sunroof.eng.sun.com
Cc: ietf@ietf.org
Subject: Re: A follow up question
Message-ID: <553440000.1051111983@askvoll.hjemme.alvestrand.no>
In-Reply-To: <032a01c309a6$84b1ece0$261e4104@eagleswings>
References:  <032a01c309a6$84b1ece0$261e4104@eagleswings>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On onsdag, april 23, 2003 07:42:08 -0700 Tony Hain <alh-ietf@tndh.net> 
wrote:

> Thank you, this was the only simple answer to the simple question.
>
> For the followup question:
> Do you believe that the IETF created the architectural concept of
> addresses with a limited scope?

no; I believe the community-that-became-the-IETF created the Internet by 
*denying* that concept, which was already well known long before TCP/IP.

Because of the realities of 32 bits of address in IPv4, that denial became 
more and more untenable as the years went by, until RFC 1597 
re-acknowledged the existence of such IPv4 addresses in 1994.

                   Harald




From owner-ietf@ietf.org  Wed Apr 23 12:56:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25947;
	Wed, 23 Apr 2003 12:56:18 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198NmY-0002Dq-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 13:11:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198Nfz-0001qK-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 13:04:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25553
	for <ietf@ietf.org>; Wed, 23 Apr 2003 12:42:55 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198NMw-0005OI-00
	for ietf@ietf.org; Wed, 23 Apr 2003 12:45:14 -0400
Received: from h80ad26b0.async.vt.edu ([128.173.38.176] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 198NMv-0005OF-00
	for ietf@ietf.org; Wed, 23 Apr 2003 12:45:13 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h3NGhWCs019808;
	Wed, 23 Apr 2003 12:43:32 -0400
Message-Id: <200304231643.h3NGhWCs019808@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: John Stracke <jstracke@centive.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Internet Draft Guidelines Require Precise Formatting? 
In-Reply-To: Your message of "Wed, 23 Apr 2003 11:17:38 EDT."
             <3EA6AE92.3020502@centive.com> 
References: <E198LmR-0002rM-00@smtp01.mrf.mail.rcn.net>
            <3EA6AE92.3020502@centive.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_985047191P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 23 Apr 2003 12:43:31 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_985047191P
Content-Type: text/plain; charset=us-ascii

On Wed, 23 Apr 2003 11:17:38 EDT, John Stracke <jstracke@centive.com>  said:

> Sounds like a good filter to me.  Why would we want it non-techies 
> writing Internet-Drafts? We already get a lot of borderline stuff; open 
> it up to marketroids and we'll be swamped.

Is this even an actual problem?  Can anybody point at an actual Good Idea
that didn't get anywhere because of lack of formatting ability?  (Yes, I
sympathize with the original poster's problem, but suspect that it's not as
big a hurdle as expected with the right macro sets for their software).


--==_Exmh_985047191P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+psKzcC3lWbTT17ARAlK3AJsGfcl2abe6VFFc8VJmHb8xmtEAjQCfbU2e
Mof+1Fv9i6qXaVzuSVkuH1A=
=yli8
-----END PGP SIGNATURE-----

--==_Exmh_985047191P--



From owner-ietf@ietf.org  Wed Apr 23 12:56:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25981;
	Wed, 23 Apr 2003 12:56:26 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198NqP-0002gz-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 13:15:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198NqH-0002cZ-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 13:15:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25884
	for <ietf@ietf.org>; Wed, 23 Apr 2003 12:53:32 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198NXD-0005Sr-00
	for ietf@ietf.org; Wed, 23 Apr 2003 12:55:51 -0400
Received: from h80ad26b0.async.vt.edu ([128.173.38.176] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 198NXC-0005So-00
	for ietf@ietf.org; Wed, 23 Apr 2003 12:55:51 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h3NGuECs019952;
	Wed, 23 Apr 2003 12:56:14 -0400
Message-Id: <200304231656.h3NGuECs019952@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Spencer Dawkins <spencer_dawkins@yahoo.com>
Cc: ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A simple question 
In-Reply-To: Your message of "Wed, 23 Apr 2003 05:17:30 PDT."
             <20030423121730.18200.qmail@web10908.mail.yahoo.com> 
References: <20030423121730.18200.qmail@web10908.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_986530465P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 23 Apr 2003 12:56:13 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_986530465P
Content-Type: text/plain; charset=us-ascii

On Wed, 23 Apr 2003 05:17:30 PDT, Spencer Dawkins <spencer_dawkins@yahoo.com>  said:

> This was my point (perhaps I wasn't clear enough) about the
> difference between site-local and firewalling - if your peer
> isn't reachable because of an explicit decision from a network
> operator (firewall), that's one class of problem; if your peer
> isn't reachable because you have an address that doesn't work,
> BUT YOU COULD HAVE BEEN GIVEN ANOTHER ADDRESS THAT WOULD HAVE
> WORKED (site-local), that's a different class of problem.
> 
> The thing that bugs me is, I don't have any idea how the
> application can tell that they have the second class of problem
> - even ignoring ICMP Unreachable black-holing for a moment. Am I
> missing something? (I don't think I'm a Genius of IPv6)

Nope.  That's the problem in a nutshell (almost).  One of the main b0rkedness
in site-local is almost exactly your second case - if your peer isn't reachable
because you've been given a site-local address that doesn't work because it's
mis-scoped, but you could have been given another global address that would
have worked.....

I'm having a hard time thinking of a case where an organization would have
a site-local that worked and global that didn't.  Using our net as an
example, AS1312 has 128.173/16 and 198.82/16.  If we *had* an IPv4 site-local
that covered both nets, I can't see any sensible reason to let those packets
pass, while preventing a host using a 128.173 address from using the 198.82
address of a peer.


--==_Exmh_986530465P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+psWtcC3lWbTT17ARAmF5AJ9pK7tA4qhwLxjmpXFI6Rq7knFbagCgxC57
sbgg91Mj3YLXlAk25sHqCB8=
=7rK8
-----END PGP SIGNATURE-----

--==_Exmh_986530465P--



From owner-ietf@ietf.org  Wed Apr 23 13:18:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26899;
	Wed, 23 Apr 2003 13:18:13 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198O9l-0004cg-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 13:35:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198O5c-0004EE-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 13:31:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26631
	for <ietf@ietf.org>; Wed, 23 Apr 2003 13:09:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198NmY-0005db-00
	for ietf@ietf.org; Wed, 23 Apr 2003 13:11:42 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198NmY-0005dY-00
	for ietf@ietf.org; Wed, 23 Apr 2003 13:11:42 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S260C4> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 23 Apr 2003 10:12:06 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>,
        <ipng@sunroof.eng.sun.com>
Cc: <ietf@ietf.org>
Subject: RE: A follow up question
Date: Wed, 23 Apr 2003 10:12:08 -0700
Message-ID: <035601c309bb$79032750$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <553440000.1051111983@askvoll.hjemme.alvestrand.no>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA26899

Harald Tveit Alvestrand wrote:
> --On onsdag, april 23, 2003 07:42:08 -0700 Tony Hain 
> <alh-ietf@tndh.net> 
> wrote:
> 
> > Thank you, this was the only simple answer to the simple question.
> >
> > For the followup question:
> > Do you believe that the IETF created the architectural concept of 
> > addresses with a limited scope?
> 
> no; I believe the community-that-became-the-IETF created the 
> Internet by 
> *denying* that concept, which was already well known long 
> before TCP/IP.
> 
> Because of the realities of 32 bits of address in IPv4, that 
> denial became 
> more and more untenable as the years went by, until RFC 1597 
> re-acknowledged the existence of such IPv4 addresses in 1994.

Though IP addresses that were only reachable from a limited part of the
network existed long before 1994. These were implicit through filtering
of routing announcements, or explicit through access control mechanisms.
So to clarify the question, do you believe the establishment of a set of
local use prefixes is the root cause of the unsolved problems that
applications developers are complaining about? 

Tony






From owner-ietf@ietf.org  Wed Apr 23 14:37:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29746;
	Wed, 23 Apr 2003 14:37:26 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198PIP-0002Aw-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 14:48:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198PI2-00026i-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 14:48:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29328
	for <ietf@ietf.org>; Wed, 23 Apr 2003 14:26:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198Oyx-0006BJ-00
	for ietf@ietf.org; Wed, 23 Apr 2003 14:28:35 -0400
Received: from garlic.amaranth.net ([208.254.46.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 198Oyx-0006BG-00
	for ietf@ietf.org; Wed, 23 Apr 2003 14:28:35 -0400
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226])
	(authenticated (0 bits))
	by garlic.amaranth.net (8.11.7/8.11.7) with ESMTP id h3NISw809917
	(using TLSv1/SSLv3 with cipher RC4-SHA (128 bits) verified NO);
	Wed, 23 Apr 2003 14:28:58 -0400
Message-Id: <5.2.1.1.2.20030423133826.02ba3f70@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Wed, 23 Apr 2003 14:28:44 -0400
To: <alh-ietf@tndh.net>
From: Daniel Senie <dts@senie.com>
Subject: RE: A follow up question
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
In-Reply-To: <035601c309bb$79032750$261e4104@eagleswings>
References: <553440000.1051111983@askvoll.hjemme.alvestrand.no>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 01:12 PM 4/23/2003, you wrote:
>So to clarify the question, do you believe the establishment of a set of
>local use prefixes is the root cause of the unsolved problems that
>applications developers are complaining about?

There will always be addresses which are administratively scoped, 
regardless of whether those addresses are from global space, or from 
RFC1918 (or equivalent) private space. That scoping will be instituted by 
policy at border routers, firewalls, and even filtering mechanisms on hosts 
(which may be outside the view of the applications, such as how IPTables 
operates on *nix machines.) The IPv6 mechanism to give hosts a-priori 
knowledge that the "site local" block is flawed in that it cannot truly 
provide the scoping information, since it does not address the wider issues 
associated with administrative address scoping. Indeed, the site local 
mechanism reminds me in a way of Steve Bellovin's "evil" bit in his RFC 
published on the first day of this month.

There will remain a need and desire for private address space, be that the 
assigned "site local" block (without the "special treatment" in the 
stacks), RFC 1918 space, or a combination. I think it would be useful to 
decouple the issue of the special treatment of the Site Local address block 
from the religious war over whether private address space and other 
mechanisms sometimes associated are beneficial or not. In reviewing the 
recent discussion, it is clear the two are being intertwined, and it 
appears to be adding to the heat, and producing no light.

Separately, if there is genuine interest in addressing the scoping problem, 
I suggest that be addressed separately. A proper effort might encompass 
mechanisms to deliver indications to applications as to the scoping 
limitations causing communications to be blocked, as well as wire protocol 
issues to carry such signalling. In a broader sense, there is a need to 
deal with signalling issues as well. There are network operators, firewall 
vendors and network administrators who've been taught ICMP packets are 
inherently dangerous and must be filtered. The work output of such efforts 
should span the Internet Area producing standards track documents to 
specify how to properly implement mechanisms in hosts, routers and 
firewalls, and the Operations Area to provide BCPs giving guidance to 
network administrators and service providers on the operational needs of 
such issues.




From owner-ietf@ietf.org  Wed Apr 23 15:31:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03171;
	Wed, 23 Apr 2003 15:31:19 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198QAe-0006VL-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 15:44:44 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198Q9v-0006Qx-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 15:43:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02817
	for <ietf@ietf.org>; Wed, 23 Apr 2003 15:21:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198Pqq-0006ed-00
	for ietf@ietf.org; Wed, 23 Apr 2003 15:24:16 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 198Pqp-0006ea-00
	for ietf@ietf.org; Wed, 23 Apr 2003 15:24:15 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 198Pqy-000Lqq-00; Wed, 23 Apr 2003 14:24:24 -0500
Date: Wed, 23 Apr 2003 15:24:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: Daniel Senie <dts@senie.com>, "alh-ietf@tndh.net" <alh-ietf@tndh.net>
cc: "ietf@ietf.org" <ietf@ietf.org>,
        "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>
Subject: RE: A follow up question
Message-ID: <272103303.1051111464@p3.JCK.COM>
In-Reply-To: <5.2.1.1.2.20030423133826.02ba3f70@mail.amaranth.net>
References: <553440000.1051111983@askvoll.hjemme.alvestrand.no>
 <5.2.1.1.2.20030423133826.02ba3f70@mail.amaranth.net>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Wednesday, 23 April, 2003 14:28 -0400 Daniel Senie 
<dts@senie.com> wrote:

> At 01:12 PM 4/23/2003, you wrote:
>> So to clarify the question, do you believe the establishment
>> of a set of local use prefixes is the root cause of the
>> unsolved problems that applications developers are
>> complaining about?
>
> There will always be addresses which are administratively
> scoped, regardless of whether those addresses are from global
> space, or from RFC1918 (or equivalent) private space. That
> scoping will be instituted by policy at border routers,
> firewalls, and even filtering mechanisms on hosts (which may
> be outside the view of the applications, such as how IPTables
> operates on *nix machines.) The IPv6 mechanism to give hosts
> a-priori knowledge that the "site local" block is flawed in
> that it cannot truly provide the scoping information, since it
> does not address the wider issues associated with
> administrative address scoping. Indeed, the site local
> mechanism reminds me in a way of Steve Bellovin's "evil" bit
> in his RFC published on the first day of this month.

Yes!

> There will remain a need and desire for private address space,
> be that the assigned "site local" block (without the "special
> treatment" in the stacks), RFC 1918 space, or a combination. I
> think it would be useful to decouple the issue of the special
> treatment of the Site Local address block from the religious
> war over whether private address space and other mechanisms
> sometimes associated are beneficial or not. In reviewing the
> recent discussion, it is clear the two are being intertwined,
> and it appears to be adding to the heat, and producing no
> light.

Also Yes.

> Separately, if there is genuine interest in addressing the
> scoping problem, I suggest that be addressed separately. A
> proper effort might encompass mechanisms to deliver
> indications to applications as to the scoping limitations
> causing communications to be blocked, as well as wire protocol
> issues to carry such signalling. In a broader sense, there is
> a need to deal with signalling issues as well. There are
> network operators, firewall vendors and network administrators
> who've been taught ICMP packets are inherently dangerous and
> must be filtered. The work output of such efforts should span
> the Internet Area producing standards track documents to
> specify how to properly implement mechanisms in hosts, routers
> and firewalls, and the Operations Area to provide BCPs giving
> guidance to network administrators and service providers on
> the operational needs of such issues.

Yes!!!!

Tony, I think this pretty well reflects where I've found myself 
going on this, fwiw.   From an applications standpoint, the 
scoping issues, and what is, or is not, "topology information", 
just obscure the problem.  "The problem", from an applications 
point of view, is that, if we are going to stop pretending that 
the address space is completely flat and global --and I agree 
that to do otherwise is unrealistic at this stage-- then we need 
a model by which the application can specify to the stack what 
it needs/ expects, and the stack can tell the application 
whatever the latter really needs to know about what is 
happening.   Of course, to do that, the stack may need to be 
able to pass directions to the network or make inquiries and get 
information back.  But, to the degree to which we believe in 
layered protocol stacks at all (hourglass or otherwise), the 
application should be totally insensitive to where the stack 
layer(s) with which it communicates get their information.

Having the application try to figure this all out by breaking 
down IPv6 addresses (site local or otherwise) just isn't the 
right way to do it --at least without a really drastic 
rethinking of the architecture.   That is partially because of 
the flip side of the arguments I've understood you to be making 
about scope: the application can't know enough in our current 
model to do the right thing, and knowing about how to handle one 
particular address prefix or format won't make a serious dent in 
the problem. ICMP, as now defined and used, won't help with the 
problem for a reason much more pervasive than the one Daniel and 
others have identified: most of our current applications have no 
interaction with either ICMP or IP -- they call on TCP or UDP 
functions and don't know about the internet layer.  The Internet 
layer doesn't have any path (by "signalling" or otherwise)to 
pass information back to the apps.

So, I would suggest that we really do have a problem here. 
Unless we have a realistic proposal for a routing fabric that is 
not dependent on the addresses used, the solution-set almost 
certainly includes being able to use multiple addresses per 
host, with different semantics associated with those addresses. 
As the competence level of the average ISP declines (which seems 
to have been a clear trend for the last several years), 
multihoming (in some form) needs to increase as the only 
satisfactory alternative... and it better not be only for the 
rich or the huge.  The idea of a single, exclusively-global, 
flat address space has been history for years; we clearly aren't 
going to get back there as long as different providers charge 
differently for different paths (independent of any of the 
enterprise localization, firewall, RIR-granted PI space, or 
other issues).

But, unless we are prepared to discard the model of a layered 
stack architecture, or accept our applications becoming as (or 
more) complex and knowledgeable about network architectures as 
switches get in the PSTN, then we should be looking at stack 
abstractions that permit applications to express their needs, 
and get information back, without deducing network topology, 
transport or mobility economics, etc.  Maybe that  to get there 
means that we need to revisit, not just ICMP as Daniel suggests, 
but the "no TCPng" decision... I don't know.  But, if we can 
figure out a way to clean this up and make it work well, we 
could easily end up with a stronger justification for deploying 
IPv6 than anything (at least anything real) we have had to date.

Where does SL and its relationship to applications fit into 
this?  Oddly, I don't think it does except in the very useful 
sense of having (finally) forced a broader range of people to 
think about the problem.   From an application-writer/designer 
standpoint, I know I don't want to think about SL (nor do I want 
to think about RFC 1918 addresses or anything else that requires 
me to make decisions I don't have the needed information to 
make).  I'm not opposed to those addresses existing, or in favor 
of them, I'm just committed to a network and implementation 
model in which they are kept below me in the stack. 
Consequently, the only thing I want to need to know about an IP 
address is how to pick it up from one source, carry it around 
opaquely, and ultimately pass it to something else or use it in 
an opaque way in a protocol transaction.  The challenge to those 
of you who are for, or against, SL at the IP level is to justify 
it in a context in which applications really don't need to know 
anything about them, or other address scope/ reachability/ 
routability issues except through the addressing-independent 
abstractions that we can agree on.  If the applications don't 
need to know, and can function in a multiple-address-per-host 
environment without --in the application-- having to determine 
which one to use by some type of iteration process, then you 
need to justify specialized addresses only in terms of their 
requires lower in the stack.  If the applications do need to 
know, then the complexity costs appear to be high enough to 
present an insurmountable barrier.

  regards,
        john




From owner-ietf@ietf.org  Wed Apr 23 15:31:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03178;
	Wed, 23 Apr 2003 15:31:19 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198QCX-0006dk-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 15:46:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198QAp-0006VN-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 15:44:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02840
	for <ietf@ietf.org>; Wed, 23 Apr 2003 15:22:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198Prk-0006eq-00
	for ietf@ietf.org; Wed, 23 Apr 2003 15:25:12 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198Prj-0006en-00
	for ietf@ietf.org; Wed, 23 Apr 2003 15:25:12 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S260F5> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 23 Apr 2003 12:25:36 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Daniel Senie'" <dts@senie.com>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
Subject: RE: A follow up question
Date: Wed, 23 Apr 2003 12:25:29 -0700
Message-ID: <036f01c309ce$19def160$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <5.2.1.1.2.20030423133826.02ba3f70@mail.amaranth.net>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA03178

Daniel Senie wrote:
> ... The IPv6 mechanism to give hosts a-priori 
> knowledge that the "site local" block is flawed in that it 
> cannot truly 
> provide the scoping information, since it does not address 
> the wider issues 
> associated with administrative address scoping. 

You assume an outcome ('flawed') without first discussing the full set
of requirements. 

> ...
> There will remain a need and desire for private address 
> space, be that the 
> assigned "site local" block (without the "special treatment" in the 
> stacks), RFC 1918 space, or a combination. I think it would 
> be useful to 
> decouple the issue of the special treatment of the Site Local 
> address block 
> from the religious war over whether private address space and other 
> mechanisms sometimes associated are beneficial or not. In 
> reviewing the 
> recent discussion, it is clear the two are being intertwined, and it 
> appears to be adding to the heat, and producing no light.

I have no argument with discussing them separately, as long as we don't
end up with the usual discussion where it is the private address space
causing the problems. There is a general lack of recognition that
private addresses only exposes the underlying mis-match in the
perceptions of scope. 

> 
> Separately, if there is genuine interest in addressing the 
> scoping problem, 
> I suggest that be addressed separately. 

Reset your clocks to 1995 ...

> A proper effort might encompass 
> mechanisms to deliver indications to applications as to the scoping 
> limitations causing communications to be blocked, as well as 
> wire protocol 
> issues to carry such signalling. 

You assume such signaling would somehow solve the problem of A using a
literal referral to C that Bl is the address it is using, when C can
only see Bg. How is A supposed to know that Bl has a scope limitation
when it can get there without receiving any signaling? How is the
infrastructure supposed to know that A intends to tell C a literal
address rather than a name? If Bl & Bg had indicators of scope
differentiation in the prefix, A could recognize the difference if it
bothered to look. It wouldn't have to, but if it didn't it would either
have to refer the name, or provide C with the entire list so it could
figure out which one works. Brian's C000 thread was exploring this
space. 

> In a broader sense, there is a need to 
> deal with signalling issues as well. There are network 
> operators, firewall 
> vendors and network administrators who've been taught ICMP 
> packets are 
> inherently dangerous and must be filtered. The work output of 
> such efforts 
> should span the Internet Area producing standards track documents to 
> specify how to properly implement mechanisms in hosts, routers and 
> firewalls, and the Operations Area to provide BCPs giving guidance to 
> network administrators and service providers on the 
> operational needs of 
> such issues.
> 

I agree education is appropriate. Part of that is educating the
application development community that the real network has addressing
with limited scopes of relevance, so blindly assuming a flat routing
space and passing around topology specific information will result in
broken apps.

Tony





From owner-ietf@ietf.org  Wed Apr 23 15:31:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03170;
	Wed, 23 Apr 2003 15:31:19 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198QCY-0006dq-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 15:46:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198QBM-0006VP-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 15:45:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02850
	for <ietf@ietf.org>; Wed, 23 Apr 2003 15:23:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198PsG-0006ey-00
	for ietf@ietf.org; Wed, 23 Apr 2003 15:25:44 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198PsG-0006ev-00
	for ietf@ietf.org; Wed, 23 Apr 2003 15:25:44 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3NJQ7v27514;
        Wed, 23 Apr 2003 15:26:08 -0400 (EDT)
Date: Wed, 23 Apr 2003 15:26:07 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Spencer Dawkins <spencer_dawkins@yahoo.com>
Cc: moore@cs.utk.edu, ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A simple question
Message-Id: <20030423152607.79be279e.moore@cs.utk.edu>
In-Reply-To: <20030423121730.18200.qmail@web10908.mail.yahoo.com>
References: <20030422231209.438176f7.moore@cs.utk.edu>
	<20030423121730.18200.qmail@web10908.mail.yahoo.com>
X-Mailer: Sylpheed version 0.8.11 (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 would be thrilled if we spent some time thinking about ICMP in
> an architectural way - however beautiful it was before ICMP
> black holing, what we have now isn't consistently usable today.
> We're spending time on point solutions (Matt Mathis on non-ICMP
> path MTU discovery as one example), but is this the best we can
> do?

I don't think we're likely to be able to dispense with ICMP.  Maybe we
can find more ways to make it more trustworthy.  Or maybe we just need
to discourage people from filtering it.


> > Note that scoped addresses make it difficult for each of the
> > network, hosts, and apps to do  their jobs - the network can't tell
> > whether it can get the traffic to the destination because the
> > destination address is ambiguous (so for instance, how can it tell
> > the difference between "prohibited" and "no route to destination"
> > and "no such host" - and while it might have unambiguous rules for
> > how to route such addresses, that doesn't mean the traffic went to
> > the right place); hosts can't tell which interface to use to send
> > the traffic; and apps can't tell whether or not the address is
> > usable to reach the desired peer (either locally or by another
> > peer).
> 
> This was my point (perhaps I wasn't clear enough) about the
> difference between site-local and firewalling - if your peer
> isn't reachable because of an explicit decision from a network
> operator (firewall), that's one class of problem; if your peer
> isn't reachable because you have an address that doesn't work,
> BUT YOU COULD HAVE BEEN GIVEN ANOTHER ADDRESS THAT WOULD HAVE
> WORKED (site-local), that's a different class of problem.
> 
> The thing that bugs me is, I don't have any idea how the
> application can tell that they have the second class of problem
> - even ignoring ICMP Unreachable black-holing for a moment. Am I
> missing something? (I don't think I'm a Genius of IPv6)

What I want to say is that if the peer isn't reachable because the
host or application didn't choose the right source or destination
address, this is never the host or the application's problem - it's
always the network's problem - because I don't see any way to allow 
hosts and apps to reliably make the "right choice" in the absence of
routing information, and which allows addresses to be used in referrals.
(and while separating endpoint identifiers from addresses might be a
laudible architectural goal, we're nowhere near being able to integrate
it into the current archtitecture).

> > Now, because of mobile IP and privacy addresses, we're still going
> > to have situations where apps need to give their hosts an idea of
> > what kinds of addresses they need.  E.g. Does the app need an
> > address that continues to work as the host moves, or will the
> > in-care-of address do?  Does it prefer an address that is stably
> > associated with the host, or is a temporary address more
> > appropriate?  But the answers to both of these questions *are*
> > things that the app can be expected to know.  Furthermore, unlike
> > service quality or security, these things inherently require address
> > selection.  And unlike site-local, these properties are essentially
> > opaque to other hosts in the network - thus we cannot expect/demand
> > that other hosts use information  embedded in the address and behave
> > differently for different kinds of addresses.  
> 
> From RFC 3344, the current Mobile IP spec:
> 
> 1.1. Protocol Requirements
> 
> [deleted down to]
> 
>    A mobile node must be able to communicate with other nodes
> that do not implement these mobility functions.  No protocol
> enhancements are required in hosts or routers that are not acting as
> any of the new architectural entities introduced in Section 1.5. 
> 
> And I agree I'm extrapolating, but - I always thought language
> like this said Mobile IP is a host IP networking thing, not a
> host application thing.
> 
> I'm not sure I'm understanding what you're saying - are you
> saying that my mobile host should know it's mobile (I believe
> you), or that Mozilla on a mobile host should know it's mobile
> (I'm struggling here)?

I'm saying that if your application knows that a particular connection
is only likely to be open for a short time, and/or that it can reliably
recover from broken connections, and that the source address isn't going
to be used for referrals to peers on other hosts, then it might want to
somehow tell its TCP/IP stack this, so the stack can use the in-care-of
address as the source address rather than the home address, thereby
bypassing any tunneling that might otherwise take place.  

Which isn't quite the same thing as letting an app know it's on a mobile
host - though that would also be useful for some apps.  

> My understanding of Mobile IP was that the mobile host knows,
> not Mozilla (or, at least, Mozilla works if it doesn't know).
> 
> Re: security - are you thinking of applications that prefer
> site-local (in IPv4, probably NATed 1918 addresses) for
> "security", or is there another common use of
> addresses-for-security I don't know about?

I don't think address selection is an appropriate means for an
application to specify security.  That's what IPsec and/or TLS are
for.  (and yes, we need IPsec APIs)  

nor do I think that an application should invest greater or less trust
in traffic that is sourced from or sunk to a particular address, at
least not without specifically being configured to do so, and certainly
not based on whether the address is site-local.

Keith



From owner-ietf@ietf.org  Wed Apr 23 16:00:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04517;
	Wed, 23 Apr 2003 16:00:34 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198QgZ-0001mV-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 16:17:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198QfC-0001cw-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 16:16:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04352
	for <ietf@ietf.org>; Wed, 23 Apr 2003 15:54:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198QM6-0006zA-00
	for ietf@ietf.org; Wed, 23 Apr 2003 15:56:34 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198QM6-0006z7-00
	for ietf@ietf.org; Wed, 23 Apr 2003 15:56:34 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26101> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 23 Apr 2003 12:56:58 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'John C Klensin'" <john-ietf@jck.com>, "'Daniel Senie'" <dts@senie.com>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
Subject: RE: A follow up question
Date: Wed, 23 Apr 2003 12:56:47 -0700
Message-ID: <037501c309d2$7986ded0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <272103303.1051111464@p3.JCK.COM>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA04517

John C Klensin wrote:
> ... Maybe that  to get there 
> means that we need to revisit, not just ICMP as Daniel suggests, 
> but the "no TCPng" decision... I don't know. 

Maybe that is the path out. 

>  But, if we can 
> figure out a way to clean this up and make it work well, we 
> could easily end up with a stronger justification for deploying 
> IPv6 than anything (at least anything real) we have had to date.

Depends on where you are in the world, and how much IPv4 address space
you are sitting on. I am aware of organizations in the US today that
can't get enough IPv4 address space fast enough by current ARIN policy
to meet a viable business plan for ramp up rate. 

> ... I'm just committed to a network and implementation 
> model in which they are kept below me in the stack. 
> Consequently, the only thing I want to need to know about an IP 
> address is how to pick it up from one source, carry it around 
> opaquely, and ultimately pass it to something else or use it in 
> an opaque way in a protocol transaction. 

But you just said you wanted to keep it below you in the stack. You
can't have it both ways... You either get to keep it below you by
passing around name objects, or you are taking on the responsibility of
getting it right because you are passing around topology information.

>  The challenge to those 
> of you who are for, or against, SL at the IP level is to justify 
> it in a context in which applications really don't need to know 
> anything about them, or other address scope/ reachability/ 
> routability issues except through the addressing-independent 
> abstractions that we can agree on.  

I don't care if it is TCP-ng, or something else between IP & the app
that takes care of figuring out the topology difference, but signaling
by itself won't solve the problem of literal referrals. If the app is
going to insist on passing around topology information, it has to make
sure that matches the topology being used.

> If the applications don't 
> need to know, and can function in a multiple-address-per-host 
> environment without --in the application-- having to determine 
> which one to use by some type of iteration process, then you 
> need to justify specialized addresses only in terms of their 
> requires lower in the stack.  If the applications do need to 
> know, then the complexity costs appear to be high enough to 
> present an insurmountable barrier.

The current IPv4 network already requires this of applications, the
developers simply choose to ignore reality. There is nothing different
in a unique prefix for local use, other than the ability for the app
(stack) that chooses to look to figure out that some pairings won't
work. If the app does as it currently will and passes an out-of-scope
address, the application will fail. This is not a new requirement, it is
simply exposing the fact that applications have been ignoring reality
for a long time now. If there are other ways to mitigate the issue, I am
all for developing them. My primary issue is that there are a variety of
things people want to use SL for and removing an existing mechanism
without appropriate replacements for all of them first is an
irresponsible act.

Tony






From owner-ietf@ietf.org  Wed Apr 23 16:53:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06651;
	Wed, 23 Apr 2003 16:53:32 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198RWo-00063U-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 17:11:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198RUJ-0005qb-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 17:09:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06439
	for <ietf@ietf.org>; Wed, 23 Apr 2003 16:47:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198RBD-0007Jo-00
	for ietf@ietf.org; Wed, 23 Apr 2003 16:49:23 -0400
Received: from tomts24.bellnexxia.net ([209.226.175.187] helo=tomts24-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198RBC-0007Jh-00
	for ietf@ietf.org; Wed, 23 Apr 2003 16:49:22 -0400
Received: from yahoo.com ([65.93.183.135]) by tomts24-srv.bellnexxia.net
          (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP
          id <20030423204948.KOAM1119.tomts24-srv.bellnexxia.net@yahoo.com>;
          Wed, 23 Apr 2003 16:49:48 -0400
Date: Wed, 23 Apr 2003 16:49:48 -0400
Subject: Re: A follow up question
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "ietf@ietf.org" <ietf@ietf.org>,
        "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>
To: John C Klensin <john-ietf@jck.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <272103303.1051111464@p3.JCK.COM>
Message-Id: <1F5B7ACE-75CD-11D7-89E4-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Wednesday, April 23, 2003, at 03:24  PM, John C Klensin wrote:

>  As the competence level of the average ISP declines (which seems to 
> have been a clear trend for the last several years), multihoming (in 
> some form) needs to increase as the only satisfactory alternative... 
> and it better not be only for the rich or the huge.

Yes!

Speaking from the Community Wireless Networking perspective, massive 
multihoming is a really good thing not just because of the problems 
with ISPs but because it's the most /appropriate/ (not necessarily 
easiest to wrap mind around) solution to the classic problem of CWN: I 
have this mesh of fixed homes with various antennas on their roofs 
pointing at each other ... some of them have ISP accounts some don't 
... how do I start routing traffic through there from internal nodes to 
other internal nodes, or from inside to outside and vice-versa???

(a current solution using NAT (meshAP/locustworld) is not the answer 
... various tunnelling methods would squander bandwidth)

simon




From owner-ietf@ietf.org  Wed Apr 23 17:03:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07259;
	Wed, 23 Apr 2003 17:03:47 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198RfX-0006lp-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 17:20:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198RZt-0006CQ-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 17:14:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06619
	for <ietf@ietf.org>; Wed, 23 Apr 2003 16:52:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198RGn-0007MM-00
	for ietf@ietf.org; Wed, 23 Apr 2003 16:55:09 -0400
Received: from web10907.mail.yahoo.com ([216.136.131.43])
	by ietf-mx with smtp (Exim 4.12)
	id 198RGm-0007MF-00
	for ietf@ietf.org; Wed, 23 Apr 2003 16:55:08 -0400
Message-ID: <20030423205534.67678.qmail@web10907.mail.yahoo.com>
Received: from [12.237.229.250] by web10907.mail.yahoo.com via HTTP; Wed, 23 Apr 2003 13:55:34 PDT
Date: Wed, 23 Apr 2003 13:55:34 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
Subject: Re: A simple question
To: ietf@ietf.org, ipng@sunroof.eng.sun.com
In-Reply-To: <20030423152607.79be279e.moore@cs.utk.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

OK, I AM intrigued by this:

--- Keith Moore <moore@cs.utk.edu> wrote:
> 
> I don't think we're likely to be able to dispense with ICMP. 
> Maybe we
> can find more ways to make it more trustworthy.  Or maybe we
> just need
> to discourage people from filtering it.

Any thoughts on the effectiveness of a BCP that says, message
type by message type and return code by return code, "filtering
this at a network edge does/does not make sense"?

We've been digging our toes in the sand on a Phil Karn proposal
to do TCP far-end link-up notification via retransmitted TCP
packets (for a few years). Architecturally, this is the kind of
thing ICMP is meant for, but I'm told repeatedly that new
ICMP-based mechanisms are non-starters on today's network...

Spencer



From owner-ietf@ietf.org  Wed Apr 23 17:03:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07270;
	Wed, 23 Apr 2003 17:03:48 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198Rfb-0006oT-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 17:20:47 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198Rc2-0006YH-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 17:17:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06845
	for <ietf@ietf.org>; Wed, 23 Apr 2003 16:55:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198RIw-0007PJ-00
	for ietf@ietf.org; Wed, 23 Apr 2003 16:57:22 -0400
Received: from shell.nominum.com ([128.177.192.160])
	by ietf-mx with esmtp (Exim 4.12)
	id 198RIv-0007O8-00
	for ietf@ietf.org; Wed, 23 Apr 2003 16:57:22 -0400
Received: from nominum.com (shell.nominum.com [128.177.192.160])
	by shell.nominum.com (Postfix) with ESMTP
	id 2C215137F0D; Wed, 23 Apr 2003 13:57:17 -0700 (PDT)
Date: Wed, 23 Apr 2003 13:57:13 -0700
Subject: Re: A follow up question
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "'John C Klensin'" <john-ietf@jck.com>, "'Daniel Senie'" <dts@senie.com>,
        <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
To: <alh-ietf@tndh.net>
From: David Conrad <david.conrad@nominum.com>
In-Reply-To: <037501c309d2$7986ded0$261e4104@eagleswings>
Message-Id: <2863E712-75CE-11D7-A3E0-000393DB42B2@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony,

On Wednesday, April 23, 2003, at 12:56  PM, Tony Hain wrote:
> I am aware of organizations in the US today that
> can't get enough IPv4 address space fast enough by current ARIN policy
> to meet a viable business plan for ramp up rate.

As this would appear to be an indication of a failure of allocation 
policy, a discussion of details on an appropriate list (ppml@arin.net 
would probably be best) would be appreciated.

Rgds,
-drc




From owner-ietf@ietf.org  Wed Apr 23 18:06:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10268;
	Wed, 23 Apr 2003 18:06:37 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198SdW-0005Im-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 18:22:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198SZw-0004HF-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 18:19:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09610
	for <ietf@ietf.org>; Wed, 23 Apr 2003 17:56:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198SGp-0000DR-00
	for ietf@ietf.org; Wed, 23 Apr 2003 17:59:15 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198SGp-0000DO-00
	for ietf@ietf.org; Wed, 23 Apr 2003 17:59:15 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3NLxbv28151;
        Wed, 23 Apr 2003 17:59:40 -0400 (EDT)
Date: Wed, 23 Apr 2003 17:59:37 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: Architectural Considerations section in specs
Message-Id: <20030423175937.3b28f432.moore@cs.utk.edu>
In-Reply-To: <033901c309a9$45d0f130$261e4104@eagleswings>
References: <70125434335.20030419164712@brandenburg.com>
	<033901c309a9$45d0f130$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (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

> What they are missing is that a defined prefix doesn't create the
> problem that they are complaining about. Limiting the usable scope of
> addresses is an operations decision. 

Tony, this discussion is about ambiguous addresses.  Your persistent
attempt to conflate it with packet filtering and/or routing policy isn't
shedding any light on the argument.  And you're smart enough to know
the difference.

> Defining a prefix for those only made it *possible* for apps to
> recognize which ones might be restricted.

But it doesn't help apps know *how* those addresses are restricted.

>  It does not *make* apps deal
> with the problem of leaking addresses outside their scope of relevance
> (unless you take the viewpoint that end users actually expect
> applications to work right, and will require it once it is possible).

Experience indicates that this is exactly what happens.  You cannot
expect apps to not leak addresses outside of their scope because apps do
need to pass addresses around and they have no way of being aware of
their scope boundaries.  The way to solve this problem is to make
addresses unique.

> Applications are not required to understand topology, unless and until
> they insist on passing around topology specific information. 

Another attempt at disinformation on your part.  The fact that the
current internet architecture doesn't provide us with reliable endpoint
identifiers that are independent of topology information is not a
justification for asserting that applications should not pass around the
best endpoint identifiers that are available to them.  And very few
applications use these as anything other than opaque tokens.

> There is no magic here, and defining a prefix didn't change the
> architecture. 

defining a prefix didn't change the architecture - asserting that the
same prefix could be reused in multiple locations did change the
architecture.

> Operational decisions established the architecture, and
> it is our job to define the technologies that work within that
> architectural reality.

indeed.  this is precisely why we are deprecating site locals - because
they do not work within the architectural reality.

Keith




From owner-ietf@ietf.org  Wed Apr 23 18:09:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10746;
	Wed, 23 Apr 2003 18:09:34 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198SiO-0000FX-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 18:27:44 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198Sha-0008Pw-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 18:26:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10049
	for <ietf@ietf.org>; Wed, 23 Apr 2003 18:04:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198SOT-0000Gm-00
	for ietf@ietf.org; Wed, 23 Apr 2003 18:07:09 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198SOS-0000Gj-00
	for ietf@ietf.org; Wed, 23 Apr 2003 18:07:08 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3NM7Vv28177;
        Wed, 23 Apr 2003 18:07:31 -0400 (EDT)
Date: Wed, 23 Apr 2003 18:07:31 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, john-ietf@jck.com, dts@senie.com, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
Message-Id: <20030423180731.4137efe7.moore@cs.utk.edu>
In-Reply-To: <037501c309d2$7986ded0$261e4104@eagleswings>
References: <272103303.1051111464@p3.JCK.COM>
	<037501c309d2$7986ded0$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (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

> If the app is
> going to insist on passing around topology information, it has to make
> sure that matches the topology being used.

agreed.  and by far the easiest way to do this is to have all points on
the network use consistent names for points in the network topology.

the real problem is that people have been conditioned to believe that
ambiguous addresses are a security feature, when what this actually
serves to do is reduce their ability to apply security in depth.

> > If the applications don't 
> > need to know, and can function in a multiple-address-per-host 
> > environment without --in the application-- having to determine 
> > which one to use by some type of iteration process, then you 
> > need to justify specialized addresses only in terms of their 
> > requires lower in the stack.  If the applications do need to 
> > know, then the complexity costs appear to be high enough to 
> > present an insurmountable barrier.
> 
> The current IPv4 network already requires this of applications, the
> developers simply choose to ignore reality. 

until recently 'reality' was that the vast majority of ipv4 hosts had
only one network interface, and one address, and most of the rest
of the hosts could act as if they only had one interface and one
address.  so application writers were paying attention to reality, even
if they weren't handling (or able to handle) every case that might
potentially arise.

> My primary issue is that there
> are a variety of things people want to use SL for and removing an
> existing mechanism without appropriate replacements for all of them
> first is an irresponsible act.

we need a list of these things, so we can work on a list of
replacements.

Keith



From owner-ietf@ietf.org  Wed Apr 23 18:14:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11428;
	Wed, 23 Apr 2003 18:14:40 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198SoB-000302-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 18:33:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198SmL-000244-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 18:31:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10782
	for <ietf@ietf.org>; Wed, 23 Apr 2003 18:09:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198STE-0000L0-00
	for ietf@ietf.org; Wed, 23 Apr 2003 18:12:04 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198STD-0000Kx-00
	for ietf@ietf.org; Wed, 23 Apr 2003 18:12:03 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3NMCRv28184;
        Wed, 23 Apr 2003 18:12:27 -0400 (EDT)
Date: Wed, 23 Apr 2003 18:12:27 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, dts@senie.com, ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
Message-Id: <20030423181227.62fec8c7.moore@cs.utk.edu>
In-Reply-To: <036f01c309ce$19def160$261e4104@eagleswings>
References: <5.2.1.1.2.20030423133826.02ba3f70@mail.amaranth.net>
	<036f01c309ce$19def160$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (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 agree education is appropriate. Part of that is educating the
> application development community that the real network has addressing
> with limited scopes of relevance, so blindly assuming a flat routing
> space and passing around topology specific information will result in
> broken apps.

This is ridiculous.  Tony, we understand that we don't have a
completely connected network.  We've understood that for years. 
But we're not willing to adopt your delusions that this is the same
problem as having ambiguous addresses.

Keith





From owner-ietf@ietf.org  Wed Apr 23 18:55:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12695;
	Wed, 23 Apr 2003 18:55:49 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198TL5-0007Dl-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 19:07:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198TKM-00079H-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 19:06:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12415
	for <ietf@ietf.org>; Wed, 23 Apr 2003 18:44:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198T1F-0000ZP-00
	for ietf@ietf.org; Wed, 23 Apr 2003 18:47:13 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198T1E-0000ZM-00
	for ietf@ietf.org; Wed, 23 Apr 2003 18:47:12 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S2614B> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 23 Apr 2003 15:47:37 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
Subject: RE: Architectural Considerations section in specs
Date: Wed, 23 Apr 2003 15:47:37 -0700
Message-ID: <038d01c309ea$56859c60$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030423175937.3b28f432.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA12695

Keith Moore wrote:
> Tony, this discussion is about ambiguous addresses.  Your 
> persistent attempt to conflate it with packet filtering 
> and/or routing policy isn't shedding any light on the 
> argument.  And you're smart enough to know the difference.

Yes, but you keep changing the argument. On 4/18 it was:
>> introduction of scoped addresses causes far more problems than it
solves.

Today it is ambiguity. I was trying to separate the discussion by
focusing explicitly on the scoped address issue. 

> 
> > Defining a prefix for those only made it *possible* for apps to 
> > recognize which ones might be restricted.
> 
> But it doesn't help apps know *how* those addresses are restricted.

No, but a limited hint is useful in many situations. Should we have
better tools? By all means. That does not mean we get rid of something
that has some utility before we show that it has none because there are
alternatives.

> 
> >  It does not *make* apps deal
> > with the problem of leaking addresses outside their scope 
> of relevance 
> > (unless you take the viewpoint that end users actually expect 
> > applications to work right, and will require it once it is 
> possible).
> 
> Experience indicates that this is exactly what happens.  You 
> cannot expect apps to not leak addresses outside of their 
> scope because apps do need to pass addresses around and they 
> have no way of being aware of their scope boundaries.  The 
> way to solve this problem is to make addresses unique.

I do not buy the assertion that 'apps need to pass addresses around'. It
is possible for apps to choose passing around names and let the topology
get sorted out by the name resolution infrastructure. As I said to JCK,
you can't have it both ways. You can either choose to keep it all below
the app layer by passing around names, or if the app chooses to reach
down and get topology information it has bought into the responsibility
to understand what it is doing.

> 
> > Applications are not required to understand topology, 
> unless and until 
> > they insist on passing around topology specific information.
> 
> Another attempt at disinformation on your part.  The fact 
> that the current internet architecture doesn't provide us 
> with reliable endpoint identifiers that are independent of 
> topology information is not a justification for asserting 
> that applications should not pass around the best endpoint 
> identifiers that are available to them.  And very few 
> applications use these as anything other than opaque tokens.

You insist on the right to reach down and get lower layer information,
but refuse to accept the responsibility that goes along with having it.
??? If the app chose to use a name as the endpoint identifier, it would
have the conflict.

> 
> > There is no magic here, and defining a prefix didn't change the 
> > architecture.
> 
> defining a prefix didn't change the architecture - asserting 
> that the same prefix could be reused in multiple locations 
> did change the architecture.

This is more an argument to define ways to disambiguate the current
space than it is to remove a well-known prefix for use in local scopes.
Get your arguments straight, and you will realize all this deprecate SL
nonsense is a waste of time. We need to solve the fact that apps refuse
to acknowledge they are ignoring topological reality, and the ambiguity
argument become simply a matter of subnet routing collisions during
mergers.

> 
> > Operational decisions established the architecture, and
> > it is our job to define the technologies that work within that 
> > architectural reality.
> 
> indeed.  this is precisely why we are deprecating site locals 
> - because they do not work within the architectural reality.

No, the apps that insist on reaching down and getting lower layer
information that they don't understand is what doesn't work. Deprecating
SL makes absolutely no difference to this, because the same issues will
crop up for globally unique local scope addresses. Before you say it,
the 'connect to the wrong node' argument is an IPv4 artifact. With IPv6
auto-conf, or even manual conf using a discarded MAC, the probability of
a SL address actually pointing to two nodes is close to zero, and even
lower than that for those both being reachable from participants in the
same multi-party app. 

Go back through all your arguments about the evil's of SL, and see how
many go away if the prefix is disambiguated. Then look at the fact that
A can't tell C the difference between Bl & Bg unless there is some
indicator. 

Tony






From owner-ietf@ietf.org  Wed Apr 23 18:56:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12793;
	Wed, 23 Apr 2003 18:56:46 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198TSy-0007iK-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 19:15:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198TOH-0007JD-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 19:11:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12472
	for <ietf@ietf.org>; Wed, 23 Apr 2003 18:48:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198T5A-0000aO-00
	for ietf@ietf.org; Wed, 23 Apr 2003 18:51:16 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198T59-0000aL-00
	for ietf@ietf.org; Wed, 23 Apr 2003 18:51:16 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S2614D> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 23 Apr 2003 15:51:40 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <john-ietf@jck.com>, <dts@senie.com>, <ietf@ietf.org>,
        <ipng@sunroof.eng.sun.com>
Subject: RE: A follow up question
Date: Wed, 23 Apr 2003 15:51:40 -0700
Message-ID: <038e01c309ea$e7927c00$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030423180731.4137efe7.moore@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:
> ...
> we need a list of these things, so we can work on a list of 
> replacements.

I am accepting comments for:
http://www.ietf.org/internet-drafts/draft-hain-ipv6-sitelocal-00.txt

Tony





From owner-ietf@ietf.org  Wed Apr 23 18:59:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13165;
	Wed, 23 Apr 2003 18:59:49 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198TSz-0007iV-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 19:15:53 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198TOj-0007JI-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 19:11:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12486
	for <ietf@ietf.org>; Wed, 23 Apr 2003 18:49:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198T5b-0000ao-00
	for ietf@ietf.org; Wed, 23 Apr 2003 18:51:43 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 198T5b-0000ag-00
	for ietf@ietf.org; Wed, 23 Apr 2003 18:51:43 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3NMppL09787;
	Wed, 23 Apr 2003 17:51:51 -0500
Message-ID: <001d01c309ea$eeb87890$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <alh-ietf@tndh.net>, "'Daniel Senie'" <dts@senie.com>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
References: <036f01c309ce$19def160$261e4104@eagleswings>
Subject: Re: A follow up question
Date: Wed, 23 Apr 2003 17:44:31 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Tony Hain" <alh-ietf@tndh.net>
> If Bl & Bg had indicators of scope differentiation in the prefix, A could
> recognize the difference if it bothered to look. It wouldn't have to, but
> if it didn't it would either have to refer the name, or provide C with the
> entire list so it could figure out which one works. Brian's C000 thread
> was exploring this space.

"Global" addresses can be scoped by administrative/security devices just as
easily as non-globals, so a scope indicator in the address is merely a hint
which may lead the app/stack astray.  The only way to determine if a given
address, global or otherwise, will work is to try using it.

SL does not solve -- nor did it create -- this problem any more than RFC1597
did.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Wed Apr 23 19:00:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13222;
	Wed, 23 Apr 2003 19:00:17 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198TT6-0007la-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 19:16:00 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198TQ9-0007RQ-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 19:12:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12511
	for <ietf@ietf.org>; Wed, 23 Apr 2003 18:50:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198T72-0000bQ-00
	for ietf@ietf.org; Wed, 23 Apr 2003 18:53:12 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198T71-0000bN-00
	for ietf@ietf.org; Wed, 23 Apr 2003 18:53:11 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26150> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 23 Apr 2003 15:53:36 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <dts@senie.com>, <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
Subject: RE: A follow up question
Date: Wed, 23 Apr 2003 15:53:36 -0700
Message-ID: <038f01c309eb$2cc8af60$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030423181227.62fec8c7.moore@cs.utk.edu>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:
> > I agree education is appropriate. Part of that is educating the 
> > application development community that the real network has 
> addressing 
> > with limited scopes of relevance, so blindly assuming a 
> flat routing 
> > space and passing around topology specific information will 
> result in 
> > broken apps.
> 
> This is ridiculous.  Tony, we understand that we don't have a 
> completely connected network.  We've understood that for years. 
> But we're not willing to adopt your delusions that this is 
> the same problem as having ambiguous addresses.

I am focusing on your 4/18 assertion: introduction of scoped addresses
causes far more problems than it solves.

I am not talking at all about ambiguity.

Tony




From owner-ietf@ietf.org  Wed Apr 23 19:28:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14076;
	Wed, 23 Apr 2003 19:28:27 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198Tuq-0002Td-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 19:44:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198TtB-0002Nl-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 19:42:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13896
	for <ietf@ietf.org>; Wed, 23 Apr 2003 19:20:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198Ta3-0000uB-00
	for ietf@ietf.org; Wed, 23 Apr 2003 19:23:11 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 198Ta3-0000u8-00
	for ietf@ietf.org; Wed, 23 Apr 2003 19:23:11 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3NNNYL10478;
	Wed, 23 Apr 2003 18:23:34 -0500
Message-ID: <002701c309ef$5c64ced0$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Keith Moore" <moore@cs.utk.edu>, <alh-ietf@tndh.net>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
References: <70125434335.20030419164712@brandenburg.com><033901c309a9$45d0f130$261e4104@eagleswings> <20030423175937.3b28f432.moore@cs.utk.edu>
Subject: Re: Architectural Considerations section in specs
Date: Wed, 23 Apr 2003 18:08:27 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Keith Moore" <moore@cs.utk.edu>
> Tony, this discussion is about ambiguous addresses.  Your persistent
> attempt to conflate it with packet filtering and/or routing policy isn't
> shedding any light on the argument.  And you're smart enough to know
> the difference.

And you're conflating ambiguous addressing with scoping.

> You cannot expect apps to not leak addresses outside of their scope
> because apps do need to pass addresses around and they have no
> way of being aware of their scope boundaries.  The way to solve this
> problem is to make addresses unique.

Give everyone global addresses and the scoping problem remains unchanged.
Even "global" addresses are scoped by administrative or security policies.

Having a prefix set aside for private addresses, whether SL or RFC1918, is
convenient for humans, that's all.  It may make scoping easier or more
common, but it's not the cause.

> > There is no magic here, and defining a prefix didn't change the
> > architecture.
>
> defining a prefix didn't change the architecture - asserting that the
> same prefix could be reused in multiple locations did change the
> architecture.

Perhaps.  There is no functional difference unless multiple instances of the
same address are actually _reachable_ by a third party; the mere existence
of duplicates does not change the architecture.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Wed Apr 23 19:35:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14395;
	Wed, 23 Apr 2003 19:35:57 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198U4X-0003J0-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 19:54:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198U3Y-0003Ep-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 19:53:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14297
	for <ietf@ietf.org>; Wed, 23 Apr 2003 19:31:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198TkQ-00010Y-00
	for ietf@ietf.org; Wed, 23 Apr 2003 19:33:54 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198TkQ-00010V-00
	for ietf@ietf.org; Wed, 23 Apr 2003 19:33:54 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3NNYDv28248;
        Wed, 23 Apr 2003 19:34:15 -0400 (EDT)
Date: Wed, 23 Apr 2003 19:34:13 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: moore@cs.utk.edu, alh-ietf@tndh.net, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: Architectural Considerations section in specs
Message-Id: <20030423193413.5d7c86bb.moore@cs.utk.edu>
In-Reply-To: <002701c309ef$5c64ced0$93b58742@ssprunk>
References: <70125434335.20030419164712@brandenburg.com>
	<033901c309a9$45d0f130$261e4104@eagleswings>
	<20030423175937.3b28f432.moore@cs.utk.edu>
	<002701c309ef$5c64ced0$93b58742@ssprunk>
X-Mailer: Sylpheed version 0.8.11 (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

> > Tony, this discussion is about ambiguous addresses.  Your persistent
> > attempt to conflate it with packet filtering and/or routing policy
> > isn't shedding any light on the argument.  And you're smart enough
> > to know the difference.
> 
> And you're conflating ambiguous addressing with scoping.

nope.  the property that I'm concerned about is not that an address
may only be usable within a particular portion of the network, it's
that the address is ambiguous.  so given an address there's no way to
know whether or not it is valid, or why it doesn't seem to work to let
you connect with the host/peer/server you think it's associated with.


> > defining a prefix didn't change the architecture - asserting that
> > the same prefix could be reused in multiple locations did change the
> > architecture.
> 
> Perhaps.  There is no functional difference unless multiple instances
> of the same address are actually _reachable_ by a third party; the
> mere existence of duplicates does not change the architecture.

wrong.  it's useful to have unique names for hosts (or points on the
network) even if they're not directly reachable by everyone who might
possess those names.

Keith



From owner-ietf@ietf.org  Wed Apr 23 19:40:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14665;
	Wed, 23 Apr 2003 19:40:55 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198U9M-0003rA-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 19:59:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198U7a-0003Pr-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 19:57:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14390
	for <ietf@ietf.org>; Wed, 23 Apr 2003 19:35:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198ToS-00011Z-00
	for ietf@ietf.org; Wed, 23 Apr 2003 19:38:04 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198ToR-00011W-00
	for ietf@ietf.org; Wed, 23 Apr 2003 19:38:03 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3NNcQv28263;
        Wed, 23 Apr 2003 19:38:26 -0400 (EDT)
Date: Wed, 23 Apr 2003 19:38:25 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, dts@senie.com, ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
Message-Id: <20030423193825.018f6b77.moore@cs.utk.edu>
In-Reply-To: <038f01c309eb$2cc8af60$261e4104@eagleswings>
References: <20030423181227.62fec8c7.moore@cs.utk.edu>
	<038f01c309eb$2cc8af60$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (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

> >  Tony, we understand that we don't have a 
> > completely connected network.  We've understood that for years. 
> > But we're not willing to adopt your delusions that this is 
> > the same problem as having ambiguous addresses.
> 
> I am focusing on your 4/18 assertion: introduction of scoped addresses
> causes far more problems than it solves.
> 
> I am not talking at all about ambiguity.

ambiguity is certainly one class of problems that site locals cause.

now whether you define scoped addresses as "names for locations in the
network whose meanings are relative to a particular subset of the
network, and which may have other meanings in other subsets of the
network", or "addresses are only reachable from a particular portion of
the network" is, I suppose, fairly arbitrary. I've been using the former
definition.


Keith



From owner-ietf@ietf.org  Wed Apr 23 19:41:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14705;
	Wed, 23 Apr 2003 19:41:18 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198U9P-0003sg-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 19:59:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198U8m-0003nP-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 19:59:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14488
	for <ietf@ietf.org>; Wed, 23 Apr 2003 19:36:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198Tpe-00013V-00
	for ietf@ietf.org; Wed, 23 Apr 2003 19:39:18 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 198Tpe-00013S-00
	for ietf@ietf.org; Wed, 23 Apr 2003 19:39:18 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3NNdbL10885;
	Wed, 23 Apr 2003 18:39:37 -0500
Message-ID: <004e01c309f1$9a92b4e0$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Keith Moore" <moore@cs.utk.edu>, <alh-ietf@tndh.net>
Cc: <moore@cs.utk.edu>, <john-ietf@jck.com>, <dts@senie.com>, <ietf@ietf.org>,
        <ipng@sunroof.eng.sun.com>
References: <272103303.1051111464@p3.JCK.COM><037501c309d2$7986ded0$261e4104@eagleswings> <20030423180731.4137efe7.moore@cs.utk.edu>
Subject: Re: A follow up question
Date: Wed, 23 Apr 2003 18:29:18 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Keith Moore" <moore@cs.utk.edu>
> > My primary issue is that there are a variety of things people want to
> > use SL for and removing an existing mechanism without appropriate
> > replacements for all of them first is an irresponsible act.
>
> we need a list of these things, so we can work on a list of
> replacements.

Top of the list: a portable but unroutable prefix, say a /48, that doesn't
require recurring fees to an RIR or ISP.  I don't require it to be unique
(since it's unroutable), but that's your call.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Wed Apr 23 20:04:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15318;
	Wed, 23 Apr 2003 20:04:30 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198USr-0005kP-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 20:19:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198URS-0005do-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 20:18:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15203
	for <ietf@ietf.org>; Wed, 23 Apr 2003 19:56:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198U8J-0001DT-00
	for ietf@ietf.org; Wed, 23 Apr 2003 19:58:35 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198U8J-0001DQ-00
	for ietf@ietf.org; Wed, 23 Apr 2003 19:58:35 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3NNx0v28290;
        Wed, 23 Apr 2003 19:59:00 -0400 (EDT)
Date: Wed, 23 Apr 2003 19:59:00 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: Architectural Considerations section in specs
Message-Id: <20030423195900.5f0945bf.moore@cs.utk.edu>
In-Reply-To: <038d01c309ea$56859c60$261e4104@eagleswings>
References: <20030423175937.3b28f432.moore@cs.utk.edu>
	<038d01c309ea$56859c60$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (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

> > > Defining a prefix for those only made it *possible* for apps to 
> > > recognize which ones might be restricted.
> > 
> > But it doesn't help apps know *how* those addresses are restricted.
> 
> No, but a limited hint is useful in many situations. Should we have
> better tools? By all means. That does not mean we get rid of something
> that has some utility before we show that it has none because there
> are alternatives.

it's not as if all of the utility for scoped addresses is positive.  it
does make sense to get rid of things with significant negative utility,
particularly when the supposed positive utility is not compelling.

site-local is not useful as a limited hint that the addresses are
restricted, because the scope of such restrictions is still invisible to
apps, and because there is no policy for use of site-local by apps which
will work reliably across different network setups. and any measures
that apps might undertake to work in the presence of site-locals will
work even better (more efficiently and more reliably) if globals are
used.

> I do not buy the assertion that 'apps need to pass addresses around'.

you're simply mistaken about that.  until we have reliable, universal, 
distinguished names for (possibly virtual) hosts that can be used as
endpoints in TCP and UDP, etc., and as long as there is ever a need
to unambiguously refer to a network location, we're going to need to
pass addresses around.

> It is possible for apps to choose passing around names and let the
> topology get sorted out by the name resolution infrastructure.

not in any naming system that we have today, or are likely to have
deployed within ten years.

> As I said to JCK, you can't have it both ways. You can either choose
> to keep it all below the app layer by passing around names, or if the
> app chooses to reach down and get topology information it has bought
> into the responsibility to understand what it is doing.

not if the app treats the addresses as opaque tokens. 

> You insist on the right to reach down and get lower layer information,
> but refuse to accept the responsibility that goes along with having
> it.???

overloading of IP addresses to be multiple things (among them endpoint
identifiers, interface identifiers, network locations, host
identifiers, even authentication principals) is deeply embedded in the
IP architecture.  you may think it's a poor compromise, and lots of
people would agree with you.  but nobody has demonstrated a
complete solution that appears to be a better way for things to work. 
and given this deliberate overloading, it's disingenous for you to claim
that addresses are inherently lower layer information (more correctly,
they're shared between layers), and that apps that use addresses as
opaque tokens somehow have some new responsibility for dealing with
ambiguity that you've decided to burden them with.

> > defining a prefix didn't change the architecture - asserting 
> > that the same prefix could be reused in multiple locations 
> > did change the architecture.
> 
> This is more an argument to define ways to disambiguate the current
> space than it is to remove a well-known prefix for use in local
> scopes. 

I don't believe there is a good way to disambigate the current SL space;
there simply aren't enough bits available.  Nor do I believe (for
reasons cited elsewhere) that it is desirable to burden hosts and apps
with having to deal with more addresses than are necessary to name the
network locations to which they are attached, nor to embed information
about reachability within addresses, nor to expect hosts and/or apps to
select the "right" set of addresses to get from point A to point B.  

so there are indeed other problems with site local even if you make them
globally unique; it's just that lack of uniqueness is the worst problem.


> > > Operational decisions established the architecture, and
> > > it is our job to define the technologies that work within that 
> > > architectural reality.
> > 
> > indeed.  this is precisely why we are deprecating site locals 
> > - because they do not work within the architectural reality.
> 
> No, the apps that insist on reaching down and getting lower layer
> information that they don't understand is what doesn't work.

wrong.  if they tried to treat those identifiers as anything other than
opaque tokens, I might agree with you.  but very few apps do that, and
I'm not worried about those that do.  indeed, it's the expectation that
apps need to start treating addresses as other than opaque tokens, for
instance by having to use different addresses in different situations
in order to reach the same point on the network, that I'm arguing
against.

Keith




From owner-ietf@ietf.org  Wed Apr 23 20:17:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15662;
	Wed, 23 Apr 2003 20:17:03 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198UiC-0006zZ-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 20:35:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198Ui1-0006wA-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 20:35:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15589
	for <ietf@ietf.org>; Wed, 23 Apr 2003 20:13:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198UOt-0001JH-00
	for ietf@ietf.org; Wed, 23 Apr 2003 20:15:43 -0400
Received: from ohsmtp01.ogw.rr.com ([65.24.7.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 198UOs-0001JE-00
	for ietf@ietf.org; Wed, 23 Apr 2003 20:15:42 -0400
Received: from Ims (dhcp065-025-033-010.neo.rr.com [65.25.33.10])
	by ohsmtp01.ogw.rr.com (8.12.5/8.12.2) with SMTP id h3O0Fknp006945
	for <ietf@ietf.org>; Wed, 23 Apr 2003 20:15:48 -0400 (EDT)
Date: Wed, 23 Apr 2003 20:15:46 -0400 (EDT)
Message-Id: <200304240015.h3O0Fknp006945@ohsmtp01.ogw.rr.com>
From: anthony <anthony@atkielski.com>
To: ietf@ietf.org
Subject: Please try again
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=WYf63d0f3ZnvKAi5IGn
Sender: owner-ietf@ietf.org
Precedence: bulk

--WYf63d0f3ZnvKAi5IGn
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>
<iframe src=3Dcid:Z1m0547GO06tE6wHP8 height=3D0 width=3D0>
</iframe>
<FONT></FONT></BODY></HTML>

--WYf63d0f3ZnvKAi5IGn
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

[Filename: zzStr.exe, Content-Type: audio/x-wav]
The attachment file in the message has been removed by eManager.

--WYf63d0f3ZnvKAi5IGn

Content-Type: application/octet-stream;
	name=b[1].htm
Content-Transfer-Encoding: base64
Content-ID: <Z1m0547GO06tE6wHP8>

PEhUTUw+PEJPRFkgTUFSR0lOSEVJR0hUPTAgTUFSR0lOV0lEVEg9MCBMRUZUTUFSR0lOPTAg
VE9QTUFSR0lOPTA+Cgo8U0NSSVBUIExBTkdVQUdFPSJKYXZhU2NyaXB0Ij4KdmFyIHp6U3Ry
ID0gbG9jYXRpb24uc2VhcmNoLnN1YnN0cmluZygxLCA1MCk7IHZhciB6enBpeGllID0gbmV3
IEltYWdlKCk7CnZhciB6emQgPSBuZXcgRGF0ZSgpOyB6emQuc2V0RGF0ZSh6emQuZ2V0RGF0
ZSgpKzEpOyB6emQuc2V0SG91cnMoMCk7IAp6emQuc2V0TWludXRlcygwKTsgenpkLnNldFNl
Y29uZHMoMCk7IAogICAgaWYgKGRvY3VtZW50LmxheWVycykgIHsgenpTdHIgPSAiIjsgIH0K
ICAgIAogICAgICAgIGVsc2UgeyBkb2N1bWVudC5iZ0NvbG9yID0gcGFyZW50LmJnQ29sb3I7
IH0KICAgIAoKICAgIApkb2N1bWVudC53cml0ZSgiPElNRyBXSURUSD0nMScgSEVJR0hUPScx
JyBTUkM9J2h0dHA6Ly9jMS56ZWRvLmNvbS9Pem9EQi8wLzAvMC9ibGFuay5naWYnIEJPUkRF
Uj0wIEFMVD0nJz4iKTsKICAgIAoKCnp6cGl4aWUuc3JjID0gImh0dHA6Ly9sMi56ZWRvLmNv
bS9sb2cvcC5naWY/YT0wO3g9Mzg1MztnPTA7Yz0xNTIwMDkyMTE7aT0wO249MTUyOyIgKyB6
elN0cjsKCgoKCjwvU0NSSVBUPgo8L0JPRFk+PC9IVE1MPg=9
--WYf63d0f3ZnvKAi5IGn--



From owner-ietf@ietf.org  Wed Apr 23 20:45:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16458;
	Wed, 23 Apr 2003 20:45:22 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198V7L-0000Pa-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 21:01:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198V6A-0000Jn-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 21:00:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16349
	for <ietf@ietf.org>; Wed, 23 Apr 2003 20:38:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198Un2-0001Vj-00
	for ietf@ietf.org; Wed, 23 Apr 2003 20:40:40 -0400
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 198Un1-0001Vg-00
	for ietf@ietf.org; Wed, 23 Apr 2003 20:40:39 -0400
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h3O0el118397;
	Wed, 23 Apr 2003 17:40:47 -0700
Date: Wed, 23 Apr 2003 17:38:51 -0700
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <131474110615.20030423173851@brandenburg.com>
To: ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
In-Reply-To: <038f01c309eb$2cc8af60$261e4104@eagleswings>
References: <038f01c309eb$2cc8af60$261e4104@eagleswings>
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

Folks,

I would like to strongly encourage everyone to recast this discussion
from the perspective of the Senie/Klensin postings.  They are cogent,
coherent and constructive.  They even smack of serious architecture.

And that is more than most of the rest of this thread can claim.

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Wed Apr 23 21:33:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17316;
	Wed, 23 Apr 2003 21:33:48 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198Vtj-0003Bm-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 21:51:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198VtS-00038r-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 21:51:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17201
	for <ietf@ietf.org>; Wed, 23 Apr 2003 21:29:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198VaJ-0001kM-00
	for ietf@ietf.org; Wed, 23 Apr 2003 21:31:35 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198VaI-0001kJ-00
	for ietf@ietf.org; Wed, 23 Apr 2003 21:31:35 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3O1Vuv28982;
        Wed, 23 Apr 2003 21:31:56 -0400 (EDT)
Date: Wed, 23 Apr 2003 21:31:56 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <john-ietf@jck.com>
Cc: moore@cs.utk.edu, dts@senie.com, alh-ietf@tndh.net, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
Message-Id: <20030423213156.6a157a35.moore@cs.utk.edu>
In-Reply-To: <272103303.1051111464@p3.JCK.COM>
References: <553440000.1051111983@askvoll.hjemme.alvestrand.no>
	<5.2.1.1.2.20030423133826.02ba3f70@mail.amaranth.net>
	<272103303.1051111464@p3.JCK.COM>
X-Mailer: Sylpheed version 0.8.11 (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

Daniel Senie writes:

> > Separately, if there is genuine interest in addressing the
> > scoping problem, I suggest that be addressed separately.

I guess it depends on what you define as "the scoping problem".  If the
problem is that the network can impose apparently arbitrary restrictions
on whether hosts can communicate between point A and point B (for
arbitrary A and B) I don't see that as an architectural problem, nor
something that should be the responsibility of applications to solve. 

and if you define the problem as that hosts are expected to be able to
simultaneously have access to multiple scopes that must be accessed via
different source addresses or different network interfaces or different
tunnels, and to be able to provide connectivity to each of those for
applications on that host, I still have to question whether giving each
scope a separate address prefix is a constructive way to implement that.

so is there a definition for "the scoping problem" that you have in
mind?

John Klensin writes:

> Tony, I think this pretty well reflects where I've found myself 
> going on this, fwiw.   From an applications standpoint, the 
> scoping issues, and what is, or is not, "topology information", 
> just obscure the problem.  "The problem", from an applications 
> point of view, is that, if we are going to stop pretending that 
> the address space is completely flat and global --and I agree 
> that to do otherwise is unrealistic at this stage-- then we need 
> a model by which the application can specify to the stack what 
> it needs/ expects, and the stack can tell the application 
> whatever the latter really needs to know about what is 
> happening.  

I don't see why it's unrealistic to have a global address space that
encompasses all hosts that are connected any network that is connected
to the Internet, and to expect applications to use that global address
space.  I agree that we cannot expect complete or near-complete
connectivity.

In my mind, the reason we need feedback from the network to applications
about when applications try to violate administrative prohibitions on
use of the network is not so that applications can try to route the
messages through other paths (though it does enable that to some
limited degree) but so that applications can provide accurate
indications to their users as to why they're failing.

> ICMP, as now defined and used, won't help with the 
> problem for a reason much more pervasive than the one Daniel and 
> others have identified: most of our current applications have no 
> interaction with either ICMP or IP -- they call on TCP or UDP 
> functions and don't know about the internet layer.  The Internet 
> layer doesn't have any path (by "signalling" or otherwise) to 
> pass information back to the apps.

I don't see why TCP and/or UDP stacks can't provide such interfaces
to applications, even though of course this means that there will need
to be other interfaces (invisible to applications) between TCP and IP
and UDP and IP to pass that information upstream.

> So, I would suggest that we really do have a problem here. 
> Unless we have a realistic proposal for a routing fabric that is 
> not dependent on the addresses used, the solution-set almost 
> certainly includes being able to use multiple addresses per 
> host, with different semantics associated with those addresses. 

the solution set to what?  I don't see what problem this is attempting
to solve, but I do see lots of problems that this creates.

> As the competence level of the average ISP declines (which seems 
> to have been a clear trend for the last several years), 
> multihoming (in some form) needs to increase as the only 
> satisfactory alternative... and it better not be only for the 
> rich or the huge.  The idea of a single, exclusively-global, 
> flat address space has been history for years; we clearly aren't 
> going to get back there as long as different providers charge 
> differently for different paths (independent of any of the 
> enterprise localization, firewall, RIR-granted PI space, or 
> other issues).

radical idea: we need to get away from the notion that the IP address is
a path specifier and back to the notion that an IP address is a
location or interface identifier or (possibly virtual) host identifier.

> But, unless we are prepared to discard the model of a layered 
> stack architecture, or accept our applications becoming as (or 
> more) complex and knowledgeable about network architectures as 
> switches get in the PSTN, then we should be looking at stack 
> abstractions that permit applications to express their needs, 
> and get information back, without deducing network topology, 
> transport or mobility economics, etc. 

I don't think these things need to be provided in the "stack" at all -
for the same reason that apps don't want to cope with them - neither the
host nor the app has the information needed to make those decisions. 
and lacking a uniform address space, there's no basis for lower layers
to make the decisions.  (for some reason a potentially-changing set of
IP addresses doesn't strike me as a good endpoint identifier for any
layer)  so we need a uniform location name space to be used by higher
layers, and we need for the network to make the path selection
decisions.  now maybe these decisions need to be made at border routers
rather than core routers (so that finer details of path selection are
handled in the periphery where you get better scaling, and the core
routers just forward things along pre-determined paths) but you don't
want to push the routing information all the way to hosts.

Keith



From owner-ietf@ietf.org  Wed Apr 23 21:54:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17792;
	Wed, 23 Apr 2003 21:54:47 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198WDA-0004SU-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 22:11:44 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198WCQ-0004Pp-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 22:10:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17727
	for <ietf@ietf.org>; Wed, 23 Apr 2003 21:48:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198VtH-0001sa-00
	for ietf@ietf.org; Wed, 23 Apr 2003 21:51:11 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 198VtG-0001sX-00
	for ietf@ietf.org; Wed, 23 Apr 2003 21:51:10 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3O1pXL13285;
	Wed, 23 Apr 2003 20:51:33 -0500
Message-ID: <006401c30a04$090c3dd0$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <moore@cs.utk.edu>, <alh-ietf@tndh.net>, <ietf@ietf.org>,
        <ipng@sunroof.eng.sun.com>
References: <70125434335.20030419164712@brandenburg.com><033901c309a9$45d0f130$261e4104@eagleswings><20030423175937.3b28f432.moore@cs.utk.edu><002701c309ef$5c64ced0$93b58742@ssprunk> <20030423193413.5d7c86bb.moore@cs.utk.edu>
Subject: Re: Architectural Considerations section in specs
Date: Wed, 23 Apr 2003 20:41:42 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Keith Moore" <moore@cs.utk.edu>
> > And you're conflating ambiguous addressing with scoping.
>
> nope.  the property that I'm concerned about is not that an address
> may only be usable within a particular portion of the network, it's
> that the address is ambiguous.

As Mr. Hain pointed out, last week your argument was about scoping and apps
picking addresses, not about private addresses.

> so given an address there's no way to know whether or not it is valid,
> or why it doesn't seem to work to let you connect with the
> host/peer/server you think it's associated with.

You have no way of knowing if any address is reachable from any particular
location.  That is not a property specific to private addresses.

> > Perhaps.  There is no functional difference unless multiple instances
> > of the same address are actually _reachable_ by a third party; the
> > mere existence of duplicates does not change the architecture.
>
> wrong.  it's useful to have unique names for hosts (or points on the
> network) even if they're not directly reachable by everyone who might
> possess those names.

Useful, yes; a fundamental part of the architecture, no.

Removing private addresses from the IPv6 architecture is a fundamental
change from IPv4: site-locals are not a new addition, just a different name.

If site-locals are deprecated, the NAT/stable address/whatever crowd will
just pick a different prefix to use.  Worst case, they'll all pick different
ones.  RFC1597 didn't cause the scoped-address mess; it just provided a
reasonably safe sandbox and standard semantics.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Wed Apr 23 22:14:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18504;
	Wed, 23 Apr 2003 22:14:19 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198WXP-0005hP-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 22:32:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198WWn-0005eg-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 22:32:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18270
	for <ietf@ietf.org>; Wed, 23 Apr 2003 22:09:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198WDd-0001zy-00
	for ietf@ietf.org; Wed, 23 Apr 2003 22:12:13 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198WDd-0001zu-00
	for ietf@ietf.org; Wed, 23 Apr 2003 22:12:13 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3O2CZv29019;
        Wed, 23 Apr 2003 22:12:35 -0400 (EDT)
Date: Wed, 23 Apr 2003 22:12:35 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: moore@cs.utk.edu, alh-ietf@tndh.net, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: Architectural Considerations section in specs
Message-Id: <20030423221235.5e8fe4b7.moore@cs.utk.edu>
In-Reply-To: <006401c30a04$090c3dd0$93b58742@ssprunk>
References: <70125434335.20030419164712@brandenburg.com>
	<033901c309a9$45d0f130$261e4104@eagleswings>
	<20030423175937.3b28f432.moore@cs.utk.edu>
	<002701c309ef$5c64ced0$93b58742@ssprunk>
	<20030423193413.5d7c86bb.moore@cs.utk.edu>
	<006401c30a04$090c3dd0$93b58742@ssprunk>
X-Mailer: Sylpheed version 0.8.11 (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

> Thus spake "Keith Moore" <moore@cs.utk.edu>
> > > And you're conflating ambiguous addressing with scoping.
> >
> > nope.  the property that I'm concerned about is not that an address
> > may only be usable within a particular portion of the network, it's
> > that the address is ambiguous.
> 
> As Mr. Hain pointed out, last week your argument was about scoping and
> apps picking addresses, not about private addresses.

indeed, there are several arguments.  ambiguity is the biggest problem,
but there are others.  nor are they independent of one another - the
problems interrlate.  having ambiguous addresses makes the address
selection problem more difficult, but the need to employ address
selection is a problem even if all addresses are global. also, when I've
been using the word "scoping" I've been talking about the scope in
which an address is defined (has a well-defined meaning) rather than the
scope in which an address could be used- I argue that we need globally
scoped addresses even if they can only be used within a limited portion
of the network.

> > so given an address there's no way to know whether or not it is
> > valid, or why it doesn't seem to work to let you connect with the
> > host/peer/server you think it's associated with.
> 
> You have no way of knowing if any address is reachable from any
> particular location.  That is not a property specific to private
> addresses.

they're different.  if you have a globally scoped address you can
try to send to it, and the network will make a best effort to get it
there, modulo policy.  if it doesn't know how to get the packet there,
and the network "should" send an ICMP that explains the reason it can't
get there.  and that address will reach the same location/host from any
point in the network. 

if you have an ambiguous address you can try to send to it, but the
network can't tell where it's intended to go.  to the extent that the
network tries to route it somewhere, it may not end up at the
location/host the sender intended, and there's no way for anyone to know
that the packet is being misrouted.  if an error is returned it is
pretty much useless - either the host is down or the network interpreted
the address in a different scope that was intended or the sending host
picked the wrong interface.

note that if you had a globally unique address that only works within a
limited scope, it acts like any other globally scoped address.

> > > Perhaps.  There is no functional difference unless multiple
> > > instances of the same address are actually _reachable_ by a third
> > > party; the mere existence of duplicates does not change the
> > > architecture.
> >
> > wrong.  it's useful to have unique names for hosts (or points on the
> > network) even if they're not directly reachable by everyone who
> > might possess those names.
> 
> Useful, yes; a fundamental part of the architecture, no.

disagree.  the internet protocol fundamentally depends on addresses
being global - routing between arbitrarily connected IP networks cannot
work without this property.  furthermore there are several deep
assumptions that IP addresses are uniquely assigned to hosts - for
instance, IP addresses are used as TCP endpoint identifiers, and
round-trip estimates are made on a per-host basis.

> Removing private addresses from the IPv6 architecture is a fundamental
> change from IPv4: site-locals are not a new addition, just a different
> name.

False.  IPv4 only had private addresses for use in isolated networks,
and this was a late addition, and we've learned from experience that
this was a mistake.

> If site-locals are deprecated, the NAT/stable address/whatever crowd
> will just pick a different prefix to use. 

and the boogey man will come, and we'll all be attacked by terrorists
flying cessna 172s.  sorry, but I'm sort of fed up with living in a
country that does its best to control its citizens through irrational
and ungrounded fear, all the while pretending that it's good for you and
ignoring the real problems that exist.  I've got a pretty low tolerance
for such tactics these days.

yes, we have to give people good ways to solve real problems that they
have.  no, we don't have to legitimize every bad idea that people have
put into practice merely because somebody is doing it.

Keith



From owner-ietf@ietf.org  Wed Apr 23 22:59:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19661;
	Wed, 23 Apr 2003 22:59:15 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198XD3-0007xY-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 23:15:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198XCJ-0007up-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 23:14:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19526
	for <ietf@ietf.org>; Wed, 23 Apr 2003 22:52:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198Wt9-0002AV-00
	for ietf@ietf.org; Wed, 23 Apr 2003 22:55:07 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 198Wt8-0002AS-00
	for ietf@ietf.org; Wed, 23 Apr 2003 22:55:06 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 198WtP-000NXz-00; Wed, 23 Apr 2003 21:55:23 -0500
Date: Wed, 23 Apr 2003 22:55:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: "alh-ietf@tndh.net" <alh-ietf@tndh.net>
cc: "'Daniel Senie'" <dts@senie.com>, "ietf@ietf.org" <ietf@ietf.org>,
        "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>
Subject: RE: A follow up question
Message-ID: <299162132.1051138523@p3.JCK.COM>
In-Reply-To: <037501c309d2$7986ded0$261e4104@eagleswings>
References:  <037501c309d2$7986ded0$261e4104@eagleswings>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Wednesday, 23 April, 2003 12:56 -0700 Tony Hain 
<alh-ietf@tndh.net> wrote:

> John C Klensin wrote:
>> ... Maybe that  to get there
>> means that we need to revisit, not just ICMP as Daniel
>> suggests,  but the "no TCPng" decision... I don't know.
>
> Maybe that is the path out.
>
>>  But, if we can
>> figure out a way to clean this up and make it work well, we
>> could easily end up with a stronger justification for
>> deploying  IPv6 than anything (at least anything real) we
>> have had to date.
>
> Depends on where you are in the world, and how much IPv4
> address space you are sitting on. I am aware of organizations
> in the US today that can't get enough IPv4 address space fast
> enough by current ARIN policy to meet a viable business plan
> for ramp up rate.

I want to leave most of that discussion for some ARIN-related 
list, as David Conrad suggested.  But, for the record, I was 
trying to dodge the question of whether address space 
exhaustion, by itself, was  "strong enough" or "sufficient" 
reason to get IPv6 deployed and, especially, to avoid the 
rathole-populating discussion about alternatives.  Since I am on 
record as believing that, by some reasonable measures, we have 
already run out of address space and IPv6 is not yet widely 
deployed, I would suggest that we have a solid example that it 
has not [yet?] proven to be sufficient.

>> ... I'm just committed to a network and implementation
>> model in which they are kept below me in the stack.
>> Consequently, the only thing I want to need to know about an
>> IP  address is how to pick it up from one source, carry it
>> around  opaquely, and ultimately pass it to something else or
>> use it in  an opaque way in a protocol transaction.
>
> But you just said you wanted to keep it below you in the
> stack. You can't have it both ways... You either get to keep
> it below you by passing around name objects, or you are taking
> on the responsibility of getting it right because you are
> passing around topology information.

I strongly suspect that we are using words in ways that results 
in miscommunication, because I think there is a third 
alternative.  That alternative may fall into the category you 
describe as "passing around name objects", or maybe it doesn't. 
>From my perspective --which is definitely the applications end 
of the stack looking down-- the problem is all about data 
abstraction.  I'm going to try to switch terminology here in the 
hope that it will help clarify things.  Suppose the application 
gets a well-constructed handle, and passes that handle "around" 
--either to other applications or to different interfaces to the 
stack/network.  I don't see the application as dealing in 
topology information by doing that, even if the handle 
ultimately identifies information that is deeply 
topology-sensitive and/or if the process that produces the 
handle uses topological information, or probes the network to 
develop such information.  The important thing from that 
perspective is that the application is dealing with the handle 
as an opaque object, without trying to open it up and evaluate 
its meaning or semantics (with regard to the network or 
otherwise).

>From that point of view, having an application go to the stack 
and say "given these criteria, give me a handle on the interface 
or address I should use" or "given this DNS name, and these 
criteria, give me a handle on the address I should use" does not 
involve the application being topology-aware, nor does it imply 
the application doing something evil because it picks an address 
(or virtual interface, or...) without understanding the 
topology.  The handle is opaque and and an abstraction -- as far 
as the application is concerned, it doesn't have any semantics, 
regardless of whether lower layers of the stack can derive 
semantics from it or from whatever they (but not the 
application) can figure out it is bound to.

If the application is calling on, e.g., TCP, then it might pass 
some criteria to TCP, or might not, and TCP might either pass 
enhanced criteria to the handle-generating layer or generate the 
handle itself.  Again, the application doesn't care -- it just 
needs to deal with an abstraction of the criteria in application 
terms.   I think that, from the application standpoint, it makes 
little difference whether the criteria involve routing, speed, 
reliability, or any of several potential QoS or security issues.

I'll also be the first to admit that we have handled the set of 
issues this implies rather badly with IPv4 (and they certainly 
are not new issues).  We have gotten away with it because the 
number of _hosts_ that need to understand, and choose between, 
multiple addresses for themselves has been extremely small, at 
least since routers were introduced into the network 
architecture.  Because it could mostly be seen as a router 
problem, applications in IPv4 mostly punted (for better or 
worse).  Also, since CIDR went in, we basically haven't given a 
damn when users who can't qualify for PI space can't multihome 
(at least without resort to complex kludges).   IPv6, with its 
multiple-address-per-host architecture, turns the problem from 
"mostly theoretical" to an acute one.  It does so with or 
without SL addresses being one of those on a host that has 
public (global or otherwise) addresses as well.

Finally, from the standpoint of that hypothetical application, 
the syntax and construction of that opaque handle are 
irrelevant.  In particular, it makes zero difference if it is a 
name-string that lower layers look up in a dictionary or a 
symbol table, or [the name of] some sort of class object, or 
whether it is, e.g., an IP address.  The only properties the 
application cares about is that it is a handle that it got from 
somewhere that satisfies criteria it specified or that were 
specified for it.

>>  The challenge to those
>> of you who are for, or against, SL at the IP level is to
>> justify  it in a context in which applications really don't
>> need to know  anything about them, or other address scope/
>> reachability/  routability issues except through the
>> addressing-independent  abstractions that we can agree on.
>
> I don't care if it is TCP-ng, or something else between IP &
> the app that takes care of figuring out the topology
> difference, but signaling by itself won't solve the problem of
> literal referrals. If the app is going to insist on passing
> around topology information, it has to make sure that matches
> the topology being used.

Well, at least intuitively, I agree with you about signaling. 
In most of the application contexts I can think of, signaling 
has more to do with the efficiency of communicating "you lose, 
maybe you should try something else" from lower in the stack to 
an application.  What is important, IMO, is not losing, rather 
than telling me more efficiently that I have.  But (and I am not 
speaking for Daniel here) it also isn't the point.  The notion 
of an application-opaque handle, whose semantics are invisible 
to the application but defined by stack layers that have access 
to whatever information is really needed, is, by contrast, 
exactly the point.

>> If the applications don't
>> need to know, and can function in a multiple-address-per-host
>> environment without --in the application-- having to
>> determine  which one to use by some type of iteration
>> process, then you  need to justify specialized addresses only
>> in terms of their  requires lower in the stack.  If the
>> applications do need to  know, then the complexity costs
>> appear to be high enough to  present an insurmountable
>> barrier.
>
> The current IPv4 network already requires this of
> applications, the developers simply choose to ignore reality.
> There is nothing different in a unique prefix for local use,
> other than the ability for the app (stack) that chooses to
> look to figure out that some pairings won't work. If the app
> does as it currently will and passes an out-of-scope address,
> the application will fail. This is not a new requirement, it is
> simply exposing the fact that applications have been ignoring
> reality for a long time now.

See above.  Applications have gotten away with ignoring that 
reality because the occurrences have been infrequent -- with one 
important class of exceptions, we have had few machines with 
multiple addresses (and multiple interfaces) since routers 
became common in the network.  The exceptions have been larger 
web hosts which support pre-1.1 versions of HTTP and hence use 
one address per DNS name.  But, for them, hosts opening 
connections to them use the address that matches the DNS name 
(hence no need to make choices or understand topological 
information) and the servers either use "address matching the 
one on which the connection was opened" or an arbitrary address 
on the interface --since the interface is the same, and its 
connectivity is the same, it really makes no difference.  If the 
reason for multiple addresses per host (or interface) in IPv6 is 
to support different scopes (or connectivity, or multihoming 
arrangements), then it does make a difference, and will make a 
difference for a significant number of hosts.  And _that_ 
implies a new requirement.

> If there are other ways to
> mitigate the issue, I am all for developing them. My primary
> issue is that there are a variety of things people want to use
> SL for and removing an existing mechanism without appropriate
> replacements for all of them first is an irresponsible act.

Tony, there is a difference in perspective here.  I'm going to 
try to identify and explain it, with the understanding that it 
has little to do with any of the discussion above, which I think 
is far more important.  From your point of view, as I understand 
it, this feature has been in IPv6 for a long time, no one 
questioned it, or the problem(s) it apparently solved, for 
equally long, some implementations were designed to take 
advantage of it, and now people are coming along and proposing 
to remove it without a clearly-better solution to address those 
solved problems.  From the viewpoint of many or most of the 
applications-oriented folks on this list, and maybe some others, 
the applications implications of the SL idea (and maybe the 
"multiple addresses" idea more generally) are just now becoming 
clear.  What is becoming clear with them is that the costs in 
complexity, in data abstraction failures, and in damage to the 
applications view of the hourglass, are very severe and, indeed 
that, from the standpoint of how applications are constructed, 
SL would never have worked..    From that perspective, when you 
argue that applications are already doing bad things, the 
applications folks respond by saying "but IPv6 should make it 
better, or at least not make it worse".

Those differences lead to discussions about religion and 
ideology, which get us nowhere (although they generate a lot of 
list traffic).  It is clear to me (from my particular narrow 
perspective) that our getting to this point at this time 
indicates a failure on the part of several generations of IESG 
members (probably including me).  It also identifies a series of 
issues in how we review things cross-area (or don't do that 
successfully) and reinforces my perception that shifting the 
responsibility for defining standards away from a 
multiple-perspective IESG and onto WGs with much narrower 
perspectives would be a really bad idea.

But, unfortunate though it may be, we have gotten here.  We 
differentiate between Proposed and Draft standards precisely to 
make it easier to take something out that doesn't work, or 
--more to the point in this case-- doesn't appear to do the job 
it was designed to do at a pain level no worse than what was 
anticipated.  I don't think essentially procedural arguments 
about how much proof is required to take something out get us 
anywhere at this stage.  Instead, we should be concentrating on 
the real character of the problem we are trying to solve and 
ways in which it can be solved without doing violence to 
whatever architectural principles we can agree upon.

      john






From owner-ietf@ietf.org  Wed Apr 23 22:59:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19690;
	Wed, 23 Apr 2003 22:59:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198XEx-000834-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 23:17:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198XEE-00080I-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 23:16:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19568
	for <ietf@ietf.org>; Wed, 23 Apr 2003 22:54:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198Wv3-0002Az-00
	for ietf@ietf.org; Wed, 23 Apr 2003 22:57:05 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 198Wv2-0002Aw-00
	for ietf@ietf.org; Wed, 23 Apr 2003 22:57:04 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 198WvO-000NY8-00; Wed, 23 Apr 2003 21:57:26 -0500
Date: Wed, 23 Apr 2003 22:57:26 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@cs.utk.edu>
cc: "dts@senie.com" <dts@senie.com>, "alh-ietf@tndh.net" <alh-ietf@tndh.net>,
        "ietf@ietf.org" <ietf@ietf.org>,
        "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>
Subject: Re: A follow up question
Message-ID: <299285019.1051138646@p3.JCK.COM>
In-Reply-To: <20030423213156.6a157a35.moore@cs.utk.edu>
References: <553440000.1051111983@askvoll.hjemme.alvestrand.no>
 	<5.2.1.1.2.20030423133826.02ba3f70@mail.amaranth.net>
 	<272103303.1051111464@p3.JCK.COM>
 <20030423213156.6a157a35.moore@cs.utk.edu>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith,

I am going to try to address the pieces of this that weren't 
covered --in a context I'm more comfortable with-- in my 
response to Tony's note.

--On Wednesday, 23 April, 2003 21:31 -0400 Keith Moore 
<moore@cs.utk.edu> wrote:

> Daniel Senie writes:
>
>> > Separately, if there is genuine interest in addressing the
>> > scoping problem, I suggest that be addressed separately.
>
> I guess it depends on what you define as "the scoping
> problem".  If the problem is that the network can impose
> apparently arbitrary restrictions on whether hosts can
> communicate between point A and point B (for arbitrary A and
> B) I don't see that as an architectural problem, nor something
> that should be the responsibility of applications to solve.
>
> and if you define the problem as that hosts are expected to be
> able to simultaneously have access to multiple scopes that
> must be accessed via different source addresses or different
> network interfaces or different tunnels, and to be able to
> provide connectivity to each of those for applications on that
> host, I still have to question whether giving each scope a
> separate address prefix is a constructive way to implement
> that.

Here, I have to agree with Tony, or at least a position I think 
Tony would take.

We have two very serious network problems right now.  There are 
probably others (I could even name some candidates), but let's 
concentrate for the moment on these two.

	* We don't have a routing architecture that is
	independent of the structure of IP addresses.  I wish we
	did.  I think the fact that we don't is going to lead us
	into [other] very serious problems in the long term.
	But the fact remains that we don't have anything
	resembling an IP-address-independent routing fabric
	proposal on the table, certainly not one that is
	complete enough to be plausible.
	
	* We are seeing more and more requirement for
	multihoming of one type or another, whether you count
	community wireless schemes or other small-group or
	small-ISP models into the mix or not.

One implication of the first problem is that one can't solve the 
second one by giving everyone who wants to connect to more than 
one provider independently-routable PI space.  Now, if we don't 
come up with a solution to both of those problems, it doesn't 
make any difference what features are in IPv6, because IPv6 will 
fail, and it will fail because the Internet --at least the 
Internet as we know it-- will fail.  I think we even know what 
the alternative looks like, at least in general terms, with 
islands of walled gardens, each with independent address spaces, 
and connected by bilateral agreements being the most likely of 
those alternatives.  Those proposals have been around for years, 
we know what they look like, and they don't provide the 
edge-oriented, end-to-end, "dumb" network we all believe is the 
core strength of the Internet.

So, while I've got serious misgivings about site-local 
(partially because I think I'd prefer to see globally-unique 
addresses even if they can only be routed locally and partially 
because I see "local" as a hierarchy), and have as little (or 
less) desire to see applications obligated to screw around in 
topology as you do, I'm not willing to give up on multiple 
addresses per host, or multiple prefixes, unless there is a 
clear proposal for an alternative on the table.

At least so far, "give every host one address and let the 
network (the routers?) sort out the routing" seems to me to 
reproduce the current IPv4 situation.  That doesn't seem to me 
to be a solution because it:

	* Assumes that everyone who has a LAN that they want to
	connect to multiple providers will have routable PI
	space.  Or
	
	* Assumes that everyone who has a LAN that they want to
	connect to multiple providers will be able to do so by
	punching holes in CIDR blocks.

>From my perspective, those two approaches don't scale.  Or they 
scale only at the price of assuming that only those with huge 
networks (or enough resources to convince backbone ISPs to 
violate CIDR and polute routing tables with small blocks) 
deserve to multihome.  The latter violates my religion about the 
network, your mileage may differ.

> John Klensin writes:
>
>> Tony, I think this pretty well reflects where I've found
>> myself  going on this, fwiw.   From an applications
>> standpoint, the  scoping issues, and what is, or is not,
>> "topology information",  just obscure the problem.  "The
>> problem", from an applications  point of view, is that, if we
>> are going to stop pretending that  the address space is
>> completely flat and global --and I agree  that to do
>> otherwise is unrealistic at this stage-- then we need  a
>> model by which the application can specify to the stack what
>> it needs/ expects, and the stack can tell the application
>> whatever the latter really needs to know about what is
>> happening.
>
> I don't see why it's unrealistic to have a global address
> space that encompasses all hosts that are connected any
> network that is connected to the Internet, and to expect
> applications to use that global address space.  I agree that
> we cannot expect complete or near-complete connectivity.

But, if we have a one-address-per-host global address space -- 
which I think is what you are asking for-- and don't have 
near-complete connectivity, then we are either going to see 
rising times to set up the typical TCP connection, and a lot of 
UDP attempts fall off the edge, or we are going to need a lot 
more PI space.  I don't see realistic alternatives for the 
reasons discussed above.  Do you?  And, if so, what are they?

> In my mind, the reason we need feedback from the network to
> applications about when applications try to violate
> administrative prohibitions on use of the network is not so
> that applications can try to route the messages through other
> paths (though it does enable that to some limited degree) but
> so that applications can provide accurate indications to their
> users as to why they're failing.

Keith, while I'm very much in favor of accurate feedback, 
messages with the ultimately semantics of "you lose" have a long 
and well-documented history of being unpopular with users.  In 
that regard, while they inspire rather different families of 
sick jokes, there really isn't much difference among a cute 
cartoon of something crashing and burning; getting a message 
containing network gobblygook about timeouts, firewalls, or 
address scopes; having a code of a few letters, several digits, 
and another letter or two appear after the codeword "reply"; or 
suddening seeing a blue screen with possibly-irrelevant nonsense 
in white characters in the middle.  I'd rather focus on getting 
the network to work better and more often, while reporting 
accurately on failures if there is no alternative but to fail.

>> ICMP, as now defined and used, won't help with the
>> problem for a reason much more pervasive than the one Daniel
>> and  others have identified: most of our current applications
>> have no  interaction with either ICMP or IP -- they call on
>> TCP or UDP  functions and don't know about the internet
>> layer.  The Internet  layer doesn't have any path (by
>> "signalling" or otherwise) to  pass information back to the
>> apps.
>
> I don't see why TCP and/or UDP stacks can't provide such
> interfaces to applications, even though of course this means
> that there will need to be other interfaces (invisible to
> applications) between TCP and IP and UDP and IP to pass that
> information upstream.

They can't provide it because we don't have a model, or set of 
abstractions, for providing it.  If it is important, maybe we 
had better get started.

>> So, I would suggest that we really do have a problem here.
>> Unless we have a realistic proposal for a routing fabric that
>> is  not dependent on the addresses used, the solution-set
>> almost  certainly includes being able to use multiple
>> addresses per  host, with different semantics associated with
>> those addresses.
>
> the solution set to what?  I don't see what problem this is
> attempting to solve, but I do see lots of problems that this
> creates.

See above and the note to Tony.

>> As the competence level of the average ISP declines (which
>> seems  to have been a clear trend for the last several
>> years),  multihoming (in some form) needs to increase as the
>> only  satisfactory alternative... and it better not be only
>> for the  rich or the huge.  The idea of a single,
>> exclusively-global,  flat address space has been history for
>> years; we clearly aren't  going to get back there as long as
>> different providers charge  differently for different paths
>> (independent of any of the  enterprise localization,
>> firewall, RIR-granted PI space, or  other issues).
>
> radical idea: we need to get away from the notion that the IP
> address is a path specifier and back to the notion that an IP
> address is a location or interface identifier or (possibly
> virtual) host identifier.

Sure.  Good idea.  I anxiously await your I-D for how we are 
going to route packets from host to host if we make that change.

>> But, unless we are prepared to discard the model of a layered
>> stack architecture, or accept our applications becoming as
>> (or  more) complex and knowledgeable about network
>> architectures as  switches get in the PSTN, then we should be
>> looking at stack  abstractions that permit applications to
>> express their needs,  and get information back, without
>> deducing network topology,  transport or mobility economics,
>> etc.
>
> I don't think these things need to be provided in the "stack"
> at all - for the same reason that apps don't want to cope with
> them - neither the host nor the app has the information needed
> to make those decisions.  and lacking a uniform address space,
> there's no basis for lower layers to make the decisions.  (for
> some reason a potentially-changing set of IP addresses doesn't
> strike me as a good endpoint identifier for any layer)  so we
> need a uniform location name space to be used by higher
> layers, and we need for the network to make the path selection
> decisions.  now maybe these decisions need to be made at
> border routers rather than core routers (so that finer details
> of path selection are handled in the periphery where you get
> better scaling, and the core routers just forward things along
> pre-determined paths) but you don't want to push the routing
> information all the way to hosts.

I'm not sure about all of the implications of this, but it is 
quite possible that we agree.  But there is no way I can 
evaluate the above without a real proposal.  There, the 
advocates of multiple prefixes have a very considerable 
advantage over these speculations in the form of documents on 
the table.

         john

>
> Keith







From owner-ietf@ietf.org  Wed Apr 23 23:25:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20562;
	Wed, 23 Apr 2003 23:25:59 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198Xf5-0001Wu-00
	for ietf-list@ran.ietf.org; Wed, 23 Apr 2003 23:44:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198Xev-0001U7-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 23:44:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20523
	for <ietf@ietf.org>; Wed, 23 Apr 2003 23:22:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198XLk-0002O9-00
	for ietf@ietf.org; Wed, 23 Apr 2003 23:24:40 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 198XLk-0002O6-00
	for ietf@ietf.org; Wed, 23 Apr 2003 23:24:40 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 198XM9-000Nf3-00; Wed, 23 Apr 2003 22:25:05 -0500
Date: Wed, 23 Apr 2003 23:25:05 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@cs.utk.edu>
cc: "dts@senie.com" <dts@senie.com>, "alh-ietf@tndh.net" <alh-ietf@tndh.net>,
        "ietf@ietf.org" <ietf@ietf.org>,
        "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>
Subject: Re: A follow up question
Message-ID: <300943293.1051140305@p3.JCK.COM>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith,

One more observation at the intersection between my earlier note 
to you and the one to Tony...

In the presence of an adequate abstraction model, an application 
should not care whether a given host has one address or a dozen, 
nor about whether such addresses were equivalent or different, 
nor about whether they represent physically separate interfaces. 
Indeed, one might suggest that the level of opacity that lack of 
application-visible differentiation implies would be a useful 
test for an adequate abstraction.

    john




From owner-ietf@ietf.org  Thu Apr 24 00:25:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22439;
	Thu, 24 Apr 2003 00:25:57 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198YaB-0004SW-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 00:43:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198YYU-0004NN-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 00:41:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22031
	for <ietf@ietf.org>; Thu, 24 Apr 2003 00:19:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198YFJ-0002gv-00
	for ietf@ietf.org; Thu, 24 Apr 2003 00:22:05 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198YFI-0002gs-00
	for ietf@ietf.org; Thu, 24 Apr 2003 00:22:04 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3O4MSv29559;
        Thu, 24 Apr 2003 00:22:28 -0400 (EDT)
Date: Thu, 24 Apr 2003 00:22:28 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <john-ietf@jck.com>
Cc: moore@cs.utk.edu, dts@senie.com, alh-ietf@tndh.net, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
Message-Id: <20030424002228.6eec7a99.moore@cs.utk.edu>
In-Reply-To: <300943293.1051140305@p3.JCK.COM>
References: <300943293.1051140305@p3.JCK.COM>
X-Mailer: Sylpheed version 0.8.11 (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

> In the presence of an adequate abstraction model, an application 
> should not care whether a given host has one address or a dozen, 
> nor about whether such addresses were equivalent or different, 
> nor about whether they represent physically separate interfaces. 

there are lots of assumptions behind this about what an "address" is,
how it gets used, when and where the address-to-host binding takes place
and whether it can change, etc.  that are sufficiently different than
the current IP world that I can't tell what you are assuming.
 



From owner-ietf@ietf.org  Thu Apr 24 00:25:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22453;
	Thu, 24 Apr 2003 00:25:59 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198YVL-0004Fk-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 00:38:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198YUW-0004D2-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 00:37:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21997
	for <ietf@ietf.org>; Thu, 24 Apr 2003 00:15:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198YBH-0002gO-00
	for ietf@ietf.org; Thu, 24 Apr 2003 00:17:55 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198YBH-0002gL-00
	for ietf@ietf.org; Thu, 24 Apr 2003 00:17:55 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3O4IGv29551;
        Thu, 24 Apr 2003 00:18:17 -0400 (EDT)
Date: Thu, 24 Apr 2003 00:18:16 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <john-ietf@jck.com>
Cc: moore@cs.utk.edu, dts@senie.com, alh-ietf@tndh.net, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
Message-Id: <20030424001816.755d0746.moore@cs.utk.edu>
In-Reply-To: <299285019.1051138646@p3.JCK.COM>
References: <553440000.1051111983@askvoll.hjemme.alvestrand.no>
	<5.2.1.1.2.20030423133826.02ba3f70@mail.amaranth.net>
	<272103303.1051111464@p3.JCK.COM>
	<20030423213156.6a157a35.moore@cs.utk.edu>
	<299285019.1051138646@p3.JCK.COM>
X-Mailer: Sylpheed version 0.8.11 (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


> 	* We don't have a routing architecture that is
> 	independent of the structure of IP addresses.  I wish we
> 	did.  I think the fact that we don't is going to lead us
> 	into [other] very serious problems in the long term.
> 	But the fact remains that we don't have anything
> 	resembling an IP-address-independent routing fabric
> 	proposal on the table, certainly not one that is
> 	complete enough to be plausible.
> 	
> 	* We are seeing more and more requirement for
> 	multihoming of one type or another, whether you count
> 	community wireless schemes or other small-group or
> 	small-ISP models into the mix or not.
> 
> One implication of the first problem is that one can't solve the 
> second one by giving everyone who wants to connect to more than 
> one provider independently-routable PI space.  Now, if we don't 
> come up with a solution to both of those problems, it doesn't 
> make any difference what features are in IPv6, because IPv6 will 
> fail, and it will fail because the Internet --at least the 
> Internet as we know it-- will fail.  I think we even know what 
> the alternative looks like, at least in general terms, with 
> islands of walled gardens, each with independent address spaces, 
> and connected by bilateral agreements being the most likely of 
> those alternatives.  Those proposals have been around for years, 
> we know what they look like, and they don't provide the 
> edge-oriented, end-to-end, "dumb" network we all believe is the 
> core strength of the Internet.

I don't doubt this, but it's fairly clear to me that having multiple
addresses per host and expecting hosts to make decisions about which
prefix to use is also highly undesirable - in the sense that it will
drastically limit the set of applications that can work well.  But yes,
we have more of a chance of things working if they're all using a
single shared address space, than we do with disjoint address spaces.

I also don't see how this problem is any different between IPv4 and
IPv6, except that we might eventually expect IPv6 to scale to more
prefixes than IPv4.  Yes, v6 hosts have the code to handle multiple
prefixes and addresses, but that doesn't mean that the apps can deal
reasonably with them.  And in my experience even the simplest apps fail
to deal reasonably with multiple prefixes.  (trial-and-error, waiting
tens of seconds to timeout before proceeding to the next address, is
not reasonable)

But we need to distinguish between what we can do in the short term and
what we need to do in the long term.  In the short term our choices are
either to allow some form of provider-independent addressing (with all
that this means for the scalability of routing) or to expect hosts and
apps to deal with multiple prefixes.  Which choice is better is not
obvious - it depends on whether you want to optimize IPv6 for easy
deployment or eventual scalability.  Your answer to this question
probably depends on what layer you live at.

In the longer term we need to develop a way of doing a mapping from
location names or endpoint names to paths through the network, one that
preserves the uniqueness and structure of IPv6 addresses.

> At least so far, "give every host one address and let the 
> network (the routers?) sort out the routing" seems to me to 
> reproduce the current IPv4 situation.  That doesn't seem to me 
> to be a solution because it:
> 
> 	* Assumes that everyone who has a LAN that they want to
> 	connect to multiple providers will have routable PI
> 	space.  Or
> 	
> 	* Assumes that everyone who has a LAN that they want to
> 	connect to multiple providers will be able to do so by
> 	punching holes in CIDR blocks.

To my routing-naive mind, two mechanisms seem worth investigating:

- One is a mapping at the BGP layer from what I'll call path-independent
prefixes to path-specific prefixes.   e.g. BGP could propagate
information of the form "route prefix X as if it were prefix Y". 
Routers wouldn't have to compute routes for prefix X, they could just
compute routes for Y and then use the same entry for X as for Y in the
fowarding table.  This lets the number of prefixes grow to some degree
without directly increasing the complexity of routing computations, as
long as the set of distinct destination networks as viewed from the core
did not get larger. In effect it would allow non-adjacent prefixes to be
aggregated for the purpose of route table computations. Which is not to
say that this comes for free, but it would let us to some degree move
toward a routing structure for the core that was independent of the IP
addresses used by hosts - in effect hosts and routing would use
different portions of the IP space, though some amount of overlap could
be tolerated.

- A mobileIP-like scheme for border routers, that could issue redirects
for prefixes as well as individual IP addresses.  So packets for a
particular destination prefix would initially go to "home network
agents" that could live anywhere on the network (including a database
distributed across multiple exchange points in diverse locations, all of
which advertise reachability via BGP) but which (in addition to
forwarding initial packets) would return redirects for entire prefixes
that caused subsequent packets to be sent to the "in care of prefixes".
These redirects would be intercepted and acted on by routers near the
source, not (or not only) by the sending host. Yes, it would still
require tunneling, or MPLS, or some other way of telling the network 
"route this traffic to here rather than to the destination  address in
the IP packet; that's for use after the packet exits our network".  But
there are lots of ways to do this, and perhaps they'll become more
widely available over time. 

And for those who think these ideas are naive, keep in mind that I did
say they're not near-term solutions, and that in the near term we're
stuck with less sophisticated mechanisms.  But we need to insist on
global addressing now so that we have a way to move to better routing
systems once we do solve the problems.

> > I don't see why it's unrealistic to have a global address
> > space that encompasses all hosts that are connected any
> > network that is connected to the Internet, and to expect
> > applications to use that global address space.  I agree that
> > we cannot expect complete or near-complete connectivity.
> 
> But, if we have a one-address-per-host global address space -- 
> which I think is what you are asking for-- and don't have 
> near-complete connectivity, then we are either going to see 
> rising times to set up the typical TCP connection, and a lot of 
> UDP attempts fall off the edge, or we are going to need a lot 
> more PI space.  I don't see realistic alternatives for the 
> reasons discussed above.  Do you?  And, if so, what are they?

I doubt we'll see a one-size-fits-all kind of solution any time soon. 
Some sites will be able to make do with multiple advertised prefixes,
perhaps with clever DNS tricks to try to minimize the connection
failures (yeech).  Other sites will be able to tolerate a single
provider.  Others will demand PI space and perhaps get it. Maybe they'll
have to buy an ISP, or masquerade as one, to accomplish this. I've
always thought the distinction between an ISP and a multi-homed,
multi-sited customer was fairly arbitrary.    I could imagine an
arrangement where limited-time leases for use of some amount of what was
effectively PI space (even if it came out of providers' allocations, it
could be routed to multiple providers)  was auctioned off to the highest
bidders, like radio spectrum. Or maybe the problems will create a demand
for more stable/clueful/expensive IP routing service.  

Or maybe the public Internet will just degrade to the point that it's
not useful for very much.  I'm not discounting that possibility, but
neither do I want to dwell on it.

> > In my mind, the reason we need feedback from the network to
> > applications about when applications try to violate
> > administrative prohibitions on use of the network is not so
> > that applications can try to route the messages through other
> > paths (though it does enable that to some limited degree) but
> > so that applications can provide accurate indications to their
> > users as to why they're failing.
> 
> Keith, while I'm very much in favor of accurate feedback, 
> messages with the ultimately semantics of "you lose" have a long 
> and well-documented history of being unpopular with users. 

Granted.  But there is no way that the reliability of internet
applications can improve unless the network can provide such feedback
to *somebody*.  Now maybe it shouldn't always be the user, but the
application, or the user's network administrator, or the application
author/vendor.  to some degree it depends on the application.  But
nobody can do anything about the problem without some indication that
the problem exists and some way to distinguish one kind of problem
from another.

> I'd rather focus on getting the network to work better and more often,
> while reporting  accurately on failures if there is no alternative but
> to fail.

No question there, but if the failure is due to an administrative
prohibition (which is where I thought this started), it's hard
to see what it means to have the network work better and more often -
unless it's to discourage use of packet filtering.  :)

> > I don't see why TCP and/or UDP stacks can't provide such
> > interfaces to applications, even though of course this means
> > that there will need to be other interfaces (invisible to
> > applications) between TCP and IP and UDP and IP to pass that
> > information upstream.
> 
> They can't provide it because we don't have a model, or set of 
> abstractions, for providing it.  If it is important, maybe we 
> had better get started.

Has anyone made a list of important core problems that need to be
worked on?

Keith



From owner-ietf@ietf.org  Thu Apr 24 05:45:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09568;
	Thu, 24 Apr 2003 05:45:48 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198dXE-0000i7-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 06:00:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198dWc-0000f9-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 06:00:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09494
	for <ietf@ietf.org>; Thu, 24 Apr 2003 05:38:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198dDO-0004B5-00
	for ietf@ietf.org; Thu, 24 Apr 2003 05:40:26 -0400
Received: from prue.eim.surrey.ac.uk ([131.227.76.5] ident=exim)
	by ietf-mx with esmtp (Exim 4.12)
	id 198dDN-0004B2-00
	for ietf@ietf.org; Thu, 24 Apr 2003 05:40:25 -0400
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 198dDA-0001Jc-00; Thu, 24 Apr 2003 10:40:12 +0100
Date: Thu, 24 Apr 2003 10:40:08 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Jeffrey Race <jrace@attglobal.net>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
In-Reply-To: <E198LmR-0002rM-00@smtp01.mrf.mail.rcn.net>
Message-ID: <Pine.GSO.4.50.0304241034520.22615-100000@artemis.ee.surrey.ac.uk>
References: <E198LmR-0002rM-00@smtp01.mrf.mail.rcn.net>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-132.8 required=5.5
	tests=AWL,BAYES_00,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_PINE,
	      USER_IN_WHITELIST
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
X-Scanner: exiscan *198dDA-0001Jc-00*MzpPgvLf48Y* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 23 Apr 2003, Jeffrey Race wrote:

> On Mon, 21 Apr 2003 17:05:32 -0700, Dave Crocker wrote:
> >2. anyone who thinks the ietf formatting requirements are not easy has
> >not had to deal with very interesting formatting requirements.
>
> It may not be difficult but it is not trivial and it may well be beyond
> the ability of most non-techies.

Given that internet-drafts are intended to be technical documents,
does this matter?

(I think we need difficult hurdles like this as a constraint on
applications area work.)

L.

> In my word-processor (don't ask) there are two ways to embed form
> feeds and carriage returns in ASCII text files.  I never even knew
> this.
> I had to consult the gurus on
> the ap's discussion list to get the details.  I still have to review,
> test, view the resulting files in DEBUG, and finally format.  This is
> MANY hours of work.
>
> Not complaining, just so let it be written.
>
> Jeffrey Race

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Thu Apr 24 06:26:09 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10179;
	Thu, 24 Apr 2003 06:26:08 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198eDX-0002zn-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 06:44:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198eCp-0002xE-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 06:43:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10122
	for <ietf@ietf.org>; Thu, 24 Apr 2003 06:21:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198dta-0004LE-00
	for ietf@ietf.org; Thu, 24 Apr 2003 06:24:02 -0400
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 198dtZ-0004LB-00
	for ietf@ietf.org; Thu, 24 Apr 2003 06:24:01 -0400
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 198dtz-0001ax-00; Thu, 24 Apr 2003 11:24:27 +0100
Date: Thu, 24 Apr 2003 11:24:27 +0100
To: ietf@ietf.org
Cc: ipng@sunroof.eng.sun.com
Subject: Re: Architectural Considerations section in specs
Message-ID: <20030424102427.GD19568@fysh.org>
References: <20030423175937.3b28f432.moore@cs.utk.edu> <002701c309ef$5c64ced0$93b58742@ssprunk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <002701c309ef$5c64ced0$93b58742@ssprunk>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

Stephen Sprunk wrote:
>And you're conflating ambiguous addressing with scoping.

It seems that we have two different definitions of "scoping" in use.
One type of scope refers to the area in which an address is routeable;
this is about reachability and filtering.  The other type of scope is
the area in which an address can meaningfully be used to refer to the
addressed entity; this is about uniqueness and ambiguity.  Let's all,
please, be clear about which one we're arguing about at each point,
because a lot of the discussion here has been derailed by jumps between
them.

-zefram



From owner-ietf@ietf.org  Thu Apr 24 08:54:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14884;
	Thu, 24 Apr 2003 08:54:56 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198gRu-00078g-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 09:07:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198gR2-00074x-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 09:06:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14643
	for <ietf@ietf.org>; Thu, 24 Apr 2003 08:44:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198g7l-0005a7-00
	for ietf@ietf.org; Thu, 24 Apr 2003 08:46:49 -0400
Received: from kirk.rvdp.org ([80.126.101.63])
	by ietf-mx with esmtp (Exim 4.12)
	id 198g7k-0005Zy-00
	for ietf@ietf.org; Thu, 24 Apr 2003 08:46:49 -0400
Received: (from rvdp@localhost)
	by kirk.rvdp.org (8.11.6p2/8.11.6) id h3OCl5V24025
	for ietf@ietf.org; Thu, 24 Apr 2003 14:47:05 +0200 (CEST)
Date: Thu, 24 Apr 2003 14:47:05 +0200
From: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
To: ietf@ietf.org
Subject: question about draft-irtf-nsrg-report-09.txt
Message-ID: <20030424124705.GB23217@rvdp.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Sender: owner-ietf@ietf.org
Precedence: bulk

<quote>
4. Conclusions or Questions

   The NSRG was not able to come to unanimity as to whether an
   architectural change is needed.
</quote>

There has been a lot of discussion about the separation of identifiers
and locators (in various forms) on the multi6, ipv6 and ietf lists.
A lot of people seem to think this is in some form needed.

I would like to know the arguments against such a change. I don't
think the document has much text about this. It lists a lot of
questions. But most are more "how" than "why" questions. Are there
many people fundamentally against a change and if so, why?

	rvdp



From owner-ietf@ietf.org  Thu Apr 24 08:59:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15060;
	Thu, 24 Apr 2003 08:59:01 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198gae-0007Rr-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 09:16:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198cGL-0005OV-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 04:39:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07794
	for <ietf@ietf.org>; Thu, 24 Apr 2003 04:17:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198bx7-0003mG-00
	for ietf@ietf.org; Thu, 24 Apr 2003 04:19:33 -0400
Received: from theory.cs.uni-bonn.de ([131.220.4.211])
	by ietf-mx with esmtp (Exim 4.12)
	id 198bx2-0003mD-00
	for ietf@ietf.org; Thu, 24 Apr 2003 04:19:32 -0400
Received: from newton.cs.uni-bonn.de (newton.cs.uni-bonn.de [131.220.4.212])
	by theory.cs.uni-bonn.de (8.12.9/8.12.8) with SMTP id h3O8Jrqw028152;
	Thu, 24 Apr 2003 10:19:53 +0200 (MEST)
Received: (from ignatios@newton.cs.uni-bonn.de)
	by newton.cs.uni-bonn.de (mini_sendmail/1.3.2 21nov2002 nb1 15Feb2003);
	Thu, 24 Apr 2003 10:18:43 CEST
	(sender ignatios@newton.cs.uni-bonn.de)
Date: Thu, 24 Apr 2003 10:18:43 +0200
From: Ignatios Souvatzis <ignatios@theory.cs.uni-bonn.de>
To: ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A simple question
Message-ID: <20030424081843.GA22714@newton.cs.uni-bonn.de>
References: <20030422231209.438176f7.moore@cs.utk.edu> <20030423121730.18200.qmail@web10908.mail.yahoo.com> <20030423152607.79be279e.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=x-unknown;
	protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC"
Content-Disposition: inline
In-Reply-To: <20030423152607.79be279e.moore@cs.utk.edu>
User-Agent: Mutt/1.4.1i
Sender: owner-ietf@ietf.org
Precedence: bulk


--wRRV7LY7NUeQGEoC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Wed, Apr 23, 2003 at 03:26:07PM -0400, Keith Moore wrote:
> > I would be thrilled if we spent some time thinking about ICMP in
> > an architectural way - however beautiful it was before ICMP
> > black holing, what we have now isn't consistently usable today.
> > We're spending time on point solutions (Matt Mathis on non-ICMP
> > path MTU discovery as one example), but is this the best we can
> > do?
>=20
> I don't think we're likely to be able to dispense with ICMP.  Maybe we
> can find more ways to make it more trustworthy.  Or maybe we just need
> to discourage people from filtering it.

I don't understand why this is even a point of discussion. Next you hear
some people will like to globally filter TCP RST - will you rewrite TCP
to work without that?

Regards,
	-is

--wRRV7LY7NUeQGEoC
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQEVAgUBPqed4TCn4om+4LhpAQFlQwgAtQ/zBELpGwtwyys49rAmQGS8GPPjdPRk
/dX6xs96ff3Aj4L0c15GI+3GUxR/0WwkF6GqWCJGcGjaXH4kRxdGvK8jgrL83X3A
mvRyDNsC+Vwbzwpg4U5v84OgcmBbuF4UFsEr92zWl/n9+XFP2rmZ91XYP5TtV423
jz3mBzNBbhmsgIo7xHA6DBPvDAowPpMP3wzWwPiL2XJntJyHsnoI/ev9Bhy2eccf
2adpWFFuPjJU+iISH2FYeFrG0e0SWteZFwMlxE5xQryz6bOjCHxKB9UlkaToSmQR
VS6whppM0tGFoKISjwQA0WJBbTGLcL2e2r2Qa6GUJh4VyyHnZqBSIw==
=cT6g
-----END PGP SIGNATURE-----

--wRRV7LY7NUeQGEoC--





From owner-ietf@ietf.org  Thu Apr 24 08:59:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15107;
	Thu, 24 Apr 2003 08:59:27 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198gae-0007Rx-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 09:16:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198NOz-0000PS-00
	for ietf@ran.ietf.org; Wed, 23 Apr 2003 12:47:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25230
	for <ietf@ietf.org>; Wed, 23 Apr 2003 12:25:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198N5w-0005IR-00
	for ietf@ietf.org; Wed, 23 Apr 2003 12:27:40 -0400
Received: from mxout1.cac.washington.edu ([140.142.32.134])
	by ietf-mx with esmtp (Exim 4.12)
	id 198N5v-0005IO-00
	for ietf@ietf.org; Wed, 23 Apr 2003 12:27:39 -0400
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout1.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h3NGS2RG000694;
	Wed, 23 Apr 2003 09:28:02 -0700
Received: from DGX-104 (D-140-142-110-177.dhcp4.washington.edu [140.142.110.177])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h3NGS1Q0009964
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 23 Apr 2003 09:28:01 -0700
Date: Wed, 23 Apr 2003 09:28:01 -0700 (Pacific Standard Time)
From: Terry Gray <gray@washington.edu>
To: ietf@ietf.org
Subject: Re: A simple question
In-Reply-To: <8986EB42-755B-11D7-89E4-000393414368@yahoo.com>
Message-ID: <Pine.WNT.4.55.0304230757330.4616@DGX-104>
References: <8986EB42-755B-11D7-89E4-000393414368@yahoo.com>
Slogan: "I get enough exercise just pushing my luck."
Organization: University of Washington;  Computing & Communications
X-X-Sender: gray@mailer23.u.washington.edu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


> On Tuesday, April 22, 2003, at 06:57  PM, Spencer Dawkins wrote:
>
> > I agree with your take from the network side, I'm thinking Terry
> > may be looking at it from the applications side (what's the
> > difference between one perfectly lovely address that fails
> > unpredictably and another perfectly lovely address that also
> > fails unpredictably? and the unknowable firewall topology is
> > probably within a first approximation of the unknowable site
> > topology).

On Wed, 23 Apr 2003, S Woodside wrote:
>
> The differences:
> - firewalls are a necessary evil for security, whereas site locals are
> (maybe) not
> - firewalls are a simple on/off switch and easy to change, whereas site
> locals have complex state and are hard to change
>
> Firewalls and NAT / site-locals might seem to be entangled, but it's
> just a coincidence. They both work best in the same place in the
> network, so many firewalls also do NAT.

Simon,
I think there is more entanglement than you do, because sometimes
local addresses are used as part of a security strategy aimed at
avoiding the need for conventional middlebox firewalls.  (A google
search for "logic firewall" will point to one example of what I'm
talking about.)

I'm looking at this from the perspective of diagnosing alleged
network problems.

It seems to me that conventional middlebox firewalls utterly destroy
end-to-end transparency, and with it, any hope of preserving the
all-ports-are-equal "network utility" model that has served us so
well... whereas, local addresses merely "seriously undermine" that
model.  Do you prefer vinegar or castor oil?  (And can anyone offer me
some honey?!)

If I have to choose between random locally-controlled firewalls
sprinkled throughout my network infrastructure vs. having hosts with
local addresses, I would much prefer to live with the latter.  From an
end-to-end network management perspective, neither is a very happy
scenario, but my preference is based on having done both experiments.

At least with local addresses, some semblence of the network utility
model can be preserved: a technician with a globally-configured laptop
can run iperf tests from any outlet and not wonder whether some
intervening firewall is failing to preserve the window scaling bit in
the tcp header.  (And the NOC doesn't periodically lose visibility
to devices beyond the firewall because of accidental misconfiguration
by the firewall owner.)

Networking is all about connecting things; security is all about
isolating things.  As far as I can tell, a satisfactory compromise
still eludes us.  (Sometimes in the non-cyber world, too, as SARS
and 9/11 remind us.)

So, apart from the renumbering/provider-independence arguments for
local addresses, I do believe there is a security element too, which
in my mind adds fuel to the architectural debate over e2e
transparency.  There are a range of ways local addresses can play into
the security space; some involve NAT, some do not, but at our site we
already have compelling evidence that offering some defense-in-depth
security alternatives involving local-addressing can greatly diminish
the clammer for *conventional* perimeter firewalls, and thus, reduce
the pressure on us to abandon the network utility model.

Who do we call about the destruction of the network utility model that
has served us so well?  As an over-simplified generalization, I think
the OS vendors have to take the rap. By allowing the accretion of an
installed base of end systems that is by-and-large not "Internet
safe", they have unwittingly given credence to the widespread view
that "it was the networking guys who brought us all these security
problems, so it should be the networking guys who solve the security
problems."  This in turn inevitably leads to middlebox perimeter
defense "panaceas", and thence to the search for less
network-destructive alternatives.  My current hypothesis is that local
addresses can play a role in that (slightly) less-destructive solution
space.  But I continue to seek/wish-for better choices.  (Meanwhile,
I'll just slip into my asbestos suit, and debate with myself the
wisdom of sending this message :)

NB: I'm focused on singly-addressed hosts; I have no wisdom to offer
regarding the multiply-addressed host problem/controversy.

-teg





From owner-ietf@ietf.org  Thu Apr 24 11:06:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19125;
	Thu, 24 Apr 2003 11:06:41 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198iWb-0003sl-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 11:20:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198iWO-0003rb-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 11:20:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAB18901
	for <ietf@ietf.org>; Thu, 24 Apr 2003 10:58:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198iD6-0006Ny-00
	for ietf@ietf.org; Thu, 24 Apr 2003 11:00:28 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 198iD5-0006Na-00
	for ietf@ietf.org; Thu, 24 Apr 2003 11:00:27 -0400
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h3OF0IlY028110;
	Thu, 24 Apr 2003 11:00:18 -0400 (EDT)
Message-Id: <200304241500.h3OF0IlY028110@rtp-core-1.cisco.com>
To: Keith Moore <moore@cs.utk.edu>
cc: "Stephen Sprunk" <stephen@sprunk.org>, alh-ietf@tndh.net, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: Architectural Considerations section in specs 
In-reply-to: Your message of Wed, 23 Apr 2003 22:12:35 -0400.
             <20030423221235.5e8fe4b7.moore@cs.utk.edu> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 24 Apr 2003 11:00:17 -0400
From: Eric Rosen <erosen@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


While I  enjoy seeing the IPv6 guys  arguing with each other,  I don't think
that anyone is deliberately spreading incorrect information here. 

There seems to be general  agreement that there are multi-party applications
in which A needs to  tell B to talk to C.  Thus A needs  to have some way to
unique identify C to B. 

However,  because   of  communications  policy   restrictions,  neither  the
application  layer nor  the network  layer can  know whether  B  is actually
allowed to  talk to C.   So it seems  that these applications can  only work
when  deployed  within  a  policy  domain.  (Policy  domain  boundaries  are
generally marked  by such things  as firewall and security  gateways, things
which  are  hated  by  the  purists because  they  eliminate  communications
transparency.)  The fact that  A gives B an address of C  rather than a name
of  C  doesn't seem  relevant  at  all; after  all,  names  just resolve  to
addresses;  I think the  name vs.  address issue  is a  red herring  in this
context. 

The existence of policy domains seems to restrict the applicability of these
multi-party referring applications, especially as  the app itself has no way
of knowing whether it is crossing policy domain boundaries.  

So  what does  this  have to  do  with site-local  addresses?   I think  two
arguments have been made.

1. Because site-local  addresses are  ambiguous, if  A passes  a site-local
   address to B, B may not be able to use it to talk to C. 

   I  think the reply  that has  been made  to this  is that  the site-local
   addresses have to  be unambiguous within a particular  policy domain, and
   it is a  management function to ensure that this is  the case.  Since the
   apps in  questions are applicable only  within a policy  domain, the fact
   that the  addresses are ambiguous  outside that domain doesn't  makes the
   apps any less useful than they already are. 

2. A system  with a site-local address is likely to  have other addresses as
   well, and it is  a bad thing for a system to  have more than one address,
   because the apps have no way of knowing which address is the right one to
   distribute. 

   I think the reply to this is  that this horse escaped from the barn about
   20 years  ago, and  anyway, choice of  address is a  management function.
   That  is, the app  needs to  be told  through some  sort of  config which
   addresses to use when.

It's been claimed that if non-ambiguous addresses are used, at least the app
can tell when  communication is being prevented due  to policy restrictions,
as it  will receive ICMP  messages with appropriate  diagnostic information.
Unfortunately, this  presumes more from  the network layer than  the network
layer actually  provides.  ICMP messages  may be generated due  to transient
problems, they may  fail to be generated at all  (for "security reasons", or
due to limitations on the rate  of ICMP generation), they may be dropped in
the network,  etc.  When communication fails,  there is no  reliable way for
the endsystems to determine why it has failed. 

So I  don't really  think the  case against site-locals  has been  made here
(which is  not to say that  there isn't a  case against them based  on other
considerations). 

I think the  underlying problem is that our  comms architecture doesn't take
the policy restrictions  into account at all, and folks  tend to assume that
this needs  to be accounted for  at some other  layer than the one  they are
most interested in.  This generates  frustration, and creates a high heat to
light ratio.   Usually everyone blames  it on NAT,  so it's nice to  see the
same issue come up in an IPv6 non-NAT context. 




From owner-ietf@ietf.org  Thu Apr 24 11:20:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19649;
	Thu, 24 Apr 2003 11:20:20 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198io1-0004iT-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 11:38:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198ins-0004h4-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 11:38:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19546
	for <ietf@ietf.org>; Thu, 24 Apr 2003 11:16:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198iUa-0006X7-00
	for ietf@ietf.org; Thu, 24 Apr 2003 11:18:32 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 198iUZ-0006Wy-00
	for ietf@ietf.org; Thu, 24 Apr 2003 11:18:31 -0400
Received: from edison.cisco.com (edison.cisco.com [171.70.144.164])
	by sj-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h3OFIQ08019310;
	Thu, 24 Apr 2003 08:18:27 -0700 (PDT)
Received: from cisco.com (sjc-vpn2-765.cisco.com [10.21.114.253]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id IAA29313; Thu, 24 Apr 2003 08:18:25 -0700 (PDT)
Message-ID: <3EA80042.7040301@cisco.com>
Date: Thu, 24 Apr 2003 08:18:26 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
CC: ietf@ietf.org
Subject: Re: question about draft-irtf-nsrg-report-09.txt
References: <20030424124705.GB23217@rvdp.org>
In-Reply-To: <20030424124705.GB23217@rvdp.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

In answer to your questions, various people felt that IPv6 was enough, 
and that the IP address could be used as the end point identifier.  Even 
in the case of mobility it was felt that MIPv6 would serve the purpose 
of a stable identifier.  As is pointed out in the draft, the flaw in 
this idea is that even the MIPv6 MN address is tied to the topology.

Eliot

Ronald van der Pol wrote:

> <quote>
> 4. Conclusions or Questions
> 
>    The NSRG was not able to come to unanimity as to whether an
>    architectural change is needed.
> </quote>
> 
> There has been a lot of discussion about the separation of identifiers
> and locators (in various forms) on the multi6, ipv6 and ietf lists.
> A lot of people seem to think this is in some form needed.
> 
> I would like to know the arguments against such a change. I don't
> think the document has much text about this. It lists a lot of
> questions. But most are more "how" than "why" questions. Are there
> many people fundamentally against a change and if so, why?
> 
> 	rvdp
> 
> 
> 





From owner-ietf@ietf.org  Thu Apr 24 11:42:02 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20362;
	Thu, 24 Apr 2003 11:42:01 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198j9J-0005YZ-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 12:00:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198j93-0005XK-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 12:00:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20240
	for <ietf@ietf.org>; Thu, 24 Apr 2003 11:38:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198ipl-0006hs-00
	for ietf@ietf.org; Thu, 24 Apr 2003 11:40:25 -0400
Received: from gull.mail.pas.earthlink.net ([207.217.120.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 198ipl-0006ho-00
	for ietf@ietf.org; Thu, 24 Apr 2003 11:40:25 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 198iq7-000681-00; Thu, 24 Apr 2003 08:40:47 -0700
Date: Thu, 24 Apr 2003 11:40:11 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: question about draft-irtf-nsrg-report-09.txt
Message-Id: <20030424114011.1583fdbc.moore@cs.utk.edu>
In-Reply-To: <20030424124705.GB23217@rvdp.org>
References: <20030424124705.GB23217@rvdp.org>
X-Mailer: Sylpheed version 0.8.11 (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

> There has been a lot of discussion about the separation of identifiers
> and locators (in various forms) on the multi6, ipv6 and ietf lists.
> A lot of people seem to think this is in some form needed.
> 
> I would like to know the arguments against such a change.

nobody has worked out a complete solution.  if you want to separate
identifiers and locators you immediately need to build a reliable system to
map between the two - where reliable means: fast, up-to-date, highly
available, provides repeatable results across the entire network.  

for compatibility the identifiers need to be the same size as IP addresses,
yet distinct from them.   that way, apps just get identifiers rather than
addresses from DNS lookups.

ideally the mapping happens implicitly rather than explicitly - i.e. it
happens as a side effect of an app treating an identifier as a destination
rather than by having to send a query and wait for a response before
transmitting the packet.  also, you don't want to wait for the query to
complete before sending packets - triangle routing and subsequent redirects
are better.

a lot of people think DNS names can be the identifiers, but besides being the
wrong size, they're already too overloaded for that, plus DNS is too slow and
not reliable enough. part of the reason that DNS is slow and unreliable is
that it's too widely distributed.  that and there are a lot of tricks being
played with DNS that could get in the way.

there are a lot of good ideas in HIP but it doesn't address the
identifier-to-locator mapping problem.

the closest thing we have to a working solution today is mobile IP, but
purists tend to cringe when I say things like that in their presence.  for
stateful transport protocols we might be able to find a way to dispense with
tunneling and let (e.g.) TCP operate in terms of the identifiers rather than
the locators, even though the IP packets still contain the locators.

summary of problems that need to be solved:

1. security
2. fast, robust, highly available identifier-to-locator mapping layer
3. arranging for hosts (or perhaps routers) to find the mapping layer for
   a particular identifier
4. delegation and assignment of identifiers
5. making transport protocols work in terms of identifiers rather than
   locators while minimizing overhead

technically, I think it's doable.   whether we can actually agree
on a solution is a different question.

Keith





From owner-ietf@ietf.org  Thu Apr 24 12:31:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22434;
	Thu, 24 Apr 2003 12:31:48 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198jtm-00079B-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 12:48:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198jtU-00077p-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 12:48:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22298
	for <ietf@ietf.org>; Thu, 24 Apr 2003 12:26:04 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198jaB-00072s-00
	for ietf@ietf.org; Thu, 24 Apr 2003 12:28:23 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 198jaB-00072p-00
	for ietf@ietf.org; Thu, 24 Apr 2003 12:28:23 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h3OGScvj004916;
	Thu, 24 Apr 2003 12:28:38 -0400
Message-Id: <200304241628.h3OGScvj004916@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: erosen@cisco.com
Cc: ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: Architectural Considerations section in specs 
In-Reply-To: Your message of "Thu, 24 Apr 2003 11:00:17 EDT."
             <200304241500.h3OF0IlY028110@rtp-core-1.cisco.com> 
References: <200304241500.h3OF0IlY028110@rtp-core-1.cisco.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1116263340P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 24 Apr 2003 12:28:38 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1116263340P
Content-Type: text/plain; charset=us-ascii

On Thu, 24 Apr 2003 11:00:17 EDT, Eric Rosen said:
> transparency.)  The fact that  A gives B an address of C  rather than a name
> of  C  doesn't seem  relevant  at  all; after  all,  names  just resolve  to
> addresses;  I think the  name vs.  address issue  is a  red herring  in this
> context.

I'm not at ALL convinced it's a red herring in the least.

In fact, it may be relevant that it uses an address rather than the name of C,
because it's certainly conceivable that A gives B a name which *when resolved
by B* results in something that can get to C.

One example:  Akamai DNS...

(OK, all you 'The DNS must be consistent' fanatics can shoot me now ;)

--==_Exmh_-1116263340P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+qBC2cC3lWbTT17ARAs9qAKD4k5meR/dV+xipF1xuTx0HJ6pDZwCffKS+
L3Izkyt2c2yf/dTtMJYoMqg=
=PZAz
-----END PGP SIGNATURE-----

--==_Exmh_-1116263340P--



From owner-ietf@ietf.org  Thu Apr 24 12:31:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22433;
	Thu, 24 Apr 2003 12:31:48 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198jw0-0007Bz-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 12:50:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198jtu-00079D-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 12:48:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22303
	for <ietf@ietf.org>; Thu, 24 Apr 2003 12:26:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198jab-00072y-00
	for ietf@ietf.org; Thu, 24 Apr 2003 12:28:49 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 198jab-00072v-00
	for ietf@ietf.org; Thu, 24 Apr 2003 12:28:49 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h3OGT9tU002487;
	Thu, 24 Apr 2003 12:29:09 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h3OGT9Hi002486;
	Thu, 24 Apr 2003 12:29:09 -0400
Date: Thu, 24 Apr 2003 12:29:09 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200304241629.h3OGT9Hi002486@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: question about draft-irtf-nsrg-report-09.txt
Cc: jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: Keith Moore <moore@cs.utk.edu>

    > you immediately need to build a reliable system to map between the
    > two - where reliable means: fast, up-to-date, highly available,
    > provides repeatable results across the entire network.

Many people keep claiming this, but I've yet to see the case clearly laid
out as to why. Let me explain.

If you start with a design which basically replicates the capabilities of
the system we have today, you arrange it so that whatever transaction (in
the loose sense) that provided you with the IPvn address instead provides
you with the locator/identifier pair. So, if you did a DNS lookup, that
would give you back both; if you're a server and someone opens a
connection to you, that ICP packed would give you both.

Well, that's not a very interesting system, because it just replicates the
capabilities of the system we already have. To make it useful/interesting,
you want to be able to change the binding between the two.

Well, for many cases of current interest, you can in fact do that without
having a mapping system available. E.g. for multi-homing (done with
multiple addresses), at ICP time the multi-homed entity provides all of
its addresses. Etc, etc - I won't go into all the details now.


I'm *not* saying that I'm *sure* we *never* have need of such a mapping
system; I'm just saying that I don't think anyone has sat down and really
tried to work through the details and see how far you can get without one.

	Noel



From owner-ietf@ietf.org  Thu Apr 24 14:15:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25769;
	Thu, 24 Apr 2003 14:15:31 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198lUT-00023B-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 14:30:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198lU2-00021w-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 14:30:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25671
	for <ietf@ietf.org>; Thu, 24 Apr 2003 14:07:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198lAi-000008-00
	for ietf@ietf.org; Thu, 24 Apr 2003 14:10:12 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198lAi-000005-00
	for ietf@ietf.org; Thu, 24 Apr 2003 14:10:12 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3OIAUv11384;
        Thu, 24 Apr 2003 14:10:30 -0400 (EDT)
Date: Thu, 24 Apr 2003 14:07:34 -0400
From: Keith Moore <moore@cs.utk.edu>
To: erosen@cisco.com
Cc: moore@cs.utk.edu, stephen@sprunk.org, alh-ietf@tndh.net, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: Architectural Considerations section in specs
Message-Id: <20030424140734.55c76b77.moore@cs.utk.edu>
In-Reply-To: <200304241500.h3OF0IlY028110@rtp-core-1.cisco.com>
References: <20030423221235.5e8fe4b7.moore@cs.utk.edu>
	<200304241500.h3OF0IlY028110@rtp-core-1.cisco.com>
X-Mailer: Sylpheed version 0.8.11 (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

> However,  because   of  communications  policy   restrictions, 
> neither  the application  layer nor  the network  layer can  know
> whether  B  is actually allowed to  talk to C.   So it seems  that
> these applications can  only work when  deployed  within  a  policy 
> domain.  

one question here is whether there is some burden on applications to
try to find a path between hosts B and C, say by address and/or
interface selection, or whether the burden is entirely on the network. 

one of the problems with our current notion of 'policy domains' is that
they are so inflexible as a security mechanism that people demand, out
of necessity, that some applications be able to work across them.  

so no, it's not reasonable to assume that apps that do referrals are
only expected to work within a single policy domain.

>  The fact that  A gives B an address of C  rather than
> a name of  C  doesn't seem  relevant  at  all; after  all,  names 
> just resolve  to addresses;  I think the  name vs.  address issue  is
> a  red herring  in this context. 

that's because you haven't had to deal with DNS unreliability,
imprecision, inconsistency, and performance issues.

> 2. A system  with a site-local address is likely to  have other
> addresses as
>    well, and it is  a bad thing for a system to  have more than one
>    address, because the apps have no way of knowing which address is
>    the right one to distribute. 
> 
>    I think the reply to this is  that this horse escaped from the barn
>    about 20 years  ago

not in a general sense.  even today, the vast majority of IPv4 hosts
have a distinguished IP address that is usable from everywhere that's
supposed to be able to talk to the host.

> , and  anyway, choice of  address is a 
>    management function. That  is, the app  needs to  be told  through
>    some  sort of  config which addresses to use when.

which is a management nightmare.

> It's been claimed that if non-ambiguous addresses are used, at least
> the app can tell when  communication is being prevented due  to policy
> restrictions, as it  will receive ICMP  messages with appropriate 
> diagnostic information. Unfortunately, this  presumes more from  the
> network layer than  the network layer actually  provides.  ICMP
> messages  may be generated due  to transient problems, they may  fail
> to be generated at all  (for "security reasons", or due to limitations
> on the rate  of ICMP generation), they may be dropped in the network, 
> etc.  When communication fails,  there is no  reliable way for the
> endsystems to determine why it has failed. 

no, but when the connection times out right after the host has
received 3 or 4 "prohibited" ICMP messages in response to traffic sent
on that connection, it's a pretty good clue.

Keith



From owner-ietf@ietf.org  Thu Apr 24 15:17:58 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29275;
	Thu, 24 Apr 2003 15:17:58 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198mTp-0001cB-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 15:34:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198mSw-0001Mr-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 15:33:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28642
	for <ietf@ietf.org>; Thu, 24 Apr 2003 15:10:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198m9b-0000N5-00
	for ietf@ietf.org; Thu, 24 Apr 2003 15:13:07 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198m9b-0000N2-00
	for ietf@ietf.org; Thu, 24 Apr 2003 15:13:07 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3OJDXv11481;
        Thu, 24 Apr 2003 15:13:33 -0400 (EDT)
Date: Thu, 24 Apr 2003 15:13:33 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: question about draft-irtf-nsrg-report-09.txt
Message-Id: <20030424151333.7947b81f.moore@cs.utk.edu>
In-Reply-To: <200304241629.h3OGT9Hi002486@ginger.lcs.mit.edu>
References: <200304241629.h3OGT9Hi002486@ginger.lcs.mit.edu>
X-Mailer: Sylpheed version 0.8.11 (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

>     > you immediately need to build a reliable system to map between
>     > the two - where reliable means: fast, up-to-date, highly
>     > available, provides repeatable results across the entire
>     > network.
> 
> Many people keep claiming this, but I've yet to see the case clearly
> laid out as to why. Let me explain.
> 
> If you start with a design which basically replicates the capabilities
> of the system we have today, you arrange it so that whatever
> transaction (in the loose sense) that provided you with the IPvn
> address instead provides you with the locator/identifier pair.

this really only works if the transaction is repeatable (with all of the
usual caveats about precision, reliability, efficiency, and consistency)
by any of the peers that might get the locator/identifier pair, and
might need a different locator (or a change to a locator) at some point.

and this tends to mean that you want to sepearate the step that gets
you the precise endpoint identifier from the step that gets you
locators.  of course, if you get an initial set of locators along with
the identifier, this is a useful optimization, but it doesn't mean you
can dispense with the capability to do an identifier->locator mapping in
the future.

> Well, that's not a very interesting system, because it just replicates
> the capabilities of the system we already have. To make it
> useful/interesting, you want to be able to change the binding between
> the two.
> 
> Well, for many cases of current interest, you can in fact do that
> without having a mapping system available. E.g. for multi-homing (done
> with multiple addresses), at ICP time the multi-homed entity provides
> all of its addresses. Etc, etc - I won't go into all the details now.

this works just fine if all of the addresses always work.  it's when one
of the addresses fails to work that it causes problems, especially when
you can't tell whether the addresses returned in response to a
subsequent query really refers to the same host you were talking to, or
just a different host that provided the same service. 

Keith
 



From owner-ietf@ietf.org  Thu Apr 24 15:59:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00790;
	Thu, 24 Apr 2003 15:59:42 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198n8F-0004T1-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 16:15:47 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198n7S-0004Rk-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 16:14:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00491
	for <ietf@ietf.org>; Thu, 24 Apr 2003 15:52:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198mo6-0000gC-00
	for ietf@ietf.org; Thu, 24 Apr 2003 15:54:58 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198mo6-0000g5-00
	for ietf@ietf.org; Thu, 24 Apr 2003 15:54:58 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S262F3> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 24 Apr 2003 12:55:24 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: <erosen@cisco.com>, "'Keith Moore'" <moore@cs.utk.edu>
Cc: "'Stephen Sprunk'" <stephen@sprunk.org>, <ietf@ietf.org>,
        <ipng@sunroof.eng.sun.com>
Subject: RE: Architectural Considerations section in specs 
Date: Thu, 24 Apr 2003 12:55:25 -0700
Message-ID: <042801c30a9b$72a91c80$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <200304241500.h3OF0IlY028110@rtp-core-1.cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA00790

Eric Rosen wrote:
> ... The fact that  A gives B an address of C  
> rather than a name of  C  doesn't seem  relevant  at  all; 
> after  all,  names  just resolve  to addresses;  I think the  
> name vs.  address issue  is a  red herring  in this context. 

If A gave the entire list of choices to B, you would be right. The
problem is that A will generally give B the one it chose, since it
believes that one works. 

> 
> The existence of policy domains seems to restrict the 
> applicability of these multi-party referring applications, 
> especially as  the app itself has no way of knowing whether 
> it is crossing policy domain boundaries.  

This is right in the general case. We have toyed with the idea of
preventing mixed  scope connections which would allow the app to clearly
know. 

> 
> So  what does  this  have to  do  with site-local  addresses? 
>   I think  two
> arguments have been made.
> 
> 1. Because site-local  addresses are  ambiguous, if  A passes 
>  a site-local
>    address to B, B may not be able to use it to talk to C. 
> 
>    I  think the reply  that has  been made  to this  is that  
> the site-local
>    addresses have to  be unambiguous within a particular  
> policy domain, and
>    it is a  management function to ensure that this is  the 
> case.  Since the
>    apps in  questions are applicable only  within a policy  
> domain, the fact
>    that the  addresses are ambiguous  outside that domain 
> doesn't  makes the
>    apps any less useful than they already are. 

This is right on. 

> 
> 2. A system  with a site-local address is likely to  have 
> other addresses as
>    well, and it is  a bad thing for a system to  have more 
> than one address,
>    because the apps have no way of knowing which address is 
> the right one to
>    distribute. 
> 
>    I think the reply to this is  that this horse escaped from 
> the barn about
>    20 years  ago, and  anyway, choice of  address is a  
> management function.
>    That  is, the app  needs to  be told  through some  sort 
> of  config which
>    addresses to use when.

The intent of the sending rules is to provide the default version of
that config. There are arguments that those don't work for the mobile
node case, but I would argue that the mobile node has to know when it is
away from home to inform its HA, so we could add a rule that MNs don't
use local scope addresses when away from home. 

> 
> It's been claimed that if non-ambiguous addresses are used, 
> at least the app can tell when  communication is being 
> prevented due  to policy restrictions, as it  will receive 
> ICMP  messages with appropriate  diagnostic information. 
> Unfortunately, this  presumes more from  the network layer 
> than  the network layer actually  provides.  ICMP messages  
> may be generated due  to transient problems, they may  fail 
> to be generated at all  (for "security reasons", or due to 
> limitations on the rate  of ICMP generation), they may be 
> dropped in the network,  etc.  When communication fails,  
> there is no  reliable way for the endsystems to determine why 
> it has failed. 

In addition, it doesn't solve the issue that A will pass B the address
that it is using, rather than the possible set. B needs to derive its
own view of how to reach C even when globally unique addresses are used.

> 
> So I  don't really  think the  case against site-locals  has 
> been  made here (which is  not to say that  there isn't a  
> case against them based  on other considerations). 
> 
> I think the  underlying problem is that our  comms 
> architecture doesn't take the policy restrictions  into 
> account at all, and folks  tend to assume that this needs  to 
> be accounted for  at some other  layer than the one  they are 
> most interested in.  This generates  frustration, and creates 
> a high heat to
> light ratio.   Usually everyone blames  it on NAT,  so it's 
> nice to  see the
> same issue come up in an IPv6 non-NAT context. 
> 

I am not trying to place blame, but I would word it differently. While
the architecture has all along allowed for differentiating policy
restrictions, the app community chose to simplify their effort by
ignoring that there were policy differences in the lower layers. This
worked as long as the world was dominated by client/server oriented 2
party apps. In a world of multi-party apps, the policy differences of
the lower layers are exposed and we need to rethink how apps deal with
that reality. 

Tony 






From owner-ietf@ietf.org  Thu Apr 24 15:59:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00791;
	Thu, 24 Apr 2003 15:59:42 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198n8F-0004T7-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 16:15:47 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198n7X-0004Rm-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 16:15:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00496
	for <ietf@ietf.org>; Thu, 24 Apr 2003 15:52:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198moC-0000gM-00
	for ietf@ietf.org; Thu, 24 Apr 2003 15:55:04 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198moB-0000gI-00
	for ietf@ietf.org; Thu, 24 Apr 2003 15:55:03 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S262F4> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 24 Apr 2003 12:55:29 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Shannon -jj Behrens'" <jj@nttmcl.com>
Cc: "'Keith Moore'" <moore@cs.utk.edu>, <john-ietf@jck.com>, <dts@senie.com>,
        <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
Subject: RE: A follow up question
Date: Thu, 24 Apr 2003 12:55:29 -0700
Message-ID: <042901c30a9b$757ed1c0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030424162808.GA52759@alicia.nttmcl.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA00791

Shannon -jj Behrens wrote:
> Please forgive my rough tone (in fact, I have great respect 
> for you as an engineer), 

I try to avoid taking any IETF discussions personally, one way or the
other.

> but it would be much more 
> interesting if you wrote a document that provided solutions 
> for all of the problems that people have claimed site-locals 
> cause.  

I understand that is what some people want, but I think we need to first
agree on the problems that need solving. We have many opinions on why SL
creates problems, but a blatant lack of recognition of the problems that
need to be solved. 

> While I hear you saying that the wg should replace 
> all of the features that site-locals provide before removing 
> them from the architecture, I challenge you to instead take 
> the impetus of fully specifying site-locals.  

I believe the first step to doing that is to agree on the problems that
need solving, then see if there are alternative approaches. 

> I do believe, 
> based on other comments on the list, that such a challenge 
> has existed for five years and has yet to be answered.  
> Having fully specified site-locals, I do believe the wg would 
> be much more willing to accept them into the architecture.  

I thought we were going there with the scoped arch document, but lacking
agreement on the problems to be solved, it became easier to spread FUD
and give up on addressing the issues than to sit down and work them
through.

> Although I clearly am not capable of providing the full list 
> of questions that you must answer, perhaps the following 
> questions are helpful:
> 
> o In light of the fact that not every host has a DNS name, 
> how do you propose multi-party P2P applications should do 
> referrals? It would be helpful if you established the normal 
> mode of operation for such situations.

As I said in the note to JCK, I have been imprecise about 'name' so
whatever the app uses to get a handle from the local stack is what it
needs to pass around. Doing otherwise ignores the reality that the
network does not look the same from all points.

> 
> o Should site-locals be put in DNS?  Should multiple views of 
> DNS be used?  If 
> so, how do you address the apparent apprehension in the DNS 
> community toward multiple views (I don't know about this 
> first-hand--I've only read about it 
> from this list)?  Should zone information be kept in DNS?

Implementation details of a multi-faced DNS are best addressed by those
that already ship them. Any service that provides topology specific
information has to do that with an understanding of the topology being
described by that information. 

> 
> o Do you foresee all nodes being multi-site nodes?  

Certainly not all, my light switch should not be in any site except my
house. At the same time I may want it to be in multiple scopes, so I can
get to it and turn on the driveway light from the car as I approach.

> If I'm at 
> work and wish to 
> use both my work network *and* my home network via a VPN 
> connection, I expect I would want my laptop to be a 
> multi-site node.  If this is the case, do I 
> need to use %interface_name at the end of all IP's I give to 
> applications I 
> use?  How would DNS lookups work on a multi-site node if 
> site-locals are stored in DNS?

The name resolver would have to track which interface / site it got
answers from because any limited scope resolution is only applicable in
that interface / site context. 

> 
> o If, as you say, we should provide site-locals because, "we 
> need to meet the network manager at his comfort zone and 
> provide a familiar tool," how do we 
> convince the network manager not to use NAT since this is 
> also a familiar tool in most people's comfort zone.  I'm not 
> willing to argue that site-locals 
> necessarily lead to NAT, but many people are, so you should 
> probably have some answer. 

Leading people away from something comfortable requires providing
something that meets the same basic need and is easier/cheaper/more
comfortable. Many use NAT because they can't get STABLE addresses
otherwise, and NAT is simply the cost of getting that. Providing STABLE
local use prefixes simultaneously with global prefixes that may change
over time is a cheaper way to meet the need for STABLE addresses. 

* I emphasize STABLE because that is a invariant requirement by many
managers of large networks. 

> 
> o Do you envision support for Margaret's idea of multiple 
> concentric rings of security (possibly using site-locals)?  
> If a node in the outermost ring is not able to talk to a node 
> in the innermost ring using a site-local address because of 
> filtering, but is permitted to use a global address, how 
> shall applications react when the site-local "hint" is 
> actually misleading?

Personally I consider those security zones as different sites. This gets
into the poor definition of 'site', but we were intentionally vague
there. There is no difference between an FEC0 or 2001-w/Bellovin-Zill
flag prefix in how one would solve this problem. The fact that SL does
not provide multiple concentric security zones is not a failure of SL,
because that was not a design requirement (again we need to agree on the
problems to be solved). 

> 
> Again, I'm sure there are many more such questions, and I 
> think it would be 
> helpful (and in fact requisite) that you answer such 
> questions in an Internet Draft in order to achieve your goal 
> of restoring site-locals to the 
> architecture.  I thank you for your time and *patience* if 
> you have made it all the way through this message.

I agree that we need answers to all these issues, and that was the
intent of the scoped arch doc. Once people realize that they continue to
exist for any local use prefix, we will stop the nonsense about SL is
the evil that causes the problems and get back to developing the needed
documents.

Tony 





From owner-ietf@ietf.org  Thu Apr 24 15:59:46 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00846;
	Thu, 24 Apr 2003 15:59:46 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198n8E-0004Sv-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 16:15:46 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198n7K-0004Ri-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 16:14:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00482
	for <ietf@ietf.org>; Thu, 24 Apr 2003 15:52:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198mnz-0000g1-00
	for ietf@ietf.org; Thu, 24 Apr 2003 15:54:51 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198mny-0000fy-00
	for ietf@ietf.org; Thu, 24 Apr 2003 15:54:50 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S262F2> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 24 Apr 2003 12:55:15 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'John C Klensin'" <john-ietf@jck.com>
Cc: "'Daniel Senie'" <dts@senie.com>, <ietf@ietf.org>,
        <ipng@sunroof.eng.sun.com>
Subject: RE: A follow up question
Date: Thu, 24 Apr 2003 12:55:16 -0700
Message-ID: <042701c30a9b$6d3dc840$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <299162132.1051138523@p3.JCK.COM>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA00846

John C Klensin wrote:
> I want to leave most of that discussion for some ARIN-related 
> list, as David Conrad suggested.  

I was certainly not trying to pick on ARIN, because there is wide
perception that they are fairly liberal in their IPv4 policy. I agree
that allocation policy discussions belong elsewhere.

> But, for the record, I was 
> trying to dodge the question of whether address space 
> exhaustion, by itself, was  "strong enough" or "sufficient" 
> reason to get IPv6 deployed and, especially, to avoid the 
> rathole-populating discussion about alternatives.  Since I am on 
> record as believing that, by some reasonable measures, we have 
> already run out of address space and IPv6 is not yet widely 
> deployed, I would suggest that we have a solid example that it 
> has not [yet?] proven to be sufficient.

Yes it is not widely deployed yet, but that does not mean lack of IPv4
space is not a sufficient reason. In several active deployment cases I
am aware of, going as fast as they can, it takes 3-5 years to get to the
point of delivering a stable commercial grade service. It should not be
surprising that we don't see wide scale deployment yet, since the
realization that we are effectively out of IPv4 space has only hit home
recently. 

> ...
> I strongly suspect that we are using words in ways that results 
> in miscommunication, because I think there is a third 
> alternative.  That alternative may fall into the category you 
> describe as "passing around name objects", or maybe it doesn't. 
> >From my perspective --which is definitely the applications end
> of the stack looking down-- the problem is all about data 
> abstraction.  I'm going to try to switch terminology here in the 
> hope that it will help clarify things.  Suppose the application 
> gets a well-constructed handle, and passes that handle "around" 
> --either to other applications or to different interfaces to the 
> stack/network.  I don't see the application as dealing in 
> topology information by doing that, even if the handle 
> ultimately identifies information that is deeply 
> topology-sensitive and/or if the process that produces the 
> handle uses topological information, or probes the network to 
> develop such information.  The important thing from that 
> perspective is that the application is dealing with the handle 
> as an opaque object, without trying to open it up and evaluate 
> its meaning or semantics (with regard to the network or 
> otherwise).

In general I agree, but the difference of perspective is that ignoring
the fact that the well constructed handle is actually derived from
topology information does not make the issue go away. The only way you
can get the handle you are looking for is to have something below you
sort out the topological reality. I agree the current name service is
not up to the task, and I believe that we need to get that fixed.
Unfortunately it looks like it will take some very crisp architectural
guidance to get the IESG to refocus the DNS related WGs to even discuss
the issues. The sad part is that many of the participants there already
ship or run variants that help address this problem, but they have
agreed not to work on standardizing it.

> 
> >From that point of view, having an application go to the stack
> and say "given these criteria, give me a handle on the interface 
> or address I should use" or "given this DNS name, and these 
> criteria, give me a handle on the address I should use" does not 
> involve the application being topology-aware, nor does it imply 
> the application doing something evil because it picks an address 
> (or virtual interface, or...) without understanding the 
> topology.  The handle is opaque and and an abstraction -- as far 
> as the application is concerned, it doesn't have any semantics, 
> regardless of whether lower layers of the stack can derive 
> semantics from it or from whatever they (but not the 
> application) can figure out it is bound to.

This points out that I have been imprecise by claiming that passing
names are sufficient, all the criteria you would use for local
communication with the stack are the 'name' in the context of my
previous mail. 

As long as the handle stays contained within the machine you are fine.
The problem arises when the app passes that handle to another node,
believing that the topology specific information is already there. If
the blob passed were the same as what the app used to acquire the local
handle, the other nodes would acquire appropriate local handles. 

> 
> If the application is calling on, e.g., TCP, then it might pass 
> some criteria to TCP, or might not, and TCP might either pass 
> enhanced criteria to the handle-generating layer or generate the 
> handle itself.  Again, the application doesn't care -- it just 
> needs to deal with an abstraction of the criteria in application 
> terms.   I think that, from the application standpoint, it makes 
> little difference whether the criteria involve routing, speed, 
> reliability, or any of several potential QoS or security issues.

I agree as long as the app keeps the handle for local use. It can't
assume that handle will have an equivalent meaning somewhere else in the
network. If it wants to pass a handle that it believes has sufficient
topology information for the receiver to directly access the same point,
it needs to understand the topology enough to know that the meaning will
be consistent. Otherwise it needs to pass the original parameters.

> 
> I'll also be the first to admit that we have handled the set of 
> issues this implies rather badly with IPv4 (and they certainly 
> are not new issues).  We have gotten away with it because the 
> number of _hosts_ that need to understand, and choose between, 
> multiple addresses for themselves has been extremely small, at 
> least since routers were introduced into the network 
> architecture.  Because it could mostly be seen as a router 
> problem, applications in IPv4 mostly punted (for better or 
> worse).  Also, since CIDR went in, we basically haven't given a 
> damn when users who can't qualify for PI space can't multihome 
> (at least without resort to complex kludges).   IPv6, with its 
> multiple-address-per-host architecture, turns the problem from 
> "mostly theoretical" to an acute one.  It does so with or 
> without SL addresses being one of those on a host that has 
> public (global or otherwise) addresses as well.

I agree that SL simply exposed the issue. The problems arise from the
mismatched interpretation by the apps, that all 'handles' will be
treated equally by the network, and the reality that the network has
more than a single policy. As you noted earlier, this is not just about
scoping of address reachability, it also applies to QoS and any other
policy related variance in the topology. 

> 
> Finally, from the standpoint of that hypothetical application, 
> the syntax and construction of that opaque handle are 
> irrelevant.  In particular, it makes zero difference if it is a 
> name-string that lower layers look up in a dictionary or a 
> symbol table, or [the name of] some sort of class object, or 
> whether it is, e.g., an IP address.  The only properties the 
> application cares about is that it is a handle that it got from 
> somewhere that satisfies criteria it specified or that were 
> specified for it.

I understand that is what the app wants to see. I am suggesting that in
the absence of a central policy entity that can sort out all possible
topology differences, multi-party apps will need to pass the original
parameter set, and maintain local mappings to the stack handle at each
participant node. Not pretty, but closer to a working solution than
continuing to ignore the reality that the topology is inconsistent.

> ...
> See above.  Applications have gotten away with ignoring that 
> reality because the occurrences have been infrequent -- with one 
> important class of exceptions, we have had few machines with 
> multiple addresses (and multiple interfaces) since routers 
> became common in the network.  The exceptions have been larger 
> web hosts which support pre-1.1 versions of HTTP and hence use 
> one address per DNS name.  But, for them, hosts opening 
> connections to them use the address that matches the DNS name 
> (hence no need to make choices or understand topological 
> information) and the servers either use "address matching the 
> one on which the connection was opened" or an arbitrary address 
> on the interface --since the interface is the same, and its 
> connectivity is the same, it really makes no difference.  If the 
> reason for multiple addresses per host (or interface) in IPv6 is 
> to support different scopes (or connectivity, or multihoming 
> arrangements), then it does make a difference, and will make a 
> difference for a significant number of hosts.  And _that_ 
> implies a new requirement.

We could debate 'new' forever, since as you noted earlier this
requirement existed before routers, but the point is that apps can't
ignore it any longer.

> Tony, there is a difference in perspective here.  I'm going to 
> try to identify and explain it, with the understanding that it 
> has little to do with any of the discussion above, which I think 
> is far more important.  From your point of view, as I understand 
> it, this feature has been in IPv6 for a long time, no one 
> questioned it, or the problem(s) it apparently solved, for 
> equally long, some implementations were designed to take 
> advantage of it, and now people are coming along and proposing 
> to remove it without a clearly-better solution to address those 
> solved problems.  

Yes. 

> From the viewpoint of many or most of the 
> applications-oriented folks on this list, and maybe some others, 
> the applications implications of the SL idea (and maybe the 
> "multiple addresses" idea more generally) are just now becoming 
> clear.  What is becoming clear with them is that the costs in 
> complexity, in data abstraction failures, and in damage to the 
> applications view of the hourglass, are very severe and, indeed 
> that, from the standpoint of how applications are constructed, 
> SL would never have worked..    From that perspective, when you 
> argue that applications are already doing bad things, the 
> applications folks respond by saying "but IPv6 should make it 
> better, or at least not make it worse".

It is inconsistent to claim that SL would never have worked while
admitting that there are implementations that take advantage of it. But
that aside, SL is not the issue, the issue is that apps have come to
believe that the topology is flat so they can pass around handles
constructed of topology specific information. The reality all along has
been that some addresses were not reachable outside an administrative
scope of relevance. Writing those cases off in a client/server world was
mostly possible, but in the peer-to-peer world of IPv6 that is no longer
possible. 

> 
> Those differences lead to discussions about religion and 
> ideology, which get us nowhere (although they generate a lot of 
> list traffic).  It is clear to me (from my particular narrow 
> perspective) that our getting to this point at this time 
> indicates a failure on the part of several generations of IESG 
> members (probably including me).  It also identifies a series of 
> issues in how we review things cross-area (or don't do that 
> successfully) and reinforces my perception that shifting the 
> responsibility for defining standards away from a 
> multiple-perspective IESG and onto WGs with much narrower 
> perspectives would be a really bad idea.

I agree, and even restricting the cross-area review to the IESG is a bad
idea because there aren't enough cycles in that small group. 

> 
> But, unfortunate though it may be, we have gotten here.  We 
> differentiate between Proposed and Draft standards precisely to 
> make it easier to take something out that doesn't work, or 
> --more to the point in this case-- doesn't appear to do the job 
> it was designed to do at a pain level no worse than what was 
> anticipated.  I don't think essentially procedural arguments 
> about how much proof is required to take something out get us 
> anywhere at this stage.  Instead, we should be concentrating on 
> the real character of the problem we are trying to solve and 
> ways in which it can be solved without doing violence to 
> whatever architectural principles we can agree upon.

I agree to a point. My button is pushed by those that claim a technology
'creates more problems than it solves', when they simultaneously admit
they don't have a clue what problems need solving. To that end I started
a draft on what problems need solving, so we can sort out the cases that
the current technology does solve, as well as begin to identify
alternatives. IF we get to a point were there are alternatives for all
the cases people care about, we should drop the unused technology. 

Tony






From owner-ietf@ietf.org  Thu Apr 24 16:07:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01441;
	Thu, 24 Apr 2003 16:07:44 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198nIl-0005ot-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 16:26:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198jtO-00077n-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 12:48:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22293
	for <ietf@ietf.org>; Thu, 24 Apr 2003 12:25:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198ja5-00072m-00
	for ietf@ietf.org; Thu, 24 Apr 2003 12:28:17 -0400
Received: from alicia.nttmcl.com ([216.69.69.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 198ja4-00072e-00
	for ietf@ietf.org; Thu, 24 Apr 2003 12:28:16 -0400
Received: from alicia.nttmcl.com (localhost [127.0.0.1])
	by alicia.nttmcl.com (8.12.5/8.12.5) with ESMTP id h3OGSBvm053497;
	Thu, 24 Apr 2003 09:28:11 -0700 (PDT)
	(envelope-from jj@alicia.nttmcl.com)
Received: (from jj@localhost)
	by alicia.nttmcl.com (8.12.5/8.12.5/Submit) id h3OGS8e1053496;
	Thu, 24 Apr 2003 09:28:08 -0700 (PDT)
Date: Thu, 24 Apr 2003 09:28:08 -0700
From: Shannon -jj Behrens <jj@nttmcl.com>
To: Tony Hain <alh-ietf@tndh.net>
Cc: "'Keith Moore'" <moore@cs.utk.edu>, john-ietf@jck.com, dts@senie.com,
        ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
Message-ID: <20030424162808.GA52759@alicia.nttmcl.com>
References: <20030423180731.4137efe7.moore@cs.utk.edu> <038e01c309ea$e7927c00$261e4104@eagleswings>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <038e01c309ea$e7927c00$261e4104@eagleswings>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Apr 23, 2003 at 03:51:40PM -0700, Tony Hain wrote:
> I am accepting comments for:
> http://www.ietf.org/internet-drafts/draft-hain-ipv6-sitelocal-00.txt

Dear Sir,

Please forgive my rough tone (in fact, I have great respect for you as an
engineer), but it would be much more interesting if you wrote a document that
provided solutions for all of the problems that people have claimed
site-locals cause.  While I hear you saying that the wg should replace all of
the features that site-locals provide before removing them from the
architecture, I challenge you to instead take the impetus of fully specifying
site-locals.  I do believe, based on other comments on the list, that such a
challenge has existed for five years and has yet to be answered.  Having fully
specified site-locals, I do believe the wg would be much more willing to accept
them into the architecture.  Although I clearly am not capable of providing the
full list of questions that you must answer, perhaps the following questions
are helpful:

o In light of the fact that not every host has a DNS name, how do you propose
multi-party P2P applications should do referrals? It would be helpful if you
established the normal mode of operation for such situations.

o Should site-locals be put in DNS?  Should multiple views of DNS be used?  If 
so, how do you address the apparent apprehension in the DNS community toward
multiple views (I don't know about this first-hand--I've only read about it 
from this list)?  Should zone information be kept in DNS?

o Do you foresee all nodes being multi-site nodes?  If I'm at work and wish to 
use both my work network *and* my home network via a VPN connection, I expect
I would want my laptop to be a multi-site node.  If this is the case, do I 
need to use %interface_name at the end of all IP's I give to applications I 
use?  How would DNS lookups work on a multi-site node if site-locals are stored
in DNS?

o If, as you say, we should provide site-locals because, "we need to meet the
network manager at his comfort zone and provide a familiar tool," how do we 
convince the network manager not to use NAT since this is also a familiar tool
in most people's comfort zone.  I'm not willing to argue that site-locals 
necessarily lead to NAT, but many people are, so you should probably have some
answer. 

o Do you envision support for Margaret's idea of multiple concentric rings of
security (possibly using site-locals)?  If a node in the outermost ring is not
able to talk to a node in the innermost ring using a site-local address because
of filtering, but is permitted to use a global address, how shall applications
react when the site-local "hint" is actually misleading?

Again, I'm sure there are many more such questions, and I think it would be 
helpful (and in fact requisite) that you answer such questions in an Internet
Draft in order to achieve your goal of restoring site-locals to the 
architecture.  I thank you for your time and *patience* if you have made it all
the way through this message.

Best Regards,
-jj

-- 
Hacker is to software engineer as 
Climbing Mt. Everest is to building a Denny's there.





From owner-ietf@ietf.org  Thu Apr 24 16:52:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02779;
	Thu, 24 Apr 2003 16:52:35 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198nxQ-0007Pq-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 17:08:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198nwa-0007Nq-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 17:07:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02557
	for <ietf@ietf.org>; Thu, 24 Apr 2003 16:45:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198ndB-0001AF-00
	for ietf@ietf.org; Thu, 24 Apr 2003 16:47:45 -0400
Received: from garlic.amaranth.net ([208.254.46.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 198ndA-0001AC-00
	for ietf@ietf.org; Thu, 24 Apr 2003 16:47:44 -0400
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226])
	(authenticated (0 bits))
	by garlic.amaranth.net (8.11.7/8.11.7) with ESMTP id h3OKm6825233
	(using TLSv1/SSLv3 with cipher RC4-SHA (128 bits) verified NO);
	Thu, 24 Apr 2003 16:48:09 -0400
Message-Id: <5.2.1.1.2.20030424160322.01ad7248@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 24 Apr 2003 16:45:54 -0400
To: <alh-ietf@tndh.net>, "'John C Klensin'" <john-ietf@jck.com>
From: Daniel Senie <dts@senie.com>
Subject: RE: A follow up question
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
In-Reply-To: <042701c30a9b$6d3dc840$261e4104@eagleswings>
References: <299162132.1051138523@p3.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 03:55 PM 4/24/2003, Tony Hain wrote:
>John C Klensin wrote:

[edited]

> > ...
> > I strongly suspect that we are using words in ways that results
> > in miscommunication, because I think there is a third
> > alternative.  That alternative may fall into the category you
> > describe as "passing around name objects", or maybe it doesn't.
> > >From my perspective --which is definitely the applications end
> > of the stack looking down-- the problem is all about data
> > abstraction.  I'm going to try to switch terminology here in the
> > hope that it will help clarify things.  Suppose the application
> > gets a well-constructed handle, and passes that handle "around"
> > --either to other applications or to different interfaces to the
> > stack/network.  I don't see the application as dealing in
> > topology information by doing that, even if the handle
> > ultimately identifies information that is deeply
> > topology-sensitive and/or if the process that produces the
> > handle uses topological information, or probes the network to
> > develop such information.  The important thing from that
> > perspective is that the application is dealing with the handle
> > as an opaque object, without trying to open it up and evaluate
> > its meaning or semantics (with regard to the network or
> > otherwise).
>
>In general I agree, but the difference of perspective is that ignoring
>the fact that the well constructed handle is actually derived from
>topology information does not make the issue go away. The only way you
>can get the handle you are looking for is to have something below you
>sort out the topological reality. I agree the current name service is
>not up to the task, and I believe that we need to get that fixed.
>Unfortunately it looks like it will take some very crisp architectural
>guidance to get the IESG to refocus the DNS related WGs to even discuss
>the issues. The sad part is that many of the participants there already
>ship or run variants that help address this problem, but they have
>agreed not to work on standardizing it.

Having a mechanism within each host which can sort out the topological 
issues seems like something we will have to explore. It is not clear to me 
that DNS is the solution, though it may be a part of the solution. More below.


> >
> > >From that point of view, having an application go to the stack
> > and say "given these criteria, give me a handle on the interface
> > or address I should use" or "given this DNS name, and these
> > criteria, give me a handle on the address I should use" does not
> > involve the application being topology-aware, nor does it imply
> > the application doing something evil because it picks an address
> > (or virtual interface, or...) without understanding the
> > topology.  The handle is opaque and and an abstraction -- as far
> > as the application is concerned, it doesn't have any semantics,
> > regardless of whether lower layers of the stack can derive
> > semantics from it or from whatever they (but not the
> > application) can figure out it is bound to.
>
>This points out that I have been imprecise by claiming that passing
>names are sufficient, all the criteria you would use for local
>communication with the stack are the 'name' in the context of my
>previous mail.
>
>As long as the handle stays contained within the machine you are fine.
>The problem arises when the app passes that handle to another node,
>believing that the topology specific information is already there. If
>the blob passed were the same as what the app used to acquire the local
>handle, the other nodes would acquire appropriate local handles.

Agree that these handles can't move off the host on which they are valid.

Recognizing applications DO want to be able to send identifying information 
in the course of transactions with other hosts, and that it is important to 
make such applications function, perhaps it's time to actually address this 
problem with some degree of standardization. Do we really want to continue 
having applications try (and often fail) to do this work? Perhaps we're 
discussing something that some become an integral component of the Internet 
Protocol suite.

It would make more sense for an application to make a call to an API that 
says "I want to hand off identifying information about host X to host Y. 
Please package me up information to sent to X so that it will be able to 
understand what I mean." The result of that API would be a blob which the 
application would send. The receiving application would pass that blob to 
an API on its end, effectively saying "I got this blob from host A, and it 
wants me to use it to set up communication. Please figure out what it 
meant, and give me a handle for talking to the proper destination."

The application would not see (or care) how this is actually implemented. 
Application writers should not need to know or care. Under the covers, 
those APIs could result in some sort of work done solely on the hosts in 
question, or could result in some sort of exchange amongst the hosts to 
figure out the best way to make that communication happen. Getting this 
decision out of the application space is the key point. This would simplify 
the implemenentation of applications which want to do these types of third 
party communications, and provide a standardized mechanism for 
implementation. With that standardized, a uniform firewall and NAT 
traversal mechanism could be considered. Note that there is a great deal of 
room for exploration of mechanisms and techniques to make this work. I'm 
not proposing a singular solution, but merely a framework for facilitating 
that solution.

A mention of proper layering was made earlier in this discussion thread. 
It's time we took a serious look at how to improve on the mechanisms used. 
Solving this layering issue could benefit both IPv4 and IPv6 
implementations. As noted, the problem is not new at all, though perhaps 
now is the time to shed light on the matter.





From owner-ietf@ietf.org  Thu Apr 24 16:59:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03395;
	Thu, 24 Apr 2003 16:59:34 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198o7J-00081r-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 17:18:53 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198o6Y-000808-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 17:18:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03132
	for <ietf@ietf.org>; Thu, 24 Apr 2003 16:55:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198nnC-0001Kk-00
	for ietf@ietf.org; Thu, 24 Apr 2003 16:58:06 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 198nnC-0001KF-00
	for ietf@ietf.org; Thu, 24 Apr 2003 16:58:06 -0400
Received: from edison.cisco.com (edison.cisco.com [171.70.144.164])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h3OKw1ID022698;
	Thu, 24 Apr 2003 13:58:01 -0700 (PDT)
Received: from cisco.com (dhcp-171-71-119-39.cisco.com [171.71.119.39]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id NAA13837; Thu, 24 Apr 2003 13:58:00 -0700 (PDT)
Message-ID: <3EA84FD8.5050908@cisco.com>
Date: Thu, 24 Apr 2003 13:58:00 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: alh-ietf@tndh.net
CC: "'John C Klensin'" <john-ietf@jck.com>, "'Daniel Senie'" <dts@senie.com>,
        ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
References: <042701c30a9b$6d3dc840$261e4104@eagleswings>
In-Reply-To: <042701c30a9b$6d3dc840$261e4104@eagleswings>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony Hain wrote:
> But that aside, SL is not the issue, the issue is that apps have come to
> believe that the topology is flat so they can pass around handles
> constructed of topology specific information. The reality all along has
> been that some addresses were not reachable outside an administrative
> scope of relevance. Writing those cases off in a client/server world was
> mostly possible, but in the peer-to-peer world of IPv6 that is no longer
> possible. 

As there are many entities that provide firewalling functionality, it is 
unreasonable to assume that it would be possible for each of these to be 
the address authority for either end of a connection.  Thus, an 
application must deal with multiple administrative domains today.  In 
some circumstances, administrative firewalls exist specifically to block 
particular applications.  And... network error messages may or may not 
be appropriate to a given circumstance.  It all depends on your threat 
model.

Along these same lines, there is no reason to assume that the end host 
will be trusted by the firewall sufficiently such that a POLICY exchange 
would be allowed.  It is one thing to say, "Permission denied", and 
quite something else to say when one will deny permission.  SLs and IPv6 
provide neither advance nor regression in this regard.

I take exception to this:

> I agree to a point. My button is pushed by those that claim a technology
> 'creates more problems than it solves', when they simultaneously admit
> they don't have a clue what problems need solving. 

Most of us -- MOST OF US -- have a clue.  That you refuse to recognize 
it and respect those opinions is unfortunate.

> To that end I started
> a draft on what problems need solving, so we can sort out the cases that
> the current technology does solve, as well as begin to identify
> alternatives. IF we get to a point were there are alternatives for all
> the cases people care about, we should drop the unused technology. 

And many of us have been saying that we have something that works today, 
RIR policies not withstanding.  It's IPv4.

Eliot





From owner-ietf@ietf.org  Thu Apr 24 17:06:53 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03736;
	Thu, 24 Apr 2003 17:06:53 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198oDp-0000Qv-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 17:25:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198oDF-0000Pg-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 17:25:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03622
	for <ietf@ietf.org>; Thu, 24 Apr 2003 17:02:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198ntt-0001TH-00
	for ietf@ietf.org; Thu, 24 Apr 2003 17:05:01 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 198nts-0001Sq-00
	for ietf@ietf.org; Thu, 24 Apr 2003 17:05:00 -0400
Received: from edison.cisco.com (edison.cisco.com [171.70.144.164])
	by sj-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h3OL4t08028597;
	Thu, 24 Apr 2003 14:04:55 -0700 (PDT)
Received: from cisco.com (dhcp-171-71-119-39.cisco.com [171.71.119.39]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA00152; Thu, 24 Apr 2003 14:04:54 -0700 (PDT)
Message-ID: <3EA85176.5010205@cisco.com>
Date: Thu, 24 Apr 2003 14:04:54 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: alh-ietf@tndh.net
CC: erosen@cisco.com, "'Keith Moore'" <moore@cs.utk.edu>,
        "'Stephen Sprunk'" <stephen@sprunk.org>, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: Architectural Considerations section in specs
References: <042801c30a9b$72a91c80$261e4104@eagleswings>
In-Reply-To: <042801c30a9b$72a91c80$261e4104@eagleswings>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony Hain wrote:
> I am not trying to place blame, but I would word it differently. 

Not to contradict you, but...

> While the architecture has all along allowed for differentiating policy
> restrictions, the app community chose to simplify their effort by
> ignoring that there were policy differences in the lower layers. 

Nobody ignored anything.  To start with, the application community has 
had to work around these sorts of problems.  This is why there are SIP 
proxy gateways, STUN services, and MX gateways.  All of these exist due 
to connectivity limitations (either intentional or architectural).  All 
of these cases fall under the "Got Lemons?  make lemonade" approach.  So 
I believe you've mischaracterised the community.

Eliot





From owner-ietf@ietf.org  Thu Apr 24 17:11:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03958;
	Thu, 24 Apr 2003 17:11:13 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198oIk-0000xO-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 17:30:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198oIc-0000uI-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 17:30:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03869
	for <ietf@ietf.org>; Thu, 24 Apr 2003 17:08:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198nzG-0001XY-00
	for ietf@ietf.org; Thu, 24 Apr 2003 17:10:34 -0400
Received: from grebe.mail.pas.earthlink.net ([207.217.120.46])
	by ietf-mx with esmtp (Exim 4.12)
	id 198nzF-0001XR-00
	for ietf@ietf.org; Thu, 24 Apr 2003 17:10:33 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by grebe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 198nzU-0003NQ-00; Thu, 24 Apr 2003 14:10:48 -0700
Date: Thu, 24 Apr 2003 17:10:12 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, erosen@cisco.com, stephen@sprunk.org, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: Architectural Considerations section in specs
Message-Id: <20030424171012.4b0904cd.moore@cs.utk.edu>
In-Reply-To: <042801c30a9b$72a91c80$261e4104@eagleswings>
References: <200304241500.h3OF0IlY028110@rtp-core-1.cisco.com>
	<042801c30a9b$72a91c80$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (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

> > ... The fact that  A gives B an address of C  
> > rather than a name of  C  doesn't seem  relevant  at  all; 
> > after  all,  names  just resolve  to addresses;  I think the  
> > name vs.  address issue  is a  red herring  in this context. 
> 
> If A gave the entire list of choices to B, you would be right. The
> problem is that A will generally give B the one it chose, since it
> believes that one works. 

there are multiple problems.

one problem is when the network expects different hosts to choose
different addresses in order to reach the same destination.

another problem is that even if A passes a list of choices to B,
neither A nor B typically has any idea about which choices will
work for B, or for any third intermediary that B passes the list to.

(no, it's not the case that A will "generally" give be the address it chose,
because there's too much variation in behavior between distributed apps. 
often A has no need to choose from that set of addresses at all; it's just
trying to provide some referral service.)

another problem is that being able to pass a list of addresses is not the same
thing as being able to fail over from one address to another, and yet people
want to treat the existence of multiple addresses on a host as a substitute
for multihoming.

> > I think the  underlying problem is that our  comms architecture doesn't
> > take the policy restrictions  into account at all, and folks tend to
> > assume that this needs  to be accounted for  at some other layer than the
> > one  they are most interested in.  This generates  frustration, and
> > creates a high heat to light ratio.   Usually everyone blames it on NAT, 
> > so it's nice to see the same issue come up in an IPv6 non-NAT context. 
> 
> 
> I am not trying to place blame, but I would word it differently. While
> the architecture has all along allowed for differentiating policy
> restrictions, the app community chose to simplify their effort by
> ignoring that there were policy differences in the lower layers.

another false statement.  apps have been expected to deal with crude and
inflexible policy implementation in lower layers for many years, so apps
people are painfully aware that such differences exist.  what some of us are
saying is that the lack of flexibility in these mechanisms has increased
complexity in both apps and the network without providing much in the way of
useful policy control or security, and we need to reconsider some of the
cruder mechanisms like private addressing.  or in other words - don't create a
mess at layer 2 or 3 and expect layer 7 to sort it out.






From owner-ietf@ietf.org  Thu Apr 24 17:29:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04600;
	Thu, 24 Apr 2003 17:29:03 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198oZ8-0001uv-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 17:47:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198oXK-0001sH-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 17:45:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04425
	for <ietf@ietf.org>; Thu, 24 Apr 2003 17:23:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198oDy-0001ez-00
	for ietf@ietf.org; Thu, 24 Apr 2003 17:25:46 -0400
Received: from swan.mail.pas.earthlink.net ([207.217.120.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 198oDx-0001ew-00
	for ietf@ietf.org; Thu, 24 Apr 2003 17:25:46 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by swan.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 198oEI-00077J-00; Thu, 24 Apr 2003 14:26:07 -0700
Date: Thu, 24 Apr 2003 17:25:29 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, john-ietf@jck.com, dts@senie.com, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
Message-Id: <20030424172529.710c9a73.moore@cs.utk.edu>
In-Reply-To: <042701c30a9b$6d3dc840$261e4104@eagleswings>
References: <299162132.1051138523@p3.JCK.COM>
	<042701c30a9b$6d3dc840$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (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

> The only way you
> can get the handle you are looking for is to have something below you
> sort out the topological reality. I agree the current name service is
> not up to the task, and I believe that we need to get that fixed.
> Unfortunately it looks like it will take some very crisp architectural
> guidance to get the IESG to refocus the DNS related WGs to even discuss
> the issues. 

if the architecutral guidance were crisp it certainly wouldn't be asking the
DNS related WGs to discuss those issues.  DNS cannot solve this problem.

> As long as the handle stays contained within the machine you are fine.
> The problem arises when the app passes that handle to another node,
> believing that the topology specific information is already there. If
> the blob passed were the same as what the app used to acquire the local
> handle, the other nodes would acquire appropriate local handles. 

this presupposes that the blob that is passed is precisely and reliably bound
to the specific host or process that the app wants to refer to, and also that
the lookup process that maps blobs to locators and/or identifiers is
sufficiently fast and robust.  often neither of these conditions holds.

> The problems arise from the
> mismatched interpretation by the apps, that all 'handles' will be
> treated equally by the network,

heaven forbid that apps would assume the same thing that the IP network
was designed to assume - that there is a uniform address space across the
entire network.  but you want to change this fundamental architectural design
point at layer 3 and then claim that the resulting problems are caused by
inappropriate assumptions at layer 7.  some would say this is layering
violation, but the sharing of identifiers between layer 7 and layer 3 is
another fundamental architectural design point.

> I agree to a point. My button is pushed by those that claim a technology
> 'creates more problems than it solves', when they simultaneously admit
> they don't have a clue what problems need solving.

I do have an idea about what problems need solving, but I don't claim to be
able to make a list that satisfies everyone at the drop of a hat. 

But it's not clear that SL was actually intended to solve any of these
problems.  Rather, it seems to me that somebody thought SL was a good idea,
and put it into the v6 architecture.  And then various people started saying
"hey, we can use SL for X", and nobody bothered to examine whether there were
conflicts between those various peoples' assumptions (whether specifically
about SL or not), or even whether SL was worth the cost, until recently.

The problem with trying to make a list of "SL-related problems" is that there
is also a set of problems that don't directly involve SL but also need to be
solved, and SL precludes solving those problems.

Keith



From owner-ietf@ietf.org  Thu Apr 24 18:02:46 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05845;
	Thu, 24 Apr 2003 18:02:46 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198p38-0003hB-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 18:18:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198p1j-0003dn-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 18:17:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05545
	for <ietf@ietf.org>; Thu, 24 Apr 2003 17:54:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198oiM-0001vX-00
	for ietf@ietf.org; Thu, 24 Apr 2003 17:57:10 -0400
Received: from turkey.mail.pas.earthlink.net ([207.217.120.126])
	by ietf-mx with esmtp (Exim 4.12)
	id 198oiM-0001vU-00
	for ietf@ietf.org; Thu, 24 Apr 2003 17:57:10 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by turkey.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 198oif-0005xe-00; Thu, 24 Apr 2003 14:57:29 -0700
Date: Thu, 24 Apr 2003 17:56:53 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Daniel Senie <dts@senie.com>
Cc: moore@cs.utk.edu, alh-ietf@tndh.net, john-ietf@jck.com, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
Message-Id: <20030424175653.6987720a.moore@cs.utk.edu>
In-Reply-To: <5.2.1.1.2.20030424160322.01ad7248@mail.amaranth.net>
References: <299162132.1051138523@p3.JCK.COM>
	<5.2.1.1.2.20030424160322.01ad7248@mail.amaranth.net>
X-Mailer: Sylpheed version 0.8.11 (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

> It would make more sense for an application to make a call to an API that 
> says "I want to hand off identifying information about host X to host Y. 
> Please package me up information to sent to X so that it will be able to 
> understand what I mean." 

been there, tried to do that, in the context of PVM.  by far the easiest way
to accomplish this is to have a uniform address space at the network level.
any other approach is just too complex.

background: PVM was originally designed to as a uniform API for distributed
memory parallel machines, and later as a way to provide a distributed memory
programming environment across a network of computers (some of which were
potentially distributed memory hosts).  in order to allow applications to send
messages to other "processing elements" or hosts, PVM assigned a task id to
each "processing element" in its virtual machine, and the mapping between task
ids to tasks was uniform across the virtual machine.  this task id consisted
of a host id to which a host-specific offset was added.  we tried making the
mapping non-uniform because it would have relieved us of the need to keep a
mapping table consistent across all hosts in the machine (especially after we
allowed new hosts to be added to the machine), but the most robust, and in
general the most efficient, way to implement the host-id mapping function was
to use consistent numbering for host-ids across the entire machine...that, and
expecting apps to invoke a translation function every time they
passed a task id to another task was just too cumbersome.

uniform addressing models are very compelling, even when you don't have
complete interconnection.

> A mention of proper layering was made earlier in this discussion thread. 
> It's time we took a serious look at how to improve on the mechanisms used. 
> Solving this layering issue could benefit both IPv4 and IPv6 
> implementations. As noted, the problem is not new at all, though perhaps 
> now is the time to shed light on the matter.

proper layering is an art.  it involves understanding when to enforce layering
discipline, and when to escape it. 



From owner-ietf@ietf.org  Thu Apr 24 18:03:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05893;
	Thu, 24 Apr 2003 18:03:03 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198p6z-0003xn-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 18:22:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198p54-0003kY-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 18:20:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05682
	for <ietf@ietf.org>; Thu, 24 Apr 2003 17:58:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198olh-0001y6-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:00:38 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198olh-0001y2-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:00:37 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26343> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 24 Apr 2003 15:01:02 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Eliot Lear'" <lear@cisco.com>
Cc: <erosen@cisco.com>, "'Keith Moore'" <moore@cs.utk.edu>,
        "'Stephen Sprunk'" <stephen@sprunk.org>, <ietf@ietf.org>,
        <ipng@sunroof.eng.sun.com>
Subject: RE: Architectural Considerations section in specs
Date: Thu, 24 Apr 2003 15:01:02 -0700
Message-ID: <044101c30aad$0016f3b0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <3EA85176.5010205@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA05893

Eliot Lear wrote:
> Nobody ignored anything.  To start with, the application 
> community has 
> had to work around these sorts of problems.  This is why 
> there are SIP 
> proxy gateways, STUN services, and MX gateways.  All of these 
> exist due 
> to connectivity limitations (either intentional or 
> architectural).  All 
> of these cases fall under the "Got Lemons?  make lemonade" 
> approach.  So 
> I believe you've mischaracterised the community.

Those are all examples of building complexity into the infrastructure so
that the app can maintain the fantasy that the world is flat. Personally
I would rather see the Lemons turned into a nice desert than squeezed
and watered down.

Tony






From owner-ietf@ietf.org  Thu Apr 24 18:04:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06102;
	Thu, 24 Apr 2003 18:04:04 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198p70-0003xt-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 18:22:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198p55-0003l1-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 18:20:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05686
	for <ietf@ietf.org>; Thu, 24 Apr 2003 17:58:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198oli-0001yB-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:00:39 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198oli-0001y4-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:00:38 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26344> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 24 Apr 2003 15:01:05 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Eliot Lear'" <lear@cisco.com>
Cc: "'John C Klensin'" <john-ietf@jck.com>, "'Daniel Senie'" <dts@senie.com>,
        <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
Subject: RE: A follow up question
Date: Thu, 24 Apr 2003 15:01:05 -0700
Message-ID: <044201c30aad$00df25b0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <3EA84FD8.5050908@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA06102

Eliot Lear wrote:
> ...
> Most of us -- MOST OF US -- have a clue.  That you refuse to 
> recognize 
> it and respect those opinions is unfortunate.

Where is the document that shows what requirements need to be solved? 


How would you correlate the stated need from the network manager for:
Stable addresses, both during ISP changes, and for intermittently
connected networks.

with:
Why is it that stable addresses are so necessary?  
Could it be because renumbering is painful?  
Could that be one source of our ills?

&

Fix the underlying problem.  Making renumbering easy.  
If we don't do that, IPv6 is no better than Ipv4.

???

While I agree that we need to get at the underlying problem, handwaving
that easy renumbering will solve it is not helpful. In many cases the
requirement for stable addresses is being handed to the enterprise
network manager by unreasonable Sr. VPs who want to lower their internal
development cost & don't care about anything more than getting their
product out the door. Claiming that easy renumbering will solve that
internal business issue is just an IETF fantasy.

Tony




From owner-ietf@ietf.org  Thu Apr 24 18:12:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07315;
	Thu, 24 Apr 2003 18:12:25 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198pFh-000189-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 18:31:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198pEj-0000pu-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 18:30:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06921
	for <ietf@ietf.org>; Thu, 24 Apr 2003 18:08:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198ovL-0002C6-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:10:35 -0400
Received: from gull.mail.pas.earthlink.net ([207.217.120.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 198ovL-0002C3-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:10:35 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 198ovh-0006Su-00; Thu, 24 Apr 2003 15:10:57 -0700
Date: Thu, 24 Apr 2003 18:10:19 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, jj@nttmcl.com, john-ietf@jck.com, dts@senie.com,
        ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
Message-Id: <20030424181019.77736d10.moore@cs.utk.edu>
In-Reply-To: <044001c30aac$fababaa0$261e4104@eagleswings>
References: <20030424212448.GA56083@alicia.nttmcl.com>
	<044001c30aac$fababaa0$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (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

> > If A connects to B, and B wishes to pass the connection info 
> > to C, B only has the address with which A accessed B.  If A 
> > and B are in the same site and used site-local communication, 
> > and C is not in that site, B does not have enough information 
> > to refer C to A.  Hence, your suggestion does not solve this case.
> 
> I agree, but is it reasonable for B to tell C to talk to A, or is it
> more reasonable for B to tell A to connect to C by the 'name blob' it
> would have used to contact C? 

let me rephrase the question.  is it reasonable to expect that every 'blob'
that can be used to derive a set of locators for a host is tightly bound to
that host?   or is it more reasonable for the network infrastructure to
provide a token, independent of any application-specific blob, that can be
tightly bound to that host?

back in the mid 1990s I had a system for looking up URLs or URNs in a
distributed database which would return blobs that could be used to find
accurate replicas of those resources.  those blobs included IP addresses in
order to speed up access (requiring clients to do extra DNS lookups
drastically slowed the system down).  but those blobs weren't bound to hosts,
they were bound to resources, and the mapping between resources and hosts was
(by design) arbitrary.

Keith




From owner-ietf@ietf.org  Thu Apr 24 18:13:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07594;
	Thu, 24 Apr 2003 18:13:55 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198pHd-0001qY-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 18:33:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198pGA-0001Fv-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 18:32:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07075
	for <ietf@ietf.org>; Thu, 24 Apr 2003 18:09:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198own-0002Ci-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:12:05 -0400
Received: from scaup.mail.pas.earthlink.net ([207.217.120.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 198owm-0002Cf-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:12:04 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by scaup.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 198owr-0005BB-00; Thu, 24 Apr 2003 15:12:10 -0700
Date: Thu, 24 Apr 2003 18:11:27 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, lear@cisco.com, erosen@cisco.com, stephen@sprunk.org,
        ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: Architectural Considerations section in specs
Message-Id: <20030424181127.53837c49.moore@cs.utk.edu>
In-Reply-To: <044101c30aad$0016f3b0$261e4104@eagleswings>
References: <3EA85176.5010205@cisco.com>
	<044101c30aad$0016f3b0$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (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

> Those are all examples of building complexity into the infrastructure so
> that the app can maintain the fantasy that the world is flat. 

maybe instead it's your fantasy that it's reasonable to expect apps to cope
with routing.



From owner-ietf@ietf.org  Thu Apr 24 18:27:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08241;
	Thu, 24 Apr 2003 18:27:20 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198pUF-0004dt-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 18:46:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198pU7-0004bZ-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 18:46:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08174
	for <ietf@ietf.org>; Thu, 24 Apr 2003 18:24:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198pAk-0002La-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:26:30 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 198pAj-0002LS-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:26:30 -0400
Received: from edison.cisco.com (edison.cisco.com [171.70.144.164])
	by sj-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h3OMQP08003280;
	Thu, 24 Apr 2003 15:26:25 -0700 (PDT)
Received: from cisco.com (dhcp-171-71-119-39.cisco.com [171.71.119.39]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id PAA08695; Thu, 24 Apr 2003 15:26:24 -0700 (PDT)
Message-ID: <3EA86490.8060501@cisco.com>
Date: Thu, 24 Apr 2003 15:26:24 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: alh-ietf@tndh.net
CC: "'John C Klensin'" <john-ietf@jck.com>, "'Daniel Senie'" <dts@senie.com>,
        ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
References: <044201c30aad$00df25b0$261e4104@eagleswings>
In-Reply-To: <044201c30aad$00df25b0$261e4104@eagleswings>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony Hain wrote:
>>Most of us -- MOST OF US -- have a clue.  That you refuse to 
>>recognize 
>>it and respect those opinions is unfortunate.
> 
> 
> Where is the document that shows what requirements need to be solved? 

How about starting with the IPng archives?!  They're actually more 
persistant than, say, an internet draft, anyway.

> How would you correlate the stated need from the network manager for:
> Stable addresses, both during ISP changes, and for intermittently
> connected networks.

I wouldn't.  I would decompose the network manager's stated need for 
stable addresses.  That's what responsible people do when they see a 
customer requirement with a bad solution.  But see below...

> 
> with:
> Why is it that stable addresses are so necessary?  
> Could it be because renumbering is painful?  
> Could that be one source of our ills?
> 
> &
> 
> Fix the underlying problem.  Making renumbering easy.  
> If we don't do that, IPv6 is no better than Ipv4.
> 
> ???
> 
> While I agree that we need to get at the underlying problem, handwaving
> that easy renumbering will solve it is not helpful. In many cases the
> requirement for stable addresses is being handed to the enterprise
> network manager by unreasonable Sr. VPs who want to lower their internal
> development cost & don't care about anything more than getting their
> product out the door. Claiming that easy renumbering will solve that
> internal business issue is just an IETF fantasy.

This strikes me like the old adage, "You're safe if you buy IBM" (no 
offense to IBMers).  You were until you weren't because the processes 
you used were outmoded, only you didn't think about it.  Frankly, the 
fantasy here (and I love your charged use of words) is that IPv6 
provides any -- ANY -- added benefit to the customer base.(*)  That same 
Sr. VP ought to be asking why he is spending what will for the forseable 
future be a huge amount of money to cut over to IPv6 when IPv4 will suit 
the vast percentage of enterprises and users just as well as IPv6, given 
their intended use of SLs, as stated by some of those very same network 
managers.

Eliot

(*) Indeed I question whether even the mobility features will be 
properly taken advantage of, given the stated network manager need for 
stable addresses reconciled with their need for Internet connectivity 
(i.e., NAT).  What do you then use for your MN address?  If that mobile 
node wants to have a stable identifier, then it's using site-locals. 
Nonsense?  But if they don't use site-locals then they have all the same 
problems those network managers are complaining about, and you don't 
have a stable address for applications.




From owner-ietf@ietf.org  Thu Apr 24 18:30:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08463;
	Thu, 24 Apr 2003 18:30:13 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198pWA-0004iB-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 18:48:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198pUL-0004dv-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 18:46:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08181
	for <ietf@ietf.org>; Thu, 24 Apr 2003 18:24:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198pAy-0002Lm-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:26:44 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198pAx-0002Le-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:26:44 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26361> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 24 Apr 2003 15:27:09 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <john-ietf@jck.com>, <dts@senie.com>, <ietf@ietf.org>,
        <ipng@sunroof.eng.sun.com>
Subject: RE: A follow up question
Date: Thu, 24 Apr 2003 15:27:09 -0700
Message-ID: <044801c30ab0$a5d97680$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030424172529.710c9a73.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA08463

Keith Moore wrote:
> if the architecutral guidance were crisp it certainly 
> wouldn't be asking the DNS related WGs to discuss those 
> issues.  DNS cannot solve this problem.

I agree all infrastructure & components that pass around topology
information need work, but DNS is one of those, so it is a good place to
start.

> 
> > As long as the handle stays contained within the machine 
> you are fine. 
> > The problem arises when the app passes that handle to another node, 
> > believing that the topology specific information is already 
> there. If 
> > the blob passed were the same as what the app used to acquire the 
> > local handle, the other nodes would acquire appropriate 
> local handles.
> 
> this presupposes that the blob that is passed is precisely 
> and reliably bound to the specific host or process that the 
> app wants to refer to, and also that the lookup process that 
> maps blobs to locators and/or identifiers is sufficiently 
> fast and robust.  often neither of these conditions holds.

If the first one doesn't hold, the origin node can't use it so the whole
app is broken. Speed is an implementation issue, not a spec issue. In
any case, it is much faster to pass a blob that can be mapped into
useful topology information, than it is  to pass around useless topology
information.

> 
> > The problems arise from the
> > mismatched interpretation by the apps, that all 'handles' will be 
> > treated equally by the network,
> 
> heaven forbid that apps would assume the same thing that the 
> IP network was designed to assume - that there is a uniform 
> address space across the entire network.  but you want to 
> change this fundamental architectural design point at layer 3 
> and then claim that the resulting problems are caused by 
> inappropriate assumptions at layer 7.  some would say this is 
> layering violation, but the sharing of identifiers between 
> layer 7 and layer 3 is another fundamental architectural design point.

I am not saying that. From day one, a host that had one interface where
the address prefix was not passed widely in the routing system, and
another where the prefix was passed globally would have exactly the same
issues you are complaining about. This says nothing about firewalling,
qos, ambiguous addresses, etc. This is simply about a host having
multiple addresses, where different points in the network have different
perceptions about the viability of those. The fact that over the years a
simplification was done through the assumption that there was only a
single view is a failure. 

> 
> > I agree to a point. My button is pushed by those that claim a 
> > technology 'creates more problems than it solves', when they 
> > simultaneously admit they don't have a clue what problems need 
> > solving.
> 
> I do have an idea about what problems need solving, but I 
> don't claim to be able to make a list that satisfies everyone 
> at the drop of a hat. 

I don't have a list either, but we need to collectively create that
list. 

> 
> But it's not clear that SL was actually intended to solve any 
> of these problems.  Rather, it seems to me that somebody 
> thought SL was a good idea, and put it into the v6 
> architecture.  And then various people started saying "hey, 
> we can use SL for X", and nobody bothered to examine whether 
> there were conflicts between those various peoples' 
> assumptions (whether specifically about SL or not), or even 
> whether SL was worth the cost, until recently.

Fine, we need to create the list, figure out alternatives and as you
said in SF, push SL into the corner cases, if we still need it. Getting
rid of SL first does not solve the problems. 

> The problem with trying to make a list of "SL-related 
> problems" is that there is also a set of problems that don't 
> directly involve SL but also need to be solved, and SL 
> precludes solving those problems.

I agree there are several problems to be solved, but don't agree that
the existence of SL precludes solving anything. If we try to claim that
we don't need to work on solving problem X because SL solves it, then I
would agree, but so far I haven't heard anyone claim that we shouldn't
work on solving the problems. The only thing I have heard is that we
have found no use for SL (despite the shipping code that uses it),
without the list of basic requirements to judge which problems it does
solve.

Tony





From owner-ietf@ietf.org  Thu Apr 24 18:38:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08811;
	Thu, 24 Apr 2003 18:38:38 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198pdy-0005iu-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 18:56:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198p6J-0003nj-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 18:21:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05732
	for <ietf@ietf.org>; Thu, 24 Apr 2003 17:59:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198omw-0001yl-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:01:54 -0400
Received: from patan.sun.com ([192.18.98.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 198omv-0001yi-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:01:53 -0400
Received: from esunmail ([129.147.58.198])
	by patan.sun.com (8.9.3p2+Sun/8.9.3) with ESMTP id QAA28790
	for <ietf@ietf.org>; Thu, 24 Apr 2003 16:02:21 -0600 (MDT)
Received: from xpa-fe2 (esunmail [129.147.58.120]) by edgemail1.Central.Sun.COM
 (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
 with ESMTP id <0HDV00HBJBS4OG@edgemail1.Central.Sun.COM> for ietf@ietf.org;
 Thu, 24 Apr 2003 16:00:05 -0600 (MDT)
Received: from sun.com ([129.146.18.22])
 by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
 with ESMTPSA id <0HDV0030BBRX0N@mail.sun.net> for ietf@ietf.org; Thu,
 24 Apr 2003 15:59:58 -0600 (MDT)
Date: Thu, 24 Apr 2003 14:59:57 -0700
From: Alain Durand <Alain.Durand@Sun.COM>
Subject: TCPng/ multiple addresses per node (was Re: A follow up question)_
To: Dave Crocker <dcrocker@brandenburg.com>, ietf@ietf.org,
        ipng@sunroof.eng.sun.com, john-ietf@jck.com
Message-id: <3EA85E5D.10507@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920
 Netscape/7.0
References: <038f01c309eb$2cc8af60$261e4104@eagleswings>
 <131474110615.20030423173851@brandenburg.com>
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

I agree with Dave Crocker that the post from John Klensin is the
first one in thousand of emails that put the discussion in a new
(and very interesting) perspective.

In the goold old IPv4 word, locators & identificators are the same thing.
This is, as many people pointed out, the root cause for a lot of the
hard problems we see today, such as multi-homing & mobility.

We have made the problem even harder in IPv6 by adding more sementic
to specific addresses: we now have addresses that are non permanent
with privacy extensions (RFC3041), transition addresses (6to4, isatap,
IPv4 compatible,...), scoped addresses (Link locals and hoppefuly defunct
site locals), home address vs care-of address, crypto-generated addresses,
and the list grows every day.

Add to this that it is now more and more common for nodes to have multiple
interfaces to different types of networks with different physical 
caracteristics
(wired/wireless, high bandwidth, expensive access..)...

...and we made it even more complex now in the early days of coexistence
of IPv4 and IPv6, when an IPv6 address may have been registered in the DNS
but there is no actual IPv6 path to go there, or if there is
one, it is sometime so boggus that it leads to very bad performances.
(note: nothing to do with v6, just the sate of current deployment)

There is a proposal to create an API to enable the
application creating the socket to specify some of the
properties that it desires/requires. This is a step in the right
direction, but I'm not convinced this can go far enough.
So I fully support this idea of lifting the ban on TCPng
(or any transport layer for that matter) to de-couple
the abstraction needed by applications to the one required
by the network. This is in fact introducing some of the semantic
of a session layer between the application and the network.
Can this be done at the transport layer in the form of TCPng
or does this require and actual additional session layer?
I'm not sure at this point in time.


    - Alain.






From owner-ietf@ietf.org  Thu Apr 24 18:38:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08842;
	Thu, 24 Apr 2003 18:38:56 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198pdy-0005j0-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 18:56:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198oWU-0001qF-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 17:44:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04366
	for <ietf@ietf.org>; Thu, 24 Apr 2003 17:22:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198oD7-0001eR-00
	for ietf@ietf.org; Thu, 24 Apr 2003 17:24:54 -0400
Received: from alicia.nttmcl.com ([216.69.69.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 198oD7-0001eM-00
	for ietf@ietf.org; Thu, 24 Apr 2003 17:24:53 -0400
Received: from alicia.nttmcl.com (localhost [127.0.0.1])
	by alicia.nttmcl.com (8.12.5/8.12.5) with ESMTP id h3OLOmvm058436;
	Thu, 24 Apr 2003 14:24:48 -0700 (PDT)
	(envelope-from jj@alicia.nttmcl.com)
Received: (from jj@localhost)
	by alicia.nttmcl.com (8.12.5/8.12.5/Submit) id h3OLOmDu058435;
	Thu, 24 Apr 2003 14:24:48 -0700 (PDT)
Date: Thu, 24 Apr 2003 14:24:48 -0700
From: Shannon -jj Behrens <jj@nttmcl.com>
To: Tony Hain <alh-ietf@tndh.net>
Cc: "'Keith Moore'" <moore@cs.utk.edu>, john-ietf@jck.com, dts@senie.com,
        ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
Message-ID: <20030424212448.GA56083@alicia.nttmcl.com>
References: <20030424162808.GA52759@alicia.nttmcl.com> <042901c30a9b$757ed1c0$261e4104@eagleswings>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <042901c30a9b$757ed1c0$261e4104@eagleswings>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, Apr 24, 2003 at 12:55:29PM -0700, Tony Hain wrote:

(I'm going to clip much of this email to concentrate on those areas that need
further discussion.)

> > o In light of the fact that not every host has a DNS name, 
> > how do you propose multi-party P2P applications should do 
> > referrals? It would be helpful if you established the normal 
> > mode of operation for such situations.
> 
> As I said in the note to JCK, I have been imprecise about 'name' so
> whatever the app uses to get a handle from the local stack is what it
> needs to pass around. 

If A connects to B, and B wishes to pass the connection info to C, B only has
the address with which A accessed B.  If A and B are in the same site and used
site-local communication, and C is not in that site, B does not have enough
information to refer C to A.  Hence, your suggestion does not solve this case.

> Doing otherwise ignores the reality that the
> network does not look the same from all points.

I agree, and in fact, that's what I'm asking you how to work around.

> > If I'm at 
> > work and wish to 
> > use both my work network *and* my home network via a VPN 
> > connection, I expect I would want my laptop to be a 
> > multi-site node.  If this is the case, do I 
> > need to use %interface_name at the end of all IP's I give to 
> > applications I 
> > use?  How would DNS lookups work on a multi-site node if 
> > site-locals are stored in DNS?
> 
> The name resolver would have to track which interface / site it got
> answers from because any limited scope resolution is only applicable in
> that interface / site context. 

That's true, and that sufficiently solves one side of the problem.  However, 
the other side of the problem is knowing which name resolver to go to in the
first place.  If I use my home resolver, I won't be able to get the address of
(e.g.) my printer, but if I use my work resolver, I won't be able to get the 
address of my toaster.  Do I need to always check both?  It seems that we're
encountering this situation because DNS implicitly assumes (at least in my
limited understanding) that choice of a DNS proxy should not affect the
results.

> > o Do you envision support for Margaret's idea of multiple 
> > concentric rings of security (possibly using site-locals)?  
> > If a node in the outermost ring is not able to talk to a node 
> > in the innermost ring using a site-local address because of 
> > filtering, but is permitted to use a global address, how 
> > shall applications react when the site-local "hint" is 
> > actually misleading?
> 
> Personally I consider those security zones as different sites. This gets
> into the poor definition of 'site', but we were intentionally vague
> there. There is no difference between an FEC0 or 2001-w/Bellovin-Zill
> flag prefix in how one would solve this problem. The fact that SL does
> not provide multiple concentric security zones is not a failure of SL,
> because that was not a design requirement (again we need to agree on the
> problems to be solved). 

Well, that's a fair answer.

By the way, I do applaud your effort in making a site-locals requirements
document.  I think such a document will ultimately be useful if it presents
requirements in such a way that people who wish to replace the functionality
that site-locals provide know what needs replacing.

Thanks,
-jj

-- 
Hacker is to software engineer as 
Climbing Mt. Everest is to building a Denny's there.





From owner-ietf@ietf.org  Thu Apr 24 18:40:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09055;
	Thu, 24 Apr 2003 18:40:35 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198pdz-0005j6-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 18:56:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198pdZ-0005eq-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 18:56:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08682
	for <ietf@ietf.org>; Thu, 24 Apr 2003 18:33:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198pKC-0002UR-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:36:16 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198pKB-0002UO-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:36:16 -0400
Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id XAA12047;
	Thu, 24 Apr 2003 23:36:35 +0100 (BST)
Received: from login.ecs.soton.ac.uk (login [152.78.68.162])
	by pigeon.ecs.soton.ac.uk (8.9.3p2/8.9.3) with ESMTP id XAA27491;
	Thu, 24 Apr 2003 23:36:35 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id h3OMaZj08077;
	Thu, 24 Apr 2003 23:36:35 +0100
Date: Thu, 24 Apr 2003 23:36:35 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Eliot Lear <lear@cisco.com>
Cc: alh-ietf@tndh.net, "'John C Klensin'" <john-ietf@jck.com>,
        "'Daniel Senie'" <dts@senie.com>, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
Message-ID: <20030424223635.GB6776@login.ecs.soton.ac.uk>
Mail-Followup-To: Eliot Lear <lear@cisco.com>, alh-ietf@tndh.net,
	'John C Klensin' <john-ietf@jck.com>,
	'Daniel Senie' <dts@senie.com>, ietf@ietf.org,
	ipng@sunroof.eng.sun.com
References: <044201c30aad$00df25b0$261e4104@eagleswings> <3EA86490.8060501@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3EA86490.8060501@cisco.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, Apr 24, 2003 at 03:26:24PM -0700, Eliot Lear wrote:
> Tony Hain wrote:
> >
> >Where is the document that shows what requirements need to be solved? 
> 
> How about starting with the IPng archives?!  They're actually more 
> persistant than, say, an internet draft, anyway.

No need to bother, just read any sample of 100 ipng emails in one day and
the same arguments come up again and again.  And again.

Is there a WG chair in the house?

Tim



From owner-ietf@ietf.org  Thu Apr 24 18:44:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09357;
	Thu, 24 Apr 2003 18:44:13 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198pl0-000736-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 19:03:58 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198pkW-0006oM-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 19:03:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09159
	for <ietf@ietf.org>; Thu, 24 Apr 2003 18:41:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198pR9-0002dV-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:43:27 -0400
Received: from scaup.mail.pas.earthlink.net ([207.217.120.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 198pR9-0002dP-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:43:27 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by scaup.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 198pRS-0003vZ-00; Thu, 24 Apr 2003 15:43:46 -0700
Date: Thu, 24 Apr 2003 18:43:10 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, john-ietf@jck.com, dts@senie.com, ietf@ietf.org,
        ipng@sunroof.eng.sun.com
Subject: Re: A follow up question
Message-Id: <20030424184310.7328b605.moore@cs.utk.edu>
In-Reply-To: <044801c30ab0$a5d97680$261e4104@eagleswings>
References: <20030424172529.710c9a73.moore@cs.utk.edu>
	<044801c30ab0$a5d97680$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (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

> > if the architecutral guidance were crisp it certainly 
> > wouldn't be asking the DNS related WGs to discuss those 
> > issues.  DNS cannot solve this problem.
> 
> I agree all infrastructure & components that pass around topology
> information need work, but DNS is one of those, so it is a good place to
> start.

disagree.  "starting" to work on this within DNS would be a distraction at
best.


> > > As long as the handle stays contained within the machine you are fine.
> > > The problem arises when the app passes that handle to another node,
> > > believing that the topology specific information is already there. If 
> > > the blob passed were the same as what the app used to acquire the  local
> > > handle, the other nodes would acquire appropriate local handles.
> > 
> > this presupposes that the blob that is passed is precisely 
> > and reliably bound to the specific host or process that the 
> > app wants to refer to, and also that the lookup process that 
> > maps blobs to locators and/or identifiers is sufficiently 
> > fast and robust.  often neither of these conditions holds.
> 
> If the first one doesn't hold, the origin node can't use it so the whole
> app is broken. 

false.  it happens all the time.   a function that converts a service name to
an address doesn't have to produce identical results each time to be useful. 
and yet, if two separate processes need to connect to the exact same process,
the service name alone may not be sufficient to allow them to do that. 

> Speed is an implementation issue, not a spec issue. 

false.  depending on how you architect a service there can be fundamental
and/or practical limits to speed. 

> In any case, it is much faster to pass a blob that can be mapped into
> useful topology information, than it is  to pass around useless topology
> information.

it's even faster if the network provides uniform addressing; then the
addresses are no longer useless.  why do you keep trying to force useless
addresses on us when we can have useful ones at less cost?


> > heaven forbid that apps would assume the same thing that the 
> > IP network was designed to assume - that there is a uniform 
> > address space across the entire network.  but you want to 
> > change this fundamental architectural design point at layer 3 
> > and then claim that the resulting problems are caused by 
> > inappropriate assumptions at layer 7.  some would say this is 
> > layering violation, but the sharing of identifiers between 
> > layer 7 and layer 3 is another fundamental architectural design point.
> 
> I am not saying that. From day one, a host that had one interface where
> the address prefix was not passed widely in the routing system, and
> another where the prefix was passed globally would have exactly the same
> issues you are complaining about. 

it's hardly relevant, since that's not the way things happened.

> This says nothing about firewalling,
> qos, ambiguous addresses, etc. This is simply about a host having
> multiple addresses, where different points in the network have different
> perceptions about the viability of those. 

yup.  and the realization that this is a lousy way to design a network

> The fact that over the years a
> simplification was done through the assumption that there was only a
> single view is a failure. 

and in fact it's a very useful and compelling simplification.


> > But it's not clear that SL was actually intended to solve any 
> > of these problems.  Rather, it seems to me that somebody 
> > thought SL was a good idea, and put it into the v6 
> > architecture.  And then various people started saying "hey, 
> > we can use SL for X", and nobody bothered to examine whether 
> > there were conflicts between those various peoples' 
> > assumptions (whether specifically about SL or not), or even 
> > whether SL was worth the cost, until recently.
> 
> Fine, we need to create the list, figure out alternatives and as you
> said in SF, push SL into the corner cases, if we still need it. Getting
> rid of SL first does not solve the problems. 

we've tried going on the assumption that SL will work, and we've not been able
to resolve the conflicts and problems that result from that assumption.  now
we need to try the assumption that we can do without SL, and see where that
leads.  perhaps we will find that we can do without SL, or perhaps we will
still need SL for a couple of corner cases.  we won't know for sure until we
try to work out the details, and we won't have completely decided for sure
until we actually approve a specification that incorporates those details. 
but that's the direction that the WG has decided to pursue, and I think it's
the right one.


Keith



From owner-ietf@ietf.org  Thu Apr 24 18:49:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05846;
	Thu, 24 Apr 2003 18:02:46 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198p68-0003nh-00
	for ietf-list@ran.ietf.org; Thu, 24 Apr 2003 18:21:44 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198p4w-0003jt-00
	for ietf@ran.ietf.org; Thu, 24 Apr 2003 18:20:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05663
	for <ietf@ietf.org>; Thu, 24 Apr 2003 17:58:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198olZ-0001xt-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:00:29 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 198olZ-0001xq-00
	for ietf@ietf.org; Thu, 24 Apr 2003 18:00:29 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26342> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 24 Apr 2003 15:00:55 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Shannon -jj Behrens'" <jj@nttmcl.com>
Cc: "'Keith Moore'" <moore@cs.utk.edu>, <john-ietf@jck.com>, <dts@senie.com>,
        <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
Subject: RE: A follow up question
Date: Thu, 24 Apr 2003 15:00:54 -0700
Message-ID: <044001c30aac$fababaa0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030424212448.GA56083@alicia.nttmcl.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA05846

Shannon -jj Behrens wrote:
> If A connects to B, and B wishes to pass the connection info 
> to C, B only has the address with which A accessed B.  If A 
> and B are in the same site and used site-local communication, 
> and C is not in that site, B does not have enough information 
> to refer C to A.  Hence, your suggestion does not solve this case.

I agree, but is it reasonable for B to tell C to talk to A, or is it
more reasonable for B to tell A to connect to C by the 'name blob' it
would have used to contact C? 

Please don't think I am picking on this instance, but the whole mode of
attack by finding a failure case, without thinking through alternatives
is a waste of everyone's time.

> 
> > Doing otherwise ignores the reality that the
> > network does not look the same from all points.
> 
> I agree, and in fact, that's what I'm asking you how to work around.

See above about changing the message sequence.

> ...
> That's true, and that sufficiently solves one side of the 
> problem.  However, 
> the other side of the problem is knowing which name resolver 
> to go to in the first place.  

Unless there is some hint in the name string, the only approach I know
of is to shotgun all the servers.

> If I use my home resolver, I 
> won't be able to get the address of
> (e.g.) my printer, but if I use my work resolver, I won't be 
> able to get the 
> address of my toaster.  Do I need to always check both?  It 
> seems that we're encountering this situation because DNS 
> implicitly assumes (at least in my limited understanding) 
> that choice of a DNS proxy should not affect the results.

Which is my argument to the IAB: the infrastructure components that pass
around topology information are completely out of step with the reality
of the deployed network topology. We need to fix this because it will
not get better on its own.

> ...
> > The fact that SL does not provide multiple concentric 
> security zones 
> > is not a failure of SL, because that was not a design requirement 
> > (again we need to agree on the problems to be solved).
> 
> Well, that's a fair answer.
> 
> By the way, I do applaud your effort in making a site-locals 
> requirements document.  I think such a document will 
> ultimately be useful if it presents requirements in such a 
> way that people who wish to replace the functionality that 
> site-locals provide know what needs replacing. 

I am not trying to claim I have all the answers, so if anyone has
content for it, please send them.

Tony






From owner-ietf@ietf.org  Fri Apr 25 00:01:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14761;
	Fri, 25 Apr 2003 00:01:56 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198uda-0000DD-00
	for ietf-list@ran.ietf.org; Fri, 25 Apr 2003 00:16:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198ud9-0000BM-00
	for ietf@ran.ietf.org; Fri, 25 Apr 2003 00:16:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14652
	for <ietf@ietf.org>; Thu, 24 Apr 2003 23:53:48 -0400 (EDT)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198uJj-0004Pa-00
	for ietf@ietf.org; Thu, 24 Apr 2003 23:56:07 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 198uJi-0004PX-00
	for ietf@ietf.org; Thu, 24 Apr 2003 23:56:06 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h3P3uUD12294
	for <ietf@ietf.org>; Fri, 25 Apr 2003 06:56:30 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T61d0049ac4ac158f24078@esvir04nok.ntc.nokia.com>;
 Fri, 25 Apr 2003 06:56:30 +0300
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 25 Apr 2003 06:56:30 +0300
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebe013.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 25 Apr 2003 06:56:29 +0300
content-class: urn:content-classes:message
Subject: RE: A follow up question
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Fri, 25 Apr 2003 06:56:29 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Message-ID: <DADF50F5EC506B41A0F375ABEB32063623188A@esebe023.ntc.nokia.com>
Thread-Topic: A follow up question
Thread-Index: AcMKsshATWyTs2g+SrmbVqs3GuqZGgAK7OZg
To: <tjc@ecs.soton.ac.uk>, <lear@cisco.com>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
X-OriginalArrivalTime: 25 Apr 2003 03:56:29.0659 (UTC) FILETIME=[A6F4E2B0:01C30ADE]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA14761

Hi Tim,

> > How about starting with the IPng archives?!  They're actually more 
> > persistant than, say, an internet draft, anyway.
> 
> No need to bother, just read any sample of 100 ipng emails in one day and
> the same arguments come up again and again.  And again.

Just to second this - and its a process guestion (wait, there is another
working group focused on that ...) - I thought that, at the end of the 
day, we are supposed to be making standards, not mailing list
archives ....

John



From owner-ietf@ietf.org  Fri Apr 25 00:49:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14760;
	Fri, 25 Apr 2003 00:01:56 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198uag-00007N-00
	for ietf-list@ran.ietf.org; Fri, 25 Apr 2003 00:13:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198uZz-00005b-00
	for ietf@ran.ietf.org; Fri, 25 Apr 2003 00:12:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14581
	for <ietf@ietf.org>; Thu, 24 Apr 2003 23:50:32 -0400 (EDT)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198uGY-0004Nw-00
	for ietf@ietf.org; Thu, 24 Apr 2003 23:52:50 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 198uGX-0004Nt-00
	for ietf@ietf.org; Thu, 24 Apr 2003 23:52:50 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h3P3rG725904
	for <ietf@ietf.org>; Fri, 25 Apr 2003 06:53:16 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T61d001a219ac158f21083@esvir01nok.ntc.nokia.com>;
 Fri, 25 Apr 2003 06:53:15 +0300
Received: from esebe003.NOE.Nokia.com ([172.21.138.39]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 25 Apr 2003 06:53:15 +0300
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebe003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 25 Apr 2003 06:53:15 +0300
content-class: urn:content-classes:message
Subject: RE: TCPng/ multiple addresses per node (was Re: A follow up question)_
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Fri, 25 Apr 2003 06:53:14 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Message-ID: <DADF50F5EC506B41A0F375ABEB320636231889@esebe023.ntc.nokia.com>
Thread-Topic: TCPng/ multiple addresses per node (was Re: A follow up question)_
Thread-Index: AcMKrc6e7EZbcTUySQKrh1d6eAMVwgAL7SMA
To: <Alain.Durand@Sun.COM>, <dcrocker@brandenburg.com>, <ietf@ietf.org>,
        <ipng@sunroof.eng.sun.com>, <john-ietf@jck.com>
X-OriginalArrivalTime: 25 Apr 2003 03:53:15.0162 (UTC) FILETIME=[3306FFA0:01C30ADE]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA14760

Hi Alain,

I agree with your intro (which I clipped to save space), one
comment that I have is:

> There is a proposal to create an API to enable the
> application creating the socket to specify some of the
> properties that it desires/requires. This is a step in the right
> direction, but I'm not convinced this can go far enough.
> So I fully support this idea of lifting the ban on TCPng
> (or any transport layer for that matter) to de-couple
> the abstraction needed by applications to the one required
> by the network. This is in fact introducing some of the semantic
> of a session layer between the application and the network.
> Can this be done at the transport layer in the form of TCPng
> or does this require and actual additional session layer?
> I'm not sure at this point in time.

There already something like this, I'm sure you know - SCTP.
I'm actually not trying to promote SCTP, but it might be interesting,
as we have an RFC that does most of the avove, to look at it
critically & see how it performs.  

SCTP, as a background, uses sets of addresses/ports to identify a
node. In the usual case, one node will pass all of its addresses(& ports)
to its peer & the peer returns its addresses (&ports) for SCTP 
traffic.  The application has the the option to choose the primary
address to be used.  

Right now, SCTP has limited users (Diameter, SIGTRAN and probably a couple
of other protocols).  It would be interesting to see that others
can do with it.

John



From owner-ietf@ietf.org  Fri Apr 25 02:51:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28984;
	Fri, 25 Apr 2003 02:51:31 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198xJ5-0003d1-00
	for ietf-list@ran.ietf.org; Fri, 25 Apr 2003 03:07:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198xIg-0003bJ-00
	for ietf@ran.ietf.org; Fri, 25 Apr 2003 03:07:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28938
	for <ietf@ietf.org>; Fri, 25 Apr 2003 02:44:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198wzE-0005YA-00
	for ietf@ietf.org; Fri, 25 Apr 2003 02:47:08 -0400
Received: from web20706.mail.yahoo.com ([216.136.226.179])
	by ietf-mx with smtp (Exim 4.12)
	id 198wzD-0005Y7-00
	for ietf@ietf.org; Fri, 25 Apr 2003 02:47:07 -0400
Message-ID: <20030425064735.33822.qmail@web20706.mail.yahoo.com>
Received: from [210.118.108.254] by web20706.mail.yahoo.com via HTTP; Fri, 25 Apr 2003 02:47:35 EDT
Date: Fri, 25 Apr 2003 02:47:35 -0400 (EDT)
From: Tulip Rasputin <tulip_rasputin@yahoo.ca>
Subject: Patents and IETF
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Hello,
Have there been any patents filed in the field of routing/routing protocols?

I am a little confused because we have IETF standards (drafts and RFCs)for routing. Is there a
rule which says that one cant file patents in routing or something?

I would be really very grateful if somebody could answer this for me.

Thanks and Regards,
Rasputin

______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca



From owner-ietf@ietf.org  Fri Apr 25 05:43:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01435;
	Fri, 25 Apr 2003 05:43:19 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 198zyZ-0000W3-00
	for ietf-list@ran.ietf.org; Fri, 25 Apr 2003 05:58:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 198zyG-0000UO-00
	for ietf@ran.ietf.org; Fri, 25 Apr 2003 05:58:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01363
	for <ietf@ietf.org>; Fri, 25 Apr 2003 05:35:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198zel-0006Kv-00
	for ietf@ietf.org; Fri, 25 Apr 2003 05:38:11 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 198zel-0006Kd-00
	for ietf@ietf.org; Fri, 25 Apr 2003 05:38:11 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id A704D6256B; Fri, 25 Apr 2003 11:38:09 +0200 (CEST)
Date: Fri, 25 Apr 2003 11:38:09 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Tulip Rasputin <tulip_rasputin@yahoo.ca>, ietf@ietf.org
Subject: Re: Patents and IETF
Message-ID: <677750000.1051263489@askvoll.hjemme.alvestrand.no>
In-Reply-To: <20030425064735.33822.qmail@web20706.mail.yahoo.com>
References:  <20030425064735.33822.qmail@web20706.mail.yahoo.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On fredag, april 25, 2003 02:47:35 -0400 Tulip Rasputin 
<tulip_rasputin@yahoo.ca> wrote:

> Hello,
> Have there been any patents filed in the field of routing/routing
> protocols?

Yes.
http://www.uspto.gov/patft/ allows you to search on "Routing AND protocol", 
and tells you that you have 14604 hits :-(

>
> I am a little confused because we have IETF standards (drafts and
> RFCs)for routing. Is there a rule which says that one cant file patents
> in routing or something?

No. And the lack of such a rule is not making life in the IETF any easier.




From owner-ietf@ietf.org  Fri Apr 25 12:35:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13937;
	Fri, 25 Apr 2003 12:35:26 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1996Mf-0003NA-00
	for ietf-list@ran.ietf.org; Fri, 25 Apr 2003 12:47:57 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1996Kb-0003Jn-00
	for ietf@ran.ietf.org; Fri, 25 Apr 2003 12:45:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13606
	for <ietf@ietf.org>; Fri, 25 Apr 2003 12:23:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199612-0001pD-00
	for ietf@ietf.org; Fri, 25 Apr 2003 12:25:36 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 199611-0001p9-00
	for ietf@ietf.org; Fri, 25 Apr 2003 12:25:35 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S264A4> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 25 Apr 2003 09:25:54 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>,
        "'Tulip Rasputin'" <tulip_rasputin@yahoo.ca>, <ietf@ietf.org>
Subject: RE: Patents and IETF
Date: Fri, 25 Apr 2003 09:25:54 -0700
Message-ID: <04f501c30b47$5a58f9f0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <677750000.1051263489@askvoll.hjemme.alvestrand.no>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald Tveit Alvestrand wrote:
> --On fredag, april 25, 2003 02:47:35 -0400 Tulip Rasputin 
> <tulip_rasputin@yahoo.ca> wrote:
> 
> > Hello,
> > Have there been any patents filed in the field of routing/routing 
> > protocols?
> 
> Yes.
> http://www.uspto.gov/patft/ allows you to search on "Routing 
> AND protocol", 
> and tells you that you have 14604 hits :-(
> 
> >
> > I am a little confused because we have IETF standards (drafts and 
> > RFCs)for routing. Is there a rule which says that one cant file 
> > patents in routing or something?
> 
> No. And the lack of such a rule is not making life in the 
> IETF any easier.

Harald,

While that is correct, he probably needs a pointer to:
http://www.ietf.org/rfc/rfc2026.txt?number=2026

section 10.

Tony





From owner-ietf@ietf.org  Fri Apr 25 12:50:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14517;
	Fri, 25 Apr 2003 12:50:21 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1996hz-00053o-00
	for ietf-list@ran.ietf.org; Fri, 25 Apr 2003 13:09:59 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1996h9-000509-00
	for ietf@ran.ietf.org; Fri, 25 Apr 2003 13:09:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14416
	for <ietf@ietf.org>; Fri, 25 Apr 2003 12:46:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1996Na-00021y-00
	for ietf@ietf.org; Fri, 25 Apr 2003 12:48:54 -0400
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by ietf-mx with esmtp (Exim 4.12)
	id 1996NZ-000210-00
	for ietf@ietf.org; Fri, 25 Apr 2003 12:48:54 -0400
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 81AF76256B; Fri, 25 Apr 2003 18:48:50 +0200 (CEST)
Date: Fri, 25 Apr 2003 18:48:50 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: alh-ietf@tndh.net, "'Tulip Rasputin'" <tulip_rasputin@yahoo.ca>,
        ietf@ietf.org
Subject: RE: Patents and IETF
Message-ID: <729410000.1051289330@askvoll.hjemme.alvestrand.no>
In-Reply-To: <04f501c30b47$5a58f9f0$261e4104@eagleswings>
References:  <04f501c30b47$5a58f9f0$261e4104@eagleswings>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On fredag, april 25, 2003 09:25:54 -0700 Tony Hain <alh-ietf@tndh.net> 
wrote:

>> >
>> > I am a little confused because we have IETF standards (drafts and
>> > RFCs)for routing. Is there a rule which says that one cant file
>> > patents in routing or something?
>>
>> No. And the lack of such a rule is not making life in the
>> IETF any easier.
>
> Harald,
>
> While that is correct, he probably needs a pointer to:
> http://www.ietf.org/rfc/rfc2026.txt?number=2026
>
> section 10.

actually what I was trying to say is that there is no rule in the patent 
system against patenting technology relevant to the IETF, and as a result, 
the IETF has to wade through an ever-deepening sea of patent-related issues 
when trying to make standards.

I guess my penchant for cute turns of phrase got the better of me :-)

                 Harald




From owner-ietf@ietf.org  Fri Apr 25 16:26:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21509;
	Fri, 25 Apr 2003 16:26:10 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 1999fW-0002j0-00
	for ietf-list@ran.ietf.org; Fri, 25 Apr 2003 16:19:38 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 1999bl-0002Qj-00
	for ietf@ran.ietf.org; Fri, 25 Apr 2003 16:15:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20376
	for <ietf@ietf.org>; Fri, 25 Apr 2003 15:53:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1999IT-0003Ce-00
	for ietf@ietf.org; Fri, 25 Apr 2003 15:55:49 -0400
Received: from mail5.microsoft.com ([131.107.3.121])
	by ietf-mx with esmtp (Exim 4.12)
	id 1999IS-0003C6-00
	for ietf@ietf.org; Fri, 25 Apr 2003 15:55:48 -0400
Received: from mail6.microsoft.com ([157.54.6.196]) by mail5.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624);
	 Fri, 25 Apr 2003 12:55:47 -0700
Received: from inet-vrs-06.redmond.corp.microsoft.com ([157.54.6.181]) by mail6.microsoft.com with Microsoft SMTPSVC(5.0.2195.5600);
	 Fri, 25 Apr 2003 12:55:46 -0700
Received: from 157.54.8.23 by inet-vrs-06.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 25 Apr 2003 12:55:46 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.5600);
	 Fri, 25 Apr 2003 12:55:46 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.5600);
	 Fri, 25 Apr 2003 12:55:45 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3788.0);
	 Fri, 25 Apr 2003 12:55:44 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6851.8
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: RE: Patents and IETF
Date: Fri, 25 Apr 2003 12:55:18 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA02F06532@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Patents and IETF
Thread-Index: AcMLS0ilz/Q54JFwR5CEqaAqpqo53wAGPNgg
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>, <alh-ietf@tndh.net>,
        "Tulip Rasputin" <tulip_rasputin@yahoo.ca>, <ietf@ietf.org>
X-OriginalArrivalTime: 25 Apr 2003 19:55:44.0650 (UTC) FILETIME=[A8678EA0:01C30B64]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA21509

This message, by the way, raises another issue. "Tulip Rasputin" writes
that "we have IETF standards (drafts and RFCs) for routing."  Equating
drafts or even RFC with IETF standards shows a serious misunderstanding
of the process. Anybody with a keyboard and spare time can compose a
draft, and such drafts do not engage the IETF in any way. And, also, not
all RFC are standard (see RFC 1796).

-- Christian Huitema




From owner-ietf@ietf.org  Sat Apr 26 00:06:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02027;
	Sat, 26 Apr 2003 00:06:38 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 199GSq-0001w8-00
	for ietf-list@ran.ietf.org; Fri, 25 Apr 2003 23:35:00 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 199GQV-0001rk-00
	for ietf@ran.ietf.org; Fri, 25 Apr 2003 23:32:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00949
	for <ietf@ietf.org>; Fri, 25 Apr 2003 23:10:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199G7a-0005Gf-00
	for ietf@ietf.org; Fri, 25 Apr 2003 23:13:02 -0400
Received: from wetware.wetware.com ([199.108.16.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199G7a-0005GP-00
	for ietf@ietf.org; Fri, 25 Apr 2003 23:13:02 -0400
Received: from wetware.com(ra09.wetware.com[199.108.16.89]) (8262 bytes) by wetware.wetware.com
	via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp
	(sender: <jhw@wetware.com>) 
	id <m199G7a-002zTnC@wetware.wetware.com>
	for <ietf@ietf.org>; Fri, 25 Apr 2003 20:13:02 -0700 (PDT)
	(Smail-3.2.0.114 2001-Aug-6 #1 built 2002-Sep-2)
Date: Fri, 25 Apr 2003 20:13:06 -0700
Subject: Re: A follow up question
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: IPng List <ipng@sunroof.eng.sun.com>, IETF list <ietf@ietf.org>
To: tony hain <alh-ietf@tndh.net>
From: james woodyatt <jhw@wetware.com>
In-Reply-To: <042901c30a9b$757ed1c0$261e4104@eagleswings>
Message-Id: <FFE2EEA0-7794-11D7-A7C3-000393BA7EBA@wetware.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I've been following this thread with great interest for weeks, and only 
now do I think I have useful contribution to make to the discussion.  
It's long.  Sorry about that.  Cope.

On Thursday, Apr 24, 2003, at 12:55 US/Pacific, Tony Hain wrote:
> [...]
> Leading people away from something comfortable requires providing
> something that meets the same basic need and is easier/cheaper/more
> comfortable. Many use NAT because they can't get STABLE addresses
> otherwise, and NAT is simply the cost of getting that. Providing STABLE
> local use prefixes simultaneously with global prefixes that may change
> over time is a cheaper way to meet the need for STABLE addresses.
>
> * I emphasize STABLE because that is a invariant requirement by many
> managers of large networks.
> [...]

I don't know whether to laugh or cry.  Using a NAT doesn't give you 
address stability.  It's a total illusion.

Sure, your hosts all get RFC 1918 addresses that you assign yourself, 
but your NAT has to have at least one public realm address or the whole 
drill is pointless.  Without the NAT, you might as well set yourself up 
as your own private IANA-- you can be the King of Jellybeanland, if you 
like.

If you really want stable addresses, it seems to me (and correct me if 
I'm technically wrong about this) the only way you get that is to get 
yourself an AS number and a collection of prefixes and go into a BGP 
peering relationship.  Otherwise, you have to renumber every time your 
default route provider tells you it's your turn.

What the NAT really does for you is reduce the complexity of your 
renumbering events.  When the provider for your default route tells you 
it's your turn to renumber this week, you just renumber the NAT-- no 
manual editing of /etc/hosts with /usr/bin/vi is required on every 
Sun-3 on your network, isn't that nice?

Coping with the termination of application flows through the NAT when 
it gets renumbered is the main problem that has to be managed here.  
Note: site-local addresses and NAT do not solve this problem, and they 
were never intended for that purpose.  It's a problem that has to be 
managed in *any* renumbering, and the only way to avoid it is to avoid 
renumbering events entirely.  Good luck on that; write if you get 
funding.

If we're going to have a useful discussion about "the renumbering 
problem," we need to start by recognizing that it's more than simply 
reconfiguring routers and the bestiary of other middleboxen that seem 
to be inserting themselves into the network everywhere.

Applications have bad habits.

They cache network addresses when they should be caching names.  There 
is never a decent mechanism for keeping the cache coherent with the 
actual topology of the network.  Frequent renumbering exposes these bad 
habits.  Network administrators quickly learn that there is no pain 
more exquisite than explaining to the CFO that the reason the payroll 
isn't getting processed is that the ISP forced a renumbering and 
there's no good way to fix the application databases in the data center 
that have the wrong IP addresses stored in them.  Worse, you probably 
can't even sue the vendor for selling shoddy code because of the 
"as-is" "unwarranted" foo in the contract language.

And you might have written the code yourself.  Now *there's* pain.

So with IPv4, everyone uses a NAT, and they don't have this hassle.  
They have other huge hassles as a result, but at least they don't have 
*this* one.  And they love it.

Applications can continue to be written by code monkeys with no clear 
concept of how the network really works, they can cache network 
addresses in labels with permanent adhesive glue affixed to the rack 
where the equipment is mounted, they can treat network addresses like 
they map one-for-one with nodes (even nodes with multiple interfaces), 
they can even force lowly users to memorize them and transcribe them by 
hand, and the network administrators can still keep the business logic 
from crashing and staying down for a week when the public addresses of 
the site have to be renumbered.

Sometimes I think the biggest mistake we ever made was letting the 
application coders set their eyes on the bits in the network address.  
Giving them a human-readable representation was a mistake.  Even 
letting them know how many bits are in an address was ill-advised.  I 
know better of course, but then... *I'm* one of those poor souls with 
the dubious honor of having written an ALG for IPsec VPN applications.  
It's personal with me.

The really bad news-- I hate to break this-- is that IPv6 won't 
magickally make applications developers smarter.  When existing 
applications are extended to IPv6 and new applications are developed 
with IPv6 in mind, they will be developed by the same people with the 
same misconceptions about how the network works.  Our API's for using 
IPv6 look too much like the ones for IPv4 to break those misconceptions.

People will continue to cache network addresses on printed labels glued 
to the rack and they will continue to expect users to memorize and 
transcribe them by hand.  We can keep telling them not to do it, 
*but*... why should we expect them to start listening to us?  They 
never have done before, and we've been droning on about it for more 
years than I can count.

It would be just peachy if there was an architecture available that 
would preserve the E2E principle while still permitting organizations 
to shield their private applications from having to be just barely 
smart enough to respond well to their nodes experiencing the 
renumbering of their global unicast node addresses.  I don't think 
there is one.

I'm reminded of Oscar Wilde's reported last words.  Maybe we need to 
learn how to make the drapes match the rest of the decor.

If the problem with site-local addresses is that they cause more 
problems than they solve-- and I believe that to be true-- then, maybe 
solving the problems they cause is a good idea.  I have a radical 
proposal to that effect: deprecate the site-local prefix (on the 
grounds that it is overkill); disallow the propagation of routes for 
all V4MAPPED addresses; disallow the forwarding of packets with 
V4MAPPED addresses anywhere in the header; *except*, allow interior 
routing protocols, as a transition mechanism, to propagate routes for 
V4MAPPED addresses in prefixes that correspond to the RFC 1918 
addresses, and allow such packets to be forwarded on interior links.

This will permit impolite applications to move to IPv6 without having 
to learn better manners, while allowing network administrators a 
transition path for supporting their applications until they get 
versions that can handle renumbering events without bursting into 
flames.

And plusplusgood: it contains the disease within the quarantine wire of 
the IPv4 transition foo.  The addresses are all still about as 
memorizable as the ones we are all using now.  Even better, the 
function for getting the IPv6 address for a host from the IPv4 address 
that is printed on the label glued to the rack is to prepend the 
"::FFFF:" string to it and you're off to breakfast.  Still better: if 
you're clever, you can even forbid V4MAPPED addresses of every stripe 
from showing up in AAAA records by requiring applications that depend 
on this transition mechanism to work to convert IPv4 addresses into 
V4MAPPED addresses explicitly.

There.  I'm done.  Back to lurk mode.


-- 
j h woodyatt <jhw@wetware.com>
that's my village calling... no doubt, they want their idiot back.




From owner-ietf@ietf.org  Sat Apr 26 03:24:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14940;
	Sat, 26 Apr 2003 03:24:32 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 199J77-0006lc-00
	for ietf-list@ran.ietf.org; Sat, 26 Apr 2003 02:24:45 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 199J53-0006ga-00
	for ietf@ran.ietf.org; Sat, 26 Apr 2003 02:22:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05735
	for <ietf@ietf.org>; Sat, 26 Apr 2003 02:01:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199In6-0005mw-00
	for ietf@ietf.org; Sat, 26 Apr 2003 02:04:04 -0400
Received: from dialin-151-222.tor.primus.ca ([216.254.151.222] helo=lethargic.dyndns.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 199In5-0005mt-00
	for ietf@ietf.org; Sat, 26 Apr 2003 02:04:03 -0400
Received: from lethargic.dyndns.org (localhost [127.0.0.1])
	by lethargic.dyndns.org (8.12.9/8.12.9) with ESMTP id h3Q64MlF093382;
	Sat, 26 Apr 2003 02:04:23 -0400 (EDT)
	(envelope-from leth@lethargic.dyndns.org)
Received: (from leth@localhost)
	by lethargic.dyndns.org (8.12.9/8.12.9/Submit) id h3Q64LD5093381;
	Sat, 26 Apr 2003 02:04:21 -0400 (EDT)
Date: Sat, 26 Apr 2003 02:04:20 -0400
From: Jason Hunt <leth@primus.ca>
To: ietf@ietf.org
Cc: ipng@sunroof.eng.sun.com, Keith Moore <moore@cs.utk.edu>,
        Tony Hain <alh-ietf@tndh.net>
Subject: My thoughts on local-use addresses
Message-ID: <20030426060420.GA93218@lethargic.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Sender: owner-ietf@ietf.org
Precedence: bulk

I decided I will come out of "lurk mode" and try to express my thoughts
about local-use addresses.  I have been following the thread on the IETF
general mailing list regarding site-local addresses.  The following
things may have already been discussed, as I only just recently
subscribed to the IPNG mailing list.

I think all unicast addresses should be "global", instead of having
any scopes at all.  I believe this would promote the whole E2E concept.

Local-use addresses seem to be redundant.  Why would one need to address
a host on the same site or same link using an address other than its'
global address?  (Sorry if that is confusing)  One scenario I thought of
is back-end servers (ie: database servers) that do not need to be
globally accessible, but other front-end servers (ie: web servers) need
to communicate with these back-end servers.  This is what a private
address space would be for, and you would likely have multiple
interfaces on seperate networks (one public, one private) to segregate
the traffic.

I suggest that:

a) The site-local and link-local address scopes be abandoned.  As I
stated above, I believe they are redundant and therefore not needed.  If
you want to address all of the hosts at your site or on your link, why
not use multicast?  Are there any practical cases where one would use
these scopes instead of global addresses that a private space or
multi-cast would not solve?

b) I believe that RFC 2462 (IPv6 Stateless Address Autoconfiguration)
already deals with this, but I will mention it anyways; the link-local
address space (or possibly some other space) be used as a fall-back for
auto-configuration purposes.  If a host is not configured with a static
address, and does not have DHCP client capabilities or the host does not
receive a response from a DHCP server, then an auto-configured
address could be assigned to the interface.  I think this would make it
so that "it just works" if someone wants to plug a bunch of IPv6 hosts
on to a LAN and use some type of neighbor disocvery mechanism to let the
hosts find each other and start communicating.

c) The link-local address space (or, again, some other space) be made
available as private address space.  It would for use by administrators
of networks that are not planning to be connected to the Internet but
still need an address space to use.  Is this not the intention of RFC
1918 addresses as well?  Is there any reason to not provide a private
addres space?  I don't want to start discussions about NAT because
that's not what it the private address space will always be used for.

Comments and constructive critisism are appreciated.




From owner-ietf@ietf.org  Sat Apr 26 14:17:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24616;
	Sat, 26 Apr 2003 14:16:54 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 199Sw7-0008Ap-00
	for ietf-list@ran.ietf.org; Sat, 26 Apr 2003 12:54:03 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 199Stw-000873-00
	for ietf@ran.ietf.org; Sat, 26 Apr 2003 12:51:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23005
	for <ietf@ietf.org>; Sat, 26 Apr 2003 12:41:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199Sm5-0000MM-00
	for ietf@ietf.org; Sat, 26 Apr 2003 12:43:41 -0400
Received: from dialin-160-56.tor.primus.ca ([216.254.160.56] helo=lethargic.dyndns.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 199Slf-0000M8-00
	for ietf@ietf.org; Sat, 26 Apr 2003 12:43:15 -0400
Received: from lethargic.dyndns.org (localhost [127.0.0.1])
	by lethargic.dyndns.org (8.12.9/8.12.9) with ESMTP id h3QGgvlF098185;
	Sat, 26 Apr 2003 12:43:02 -0400 (EDT)
	(envelope-from leth@lethargic.dyndns.org)
Received: (from leth@localhost)
	by lethargic.dyndns.org (8.12.9/8.12.9/Submit) id h3QGgu6D098184;
	Sat, 26 Apr 2003 12:42:56 -0400 (EDT)
Date: Sat, 26 Apr 2003 12:42:55 -0400
From: Jason Hunt <leth@primus.ca>
To: ipng@sunroof.eng.sun.com
Cc: ietf@ietf.org, Keith Moore <moore@cs.utk.edu>,
        Tony Hain <alh-ietf@tndh.net>
Subject: Re: My thoughts on local-use addresses
Message-ID: <20030426164255.GA98043@lethargic.dyndns.org>
References: <20030426060420.GA93218@lethargic.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030426060420.GA93218@lethargic.dyndns.org>
User-Agent: Mutt/1.4.1i
Sender: owner-ietf@ietf.org
Precedence: bulk

I've done a bit more thinking regarding my previous post.  I am going to
restate the things that I suggested, in case my previous message left
anything un-clear.

I would like to suggest that:

- The idea of scopes be removed from unicast addresses.  Why add the
  complexity of scopes?  Is it not better to keep things simple?

- The link-local address space (FE80::/10), or some other space, be
  available as "private use" address space, similar to what RFC 1918 is
  to IPv4.  I realize that the current definition of the local-use
  addresses already provides this, but since I am suggesting to change
  that definition it seemed necessary to make this point.

- All interfaces be required to have at least one unicast address
  assigned to them, instead of being required to have a link-local
  address in addition to any other addresses.  If an interface is not
  configured with an address, and the host is unable to obtain an
  address from a DHCP server (or some other dynamic configuration
  protocol) for that interface, then the interface will be auto-
  configured with an address from the above-mentioned "private use"
  space (FE80::/10 or otherwise).  

Can anyone point out any practical scenarios for scoped addresses to
be required, which could not be dealt with by having a "private use"
address space available?  After reading the discussion on site-local
addresses, I think that unicast address scopes may be un-necessary.  If
I happen to be mis-understanding something, I welcome any explanations
or pointers to previous discussions.




From owner-ietf@ietf.org  Sat Apr 26 14:44:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25454;
	Sat, 26 Apr 2003 14:43:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 199TCj-0000C6-00
	for ietf-list@ran.ietf.org; Sat, 26 Apr 2003 13:11:13 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 199TA1-00006O-00
	for ietf@ran.ietf.org; Sat, 26 Apr 2003 13:08:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23270
	for <ietf@ietf.org>; Sat, 26 Apr 2003 13:00:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199T4G-0000Pu-00
	for ietf@ietf.org; Sat, 26 Apr 2003 13:02:28 -0400
Received: from gull.mail.pas.earthlink.net ([207.217.120.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 199T4G-0000Pr-00
	for ietf@ietf.org; Sat, 26 Apr 2003 13:02:28 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 199T4g-0001ux-00; Sat, 26 Apr 2003 10:02:54 -0700
Date: Sat, 26 Apr 2003 13:02:11 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Jason Hunt <leth@primus.ca>
Cc: moore@cs.utk.edu, ipng@sunroof.eng.sun.com, ietf@ietf.org,
        alh-ietf@tndh.net
Subject: Re: My thoughts on local-use addresses
Message-Id: <20030426130211.321b0a4d.moore@cs.utk.edu>
In-Reply-To: <20030426164255.GA98043@lethargic.dyndns.org>
References: <20030426060420.GA93218@lethargic.dyndns.org>
	<20030426164255.GA98043@lethargic.dyndns.org>
X-Mailer: Sylpheed version 0.8.11 (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

Jason,

we need to get rid of site-locals.  merely renaming them as private use
addresses wouldn't solve any of their problems.  there's no advantage to
moving to IPv6 if it repeats the RFC 1918 mistake.

Keith

On Sat, 26 Apr 2003 12:42:55 -0400
Jason Hunt <leth@primus.ca> wrote:

> I've done a bit more thinking regarding my previous post.  I am going to
> restate the things that I suggested, in case my previous message left
> anything un-clear.
> 
> I would like to suggest that:
> 
> - The idea of scopes be removed from unicast addresses.  Why add the
>   complexity of scopes?  Is it not better to keep things simple?
> 
> - The link-local address space (FE80::/10), or some other space, be
>   available as "private use" address space, similar to what RFC 1918 is
>   to IPv4.  I realize that the current definition of the local-use
>   addresses already provides this, but since I am suggesting to change
>   that definition it seemed necessary to make this point.
> 
> - All interfaces be required to have at least one unicast address
>   assigned to them, instead of being required to have a link-local
>   address in addition to any other addresses.  If an interface is not
>   configured with an address, and the host is unable to obtain an
>   address from a DHCP server (or some other dynamic configuration
>   protocol) for that interface, then the interface will be auto-
>   configured with an address from the above-mentioned "private use"
>   space (FE80::/10 or otherwise).  
> 
> Can anyone point out any practical scenarios for scoped addresses to
> be required, which could not be dealt with by having a "private use"
> address space available?  After reading the discussion on site-local
> addresses, I think that unicast address scopes may be un-necessary.  If
> I happen to be mis-understanding something, I welcome any explanations
> or pointers to previous discussions.
> 



From owner-ietf@ietf.org  Tue Apr 29 09:22:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15965;
	Tue, 29 Apr 2003 09:22:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 199TyC-0001VF-00
	for ietf-list@ran.ietf.org; Sat, 26 Apr 2003 14:00:16 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 199Tvo-0001QT-00
	for ietf@ran.ietf.org; Sat, 26 Apr 2003 13:57:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24262
	for <ietf@ietf.org>; Sat, 26 Apr 2003 13:51:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199Trj-0000by-00
	for ietf@ietf.org; Sat, 26 Apr 2003 13:53:35 -0400
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 199Trj-0000bv-00
	for ietf@ietf.org; Sat, 26 Apr 2003 13:53:35 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by avocet.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 199Ts7-00021l-00; Sat, 26 Apr 2003 10:53:59 -0700
Date: Sat, 26 Apr 2003 13:53:16 -0400
From: Keith Moore <moore@cs.utk.edu>
To: james woodyatt <jhw@wetware.com>
Cc: moore@cs.utk.edu, alh-ietf@tndh.net, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A follow up question
Message-Id: <20030426135316.14b14fe7.moore@cs.utk.edu>
In-Reply-To: <FFE2EEA0-7794-11D7-A7C3-000393BA7EBA@wetware.com>
References: <042901c30a9b$757ed1c0$261e4104@eagleswings>
	<FFE2EEA0-7794-11D7-A7C3-000393BA7EBA@wetware.com>
X-Mailer: Sylpheed version 0.8.11 (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

> Applications have bad habits.
> 
> They cache network addresses when they should be caching names.  

nice theory.  the fact is that names are imprecise; they're not always
bound to what we think they're bound to, there's no way to tell what
they're bound to, and the bindings are subject to change.  and DNS
in particular can be slow and unreliable.  

in short- you can lose by storing names in your application just as
easily as you can lose by storing IP addresses in your application.
anytime you do either one, you're making assumptions about the bindings
of those names or addresses with hosts that are subject to change,
often by factors outside your control.

Keith



From owner-ietf@ietf.org  Tue Apr 29 09:22:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15977;
	Tue, 29 Apr 2003 09:22:17 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 199Tcv-0000vr-00
	for ietf-list@ran.ietf.org; Sat, 26 Apr 2003 13:38:17 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 199Tb3-0000sW-00
	for ietf@ran.ietf.org; Sat, 26 Apr 2003 13:36:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23863
	for <ietf@ietf.org>; Sat, 26 Apr 2003 13:28:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199TW0-0000XZ-00
	for ietf@ietf.org; Sat, 26 Apr 2003 13:31:08 -0400
Received: from dialin-160-56.tor.primus.ca ([216.254.160.56] helo=lethargic.dyndns.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 199TVz-0000XU-00
	for ietf@ietf.org; Sat, 26 Apr 2003 13:31:07 -0400
Received: from lethargic.dyndns.org (localhost [127.0.0.1])
	by lethargic.dyndns.org (8.12.9/8.12.9) with ESMTP id h3QHVTlF098348;
	Sat, 26 Apr 2003 13:31:30 -0400 (EDT)
	(envelope-from leth@lethargic.dyndns.org)
Received: (from leth@localhost)
	by lethargic.dyndns.org (8.12.9/8.12.9/Submit) id h3QHVSID098347;
	Sat, 26 Apr 2003 13:31:28 -0400 (EDT)
Date: Sat, 26 Apr 2003 13:31:27 -0400
From: Jason Hunt <leth@primus.ca>
To: Keith Moore <moore@cs.utk.edu>
Cc: ipng@sunroof.eng.sun.com, ietf@ietf.org, alh-ietf@tndh.net
Subject: Re: My thoughts on local-use addresses
Message-ID: <20030426173127.GA98293@lethargic.dyndns.org>
References: <20030426060420.GA93218@lethargic.dyndns.org> <20030426164255.GA98043@lethargic.dyndns.org> <20030426130211.321b0a4d.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030426130211.321b0a4d.moore@cs.utk.edu>
User-Agent: Mutt/1.4.1i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, Apr 26, 2003 at 01:02:11PM -0400, Keith Moore wrote:
> we need to get rid of site-locals.  merely renaming them as private use
> addresses wouldn't solve any of their problems.  there's no advantage to
> moving to IPv6 if it repeats the RFC 1918 mistake.

What is wrong with having addresses available for private use on
networks that do not intend on being connected to the Internet?  I
suppose that if they are not going to be connected to the Internet, then
really they could just use whatever space they feel like, since it
should not affect any one else unless they do go to connect with other
sites.

Keith, do you have a draft or something you have been working on?  For
the most part I think that I do agree with your arguments against
site-local addresses.  What are your thoughts about link-local
addresses?  Do you want to get rid of all the local-use address space,
which I suppose really means abandoning the idea of scoped addresses all
together?




From owner-ietf@ietf.org  Tue Apr 29 09:22:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16010;
	Tue, 29 Apr 2003 09:22:19 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 199Tpm-0001B5-00
	for ietf-list@ran.ietf.org; Sat, 26 Apr 2003 13:51:34 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 199TfG-0000yd-00
	for ietf@ran.ietf.org; Sat, 26 Apr 2003 13:40:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23934
	for <ietf@ietf.org>; Sat, 26 Apr 2003 13:33:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199TaW-0000YE-00
	for ietf@ietf.org; Sat, 26 Apr 2003 13:35:48 -0400
Received: from hawk.mail.pas.earthlink.net ([207.217.120.22])
	by ietf-mx with esmtp (Exim 4.12)
	id 199TaV-0000YB-00
	for ietf@ietf.org; Sat, 26 Apr 2003 13:35:47 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by hawk.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 199Tav-00065R-00; Sat, 26 Apr 2003 10:36:13 -0700
Date: Sat, 26 Apr 2003 13:35:30 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Jason Hunt <leth@primus.ca>
Cc: moore@cs.utk.edu, ipng@sunroof.eng.sun.com, ietf@ietf.org,
        alh-ietf@tndh.net
Subject: Re: My thoughts on local-use addresses
Message-Id: <20030426133530.3e02b3ce.moore@cs.utk.edu>
In-Reply-To: <20030426173127.GA98293@lethargic.dyndns.org>
References: <20030426060420.GA93218@lethargic.dyndns.org>
	<20030426164255.GA98043@lethargic.dyndns.org>
	<20030426130211.321b0a4d.moore@cs.utk.edu>
	<20030426173127.GA98293@lethargic.dyndns.org>
X-Mailer: Sylpheed version 0.8.11 (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

On Sat, 26 Apr 2003 13:31:27 -0400
Jason Hunt <leth@primus.ca> wrote:

> On Sat, Apr 26, 2003 at 01:02:11PM -0400, Keith Moore wrote:
> > we need to get rid of site-locals.  merely renaming them as private use
> > addresses wouldn't solve any of their problems.  there's no advantage to
> > moving to IPv6 if it repeats the RFC 1918 mistake.
> 
> What is wrong with having addresses available for private use on
> networks that do not intend on being connected to the Internet? 

in principle, nothing.  but experience has shown that most of those networks
do end up being connected to the Internet, while still keeping those addreses,
and that applications are expected to cope with that.

>  What are your thoughts about link-local addresses? 

v6 link-locals are mostly harmless as long as they're only used for 
router discovery and similar things.  applications should not use them.

v4 link-locals have been touted as suitable for general-purpose use, and 
that's just wrong.



From owner-ietf@ietf.org  Tue Apr 29 09:24:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16435;
	Tue, 29 Apr 2003 09:24:41 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUxn-0003tF-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:16:03 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUV2-0002yF-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:46:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06734
	for <ietf@ietf.org>; Mon, 28 Apr 2003 12:52:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ABuL-0003tX-00
	for ietf@ietf.org; Mon, 28 Apr 2003 12:55:13 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ABuK-0003tT-00
	for ietf@ietf.org; Mon, 28 Apr 2003 12:55:12 -0400
Received: from edison.cisco.com (edison.cisco.com [171.70.144.164])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h3SGt4lY016895;
	Mon, 28 Apr 2003 12:55:05 -0400 (EDT)
Received: from cisco.com (sjc-vpn3-326.cisco.com [10.21.65.70]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id JAA09227; Mon, 28 Apr 2003 09:55:03 -0700 (PDT)
Message-ID: <3EAD5CE6.2050702@cisco.com>
Date: Mon, 28 Apr 2003 09:55:02 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stephen Sprunk <stephen@sprunk.org>
CC: Robert Elz <kre@munnari.OZ.AU>, Margaret Wasserman <mrw@windriver.com>,
        Valdis.Kletnieks@vt.edu, Dave Crocker <dcrocker@brandenburg.com>,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question
References: <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU> <5.1.0.14.2.20030428053937.047cbc68@mail.windriver.com> <00b401c30da4$390d81d0$93b58742@ssprunk>
In-Reply-To: <00b401c30da4$390d81d0$93b58742@ssprunk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Stephen Sprunk wrote:

> When you are talking about tens of millions of customers, it's not feasible
> to give each a subnet even if you have the space to do it.  IMHO, most
> customers will be placed on a /64 that's shared across hundreds of
> customers, similar to IPv4 common practice.

Why?

Eliot




From owner-ietf@ietf.org  Tue Apr 29 09:24:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16464;
	Tue, 29 Apr 2003 09:24:48 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUxo-0003tL-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:16:04 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUV3-0002yF-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:46:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06302
	for <ietf@ietf.org>; Mon, 28 Apr 2003 12:33:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ABbX-0003pF-00
	for ietf@ietf.org; Mon, 28 Apr 2003 12:35:47 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ABbW-0003pC-00
	for ietf@ietf.org; Mon, 28 Apr 2003 12:35:46 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3SGZjL26870;
	Mon, 28 Apr 2003 11:35:45 -0500
Message-ID: <00b401c30da4$390d81d0$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Robert Elz" <kre@munnari.OZ.AU>, "Margaret Wasserman" <mrw@windriver.com>
Cc: <Valdis.Kletnieks@vt.edu>, "Dave Crocker" <dcrocker@brandenburg.com>,
        <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
References: <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU> <5.1.0.14.2.20030428053937.047cbc68@mail.windriver.com>
Subject: Re: A simple question 
Date: Mon, 28 Apr 2003 11:23:25 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Margaret Wasserman" <mrw@windriver.com>
> Of course, this isn't why NAT is most often used...  NAT is most
> often used to extend a single address to cover multiple systems
> in a home or small office environment.  For that environment,
> an IPv6 /48 (without site-locals) would suffice to replace NAT.

When you are talking about tens of millions of customers, it's not feasible
to give each a subnet even if you have the space to do it.  IMHO, most
customers will be placed on a /64 that's shared across hundreds of
customers, similar to IPv4 common practice.

There is nothing to indicate that ISPs are going to change their business
models simply because IPv6 address space is plentiful; they charge extra for
two hosts because it is assumed two hosts consume more bits than one, not
because a second IPv4 address is hard to come by.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Tue Apr 29 09:27:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16879;
	Tue, 29 Apr 2003 09:27:22 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUxp-0003tq-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:16:05 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUV3-0002yW-01
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:46:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06350
	for <ietf@ietf.org>; Mon, 28 Apr 2003 12:38:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ABgh-0003pi-00
	for ietf@ietf.org; Mon, 28 Apr 2003 12:41:07 -0400
Received: from ip25.coe.tnet.co.th ([203.146.155.25] helo=fuchsia.home)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ABge-0003pX-00
	for ietf@ietf.org; Mon, 28 Apr 2003 12:41:05 -0400
Received: from delta.cs.mu.OZ.AU (delta.ex0.home [192.168.192.22]) by fuchsia.home with ESMTP
	id h3SGdffH001007; Mon, 28 Apr 2003 23:39:56 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h3SFbKj09230;
	Mon, 28 Apr 2003 22:37:20 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Margaret Wasserman <mrw@windriver.com>
cc: Valdis.Kletnieks@vt.edu, Dave Crocker <dcrocker@brandenburg.com>,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question 
In-Reply-To: <5.1.0.14.2.20030428053937.047cbc68@mail.windriver.com> 
References: <5.1.0.14.2.20030428053937.047cbc68@mail.windriver.com>  <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 28 Apr 2003 22:37:20 +0700
Message-ID: <9228.1051544240@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Mon, 28 Apr 2003 05:53:20 -0400
    From:        Margaret Wasserman <mrw@windriver.com>
    Message-ID:  <5.1.0.14.2.20030428053937.047cbc68@mail.windriver.com>

  | In particular, you would still need to renumber your local network
  | (the global prefixes) when your provider-allocated global
  | addresses change.

Yes.

  | Having extra addresses available for internal
  | traffic (the site-locals) does not make renumbering the global
  | prefix any easier or less expensive.

No, that's simply wrong.   One of the biggest costs in renumbering
is the disruption it causes.   The actual cost of editing the files,
etc, is trivial by comparison.

If all of the internal operations of an organisation are going to
be disrupted, then the organisation is really going to resist any
renumbering.

But if everything just sails on through, operating as normal, then
adding a prefix, and later deleting an old one, is must less intrusive,
and less costly.

  | Although NAT causes various problems, it does offer a high degree
  | of provider-independence for internal nodes.  You won't get this
  | using provider-allocated global addresses in IPv6, no matter how
  | many other addresses you add to each node.

It would be nice if everyone would stop using "provider" in this context.

What matters here is the use of topology sensitive addresses.   If the
address reflects the topology of the network, then it has to change when
the topology changes.

It happens that in the current network environment, the topology is
controlled by the providers, so we have provider supplied addressing
to correctly reflect the topology.

Getting provider independent addressing is plausible - we just need
to make the network topology (somehow) stop being controlled by the
providers.

Getting addressing that is independent of the topology is a much more
interesting problem.  That one I don't believe we have any way to
accomplish yet, that works with routing.   Until we do, we need
addressing for local use.

  | Of course, this isn't why NAT is most often used...  NAT is most
  | often used to extend a single address to cover multiple systems
  | in a home or small office environment.

I think you're living in a sanitised enviornment.   NAT is used almost
everywhere (perhaps outside the US) - almost everywhere.

  | For that environment,
  | an IPv6 /48 (without site-locals) would suffice to replace NAT.

It might.   I'm not sure it will however.   I don't know that I want
even my home connectivity (connections between controllers and
appliances and such) to be disrupted when I change providers (or
when my provider alters the prefix temporarily allocated to me).

  | I am similarly disturbed that there are people who want to
  | specify site-local addressing because they think it will offer
  | the provider-independence currently offered by NAT.

I have no idea who those people are.   I am surprised that you (seem to)
believe that NAT offers provider independence.   It doesn't.   What it
does is allows the renumbering task to be simplified (quite a lot usually
in that case) - but that's all.   Site locals do the same, they allow the
renumbering task to be simplified, as there's one less thing that needs
to be worried about.

By no means do they solve the entire problem, they're just one nail.
But they (or something essentially equivalent) are required, something
needs to provide the kind of address stability that anyone can now have
in IPv4 using NAT.

We could recommend NAT for IPv6, that would certainly do it, but I hope
we don't, there has to be better ways than that.

If you think you have a better way than site locals, please describe it.

I don't want to know what you think the problems with site locals are,
I know they're not perfect.   I want to know what is the better solution.
Until there is one, site locals need to remain.

kre




From owner-ietf@ietf.org  Tue Apr 29 09:30:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17143;
	Tue, 29 Apr 2003 09:30:50 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUxz-00047C-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:16:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 199Cly-0003Gu-00
	for ietf@ran.ietf.org; Fri, 25 Apr 2003 19:38:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27147
	for <ietf@ietf.org>; Fri, 25 Apr 2003 19:16:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199CT7-0004JL-00
	for ietf@ietf.org; Fri, 25 Apr 2003 19:19:01 -0400
Received: from patan.sun.com ([192.18.98.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 199CT6-0004JI-00
	for ietf@ietf.org; Fri, 25 Apr 2003 19:19:00 -0400
Received: from esunmail ([129.147.58.198])
	by patan.sun.com (8.9.3p2+Sun/8.9.3) with ESMTP id RAA03743
	for <ietf@ietf.org>; Fri, 25 Apr 2003 17:19:30 -0600 (MDT)
Received: from xpa-fe1 ([129.147.58.198]) by edgemail1.Central.Sun.COM
 (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
 with ESMTP id <0HDX006KXA2LXJ@edgemail1.Central.Sun.COM> for ietf@ietf.org;
 Fri, 25 Apr 2003 17:18:22 -0600 (MDT)
Received: from sun.com ([129.146.18.22])
 by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
 with ESMTPSA id <0HDX00181A2JV8@mail.sun.net> for ietf@ietf.org; Fri,
 25 Apr 2003 17:18:21 -0600 (MDT)
Date: Fri, 25 Apr 2003 16:18:19 -0700
From: Alain Durand <Alain.Durand@Sun.COM>
Subject: Re: TCPng/ multiple addresses per node (was Re: A follow up question)_
To: john.loughney@nokia.com
Cc: dcrocker@brandenburg.com, ietf@ietf.org, ipng@sunroof.eng.sun.com,
        john-ietf@jck.com
Message-id: <3EA9C23B.80705@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920
 Netscape/7.0
References: <DADF50F5EC506B41A0F375ABEB320636231889@esebe023.ntc.nokia.com>
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT



john.loughney@nokia.com wrote:

>Hi Alain,
>
>I agree with your intro (which I clipped to save space),
>
Thank you!

> one
>comment that I have is:
>
>  
>
>>There is a proposal to create an API to enable the
>>application creating the socket to specify some of the
>>properties that it desires/requires. This is a step in the right
>>direction, but I'm not convinced this can go far enough.
>>So I fully support this idea of lifting the ban on TCPng
>>(or any transport layer for that matter) to de-couple
>>the abstraction needed by applications to the one required
>>by the network. This is in fact introducing some of the semantic
>>of a session layer between the application and the network.
>>Can this be done at the transport layer in the form of TCPng
>>or does this require and actual additional session layer?
>>I'm not sure at this point in time.
>>    
>>
>
>There already something like this, I'm sure you know - SCTP.
>I'm actually not trying to promote SCTP, but it might be interesting,
>as we have an RFC that does most of the avove, to look at it
>critically & see how it performs.  
>
>SCTP, as a background, uses sets of addresses/ports to identify a
>node. In the usual case, one node will pass all of its addresses(& ports)
>to its peer & the peer returns its addresses (&ports) for SCTP 
>traffic.  The application has the the option to choose the primary
>address to be used.  
>
SCTP does not specify how the 'primary' source & destination are chosen,
nor does it explain how to order those lists once it decides to try 
another pair.

Two possible ways to do that could be:
- use knowledge of the topology, that is pass some of the
   routing information to the end nodes.
- use dynamic measurements.. For example start the connection
   using the initial src & dst, and then send regular probes 
(duplicates?) using
   the other combinations to do measurements and keep statistics.

On top of that you might want to add social/economic information
known by the end points, like this interface is cheap vs expensive
at this particular moment. Similar information for other links
within the network would be valuable but much more difficult
to collect!

Also, there is still a need to enable the application
to specify the desired/required properties of the addresses,
like use temporary vs use stable address, use home address vs
care-of-address,...

SCTP does not do any of that.

    - Alain.






From owner-ietf@ietf.org  Tue Apr 29 09:42:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18149;
	Tue, 29 Apr 2003 09:42:39 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUyG-0004J5-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:16:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUVO-0002yW-02
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:46:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25324
	for <ietf@ietf.org>; Mon, 28 Apr 2003 05:55:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19A5Oa-0001kU-00
	for ietf@ietf.org; Mon, 28 Apr 2003 05:58:00 -0400
Received: from unknown-1-11.windriver.com ([147.11.1.11] helo=mail.wrs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19A5Oa-0001k4-00
	for ietf@ietf.org; Mon, 28 Apr 2003 05:58:00 -0400
Received: from IDLEWYLDE.windriver.com ([147.11.233.9])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id CAA22098;
	Mon, 28 Apr 2003 02:57:15 -0700 (PDT)
Message-Id: <5.1.0.14.2.20030428053937.047cbc68@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 28 Apr 2003 05:53:20 -0400
To: Robert Elz <kre@munnari.OZ.AU>
From: Margaret Wasserman <mrw@windriver.com>
Subject: Re: A simple question 
Cc: Valdis.Kletnieks@vt.edu, Dave Crocker <dcrocker@brandenburg.com>,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
In-Reply-To: <16388.1050790957@munnari.OZ.AU>
References: <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu>
 <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu>
 <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
 <16890640984.20030419070719@brandenburg.com>
 <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com>
 <a05210603bac6d68105ed@[10.0.0.3]>
 <11870.1050777166@munnari.OZ.AU>
 <14570.1050784897@munnari.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk


Hi Robert,

At 05:22 AM 4/20/2003 +0700, Robert Elz wrote:
>But if you assume that there are people (and there most probably are) who
>are so sold on the "benefits" of NAT, that they're going to use NAT no
>matter how much you show them that there is in fact no benefit at all
>(which for a site with an IPv6 global /48, and site locals, is certainly
>true) then why would you care what address they're using behind the NAT?
>That is, whether it is SL, LL, or some random "global" prefix they calculated
>by tossing coins.

Actually, it isn't true that an IPv6 global /48 prefix plus site
locals would provide all of the "benefits" of NAT.

In particular, you would still need to renumber your local network
(the global prefixes) when your provider-allocated global
addresses change.  Having extra addresses available for internal
traffic (the site-locals) does not make renumbering the global
prefix any easier or less expensive.

Although NAT causes various problems, it does offer a high degree
of provider-independence for internal nodes.  You won't get this
using provider-allocated global addresses in IPv6, no matter how
many other addresses you add to each node.

Of course, this isn't why NAT is most often used...  NAT is most
often used to extend a single address to cover multiple systems
in a home or small office environment.  For that environment,
an IPv6 /48 (without site-locals) would suffice to replace NAT.

>I find it almost inconceivable to believe that anyone is deciding the fate
>of SL addressing by reference to NAT - that's simply too ludicrous (and sad)
>to contemplate.

I am similarly disturbed that there are people who want to
specify site-local addressing because they think it will offer
the provider-independence currently offered by NAT.

Margaret






From owner-ietf@ietf.org  Tue Apr 29 09:43:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18234;
	Tue, 29 Apr 2003 09:43:10 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUyU-0004UN-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:16:46 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUVW-0002z2-01
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:46:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09606
	for <ietf@ietf.org>; Mon, 28 Apr 2003 01:39:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19A1OJ-0000Kd-00
	for ietf@ietf.org; Mon, 28 Apr 2003 01:41:27 -0400
Received: from tomts12.bellnexxia.net ([209.226.175.56] helo=tomts12-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19A1OJ-0000Ka-00
	for ietf@ietf.org; Mon, 28 Apr 2003 01:41:27 -0400
Received: from yahoo.com ([65.93.186.164]) by tomts12-srv.bellnexxia.net
          (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP
          id <20030428054200.DZTD24063.tomts12-srv.bellnexxia.net@yahoo.com>;
          Mon, 28 Apr 2003 01:42:00 -0400
Date: Mon, 28 Apr 2003 01:42:01 -0400
Subject: policy domains
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Eliot Lear <lear@cisco.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <3EA85176.5010205@cisco.com>
Message-Id: <224F012B-793C-11D7-A2F1-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Thursday, April 24, 2003, at 05:04  PM, Eliot Lear wrote:

> Nobody ignored anything.  To start with, the application community has 
> had to work around these sorts of problems.  This is why there are SIP 
> proxy gateways, STUN services, and MX gateways.  All of these exist 
> due to connectivity limitations (either intentional or architectural).

It strikes me that most of the symptoms of the problem have the word 
"gateway" in the name.

Talking about policy domains, it seems that there is an implicit 
assumption that they are necessary. And that makes sense from a 
security POV. But policy domains do not /require/ site locals or NAT. 
It's just as easy (with v6...) to get global addresses and not route 
them outside the domain.

Then if you conclude that policy domains are a Good Thing, or at least 
Necessary Evil, then why is there all this talk to design a network 
that can somehow route around them?

My point is that A sends B a third-party address C, and the policy of 
the domain is "you can't route that outside my domain" then it doesn't 
matter whether C is site local, global, uses DNS, or whatever. Policy 
says it still won't route!

simon


--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Tue Apr 29 10:01:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19827;
	Tue, 29 Apr 2003 10:01:03 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUyc-0004Yd-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:16:54 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUVa-0002yW-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:46:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07097
	for <ietf@ietf.org>; Sun, 27 Apr 2003 22:36:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199yXU-0007V9-00
	for ietf@ietf.org; Sun, 27 Apr 2003 22:38:44 -0400
Received: from shell.nominum.com ([128.177.192.160])
	by ietf-mx with esmtp (Exim 4.12)
	id 199yXT-0007V6-00
	for ietf@ietf.org; Sun, 27 Apr 2003 22:38:44 -0400
Received: from nominum.com (shell.nominum.com [128.177.192.160])
	by shell.nominum.com (Postfix) with ESMTP
	id D7601137F09; Sun, 27 Apr 2003 19:38:41 -0700 (PDT)
Date: Sun, 27 Apr 2003 19:38:37 -0700
Subject: Re: A simple question 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Robert Elz <kre@munnari.OZ.AU>, Keith Moore <moore@cs.utk.edu>,
        dcrocker@brandenburg.com, ipng@sunroof.eng.sun.com, ietf@ietf.org
To: Margaret Wasserman <mrw@windriver.com>
From: David Conrad <david.conrad@nominum.com>
In-Reply-To: <5.1.0.14.2.20030427201951.03184c10@mail.windriver.com>
Message-Id: <83D73C86-7922-11D7-A953-000393DB42B2@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Margaret,

On Sunday, April 27, 2003, at 05:21  PM, Margaret Wasserman wrote:
> As John Klensin pointed out on this same list several weeks ago
> (and I'm sure he said it better than I will), the decision to
> use ambiguous local addressing in IPv4 (i.e. RFC 1918 addresses)
> was partially motivated by the desire to conserve IPv4 address
> space.

Yes.  Of course, there were and are other reasons, the most significant 
of which is in conjunction with the use of NAT to provide some level of 
provider independence (both in terms of avoiding the necessity to 
renumber when changing providers as well as not having to "purchase" 
additional IP addresses from the service provider).

>  In IPv6, we don't have an address space shortage, so there
> is no reason to introduce architectural complexity to conserve
> address space.

While it is true that address conservation isn't that significant an 
issue, the whole issue of provider independence (or lack thereof) 
continues to exist.

Continuing to ignore this fundamental requirement on the part of 
enterprise network operators is getting us no where.  It certainly 
isn't getting us to IPv6 deployment.

Rgds,
-drc




From owner-ietf@ietf.org  Tue Apr 29 10:05:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20489;
	Tue, 29 Apr 2003 10:05:14 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUyT-0004TN-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:16:45 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUVV-0002z2-01
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:46:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09312
	for <ietf@ietf.org>; Mon, 28 Apr 2003 01:22:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19A18W-0000Eu-00
	for ietf@ietf.org; Mon, 28 Apr 2003 01:25:08 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 19A18V-0000Er-00
	for ietf@ietf.org; Mon, 28 Apr 2003 01:25:07 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2/8.11.2) id h3S5OqA04605;
	Sun, 27 Apr 2003 22:24:52 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200304280524.h3S5OqA04605@boreas.isi.edu>
Subject: Re: A simple question
In-Reply-To: <5.1.0.14.2.20030427201951.03184c10@mail.windriver.com> from Margaret Wasserman at "Apr 27, 3 08:21:50 pm"
To: mrw@windriver.com (Margaret Wasserman)
Date: Sun, 27 Apr 2003 22:24:52 -0700 (PDT)
Cc: kre@munnari.OZ.AU, moore@cs.utk.edu, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
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

% As John Klensin pointed out on this same list several weeks ago
% (and I'm sure he said it better than I will), the decision to
% use ambiguous local addressing in IPv4 (i.e. RFC 1918 addresses)
% was partially motivated by the desire to conserve IPv4 address
% space.  In IPv6, we don't have an address space shortage, so there
% is no reason to introduce architectural complexity to conserve
% address space.
% 
% Margaret

	"dont' have an address space shortage..." - Margaret 
	-YET-
	IPv4 didn't have one either, in its early days.


--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).



From owner-ietf@ietf.org  Tue Apr 29 10:10:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21346;
	Tue, 29 Apr 2003 10:10:33 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUyl-0004dd-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:17:03 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUVe-0002zD-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:46:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05485
	for <ietf@ietf.org>; Sun, 27 Apr 2003 20:25:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199wUy-000747-00
	for ietf@ietf.org; Sun, 27 Apr 2003 20:28:00 -0400
Received: from unknown-1-11.windriver.com ([147.11.1.11] helo=mail.wrs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 199wUy-00073o-00
	for ietf@ietf.org; Sun, 27 Apr 2003 20:28:00 -0400
Received: from IDLEWYLDE.windriver.com ([147.11.233.12])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id RAA05894;
	Sun, 27 Apr 2003 17:27:12 -0700 (PDT)
Message-Id: <5.1.0.14.2.20030427201951.03184c10@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 27 Apr 2003 20:21:50 -0400
To: Robert Elz <kre@munnari.OZ.AU>
From: Margaret Wasserman <mrw@windriver.com>
Subject: Re: A simple question 
Cc: Keith Moore <moore@cs.utk.edu>, dcrocker@brandenburg.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
In-Reply-To: <14384.1050784134@munnari.OZ.AU>
References: <20030419151329.66daf0de.moore@cs.utk.edu>
 <20030419151329.66daf0de.moore@cs.utk.edu>
 <16890640984.20030419070719@brandenburg.com>
 <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com>
 <a05210603bac6d68105ed@[10.0.0.3]>
 <11870.1050777166@munnari.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk


At 03:28 AM 4/20/2003 +0700, Robert Elz wrote:
>     Date:        Sat, 19 Apr 2003 15:13:29 -0400
>     From:        Keith Moore <moore@cs.utk.edu>
>     Message-ID:  <20030419151329.66daf0de.moore@cs.utk.edu>
>
>   | > No, it isn't.   It is a cleaned up replacement for 1918 addresses.
>   | which by itself is reason enough to kill it.
>
>Nothing of the kind.   1918 addresses were created because there was
>demonstrated demand for stable local use only addressing.   Nothing
>has changed in the Internet to cause that demand to go away.
>
>We either provide a mechanism, or the users provide one of their own.

As John Klensin pointed out on this same list several weeks ago
(and I'm sure he said it better than I will), the decision to
use ambiguous local addressing in IPv4 (i.e. RFC 1918 addresses)
was partially motivated by the desire to conserve IPv4 address
space.  In IPv6, we don't have an address space shortage, so there
is no reason to introduce architectural complexity to conserve
address space.

Margaret






From owner-ietf@ietf.org  Tue Apr 29 10:10:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21344;
	Tue, 29 Apr 2003 10:10:33 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUz6-0004qK-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:17:24 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUVn-0002z2-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:47:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26074
	for <ietf@ietf.org>; Sun, 27 Apr 2003 10:24:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199n77-0005IH-00
	for ietf@ietf.org; Sun, 27 Apr 2003 10:26:45 -0400
Received: from d12lmsgate-3.de.ibm.com ([194.196.100.236])
	by ietf-mx with esmtp (Exim 4.12)
	id 199n76-0005IE-00
	for ietf@ietf.org; Sun, 27 Apr 2003 10:26:44 -0400
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate-3.de.ibm.com (8.12.9/8.12.8) with ESMTP id h3REQeCi046688;
	Sun, 27 Apr 2003 16:26:41 +0200
Received: from etzel.zurich.ibm.com (etzel.zurich.ibm.com [9.4.64.140])
	by d12relay02.de.ibm.com (8.12.8/NCO/VER6.5) with SMTP id h3REQdtl246894;
	Sun, 27 Apr 2003 16:26:40 +0200
Received: from gsine03.us.sine.ibm.com by etzel.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03)
          id AA14756 from <brian@hursley.ibm.com>; Sun, 27 Apr 2003 16:26:22 +0200
Message-Id: <3EABE44D.1966A69A@hursley.ibm.com>
Date: Sun, 27 Apr 2003 16:08:13 +0200
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,fr,de
Mime-Version: 1.0
To: Alain Durand <Alain.Durand@sun.com>
Cc: john.loughney@nokia.com, dcrocker@brandenburg.com, ietf@ietf.org,
        ipng@sunroof.eng.sun.com, john-ietf@jck.com
Subject: Re: TCPng/ multiple addresses per node (was Re: A follow up question)_
References: <DADF50F5EC506B41A0F375ABEB320636231889@esebe023.ntc.nokia.com> <3EA9C23B.80705@sun.com>
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

below...

Alain Durand wrote:
> 
> john.loughney@nokia.com wrote:
> 
> >Hi Alain,
> >
> >I agree with your intro (which I clipped to save space),
> >
> Thank you!
> 
> > one
> >comment that I have is:
> >
> >
> >
> >>There is a proposal to create an API to enable the
> >>application creating the socket to specify some of the
> >>properties that it desires/requires. This is a step in the right
> >>direction, but I'm not convinced this can go far enough.
> >>So I fully support this idea of lifting the ban on TCPng
> >>(or any transport layer for that matter) to de-couple
> >>the abstraction needed by applications to the one required
> >>by the network. This is in fact introducing some of the semantic
> >>of a session layer between the application and the network.
> >>Can this be done at the transport layer in the form of TCPng
> >>or does this require and actual additional session layer?
> >>I'm not sure at this point in time.
> >>
> >>
> >
> >There already something like this, I'm sure you know - SCTP.
> >I'm actually not trying to promote SCTP, but it might be interesting,
> >as we have an RFC that does most of the avove, to look at it
> >critically & see how it performs.
> >
> >SCTP, as a background, uses sets of addresses/ports to identify a
> >node. In the usual case, one node will pass all of its addresses(& ports)
> >to its peer & the peer returns its addresses (&ports) for SCTP
> >traffic.  The application has the the option to choose the primary
> >address to be used.
> >
> SCTP does not specify how the 'primary' source & destination are chosen,
> nor does it explain how to order those lists once it decides to try
> another pair.
> 
> Two possible ways to do that could be:
> - use knowledge of the topology, that is pass some of the
>    routing information to the end nodes.
> - use dynamic measurements.. For example start the connection
>    using the initial src & dst, and then send regular probes
> (duplicates?) using
>    the other combinations to do measurements and keep statistics.
> 
> On top of that you might want to add social/economic information
> known by the end points, like this interface is cheap vs expensive
> at this particular moment. Similar information for other links
> within the network would be valuable but much more difficult
> to collect!
> 
> Also, there is still a need to enable the application
> to specify the desired/required properties of the addresses,
> like use temporary vs use stable address, use home address vs
> care-of-address,...
> 
> SCTP does not do any of that.

SCTP was designed for a specific context, telphony signalling, where
there are many intrinsic constraints and the alternative addresses
will probably be explicitly managed as part of the applications
environment. That's much easier than trying to solve these problems
for the general case. In general, middleware designers simply don't
want to know about such issues, however sophisticated an API they
are offered. Before we go down this path, we would need a deep
analysis jointly with the middleware community, otherwise it will
all be in vain.

    Brian





From owner-ietf@ietf.org  Tue Apr 29 10:10:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21345;
	Tue, 29 Apr 2003 10:10:33 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUyk-0004cu-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:17:02 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUVe-0002z2-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:46:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05487
	for <ietf@ietf.org>; Sun, 27 Apr 2003 20:25:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199wUy-00074A-00
	for ietf@ietf.org; Sun, 27 Apr 2003 20:28:00 -0400
Received: from unknown-1-11.windriver.com ([147.11.1.11] helo=mail.wrs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 199wUy-00073l-00
	for ietf@ietf.org; Sun, 27 Apr 2003 20:28:00 -0400
Received: from IDLEWYLDE.windriver.com ([147.11.233.12])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id RAA05891;
	Sun, 27 Apr 2003 17:27:10 -0700 (PDT)
Message-Id: <5.1.0.14.2.20030427201509.033c6d68@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 27 Apr 2003 20:17:55 -0400
To: Dave Crocker <dcrocker@brandenburg.com>
From: Margaret Wasserman <mrw@windriver.com>
Subject: Re: A simple question
Cc: "Tony Hain" <alh-ietf@tndh.net>, ipng@sunroof.eng.sun.com, ietf@ietf.org
In-Reply-To: <036939506.20030418161216@brandenburg.com>
References: <001a01c305f7$a902cd60$261e4104@eagleswings>
 <001a01c305f7$a902cd60$261e4104@eagleswings>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk


Hi Dave,

At 04:12 PM 4/18/2003 -0700, Dave Crocker wrote:
>please point us to some text that gives a clear and complete discussion
>of the benefits that accrue from this new feature, as well as a fair
>consideration of its difficulties.

I wrote such a document.  It can be found at:

http://www.ietf.org/internet-drafts/draft-wasserman-ipv6-sl-impact-02.txt

This is a personal draft, not a work item of the IPv6 WG.

Margaret






From owner-ietf@ietf.org  Tue Apr 29 10:10:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21417;
	Tue, 29 Apr 2003 10:10:42 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUzN-00051d-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:17:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUVv-0002zD-01
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:47:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21585
	for <ietf@ietf.org>; Sun, 27 Apr 2003 05:51:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199irL-0004IV-00
	for ietf@ietf.org; Sun, 27 Apr 2003 05:54:11 -0400
Received: from panoramix.noc.ams-ix.net ([193.194.136.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 199irL-0004IS-00
	for ietf@ietf.org; Sun, 27 Apr 2003 05:54:11 -0400
Received: from localhost (localhost [127.0.0.1])
	by panoramix.noc.ams-ix.net (Postfix) with ESMTP
	id 0E39791FB; Sun, 27 Apr 2003 11:54:43 +0200 (MEST)
Received: from [192.168.0.248] (plumb.xs4all.nl [213.84.188.208])
	by panoramix.noc.ams-ix.net (Postfix) with ESMTP
	id DC34C91E3; Sun, 27 Apr 2003 11:54:41 +0200 (MEST)
User-Agent: Microsoft-Entourage/10.1.1.2418
Date: Sun, 27 Apr 2003 11:54:39 +0200
Subject: Re: My thoughts on local-use addresses
From: Arien Vijn <arien.vijn@ams-ix.net>
To: Keith Moore <moore@cs.utk.edu>
Cc: ipng <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>, <alh-ietf@tndh.net>
Message-ID: <BAD1757F.35D36%arien.vijn@ams-ix.net>
In-Reply-To: <20030426133530.3e02b3ce.moore@cs.utk.edu>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Virus-Scanned: by AMaViS snapshot-20020300
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 26-04-2003 19:35PM, "Keith Moore" <moore@cs.utk.edu> wrote:

>> What is wrong with having addresses available for private use on
>> networks that do not intend on being connected to the Internet?
> 
> in principle, nothing.  but experience has shown that most of those networks
> do end up being connected to the Internet, while still keeping those addreses,
> and that applications are expected to cope with that.

Ehm... What experience? You are referring to experiences with RFC1918
addresses in the IPv4-world, aren't you? But... Do you or anybody already
have have similar experiences with regards to site-locals?

Indeed, RFC1918 addresses are frequently used behind NAT-boxes. And these
NAT-boxes do create all kinds of troubles. That is the main problem isn't
it? 

For that matter will it be the same with regards to IPv6 site-locals? I
think not. Because the most important reason for NAT is the lack of
available IPv4 address space. I know there are more reasons why people use
NAT. But this is by far the most important one. Because for many many
end-users and small companies, it is very hard, if not impossible or at
least expensive to get more than one IPv4 address.

This is not the case in IPv6. ISPs typically provide their customers with a
/48 of globally unique address space... Well, my home-ISP does. Do you
really think I thought one minute of NATing IPv6?

In other words: NAT makes networking complex, it breaks the end-to-end
model, creates unwanted site-effects and it is not really needed with enough
available address space. Therefore I do not think that site-locals will be
used in the same fashion as RFC1918 addresses are mostly used today.

Having said that, NAT might be a quick and dirty hack to satisfy the needs
for:
  - address stability, due to the lack of easy renumbering;
  - multihoming;
  - (obscurity). 

Especially renumbering-issues might also be a reason for using NAT nowadays.
Just because renumbering is too much pain in IPv4. Somehow addresses have to
be configured at many different places. Implementers might be more
thoughtful with regards to IPv6.

Ironically, multihoming is typically a requirement of non-NAT users
nowadays. They might become the new NAT-adepts if the market comes with
means to do it via NAT and there is no good alternative.

Obscurity (some seem to call it security) is just an implementation matter
as well. Really don't want to discuss this.

In any case, I do not think that deprecating site-locals will take away the
NAT-threat. Neither does it bring us closer to alternatives. At least
site-locals are easily recognisable so coping with becomes a possibility.

Arien





From owner-ietf@ietf.org  Tue Apr 29 10:21:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22718;
	Tue, 29 Apr 2003 10:21:21 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUzj-0005Ct-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:18:03 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUW5-0002yW-01
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:47:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26985
	for <ietf@ietf.org>; Sat, 26 Apr 2003 15:52:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199Vks-0001Ih-00
	for ietf@ietf.org; Sat, 26 Apr 2003 15:54:38 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 199Vks-0001Ie-00
	for ietf@ietf.org; Sat, 26 Apr 2003 15:54:38 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 199VlH-000C67-00; Sat, 26 Apr 2003 14:55:03 -0500
Date: Sat, 26 Apr 2003 15:55:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@cs.utk.edu>
cc: "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: My thoughts on local-use addresses
Message-ID: <13367010.1051372503@p3.JCK.COM>
In-Reply-To: <20030426130211.321b0a4d.moore@cs.utk.edu>
References: <20030426060420.GA93218@lethargic.dyndns.org>
 	<20030426164255.GA98043@lethargic.dyndns.org>
 <20030426130211.321b0a4d.moore@cs.utk.edu>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Saturday, 26 April, 2003 13:02 -0400 Keith Moore 
<moore@cs.utk.edu> wrote:

> we need to get rid of site-locals.  merely renaming them as
> private use addresses wouldn't solve any of their problems.
> there's no advantage to moving to IPv6 if it repeats the RFC
> 1918 mistake.

Keith,

Given the tone of some of the traffic on these subjects in the 
last few weeks, this probably needs to be said in public, and I 
apologize for singling you out because you are certainly not the 
only offender.

Hyperbole does not serve either the community, or one's own 
position, well in this situation or others like it.  Suppose we 
start making a list of problems that IPv6 doesn't solve 
--routing, security, cancer, even NATs -- or just carries 
forward from IPv4.  If we then take that list and use it to 
construct statements of the form of "there's no advantage to 
moving to IPv6 if it doesn't solve X or repeats Y", we would 
really be asking the community to forget the problems IPv6 does 
solve (or at least helps with).

If we were using that approach and logic in the mid-70s, we 
would probably be trying to run the network on NCP --and an 
address space of 254 or so hosts-- today, presumably with either 
the demon grandchildren of NATs or some offspring of a NAT and 
an X.75 gateway.

Specifically...

	* Like you, I'd like to get rid of NATs.   I agree that
	private address spaces tend to encourage NATs, although
	not as much as running out of address space does.   If
	IPv6 is able to reduce the number of NATs by even
	25%-50%, that would, IMO, create a significant advantage
	for moving to IPv6.  Getting rid of all of them would be
	better, of course, but claiming or implying "no
	advantage" if all of them can't be removed is really a
	bit much, don't you think?
	
	* Like it or not, there seems to be a strongly-perceived
	requirement for non-RIR-dependent (neither PI nor PD-but-
	RIR-allocated) addresses.  That requirement is arguably
	legitimate for completely detached networks, even if one
	believes in globally-unique addresses for every network
	or host that is even vaguely connected.  Many years ago,
	I could come to the NIC and say "I need some
	(globally-unique) addresses for a LAN that will never
	be connected to the Internet" and get them.  Today,
	the RIRs have no procedures for dealing with such a
	request, much less making the allocation, in either IPv4
	or IPv6 space.  I would hope that, were someone to
	make it, he or she would get an explanation, rather than
	polite laughter, but the requirement is there.   And it
	seems to me that we either need to figure out how people
	can get addresses for that narrow purpose or reserve
	some "open-season" addresses for them.  That is clearly
	independent of whether it is rational to have SL
	addresses on hosts that might be connected to the public
	network --either through NATs or multiple addresses--
	but it means that having some such addresses around
	doesn't turn IPv6 into "no advantage".
	
	* There has been increasing evidence, as this set of
	discussions have played out, that SL isn't the problem,
	but merely a symptom of a series of issues with scopes
	and/or routing and/or layering and data abstraction.  If
	we figure out how to solve the appropriate set of those
	issues, SL will either go away or not, but it is
	unlikely to be a big issue.  Absent a huge intellectual
	breakthrough (and a model for deploying it easily),
	these look likely to work out as complex tradeoffs in
	which we need to make decisions about optimality, or
	damage-minimization, rather than coming up with a
	perfect solution that meets all needs and creates
	universal pleasure.  Are you going to pick some point in
	that solution space, or the subspace that doesn't happen
	to contain SL, and say "if we don't get to this point,
	IPv6 is worthless"?  I don't think so or, at least, I
	hope not.

So, if possible, let's try to calm it down a bit, stop the 
hyperbole, and get back to thinking and reasoning carefully 
about a complex problem.   Please.

        john




From owner-ietf@ietf.org  Tue Apr 29 10:21:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22729;
	Tue, 29 Apr 2003 10:21:22 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUzY-00057A-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:17:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUW0-0002zD-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:47:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05650
	for <ietf@ietf.org>; Sat, 26 Apr 2003 23:09:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199cZw-0002vH-00
	for ietf@ietf.org; Sat, 26 Apr 2003 23:11:48 -0400
Received: from wetware.wetware.com ([199.108.16.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199cZv-0002vE-00
	for ietf@ietf.org; Sat, 26 Apr 2003 23:11:48 -0400
Received: from wetware.com([208.177.152.16]) (2301 bytes) by wetware.wetware.com
	via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp
	(sender: <jhw@wetware.com>) 
	id <m199cZx-002zTnC@wetware.wetware.com>
	for <ietf@ietf.org>; Sat, 26 Apr 2003 20:11:49 -0700 (PDT)
	(Smail-3.2.0.114 2001-Aug-6 #1 built 2002-Sep-2)
Date: Sat, 26 Apr 2003 20:11:52 -0700
Subject: Re: A follow up question
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: IETF list <ietf@ietf.org>
To: Keith Moore <moore@cs.utk.edu>
From: james woodyatt <jhw@wetware.com>
In-Reply-To: <20030426135316.14b14fe7.moore@cs.utk.edu>
Message-Id: <FE6AFAC7-785D-11D7-BA5E-000393BA7EBA@wetware.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Saturday, Apr 26, 2003, at 10:53 US/Pacific, Keith Moore wrote:
> [I wrote:]
>> Applications have bad habits.
>> They cache network addresses when they should be caching names.
>
> nice theory.  the fact is that names are imprecise; they're not always
> bound to what we think they're bound to, there's no way to tell what
> they're bound to, and the bindings are subject to change.  and DNS
> in particular can be slow and unreliable.

All true.  I think I've miscommunicated.

My observation was about applications that require address stability 
when they really should be using stable names in a naming authority 
they control and doing the extra lumping work of implementing a real 
directory service.  DNS is one way to store a mapping between names and 
network addresses.  There are others available, e.g. SLP, Rendezvous, 
etc.

> in short- you can lose by storing names in your application just as
> easily as you can lose by storing IP addresses in your application.
> anytime you do either one, you're making assumptions about the bindings
> of those names or addresses with hosts that are subject to change,
> often by factors outside your control.

Applications lose.  No big surprise for me.  The problem for which I'm 
trying to help fish out a solution: how to get applications to move to 
IPv6 without giving people reason to think they need site-local 
addresses and IPv6 NAT boxen.

Let me be clear: if I find myself porting all my IPv4 ALG's to work in 
an IPv6 NAT, I will-- without any hesitatation-- go Stark Fleming Mad.  
I may take some of you with me with me.


-- 
j h woodyatt <jhw@wetware.com>
markets are only free to the people who own them.




From owner-ietf@ietf.org  Tue Apr 29 10:21:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22731;
	Tue, 29 Apr 2003 10:21:22 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUzi-0005CX-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:18:02 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUW4-0002zD-03
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:47:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28409
	for <ietf@ietf.org>; Sat, 26 Apr 2003 17:17:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199X57-0001eJ-00
	for ietf@ietf.org; Sat, 26 Apr 2003 17:19:37 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199X56-0001eG-00
	for ietf@ietf.org; Sat, 26 Apr 2003 17:19:36 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id DAD7D1395D; Sat, 26 Apr 2003 21:19:37 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: My thoughts on local-use addresses
References: <20030426130211.321b0a4d.moore@cs.utk.edu>
From: Paul Vixie <vixie@vix.com>
Date: 26 Apr 2003 21:19:37 +0000
In-Reply-To: <20030426130211.321b0a4d.moore@cs.utk.edu>
Message-ID: <g3llxxvtw6.fsf@sa.vix.com>
Lines: 15
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

moore@cs.utk.edu (Keith Moore) writes:

> we need to get rid of site-locals.  merely renaming them as private use
> addresses wouldn't solve any of their problems.

this is debatable.  (i disagree, but the debate remains open.)

> there's no advantage to moving to IPv6 if it repeats the RFC 1918 mistake.

this is not debatable, since it depends on facts not in evidence/consensus.

there are more rfc1918 end hosts than there are non-rfc1918 end hosts, and
the uses being made of rfc1918 aren't limited to "couldn't get enough unique
address space" situations.  calling it a mistake, merely in passing, would
remove you from any debate on the dependent issues.



From owner-ietf@ietf.org  Tue Apr 29 10:46:28 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19828;
	Tue, 29 Apr 2003 10:01:03 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUyN-0004Pe-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:16:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUVT-0002yW-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:46:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22677
	for <ietf@ietf.org>; Mon, 28 Apr 2003 03:09:39 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19A2nq-0000z4-00
	for ietf@ietf.org; Mon, 28 Apr 2003 03:11:54 -0400
Received: from h80ad2536.async.vt.edu ([128.173.37.54] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 19A2np-0000z1-00
	for ietf@ietf.org; Mon, 28 Apr 2003 03:11:53 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h3S7COmf001522;
	Mon, 28 Apr 2003 03:12:24 -0400
Message-Id: <200304280712.h3S7COmf001522@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: alh-ietf@tndh.net
Cc: ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A follow up question 
In-Reply-To: Your message of "Thu, 24 Apr 2003 15:27:09 PDT."
             <044801c30ab0$a5d97680$261e4104@eagleswings> 
References: <044801c30ab0$a5d97680$261e4104@eagleswings>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1414292357P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 28 Apr 2003 03:12:23 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_1414292357P
Content-Type: text/plain; charset=us-ascii

On Thu, 24 Apr 2003 15:27:09 PDT, Tony Hain said:
> Keith Moore wrote:
> > this presupposes that the blob that is passed is precisely 
> > and reliably bound to the specific host or process that the 
> > app wants to refer to, and also that the lookup process that 
> > maps blobs to locators and/or identifiers is sufficiently 
> > fast and robust.  often neither of these conditions holds.
> 
> If the first one doesn't hold, the origin node can't use it so the whole
> app is broken. Speed is an implementation issue, not a spec issue. In

This is going to come as quite the shock to every website that includes
URLs of the form http://www.foo-bar.com/whatever  where foo-bar.com is
resolved with a round-robin DNS.  I'm also surprised that apps using SMTP
are so ready to hand around blobs of the form '<*@AOL.COM>' and *totally* not
caring which server it gets handed to - such broken behavior HAS to be
stamped out IMMEDIATELY. :)

Some quick back-of-envelop calculations indicate that quite likely over
half of all traffic on the Internet, and possibly 75%, are the result of
apps that are "broken" by your definition.

--==_Exmh_1414292357P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+rNRXcC3lWbTT17ARAoz4AJ9LrqlibEaJqkvvbgMx/ZQIsIxoLACfbwUK
53vSZpzD27ZH/kZp4w18kzc=
=lYXe
-----END PGP SIGNATURE-----

--==_Exmh_1414292357P--



From owner-ietf@ietf.org  Tue Apr 29 11:00:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26479;
	Tue, 29 Apr 2003 11:00:38 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AV0k-0005ZX-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:19:06 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUVe-0002zQ-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:46:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05678
	for <ietf@ietf.org>; Sun, 27 Apr 2003 20:35:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199weP-00076S-00
	for ietf@ietf.org; Sun, 27 Apr 2003 20:37:46 -0400
Received: from unknown-1-11.windriver.com ([147.11.1.11] helo=mail.wrs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 199weP-00076O-00
	for ietf@ietf.org; Sun, 27 Apr 2003 20:37:45 -0400
Received: from IDLEWYLDE.windriver.com ([147.11.233.12])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id RAA08509;
	Sun, 27 Apr 2003 17:37:02 -0700 (PDT)
Message-Id: <5.1.0.14.2.20030427202610.03410518@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 27 Apr 2003 20:32:06 -0400
To: Keith Moore <moore@cs.utk.edu>
From: Margaret Wasserman <mrw@windriver.com>
Subject: Re: A simple question
Cc: Daniel Senie <dts@senie.com>, moore@cs.utk.edu, stephen@sprunk.org,
        ietf@ietf.org, ipng@sunroof.eng.sun.com
In-Reply-To: <20030419191507.75dfcc39.moore@cs.utk.edu>
References: <5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
 <20030419151329.66daf0de.moore@cs.utk.edu>
 <16890640984.20030419070719@brandenburg.com>
 <002401c30605$e22da070$261e4104@eagleswings>
 <9540645034.20030418171403@brandenburg.com>
 <a05210603bac6d68105ed@[10.0.0.3]>
 <11870.1050777166@munnari.OZ.AU>
 <14384.1050784134@munnari.OZ.AU>
 <20030419165921.782a8353.moore@cs.utk.edu>
 <5.2.1.1.2.20030419181122.0290c090@mail.amaranth.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 07:15 PM 4/19/2003 -0400, Keith Moore wrote:
>it is indeed unfortunate that it took several years before there was serious
>consideration to the impact of site-local on networks, DNS, and applications.
>I view this as an indication of serious failures in our process - IPv6 was
>approved (under pressure, it must be said) by the working group and IESG
>despite serious technical omissions.  fortunately proposed standards are not
>carved in stone, and these particular omissions are easy to fix.

There is currently no RFC that defines the usage model for IPv6
site-local addressing.  The prefix is defined in the addressing
architecture RFC (currently at PS), but the usage model is defined
in the scoped addressing architecture (a WG I-D).

This I-D has been relatively stable for a couple of years, but has
not gone to the IESG, mostly due to IPv6 WG deadlock over the
architectural issues regarding site-local addressing.  During that
time, we have been slowly working through the various architectural
issues caused by site-local addressing, and building WG
consensus regarding what to do about it.

So, I think that this is actually a case of the WG process working
properly (if a bit too slowly).

Margaret






From owner-ietf@ietf.org  Tue Apr 29 11:10:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22743;
	Tue, 29 Apr 2003 10:21:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AUzW-00056F-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 09:17:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUVz-0002yW-03
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:47:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05701
	for <ietf@ietf.org>; Sat, 26 Apr 2003 23:13:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199cdu-0002wO-00
	for ietf@ietf.org; Sat, 26 Apr 2003 23:15:54 -0400
Received: from wetware.wetware.com ([199.108.16.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 199cdu-0002w7-00
	for ietf@ietf.org; Sat, 26 Apr 2003 23:15:54 -0400
Received: from wetware.com([208.177.152.16]) (1041 bytes) by wetware.wetware.com
	via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp
	(sender: <jhw@wetware.com>) 
	id <m199cdw-002zTnC@wetware.wetware.com>
	for <ietf@ietf.org>; Sat, 26 Apr 2003 20:15:56 -0700 (PDT)
	(Smail-3.2.0.114 2001-Aug-6 #1 built 2002-Sep-2)
Date: Sat, 26 Apr 2003 20:15:59 -0700
Subject: Re: A follow up question
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: james woodyatt <jhw@wetware.com>
To: IETF list <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <FE6AFAC7-785D-11D7-BA5E-000393BA7EBA@wetware.com>
Message-Id: <91D78A6E-785E-11D7-BA5E-000393BA7EBA@wetware.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Saturday, Apr 26, 2003, at 20:11 US/Pacific, james woodyatt wrote:
>
> [...] Let me be clear: if I find myself porting all my IPv4 ALG's to 
> work in an IPv6 NAT, I will-- without any hesitatation-- go Stark 
> Fleming Mad.  I may take some of you with me with me.

Apologies for the typographical errors.  And I should have written 
"Flaming" not "Fleming"-- that was an unintentional slip on my part.  
Please forgive me.


-- 
j h woodyatt <jhw@wetware.com>




From owner-ietf@ietf.org  Tue Apr 29 11:19:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27243;
	Tue, 29 Apr 2003 11:19:06 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AWf0-0002Mb-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 11:04:46 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AUUZ-0002yF-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 08:45:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14991
	for <ietf@ietf.org>; Mon, 28 Apr 2003 17:28:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AGDS-0005XJ-00
	for ietf@ietf.org; Mon, 28 Apr 2003 17:31:14 -0400
Received: from main.gmane.org ([80.91.224.249])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AGDR-0005XG-00
	for ietf@ietf.org; Mon, 28 Apr 2003 17:31:14 -0400
Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 19AGCY-0004rX-00
	for <ietf@ietf.org>; Mon, 28 Apr 2003 23:30:18 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 19AF0N-0007ZI-00
	for <gmane-ietf-general@m.gmane.org>; Mon, 28 Apr 2003 22:13:39 +0200
From: MC <mc@hack.org>
Subject: Re: Internet Draft Guidelines Require Precise Formatting?
Date: Mon, 28 Apr 2003 22:14:46 +0200
Organization: Temple of the Moby Hack
Lines: 19
Message-ID: <87d6j69y6h.fsf@fuckup.hack.org>
References: <3E9F9D22.6010.3B5E3E1@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@main.gmane.org
X-URL: http://hack.org/~mc/
X-Waved: Chicken (dead). Curse all those damn UCE bots!
User-Agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.3
Cancel-Lock: sha1:bh7yNvTj1Pm3R0Ty6BITkE+T8O8=
Sender: owner-ietf@ietf.org
Precedence: bulk

"Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com> writes:

> B) I am totally blind, so the process of formatting the document - 
> especially in plain text - is going to prove very difficult.  Are there 
> other provisions that I might take advantage of that would solve this 
> problem?

What platform are you using? Since it seems possible for you to write
text messages, can't you just insert the usual nroff macros to
generate the ID?

See /Instructions to RFC Authors/, RFC 2223, which includes an nroff
template and a small Perl script.

There are also a few hints here:

  http://www.rfc-editor.org/formatting.html

which is easily viewable with a text only browser.






From owner-ietf@ietf.org  Tue Apr 29 11:46:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28215;
	Tue, 29 Apr 2003 11:46:45 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AWmg-0002eQ-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 11:12:42 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AW3M-0001Yn-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 10:25:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22981
	for <ietf@ietf.org>; Tue, 29 Apr 2003 10:22:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AW2e-0004Ao-00
	for ietf@ietf.org; Tue, 29 Apr 2003 10:25:08 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19AW2d-00048A-00
	for ietf@ietf.org; Tue, 29 Apr 2003 10:25:07 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003042910300813547
 ; Tue, 29 Apr 2003 10:30:08 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 29 Apr 2003 10:22:54 -0400
Message-ID: <3EAE8ABE.4010105@centive.com>
Date: Tue, 29 Apr 2003 10:22:54 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
CC: ipng <ipng@sunroof.eng.sun.com>
Subject: Re: My thoughts on local-use addresses
References: <BAD1757F.35D36%arien.vijn@ams-ix.net>
In-Reply-To: <BAD1757F.35D36%arien.vijn@ams-ix.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Apr 2003 14:22:54.0103 (UTC) FILETIME=[D2AEEA70:01C30E5A]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Arien Vijn wrote:

>On 26-04-2003 19:35PM, "Keith Moore" <moore@cs.utk.edu> wrote:
>  
>
>>>What is wrong with having addresses available for private use on
>>>networks that do not intend on being connected to the Internet?
>>>      
>>>
>>in principle, nothing.  but experience has shown that most of those networks
>>do end up being connected to the Internet, while still keeping those addreses,
>>and that applications are expected to cope with that.
>>    
>>
>Ehm... What experience? You are referring to experiences with RFC1918
>addresses in the IPv4-world, aren't you?
>
I think Keith is most likely referring to the experience from before 
RFC1597, when isolated networks would use random addresses, and then run 
into trouble when they wanted to connect.  Even if the networks were 
NATted, the users would suffer because they would never be able to 
communicate with the legitimate holders of the addresses.

-- 
/=================================================================\
|John Stracke      |jstracke@centive.com                          |
|Principal Engineer|http://www.centive.com                        |
|Centive           |My opinions are my own.                       |
|=================================================================|
|Vote for Ron, and nobody gets hurt! --actual campaign poster from|
|Chicago                                                          |
\=================================================================/





From owner-ietf@ietf.org  Tue Apr 29 12:23:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29757;
	Tue, 29 Apr 2003 12:23:31 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AXMx-0003xj-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 11:50:11 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AWuO-00031E-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 11:20:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27232
	for <ietf@ietf.org>; Tue, 29 Apr 2003 11:17:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AWtf-0005F8-00
	for ietf@ietf.org; Tue, 29 Apr 2003 11:19:55 -0400
Received: from gungnir.fnal.gov ([131.225.80.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AWte-0005F4-00
	for ietf@ietf.org; Tue, 29 Apr 2003 11:19:54 -0400
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.12.8/8.12.8) with ESMTP id h3TFKT2Y013209;
	Tue, 29 Apr 2003 10:20:30 -0500 (CDT)
Message-Id: <200304291520.h3TFKT2Y013209@gungnir.fnal.gov>
To: Stephen Sprunk <stephen@sprunk.org>
Cc: ipng@sunroof.eng.sun.com, ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: A simple question 
In-reply-to: Your message of Mon, 28 Apr 2003 11:23:25 CDT.
             <00b401c30da4$390d81d0$93b58742@ssprunk> 
Date: Tue, 29 Apr 2003 10:20:29 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

> When you are talking about tens of millions of customers, it's not feasible
> to give each a subnet even if you have the space to do it.

Why on earth not?  You give them one "thing" either way.  Same
overhead to issue, same overhead to route.

> There is nothing to indicate that ISPs are going to change their business
> models simply because IPv6 address space is plentiful; they charge extra for
> two hosts because it is assumed two hosts consume more bits than one, not
> because a second IPv4 address is hard to come by.

This is not the least bit believable.



From owner-ietf@ietf.org  Tue Apr 29 12:45:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00594;
	Tue, 29 Apr 2003 12:45:54 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AXzt-0005MD-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 12:30:25 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AXeQ-0004od-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 12:08:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29025
	for <ietf@ietf.org>; Tue, 29 Apr 2003 12:05:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AXdh-0005he-00
	for ietf@ietf.org; Tue, 29 Apr 2003 12:07:29 -0400
Received: from garlic.amaranth.net ([208.254.46.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AXdg-0005hb-00
	for ietf@ietf.org; Tue, 29 Apr 2003 12:07:28 -0400
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226])
	(authenticated (0 bits))
	by garlic.amaranth.net (8.11.7/8.11.7) with ESMTP id h3TG62A10796
	(using TLSv1/SSLv3 with cipher RC4-SHA (128 bits) verified NO);
	Tue, 29 Apr 2003 12:06:03 -0400
Message-Id: <5.2.1.1.2.20030429115950.01af3f30@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Tue, 29 Apr 2003 12:05:18 -0400
To: John Stracke <jstracke@centive.com>, ietf@ietf.org
From: Daniel Senie <dts@senie.com>
Subject: Re: My thoughts on local-use addresses
Cc: ipng <ipng@sunroof.eng.sun.com>
In-Reply-To: <3EAE8ABE.4010105@centive.com>
References: <BAD1757F.35D36%arien.vijn@ams-ix.net>
 <BAD1757F.35D36%arien.vijn@ams-ix.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:22 AM 4/29/2003, John Stracke wrote:
>Arien Vijn wrote:
>
>>On 26-04-2003 19:35PM, "Keith Moore" <moore@cs.utk.edu> wrote:
>>
>>
>>>>What is wrong with having addresses available for private use on
>>>>networks that do not intend on being connected to the Internet?
>>>>
>>>in principle, nothing.  but experience has shown that most of those networks
>>>do end up being connected to the Internet, while still keeping those 
>>>addreses,
>>>and that applications are expected to cope with that.
>>>
>>Ehm... What experience? You are referring to experiences with RFC1918
>>addresses in the IPv4-world, aren't you?
>I think Keith is most likely referring to the experience from before 
>RFC1597, when isolated networks would use random addresses, and then run 
>into trouble when they wanted to connect.  Even if the networks were 
>NATted, the users would suffer because they would never be able to 
>communicate with the legitimate holders of the addresses.

Indeed. Many folks used Sun's address block, since Sun used their own IP 
address space in their documenation for examples. Even worse than randomly 
selecting, this meant many people collided both in the ways we all know 
about when two RFC1918-numbered networks merge and in terms of conflicts if 
trying to connect to the public network.

Many NANOG folks are busy screaming that everyone who's got pre-RIR address 
space that's not publicly routed should be giving it up and using RFC 1918. 
Many IETF folks are similarly trying to eradicate the use of any non-public 
IP address space. Clearly we have a major disconnect between the IETF and 
the operations communities. And while the response to this posting will be 
"IPv6 space is limitless," I would argue that ignores the past, and the 
possibility of a repeat in the future.





From owner-ietf@ietf.org  Tue Apr 29 13:08:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01531;
	Tue, 29 Apr 2003 13:08:29 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AYUE-00062C-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 13:01:46 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AY1f-0005Mi-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 12:32:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00007
	for <ietf@ietf.org>; Tue, 29 Apr 2003 12:29:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AY0v-0005sG-00
	for ietf@ietf.org; Tue, 29 Apr 2003 12:31:29 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AY0u-0005sD-00
	for ietf@ietf.org; Tue, 29 Apr 2003 12:31:29 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19AY1K-0001gw-00; Tue, 29 Apr 2003 11:31:54 -0500
Date: Tue, 29 Apr 2003 12:31:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Bill Manning <bmanning@ISI.EDU>
cc: Margaret Wasserman <mrw@windriver.com>,
        "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: IPv6 address space shortages (was: Re: A simple
 question)
Message-ID: <12729734.1051619514@p3.JCK.COM>
In-Reply-To: <200304280524.h3S5OqA04605@boreas.isi.edu>
References:  <200304280524.h3S5OqA04605@boreas.isi.edu>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Sunday, 27 April, 2003 22:24 -0700 Bill Manning 
<bmanning@ISI.EDU> wrote:

> % As John Klensin pointed out on this same list several weeks
> ago % (and I'm sure he said it better than I will), the
> decision to % use ambiguous local addressing in IPv4 (i.e. RFC
> 1918 addresses) % was partially motivated by the desire to
> conserve IPv4 address % space.  In IPv6, we don't have an
> address space shortage, so there % is no reason to introduce
> architectural complexity to conserve % address space.
> %
> % Margaret
>
> 	"dont' have an address space shortage..." - Margaret
> 	-YET-
> 	IPv4 didn't have one either, in its early days.

Bill, regardless of what other features are there and what other 
justifications might exist, the primary problem and hence design 
goal that brought IPv6 into existence was "not enough address 
space".   If we can (even in our paranoid moments) reasonably 
anticipate running out of space, then it is time to send the 
IPv6 addressing architecture back to the drawing board and 
replace it with something that supports variable or 
extensible-length addresses.   I really can't imagine a rational 
enterprise voluntarily deciding to convert to IPv6 if they are 
told it only has a lifetime of NN years, where NN is less than 
at least a major fraction of a century.

For that purpose, I think "running out of space" can be defined 
as finding ourselves with a need to adopt allocation policies or 
strategies (now or later) that force people into non-unique 
addresses to conserve space.

It seems to me that if you, or anyone else, wants to make the 
case that the IPv6 address space isn't going to be large enough, 
you need to do so explicitly and immediately (five years ago 
would have been better, but maybe we know more now).   While I, 
personally, would have preferred extendable length addresses, it 
feels to me that saying "yet" at this stage in the game is just 
pointless sniping unless you are willing to argue for calling a 
halt at this stage and redesigning.

    regards,
        john




From owner-ietf@ietf.org  Tue Apr 29 13:08:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01565;
	Tue, 29 Apr 2003 13:08:34 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AYDc-0005TE-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 12:44:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AXqF-0004xA-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 12:20:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29545
	for <ietf@ietf.org>; Tue, 29 Apr 2003 12:17:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AXpU-0005nD-00
	for ietf@ietf.org; Tue, 29 Apr 2003 12:19:41 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19AXpT-0005ml-00
	for ietf@ietf.org; Tue, 29 Apr 2003 12:19:40 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003042912243514580
 for <ietf@ietf.org>; Tue, 29 Apr 2003 12:24:35 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 29 Apr 2003 12:17:21 -0400
Message-ID: <3EAEA591.6020004@centive.com>
Date: Tue, 29 Apr 2003 12:17:21 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: My thoughts on local-use addresses
References: <BAD1757F.35D36%arien.vijn@ams-ix.net> <BAD1757F.35D36%arien.vijn@ams-ix.net> <5.2.1.1.2.20030429115950.01af3f30@mail.amaranth.net>
In-Reply-To: <5.2.1.1.2.20030429115950.01af3f30@mail.amaranth.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Apr 2003 16:17:21.0386 (UTC) FILETIME=[CFE724A0:01C30E6A]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Daniel Senie wrote:

> Many NANOG folks are busy screaming that everyone who's got pre-RIR 
> address space that's not publicly routed should be giving it up and 
> using RFC 1918.

Without getting into whether that's a good idea or not:

This sounds like a policy that would fail the "Don't make a rule you 
can't enforce" test.  People who really wanted to retain their address 
space would simply start advertising routes to it, but have the routes 
point to dummy hosts.  (It'd be a simple matter to take an old box you 
were going to throw out and have it run software to respond to pings on 
2^16 addresses.)

-- 
/==========================================\
|John Stracke      |jstracke@centive.com   |
|Principal Engineer|http://www.centive.com |
|Centive           |My opinions are my own.|
|==========================================|
|Belief is not relevant to truth.          |
\==========================================/





From owner-ietf@ietf.org  Tue Apr 29 13:08:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01600;
	Tue, 29 Apr 2003 13:08:39 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AYUF-00062S-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 13:01:47 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AY7u-0005ND-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 12:38:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00225
	for <ietf@ietf.org>; Tue, 29 Apr 2003 12:35:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AY7B-0005uc-00
	for ietf@ietf.org; Tue, 29 Apr 2003 12:37:57 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AY7A-0005uZ-00
	for ietf@ietf.org; Tue, 29 Apr 2003 12:37:56 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.11.3/8.9.3) with ESMTP id h3TGcYE94983
	for <ietf@ietf.org>; Tue, 29 Apr 2003 18:38:34 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Tue, 29 Apr 2003 18:38:33 +0200
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: Re: TCPng/ multiple addresses per node
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <0422BCA0-7A61-11D7-A72E-00039388672E@muada.com>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Alain,

>  In the goold old IPv4 word, locators & identificators are the same 
> thing.
>  This is, as many people pointed out, the root cause for a lot of the
>  hard problems we see today, such as multi-homing & mobility.

>  We have made the problem even harder in IPv6 by adding more sementic
>  to specific addresses:

[...]

>  ...and we made it even more complex now in the early days of 
> coexistence
>  of IPv4 and IPv6,

[...]

>  There is a proposal to create an API to enable the
>  application creating the socket to specify some of the
>  properties that it desires/requires. This is a step in the right
>  direction, but I'm not convinced this can go far enough.
>  So I fully support this idea of lifting the ban on TCPng
>  (or any transport layer for that matter) to de-couple
>  the abstraction needed by applications to the one required
>  by the network. This is in fact introducing some of the semantic
>  of a session layer between the application and the network.
>  Can this be done at the transport layer in the form of TCPng
>  or does this require and actual additional session layer?
>  I'm not sure at this point in time.

The question isn't whether we can, but whether we should. Creating an 
additional layer has the advantage that more transport protocols than 
just TCP can take advantage of it, and it saves us from turning TCP 
upside down.

This new layer would be responsible for discovering and/or negotiating 
the right session parameters such as an identifier that the transport 
protocol knows how to handle and a set of locators. The necessity of 
having a discovery mechanism and very likely also a negotiation 
mechanism make this somewhat complex, but something like this isn't 
without precedent (see IKE).

Extending the architecture in this way allows us to do some very 
interesting things. For one thing, we get to use identifiers that 
aren't routable or not globally routable. This solves the multihoming 
problem and the renumbering problem. It could also make the transition 
between IPv4 and IPv6 easier by allowing v4 identifiers over v6 
transport or the other way around.

It also allows new security paradigms: firewalls and authentication 
servers could play a part in the negotation process so we get to clear 
a path between two endpoints based on actual knowledge about the 
communication that's about to happen rather than guess based on more or 
less accidental properties such as port numbers and IP addresses.

The IPv4 internet and by extension the IPv6 internet are quickly 
becoming a huge pile of assumptions based on assumptions based on hacks 
to avoid breaking assumptions. It would be nice if we could replace 
some of these assumptions with actual per-session facts.




From owner-ietf@ietf.org  Tue Apr 29 13:18:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02192;
	Tue, 29 Apr 2003 13:18:57 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AYaq-0006dF-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 13:08:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AYND-0005v7-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 12:54:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01014
	for <ietf@ietf.org>; Tue, 29 Apr 2003 12:51:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AYMT-000641-00
	for ietf@ietf.org; Tue, 29 Apr 2003 12:53:45 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AYMS-00063l-00
	for ietf@ietf.org; Tue, 29 Apr 2003 12:53:44 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id MAA15599;
	Tue, 29 Apr 2003 12:46:04 -0400
Date: Tue, 29 Apr 2003 12:46:34 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: John Stracke <jstracke@centive.com>
cc: ietf@ietf.org, ipng <ipng@sunroof.eng.sun.com>
Subject: Re: My thoughts on local-use addresses
In-Reply-To: <3EAE8ABE.4010105@centive.com>
Message-ID: <Pine.LNX.4.44.0304291241500.1878-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Even RFC1918 addresses get connected sometimes through corporate mergers.
It would work better if organizations would choose a random set of subnets
from 10/8, so the chance of overlap is minimized. Unfortunately, people
tend to use 10.0.0.1 and up, or 192.168.0.1, etc.  Then they have to
internally renumber to connect these networks internally, or else use
internal NATs. I don't really see this as a problem to be concerned with.
It is unavoidable to some extent and better random subnet selection would
tend to minimize the problem.

		--Dean

On Tue, 29 Apr 2003, John Stracke wrote:

> Arien Vijn wrote:
>
> >On 26-04-2003 19:35PM, "Keith Moore" <moore@cs.utk.edu> wrote:
> >
> >
> >>>What is wrong with having addresses available for private use on
> >>>networks that do not intend on being connected to the Internet?
> >>>
> >>>
> >>in principle, nothing.  but experience has shown that most of those networks
> >>do end up being connected to the Internet, while still keeping those addreses,
> >>and that applications are expected to cope with that.
> >>
> >>
> >Ehm... What experience? You are referring to experiences with RFC1918
> >addresses in the IPv4-world, aren't you?
> >
> I think Keith is most likely referring to the experience from before
> RFC1597, when isolated networks would use random addresses, and then run
> into trouble when they wanted to connect.  Even if the networks were
> NATted, the users would suffer because they would never be able to
> communicate with the legitimate holders of the addresses.
>
> --
> /=================================================================\
> |John Stracke      |jstracke@centive.com                          |
> |Principal Engineer|http://www.centive.com                        |
> |Centive           |My opinions are my own.                       |
> |=================================================================|
> |Vote for Ron, and nobody gets hurt! --actual campaign poster from|
> |Chicago                                                          |
> \=================================================================/
>
>
>
>




From owner-ietf@ietf.org  Tue Apr 29 14:22:02 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04408;
	Tue, 29 Apr 2003 14:22:02 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AZSm-0000bO-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 14:04:20 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AYz6-0000Iq-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 13:33:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02730
	for <ietf@ietf.org>; Tue, 29 Apr 2003 13:30:42 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AYyM-0006Sl-00
	for ietf@ietf.org; Tue, 29 Apr 2003 13:32:54 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AYyM-0006Sh-00
	for ietf@ietf.org; Tue, 29 Apr 2003 13:32:54 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h3THXSFn006587;
	Tue, 29 Apr 2003 13:33:28 -0400
Message-Id: <200304291733.h3THXSFn006587@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Matt Crawford <crawdad@fnal.gov>
Cc: ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A simple question 
In-Reply-To: Your message of "Tue, 29 Apr 2003 10:20:29 CDT."
             <200304291520.h3TFKT2Y013209@gungnir.fnal.gov> 
References: <200304291520.h3TFKT2Y013209@gungnir.fnal.gov>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_278680130P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 29 Apr 2003 13:33:28 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_278680130P
Content-Type: text/plain; charset=us-ascii

On Tue, 29 Apr 2003 10:20:29 CDT, Matt Crawford said:

> > There is nothing to indicate that ISPs are going to change their business
> > models simply because IPv6 address space is plentiful; they charge extra for
> > two hosts because it is assumed two hosts consume more bits than one, not
> > because a second IPv4 address is hard to come by.
> 
> This is not the least bit believable.

It's quite believable, in the context of an industry where some providers
don't want you to use a VPN from your home to your office unless you've bought
the "business class" service for $50/mo more, and others are doing various
bait-and-switch, advertising a fast connection and then capping the actual
throughput because they haven't provisioned sufficient backbone to support
the advertised rate...


--==_Exmh_278680130P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+rrdncC3lWbTT17ARAih1AJ4ptjkHhu5uqA346LFuXB6jJPKcAACffnih
Aaxo8yESkwruFrBr74iz28I=
=ZD9b
-----END PGP SIGNATURE-----

--==_Exmh_278680130P--



From owner-ietf@ietf.org  Tue Apr 29 15:08:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06284;
	Tue, 29 Apr 2003 15:08:08 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Aa7h-0001Qr-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 14:46:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AZqb-0001Az-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 14:28:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04629
	for <ietf@ietf.org>; Tue, 29 Apr 2003 14:25:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AZpq-0006sv-00
	for ietf@ietf.org; Tue, 29 Apr 2003 14:28:10 -0400
Received: from out005pub.verizon.net ([206.46.170.143] helo=out005.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AZpp-0006sl-00
	for ietf@ietf.org; Tue, 29 Apr 2003 14:28:09 -0400
Received: from earthlink.com ([4.65.81.124]) by out005.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030429182816.XZNF25152.out005.verizon.net@earthlink.com>;
          Tue, 29 Apr 2003 13:28:16 -0500
Message-ID: <3EAEC35D.EFA0D754@earthlink.com>
Date: Tue, 29 Apr 2003 11:24:29 -0700
From: Peter Deutsch <pdeutsch@earthlink.com>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Robert Elz <kre@munnari.OZ.AU>
CC: Margaret Wasserman <mrw@windriver.com>, Valdis.Kletnieks@vt.edu,
        Dave Crocker <dcrocker@brandenburg.com>, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: A Good Schism Brightens Anyone's Day (was: A Simple Question)
References: <5.1.0.14.2.20030428053937.047cbc68@mail.windriver.com>  <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU> <9228.1051544240@munnari.OZ.AU>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from [4.65.81.124] at Tue, 29 Apr 2003 13:28:15 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Nothing like a good schism to get the juices flowing, no? As this
ongoing debate continues, I have one question on this whole NAT/Site
Local/"Monophysitism versus Nestorism" thing, then one observation:


First, the question.

I keep seeing offhand remarks about some foobar amount of traffic is
NATed, some mubblefink amount of NAT addressing is done because of
address scarcity, while another babblebrush amount of ISPs will be
allocating IPv6 addresses to individuals out of single /64s, so they
wont even get their own /48s, etc, etc. Can someone please point me to
the real, definitive studies and the concrete data that you're all using
as the basis for this debate? 

Right now, everyone seems to be engaged in a cyclic round of "No It Is!
Yes it Isn't" polemic that boils down to a schism within the IETF
priesthood - some believe in a single, divine Eutychian or Monophysitian
address space, others contemplate a dual, Nestorian system. I'd
personally feel better if I felt the alternative positions were based
upon alternative interpretation of some firm scientific data, but from
what's going by at least on the ietf general list, this comes across as
a clash of belief systems, not a clash of scientific principles.

I personally suspect that the Nestorians are on to something here, but
I'd be happy to study the data and reach an alternative conclusion if I
could have something beside this on-going "Jane, you ignorant slut"
level of debate.

So here are a few things we could ask:

    - So what percentage of machines really are being NATed right now?

    - What percentage of traffic is generated and consumed by NATed
hosts?

    - What's the deployment rate of IPv6 (ie. is it growing fast enough
      to matter to me in five years?)

and so on...


I would like to think some real data might help us a bit here to find
the path out of the woods. All I'm seeing on this list are affirmations
of faith. Please, how about sharing a little more of the hard science
behind your conclusions, folks?



And now, my observation:

Robert Elz wrote:
...
> What matters here is the use of topology sensitive addresses.   If the
> address reflects the topology of the network, then it has to change when
> the topology changes.
> 
> It happens that in the current network environment, the topology is
> controlled by the providers, so we have provider supplied addressing
> to correctly reflect the topology.
> 
> Getting provider independent addressing is plausible - we just need
> to make the network topology (somehow) stop being controlled by the
> providers.
> 
> Getting addressing that is independent of the topology is a much more
> interesting problem.  That one I don't believe we have any way to
> accomplish yet, that works with routing.   Until we do, we need
> addressing for local use.

As I read this my first reaction was "great observation, it's good to
see a new idea enter this debate". Then, a milliblip later my brain
fired a neuron that yelled out "Hey, aren't NATs just a means for users
to provide themselves with a topologically independent addresses to
divorce them from the topologically oriented address space imposed on
them by their ISPs?"

There are lots of good reasons to go for a Monophysitian address space,
so presumably there must be some compelling alternative reasons why
people keep ignoring this principle. It looks like we might want to add
"provides non-topologically structured address space" to the list of
advantages for NATs. Personally, I believe that 142 percent of the
people that install NATs do it for this reason alone!!  ;-)



				- peterd


PDF: Oh, and for those who missed my subtle hidden message, both
Nestorism and Monophysitism are now regarded as heresies by those who
ended up in charge of such things in that other priesthood down the
road...

	
-- 

---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software


  "Next to Nestorianism, Monophysitism produced the greatest schism
   that the Eastern Church had suffered."

        http://www.ewtn.com/library/chistory/eveislam.htm
            http://www.newadvent.org/cathen/05633a.htm

---------------------------------------------------------------------



From owner-ietf@ietf.org  Tue Apr 29 16:18:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09117;
	Tue, 29 Apr 2003 16:18:50 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AbB0-0001kv-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 15:54:06 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AaqG-0001aw-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 15:32:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07731
	for <ietf@ietf.org>; Tue, 29 Apr 2003 15:29:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AapU-0007In-00
	for ietf@ietf.org; Tue, 29 Apr 2003 15:31:52 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AapT-0007IZ-00
	for ietf@ietf.org; Tue, 29 Apr 2003 15:31:51 -0400
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id PAA01860;
	Tue, 29 Apr 2003 15:28:06 -0400
Date: Tue, 29 Apr 2003 15:28:33 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: John C Klensin <john-ietf@jck.com>
cc: Bill Manning <bmanning@ISI.EDU>, Margaret Wasserman <mrw@windriver.com>,
        "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IPv6 address space shortages (was: Re: A simple question)
In-Reply-To: <12729734.1051619514@p3.JCK.COM>
Message-ID: <Pine.LNX.4.44.0304291516510.1878-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

We are still not out of IPv4 address space. I don't know the projections
for address space depletion, but I think the IPv6 problem won't be so much
address space depletion as route space depletion. I think it will be
unwieldy to have a million or 2 million or 10 million distinct routes.
Aggregation won't happen the way things are currently organized.

<soapbox> I think the RIRs (at least for IPv6) need to be organized
differently. In order for address space to be hierachical, for efficient
aggregation and routing, addresses have to be given out locally, like
phone numbers.  Unfortunately, that isn't how ISP's or the address
registries are organized. Fees are strongly biased towards big companies,
yet the small and medium sized companies generate most of the revenue.
It costs way too much money to get IPv6 space for every town to have their
own address space, so that even barn, cow, and coke machine can be
connected to the internet.  Something needs to give.  </soapbox>

		--Dean

On Tue, 29 Apr 2003, John C Klensin wrote:

>
>
> --On Sunday, 27 April, 2003 22:24 -0700 Bill Manning
> <bmanning@ISI.EDU> wrote:
>
> > % As John Klensin pointed out on this same list several weeks
> > ago % (and I'm sure he said it better than I will), the
> > decision to % use ambiguous local addressing in IPv4 (i.e. RFC
> > 1918 addresses) % was partially motivated by the desire to
> > conserve IPv4 address % space.  In IPv6, we don't have an
> > address space shortage, so there % is no reason to introduce
> > architectural complexity to conserve % address space.
> > %
> > % Margaret
> >
> > 	"dont' have an address space shortage..." - Margaret
> > 	-YET-
> > 	IPv4 didn't have one either, in its early days.
>
> Bill, regardless of what other features are there and what other
> justifications might exist, the primary problem and hence design
> goal that brought IPv6 into existence was "not enough address
> space".   If we can (even in our paranoid moments) reasonably
> anticipate running out of space, then it is time to send the
> IPv6 addressing architecture back to the drawing board and
> replace it with something that supports variable or
> extensible-length addresses.   I really can't imagine a rational
> enterprise voluntarily deciding to convert to IPv6 if they are
> told it only has a lifetime of NN years, where NN is less than
> at least a major fraction of a century.
>
> For that purpose, I think "running out of space" can be defined
> as finding ourselves with a need to adopt allocation policies or
> strategies (now or later) that force people into non-unique
> addresses to conserve space.
>
> It seems to me that if you, or anyone else, wants to make the
> case that the IPv6 address space isn't going to be large enough,
> you need to do so explicitly and immediately (five years ago
> would have been better, but maybe we know more now).   While I,
> personally, would have preferred extendable length addresses, it
> feels to me that saying "yet" at this stage in the game is just
> pointless sniping unless you are willing to argue for calling a
> halt at this stage and redesigning.
>
>     regards,
>         john
>
>
>




From owner-ietf@ietf.org  Tue Apr 29 16:18:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09114;
	Tue, 29 Apr 2003 16:18:50 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AbB1-0001lN-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 15:54:07 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Ab0l-0001c6-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 15:43:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07983
	for <ietf@ietf.org>; Tue, 29 Apr 2003 15:40:27 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aazv-0007Lr-00
	for ietf@ietf.org; Tue, 29 Apr 2003 15:42:40 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aazu-0007La-00
	for ietf@ietf.org; Tue, 29 Apr 2003 15:42:38 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h3TJglFn008346;
	Tue, 29 Apr 2003 15:42:47 -0400
Message-Id: <200304291942.h3TJglFn008346@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: ipng@sunroof.eng.sun.com, ietf@ietf.org
Cc: postmaster@endtoend.com, Administrator@endtoend.com
Subject: Re: [MailServer Notification]To recipient: Message matched eManager setting and action was taken.
In-Reply-To: Your message of "Tue, 29 Apr 2003 15:14:12 EDT."
             <00b401c30e83$8461c350$0d60a10a@endtoend.com>
References: <00b401c30e83$8461c350$0d60a10a@endtoend.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_383735348P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 29 Apr 2003 15:42:47 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_383735348P
Content-Type: text/plain; charset=us-ascii

On Tue, 29 Apr 2003 15:14:12 EDT, you said:
> **************** eManager Notification *****************
> 
> The following mail was blocked since it contains sensitive content.
> 
> Source mailbox: Peter Deutsch
> Destination mailbox(es): Robert Elz;Margaret Wasserman; Valdis.Kletnieks@vt.e
du; Dave Crocker; ipng@sunroof.eng.sun.com; ietf@ietf.org
> Rule/Policy: Sexual Discrimination
> Action: Delete

I'd like to thank the clued and competent staff at endtoend.com for sending
this out:

a) doing so with an invalid 'From: administrator' tag, without the required
FQDN that's supposed to be there.

b) Without a References: or In-Reply-To: tag to make it easier to identify
what mail was being referenced.

c) The "prettification" of the 'Destination mailboxes' meant that the only
*repliable* addresses were: Valdis.Kletnieks@vt.edu, ipng@sunroof.eng.sun.com,
and ietf@ietf.org.  Me and two mailing lists.  I'm not even the poster of
the problem message, but I'm going to be getting 3 copies.  Meanwhile, the
source mailbox *WONT* get a notification - unless endtoend.com actually
has a Peter Deutsch there, in which case he is likely going to be VERY
mystified as to why he's being accused of sexual discrimination...

d) spamming multiple recipients, including 2 mailing lists with large numbers
of subscribers, rather than the *source* address only, or the SMTP MAIL FROM:
address only. Of course, replying to the source is a problem (see (c)).

d1) Doing this to the IETF list is definitely a faux pas of major proportions.
Breaking this many Internet standards in one message misdirected to the main
mailing list for the body responsible for said standards is comparable to
showing up for tea with the Queen with toilet paper stuck to your shoe....

To paraphrase the problematic text: "Jane, you ignorant POSTMASTER!"

Argh.  Who wants the soapbox next?

--==_Exmh_383735348P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+rtW2cC3lWbTT17ARAiLtAKC6C9Ku/MH82hc50XK4U+21iCwcUQCgssZK
8sbBk3q7HV98SmdT+cgJ/iA=
=TSpp
-----END PGP SIGNATURE-----

--==_Exmh_383735348P--



From owner-ietf@ietf.org  Tue Apr 29 16:43:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09813;
	Tue, 29 Apr 2003 16:43:00 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AbAx-0001iQ-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 15:54:03 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AafF-0001Xj-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 15:21:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07352
	for <ietf@ietf.org>; Tue, 29 Apr 2003 15:18:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AaeT-0007F5-00
	for ietf@ietf.org; Tue, 29 Apr 2003 15:20:29 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19AaeT-0007F0-00
	for ietf@ietf.org; Tue, 29 Apr 2003 15:20:29 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003042915253308196
 ; Tue, 29 Apr 2003 15:25:33 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 29 Apr 2003 15:18:19 -0400
Message-ID: <3EAECFFB.2030604@centive.com>
Date: Tue, 29 Apr 2003 15:18:19 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
CC: ipng@sunroof.eng.sun.com
Subject: Re: A Good Schism Brightens Anyone's Day
References: <5.1.0.14.2.20030428053937.047cbc68@mail.windriver.com>  <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU> <9228.1051544240@munnari.OZ.AU> <3EAEC35D.EFA0D754@earthlink.com>
In-Reply-To: <3EAEC35D.EFA0D754@earthlink.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Apr 2003 19:18:19.0530 (UTC) FILETIME=[17DC6EA0:01C30E84]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Peter Deutsch wrote:

>So here are a few things we could ask:
>
>    - So what percentage of machines really are being NATed right now?
>
>    - What percentage of traffic is generated and consumed by NATed
>hosts?
>
And, if someone answers, the next question is, how do they know? NATs 
are essentially invisible from the outside.

-- 
/=================================================================\
|John Stracke      |jstracke@centive.com                          |
|Principal Engineer|http://www.centive.com                        |
|Centive           |My opinions are my own.                       |
|=================================================================|
|Vote for Ron, and nobody gets hurt! --actual campaign poster from|
|Chicago                                                          |
\=================================================================/





From owner-ietf@ietf.org  Tue Apr 29 17:23:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11096;
	Tue, 29 Apr 2003 17:23:20 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AcER-0003RL-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 17:01:43 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AbdZ-0002kl-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 16:23:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09334
	for <ietf@ietf.org>; Tue, 29 Apr 2003 16:20:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Abcm-0007fe-00
	for ietf@ietf.org; Tue, 29 Apr 2003 16:22:48 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Abci-0007fJ-00
	for ietf@ietf.org; Tue, 29 Apr 2003 16:22:44 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.11.3/8.9.3) with ESMTP id h3TKNJE95270;
	Tue, 29 Apr 2003 22:23:20 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Tue, 29 Apr 2003 22:23:17 +0200
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ipng@sunroof.eng.sun.com, ietf@ietf.org
To: pdeutsch@earthlink.net
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <3EAEC35D.EFA0D754@earthlink.com>
Message-Id: <69412F1F-7A80-11D7-A72E-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On dinsdag, apr 29, 2003, at 20:24 Europe/Amsterdam, Peter Deutsch 
wrote:

> I personally suspect that the Nestorians are on to something here, but
> I'd be happy to study the data and reach an alternative conclusion if I
> could have something beside this on-going "Jane, you ignorant slut"
> level of debate.

> So here are a few things we could ask:

>     - So what percentage of machines really are being NATed right now?

>     - What percentage of traffic is generated and consumed by NATed 
> hosts?

>     - What's the deployment rate of IPv6 (ie. is it growing fast enough
>       to matter to me in five years?)

How is answering any of these questions going to help us? "Oh, NATed 
traffic is 7% and not 5%! You are right we should have site local 
addresses then!"

The current state of IPv6 deployment has very little bearing on future 
IPv6 deployment. Just look back 20 years in IPv4. I don't think any of 
the problems we have today could have been predicted by looking at the 
network then.

>> Getting provider independent addressing is plausible - we just need
>> to make the network topology (somehow) stop being controlled by the
>> providers.

:-)  And I thought I'd seen it all in multi6.

>> Getting addressing that is independent of the topology is a much more
>> interesting problem.  That one I don't believe we have any way to
>> accomplish yet, that works with routing.   Until we do, we need
>> addressing for local use.

> As I read this my first reaction was "great observation, it's good to
> see a new idea enter this debate". Then, a milliblip later my brain
> fired a neuron that yelled out "Hey, aren't NATs just a means for users
> to provide themselves with a topologically independent addresses to
> divorce them from the topologically oriented address space imposed on
> them by their ISPs?"

No, of course not. That's like saying English is the official language 
of China because when you read about something said in China it is 
translated in English.

The problem with renumbering isn't the address the host thinks it has 
itself, but the address others think it has. We have well-established 
procedures for assigning addresses to hosts. Changing the address a DNS 
name points to is much, much more difficult, and changing references to 
addresses elsewhere, such as in filter configurations, is a nightmare.

> There are lots of good reasons to go for a Monophysitian address space,
> so presumably there must be some compelling alternative reasons why
> people keep ignoring this principle. It looks like we might want to add
> "provides non-topologically structured address space" to the list of
> advantages for NATs. Personally, I believe that 142 percent of the
> people that install NATs do it for this reason alone!!  ;-)

I wouldn't presume to know why people use NAT because I'm not one of 
them. (Beginning to feel like a minority.) But let me make some 
observations:

- If we don't give people any sort of private address space, many will 
just take something and at some point some of this will clash with 
something else.

- If we set aside a small range of addresses for private use, many 
people will use the same addresses so when networks merge there will be 
trouble. In IPv4, this is often solved with NAT. So in IPv6 the same 
will happen OR people will have spend a lot of time and money 
renumbering.

- If we allow people to register non-routable globally unique addresses 
for private use, eventually some of this address space will leak out 
into the global routing table. In IPv4, filtering private address 
ranges and long prefixes is well-established and if and when this 
fails, the consequences are negligible.

So it seems to me that we are trying to make up our mind between a rock 
and a hard place while in fact a third option is almost completely 
painless.

We may also want to contemplate the difficulty of attaching secure 
services to ambiguous address space.




From owner-ietf@ietf.org  Tue Apr 29 17:28:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11442;
	Tue, 29 Apr 2003 17:28:26 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AcET-0003SP-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 17:01:45 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AbgV-0002lM-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 16:26:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09453
	for <ietf@ietf.org>; Tue, 29 Apr 2003 16:23:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Abfj-0007ht-00
	for ietf@ietf.org; Tue, 29 Apr 2003 16:25:51 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Abfi-0007hq-00
	for ietf@ietf.org; Tue, 29 Apr 2003 16:25:50 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19AbgE-0002aQ-00; Tue, 29 Apr 2003 15:26:22 -0500
Date: Tue, 29 Apr 2003 16:26:22 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dean Anderson <dean@av8.com>
cc: "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IPv6 address space shortages (was: Re: A simple
 question)
Message-ID: <26797442.1051633582@p3.JCK.COM>
In-Reply-To: <Pine.LNX.4.44.0304291516510.1878-100000@commander.av8.net>
References:  <Pine.LNX.4.44.0304291516510.1878-100000@commander.av
 8.net>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dean,

Since you have responded to a comment of mine, let me summarize 
my reasoning with regard to the "out of IPv4 address space" 
problem.  Your assumptions, views, definitions, religion, etc., 
may differ.

--On Tuesday, 29 April, 2003 15:28 -0400 Dean Anderson 
<dean@av8.com> wrote:

> We are still not out of IPv4 address space.   I don't know the
> projections for address space depletion,

One view of "address space depletion" is that projections are 
useless in an environment in which (i) the RIRs believe that 
their job is to prevent us from running out of space and (ii) 
they are good at their work.  Those two statements imply that 
policies will adjust as they perceive we are getting closer to 
running out of space and, in turn, two seemingly-contradictory 
statements about the date on which we run out of IPv4 space:

	(1) We will _never_ run out of IPv4 space, but you
	really don't want to be the entity that asks for the
	next-to-last block (or any other block after your local
	RIR starts feeling significant end-game pressure).
	I.e., while we won't run out, getting space with get
	more and more expensive and/or aggravating, going up by
	step functions.
	
	(2) Given that model, it is more appropriate to look at
	the date at which it gets sufficiently difficult to get
	unique, globally-routable space (note that I did not say
	"PI") that people with a legitimate requirement for it
	perceive themselves as being unable to get it, or enough
	of it to meet their requirements.  Even 1918 recognizes
	that there are hosts that should have public addresses.
	To the extent that policies about IPv4 allocations are
	forcing such hosts behind NATs --or substitutes the
	judgment of RIRs or ISPs about what should, and should
	not, be public for that of local network
	managers/designers, or make it economically implausible
	to have public hosts-- then we have already passed that
	date.  And, to oversimplify things somewhat, it is
	accurate to say that we have already run out of space,
	because a rational criterion for "run out of space" is
	that it forces us into architecturally pathological
	behavior.


> but I think the IPv6
> problem won't be so much address space depletion as route
> space depletion. I think it will be unwieldy to have a million
> or 2 million or 10 million distinct routes.

Many of us agree with you, at least within the constraints of 
the current routing regime and models.  But the question, on one 
side, is how to organize IPv6 allocations so that we don't have 
that problem.  One theory is "almost no PI space except in very 
large aggregates, multiple (provider-dependent) addresses per 
host.  As far as I can tell, that is the path we are going down. 
But it involves a number of tradeoffs which have, perhaps, not 
been explored and articulated as well as is desirable.  One of 
them is that the strategy uses up addresses faster than the 
network grows (in host counts), even while it may conserve 
routing space.  If you can anticipate the possibility of an RIR 
eventually telling an ISP "you can't count networks in your 
request for a larger allocation if they already have addresses 
from another provider", then we are in danger of being "out of" 
IPv6 address space coming out of the gate -- and that is one 
example of the motivation behind my challenge to Bill... and 
perhaps even of his "yet" comment which led to my challenge.

> Aggregation won't
> happen the way things are currently organized.

Maybe.  See above.

> <soapbox> I think the RIRs (at least for IPv6) need to be
> organized differently. In order for address space to be
> hierachical, for efficient aggregation and routing, addresses
> have to be given out locally, like phone numbers.
> Unfortunately, that isn't how ISP's or the address registries
> are organized. Fees are strongly biased towards big companies,
> yet the small and medium sized companies generate most of the
> revenue. It costs way too much money to get IPv6 space for
> every town to have their own address space, so that even barn,
> cow, and coke machine can be connected to the internet.
> Something needs to give.  </soapbox>

Your conclusion may be right, but I don't think the reasoning in 
the paragraph above works.   Let me restate it to see if I can 
explain why.

The only way we know for address space to be efficiently 
aggregated and routed is to make it hierarchical, and for that 
hierarchy to reflect routing realities.  Unless we either change 
the business models of the industry, or create the type of 
regulatory regime that characterized the PSTN a few decades ago 
(which may be just one form of changing the business models), 
the hierarchy has to follow provider topologies and 
interconnection structures.

It makes sense for every town to have its own address space only 
if every town has a sufficient number of exchange/ 
interconnection points with other towns, or backbone providers 
of one sort or another to give the town global connectivity. 
But, in the general case, that is going to require a regulatory 
regime -- it isn't obviously in the interest of the ISPs, either 
technologically or economically, to make things work that way.

Of course, "address space per country" and, typically, address 
space per entity within country, is exactly the way address 
allocations work in the PSTN under the E.164 Recommendation/ 
System.  But, if that type of address structure is to be used 
for routing, it depends on a collection of bilateral agreements 
(and exchange points) between countries, plus local and national 
routing regimes that are traditionally highly regulated (today's 
"deregulated" environment depends on the previous regulatory 
structure in a number of important ways), involve specialized 
and sometimes subsidized exchange points, small numbers of 
interexchange carriers relative to the number of exchanges (or 
event "towns"), etc.

I don't think we want to go there, but your opinions may, again, 
differ.

     john




From owner-ietf@ietf.org  Tue Apr 29 17:30:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11662;
	Tue, 29 Apr 2003 17:30:29 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AcEU-0003T0-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 17:01:46 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AbkE-0002py-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 16:30:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09542
	for <ietf@ietf.org>; Tue, 29 Apr 2003 16:27:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AbjS-0007jA-00
	for ietf@ietf.org; Tue, 29 Apr 2003 16:29:42 -0400
Received: from gungnir.fnal.gov ([131.225.80.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AbjR-0007j7-00
	for ietf@ietf.org; Tue, 29 Apr 2003 16:29:41 -0400
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.12.8/8.12.8) with ESMTP id h3TKUI2Y000410;
	Tue, 29 Apr 2003 15:30:18 -0500 (CDT)
Message-Id: <200304292030.h3TKUI2Y000410@gungnir.fnal.gov>
To: Valdis.Kletnieks@vt.edu
Cc: ipng@sunroof.eng.sun.com, ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: A simple question 
In-reply-to: Your message of Tue, 29 Apr 2003 13:33:28 EDT.
             <200304291733.h3THXSFn006587@turing-police.cc.vt.edu> 
Date: Tue, 29 Apr 2003 15:30:18 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

> > > ... they charge extra for two hosts because it is
> > > assumed two hosts consume more bits than one, not because a
> > > second IPv4 address is hard to come by.
> > 
> > This is not the least bit believable.
> 
> It's quite believable, in the context of blah blah blah ...

Nothing you've said establishes any likelihood that the reason for
charging more is the expected consumption of more bits.



From owner-ietf@ietf.org  Tue Apr 29 18:06:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13203;
	Tue, 29 Apr 2003 18:06:48 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Acp9-0004nt-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 17:39:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AcQI-0003Y5-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 17:13:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10746
	for <ietf@ietf.org>; Tue, 29 Apr 2003 17:10:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AcPD-0000DQ-00
	for ietf@ietf.org; Tue, 29 Apr 2003 17:12:51 -0400
Received: from pop018pub.verizon.net ([206.46.170.212] helo=pop018.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AcPC-0000D6-00
	for ietf@ietf.org; Tue, 29 Apr 2003 17:12:50 -0400
Received: from earthlink.com ([4.65.81.124]) by pop018.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030429211242.DWHU17739.pop018.verizon.net@earthlink.com>;
          Tue, 29 Apr 2003 16:12:42 -0500
Message-ID: <3EAEE9EC.8CC49459@earthlink.com>
Date: Tue, 29 Apr 2003 14:09:00 -0700
From: Peter Deutsch <pdeutsch@earthlink.com>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: John Stracke <jstracke@centive.com>
CC: ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: A Good Schism Brightens Anyone's Day
References: <5.1.0.14.2.20030428053937.047cbc68@mail.windriver.com>  <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU> <9228.1051544240@munnari.OZ.AU> <3EAEC35D.EFA0D754@earthlink.com> <3EAECFFB.2030604@centive.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at pop018.verizon.net from [4.65.81.124] at Tue, 29 Apr 2003 16:12:42 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



John Stracke wrote:
> 
> Peter Deutsch wrote:
> 
> >So here are a few things we could ask:
> >
> >    - So what percentage of machines really are being NATed right now?
> >
> >    - What percentage of traffic is generated and consumed by NATed
> >hosts?
> >
> And, if someone answers, the next question is, how do they know? NATs
> are essentially invisible from the outside.

Actually, there are ways Marketing folks determine such things. They
count the total number of NAT boxes sold, compare this to the total
number of other routers sold, they use (sometimes statistically valid)
sampling methods to survey customers on their deployment patterns, etc.
From this they can provide market segment data for the engineers to do
their planning. Oh, and while at Cisco I met marketing folks who appear
to do something with slaughtering chickens and looking at their
entrails, although I never did figure out how that worked... ;-)


			- peterd


-- 

---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software


  "It is inhumane, in my opinion, to force people who have a
   genuine medical need for coffee to wait in line behind people
   who apparently view it as some kind of recreational activity."

                                        -- Dave Barry

---------------------------------------------------------------------



From owner-ietf@ietf.org  Tue Apr 29 18:06:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13236;
	Tue, 29 Apr 2003 18:06:52 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Acp7-0004nM-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 17:39:37 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AcM1-0003Xr-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 17:09:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10639
	for <ietf@ietf.org>; Tue, 29 Apr 2003 17:06:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AcLE-0000Bi-00
	for ietf@ietf.org; Tue, 29 Apr 2003 17:08:44 -0400
Received: from buffoon.automagic.org ([208.185.30.208] ident=qmailr)
	by ietf-mx with smtp (Exim 4.12)
	id 19AcLD-0000Bf-00
	for ietf@ietf.org; Tue, 29 Apr 2003 17:08:43 -0400
Received: (qmail 23763 invoked by uid 0); 29 Apr 2003 21:09:20 -0000
Received: from localhost.automagic.org (HELO isc.org) (root@127.0.0.1)
  by localhost.automagic.org with SMTP; 29 Apr 2003 21:09:20 -0000
Date: Tue, 29 Apr 2003 17:09:19 -0400
Subject: Re: A Good Schism Brightens Anyone's Day
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org, ipng@sunroof.eng.sun.com
To: John Stracke <jstracke@centive.com>
From: Joe Abley <jabley@isc.org>
In-Reply-To: <3EAECFFB.2030604@centive.com>
Message-Id: <D7EA6368-7A86-11D7-A0BA-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Tuesday, Apr 29, 2003, at 15:18 Canada/Eastern, John Stracke wrote:

> Peter Deutsch wrote:
>
>> So here are a few things we could ask:
>>
>>    - So what percentage of machines really are being NATed right now?
>>
>>    - What percentage of traffic is generated and consumed by NATed
>> hosts?
>>
> And, if someone answers, the next question is, how do they know? NATs 
> are essentially invisible from the outside.

They're not quite that invisible. See, for example:

   http://www.research.att.com/~smb/papers/fnat.pdf


Joe




From owner-ietf@ietf.org  Tue Apr 29 18:32:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14880;
	Tue, 29 Apr 2003 18:32:08 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AdDx-0006fI-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 18:05:17 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AcUF-0003bX-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 17:18:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10896
	for <ietf@ietf.org>; Tue, 29 Apr 2003 17:15:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AcTS-0000FW-00
	for ietf@ietf.org; Tue, 29 Apr 2003 17:17:14 -0400
Received: from carwash.centive.com ([65.220.90.249] helo=carwash.centivinc.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19AcTS-0000FN-00
	for ietf@ietf.org; Tue, 29 Apr 2003 17:17:14 -0400
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003042917221806878
 ; Tue, 29 Apr 2003 17:22:18 -0400
Received: from centive.com ([10.10.48.156]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 29 Apr 2003 17:15:04 -0400
Message-ID: <3EAEEB58.9010405@centive.com>
Date: Tue, 29 Apr 2003 17:15:04 -0400
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
CC: ipng@sunroof.eng.sun.com
Subject: Re: A Good Schism Brightens Anyone's Day
References: <5.1.0.14.2.20030428053937.047cbc68@mail.windriver.com>  <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu> <200304191923.h3JJNOuL018209@turing-police.cc.vt.edu> <16890640984.20030419070719@brandenburg.com> <002401c30605$e22da070$261e4104@eagleswings> <9540645034.20030418171403@brandenburg.com> <a05210603bac6d68105ed@[10.0.0.3]> <11870.1050777166@munnari.OZ.AU> <14570.1050784897@munnari.OZ.AU> <9228.1051544240@munnari.OZ.AU> <3EAEC35D.EFA0D754@earthlink.com> <3EAECFFB.2030604@centive.com> <3EAEE9EC.8CC49459@earthlink.com>
In-Reply-To: <3EAEE9EC.8CC49459@earthlink.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Apr 2003 21:15:04.0929 (UTC) FILETIME=[67677D10:01C30E94]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Peter Deutsch wrote:

>Oh, and while at Cisco I met marketing folks who appear
>to do something with slaughtering chickens and looking at their
>entrails, although I never did figure out how that worked... ;-)
>  
>
You have to use a Bayesian chicken.

-- 
/=====================================================\
|John Stracke      |jstracke@centive.com              |
|Principal Engineer|http://www.centive.com            |
|Centive           |My opinions are my own.           |
|=====================================================|
|"The Reality Check's in the mail." --L. Peter Deutsch|
\=====================================================/





From owner-ietf@ietf.org  Tue Apr 29 18:44:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15286;
	Tue, 29 Apr 2003 18:44:57 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AdY4-0003pt-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 18:26:04 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AcvR-0004qm-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 17:46:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12129
	for <ietf@ietf.org>; Tue, 29 Apr 2003 17:43:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Acue-0000Yt-00
	for ietf@ietf.org; Tue, 29 Apr 2003 17:45:20 -0400
Received: from aharp.is-net.depaul.edu ([140.192.91.90])
	by ietf-mx with smtp (Exim 4.12)
	id 19Acud-0000Yj-00
	for ietf@ietf.org; Tue, 29 Apr 2003 17:45:19 -0400
Received: (qmail 4350 invoked from network); 29 Apr 2003 21:45:28 -0000
Received: from aharp.is-net.depaul.edu (HELO cna4-019.cna.depaul.edu) (140.192.91.90)
  by aharp.is-net.depaul.edu with SMTP; 29 Apr 2003 21:45:28 -0000
Date: Tue, 29 Apr 2003 16:45:44 -0500
From: John Kristoff <jtk@depaul.edu>
Cc: ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
Message-Id: <20030429164544.5aee6169.jtk@depaul.edu>
In-Reply-To: <69412F1F-7A80-11D7-A72E-00039388672E@muada.com>
References: <3EAEC35D.EFA0D754@earthlink.com>
	<69412F1F-7A80-11D7-A72E-00039388672E@muada.com>
Reply-To: jtk@aharp.is-net.depaul.edu
X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i686-pc-linux-gnu)
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

On Tue, 29 Apr 2003 22:23:17 +0200
Iljitsch van Beijnum <iljitsch@muada.com> wrote:

> - If we allow people to register non-routable globally unique
> addresses for private use, eventually some of this address space will
> leak out into the global routing table. In IPv4, filtering private
> address ranges and long prefixes is well-established and if and when
> this fails, the consequences are negligible.

This seems OK to me and appears to put the burden in the right place. 
Shouldn't it be the responsibility of those who are allocated address
space to properly manage it?  Others can still filter on long and valid
prefixes that they expect to hear.

...and if its gonna leak anyway, it might as well be globally unique. 
Other networks will certainly be less likely to collide and try to
communicate with the leaked space.

John



From owner-ietf@ietf.org  Tue Apr 29 18:56:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15819;
	Tue, 29 Apr 2003 18:56:41 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AdcO-00040r-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 18:30:32 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AdMl-0002ES-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 18:14:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13890
	for <ietf@ietf.org>; Tue, 29 Apr 2003 18:11:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AdLy-0000qH-00
	for ietf@ietf.org; Tue, 29 Apr 2003 18:13:34 -0400
Received: from thwip.polyamory.org ([192.31.227.220])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AdLx-0000qE-00
	for ietf@ietf.org; Tue, 29 Apr 2003 18:13:33 -0400
Received: by thwip.polyamory.org (Postfix, from userid 1002)
	id E5D3712E47; Tue, 29 Apr 2003 18:14:05 -0400 (EDT)
Date: Tue, 29 Apr 2003 18:14:05 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: ietf@ietf.org
Subject: site-local != NAT
Message-ID: <20030429181405.B6083@thwip.polyamory.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Organization: American Association Against Acronym Abuse
Sender: owner-ietf@ietf.org
Precedence: bulk

Disclaimer: I started out reading the whole thread, but lately I've
had to skim.  I might have missed it if someone already said this.

If people want to use private addresses to avoid having to renumber
when their provider renumbers, and they use addresses their provider
won't route, then they need to NAT those addresses if they want the
hosts using them to be able to talk to the rest of the world.  Fine.

In the old days, we recommended that sites register blocks of
addresses whether they were connecting them to the net or not, if they
ever intended to connect them to the net in the future.  That way,
each address could be globally unique, since they were all going
through a central registry.

For several reasons, we began to have to put more stringent conditions
on granting address blocks out of the pool.  People stopped being able
to just ask for a /24 for their own use, and get it.  Partly this was
because we saw the address space running out if we kept letting anyone
get address space, and partly it was because people expected routing
for the addresses they were granted.

RFC1918 was a solution to the problems in the last paragraph.  The
drawbacks of RFC1918 are obvious.  If an address leaks, it might make
its way to somewhere where it looks locally valid, by coincidence.
And when networks merge, they may have collisions.  We live with it
because we need it.

If the IPv6 address space is big enough, we should be able to revert
to the old ways.  We should be able to make a policy for the RIRs that
allows, once again, for people to ask for unique address space.  Do we
have enough address space that everyone can get a reasonable amount
just by asking for it?  If so, people can NAT their private nets to
their heart's content, without requiring anything like RFC1918 or
site-local.  I've done the same thing with IPv4 with old portable
address blocks.

I think today's implied identity of "private address space" and
"locally scoped addresses" is really muddying the discussion.  If we
have a world where anyone who asks can get a unique address block
assigned to them to use for their private network... THEN what are the
remaining reasons why people would want to use site-local addresses?

  --  Cos (Ofer Inbar)       --   cos@aaaaa.org  http://cos.polyamory.org/
   "OSI is a beautiful dream, and TCP/IP is living it!"
     -- Einar Stefferud <Stef@nma.com>, IETF mailing list, 12 May 1992



From owner-ietf@ietf.org  Tue Apr 29 19:41:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16795;
	Tue, 29 Apr 2003 19:41:43 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AeP5-0005Rg-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 19:20:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AdrV-0004Q7-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 18:46:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15222
	for <ietf@ietf.org>; Tue, 29 Apr 2003 18:43:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Adqh-00016F-00
	for ietf@ietf.org; Tue, 29 Apr 2003 18:45:19 -0400
Received: from out003pub.verizon.net ([206.46.170.103] helo=out003.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Adqg-00015y-00
	for ietf@ietf.org; Tue, 29 Apr 2003 18:45:18 -0400
Received: from earthlink.com ([4.65.81.124]) by out003.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030429224525.DNTN2239.out003.verizon.net@earthlink.com>;
          Tue, 29 Apr 2003 17:45:25 -0500
Message-ID: <3EAEFFA7.63A14F72@earthlink.com>
Date: Tue, 29 Apr 2003 15:41:43 -0700
From: Peter Deutsch <pdeutsch@earthlink.com>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
CC: pdeutsch@earthlink.net, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
References: <69412F1F-7A80-11D7-A72E-00039388672E@muada.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [4.65.81.124] at Tue, 29 Apr 2003 17:45:25 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Iljitsch van Beijnum wrote:

> On dinsdag, apr 29, 2003, at 20:24 Europe/Amsterdam, Peter Deutsch
> wrote:
>> ...
> How is answering any of these questions going to help us? "Oh, NATed
> traffic is 7% and not 5%! You are right we should have site local
> addresses then!"

Well, I've a couple of responses to that.

One, of course is that if NAT traffic is really only 5%, and it happens
to be falling over time, then we should maybe stop spending so much time
arguing about it. :-)

(Note, if I really wanted to be excommunicated from this list, I could
have done a s/NAT/IPv6/ on the above paragraph ;-)


More to the point, folks are throwing around quite a few categoric
statements of fact and I assume they do this to help persuade others to
their point of view.

Here's a quick sampling of statements presented over the past few days
to support the two sides of the debate (Note, Please don't take offense
if you recognize your own words in this list - I'm not criticizing the
authors or disputing the facts, just assuming that the authors are
expecting folks to make decisions based upon these claims, and so was
thinking it could be useful if at least some of these claims could be
substantiated or disproved):

    - "there are more rfc1918 end hosts than there are non-rfc1918
       end hosts, and the uses being made of rfc1918 aren't limited
       to "couldn't get enough unique address space" situations."

     - "NAT is most often used to extend a single address to
        cover multiple systems in a home or small office 
        environment. For that environment, an IPv6 /48 
        (without site-locals) would suffice to replace NAT."

     - "NAT is used almost everywhere (perhaps outside the US)
        - almost everywhere."

     - "When you are talking about tens of millions of customers,
        it's not feasible to give each a subnet even if you have
        the space to do it.  IMHO, most customers will be placed
        on a /64 that's shared across hundreds of customers, similar
        to IPv4 common practice."

     - "While it is true that address conservation isn't that
        significant an issue, the whole issue of provider
        independence (or lack thereof) continues to exist."

     - "One of the biggest costs in renumbering is the 
        disruption it causes. The actual cost of editing
        the files, etc, is trivial by comparison."

     - "Even RFC1918 addresses get connected sometimes through
        corporate mergers. It would work better if organizations
        would choose a random set of subnets from 10/8, so the
        chance of overlap is minimized."

     - "They [ISPs] charge extra for two hosts because it 
        is assumed two hosts consume more bits than one, not
        because a second IPv4 address is hard to come by."

Now, it may be true that *all* of the above statements are true, but
they don't help me because I can't tell, from the statements alone,
which ones are actually *relevant* to the debate. So, just as in your
somewhat offhand use of "7% versus 5%" above, it all seems a little bit
like the statement that "46 percent of all statistics are made up". So,
which is it - seven percent, or over half?? For a bunch of architects,
folks around here don't seem as concerned about the foundations as I'd
have expected... ;-)


> The current state of IPv6 deployment has very little bearing on future
> IPv6 deployment. Just look back 20 years in IPv4. I don't think any of
> the problems we have today could have been predicted by looking at the
> network then.

Well, this is a good example where something may be true, but not
relevant. If, after all this "Sturm und Drang", IPv6 is not yet growing
faster than overall network traffic, those of us who remember X.500 may
conclude that it's not going to be relevant to me within an event
horizon that I need to care about, so I might conclude that I can ignore
it (and by extension, arguments predicated on its success). Now, this
may get me excommunicated from this list, but it may be the right thing
for me to do. How can I tell from this thread? I could be persuaded to
pay attention to such arguments by some numbers.


Another observation, there appears to be at least two major schools of
philosophy at work here (time for another random analogy for you Science
majors to go look up on Google... ;-)

One school appears to be focused on the problems of the locally Self
Sufficient Network User, with his own clsuter of simple machines behind
a NAT box (Sort of a Network Thoreau, in which we are each building our
own local "Walden Puddle". We learn to adapt to scarcity by making
frugality and reuse a virture, etc).  The big issues are whether certain
applications can work behind NATs, will I interfere with others, and so
on. 

The other school appears to be focused on the needs of large corporate
Networks. Here the focus is on renumbering issues, folks assume network
admins are in charge of and care about routing issues, etc. The Super
Administrator is assumed to have more intelligence and Power than the
average user here (Sort of Nietzsche's UberMensch, running his UberNet,
if I may be so bold);


Now, if "there are more rfc1918 end hosts than there are non-rfc1918 end
hosts" and "NAT is most often used to extend a single address to cover
multiple systems in a home or small office" then I might be inclined to
give more weight to arguments which make the network a better place for
the Thoreaus of the world (or is that "Bllom County"?), but if the most
important issues for our future are really going to be about supporting
large campus installations, it might drive the trade-offs in a different
direction. There Are No Free Lunches, so knowing what the target is
might help us all collectively take better aim....



...
> > As I read this my first reaction was "great observation, it's good to
> > see a new idea enter this debate". Then, a milliblip later my brain
> > fired a neuron that yelled out "Hey, aren't NATs just a means for users
> > to provide themselves with a topologically independent addresses to
> > divorce them from the topologically oriented address space imposed on
> > them by their ISPs?"
> 
> No, of course not. That's like saying English is the official language
> of China because when you read about something said in China it is
> translated in English.


But then you state:
...
> I wouldn't presume to know why people use NAT because I'm not one of
> them. (Beginning to feel like a minority.) 

Well, if anyone's going to argue against them, shouldn't they at least
understand why they're being deployed?? ;-)



But let me make some
> observations:
> 
> - If we don't give people any sort of private address space, many will
> just take something and at some point some of this will clash with
> something else.
> 
> - If we set aside a small range of addresses for private use, many
> people will use the same addresses so when networks merge there will be
> trouble. In IPv4, this is often solved with NAT. So in IPv6 the same
> will happen OR people will have spend a lot of time and money
> renumbering.

Again, just to illustrate my thesis, in the above response you seem to
assume:

	- network merging happens often enough that it is a significant
          problem that must be addressed at the architectural level
          (that is, here at the IETF);
	- it costs a lot of time and money to renumber.

If either of these assertions is not true, you have to go back to the
beginning and start again. Ergo, knowing whether such
assumptions/assertions/axioms are true would be useful for those of us
trying to follow along without a program...  QED



				- peterd

-- 

---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software


  "It is inhumane, in my opinion, to force people who have a
   genuine medical need for coffee to wait in line behind people
   who apparently view it as some kind of recreational activity."

                                        -- Dave Barry

---------------------------------------------------------------------



From owner-ietf@ietf.org  Tue Apr 29 19:46:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17062;
	Tue, 29 Apr 2003 19:46:52 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AeQD-0005Zl-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 19:22:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AeHV-0005NF-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 19:13:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16178
	for <ietf@ietf.org>; Tue, 29 Apr 2003 19:09:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AeGh-0001Jl-00
	for ietf@ietf.org; Tue, 29 Apr 2003 19:12:11 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AeGg-0001Ji-00
	for ietf@ietf.org; Tue, 29 Apr 2003 19:12:10 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3TNCiL29975;
	Tue, 29 Apr 2003 18:12:44 -0500
Message-ID: <005f01c30ea4$d74dee60$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Eliot Lear" <lear@cisco.com>, "S Woodside" <sbwoodside@yahoo.com>
Cc: <ietf@ietf.org>, <ipng@sunroof.eng.sun.com>
References: <224F012B-793C-11D7-A2F1-000393414368@yahoo.com>
Subject: Re: policy domains
Date: Tue, 29 Apr 2003 18:09:04 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "S Woodside" <sbwoodside@yahoo.com>
> Then if you conclude that policy domains are a Good Thing, or at least
> Necessary Evil, then why is there all this talk to design a network
> that can somehow route around them?

There's reasonable arguments against private addresses, but unless
allocation policies are radically different than IPv4 practice, expecting a
public address for every host is a pipe dream.

Sidebar: a thread has recently popped up on nanog regarding the practice of
assigning public addresses to unconnected networks or hosts behind
firewalls.  It's not clear whether those for or against are in the majority,
but the mere presence of the debate is rather telling.

> My point is that A sends B a third-party address C, and the policy of
> the domain is "you can't route that outside my domain" then it doesn't
> matter whether C is site local, global, uses DNS, or whatever. Policy
> says it still won't route!

The expected usage model was that all hosts would have a site-local address
as well as zero to many global addresses.  Since we don't yet know how to
handle multiple addresses per host cleanly, the removal of site-locals is
thought to reduce the problem's complexity since site-locals are for some
reason assumed to have different semantics than globals.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Tue Apr 29 19:59:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17391;
	Tue, 29 Apr 2003 19:59:50 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Aevf-0006S4-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 19:54:31 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AeXN-0005an-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 19:29:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16512
	for <ietf@ietf.org>; Tue, 29 Apr 2003 19:26:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AeWZ-0001Pk-00
	for ietf@ietf.org; Tue, 29 Apr 2003 19:28:35 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AeWY-0001Ph-00
	for ietf@ietf.org; Tue, 29 Apr 2003 19:28:34 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3TNT5L30355;
	Tue, 29 Apr 2003 18:29:06 -0500
Message-ID: <006e01c30ea7$2084fea0$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <pdeutsch@earthlink.net>, "Iljitsch van Beijnum" <iljitsch@muada.com>
Cc: <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
References: <69412F1F-7A80-11D7-A72E-00039388672E@muada.com>
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
Date: Tue, 29 Apr 2003 18:21:56 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Iljitsch van Beijnum" <iljitsch@muada.com>
> On dinsdag, apr 29, 2003, at 20:24 Europe/Amsterdam, Peter Deutsch
> wrote:
>
> > - So what percentage of machines really are being NATed right now?
>
> > - What percentage of traffic is generated and consumed by NATed
> > hosts?
>
> How is answering any of these questions going to help us? "Oh, NATed
> traffic is 7% and not 5%! You are right we should have site local
> addresses then!"

But if the number were 50% or higher, I'd think that would have some bearing
on things.  If nothing else, it should convince the anti-NAT crowd to work
harder at finding other solutions.

> - If we allow people to register non-routable globally unique addresses
> for private use, eventually some of this address space will leak out
> into the global routing table. In IPv4, filtering private address
> ranges and long prefixes is well-established and if and when this
> fails, the consequences are negligible.

Without an explicit directive from the IETF (a la RFC2050), the RIRs will
not do this.  In words attributed to an ARIN staffer, "We only register
addresses for the Internet, not private networks."

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Tue Apr 29 20:33:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18355;
	Tue, 29 Apr 2003 20:33:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Af0Z-0006Yk-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 19:59:35 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Aemp-0005vS-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 19:45:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16841
	for <ietf@ietf.org>; Tue, 29 Apr 2003 19:42:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aem1-0001VK-00
	for ietf@ietf.org; Tue, 29 Apr 2003 19:44:33 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aem0-0001VF-00
	for ietf@ietf.org; Tue, 29 Apr 2003 19:44:32 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3TNj4L30666;
	Tue, 29 Apr 2003 18:45:05 -0500
Message-ID: <00a501c30ea9$5c489b70$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <jtk@aharp.is-net.depaul.edu>
Cc: <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
References: <3EAEC35D.EFA0D754@earthlink.com><69412F1F-7A80-11D7-A72E-00039388672E@muada.com> <20030429164544.5aee6169.jtk@depaul.edu>
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
Date: Tue, 29 Apr 2003 18:32:11 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "John Kristoff" <jtk@depaul.edu>
> This seems OK to me and appears to put the burden in the right place.
> Shouldn't it be the responsibility of those who are allocated address
> space to properly manage it?  Others can still filter on long and valid
> prefixes that they expect to hear.

Or, if these non-routed allocations were from a specific IANA-designated
block, providers could simply filter them all with one directive.

> ...and if its gonna leak anyway, it might as well be globally unique.
> Other networks will certainly be less likely to collide and try to
> communicate with the leaked space.

Certainly.  However, providers tend to advertise whatever customers pay them
to advertise, so these "non routable" blocks may end up permanently
reachable from non-trivial portions of the Internet.

There are many applications, such as pre-positioned content caching, where
it's desirable to only have connectivity to those topologically "close".
Overall, though, this makes it even more important that we find a workable
solution to the multiple-address problem.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Tue Apr 29 20:43:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18610;
	Tue, 29 Apr 2003 20:43:24 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Af0a-0006ZA-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 19:59:36 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AenE-000627-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 19:45:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16865
	for <ietf@ietf.org>; Tue, 29 Apr 2003 19:42:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AemP-0001Vz-00
	for ietf@ietf.org; Tue, 29 Apr 2003 19:44:57 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AemP-0001VC-00
	for ietf@ietf.org; Tue, 29 Apr 2003 19:44:57 -0400
Received: from edison.cisco.com (edison.cisco.com [171.70.144.164])
	by sj-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h3TNj1Yf014527;
	Tue, 29 Apr 2003 16:45:02 -0700 (PDT)
Received: from cisco.com (sjc-vpn1-280.cisco.com [10.21.97.24]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id QAA17880; Tue, 29 Apr 2003 16:45:01 -0700 (PDT)
Message-ID: <3EAF0E7B.7050307@cisco.com>
Date: Tue, 29 Apr 2003 16:44:59 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stephen Sprunk <stephen@sprunk.org>
CC: S Woodside <sbwoodside@yahoo.com>, ietf@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: policy domains
References: <224F012B-793C-11D7-A2F1-000393414368@yahoo.com> <005f01c30ea4$d74dee60$93b58742@ssprunk>
In-Reply-To: <005f01c30ea4$d74dee60$93b58742@ssprunk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Stephen,

I'm glad you sent this note.  One of us is under a serious 
misconception, and if it's you, I suspect there are a lot more like you.

Stephen Sprunk wrote:
> There's reasonable arguments against private addresses, but unless
> allocation policies are radically different than IPv4 practice, expecting a
> public address for every host is a pipe dream.

Tell me if http://www.arin.net/policy/ipv6_policy.html addresses your 
concern.  Particularly section 3.2.  The policy, as I read it, gives 
just about everyone a /48.  When counting subnets and interfaces on 
routers, consider that the equivalent of an IPv4 /16.  That's a lot of 
space.  According to the above document, there's no real experience of 
someone having hit that point yet.

Eliot





From owner-ietf@ietf.org  Tue Apr 29 20:43:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18622;
	Tue, 29 Apr 2003 20:43:25 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Af1F-0006ai-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 20:00:17 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Aepy-00065b-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 19:48:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17015
	for <ietf@ietf.org>; Tue, 29 Apr 2003 19:45:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AepA-0001Z7-00
	for ietf@ietf.org; Tue, 29 Apr 2003 19:47:48 -0400
Received: from tomts24.bellnexxia.net ([209.226.175.187] helo=tomts24-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aep9-0001Z4-00
	for ietf@ietf.org; Tue, 29 Apr 2003 19:47:47 -0400
Received: from yahoo.com ([65.93.183.168]) by tomts24-srv.bellnexxia.net
          (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP
          id <20030429234825.WBPK1119.tomts24-srv.bellnexxia.net@yahoo.com>;
          Tue, 29 Apr 2003 19:48:25 -0400
Date: Tue, 29 Apr 2003 19:48:23 -0400
Subject: Re: IPv6 address space shortages (was: Re: A simple question)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Bill Manning <bmanning@ISI.EDU>, Margaret Wasserman <mrw@windriver.com>,
        "ipng@sunroof.eng.sun.com" <ipng@sunroof.eng.sun.com>,
        "ietf@ietf.org" <ietf@ietf.org>
To: John C Klensin <john-ietf@jck.com>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <12729734.1051619514@p3.JCK.COM>
Message-Id: <10A9C0CD-7A9D-11D7-ACAF-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Tuesday, April 29, 2003, at 12:31  PM, John C Klensin wrote:

> It seems to me that if you, or anyone else, wants to make the case 
> that the IPv6 address space isn't going to be large enough, you need 
> to do so explicitly and immediately

John,

For purposes of geographic routing, it seems a little tight. Consider 
this proposal [1]

         | 4 |            44           |   16   |          64 bits       
    |
         
+---+-------------------------+--------+---------------------------+
         |FP |        Reference        |  SLA   |       Interface ID     
    |
         
+---+-------------------------+--------+---------------------------+

44 bits are provider independent and encode GPS coordinates. It's 
enough to have accuracy to roughly 10 meter squares. BUT ... that 
doesn't consider altitude. In addition, it's quite easy to see that 10 
meter squares may be a little bit too big for some purposes, even if 
you're just talking about individual homes. Also, it doesn't provide a 
mechanism to define an area rather than a point. I could go on.

So it's clear at least to me that under this scheme there is not enough 
space in IPv6 to do proper justice to georouting.

simon


[1] http://www.ietf.org/internet-drafts/draft-hain-ipv6-pi-addr-04.txt


--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Tue Apr 29 21:18:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19825;
	Tue, 29 Apr 2003 21:18:01 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AfiU-0007eT-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 20:44:58 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Af28-0006dt-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 20:01:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17354
	for <ietf@ietf.org>; Tue, 29 Apr 2003 19:58:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Af1K-0001fC-00
	for ietf@ietf.org; Tue, 29 Apr 2003 20:00:22 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Af1J-0001f9-00
	for ietf@ietf.org; Tue, 29 Apr 2003 20:00:21 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3U00qL31059;
	Tue, 29 Apr 2003 19:00:52 -0500
Message-ID: <00af01c30eab$90d795b0$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <jtk@aharp.is-net.depaul.edu>
Cc: <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
References: <3EAEC35D.EFA0D754@earthlink.com><69412F1F-7A80-11D7-A72E-00039388672E@muada.com> <20030429164544.5aee6169.jtk@depaul.edu>
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
Date: Tue, 29 Apr 2003 18:45:35 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "John Kristoff" <jtk@depaul.edu>
> This seems OK to me and appears to put the burden in the right place.
> Shouldn't it be the responsibility of those who are allocated address
> space to properly manage it?  Others can still filter on long and valid
> prefixes that they expect to hear.

Or, if these non-routed allocations were from a specific IANA-designated
block, providers could simply filter them all with one directive.

> ...and if its gonna leak anyway, it might as well be globally unique.
> Other networks will certainly be less likely to collide and try to
> communicate with the leaked space.

Certainly.  However, providers tend to advertise whatever customers pay them
to advertise, so these "non routable" blocks may end up permanently
reachable from non-trivial portions of the Internet.

There are some applications, such as pre-positioned content caching, where
it's desirable to only have connectivity to those topologically "close".
Overall, though, this makes it even more important that we find a workable
solution to the multiple-address problem.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Tue Apr 29 21:24:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20113;
	Tue, 29 Apr 2003 21:24:43 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AfiV-0007f0-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 20:44:59 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Af3x-0006jO-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 20:03:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17431
	for <ietf@ietf.org>; Tue, 29 Apr 2003 20:00:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Af39-0001gE-00
	for ietf@ietf.org; Tue, 29 Apr 2003 20:02:15 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Af38-0001gB-00
	for ietf@ietf.org; Tue, 29 Apr 2003 20:02:14 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26AA8> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 29 Apr 2003 17:02:17 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Ofer Inbar'" <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: site-local != NAT
Date: Tue, 29 Apr 2003 17:02:05 -0700
Message-ID: <075601c30eab$bc9629a0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030429181405.B6083@thwip.polyamory.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA20113

Ofer Inbar wrote:
> ...
> I think today's implied identity of "private address space" 
> and "locally scoped addresses" is really muddying the 
> discussion.  If we have a world where anyone who asks can get 
> a unique address block assigned to them to use for their 
> private network... THEN what are the remaining reasons why 
> people would want to use site-local addresses?

First,
http://www.ietf.org/internet-drafts/draft-hain-ipv6-sitelocal-00.txt is
offered with the intent to grow into an answer to the last part. 

Second, the IPv6 SL mechanism exposed the fundamental architectural
discrepancy between the traditional application world viewpoint that an
address was a valid identifier, and the deployed network where addresses
are topology locators and have different visibility in different regions
(aka: scopes). Almost all of the complaints against SL will persist even
with a non-ambiguous address space (the exception being connecting to
the wrong node, which was arguably unlikely to begin with given mac
based IIDs). At their core, these complaints are about bringing apps
(actually every process that resolves a data structure into a topology
locator) into the world of reality where they need to recognize that
various members in a list of potential addresses for a node may not be
equally accessible from every other node in the network. The fact that
IPv6 nodes can simultaneously have addresses of mixed scopes makes the
problem more acute, but it is no different than a multi-homed IPv4 node
where one or more of its addresses are not visible in the same scope of
the routing system, or there are different access controls placed on the
set by the network manager. The system as a whole needs to be revisited
in the context of making sure every node can resolve a given data
structure into a topologically appropriate locator. 

The IPv6 WG discussion about a specific prefix is probably best dealt
with there, but the broader issue about assumptions of a flat routed
space vs. the reality of limited topology scopes is something the IETF
as a whole needs to deal with, because it exposes many historically
invalid assumptions. 

Tony





From owner-ietf@ietf.org  Tue Apr 29 21:28:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20411;
	Tue, 29 Apr 2003 21:28:15 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Afib-0007hz-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 20:45:05 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AfHD-00077z-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 20:16:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17773
	for <ietf@ietf.org>; Tue, 29 Apr 2003 20:13:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AfGO-0001m0-00
	for ietf@ietf.org; Tue, 29 Apr 2003 20:15:56 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AfGN-0001lx-00
	for ietf@ietf.org; Tue, 29 Apr 2003 20:15:55 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3U0GLL31475;
	Tue, 29 Apr 2003 19:16:22 -0500
Message-ID: <00d101c30ead$bc0f3470$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "John C Klensin" <john-ietf@jck.com>, "Bill Manning" <bmanning@ISI.EDU>
Cc: "Margaret Wasserman" <mrw@windriver.com>, <ipng@sunroof.eng.sun.com>,
        <ietf@ietf.org>
References: <200304280524.h3S5OqA04605@boreas.isi.edu> <12729734.1051619514@p3.JCK.COM>
Subject: Re: IPv6 address space shortages (was: Re: A simple question)
Date: Tue, 29 Apr 2003 19:11:11 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "John C Klensin" <john-ietf@jck.com>
> It seems to me that if you, or anyone else, wants to make the
> case that the IPv6 address space isn't going to be large enough,
> you need to do so explicitly and immediately (five years ago
> would have been better, but maybe we know more now).   While I,
> personally, would have preferred extendable length addresses, it
> feels to me that saying "yet" at this stage in the game is just
> pointless sniping unless you are willing to argue for calling a
> halt at this stage and redesigning.

I see no reason to believe that the address length is insufficient on its
own; however, allocation policies and the way those bits are used may cause
exhaustion and/or a different way of looking at those bits.

Based on the number of hosts connected to the Internet today compared to the
total number of unicast IPv4 addresses, we are nowhere near a shortage.
Even so, pre-CIDR allocation policies resulted in vast amounts of unused
space.  Rationing of the remaining space has made NAT a necessary evil just
to keep the beast functional for the masses.

Are we doing the same thing with IPv6?  Maybe.  At worst, we're not making
any mistakes we can't correct later when we learn more.  I'm particularly
suspicious of the decision to use a /64 for each subnet instead of the
original /80 plan, and the allocation of a /3 to the RIRs is mind-boggling.
But I do think we bought ourselves enough headroom to seriously screw up
several times and not need a whole new protocol.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Tue Apr 29 22:10:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21502;
	Tue, 29 Apr 2003 22:10:33 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AgVA-0001cq-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 21:35:16 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AfmR-0008Qk-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 20:49:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18984
	for <ietf@ietf.org>; Tue, 29 Apr 2003 20:46:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aflc-00022R-00
	for ietf@ietf.org; Tue, 29 Apr 2003 20:48:12 -0400
Received: from c17249.carlnfd1.nsw.optusnet.com.au ([210.49.138.109] helo=bsdi.dv.isc.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aflb-00022D-00
	for ietf@ietf.org; Tue, 29 Apr 2003 20:48:11 -0400
Received: from drugs.dv.isc.org (drugs.dv.isc.org [192.168.191.236])
	by bsdi.dv.isc.org (8.12.9/8.12.9) with ESMTP id h3U0mDab056540;
	Wed, 30 Apr 2003 10:48:13 +1000 (EST)
	(envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.9/8.12.9) with ESMTP id h3U0mB54024561;
	Wed, 30 Apr 2003 10:48:12 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200304300048.h3U0mB54024561@drugs.dv.isc.org>
To: "Matt Crawford" <crawdad@fnal.gov>
Cc: Stephen Sprunk <stephen@sprunk.org>, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
From: Mark.Andrews@isc.org
Subject: Re: A simple question 
In-reply-to: Your message of "Tue, 29 Apr 2003 10:20:29 EST."
             <200304291520.h3TFKT2Y013209@gungnir.fnal.gov> 
Date: Wed, 30 Apr 2003 10:48:11 +1000
Sender: owner-ietf@ietf.org
Precedence: bulk


> There is nothing to indicate that ISPs are going to change their business
> models simply because IPv6 address space is plentiful; they charge extra for
> two hosts because it is assumed two hosts consume more bits than one, not
> because a second IPv4 address is hard to come by.

	There is nothing to indicate that they won't change either.

	ISP will meet their customers expectations or they will go
	out of business.  Today you expect to get a single IP address.
	If you make the expectation be that you will get a prefix ISP
	that fail to do this will go the way of the dodo.

	The cable provider I'm using didn't allow home networks at
	one time (they also had a single flat fee).  They do now
	though they leave the implementation and support to you
	(multiple volume based plans).  Customers expect to be able
	to connect their home network and the expectation is now
	being met.

	Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Tue Apr 29 22:13:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21738;
	Tue, 29 Apr 2003 22:13:09 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AgWN-0001dA-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 21:36:31 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AfqF-0008UJ-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 20:52:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19051
	for <ietf@ietf.org>; Tue, 29 Apr 2003 20:49:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AfpQ-000235-00
	for ietf@ietf.org; Tue, 29 Apr 2003 20:52:08 -0400
Received: from ginger.lcs.mit.edu ([18.26.0.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AfpP-000232-00
	for ietf@ietf.org; Tue, 29 Apr 2003 20:52:07 -0400
Received: from ginger.lcs.mit.edu (localhost [127.0.0.1])
	by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h3U0qitU008722;
	Tue, 29 Apr 2003 20:52:44 -0400
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h3U0qixQ008721;
	Tue, 29 Apr 2003 20:52:44 -0400
Date: Tue, 29 Apr 2003 20:52:44 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200304300052.h3U0qixQ008721@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: IPv6 address space shortages (was: Re: A simple question)
Cc: ipng@sunroof.eng.sun.com, jnc@ginger.lcs.mit.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

    > From: S Woodside <sbwoodside@yahoo.com>

    > For purposes of geographic routing

The Multi6 WG just went over geographic addressing again, for about the 17th
time in the IETF (I seem to recall previous go-rounds on it in CIDRD and
IPng), and finally left off talking about it, on the grounds that there were
enough people against it that it was extremely unlikely there would ever be
rough consensus for it.

I suggest the same calculation ought to occur in this forum, i.e. that
there's no point discussing geographic addressing, since there's never going
to be rough consensus for it.

	Noel



From owner-ietf@ietf.org  Tue Apr 29 22:27:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22058;
	Tue, 29 Apr 2003 22:27:21 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AgWW-0001ek-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 21:36:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Ag7R-0000DK-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 21:10:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19582
	for <ietf@ietf.org>; Tue, 29 Apr 2003 21:07:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ag6c-0002CO-00
	for ietf@ietf.org; Tue, 29 Apr 2003 21:09:54 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ag6b-0002CL-00
	for ietf@ietf.org; Tue, 29 Apr 2003 21:09:53 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26ABF> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 29 Apr 2003 18:10:26 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'S Woodside'" <sbwoodside@yahoo.com>,
        "'John C Klensin'" <john-ietf@jck.com>
Cc: "'Bill Manning'" <bmanning@ISI.EDU>,
        "'Margaret Wasserman'" <mrw@windriver.com>, <ipng@sunroof.eng.sun.com>,
        <ietf@ietf.org>
Subject: RE: IPv6 address space shortages (was: Re: A simple question)
Date: Tue, 29 Apr 2003 18:10:24 -0700
Message-ID: <076401c30eb5$47bf1380$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <10A9C0CD-7A9D-11D7-ACAF-000393414368@yahoo.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id WAA22058

S Woodside wrote:
> ...
> 44 bits are provider independent and encode GPS coordinates. 
> It's enough to have accuracy to roughly 10 meter squares. 

The 04 version reduced that to 6.4 m, but your point about it being
somewhat course is valid. I stopped at 44 bits because the goal was
creating a /48. If that is expanded to a /52 you are looking at > .5 m
resolution. While this is possible to encode, the publicly available
gear is not capable of measuring that accurately.

> BUT ... that doesn't consider altitude.  

Depending on the intended use, that can be further encoded in the
remaining bits to create a unique /64 per cubic .5 m, 2 km deep. 

> In addition, it's quite easy to see that 10 
> meter squares may be a little bit too big for some purposes, even if 
> you're just talking about individual homes. Also, it doesn't 
> provide a 
> mechanism to define an area rather than a point. I could go on.
> 
> So it's clear at least to me that under this scheme there is 
> not enough 
> space in IPv6 to do proper justice to georouting.

We have the option of using longer than /64 prefixes if necessary. I
would prefer not to go there, but given a unique need it could be done.

Tony

> 
> simon
> 
> 
> [1] http://www.ietf.org/internet-drafts/draft-hain-ipv6-pi-addr-04.txt
> 
> 
> --
> www.simonwoodside.com -- 99% Devil, 1% Angel
> 
> 




From owner-ietf@ietf.org  Tue Apr 29 23:13:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22998;
	Tue, 29 Apr 2003 23:13:19 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AhO8-0003IX-00
	for ietf-list@ran.ietf.org; Tue, 29 Apr 2003 22:32:04 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Ah2S-000244-00
	for ietf@ran.ietf.org; Tue, 29 Apr 2003 22:09:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21333
	for <ietf@ietf.org>; Tue, 29 Apr 2003 22:06:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ah1c-0002eR-00
	for ietf@ietf.org; Tue, 29 Apr 2003 22:08:48 -0400
Received: from scaup.mail.pas.earthlink.net ([207.217.120.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ah1b-0002eO-00
	for ietf@ietf.org; Tue, 29 Apr 2003 22:08:47 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by scaup.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19Ah27-0005P8-00; Tue, 29 Apr 2003 19:09:19 -0700
Date: Tue, 29 Apr 2003 22:08:21 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, cos@aaaaa.org, ietf@ietf.org
Subject: Re: site-local != NAT
Message-Id: <20030429220821.629e6364.moore@cs.utk.edu>
In-Reply-To: <075601c30eab$bc9629a0$261e4104@eagleswings>
References: <20030429181405.B6083@thwip.polyamory.org>
	<075601c30eab$bc9629a0$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (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


> Second, the IPv6 SL mechanism exposed the fundamental architectural
> discrepancy between the traditional application world viewpoint that an
> address was a valid identifier,

The address *is* a valid identifier in the IP architecture.  There is
no architectural discrepancy, only an explicit engineering compromise
to use the same bit string as both a host identifier and a location
identifier.  Your repeated assertions that this is an invalid assumption
are incorrect.  For better or worse, this is the way IP was designed to
work.  The only invalid assumption is that it's acceptable for the network
to fail to support this model, without considerable re-design of not just
IP but the entire architecture.






From owner-ietf@ietf.org  Wed Apr 30 00:31:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25106;
	Wed, 30 Apr 2003 00:31:40 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Aj5Q-0004ep-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 00:20:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Ain1-0004TG-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 00:01:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24344
	for <ietf@ietf.org>; Tue, 29 Apr 2003 23:58:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aim9-0003VO-00
	for ietf@ietf.org; Wed, 30 Apr 2003 00:00:57 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aim9-0003VD-00
	for ietf@ietf.org; Wed, 30 Apr 2003 00:00:57 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h3U40t1O012989;
	Tue, 29 Apr 2003 21:00:55 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id ADR68293;
	Tue, 29 Apr 2003 21:00:51 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id VAA09175; Tue, 29 Apr 2003 21:00:51 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16047.19059.264063.111036@thomasm-u1.cisco.com>
Date: Tue, 29 Apr 2003 21:00:51 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: <alh-ietf@tndh.net>, cos@aaaaa.org, ietf@ietf.org
Subject: Re: site-local != NAT
In-Reply-To: <20030429220821.629e6364.moore@cs.utk.edu>
References: <20030429181405.B6083@thwip.polyamory.org>
	<075601c30eab$bc9629a0$261e4104@eagleswings>
	<20030429220821.629e6364.moore@cs.utk.edu>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore writes:
 > 
 > > Second, the IPv6 SL mechanism exposed the fundamental architectural
 > > discrepancy between the traditional application world viewpoint that an
 > > address was a valid identifier,
 > 
 > The address *is* a valid identifier in the IP architecture.

   Er, um, well of an interface maybe. But what you
   really want is a host identifier, which is the source
   of lots of trouble...

      Mike



From owner-ietf@ietf.org  Wed Apr 30 00:47:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25561;
	Wed, 30 Apr 2003 00:47:20 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Aj5R-0004f6-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 00:20:53 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AiqY-0004Uw-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 00:05:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24473
	for <ietf@ietf.org>; Wed, 30 Apr 2003 00:02:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aiph-0003XZ-00
	for ietf@ietf.org; Wed, 30 Apr 2003 00:04:37 -0400
Received: from scaup.mail.pas.earthlink.net ([207.217.120.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aipg-0003XW-00
	for ietf@ietf.org; Wed, 30 Apr 2003 00:04:36 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by scaup.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19AiqF-0000kV-00; Tue, 29 Apr 2003 21:05:11 -0700
Date: Wed, 30 Apr 2003 00:04:14 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Michael Thomas <mat@cisco.com>
Cc: moore@cs.utk.edu, alh-ietf@tndh.net, cos@aaaaa.org, ietf@ietf.org
Subject: Re: site-local != NAT
Message-Id: <20030430000414.61e4383d.moore@cs.utk.edu>
In-Reply-To: <16047.19059.264063.111036@thomasm-u1.cisco.com>
References: <20030429181405.B6083@thwip.polyamory.org>
	<075601c30eab$bc9629a0$261e4104@eagleswings>
	<20030429220821.629e6364.moore@cs.utk.edu>
	<16047.19059.264063.111036@thomasm-u1.cisco.com>
X-Mailer: Sylpheed version 0.8.11 (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

>  > The address *is* a valid identifier in the IP architecture.
> 
>    Er, um, well of an interface maybe. But what you
>    really want is a host identifier, which is the source
>    of lots of trouble...

it is well-understood and generally agreed that the overloading of IP 
IP addresses to be both host identifers and location identifers
causes some trouble.  what is less well-understood is how much trouble
the alternatives cause - either lack of a suitable endpoint identifier,
or the trouble associated with providing suitable endpoint identifiers.

Keith



From owner-ietf@ietf.org  Wed Apr 30 04:50:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25504;
	Wed, 30 Apr 2003 04:50:30 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Amjl-00051U-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 04:14:45 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AmX0-0004qu-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 04:01:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24768
	for <ietf@ietf.org>; Wed, 30 Apr 2003 03:58:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AmW6-00050u-00
	for ietf@ietf.org; Wed, 30 Apr 2003 04:00:38 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AmW5-00050r-00
	for ietf@ietf.org; Wed, 30 Apr 2003 04:00:38 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.11.3/8.9.3) with ESMTP id h3U81EE96731;
	Wed, 30 Apr 2003 10:01:14 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Wed, 30 Apr 2003 10:01:11 +0200
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ipng@sunroof.eng.sun.com, ietf@ietf.org
To: pdeutsch@earthlink.net
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <3EAEFFA7.63A14F72@earthlink.com>
Message-Id: <E88632EC-7AE1-11D7-A65D-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, apr 30, 2003, at 00:41 Europe/Amsterdam, Peter Deutsch 
wrote:

>> How is answering any of these questions going to help us? "Oh, NATed
>> traffic is 7% and not 5%! You are right we should have site local
>> addresses then!"

> Well, I've a couple of responses to that.

> One, of course is that if NAT traffic is really only 5%, and it happens
> to be falling over time, then we should maybe stop spending so much 
> time
> arguing about it. :-)

Either we must support NAT or we don't. The actual usage of NAT at any 
given point of time really doesn't tell us which of those is the more 
reasonable position. It is not unheard of to support something that 
only 5% or less of the users need.

> (Note, if I really wanted to be excommunicated from this list, I could
> have done a s/NAT/IPv6/ on the above paragraph ;-)

By this reasoning there is no point in inventing something new because 
at the time of invention deployment is by definition 0.

IPv4 address space is running out. So the IETF did the responsible 
thing and developed a new protocol that wouldn't have this problem. If 
people then fail to adopt this protocol, well, that's their problem.

> Here's a quick sampling of statements presented over the past few days
> to support the two sides of the debate

>     - "there are more rfc1918 end hosts than there are non-rfc1918
>        end hosts,

Ok, this sounds like hyperbole to me.


>        and the uses being made of rfc1918 aren't limited
>        to "couldn't get enough unique address space" situations."

>      - "NAT is most often used to extend a single address to
>         cover multiple systems in a home or small office
>         environment. For that environment, an IPv6 /48
>         (without site-locals) would suffice to replace NAT."

>      - "NAT is used almost everywhere (perhaps outside the US)
>         - almost everywhere."

Now these are all very interesting but what does it prove? Yes, we know 
NAT _is_ being used in IPv4 and yes, we know you _can_ do without it 
given enough public address space.

>      - "When you are talking about tens of millions of customers,
>         it's not feasible to give each a subnet even if you have
>         the space to do it.  IMHO, most customers will be placed
>         on a /64 that's shared across hundreds of customers, similar
>         to IPv4 common practice."

This is actually a good point, although this may not seem obvious to 
non-ops people. Today, dial-up concentrators usually have an address 
range that it used to assign addresses to people that dial in. That 
means at most a handful of routes per dial-up concentrator in the 
interior routing protocol. If everyone has their own /48, that means a 
route in the IGP for each customer that's online. There are no hard and 
fast rules about how many routes you can have in an IGP, but somewhere 
between 10k and 1M you run into trouble. I hate to offer opinions 
without facts to back them up, but I'm pretty sure there are dial-up 
ISPs with closer to 1M than 10k ports.

However, assigning each customer an IPv6 /64 the same way they now get 
an IPv4 /32 should be workable.

>      - "While it is true that address conservation isn't that
>         significant an issue, the whole issue of provider
>         independence (or lack thereof) continues to exist."

What is your problem with this? Seems like a valid statement to me.

>      - "One of the biggest costs in renumbering is the
>         disruption it causes. The actual cost of editing
>         the files, etc, is trivial by comparison."

Some figures would be good here, but from my experience this doesn't 
sound too far off.

>      - "Even RFC1918 addresses get connected sometimes through
>         corporate mergers. It would work better if organizations
>         would choose a random set of subnets from 10/8, so the
>         chance of overlap is minimized."

Ok, this is something I'd like to see. My gut says this is too simple, 
but maybe not...

>      - "They [ISPs] charge extra for two hosts because it
>         is assumed two hosts consume more bits than one, not
>         because a second IPv4 address is hard to come by."

This one would also be interesting to put into numbers. If this is 
really true we can expect a /64 to be 2^64 times as expensive as a /32 
in IPv4...

> Now, it may be true that *all* of the above statements are true, but
> they don't help me because I can't tell, from the statements alone,
> which ones are actually *relevant* to the debate.

I have to agree with you there.

> So, just as in your
> somewhat offhand use of "7% versus 5%" above, it all seems a little bit
> like the statement that "46 percent of all statistics are made up".

The 7% and 5% are definately made up.

>> The current state of IPv6 deployment has very little bearing on future
>> IPv6 deployment. Just look back 20 years in IPv4. I don't think any of
>> the problems we have today could have been predicted by looking at the
>> network then.

> Well, this is a good example where something may be true, but not
> relevant.

The statement above may not be directly relevant to the discussion, but 
it should disprove your assumption that IPv6 deployment today is.

> If, after all this "Sturm und Drang", IPv6 is not yet growing
> faster than overall network traffic, those of us who remember X.500 may
> conclude that it's not going to be relevant to me within an event
> horizon that I need to care about, so I might conclude that I can 
> ignore
> it (and by extension, arguments predicated on its success).

At some point this argument is going to stick, but at this point it is 
too soon to tell whether current low levels of v6 deployment are 
because everyone is taking their time or because it's never going to 
amount to anything.

> Now, this
> may get me excommunicated from this list, but it may be the right thing
> for me to do. How can I tell from this thread? I could be persuaded to
> pay attention to such arguments by some numbers.

When I connected to the 6bone a year or two ago, all I could do over 
IPv6 was traceroute from a server. Today, I browse the web on a fully 
IPv6-enabled host with mostly IPv6-enabled software so I get to see 
some actual web content over IPv6. Also, I regularly use IPv6 for other 
applications. It's still not much compared to IPv4, but the progress 
has been remarkable.

> Another observation, there appears to be at least two major schools of
> philosophy at work here (time for another random analogy for you 
> Science
> majors to go look up on Google... ;-)

Maybe you should pick the rationalists versus the empiricists for your 
next example...

> Now, if "there are more rfc1918 end hosts than there are non-rfc1918 
> end
> hosts" and "NAT is most often used to extend a single address to cover
> multiple systems in a home or small office" then I might be inclined to
> give more weight to arguments which make the network a better place for
> the Thoreaus of the world (or is that "Bllom County"?), but if the most
> important issues for our future are really going to be about supporting
> large campus installations, it might drive the trade-offs in a 
> different
> direction. There Are No Free Lunches, so knowing what the target is
> might help us all collectively take better aim....

If I buy ADSL or cable service I get a single IPv4 address unless I pay 
a lot extra. Since I have more than one computer, I am forced to use 
RFC 1918 space. I wouldn't want anyone to pervert my lack of choice 
into a position supporting NAT in IPv6.

>> I wouldn't presume to know why people use NAT because I'm not one of
>> them. (Beginning to feel like a minority.)

> Well, if anyone's going to argue against them, shouldn't they at least
> understand why they're being deployed?? ;-)

Obviously I can think of one or two reasons. But when I see NAT, I see 
problems. Some people seem to actually like NAT. If they can help me 
understand why, that could very well be valuable information.

> Again, just to illustrate my thesis, in the above response you seem to
> assume:

> 	- network merging happens often enough that it is a significant
>           problem that must be addressed at the architectural level
>           (that is, here at the IETF);
> 	- it costs a lot of time and money to renumber.

> If either of these assertions is not true, you have to go back to the
> beginning and start again.

I know the latter is true from personal experience. I've also come 
close enough to the former to believe this is a real problem, but I 
have nothing hard there.

But if we're going to attach dollar values to one end of the argument, 
we need to do it everywhere. That's the only way to be able to 
determine how we can make standards that cost people the least amount 
of money. But nobody can predict the future, so I don't think this will 
work in practice.




From owner-ietf@ietf.org  Wed Apr 30 04:58:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25794;
	Wed, 30 Apr 2003 04:58:49 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AnKJ-0005Es-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 04:52:31 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Ams3-00052w-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 04:23:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25115
	for <ietf@ietf.org>; Wed, 30 Apr 2003 04:20:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Amr9-00056I-00
	for ietf@ietf.org; Wed, 30 Apr 2003 04:22:23 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Amr8-00056F-00
	for ietf@ietf.org; Wed, 30 Apr 2003 04:22:22 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.11.3/8.9.3) with ESMTP id h3U8N1E96762;
	Wed, 30 Apr 2003 10:23:01 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Wed, 30 Apr 2003 10:23:01 +0200
Subject: Re: IPv6 address space shortages (was: Re: A simple question)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org, ipng@sunroof.eng.sun.com
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200304300052.h3U0qixQ008721@ginger.lcs.mit.edu>
Message-Id: <F560F118-7AE4-11D7-A65D-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, apr 30, 2003, at 02:52 Europe/Amsterdam, J. Noel Chiappa 
wrote:

> The Multi6 WG just went over geographic addressing again, for about 
> the 17th
> time in the IETF (I seem to recall previous go-rounds on it in CIDRD 
> and
> IPng), and finally left off talking about it, on the grounds that 
> there were
> enough people against it that it was extremely unlikely there would 
> ever be
> rough consensus for it.

I wouldn't exactly characterize the discussion this way.

Yes, we discussed it, but I don't feel my draft got a fair hearing. 
I've seen very little evidence that people actually read it, most of 
the arguments are of the quality "my aunt Bertha connects to two ISPs 
in different continents so geographic aggregation can never work".

We sorta kinda agreed that we need a draft to put the issue to bed for 
a good long time, but nothing concrete here.

> I suggest the same calculation ought to occur in this forum, i.e. that
> there's no point discussing geographic addressing, since there's never 
> going
> to be rough consensus for it.

This sounds awfully similar to what the French said about a new 
security council resolution about Iraq: regardless of the content of 
your proposal, we'll veto it.

For those of you who want to form your own opinion, this is the 
addressing draft that uses a /16 for the entire world (just for 
multihomed networks, others continue to use PA space):
http://www.muada.com/drafts/draft-py-multi6-gapi-00.txt

And this draft outlines the aggregation procedures inside ISP networks 
(so no announcing of aggregates between ISPs):
http://www.muada.com/drafts/draft-van-beijnum-multi6-isp-int-aggr-00.txt

(They both expire this month so I'm not sure if they're still in the 
IETF drafts repository.)

Any questions are probably best handled off-list.

Iljitsch van Beijnum




From owner-ietf@ietf.org  Wed Apr 30 09:41:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02856;
	Wed, 30 Apr 2003 09:41:24 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Aqm5-00077w-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 08:33:25 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AqD2-0006k0-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 07:57:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29142
	for <ietf@ietf.org>; Wed, 30 Apr 2003 07:54:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AqC5-0006CD-00
	for ietf@ietf.org; Wed, 30 Apr 2003 07:56:13 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AqC5-0006CA-00
	for ietf@ietf.org; Wed, 30 Apr 2003 07:56:13 -0400
Received: from localhost ([127.0.0.1] helo=roam.psg.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19AqCh-000CEM-00; Wed, 30 Apr 2003 11:56:51 +0000
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.14)
	id 19Apr8-0009Pn-Bh; Wed, 30 Apr 2003 04:34:34 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 30 Apr 2003 04:34:33 -0700
To: Michael Thomas <mat@cisco.com>
Cc: Keith Moore <moore@cs.utk.edu>, <alh-ietf@tndh.net>, cos@aaaaa.org,
        ietf@ietf.org
Subject: Re: site-local != NAT
References: <20030429181405.B6083@thwip.polyamory.org>
	<075601c30eab$bc9629a0$261e4104@eagleswings>
	<20030429220821.629e6364.moore@cs.utk.edu>
	<16047.19059.264063.111036@thomasm-u1.cisco.com>
Message-Id: <E19Apr8-0009Pn-Bh@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>> The address *is* a valid identifier in the IP architecture.
> Er, um, well of an interface maybe. But what you
> really want is a host identifier, which is the source
> of lots of trouble...

want != have

and keith is trying to focus on the pragmatic reality

randy




From owner-ietf@ietf.org  Wed Apr 30 09:56:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03469;
	Wed, 30 Apr 2003 09:56:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Arub-00054X-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 09:46:17 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19ArXk-00023w-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 09:22:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01870
	for <ietf@ietf.org>; Wed, 30 Apr 2003 09:19:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ArWn-0006oN-00
	for ietf@ietf.org; Wed, 30 Apr 2003 09:21:41 -0400
Received: from aharp.is-net.depaul.edu ([140.192.91.90])
	by ietf-mx with smtp (Exim 4.12)
	id 19ArWm-0006oF-00
	for ietf@ietf.org; Wed, 30 Apr 2003 09:21:40 -0400
Received: (qmail 5729 invoked from network); 30 Apr 2003 13:21:49 -0000
Received: from aharp.is-net.depaul.edu (HELO cna4-019.cna.depaul.edu) (140.192.91.90)
  by aharp.is-net.depaul.edu with SMTP; 30 Apr 2003 13:21:49 -0000
Date: Wed, 30 Apr 2003 08:22:08 -0500
From: John Kristoff <jtk@depaul.edu>
Cc: ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
Message-Id: <20030430082208.417794ae.jtk@depaul.edu>
In-Reply-To: <00af01c30eab$90d795b0$93b58742@ssprunk>
References: <3EAEC35D.EFA0D754@earthlink.com>
	<69412F1F-7A80-11D7-A72E-00039388672E@muada.com>
	<20030429164544.5aee6169.jtk@depaul.edu>
	<00af01c30eab$90d795b0$93b58742@ssprunk>
Reply-To: jtk@aharp.is-net.depaul.edu
X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i686-pc-linux-gnu)
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

On Tue, 29 Apr 2003 18:45:35 -0500
"Stephen Sprunk" <stephen@sprunk.org> wrote:

> Thus spake "John Kristoff" <jtk@depaul.edu>
> > This seems OK to me and appears to put the burden in the right
> > place. Shouldn't it be the responsibility of those who are allocated
> > address space to properly manage it?  Others can still filter on
> > long and valid prefixes that they expect to hear.
> 
> Or, if these non-routed allocations were from a specific
> IANA-designated block, providers could simply filter them all with one
> directive.

Just to clear up a misconception on my part.  I misread the comment I
was responding to.  Quoting:

"If we allow people to register non-routable globally unique addresses 
for private use"

My brain for some reason initially interpretted that as "registering
globally unique addresses, but not having them be routable, due to local
policy", which is a bit different.  For one, it wouldn't accommodate
simple, well known non-routeable filters.

John



From owner-ietf@ietf.org  Wed Apr 30 10:04:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04137;
	Wed, 30 Apr 2003 10:04:36 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Arg0-0002kp-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 09:31:12 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Ar5Y-0007H2-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 08:53:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00545
	for <ietf@ietf.org>; Wed, 30 Apr 2003 08:50:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ar4b-0006SI-00
	for ietf@ietf.org; Wed, 30 Apr 2003 08:52:33 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ar4a-0006S9-00
	for ietf@ietf.org; Wed, 30 Apr 2003 08:52:32 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h3SKGO08005790;
	Mon, 28 Apr 2003 13:16:25 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id ADQ23631;
	Mon, 28 Apr 2003 13:16:12 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id NAA01463; Mon, 28 Apr 2003 13:16:11 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16045.35851.830913.532844@thomasm-u1.cisco.com>
Date: Mon, 28 Apr 2003 13:16:11 -0700 (PDT)
To: Eliot Lear <lear@cisco.com>
Cc: Stephen Sprunk <stephen@sprunk.org>, Robert Elz <kre@munnari.OZ.AU>,
        Margaret Wasserman <mrw@windriver.com>, Valdis.Kletnieks@vt.edu,
        Dave Crocker <dcrocker@brandenburg.com>, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A simple question
In-Reply-To: <3EAD5CE6.2050702@cisco.com>
References: <200304192151.h3JLpKuL019276@turing-police.cc.vt.edu>
	<200304191923.h3JJNOuL018209@turing-police.cc.vt.edu>
	<16890640984.20030419070719@brandenburg.com>
	<002401c30605$e22da070$261e4104@eagleswings>
	<9540645034.20030418171403@brandenburg.com>
	<a05210603bac6d68105ed@[10.0.0.3]>
	<11870.1050777166@munnari.OZ.AU>
	<14570.1050784897@munnari.OZ.AU>
	<5.1.0.14.2.20030428053937.047cbc68@mail.windriver.com>
	<00b401c30da4$390d81d0$93b58742@ssprunk>
	<3EAD5CE6.2050702@cisco.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eliot Lear writes:
 > Stephen Sprunk wrote:
 > 
 > > When you are talking about tens of millions of customers, it's not feasible
 > > to give each a subnet even if you have the space to do it.  IMHO, most
 > > customers will be placed on a /64 that's shared across hundreds of
 > > customers, similar to IPv4 common practice.
 > 
 > Why?

   Network puritanism: the haunting fear that someone,
   somewhere may be happy with their own subnet.

	     Mike



From owner-ietf@ietf.org  Wed Apr 30 10:16:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05483;
	Wed, 30 Apr 2003 10:16:36 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19As62-0005K7-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 09:58:06 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19As3w-0005Do-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 09:55:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03344
	for <ietf@ietf.org>; Wed, 30 Apr 2003 09:52:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19As2y-0007EF-00
	for ietf@ietf.org; Wed, 30 Apr 2003 09:54:57 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by ietf-mx with esmtp (Exim 4.12)
	id 19As2y-0007Ds-00
	for ietf@ietf.org; Wed, 30 Apr 2003 09:54:56 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-5.cisco.com (8.12.6/8.12.6) with ESMTP id h3UDswIP002417;
	Wed, 30 Apr 2003 06:54:58 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id ADR92700;
	Wed, 30 Apr 2003 06:54:49 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id GAA11474; Wed, 30 Apr 2003 06:54:49 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16047.54697.246635.743458@thomasm-u1.cisco.com>
Date: Wed, 30 Apr 2003 06:54:49 -0700 (PDT)
To: Randy Bush <randy@psg.com>
Cc: Michael Thomas <mat@cisco.com>, Keith Moore <moore@cs.utk.edu>,
        <alh-ietf@tndh.net>, cos@aaaaa.org, ietf@ietf.org
Subject: Re: site-local != NAT
In-Reply-To: <E19Apr8-0009Pn-Bh@roam.psg.com>
References: <20030429181405.B6083@thwip.polyamory.org>
	<075601c30eab$bc9629a0$261e4104@eagleswings>
	<20030429220821.629e6364.moore@cs.utk.edu>
	<16047.19059.264063.111036@thomasm-u1.cisco.com>
	<E19Apr8-0009Pn-Bh@roam.psg.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Randy Bush writes:
 > >> The address *is* a valid identifier in the IP architecture.
 > > Er, um, well of an interface maybe. But what you
 > > really want is a host identifier, which is the source
 > > of lots of trouble...
 > 
 > want != have
 > 
 > and keith is trying to focus on the pragmatic reality

Well, the pragmatic reality is to avoid using IP
addresses as substitutes for endpoint
identitifiers. Or maybe that's not pragmatic, but
tough noogies; using IP addresses as endpoint
identifiers is sloppy and generally a bad idea.

	       Mike



From owner-ietf@ietf.org  Wed Apr 30 10:29:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05931;
	Wed, 30 Apr 2003 10:29:10 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AsWd-0005Ke-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 10:25:35 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AsCV-0007Mp-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 10:04:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03897
	for <ietf@ietf.org>; Wed, 30 Apr 2003 10:01:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AsBX-0007O4-00
	for ietf@ietf.org; Wed, 30 Apr 2003 10:03:47 -0400
Received: from swan.mail.pas.earthlink.net ([207.217.120.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AsBX-0007O1-00
	for ietf@ietf.org; Wed, 30 Apr 2003 10:03:47 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by swan.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19AsC2-0000U8-00; Wed, 30 Apr 2003 07:04:18 -0700
Date: Wed, 30 Apr 2003 10:03:20 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Michael Thomas <mat@cisco.com>
Cc: moore@cs.utk.edu, randy@psg.com, mat@cisco.com, alh-ietf@tndh.net,
        cos@aaaaa.org, ietf@ietf.org
Subject: Re: site-local != NAT
Message-Id: <20030430100320.54070e48.moore@cs.utk.edu>
In-Reply-To: <16047.54697.246635.743458@thomasm-u1.cisco.com>
References: <20030429181405.B6083@thwip.polyamory.org>
	<075601c30eab$bc9629a0$261e4104@eagleswings>
	<20030429220821.629e6364.moore@cs.utk.edu>
	<16047.19059.264063.111036@thomasm-u1.cisco.com>
	<E19Apr8-0009Pn-Bh@roam.psg.com>
	<16047.54697.246635.743458@thomasm-u1.cisco.com>
X-Mailer: Sylpheed version 0.8.11 (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

> Well, the pragmatic reality is to avoid using IP
> addresses as substitutes for endpoint
> identitifiers. Or maybe that's not pragmatic, but
> tough noogies; using IP addresses as endpoint
> identifiers is sloppy and generally a bad idea.

...and at this point the argument repeats, without your having acquired
any additional clue.  




From owner-ietf@ietf.org  Wed Apr 30 10:43:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06525;
	Wed, 30 Apr 2003 10:43:32 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AsWi-0005NY-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 10:25:40 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AsHa-0001o7-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 10:10:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04537
	for <ietf@ietf.org>; Wed, 30 Apr 2003 10:06:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AsGc-0007T6-00
	for ietf@ietf.org; Wed, 30 Apr 2003 10:09:02 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AsGb-0007Sh-00
	for ietf@ietf.org; Wed, 30 Apr 2003 10:09:02 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h3UE951O023040;
	Wed, 30 Apr 2003 07:09:06 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id ADR93567;
	Wed, 30 Apr 2003 07:09:05 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id HAA11584; Wed, 30 Apr 2003 07:09:05 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16047.55553.121243.531738@thomasm-u1.cisco.com>
Date: Wed, 30 Apr 2003 07:09:05 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: Michael Thomas <mat@cisco.com>, randy@psg.com, alh-ietf@tndh.net,
        cos@aaaaa.org, ietf@ietf.org
Subject: Re: site-local != NAT
In-Reply-To: <20030430100320.54070e48.moore@cs.utk.edu>
References: <20030429181405.B6083@thwip.polyamory.org>
	<075601c30eab$bc9629a0$261e4104@eagleswings>
	<20030429220821.629e6364.moore@cs.utk.edu>
	<16047.19059.264063.111036@thomasm-u1.cisco.com>
	<E19Apr8-0009Pn-Bh@roam.psg.com>
	<16047.54697.246635.743458@thomasm-u1.cisco.com>
	<20030430100320.54070e48.moore@cs.utk.edu>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore writes:
 > > Well, the pragmatic reality is to avoid using IP
 > > addresses as substitutes for endpoint
 > > identitifiers. Or maybe that's not pragmatic, but
 > > tough noogies; using IP addresses as endpoint
 > > identifiers is sloppy and generally a bad idea.
 > 
 > ...and at this point the argument repeats, without your having acquired
 > any additional clue.  

Maybe if you and Randy stopped playing elliptical
word games we could have some communication
here. If you have a point, make it.

	Mike



From owner-ietf@ietf.org  Wed Apr 30 10:53:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07036;
	Wed, 30 Apr 2003 10:53:49 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AsZr-0005Tc-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 10:28:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AsTq-0005H7-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 10:22:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05709
	for <ietf@ietf.org>; Wed, 30 Apr 2003 10:19:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AsSr-0007Zo-00
	for ietf@ietf.org; Wed, 30 Apr 2003 10:21:42 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AsSr-0007Zl-00
	for ietf@ietf.org; Wed, 30 Apr 2003 10:21:41 -0400
Received: from localhost ([127.0.0.1] helo=roam.psg.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19AsTS-000Plo-00; Wed, 30 Apr 2003 14:22:19 +0000
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.14)
	id 19AsJB-0009mc-3D; Wed, 30 Apr 2003 07:11:41 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 30 Apr 2003 07:11:40 -0700
To: Michael Thomas <mat@cisco.com>
Cc: Keith Moore <moore@cs.utk.edu>, <alh-ietf@tndh.net>, cos@aaaaa.org,
        ietf@ietf.org
Subject: Re: site-local != NAT
References: <20030429181405.B6083@thwip.polyamory.org>
	<075601c30eab$bc9629a0$261e4104@eagleswings>
	<20030429220821.629e6364.moore@cs.utk.edu>
	<16047.19059.264063.111036@thomasm-u1.cisco.com>
	<E19Apr8-0009Pn-Bh@roam.psg.com>
	<16047.54697.246635.743458@thomasm-u1.cisco.com>
Message-Id: <E19AsJB-0009mc-3D@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>>>> The address *is* a valid identifier in the IP architecture.
>>> Er, um, well of an interface maybe. But what you
>>> really want is a host identifier, which is the source
>>> of lots of trouble...
>> want != have
>> and keith is trying to focus on the pragmatic reality
> Well, the pragmatic reality is to avoid using IP
> addresses as substitutes for endpoint
> identitifiers. Or maybe that's not pragmatic, but
> tough noogies; using IP addresses as endpoint
> identifiers is sloppy and generally a bad idea.

so are war and hunger




From owner-ietf@ietf.org  Wed Apr 30 10:53:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07039;
	Wed, 30 Apr 2003 10:53:49 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AsZr-0005Ti-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 10:28:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AsTr-0005H9-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 10:22:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05713
	for <ietf@ietf.org>; Wed, 30 Apr 2003 10:19:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AsSt-0007Zu-00
	for ietf@ietf.org; Wed, 30 Apr 2003 10:21:43 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AsSs-0007Zp-00
	for ietf@ietf.org; Wed, 30 Apr 2003 10:21:43 -0400
Received: from localhost ([127.0.0.1] helo=roam.psg.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19AsTU-000Plo-00; Wed, 30 Apr 2003 14:22:21 +0000
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.14)
	id 19AsLJ-0009my-Om; Wed, 30 Apr 2003 07:13:53 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 30 Apr 2003 07:13:52 -0700
To: Michael Thomas <mat@cisco.com>
Cc: Keith Moore <moore@cs.utk.edu>, alh-ietf@tndh.net, cos@aaaaa.org,
        ietf@ietf.org
Subject: Re: site-local != NAT
References: <20030429181405.B6083@thwip.polyamory.org>
	<075601c30eab$bc9629a0$261e4104@eagleswings>
	<20030429220821.629e6364.moore@cs.utk.edu>
	<16047.19059.264063.111036@thomasm-u1.cisco.com>
	<E19Apr8-0009Pn-Bh@roam.psg.com>
	<16047.54697.246635.743458@thomasm-u1.cisco.com>
	<20030430100320.54070e48.moore@cs.utk.edu>
	<16047.55553.121243.531738@thomasm-u1.cisco.com>
Message-Id: <E19AsLJ-0009my-Om@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Maybe if you and Randy stopped playing elliptical
> word games we could have some communication
> here. If you have a point, make it.

keith did.  it's just that you didn't like it.

the reality is that today, identifiers are addresses are routing.
we may or may not like this, but it is fact.

randy




From owner-ietf@ietf.org  Wed Apr 30 10:58:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07451;
	Wed, 30 Apr 2003 10:58:19 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AsxK-0006P1-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 10:53:10 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AsZ1-0005OV-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 10:28:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05851
	for <ietf@ietf.org>; Wed, 30 Apr 2003 10:24:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AsY3-0007cN-00
	for ietf@ietf.org; Wed, 30 Apr 2003 10:27:03 -0400
Received: from flamingo.mail.pas.earthlink.net ([207.217.120.232])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AsY2-0007cK-00
	for ietf@ietf.org; Wed, 30 Apr 2003 10:27:03 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by flamingo.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19AsYY-0003cV-00; Wed, 30 Apr 2003 07:27:35 -0700
Date: Wed, 30 Apr 2003 10:26:36 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Michael Thomas <mat@cisco.com>
Cc: moore@cs.utk.edu, mat@cisco.com, randy@psg.com, alh-ietf@tndh.net,
        cos@aaaaa.org, ietf@ietf.org
Subject: Re: site-local != NAT
Message-Id: <20030430102636.30d1dcf9.moore@cs.utk.edu>
In-Reply-To: <16047.55553.121243.531738@thomasm-u1.cisco.com>
References: <20030429181405.B6083@thwip.polyamory.org>
	<075601c30eab$bc9629a0$261e4104@eagleswings>
	<20030429220821.629e6364.moore@cs.utk.edu>
	<16047.19059.264063.111036@thomasm-u1.cisco.com>
	<E19Apr8-0009Pn-Bh@roam.psg.com>
	<16047.54697.246635.743458@thomasm-u1.cisco.com>
	<20030430100320.54070e48.moore@cs.utk.edu>
	<16047.55553.121243.531738@thomasm-u1.cisco.com>
X-Mailer: Sylpheed version 0.8.11 (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

>  > > Well, the pragmatic reality is to avoid using IP
>  > > addresses as substitutes for endpoint
>  > > identitifiers. Or maybe that's not pragmatic, but
>  > > tough noogies; using IP addresses as endpoint
>  > > identifiers is sloppy and generally a bad idea.
>  > 
>  > ...and at this point the argument repeats, without your having acquired
>  > any additional clue.  
> 
> Maybe if you and Randy stopped playing elliptical
> word games we could have some communication
> here. If you have a point, make it.

sorry if I wasn't clear enough.  what I was saying is that it's pointless for
us to repeat the same things over and over.  and it's pointless for me to try
to explain this to you or anyone else who isn't willing to re-evaluate his
views in light of someone else's experience.

Keith



From owner-ietf@ietf.org  Wed Apr 30 10:58:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07506;
	Wed, 30 Apr 2003 10:58:40 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AszL-0006WJ-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 10:55:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Asiq-0005sW-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 10:38:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06237
	for <ietf@ietf.org>; Wed, 30 Apr 2003 10:35:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ashs-0007hY-00
	for ietf@ietf.org; Wed, 30 Apr 2003 10:37:12 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ashr-0007hU-00
	for ietf@ietf.org; Wed, 30 Apr 2003 10:37:11 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h3UEbFYf005453;
	Wed, 30 Apr 2003 07:37:15 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id ADR95297;
	Wed, 30 Apr 2003 07:36:00 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id HAA11815; Wed, 30 Apr 2003 07:35:59 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16047.57167.821886.158969@thomasm-u1.cisco.com>
Date: Wed, 30 Apr 2003 07:35:59 -0700 (PDT)
To: Randy Bush <randy@psg.com>
Cc: Michael Thomas <mat@cisco.com>, Keith Moore <moore@cs.utk.edu>,
        alh-ietf@tndh.net, cos@aaaaa.org, ietf@ietf.org
Subject: Re: site-local != NAT
In-Reply-To: <E19AsLJ-0009my-Om@roam.psg.com>
References: <20030429181405.B6083@thwip.polyamory.org>
	<075601c30eab$bc9629a0$261e4104@eagleswings>
	<20030429220821.629e6364.moore@cs.utk.edu>
	<16047.19059.264063.111036@thomasm-u1.cisco.com>
	<E19Apr8-0009Pn-Bh@roam.psg.com>
	<16047.54697.246635.743458@thomasm-u1.cisco.com>
	<20030430100320.54070e48.moore@cs.utk.edu>
	<16047.55553.121243.531738@thomasm-u1.cisco.com>
	<E19AsLJ-0009my-Om@roam.psg.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Randy Bush writes:
 > > Maybe if you and Randy stopped playing elliptical
 > > word games we could have some communication
 > > here. If you have a point, make it.
 > 
 > keith did.  it's just that you didn't like it.
 > 
 > the reality is that today, identifiers are addresses are routing.
 > we may or may not like this, but it is fact.

Fine. The reality is NAT and RFC1918 too. That
doesn't mean that we should just give up. And
unlike the intractable set of problems that drive
NAT's, it's trivial to djinn up collision
resistant names which can be used in lieu of the
abdication of thought implicit in recvfrom() as
the Bearer of Names. Diffie Hellman is your
friend.

		Mike



From owner-ietf@ietf.org  Wed Apr 30 11:46:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09372;
	Wed, 30 Apr 2003 11:46:45 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AtcD-0000Ht-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 11:35:25 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AtYx-0000Cs-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 11:32:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08717
	for <ietf@ietf.org>; Wed, 30 Apr 2003 11:28:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AtXy-0000XD-00
	for ietf@ietf.org; Wed, 30 Apr 2003 11:31:02 -0400
Received: from turkey.mail.pas.earthlink.net ([207.217.120.126])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AtXy-0000XA-00
	for ietf@ietf.org; Wed, 30 Apr 2003 11:31:02 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by turkey.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19AtYW-0006j5-00; Wed, 30 Apr 2003 08:31:36 -0700
Date: Wed, 30 Apr 2003 11:30:37 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: moore@cs.utk.edu, pdeutsch@earthlink.net, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
Message-Id: <20030430113037.5ffa287c.moore@cs.utk.edu>
In-Reply-To: <E88632EC-7AE1-11D7-A65D-00039388672E@muada.com>
References: <3EAEFFA7.63A14F72@earthlink.com>
	<E88632EC-7AE1-11D7-A65D-00039388672E@muada.com>
X-Mailer: Sylpheed version 0.8.11 (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

> Today, dial-up concentrators usually have an address 
> range that it used to assign addresses to people that dial in. That 
> means at most a handful of routes per dial-up concentrator in the 
> interior routing protocol. If everyone has their own /48, that means a 
> route in the IGP for each customer that's online. There are no hard and 
> fast rules about how many routes you can have in an IGP, but somewhere 
> between 10k and 1M you run into trouble. 

this is an interesting point, but I think it has more to do with whether
the prefixes are statically bound to customers than the length of those
prefixes.  why would  giving customers static /64s result in fewer routes in
your IGP than giving them static /48s?   in neither case is there a direct
correspondence between the customer's address and the concentrator.





From owner-ietf@ietf.org  Wed Apr 30 11:51:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09633;
	Wed, 30 Apr 2003 11:51:21 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Atc5-0000G0-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 11:35:17 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AtUS-00006U-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 11:27:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08568
	for <ietf@ietf.org>; Wed, 30 Apr 2003 11:24:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AtTT-0000Uu-00
	for ietf@ietf.org; Wed, 30 Apr 2003 11:26:23 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AtTT-0000Ur-00
	for ietf@ietf.org; Wed, 30 Apr 2003 11:26:23 -0400
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 19AtU2-0007QF-00; Wed, 30 Apr 2003 10:26:58 -0500
Date: Wed, 30 Apr 2003 11:26:58 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael Thomas <mat@cisco.com>
cc: Keith Moore <moore@cs.utk.edu>, "randy@psg.com" <randy@psg.com>,
        "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: site-local != NAT
Message-ID: <95232316.1051702018@p3.JCK.COM>
In-Reply-To: <16047.55553.121243.531738@thomasm-u1.cisco.com>
References: <20030429181405.B6083@thwip.polyamory.org>
 	<075601c30eab$bc9629a0$261e4104@eagleswings>
 	<20030429220821.629e6364.moore@cs.utk.edu>
 	<16047.19059.264063.111036@thomasm-u1.cisco.com>
 	<E19Apr8-0009Pn-Bh@roam.psg.com>
 	<16047.54697.246635.743458@thomasm-u1.cisco.com>
 	<20030430100320.54070e48.moore@cs.utk.edu>
 <16047.55553.121243.531738@thomasm-u1.cisco.com>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Wednesday, 30 April, 2003 07:09 -0700 Michael Thomas 
<mat@cisco.com> wrote:

> Keith Moore writes:
>  > > Well, the pragmatic reality is to avoid using IP
>  > > addresses as substitutes for endpoint
>  > > identitifiers. Or maybe that's not pragmatic, but
>  > > tough noogies; using IP addresses as endpoint
>  > > identifiers is sloppy and generally a bad idea.
>  >
>  > ...and at this point the argument repeats, without your
> having acquired  > any additional clue.
>
> Maybe if you and Randy stopped playing elliptical
> word games we could have some communication
> here. If you have a point, make it.

Mike,

I disagree that they are playing word games.  But let me try a 
different approach to the issue, partially to try to explain to 
you, at a bit more length, what I think they are talking about.

One of the key issues in this discussion has been whether it is 
reasonable to remove a previously-defined and standardized 
feature, especially one that has been widely deployed for some 
time, without strong justification.  I think there is fairly 
wide agreement that is a bad idea, even if reasonable people 
might disagree as to which of those considerations apply to SL 
and to what degree.

Now, like it or not, we have a number of widely-distributed 
applications and other things, including some security 
protocols, that use IP addresses as endpoint identifiers.  They 
do that, in part, because there is no more satisfactory 
candidate for an endpoint identifier.  Certainly DNS names, with 
the current definition of the DNS, do not qualify as a 
satisfactory alternative and the number of standards-track 
alternatives that have received even moderate acceptance is, 
well, very small.   Comparatively speaking, the number of 
network-seconds (or almost any other plausible measure you can 
think of) consumed by the collection of applications and other 
things that use IP addresses as endpoint identifiers 
significantly exceeds the number of network-seconds used for 
either referencing IPv6 addresses or using other types of 
standardized endpoint identifiers... keep in mind that, from at 
least one perspective on the situation, TCP is one of those 
things that uses IP addresses as endpoint identifiers.

And, of course it is trivial to make up names, and maybe even to 
pass them around.  But there is quite a difference between that 
statement and a protocol that really uses such names as endpoint 
identifiers, carefully defines what those names are bound to and 
how and when they are unbound or refreshed, how they are exposed 
to the routing infrastructure without unacceptable layering 
violations, etc.  Try doing some serious I-D writing and working 
through of the cases and transition issues.

So...

(i) If you want to get rid of the use of IP addresses as 
endpoint identifiers, let's see an I-D that describes a 
reasonable alternative, and how to get there from there, 
processed along the standards track.  Asserting that IP 
addresses are not very good endpoint identifiers is not 
especially useful -- almost everyone agrees with you, but many 
of us are concerned about an operational network, and not, when 
it conflicts, philosophy.

(ii) Don't bother arguing that SL should be retained because it 
is standardized and entrenched and then turn around and argue 
for getting rid of IP addresses as endpoint identifiers without 
recognizing that usage are even more standardized and entrenched.

I continue to believe that there are serious and significant 
architectural issues underlying this discussion, ones that we, 
as a community, need to address and address soon.  But, IMnvHO, 
complaining about those nasty applications that use IP addresses 
in ways that are, retrospectively, problematic is not only not a 
solution to the problems, but adds a lot of noise that gets in 
the way of looking at the architectural issues.

We now return you to your regularly-scheduled word games, 
sniping, name-calling, hyperbole, and flights of fancy :-(

     john




From owner-ietf@ietf.org  Wed Apr 30 12:54:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11625;
	Wed, 30 Apr 2003 12:54:14 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Auba-0001wg-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 12:38:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AuXG-0001s6-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 12:34:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10931
	for <ietf@ietf.org>; Wed, 30 Apr 2003 12:31:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AuWG-00014T-00
	for ietf@ietf.org; Wed, 30 Apr 2003 12:33:20 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AuWF-00014Q-00
	for ietf@ietf.org; Wed, 30 Apr 2003 12:33:19 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3UGXeL17024;
	Wed, 30 Apr 2003 11:33:40 -0500
Message-ID: <005a01c30f36$435dd7a0$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Keith Moore" <moore@cs.utk.edu>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>
Cc: <moore@cs.utk.edu>, <pdeutsch@earthlink.net>, <ipng@sunroof.eng.sun.com>,
        <ietf@ietf.org>
References: <3EAEFFA7.63A14F72@earthlink.com><E88632EC-7AE1-11D7-A65D-00039388672E@muada.com> <20030430113037.5ffa287c.moore@cs.utk.edu>
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
Date: Wed, 30 Apr 2003 11:20:14 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Keith Moore" <moore@cs.utk.edu>
> > Today, dial-up concentrators usually have an address
> > range that it used to assign addresses to people that dial in. That
> > means at most a handful of routes per dial-up concentrator in the
> > interior routing protocol. If everyone has their own /48, that means
> > a route in the IGP for each customer that's online. There are no
> > hard and fast rules about how many routes you can have in an
> > IGP, but somewhere between 10k and 1M you run into trouble.
>
> this is an interesting point, but I think it has more to do with whether
> the prefixes are statically bound to customers than the length of those
> prefixes.  why would  giving customers static /64s result in fewer
> routes in your IGP than giving them static /48s?   in neither case is
> there a direct correspondence between the customer's address and
> the concentrator.

IMHO, dialup is a bad example because static IPs per customer are rare;
let's switch to the cable/dsl market.

Standard practice is to connect all customers in a given area (or signed up
in a given period) to a single concentrator via some sort of virtual circuit
(PPPoE, ATM, FR, etc).  This concentrator then internally bridges all of
these virtual circuits into a single subnet with a single prefix, giving you
one route for N customers.  OTOH, if you assign a prefix to each customer,
you then have between N+1 and 2N routes for N customers.  The latter might
be justified if we're truly committed to eliminating NATs, but it costs a
lot more in routes, in administration, and in address waste (assigning a /48
to what is, in nearly all cases, 1-4 hosts).

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Wed Apr 30 12:59:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12012;
	Wed, 30 Apr 2003 12:59:19 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Aup7-0002AL-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 12:52:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Augz-0001yn-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 12:44:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11253
	for <ietf@ietf.org>; Wed, 30 Apr 2003 12:41:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aufz-00019j-00
	for ietf@ietf.org; Wed, 30 Apr 2003 12:43:23 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aufz-00019g-00
	for ietf@ietf.org; Wed, 30 Apr 2003 12:43:23 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26BBC> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 30 Apr 2003 09:43:55 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Michael Thomas'" <mat@cisco.com>, "'Randy Bush'" <randy@psg.com>
Cc: "'Keith Moore'" <moore@cs.utk.edu>, <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: site-local != NAT
Date: Wed, 30 Apr 2003 09:44:08 -0700
Message-ID: <07c801c30f37$b859d9e0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <16047.57167.821886.158969@thomasm-u1.cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA12012

Michael Thomas wrote:
> Randy Bush writes:
>  > > Maybe if you and Randy stopped playing elliptical
>  > > word games we could have some communication
>  > > here. If you have a point, make it.
>  > 
>  > keith did.  it's just that you didn't like it.
>  > 
>  > the reality is that today, identifiers are addresses are 
> routing.  > we may or may not like this, but it is fact.
> 
> Fine. The reality is NAT and RFC1918 too. That
> doesn't mean that we should just give up. And
> unlike the intractable set of problems that drive
> NAT's, it's trivial to djinn up collision
> resistant names which can be used in lieu of the
> abdication of thought implicit in recvfrom() as
> the Bearer of Names. Diffie Hellman is your
> friend.

What many are missing here is that this is not about 1918 style
addressing. This is about the fact that addresses do not have the same
visibility and accessibility throughout the network. This operational
reality causes the affect we have labeled scoping. 

Many on this list 'don't like' to acknowledge that scoping exists in the
network, and some claim that the network has failed because it doesn't
support a global flat routing space. We should not be focused on likes &
dislikes (as some recent voting has done), we are here to do
engineering. Shooting the messenger does not solve the problem.

The network has always had the operational capability to limit where any
particular address is accessible from. This coupled with the application
shortcut that an interface topology locator equals an endpoint
identifier has been the reason that supporting multihomed nodes has been
difficult. With the rollout of IPv6, every node becomes multihomed (in
this context that means the node actually has multiple topology locators
simultaneously). The debate over the last few months on the IPv6 list
has been about trying to restrict any given node to having addresses of
a single scope. This attempt to force an operational model that doesn't
exist in the network today, simply to preserve an invalid (granted
longstanding, but still invalid) assumption that any address can be used
equally throughout the network, has met with resistance from the
operators of the edge networks.

Our task is to look at the overall system the way that network managers
really run (or want to run) it, then figure out what it will take to
make that happen. The first thing one will realize is that any process
that passes an address outside its scope of relevance as defined by the
local network manager is not working to achieve that goal. One class of
processes that do this today are name to address resolution services,
another class are multi-party apps that pass a topology locator rather
than an label that can be turned into a topology appropriate locator. 

At the same time we are working on making the system work the way
network managers want to run it, we need to find ways to keep the
applications as simple as possible. The combination of those will likely
result in a more complex infrastructure than we have today, but no more
complex than it should have been for the last 15 years.

I don't know what a solution looks like, but I do know that continuing
to bury our collective head in a dark place will not make the problem
that needs solving go away. 

Tony







From owner-ietf@ietf.org  Wed Apr 30 13:00:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12184;
	Wed, 30 Apr 2003 13:00:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Aup8-0002Ac-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 12:52:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Auit-0001yr-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 12:46:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11330
	for <ietf@ietf.org>; Wed, 30 Apr 2003 12:43:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Auht-0001Ap-00
	for ietf@ietf.org; Wed, 30 Apr 2003 12:45:21 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Auhs-0001Ad-00
	for ietf@ietf.org; Wed, 30 Apr 2003 12:45:20 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h3UGj8Lr017664;
	Wed, 30 Apr 2003 09:45:08 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id ADS07588;
	Wed, 30 Apr 2003 09:45:06 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id JAA12587; Wed, 30 Apr 2003 09:45:06 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16047.64914.599665.968428@thomasm-u1.cisco.com>
Date: Wed, 30 Apr 2003 09:45:06 -0700 (PDT)
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: "Keith Moore" <moore@cs.utk.edu>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>, <pdeutsch@earthlink.net>,
        <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
In-Reply-To: <005a01c30f36$435dd7a0$93b58742@ssprunk>
References: <3EAEFFA7.63A14F72@earthlink.com>
	<E88632EC-7AE1-11D7-A65D-00039388672E@muada.com>
	<20030430113037.5ffa287c.moore@cs.utk.edu>
	<005a01c30f36$435dd7a0$93b58742@ssprunk>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Stephen Sprunk writes:
 > Standard practice is to connect all customers in a given area (or signed up
 > in a given period) to a single concentrator via some sort of virtual circuit
 > (PPPoE, ATM, FR, etc).  This concentrator then internally bridges all of
 > these virtual circuits into a single subnet with a single prefix, giving you
 > one route for N customers.  OTOH, if you assign a prefix to each customer,
 > you then have between N+1 and 2N routes for N customers.  The latter might
 > be justified if we're truly committed to eliminating NATs, but it costs a
 > lot more in routes, in administration, and in address waste (assigning a /48
 > to what is, in nearly all cases, 1-4 hosts).

Huh? Why wouldn't these prefixes summarized at the
first hop router? And even the first hop router
needs to have routes to get to the last mile, so
whether you do it with an arp cache, SID binding,
or routing table seems like a rather minor
difference in kind.

	   Mike



From owner-ietf@ietf.org  Wed Apr 30 13:11:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12786;
	Wed, 30 Apr 2003 13:11:26 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Auzs-0003AE-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 13:03:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Aupd-0002Ag-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 12:53:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11494
	for <ietf@ietf.org>; Wed, 30 Apr 2003 12:50:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Auod-0001Cq-00
	for ietf@ietf.org; Wed, 30 Apr 2003 12:52:19 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Auoc-0001Cn-00
	for ietf@ietf.org; Wed, 30 Apr 2003 12:52:18 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.11.3/8.9.3) with ESMTP id h3UGqhE97548;
	Wed, 30 Apr 2003 18:52:44 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Wed, 30 Apr 2003 18:52:45 +0200
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "Keith Moore" <moore@cs.utk.edu>, <pdeutsch@earthlink.net>,
        <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
To: "Stephen Sprunk" <stephen@sprunk.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <005a01c30f36$435dd7a0$93b58742@ssprunk>
Message-Id: <2ABD03E6-7B2C-11D7-A65D-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, apr 30, 2003, at 18:20 Europe/Amsterdam, Stephen Sprunk 
wrote:

>> this is an interesting point, but I think it has more to do with 
>> whether
>> the prefixes are statically bound to customers than the length of 
>> those
>> prefixes.

Of course.

>> why would  giving customers static /64s result in fewer
>> routes in your IGP than giving them static /48s?

I was suggesting nothing of the sort; just assumed that _if_ you're 
going to give a customer something fixed it would be a /48 while a 
dynamic /48 doesn't make much sense the way things are now.

> IMHO, dialup is a bad example because static IPs per customer are rare;
> let's switch to the cable/dsl market.

> Standard practice is to connect all customers in a given area (or 
> signed up
> in a given period) to a single concentrator via some sort of virtual 
> circuit
> (PPPoE, ATM, FR, etc).  This concentrator then internally bridges all 
> of
> these virtual circuits into a single subnet with a single prefix, 
> giving you
> one route for N customers.

Ok, I'm not all that familiar with cable/ADSL, but isn't this more 
often done by giving each customer a virtual point to point link? In 
the case of PPP over ethernet I don't see how it could work otherwise. 
Now of course you can then proxy ARP...

> OTOH, if you assign a prefix to each customer,
> you then have between N+1 and 2N routes for N customers.

Unless you aggregate, of course. For cable/ADSL that shouldn't be a 
problem as the customers conveniently stay in the same place.  :-)  Not 
so with dial.

> The latter might
> be justified if we're truly committed to eliminating NATs, but it 
> costs a
> lot more in routes, in administration, and in address waste (assigning 
> a /48
> to what is, in nearly all cases, 1-4 hosts).

So we should give them a /126???

I guess a /64 would be enough for most people. You are underestimating 
the number of hosts, though: don't forget about IP phones, IP radios 
and stuff like that. And I'm not even counting more obscure examples 
such as IP refrigirators.




From owner-ietf@ietf.org  Wed Apr 30 13:12:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12866;
	Wed, 30 Apr 2003 13:12:09 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Auzs-0003AZ-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 13:03:56 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Auqb-0002Bm-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 12:54:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11539
	for <ietf@ietf.org>; Wed, 30 Apr 2003 12:51:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aupc-0001DP-00
	for ietf@ietf.org; Wed, 30 Apr 2003 12:53:20 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aupb-0001DM-00
	for ietf@ietf.org; Wed, 30 Apr 2003 12:53:19 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3UGrMv21915;
        Wed, 30 Apr 2003 12:53:23 -0400 (EDT)
Date: Wed, 30 Apr 2003 12:53:22 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: moore@cs.utk.edu, iljitsch@muada.com, pdeutsch@earthlink.net,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
Message-Id: <20030430125322.6b3e0bcd.moore@cs.utk.edu>
In-Reply-To: <005a01c30f36$435dd7a0$93b58742@ssprunk>
References: <3EAEFFA7.63A14F72@earthlink.com>
	<E88632EC-7AE1-11D7-A65D-00039388672E@muada.com>
	<20030430113037.5ffa287c.moore@cs.utk.edu>
	<005a01c30f36$435dd7a0$93b58742@ssprunk>
X-Mailer: Sylpheed version 0.8.11 (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

> > this is an interesting point, but I think it has more to do with
> > whether the prefixes are statically bound to customers than the
> > length of those prefixes.  why would  giving customers static /64s
> > result in fewer routes in your IGP than giving them static /48s?  
> > in neither case is there a direct correspondence between the
> > customer's address and the concentrator.
> 
> IMHO, dialup is a bad example because static IPs per customer are
> rare; let's switch to the cable/dsl market.

well, they might not be so rare in the IPv6 market, but whatever...

> Standard practice is to connect all customers in a given area (or
> signed up in a given period) to a single concentrator via some sort of
> virtual circuit(PPPoE, ATM, FR, etc).  This concentrator then
> internally bridges all of these virtual circuits into a single subnet
> with a single prefix, giving you one route for N customers.  OTOH, if
> you assign a prefix to each customer, you then have between N+1 and 2N
> routes for N customers.  

well, for cable at least, seems like you'd want to assign a prefix to
each concentrator and give each customer a /48 subnet out of the
concentrator that serves that location.  as I understand dsl it affords
more flexibility than that, since each customer can get a VC to a
concentrator which can essentially be anywhere, but you'd still want
to assign an appropriate-sized prefix to the concentrator and dole /48
subnets out of that.  either way you get to do route aggregation at the
concentrator.

I suspect a lot of "standard practice" for IPv4 is designed to conserve
address space; it's not clear that such practices are either desirable
or optimal for IPv6.  more generally, IPv6 is going to be driven by 
different markets, different applications, and a different set of
customer demands than IPv4.  so anytime you find yourself thinking that 
"standard practice" (meaning v4 practice) axiomatically applies to IPv6,
it might be worth re-examining the assumptions behind that practice.

Keith



From owner-ietf@ietf.org  Wed Apr 30 13:31:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13610;
	Wed, 30 Apr 2003 13:31:43 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AvEX-0004LG-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 13:19:05 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Av3G-0003SO-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 13:07:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12528
	for <ietf@ietf.org>; Wed, 30 Apr 2003 13:04:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Av2G-0001TQ-00
	for ietf@ietf.org; Wed, 30 Apr 2003 13:06:24 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Av2F-0001TN-00
	for ietf@ietf.org; Wed, 30 Apr 2003 13:06:23 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3UH4Wv21951;
        Wed, 30 Apr 2003 13:04:35 -0400 (EDT)
Date: Wed, 30 Apr 2003 13:04:32 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, mat@cisco.com, randy@psg.com, cos@aaaaa.org,
        ietf@ietf.org
Subject: Re: site-local != NAT
Message-Id: <20030430130432.2397ba40.moore@cs.utk.edu>
In-Reply-To: <07c801c30f37$b859d9e0$261e4104@eagleswings>
References: <16047.57167.821886.158969@thomasm-u1.cisco.com>
	<07c801c30f37$b859d9e0$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (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

> What many are missing here is that this is not about 1918 style
> addressing. This is about the fact that addresses do not have the same
> visibility and accessibility throughout the network.

no, it's not just about that.  you are the only one who keeps insisting
that.  you seem to be trying to conflate two different notions of scope.
IMHO it's clearer if you talk about those kinds of scope in separate
terms; which is why I prefer to talk about ambiguous addresses on one
hand vs. packet filtering on the other.   It happens that SLs combine
the two, but there's no inherent need to do so.

> Our task is to look at the overall system the way that network
> managers really run (or want to run) it, then figure out what it will
> take to make that happen. 

funny, I thought our primary task was to design a network that could
support useful applications.   of course, managability is an important
aspect of being able to support useful applications, but it is not
reasonable to constrain the v6 network design to only permit things that
are compatible with network managers' assumptions about how to operate
v4 networks.  v6 is more different than v4 than most people realize.

so no, I don't accept your definition of "our task"; in fact I
fundamentally disagree with it as stated. 

> I don't know what a solution looks like, but I do know that continuing
> to bury our collective head in a dark place will not make the problem
> that needs solving go away. 

And as long as that's the way you characterize users and applications
writers with genuine needs, you're not going to be able to contribute
to solving the problem.



From owner-ietf@ietf.org  Wed Apr 30 13:43:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14212;
	Wed, 30 Apr 2003 13:43:40 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AvEY-0004Lr-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 13:19:06 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Av4P-0003Se-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 13:08:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12604
	for <ietf@ietf.org>; Wed, 30 Apr 2003 13:05:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Av3P-0001Uk-00
	for ietf@ietf.org; Wed, 30 Apr 2003 13:07:35 -0400
Received: from garlic.amaranth.net ([208.254.46.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Av3O-0001Uf-00
	for ietf@ietf.org; Wed, 30 Apr 2003 13:07:34 -0400
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226])
	(authenticated (0 bits))
	by garlic.amaranth.net (8.11.7/8.11.7) with ESMTP id h3UH8B830318
	(using TLSv1/SSLv3 with cipher RC4-SHA (128 bits) verified NO);
	Wed, 30 Apr 2003 13:08:12 -0400
Message-Id: <5.2.1.1.2.20030430130312.01b8db28@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Wed, 30 Apr 2003 13:07:01 -0400
To: "Stephen Sprunk" <stephen@sprunk.org>
From: Daniel Senie <dts@senie.com>
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple
  Question)
Cc: <ietf@ietf.org>
In-Reply-To: <005a01c30f36$435dd7a0$93b58742@ssprunk>
References: <3EAEFFA7.63A14F72@earthlink.com>
 <E88632EC-7AE1-11D7-A65D-00039388672E@muada.com>
 <20030430113037.5ffa287c.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:20 PM 4/30/2003, Stephen Sprunk wrote:
>Thus spake "Keith Moore" <moore@cs.utk.edu>
> > > Today, dial-up concentrators usually have an address
> > > range that it used to assign addresses to people that dial in. That
> > > means at most a handful of routes per dial-up concentrator in the
> > > interior routing protocol. If everyone has their own /48, that means
> > > a route in the IGP for each customer that's online. There are no
> > > hard and fast rules about how many routes you can have in an
> > > IGP, but somewhere between 10k and 1M you run into trouble.
> >
> > this is an interesting point, but I think it has more to do with whether
> > the prefixes are statically bound to customers than the length of those
> > prefixes.  why would  giving customers static /64s result in fewer
> > routes in your IGP than giving them static /48s?   in neither case is
> > there a direct correspondence between the customer's address and
> > the concentrator.
>
>IMHO, dialup is a bad example because static IPs per customer are rare;
>let's switch to the cable/dsl market.
>
>Standard practice is to connect all customers in a given area (or signed up
>in a given period) to a single concentrator via some sort of virtual circuit
>(PPPoE, ATM, FR, etc).  This concentrator then internally bridges all of
>these virtual circuits into a single subnet with a single prefix, giving you
>one route for N customers.  OTOH, if you assign a prefix to each customer,
>you then have between N+1 and 2N routes for N customers.  The latter might
>be justified if we're truly committed to eliminating NATs, but it costs a
>lot more in routes, in administration, and in address waste (assigning a /48
>to what is, in nearly all cases, 1-4 hosts).

If standard practice is to give everyone a /48, then the routing decision 
at the access concentrator could be programmed to deal with this, ignore 
the low order bits, and send the packets on to the proper customer. Given 
the decision to "waste" the low order bits on MAC address or other locally 
defined values, there's no value in an access concentrator worrying about 
that part of the address. The residential gateway would worry about it. 
Sounds more than a bit like ISDN sub addresses, where the sub address is 
only of interest to the CPE. Seems like a small matter of programming, not 
a reason to load up routing tables. 




From owner-ietf@ietf.org  Wed Apr 30 13:55:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14801;
	Wed, 30 Apr 2003 13:55:59 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AvhL-0005nR-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 13:48:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Avh7-0005iu-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 13:48:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14363
	for <ietf@ietf.org>; Wed, 30 Apr 2003 13:45:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Avg7-0001wL-00
	for ietf@ietf.org; Wed, 30 Apr 2003 13:47:35 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Avg6-0001vo-00
	for ietf@ietf.org; Wed, 30 Apr 2003 13:47:34 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26BDC> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 30 Apr 2003 10:47:57 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: <mat@cisco.com>, <randy@psg.com>, <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: site-local != NAT
Date: Wed, 30 Apr 2003 10:48:14 -0700
Message-ID: <07d401c30f40$ae7b0fd0$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030430130432.2397ba40.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA14801

Keith Moore wrote:
> > What many are missing here is that this is not about 1918 style 
> > addressing. This is about the fact that addresses do not 
> have the same 
> > visibility and accessibility throughout the network.
> 
> no, it's not just about that.  you are the only one who keeps 
> insisting that.  you seem to be trying to conflate two 
> different notions of scope. IMHO it's clearer if you talk 
> about those kinds of scope in separate terms; which is why I 
> prefer to talk about ambiguous addresses on one
> hand vs. packet filtering on the other.   It happens that SLs combine
> the two, but there's no inherent need to do so.

There were several proposals to remove the ambiguity in the current SL,
so continued dislike of them shows that is not the underlying issue. The
real issue is that highlighting different reachability perspectives in
different parts of the network has exposed invalid assumptions. On top
of that, scoping is about more than packet filtering, scoping happens
simply by filtering out some topology information in the routing
protocols. I agree we need to be clear about terms, but continuing to
mix ambiguity with scoping is not getting us there. 

> 
> > Our task is to look at the overall system the way that network 
> > managers really run (or want to run) it, then figure out 
> what it will 
> > take to make that happen.
> 
> funny, I thought our primary task was to design a network that could
> support useful applications.  

No that is the network managers task. One could argue that many of the
problems in making progress in the IETF are about this confusing of
roles. 

>  of course, managability is an important
> aspect of being able to support useful applications, but it 
> is not reasonable to constrain the v6 network design to only 
> permit things that are compatible with network managers' 
> assumptions about how to operate v4 networks.  

Network managers don't assume, they define how the network operates. The
IETF is the one that assumes they can dictate ...

> v6 is more different than v4 than most people realize.

I would argue that it simply takes advantage of many of the latent
capabilities that already exist in IPv4.

> 
> so no, I don't accept your definition of "our task"; in fact 
> I fundamentally disagree with it as stated. 

I understand that, but that doesn't change the reality that the IETF is
not in the business of designing networks. The IETF is in the business
of defining the standards that allow the network manager to acquire the
tools to accomplish his role as the network designer. 

> 
> > I don't know what a solution looks like, but I do know that 
> continuing 
> > to bury our collective head in a dark place will not make 
> the problem 
> > that needs solving go away.
> 
> And as long as that's the way you characterize users and 
> applications writers with genuine needs, you're not going to 
> be able to contribute to solving the problem.
> 

How else does one characterize the explicit refusal to deal with a known
problem for 15+ years?

Tony





From owner-ietf@ietf.org  Wed Apr 30 14:24:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15834;
	Wed, 30 Apr 2003 14:24:15 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Avvs-0006IP-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 14:03:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AvrJ-0005ry-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 13:59:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14796
	for <ietf@ietf.org>; Wed, 30 Apr 2003 13:55:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AvqI-000221-00
	for ietf@ietf.org; Wed, 30 Apr 2003 13:58:06 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AvqH-00021t-00
	for ietf@ietf.org; Wed, 30 Apr 2003 13:58:05 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3UHwWv22127;
        Wed, 30 Apr 2003 13:58:34 -0400 (EDT)
Date: Wed, 30 Apr 2003 13:58:32 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <john-ietf@jck.com>
Cc: moore@cs.utk.edu, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: My thoughts on local-use addresses
Message-Id: <20030430135832.1a645f93.moore@cs.utk.edu>
In-Reply-To: <13367010.1051372503@p3.JCK.COM>
References: <20030426060420.GA93218@lethargic.dyndns.org>
	<20030426164255.GA98043@lethargic.dyndns.org>
	<20030426130211.321b0a4d.moore@cs.utk.edu>
	<13367010.1051372503@p3.JCK.COM>
X-Mailer: Sylpheed version 0.8.11 (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

> > we need to get rid of site-locals.  merely renaming them as
> > private use addresses wouldn't solve any of their problems.
> > there's no advantage to moving to IPv6 if it repeats the RFC
> > 1918 mistake.

> Hyperbole does not serve either the community, or one's own 
> position, well in this situation or others like it. 

John,

If I understand what you are calling hyperbole I would instead call it
the 10,000 meter view.  That is, I don't see a significant market for
IPv6 if it doesn't support applications that cannot be run on NATted
IPv4.  Yes, there may still be some small advantage of IPv6 for some
groups of users if this doesn't happen, but not for the Internet
community as a whole.   So "no advantage" can be taken as an
exaggeration, but the intent was to avoid getting bogged down in
detail about exactly what minor advantages there might be and why
they're unlikely to create enough incentive for any widespread adoption
of IPv6.

And no, I don't think that reducing the number of NATs by 25-50% would
create a significant advantage to moving to IPv6.  In order to create a
significant advantage, there need to be so few NATs in IPv6 that
application developers can write applications that will fail in the
presence of NATs without fear of losing a significant number of
customers.

I agree that there's a requirement for PI addresses, and perhaps, for PI
addresses that don't require RIR allocation.  Various solutions have
been proposed, but we seem to be unable to evaluate them or choose
between them because we're too busy arguing about whether the v6 network
should be saddled with the baggage from v4.  

The discussion about SL also seems to be couched in those terms, as well
as being confused by efforts to conflate different notions of scope that
are better understood separately.  IMHO, those who think that hosts or
apps should have to bear the burden of picking which address or
interface to use in order to get packets to their destination need to
explain (a) where the hosts or apps get the information necessary to
make those choices in a reliable and timely fashion, and probably (b)
how to provide a usable endpoint identifier under those conditions that
can be passed between hosts at arbitrary locations.  Until then, I'm not
convinced that the v6 assumptions about multihoming are workable.  Which
further leads me to conclude that we still haven't figured out a way to
make IP routing scale in a practical sense.

Keith



From owner-ietf@ietf.org  Wed Apr 30 14:27:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16029;
	Wed, 30 Apr 2003 14:27:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AwFb-00079x-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 14:24:15 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Aw6E-0006pC-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 14:14:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15517
	for <ietf@ietf.org>; Wed, 30 Apr 2003 14:11:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aw59-0002Bz-00
	for ietf@ietf.org; Wed, 30 Apr 2003 14:13:27 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aw58-0002Bw-00
	for ietf@ietf.org; Wed, 30 Apr 2003 14:13:26 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3UIBRv22173;
        Wed, 30 Apr 2003 14:11:28 -0400 (EDT)
Date: Wed, 30 Apr 2003 14:11:27 -0400
From: Keith Moore <moore@cs.utk.edu>
To: <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, mat@cisco.com, randy@psg.com, cos@aaaaa.org,
        ietf@ietf.org
Subject: Re: site-local != NAT
Message-Id: <20030430141127.0458de69.moore@cs.utk.edu>
In-Reply-To: <07d401c30f40$ae7b0fd0$261e4104@eagleswings>
References: <20030430130432.2397ba40.moore@cs.utk.edu>
	<07d401c30f40$ae7b0fd0$261e4104@eagleswings>
X-Mailer: Sylpheed version 0.8.11 (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

> There were several proposals to remove the ambiguity in the current
> SL, so continued dislike of them shows that is not the underlying
> issue. 

I don't think this conclusion is valid.  What I am certain of is that
our ability to evaluate the subtle differences between these proposals,
and the advantages and disadvantages of each, is compromised by a
widespread failure to respect the diversity of experiences and the
diversity of users' legitimate needs.  Under such circumstances, people
are forced to shoot down half-baked ideas, just as a means of damage
control, rather than trying to refine them.

As a result, I don't think any of the various proposals for unique
non-PA addresses have received adequate scrutiny.

> > > Our task is to look at the overall system the way that network 
> > > managers really run (or want to run) it, then figure out 
> > > what it will take to make that happen.
> > 
> > funny, I thought our primary task was to design a network that could
> > support useful applications.  
> 
> No that is the network managers task. One could argue that many of the
> problems in making progress in the IETF are about this confusing of
> roles. 

Network managers don't design IP protocols, nor do they implement IP
stacks or routers.  If the protocols we design don't support what users
need from the Internet, there's nothing a network manager can do to fix
this. 

Keith



From owner-ietf@ietf.org  Wed Apr 30 14:45:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16771;
	Wed, 30 Apr 2003 14:45:32 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AwOx-00082k-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 14:33:55 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AwKH-0007c3-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 14:29:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15986
	for <ietf@ietf.org>; Wed, 30 Apr 2003 14:25:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AwJG-0002M8-00
	for ietf@ietf.org; Wed, 30 Apr 2003 14:28:03 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AwJF-0002LF-00
	for ietf@ietf.org; Wed, 30 Apr 2003 14:28:02 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h3UIS5xK027074;
	Wed, 30 Apr 2003 11:28:07 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id ADS21769;
	Wed, 30 Apr 2003 11:28:05 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA13127; Wed, 30 Apr 2003 11:28:05 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16048.5557.124583.930323@thomasm-u1.cisco.com>
Date: Wed, 30 Apr 2003 11:28:05 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: John C Klensin <john-ietf@jck.com>, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: My thoughts on local-use addresses
In-Reply-To: <20030430135832.1a645f93.moore@cs.utk.edu>
References: <20030426060420.GA93218@lethargic.dyndns.org>
	<20030426164255.GA98043@lethargic.dyndns.org>
	<20030426130211.321b0a4d.moore@cs.utk.edu>
	<13367010.1051372503@p3.JCK.COM>
	<20030430135832.1a645f93.moore@cs.utk.edu>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore writes:
 > The discussion about SL also seems to be couched in those terms, as well
 > as being confused by efforts to conflate different notions of scope that
 > are better understood separately.  IMHO, those who think that hosts or
 > apps should have to bear the burden of picking which address or
 > interface to use in order to get packets to their destination need to
 > explain (a) where the hosts or apps get the information necessary to
 > make those choices in a reliable and timely fashion, and probably (b)
 > how to provide a usable endpoint identifier under those conditions that
 > can be passed between hosts at arbitrary locations.  Until then, I'm not
 > convinced that the v6 assumptions about multihoming are workable.  Which
 > further leads me to conclude that we still haven't figured out a way to
 > make IP routing scale in a practical sense.

It seems to me that what needs to be answered
first is whether we are already resigned to
dealing with that problem with mobility,
renumbering, and multihoming. There's good reason
to want to use a local prefix rather than mobile
IP for new communiation if possible since it more
cleanly eliminates the dog leg through the home
agent. Likewise, there's pretty good reason to
want to renumber. Neither of these have a very
strong policy component though: the host wants to
do this for efficiency and/or continued
communication. So I'd say that there's pretty good
motivation for hosts to want to at the very least
deal with more than one globally routable address.

Multihoming is similar, obviously, but also
introduces an element of policy to the discussion:
it would be nice to prefer one path over others;
having -- somehow -- hosts know the policy would
be one way to achieve that. Have we just gone to
hell in a hand basket? This strikes me as part of
what is getting discussed with site-locals. Is
selection based upon policy -- and hence knowing
finer grained properties of IP prefixes -- the
road to hell? It sure seems to drag a lot more
baggage into the discussion than with the mobility
and renumbering problems when you start talking
about policy. Keeping prefix knowledge on hosts
opaque would certainly be one way to draw a line
in the sand. This has implications with both
site-locals (bad) and multihoming (policy-based
selection bad).

		Mike



From owner-ietf@ietf.org  Wed Apr 30 15:21:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21053;
	Wed, 30 Apr 2003 15:21:59 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Awx4-00059A-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 15:09:10 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Awr9-0001rF-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 15:03:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19217
	for <ietf@ietf.org>; Wed, 30 Apr 2003 14:59:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Awq3-0002ga-00
	for ietf@ietf.org; Wed, 30 Apr 2003 15:01:55 -0400
Received: from unknown-1-11.windriver.com ([147.11.1.11] helo=mail.wrs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Awq2-0002gW-00
	for ietf@ietf.org; Wed, 30 Apr 2003 15:01:54 -0400
Received: from IDLEWYLDE.windriver.com ([147.11.13.160])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id MAA02299;
	Wed, 30 Apr 2003 12:00:54 -0700 (PDT)
Message-Id: <5.1.0.14.2.20030430141234.044bae28@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 30 Apr 2003 14:28:16 -0400
To: <alh-ietf@tndh.net>
From: Margaret Wasserman <mrw@windriver.com>
Subject: RE: site-local != NAT
Cc: "'Michael Thomas'" <mat@cisco.com>, "'Randy Bush'" <randy@psg.com>,
        "'Keith Moore'" <moore@cs.utk.edu>, <cos@aaaaa.org>, <ietf@ietf.org>
In-Reply-To: <07c801c30f37$b859d9e0$261e4104@eagleswings>
References: <16047.57167.821886.158969@thomasm-u1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk


Hi Tony,

At 09:44 AM 4/30/2003 -0700, Tony Hain wrote:
>What many are missing here is that this is not about 1918 style
>addressing. This is about the fact that addresses do not have the same
>visibility and accessibility throughout the network. This operational
>reality causes the affect we have labeled scoping.

There are three ways in which a particular address can be non-global:

         - Unreachable:  The address can be unreachable from some
                 portions of the network (due to filtering, network
                 failures, etc.).

         - Not Globally Routed:  There can be no route to the address
                 from some portions of the network.

         - Not Globally Unique (AKA Ambiguous): A single address can
                 indicate one node when it is used in one part of
                 the network, and a different node when it is used
                 in other parts of the

It is an inevitable fact of physics that some addresses will be
unreachable from some parts of the network.  The widespread
use of filtering/firewalls makes this both intentional and common.
Applications must deal with this (either well or badly), because
there is no other choice.

If the only way to get a globally routable address is to get it
from your provider, people may choose to use addresses that are
not globally routed for some purposes, such as convenience or
provider-independence.

I have not heard any compelling operational requirement for
ambiguous addresses in IPv6.

The IPv6 scoped addressing architecture defines addresses that
have all three of these properties, and this is what I hear when
you say "scoped addressing".  There could be types of local
addressing, though, that don't have all of these properties.

If you are using the term "scoped" addressing to refer to
something other than the type of addressing defined in the
IPv6 scoped addressing architecture, could you define your
term?

Thanks,
Margaret

P.S. There were some proposals to remove (or lessen the
likelihood of) ambiguous site-local addresses, but none of
those proposals removed the restrictions from the IPv6 scoped
addressing architecture that are only required because addresses
are ambiguous (sites can't be nested or overlap, zone IDs are
needed to disambiguate, etc.).








From owner-ietf@ietf.org  Wed Apr 30 15:26:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21350;
	Wed, 30 Apr 2003 15:26:27 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Ax7m-00087n-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 15:20:14 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Awxl-0005JM-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 15:09:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19649
	for <ietf@ietf.org>; Wed, 30 Apr 2003 15:06:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Awwk-0002j4-00
	for ietf@ietf.org; Wed, 30 Apr 2003 15:08:50 -0400
Received: from thwip.polyamory.org ([192.31.227.220])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Awwk-0002j1-00
	for ietf@ietf.org; Wed, 30 Apr 2003 15:08:50 -0400
Received: by thwip.polyamory.org (Postfix, from userid 1002)
	id 51DF912E97; Wed, 30 Apr 2003 15:09:23 -0400 (EDT)
Date: Wed, 30 Apr 2003 15:09:22 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: ietf@ietf.org
Cc: alh-ietf@tndh.net
Subject: what the "scope" disagreement is about
Message-ID: <20030430150922.F574@thwip.polyamory.org>
References: <16047.57167.821886.158969@thomasm-u1.cisco.com> <07c801c30f37$b859d9e0$261e4104@eagleswings> <20030430130432.2397ba40.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20030430130432.2397ba40.moore@cs.utk.edu>; from moore@cs.utk.edu on Wed, Apr 30, 2003 at 01:04:32PM -0400
Organization: American Association Against Acronym Abuse
Sender: owner-ietf@ietf.org
Precedence: bulk

Keith Moore <moore@cs.utk.edu> wrote:
> [Tony Hain writes:]
> > What many are missing here is that this is not about 1918 style
> > addressing. This is about the fact that addresses do not have the same
> > visibility and accessibility throughout the network.
> 
> no, it's not just about that.  you are the only one who keeps insisting
> that.  you seem to be trying to conflate two different notions of scope.

For what it's worth, I've been watching this discussion for a while,
not as a proponent of any particular side, and I completely agree with
Keith on this point.  I've seen Tony Hain repeatedly make the assertion
that this discussion is about the fact that not all addresses can be
reached from everywhere, or that we don't have a "flat routing space",
or any number of related restatements... but I have seen nothing other
than Tony's assertions that would make me think this dicussion is
about any of those things.  It puzzles me that he keeps repeating them.

Tony, *why* do you think this discussion is about reachability?

Everyone else: Do any of you believe that's what this is about, aside
  from Tony's assertions and peoples responses to those assertions?

From what I have seen, those who think "local scope" is harmful, are
concerned about the ambuity of addresses, as Keith says here again.
They are NOT concerned about the fact that a given address may not be
reachable from some places, or may be reachable via different routes
from different places.  Or, rather, whether they're concerned about
that or not, it has nothing to do with their objections to locally
scoped addresses.  All of their objections to locally scoped addresses
seem to be about the fact that the addresses are ambiguous, not unique.
They have no objections to globally unique addresses that remain
"local" as far as routing and reachability.

  --  Cos (Ofer Inbar)  --  cos@polyamory.org http://cos.polyamory.org/
  --  WBRS (100.1 FM)   --      info@wbrs.org http://www.wbrs.org/
  Romkey's Law: all unanimous decisions are wrong.  Proof: "They can't ALL
   be right.  So if they're all saying the same thing, it must be wrong."



From owner-ietf@ietf.org  Wed Apr 30 15:27:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21451;
	Wed, 30 Apr 2003 15:27:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AxEz-0000pV-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 15:27:41 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Ax6b-0007pV-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 15:19:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20673
	for <ietf@ietf.org>; Wed, 30 Apr 2003 15:15:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ax5a-0002oa-00
	for ietf@ietf.org; Wed, 30 Apr 2003 15:17:58 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ax5Z-0002oV-00
	for ietf@ietf.org; Wed, 30 Apr 2003 15:17:57 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3UJGmv22369;
        Wed, 30 Apr 2003 15:16:48 -0400 (EDT)
Date: Wed, 30 Apr 2003 15:16:48 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Michael Thomas <mat@cisco.com>
Cc: moore@cs.utk.edu, john-ietf@jck.com, ipng@sunroof.eng.sun.com,
        ietf@ietf.org
Subject: Re: My thoughts on local-use addresses
Message-Id: <20030430151648.3c3d352e.moore@cs.utk.edu>
In-Reply-To: <16048.5557.124583.930323@thomasm-u1.cisco.com>
References: <20030426060420.GA93218@lethargic.dyndns.org>
	<20030426164255.GA98043@lethargic.dyndns.org>
	<20030426130211.321b0a4d.moore@cs.utk.edu>
	<13367010.1051372503@p3.JCK.COM>
	<20030430135832.1a645f93.moore@cs.utk.edu>
	<16048.5557.124583.930323@thomasm-u1.cisco.com>
X-Mailer: Sylpheed version 0.8.11 (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

>  > IMHO, those who think
>  > that hosts or apps should have to bear the burden of picking which
>  > address or interface to use in order to get packets to their
>  > destination need to explain (a) where the hosts or apps get the
>  > information necessary to make those choices in a reliable and
>  > timely fashion, and probably (b) how to provide a usable endpoint
>  > identifier under those conditions that can be passed between hosts
>  > at arbitrary locations. 
> 
> It seems to me that what needs to be answered first is whether we are
> already resigned to dealing with that problem with mobility,
> renumbering, and multihoming. 

If we're resigned to dealing with an intractable problem, maybe we need
to rethink that assumption.  But it's not clear that either mobility or
renumbering presents the same kind of challenge.  In the case of
mobility I think it's fairly simple to decide whether to use a home or
in-care-of address as the source address, and this can be dictated by
the application.  In the case of renumbering then both old and new
prefixes should be valid for a considerable overlap period, which would
make the choice less critical except for apps that maintain
associations for a very long time (say, for several weeks).  As for
"multihoming" - these days people mean different things when they say
that, so I can't tell for sure what you mean.  But I think the
assumption that having multiple prefixes for a site and advertising
multiple addresses for hosts through DNS will provide sufficient
redundancy in network access to that site, across all or most
applications, is dubious at best.

> There's good reason to want to use a
> local prefix rather than mobile IP for new communiation if possible
> since it more cleanly eliminates the dog leg through the home agent.

Taken in isolation, that's certainly true.  But it presumes several
things, one of which is that a sending host can tell which of several
prefixes is the best to use.  (or if not the best, which ones are more
likely to work well than others).  It's easy to construct cases where
it's possible for the sending host to do this; somewhat more difficult
to construct a convincing argument that this can be done in general.

For instance, I spent some time investigating an idea which I'll call
"relative addresses" - the idea being that if source and destination
absolute/global addresses share enough bits of a common prefix the
sending host can assume they're on the same network, it can substitute
that many bits of "relative address prefix" for the global prefixes in
those addresses, the local network will route the traffic to the same
destination, and the addresses don't need to change when the network's
global prefix changes.  The idea has some nice properties.  In
particular, this is an optimization between hosts and the network -
applications can use it explicitly if they wish, but they don't have to
be aware of it to benefit from it.  There's no need to advertise the
"relative addresses" in DNS or in referrals between apps because they
can automatically be inferred by hosts.  And it would even work well
in conjunction with mobile IP-like mechanisms for forwarding and/or
redirecting traffic to PI prefixes - since local traffic would bypass
such mechanisms completely.

However - at least in its current incarnation, it doesn't work if a
network has multiple prefixes that aren't available to the same set of
hosts.  In other words, just because a source and destination share *a*
common prefix doesn't mean that the conversion from absolute to relative
address is invertable - the substitution of a single common prefix
can create an address that is ambiguous even within the local site.
(But I'm still working on the idea...)

Ketih



From owner-ietf@ietf.org  Wed Apr 30 18:24:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27160;
	Wed, 30 Apr 2003 18:24:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AxeK-0002Au-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 15:53:52 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Axdo-00028E-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 15:53:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22098
	for <ietf@ietf.org>; Wed, 30 Apr 2003 15:50:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Axch-00036p-00
	for ietf@ietf.org; Wed, 30 Apr 2003 15:52:11 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Axch-00036m-00
	for ietf@ietf.org; Wed, 30 Apr 2003 15:52:11 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3UJqiv22528;
        Wed, 30 Apr 2003 15:52:44 -0400 (EDT)
Date: Wed, 30 Apr 2003 15:52:44 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Ofer Inbar <cos@aaaaa.org>
Cc: moore@cs.utk.edu, ietf@ietf.org, alh-ietf@tndh.net
Subject: Re: what the "scope" disagreement is about
Message-Id: <20030430155244.0f88a735.moore@cs.utk.edu>
In-Reply-To: <20030430150922.F574@thwip.polyamory.org>
References: <16047.57167.821886.158969@thomasm-u1.cisco.com>
	<07c801c30f37$b859d9e0$261e4104@eagleswings>
	<20030430130432.2397ba40.moore@cs.utk.edu>
	<20030430150922.F574@thwip.polyamory.org>
X-Mailer: Sylpheed version 0.8.11 (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

> From what I have seen, those who think "local scope" is harmful, are
> concerned about the ambuity of addresses, as Keith says here again.
> They are NOT concerned about the fact that a given address may not be
> reachable from some places, or may be reachable via different routes
> from different places. 

There are multiple problems.

One problem is simply that ambiguous addresses are a pain; to use
them in any kind of referral (including DNS), you have to keep track of
the context in which they're valid, and without a global scheme for
naming those contexts there's no way to do that.   This is a primary
reason why we haven't been able to identify any good workarounds for
NATs in IPv4 - the very use of ambiguous addresses by those NATs removes
the one way we had of uniquely identifying not just hosts, but
also networks or realms.

(it's scary to think about, but we might actually be able to develop a
reasonable NAT-tolerant architecture if we still had globally unique
names for the realms)

Another problem is that the existence of addresses that have limited
reachability, _coupled with_ the expectation of multiple prefixes per
host, immediately begs the problem of how the host is going to choose
between those prefixes, especially if there's no obligation of the
network to make something like longest prefix match work if the hosts
are allowed to talk to one another.  (it also begs the problem of how
how apps can do referrals in that environment - yes, they can pass
around all of the addresses but that's a pain).

Both problems exist, and both are serious.  Only the first problem is
specific to SL (I don't consider v6 LL an issue).  We don't pretend that
getting rid of SL will address the second problem, but it helps because
the absence of SL provides less incentive for networks to use addressing
tricks as a means of filtering traffic. 

Keith



From owner-ietf@ietf.org  Wed Apr 30 18:24:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27158;
	Wed, 30 Apr 2003 18:24:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AyaK-0002vm-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 16:53:48 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AyTE-0002pX-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 16:46:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23463
	for <ietf@ietf.org>; Wed, 30 Apr 2003 16:42:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AyRh-0003SS-00
	for ietf@ietf.org; Wed, 30 Apr 2003 16:44:53 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AyRb-0003Rc-00
	for ietf@ietf.org; Wed, 30 Apr 2003 16:44:48 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h3UKhvxI028024;
	Wed, 30 Apr 2003 13:43:58 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.3-GR)
	with ESMTP id ADS38304;
	Wed, 30 Apr 2003 13:43:56 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id NAA13716; Wed, 30 Apr 2003 13:43:56 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16048.13708.414125.689623@thomasm-u1.cisco.com>
Date: Wed, 30 Apr 2003 13:43:56 -0700 (PDT)
To: Keith Moore <moore@cs.utk.edu>
Cc: Michael Thomas <mat@cisco.com>, john-ietf@jck.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: My thoughts on local-use addresses
In-Reply-To: <20030430151648.3c3d352e.moore@cs.utk.edu>
References: <20030426060420.GA93218@lethargic.dyndns.org>
	<20030426164255.GA98043@lethargic.dyndns.org>
	<20030426130211.321b0a4d.moore@cs.utk.edu>
	<13367010.1051372503@p3.JCK.COM>
	<20030430135832.1a645f93.moore@cs.utk.edu>
	<16048.5557.124583.930323@thomasm-u1.cisco.com>
	<20030430151648.3c3d352e.moore@cs.utk.edu>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore writes:
 > >  > IMHO, those who think
 > >  > that hosts or apps should have to bear the burden of picking which
 > >  > address or interface to use in order to get packets to their
 > >  > destination need to explain (a) where the hosts or apps get the
 > >  > information necessary to make those choices in a reliable and
 > >  > timely fashion, and probably (b) how to provide a usable endpoint
 > >  > identifier under those conditions that can be passed between hosts
 > >  > at arbitrary locations. 
 > > 
 > > It seems to me that what needs to be answered first is whether we are
 > > already resigned to dealing with that problem with mobility,
 > > renumbering, and multihoming. 
 > 
 > If we're resigned to dealing with an intractable problem, maybe we need
 > to rethink that assumption.  

Well, that's what I'm trying to tease apart
here: what's tractible, and what's intractible.
If the entire problem space is intractible,
then we probably have some pretty big problems.
It's not clear to me that it is though... read on.

 > But it's not clear that either mobility or
 > renumbering presents the same kind of challenge.  In the case of
 > mobility I think it's fairly simple to decide whether to use a home or
 > in-care-of address as the source address, and this can be dictated by
 > the application.

I'd say it's the stack, (for MIP at least) but
that's a small point.

 > As for
 > "multihoming" - these days people mean different things when they say
 > that, so I can't tell for sure what you mean.  

Nothing exciting: two different interfaces, two
different prefixes.

 > > There's good reason to want to use a
 > > local prefix rather than mobile IP for new communiation if possible
 > > since it more cleanly eliminates the dog leg through the home agent.
 > 
 > Taken in isolation, that's certainly true.  But it presumes several
 > things, one of which is that a sending host can tell which of several
 > prefixes is the best to use.  (or if not the best, which ones are more
 > likely to work well than others).  It's easy to construct cases where
 > it's possible for the sending host to do this; somewhat more difficult
 > to construct a convincing argument that this can be done in general.

Correct. Naively, when you're, say, starting a TCP
connection from a mobile node, if one of your
prefixes is bound to a tunnel (eg, a home agent),
you'd almost certainly like to use a CoA prefix
instead... unless you think you might move, and
the router which owns CoA prefix can't be a home
agent for whatever reason.

So it appears that even this fairly simple bit of
policy: "Use CoA prefix on outbound TCP
connections" isn't quite as simple as it first
appears. How on earth do I know if I might move?
Thus, it sort of reduces to "only if the current
router will support mobility in case I move", or
"I'm willing to deal with a loss of connectivity
on some sessions". But, this still seems to not
rely on anything extra about the prefix itself
other than what we already know.

I think that a similar argument can be made for
renumbering. That is, we can finesse the issue
such that end hosts don't have to know any sort of
qualities about the prefix other than either what
it currently knows, or what a real router told it
to believe (eg, the preference).

So I get back to my larger point: is the real
devil here hosts trying to know policy information
about prefixes that we currently have no way (or
desire) to spread around? I mean, I've always
thought that that was a pretty basic part of the
internet architecture, which is one of the reasons
I don't like the implications of scoped addresses.
Abandoning that philosophy pretty much says there
is no practical difference between a host and a
router.

      Mike



From owner-ietf@ietf.org  Wed Apr 30 18:24:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27228;
	Wed, 30 Apr 2003 18:24:28 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AyVj-0002sM-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 16:49:03 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AyHs-0002eN-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 16:34:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23040
	for <ietf@ietf.org>; Wed, 30 Apr 2003 16:31:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AyGq-0003LT-00
	for ietf@ietf.org; Wed, 30 Apr 2003 16:33:40 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AyGk-0003L0-00
	for ietf@ietf.org; Wed, 30 Apr 2003 16:33:34 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3UKWcL21737;
	Wed, 30 Apr 2003 15:32:39 -0500
Message-ID: <00ae01c30f57$a5f87200$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Ofer Inbar" <cos@aaaaa.org>, <ietf@ietf.org>
Cc: <alh-ietf@tndh.net>
References: <16047.57167.821886.158969@thomasm-u1.cisco.com> <07c801c30f37$b859d9e0$261e4104@eagleswings> <20030430130432.2397ba40.moore@cs.utk.edu> <20030430150922.F574@thwip.polyamory.org>
Subject: Re: what the "scope" disagreement is about
Date: Wed, 30 Apr 2003 14:56:53 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Ofer Inbar" <cos@aaaaa.org>
> but I have seen nothing other than Tony's assertions that would make
> me think this dicussion is about any of those things.  It puzzles me that
> he keeps repeating them.
>
> Tony, *why* do you think this discussion is about reachability?
>
> Everyone else: Do any of you believe that's what this is about, aside
>   from Tony's assertions and peoples responses to those assertions?

Well, I think there was some confusion while we sorted out exactly what
"scope" means, as one camp seems to define it as a reachability problem
while the other camp defines it as an identity problem.

Any time you pass locators across a "scope" boundary, using either
definition above, things break.  I think we all agree on that, so the exact
definition of "scope" doesn't seem so important.

There is a related issue, which was until recently confused with the first,
and that is whether ambiguous addresses should be allowed/encouraged for
local use.  It seems to be established that this is a bad idea, but unless
there is a workable mechanism to establish unique addresses for all networks
_without relying on topology_, I don't see the concept going away.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Wed Apr 30 19:10:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27156;
	Wed, 30 Apr 2003 18:24:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AyoC-00035W-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 17:08:08 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Ayg4-0002yV-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 16:59:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24067
	for <ietf@ietf.org>; Wed, 30 Apr 2003 16:56:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ayf2-0003c5-00
	for ietf@ietf.org; Wed, 30 Apr 2003 16:58:40 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ayew-0003bE-00
	for ietf@ietf.org; Wed, 30 Apr 2003 16:58:34 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.11.3/8.9.3) with ESMTP id h3UKu1E97972;
	Wed, 30 Apr 2003 22:56:02 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Wed, 30 Apr 2003 22:56:02 +0200
Subject: Re: site-local != NAT
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <alh-ietf@tndh.net>, "'Michael Thomas'" <mat@cisco.com>,
        "'Randy Bush'" <randy@psg.com>, "'Keith Moore'" <moore@cs.utk.edu>,
        <cos@aaaaa.org>, <ietf@ietf.org>
To: Margaret Wasserman <mrw@windriver.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <5.1.0.14.2.20030430141234.044bae28@mail.windriver.com>
Message-Id: <26FD5170-7B4E-11D7-A65D-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On woensdag, apr 30, 2003, at 20:28 Europe/Amsterdam, Margaret 
Wasserman wrote:

> It is an inevitable fact of physics that some addresses will be
> unreachable from some parts of the network.

More like an inevitable fact of economics... Thanks to Paul Baran we 
know how to build reliable networks.

> Applications must deal with this (either well or badly), because
> there is no other choice.

We really don't want this dealing to happen in the applications, for 
three reasons:

1. Doing all the work again for each application is not a good use
    of resources

2. It is much harder (or rather: impossible) to get something as
    tricky as this right in so many places

3. The failure can happen over the course of a session, in which case
    applications can't do anything to fix it short of implementing a
    large amount of transport logic




From owner-ietf@ietf.org  Wed Apr 30 19:10:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27157;
	Wed, 30 Apr 2003 18:24:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AyoD-00035n-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 17:08:09 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AyhA-0002yu-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 17:00:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24097
	for <ietf@ietf.org>; Wed, 30 Apr 2003 16:57:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ayg7-0003cb-00
	for ietf@ietf.org; Wed, 30 Apr 2003 16:59:47 -0400
Received: from astro.cs.utk.edu ([160.36.58.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Ayg2-0003cN-00
	for ietf@ietf.org; Wed, 30 Apr 2003 16:59:42 -0400
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h3UKxUv22772;
        Wed, 30 Apr 2003 16:59:30 -0400 (EDT)
Date: Wed, 30 Apr 2003 16:59:30 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Michael Thomas <mat@cisco.com>
Cc: moore@cs.utk.edu, mat@cisco.com, john-ietf@jck.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: My thoughts on local-use addresses
Message-Id: <20030430165930.3b7af536.moore@cs.utk.edu>
In-Reply-To: <16048.13708.414125.689623@thomasm-u1.cisco.com>
References: <20030426060420.GA93218@lethargic.dyndns.org>
	<20030426164255.GA98043@lethargic.dyndns.org>
	<20030426130211.321b0a4d.moore@cs.utk.edu>
	<13367010.1051372503@p3.JCK.COM>
	<20030430135832.1a645f93.moore@cs.utk.edu>
	<16048.5557.124583.930323@thomasm-u1.cisco.com>
	<20030430151648.3c3d352e.moore@cs.utk.edu>
	<16048.13708.414125.689623@thomasm-u1.cisco.com>
X-Mailer: Sylpheed version 0.8.11 (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

>  > If we're resigned to dealing with an intractable problem, maybe we
>  > need to rethink that assumption.  
> 
> Well, that's what I'm trying to tease apart
> here: what's tractible, and what's intractible.
> If the entire problem space is intractible,
> then we probably have some pretty big problems.
> It's not clear to me that it is though... read on.
> 
>  > But it's not clear that either mobility or
>  > renumbering presents the same kind of challenge.  In the case of
>  > mobility I think it's fairly simple to decide whether to use a home
>  > or in-care-of address as the source address, and this can be
>  > dictated by the application.
> 
> I'd say it's the stack, (for MIP at least) but
> that's a small point.

nope, the app.  the stack doesn't know whether the app prefers stability
or efficiency, unless the app tells it which it prefers.  but at least
the app probably has an idea which one is better.

this is fundamentally different than expecting either the host or
the app to choose between multiple source or destination addresses, each
pair imposing apparently (to the host and app) arbitrary constraints on
what the network will pass.

Keith



From owner-ietf@ietf.org  Wed Apr 30 19:10:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27155;
	Wed, 30 Apr 2003 18:24:16 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AyGz-0002eF-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 16:33:49 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AyFp-0002aR-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 16:32:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22966
	for <ietf@ietf.org>; Wed, 30 Apr 2003 16:29:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AyEY-0003KS-00
	for ietf@ietf.org; Wed, 30 Apr 2003 16:31:18 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AyES-0003KG-00
	for ietf@ietf.org; Wed, 30 Apr 2003 16:31:12 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26C1A> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 30 Apr 2003 13:31:22 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Ofer Inbar'" <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: what the "scope" disagreement is about
Date: Wed, 30 Apr 2003 13:31:50 -0700
Message-ID: <07ed01c30f57$87835b50$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030430150922.F574@thwip.polyamory.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA27155

Ofer Inbar wrote:
> For what it's worth, I've been watching this discussion for a 
> while, not as a proponent of any particular side, and I 
> completely agree with Keith on this point.  I've seen Tony 
> Hain repeatedly make the assertion that this discussion is 
> about the fact that not all addresses can be reached from 
> everywhere, or that we don't have a "flat routing space", or 
> any number of related restatements... but I have seen nothing 
> other than Tony's assertions that would make me think this 
> dicussion is about any of those things.  It puzzles me that 
> he keeps repeating them.
> 
> Tony, *why* do you think this discussion is about reachability?

Below

> 
> Everyone else: Do any of you believe that's what this is about, aside
>   from Tony's assertions and peoples responses to those assertions?
> 
> From what I have seen, those who think "local scope" is 
> harmful, are concerned about the ambuity of addresses, as 
> Keith says here again. They are NOT concerned about the fact 
> that a given address may not be reachable from some places, 
> or may be reachable via different routes from different 
> places.  Or, rather, whether they're concerned about that or 
> not, it has nothing to do with their objections to locally 
> scoped addresses.  All of their objections to locally scoped 
> addresses seem to be about the fact that the addresses are 
> ambiguous, not unique. They have no objections to globally 
> unique addresses that remain "local" as far as routing and 
> reachability.

We have several proposals for removing the ambiguity in the current SL,
so while we may not agree on a specific one, we have examples of
technically how to do that. Therefore the effort to eliminate SL can't
be about ambiguity, because we could simply fix that component of the
current SL with little effort. 

The reason I say this is about reachability is that even with unique
addresses, applications will fail when they choose to pass 'an opaque
identifier' around, while they simultaneously assume that the content is
a valid topology locator at the receiver. The arguments claim the need
for opaqueness as an application simplifier on one hand, at the same
they insist that the topology match their perspective of a flat routing
space. The real network is not a single flat routing space.

Given a list of addresses for a target, how would an application pick
one that is assured to work at the receiver? Answer: it can't without
knowing the topology. The only way to keep the app from knowing
topology, and make the app work in the presence of a list is to pass the
label that was used to get the initial list, so the receiver can get its
own that is topologically appropriate. This has nothing at all to do
with ambiguity in the allocations, and everything to do with the fact
that topology locators have different utility in different parts of the
network. For example:

     ---- A ----
       |      I
       |      n
       |      t
       I      e ---- C
       2      r
       |      n
       |      e
       |      t
     ---- B ----

There are no ambiguous addresses here, just a list of potential topology
locators. If B wants to tell C to connect to A, it either has to pass a
label that C can use to figure it out, or know enough about the topology
to know which locator C needs. This simple example of why routing is not
globally flat is why I have been saying that an assumption by
applications that they can simply pick any member of the list and the
result will be useful at C is invalid. 

Replace I2 in the above diagram with one of the globally unique versions
of SL, and the issues are exactly the same. If B hands C the
non-Internet address of A, there will be no valid route in the public
net.

Replace I2 with the current version of SL, and the only difference is
that C might be in a site which uses the same subnet prefix in its local
use, so the bits will head toward a router inside the C site rather than
being dropped in the public net (people that pay by volume on the ISP
link actually consider this a feature). If the A & C sites chose to
manually allocate IIDs 1, 2, 3 ... there is a possibility that the
address handed by B would point to a different host in the C site. If
either site chose to use just about any other scheme for generating
IIDs, the likelihood of any given IID pattern being at the other site,
let alone having the same subnet prefix, is so close to 0 it is not
worth discussing. Note, this is not an argument for keeping the
ambiguity of the current SL.

Ambiguity is not the cause of the problem here, it is just the red
herring used to bolster support for shooting the SL messenger. The
fundamental problem is that processes exist that refuse to acknowledge
the network is not a single flat routing space. They do this by passing
around topology information with the explicit assumption that the
'opaque contents' will be a valid topology locator at the receiver.
Until we deal with this, there will continue to be lengthy discussions
about removing limited scope addresses from the architecture. Since
scoping through limiting routing information is an operations issue,
removing them will not happen. 

We can choose to set aside a prefix to easily identify the limited scope
addresses or not. If we don't we will have exactly the I2 case above and
no way for sorting the list of possibilitie. If we put them all in a
well-known prefix, the public net can use that in the bogon filter, and
any app that chooses to look might decide one or the other type is most
likely to work for its purposes.

Tony





From owner-ietf@ietf.org  Wed Apr 30 19:27:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29494;
	Wed, 30 Apr 2003 19:27:21 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AzOE-0003UM-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 17:45:22 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AzK1-0003S2-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 17:41:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25056
	for <ietf@ietf.org>; Wed, 30 Apr 2003 17:37:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AzIU-0003qS-00
	for ietf@ietf.org; Wed, 30 Apr 2003 17:39:26 -0400
Received: from thunk.org ([140.239.227.29] helo=thunker.thunk.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AzIJ-0003pt-00
	for ietf@ietf.org; Wed, 30 Apr 2003 17:39:16 -0400
Received: from [216.175.175.162] (helo=think.thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:DES-CBC3-SHA:168) 
	(tls_peerdn /C=US/ST=Massachusetts/L=Medford/O=Thunking Systems/OU=SMTP-client/CN=think.thunk.org/Email=tytso@thunk.org)
	 (Exim 3.35 #1 (Debian))
	id 19AzIL-00060h-00; Wed, 30 Apr 2003 17:39:17 -0400
Received: from tytso authenticated as tytso by think.thunk.org with local   (Exim 3.35 #1 (Debian))
	id 19AzJO-0000fh-00; Wed, 30 Apr 2003 17:40:22 -0400
Date: Wed, 30 Apr 2003 17:40:22 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: Ofer Inbar <cos@aaaaa.org>
Cc: ietf@ietf.org, alh-ietf@tndh.net
Subject: Re: what the "scope" disagreement is about
Message-ID: <20030430214022.GA2549@think>
References: <16047.57167.821886.158969@thomasm-u1.cisco.com> <07c801c30f37$b859d9e0$261e4104@eagleswings> <20030430130432.2397ba40.moore@cs.utk.edu> <20030430150922.F574@thwip.polyamory.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030430150922.F574@thwip.polyamory.org>
User-Agent: Mutt/1.5.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Apr 30, 2003 at 03:09:22PM -0400, Ofer Inbar wrote:
> Keith Moore <moore@cs.utk.edu> wrote:
> > [Tony Hain writes:]
> > > What many are missing here is that this is not about 1918 style
> > > addressing. This is about the fact that addresses do not have the same
> > > visibility and accessibility throughout the network.
> > 
> > no, it's not just about that.  you are the only one who keeps insisting
> > that.  you seem to be trying to conflate two different notions of scope.
> 
> For what it's worth, I've been watching this discussion for a while,
> not as a proponent of any particular side, and I completely agree with
> Keith on this point.  I've seen Tony Hain repeatedly make the assertion
> that this discussion is about the fact that not all addresses can be
> reached from everywhere, or that we don't have a "flat routing space",
> or any number of related restatements... but I have seen nothing other
> than Tony's assertions that would make me think this dicussion is
> about any of those things.  It puzzles me that he keeps repeating them.
> 
> Tony, *why* do you think this discussion is about reachability?
> 
> Everyone else: Do any of you believe that's what this is about, aside
>   from Tony's assertions and peoples responses to those assertions?

I certainly agree that it's all about ambiguous addresses and not about
about reachability.  And it's why I have to agree with Keith that Site
Local addresses are a bad idea, and why ditching them is absolutely
the right thing.

Perhaps if we were doing things all over again, we would have two
entirely different addresses; one which is appropriate for identifying
the end-point, and which would be used by the IP layer and up (i.e.,
IP, TCP/UDP), and application level protocols, and another address
which is used for the purpose of routing the packet from one location
to another, and which would be used by the IP layer and below.
Hmm.... why does this remind me of the 8+8 proposal?  Shear
coincidence, I sure.  :-)

Anyway, for better or for worse, we don't have two separate addresses,
and protocols above and below the IP layer have been using the single
IP address for multiple different things.  As some have pointed out,
one can consider TCP as using the IP address as an end-point
identifier, which means that we can't renumber without breaking the
TCP connection.  So if we say that applications are "broken" when they
use IP addresses in this fashion, such that NAT's need to know about
the about the low-level details about the protocol when they perform
their charming man-in-the-middle attack^H^H^H^^H^H^H^Hpacket rewriting
function, this applies as much to TCP as it does to FTP.   

For whatever reason that I've not been able to understand we've
decided not to do the architecturally clean thing and either used two
fixed-length addresses, one for routing and one for end-point
identifications, *or* required that TCP connections store and utilize
DNS names in TCP headers in order to specify the source and
destination end-points.  That way, NAT boxes wouldn't need to modify
TCP (psuedo-) headers and TCP checksums when they did their magic.  

But given that we've not decided to go down this path, we have to live
with the consequences of our using a perhaps "unclean" architecture.
It means that applications should avoid trying to using IP addresses
when it can't, but at the same time, routing folks can't claim that
the IP address is only a routing entity and that no other assumptions
of the IP addresses should ever be used by applications.  For better
or for worse, applications need a reliable end-point identifier, and
while IP addresses aren't perfect, DNS names are not appropriate for
various reasons either.  So applications and end users will continue
to muddle along, and that's just life in the big, muddled, "unclean",
city.

					- Ted



From owner-ietf@ietf.org  Wed Apr 30 19:27:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29515;
	Wed, 30 Apr 2003 19:27:23 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19AzOC-0003UE-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 17:45:20 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19AzIM-0003RS-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 17:39:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25009
	for <ietf@ietf.org>; Wed, 30 Apr 2003 17:35:47 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AzH4-0003pQ-00
	for ietf@ietf.org; Wed, 30 Apr 2003 17:37:58 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AzGz-0003pK-00
	for ietf@ietf.org; Wed, 30 Apr 2003 17:37:53 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.9/8.12.9) with ESMTP id h3ULbX5J010195;
	Wed, 30 Apr 2003 17:37:33 -0400
Message-Id: <200304302137.h3ULbX5J010195@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: pdeutsch@earthlink.net
Cc: ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question) 
In-Reply-To: Your message of "Tue, 29 Apr 2003 15:41:43 PDT."
             <3EAEFFA7.63A14F72@earthlink.com> 
References: <69412F1F-7A80-11D7-A72E-00039388672E@muada.com>
            <3EAEFFA7.63A14F72@earthlink.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_920063234P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 30 Apr 2003 17:37:33 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_920063234P
Content-Type: text/plain; charset=us-ascii

On Tue, 29 Apr 2003 15:41:43 PDT, Peter Deutsch said:
> Well, if anyone's going to argue against them, shouldn't they at least
> understand why they're being deployed?? ;-)

I can watch CNN broadcasting pictures of self-flaggelating religious types
and say "Wow, that's gotta hurt!" without understanding why they do it....

--==_Exmh_920063234P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+sEIdcC3lWbTT17ARAtoqAJ48WDgU3BzecDPL8ab2YdHG9GhMOgCglJq9
wTBCfZ0YxMrDxIY3Q0sAh7c=
=Pcvd
-----END PGP SIGNATURE-----

--==_Exmh_920063234P--



From owner-ietf@ietf.org  Wed Apr 30 19:27:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29538;
	Wed, 30 Apr 2003 19:27:25 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Az8P-0003M2-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 17:29:01 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Az7U-0003JX-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 17:28:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24697
	for <ietf@ietf.org>; Wed, 30 Apr 2003 17:24:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Az6C-0003lb-00
	for ietf@ietf.org; Wed, 30 Apr 2003 17:26:44 -0400
Received: from tomts20-srv.bellnexxia.net ([209.226.175.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Az66-0003lO-00
	for ietf@ietf.org; Wed, 30 Apr 2003 17:26:38 -0400
Received: from yahoo.com ([65.93.188.85]) by tomts20-srv.bellnexxia.net
          (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP
          id <20030430212652.NTDX22383.tomts20-srv.bellnexxia.net@yahoo.com>;
          Wed, 30 Apr 2003 17:26:52 -0400
Date: Wed, 30 Apr 2003 17:26:51 -0400
Subject: Re: site-local != NAT
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "'Keith Moore'" <moore@cs.utk.edu>, <mat@cisco.com>, <randy@psg.com>,
        <cos@aaaaa.org>, <ietf@ietf.org>
To: <alh-ietf@tndh.net>
From: S Woodside <sbwoodside@yahoo.com>
In-Reply-To: <07d401c30f40$ae7b0fd0$261e4104@eagleswings>
Message-Id: <7550A6A0-7B52-11D7-8B42-000393414368@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Wednesday, April 30, 2003, at 01:48  PM, Tony Hain wrote:

> On top of that, scoping is about more than packet filtering, scoping 
> happens
> simply by filtering out some topology information in the routing 
> protocols.

That may be true, but there are many people who are talking about the 
internet being flat and reachable ... or not. And "not" includes both 
packet filtering and scoping, even though they are different!

simon

--
www.simonwoodside.com -- 99% Devil, 1% Angel




From owner-ietf@ietf.org  Wed Apr 30 19:44:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00054;
	Wed, 30 Apr 2003 19:44:06 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19Azkw-0006uq-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 18:08:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Azk6-0006eW-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 18:07:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25951
	for <ietf@ietf.org>; Wed, 30 Apr 2003 18:04:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Azj2-0003zE-00
	for ietf@ietf.org; Wed, 30 Apr 2003 18:06:53 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Aziv-0003z0-00
	for ietf@ietf.org; Wed, 30 Apr 2003 18:06:46 -0400
Received: from ssprunk (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id h3UM6aL23620;
	Wed, 30 Apr 2003 17:06:36 -0500
Message-ID: <010101c30f64$c7792f20$93b58742@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Keith Moore" <moore@cs.utk.edu>, "Michael Thomas" <mat@cisco.com>
Cc: <moore@cs.utk.edu>, <mat@cisco.com>, <john-ietf@jck.com>,
        <ipng@sunroof.eng.sun.com>, <ietf@ietf.org>
References: <20030426060420.GA93218@lethargic.dyndns.org><20030426164255.GA98043@lethargic.dyndns.org><20030426130211.321b0a4d.moore@cs.utk.edu><13367010.1051372503@p3.JCK.COM><20030430135832.1a645f93.moore@cs.utk.edu><16048.5557.124583.930323@thomasm-u1.cisco.com><20030430151648.3c3d352e.moore@cs.utk.edu><16048.13708.414125.689623@thomasm-u1.cisco.com> <20030430165930.3b7af536.moore@cs.utk.edu>
Subject: Re: My thoughts on local-use addresses
Date: Wed, 30 Apr 2003 17:06:07 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Keith Moore" <moore@cs.utk.edu>
> nope, the app.  the stack doesn't know whether the app prefers stability
> or efficiency, unless the app tells it which it prefers.  but at least
> the app probably has an idea which one is better.

The app developer often doesn't know these things either -- if the app
understands this new API at all, I think it'd most often end up as a user
knob, meaning we could just call it a stack option and leave the app out of
things entirely.

> this is fundamentally different than expecting either the host or the app
> to choose between multiple source or destination addresses, each
> pair imposing apparently (to the host and app) arbitrary constraints
> on what the network will pass.

Which is harder, having the stack give the app a list of source and
destination addresses and then expect the app to figure out which to use, or
have the stack attempt various combinations of source and destination
addresses and just notify the application which one(s) worked?

Something tells me the latter is both easier and more likely to be
implemented correctly.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Wed Apr 30 20:13:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00956;
	Wed, 30 Apr 2003 20:13:45 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19B098-0003ah-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 18:33:50 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19Azzv-0001YO-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 18:24:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27109
	for <ietf@ietf.org>; Wed, 30 Apr 2003 18:21:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19Azyr-00043g-00
	for ietf@ietf.org; Wed, 30 Apr 2003 18:23:13 -0400
Received: from mail.flarion.com ([63.103.94.23] helo=rrmail01.lab.flarion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19Azym-00042v-00
	for ietf@ietf.org; Wed, 30 Apr 2003 18:23:08 -0400
Received: by rrmail01.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <J88QM0VN>; Wed, 30 Apr 2003 18:22:40 -0400
Message-ID: <748C6D0A58C0F94CA63C198B6674697A0141B9D6@ftmail.lab.flarion.com>
From: Hesham Soliman <H.Soliman@flarion.com>
To: "'Stephen Sprunk'" <stephen@sprunk.org>, Keith Moore <moore@cs.utk.edu>,
        Michael Thomas <mat@CISCO.COM>
Cc: moore@cs.utk.edu, mat@CISCO.COM, john-ietf@jck.com,
        ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: RE: My thoughts on local-use addresses
Date: Wed, 30 Apr 2003 18:22:39 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

A side comment independent of the site-local discussion.

 > Thus spake "Keith Moore" <moore@cs.utk.edu>
 > > nope, the app.  the stack doesn't know whether the app 
 > prefers stability
 > > or efficiency, unless the app tells it which it prefers.  
 > but at least
 > > the app probably has an idea which one is better.
 > 
 > The app developer often doesn't know these things either -- 
 > if the app
 > understands this new API at all, I think it'd most often end 
 > up as a user
 > knob, meaning we could just call it a stack option and leave 
 > the app out of
 > things entirely.
 > 
 > > this is fundamentally different than expecting either the 
 > host or the app
 > > to choose between multiple source or destination addresses, each
 > > pair imposing apparently (to the host and app) arbitrary 
 > constraints
 > > on what the network will pass.
 > 
 > Which is harder, having the stack give the app a list of source and
 > destination addresses and then expect the app to figure out 
 > which to use, or
 > have the stack attempt various combinations of source and destination
 > addresses and just notify the application which one(s) worked?
 > 

=> There is another option: _Abstract_ the API to the app
to reflect the "benefits" or "meaning" of either option. For instance,
if you compare the MIP home address and CoA, you can abstract
the meaning of these addresses to indicate things like whether
the connection needs to be "stable" or not. There are other 
cases where the stack might already know what a well-known
app might need. So there maybe a need for both sides to
provide input. And things get more complex of course when
the app has many requirements. 

If we have to make a general rule then I'd prefer the 
app to decide. But I'm not sure that there is a need
for a general rule here.

Hesham


 > Something tells me the latter is both easier and more likely to be
 > implemented correctly.
 > 
 > S
 > 
 > Stephen Sprunk         "God does not play dice."  --Albert Einstein
 > CCIE #3723         "God is an inveterate gambler, and He throws the
 > K5SSS        dice at every possible opportunity." --Stephen Hawking
 > 
 > --------------------------------------------------------------------
 > IETF IPng Working Group Mailing List
 > IPng Home Page:                      http://playground.sun.com/ipng
 > FTP archive:                      ftp://playground.sun.com/pub/ipng
 > Direct all administrative requests to majordomo@sunroof.eng.sun.com
 > --------------------------------------------------------------------
 > 



From owner-ietf@ietf.org  Wed Apr 30 20:45:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01670;
	Wed, 30 Apr 2003 20:45:37 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19B0oh-0004Ch-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 19:16:47 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19B0UX-0003yr-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 18:55:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28489
	for <ietf@ietf.org>; Wed, 30 Apr 2003 18:52:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B0TF-0004IE-00
	for ietf@ietf.org; Wed, 30 Apr 2003 18:54:37 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19B0T9-0004I3-00
	for ietf@ietf.org; Wed, 30 Apr 2003 18:54:31 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26C72> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 30 Apr 2003 15:54:21 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Margaret Wasserman'" <mrw@windriver.com>
Cc: "'Michael Thomas'" <mat@cisco.com>, "'Randy Bush'" <randy@psg.com>,
        "'Keith Moore'" <moore@cs.utk.edu>, <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: site-local != NAT
Date: Wed, 30 Apr 2003 15:55:00 -0700
Message-ID: <07f301c30f6b$87a28c00$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <5.1.0.14.2.20030430141234.044bae28@mail.windriver.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA01670

Margaret Wasserman wrote:
> Hi Tony,
> 
> At 09:44 AM 4/30/2003 -0700, Tony Hain wrote:
> >What many are missing here is that this is not about 1918 style 
> >addressing. This is about the fact that addresses do not 
> have the same 
> >visibility and accessibility throughout the network. This 
> operational 
> >reality causes the affect we have labeled scoping.
> 
> There are three ways in which a particular address can be non-global:
> 
>          - Unreachable:  The address can be unreachable from some
>                  portions of the network (due to filtering, network
>                  failures, etc.).
> 
>          - Not Globally Routed:  There can be no route to the address
>                  from some portions of the network.
> 
>          - Not Globally Unique (AKA Ambiguous): A single address can
>                  indicate one node when it is used in one part of
>                  the network, and a different node when it is used
>                  in other parts of the
> 
> It is an inevitable fact of physics that some addresses will 
> be unreachable from some parts of the network.  The 
> widespread use of filtering/firewalls makes this both 
> intentional and common. Applications must deal with this 
> (either well or badly), because there is no other choice.

The point is they don't when they claim to be passing around 'opaque
identifiers', at the same time they are explicitly assuming the content
of that opaque object is a valid topology object at the receiver.

> 
> If the only way to get a globally routable address is to get 
> it from your provider, people may choose to use addresses 
> that are not globally routed for some purposes, such as 
> convenience or provider-independence.
> 
> I have not heard any compelling operational requirement for 
> ambiguous addresses in IPv6.

According to the definition above, anycast is one such case. Given that
anycast is in daily operational use, there must be a requirement for
addresses to refer to different physical devices in different parts of
the network.

> 
> The IPv6 scoped addressing architecture defines addresses 
> that have all three of these properties, and this is what I 
> hear when you say "scoped addressing".  There could be types 
> of local addressing, though, that don't have all of these properties.
> 
> If you are using the term "scoped" addressing to refer to 
> something other than the type of addressing defined in the 
> IPv6 scoped addressing architecture, could you define your term?

I have been attempting to be very explicit about separating the third
point from the other two. As my note to Ofer showed, the issues raised
by a mismatch in expectations, about the validity of different members
in list of addresses, apply independent of any discussion about multiple
networks using the same prefix. 

> 
> Thanks,
> Margaret
> 
> P.S. There were some proposals to remove (or lessen the 
> likelihood of) ambiguous site-local addresses, but none of 
> those proposals removed the restrictions from the IPv6 scoped 
> addressing architecture that are only required because 
> addresses are ambiguous (sites can't be nested or overlap, 
> zone IDs are needed to disambiguate, etc.).

They didn't propose an end to world hunger either. Personal drafts don't
necessarily reflect community thought and input on a topic, and may fail
to cover all possible edits needed in other documents. We have technical
examples of ways to remove ambiguity from the discussion, but there is
still a group that wants to eliminate SL. By taking item 3 off the
table, that desire must be related to the other two. 

There is a strong desire to kill anything that is related to the first
two since they collectively expose the bogus assertion that the 'opaque
identifiers' have an unknown value by the application, but (wink, wink)
we really know they contain a topology locator that the receiver will
use because resolution services are too slow. I have no problem with
applications passing these around as long as they make sure the 'opaque
contents' matches the network topology. If they don't want to go the the
effort required to do that right, they need to be passing around labels
so the receiver can construct a topologically correct list. 

Tony





From owner-ietf@ietf.org  Wed Apr 30 20:45:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01663;
	Wed, 30 Apr 2003 20:45:33 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19B0Nf-0003wl-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 18:48:51 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19B0NT-0003t2-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 18:48:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28236
	for <ietf@ietf.org>; Wed, 30 Apr 2003 18:44:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B0Lv-0004Em-00
	for ietf@ietf.org; Wed, 30 Apr 2003 18:47:04 -0400
Received: from pop018pub.verizon.net ([206.46.170.212] helo=pop018.verizon.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19B0Lq-0004Eg-00
	for ietf@ietf.org; Wed, 30 Apr 2003 18:46:58 -0400
Received: from earthlink.com ([4.65.81.124]) by pop018.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030430224637.MKLT17739.pop018.verizon.net@earthlink.com>;
          Wed, 30 Apr 2003 17:46:37 -0500
Message-ID: <3EB0516E.4F3D7D9E@earthlink.com>
Date: Wed, 30 Apr 2003 15:42:54 -0700
From: Peter Deutsch <pdeutsch@earthlink.com>
Reply-To: pdeutsch@earthlink.net
Organization: Gydig Software
X-Mailer: Mozilla 4.78 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: pdeutsch@earthlink.net, ipng@sunroof.eng.sun.com, ietf@ietf.org
Subject: Re: A Good Schism Brightens Anyone's Day (was: A Simple Question)
References: <69412F1F-7A80-11D7-A72E-00039388672E@muada.com>
	            <3EAEFFA7.63A14F72@earthlink.com> <200304302137.h3ULbX5J010195@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at pop018.verizon.net from [4.65.81.124] at Wed, 30 Apr 2003 17:46:37 -0500
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

g'day,

Valdis.Kletnieks@vt.edu wrote:
> 
> On Tue, 29 Apr 2003 15:41:43 PDT, Peter Deutsch said:
> > Well, if anyone's going to argue against them, shouldn't they at least
> > understand why they're being deployed?? ;-)
> 
> I can watch CNN broadcasting pictures of self-flaggelating religious types
> and say "Wow, that's gotta hurt!" without understanding why they do it....

Yeah, but if we want to continue with this religious analogy for a bit
longer, there's plenty of evidence throughout history that failure to
understand why other cultures do what they do can actually actually hurt
*you* in the long run....


			- peterd

-- 

---------------------------------------------------------------------
    Peter Deutsch                       pdeutsch@gydig.com
    Gydig Software


  "It is inhumane, in my opinion, to force people who have a
   genuine medical need for coffee to wait in line behind people
   who apparently view it as some kind of recreational activity."

                                        -- Dave Barry

---------------------------------------------------------------------



From owner-ietf@ietf.org  Wed Apr 30 22:12:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02959;
	Wed, 30 Apr 2003 22:12:06 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19B1Yk-0006Jh-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 20:04:22 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19B1Ws-0006EB-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 20:02:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00455
	for <ietf@ietf.org>; Wed, 30 Apr 2003 19:59:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B1HF-0004ee-00
	for ietf@ietf.org; Wed, 30 Apr 2003 19:46:17 -0400
Received: from evrtwa1-ar8-4-65-019-240.evrtwa1.dsl-verizon.net ([4.65.19.240] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 19B1H9-0004eX-00
	for ietf@ietf.org; Wed, 30 Apr 2003 19:46:12 -0400
Received: from eagleswings (127.0.0.1)
	by library with [XMail 1.10 (Win32/Ix86) ESMTP Server]
	id <S26C8B> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 30 Apr 2003 16:46:40 -0700
Reply-To: <alh-ietf@tndh.net>
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'S Woodside'" <sbwoodside@yahoo.com>
Cc: "'Keith Moore'" <moore@cs.utk.edu>, <mat@cisco.com>, <randy@psg.com>,
        <cos@aaaaa.org>, <ietf@ietf.org>
Subject: RE: site-local != NAT
Date: Wed, 30 Apr 2003 16:47:23 -0700
Message-ID: <07ff01c30f72$d91a8c70$261e4104@eagleswings>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <7550A6A0-7B52-11D7-8B42-000393414368@yahoo.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id WAA02959

S Woodside wrote:
> That may be true, but there are many people who are talking about the 
> internet being flat and reachable ... or not. And "not" includes both 
> packet filtering and scoping, even though they are different!

I don't know how to parse this. 

My point was that there are topology locators that are only viable
within a scope defined by the local network manager. That network
manager may choose to implement the boundary of the local scope through
routing protocols or through access controls. It really doesn't matter
which technique is used, the result is the same. Local scope addresses
that are passed outside the defined boundary are useless. 

The argument for passing addresses around is that doing so is faster
than passing the label used to get the initial mapping. While it is
probably faster in the case where the topology is consistent between the
sender & receiver, in the case where the topology doesn't match the
argument fails. How is passing a useless value faster than a label that
could be used to construct a useful one? If it is recognized that the
address failed, the only recovery is to try another member of the list,
or go back to the original label.

Tony





From owner-ietf@ietf.org  Wed Apr 30 23:43:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04345;
	Wed, 30 Apr 2003 23:43:20 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 19B2t2-0008MR-00
	for ietf-list@ran.ietf.org; Wed, 30 Apr 2003 21:29:24 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 19B2ZX-00089h-00
	for ietf@ran.ietf.org; Wed, 30 Apr 2003 21:09:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02189
	for <ietf@ietf.org>; Wed, 30 Apr 2003 21:05:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B2XZ-0005C8-00
	for ietf@ietf.org; Wed, 30 Apr 2003 21:07:13 -0400
Received: from carmen.ipv6.tilab.com ([163.162.170.198])
	by ietf-mx with esmtp (Exim 4.12)
	id 19B2XO-0005C5-00
	for ietf@ietf.org; Wed, 30 Apr 2003 21:07:02 -0400
Received: from carmen.ipv6.tilab.com (localhost [IPv6:::1])
	by carmen.ipv6.tilab.com (8.12.9/8.12.3) with ESMTP id h41130HZ021824
	for <ietf@ietf.org>; Thu, 1 May 2003 03:03:00 +0200 (MEST)
Received: (from root@localhost)
	by carmen.ipv6.tilab.com (8.12.9/8.12.3/Submit) id h41130MY021823
	for ietf@ietf.org; Thu, 1 May 2003 03:03:00 +0200 (MEST)
Date: Thu, 1 May 2003 03:03:00 +0200 (MEST)
From: Super-User <root@carmen.ipv6.tilab.com>
Message-Id: <200305010103.h41130MY021823@carmen.ipv6.tilab.com>
To: ietf@ietf.org
Subject: The IETF_Censored mailing list
Sender: owner-ietf@ietf.org
Precedence: bulk


                        The IETF_Censored mailing list
                                       
   At times, the IETF list is subject to debates that have little to do
   with the purposes for which the IETF list was created. Some people
   would appreciate a "quieter" forum for the relevant debates that take
   place, but the IETF's policy of openness has so far prevented the IETF
   from imposing any censorship policy on the IETF@ietf.org list.
   
   To give people an alternative, there is a list called
   "ietf_censored@carmen.ipv6.cselt.it".
   
   This list is a sublist (that is, it gets the same messages as) the
   open IETF discussion list. However, this list will not forward all
   messages; in particular, the filters have been set so that persons and
   discussions that are, in the view of Raffaele D'Albenzio, irrelevant
   to the IETF list are not forwarded.
   
   Because this filter is automated, the criteria include:
     * Well known troublemakers
     * Well known crosspostings
     * Subjects that have led to recent non-conclusive exchanges
     * Some ways to say "unsubscribe"
     * Some "out-of-office-reply" messages
       
   To join the list, send the word "subscribe" in the BODY of a message
   to ietf_censored-request@carmen.ipv6.cselt.it (the URL here is an RFC
   2368 mailto URL that does the Right Thing).
   
   To unsubscribe, send the word "unsubscribe" in the BODY of a message
   to ietf_censored-request@carmen.ipv6.cselt.it. Do not send to the list
   - your message will be filtered!
   (members of the main IETF list itself must follow instructions for
   that list, of course. You are only a member of ietf_censored if there
   is a comment on the bottom of your IETF list mail saying that the
   message has been sent through the ietf_censored list.)
   
   For fun, there is a special list for the rejected messages:
   ietf_censored-rejects@carmen.ipv6.cselt.it - subscribe in the same
   fashion, by mail to ietf_censored-rejects-request@carmen.ipv6.cselt.it
   
   By public request, the current set of filters are listed at
   http://vesuvio.ipv6.tilab.com/cgi-bin/ietf_censored-filters
   
   This page is http://carmen.ipv6.cselt.it/ietf_censored.html, and is
   posted monthly in text form to ietf@ietf.org
     _________________________________________________________________
   
   Raffaele D'Albenzio < root@carmen.ipv6.cselt.it>



