From owner-ietf-outbound  Sat Apr  1 01:01:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA25094
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 01:00:03 -0500 (EST)
Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25041
	for <ietf@ietf.org>; Sat, 1 Apr 2000 00:52:40 -0500 (EST)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id VAA00631;
	Fri, 31 Mar 2000 21:52:20 -0800 (PST)
Date: Fri, 31 Mar 2000 21:52:20 -0800 (PST)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200004010552.VAA00631@shell9.ba.best.com>
To: janet@W3.ORG
Subject: Re: HTML forms
Cc: ietf@ietf.org, www-html@W3.ORG
X-Loop: ietf@ietf.org

Janet,

Thank you for your reply correcting my error:

>>... The W3C... constrains meaningful debate to those
>> willing and able to pay US$50,000 per year.  
>
> That is not true, on a variety of counts. I'll name two.
> First, membership has two levels: full and affiliate. For
> more details, please refer to:
>   http://www.w3.org/Consortium/Prospectus/Joining

You are right.  I made a serious mistake that I wish you 
had replied directly and to the IETF in correcting. 
Affiliate-level membership costs only US$5,000 for 
nonprofit, government, and small businesses.  That means 
that the W3C has a membership fee income is well below the 
$20 million I mistakenly figured.  I wish I had known about 
affiliate membership two years ago.  Now, I would look 
forward to joining as an Affiliate, but after interacting 
with the HTML working group membership and leadership, it 
is clear that I am better off unaffiliated.

>... People have provided you with a thoughtful technical
> evaluation of your proposal....

That is true, but you refer to the comment addendum of 3rd 
March 2000 which only addresses the DEVICE attribute and 
neglects at least four related topics:  the two proposed 
multipart/form-data headers, the MAXTIME attribute, and the 
security considerations of the device upload draft.  As you 
are the official spokesperson of the W3C, I ask that those 
issues be addressed.  I have agreed not to bother 
Dr. Pemberton with these matters any further.  The HTML 
staff contact would seem to be the appropriate person to 
address the issues but has never done so after several 
direct requests over the past couple years.  So, who is the 
correct person to address these issues?

Also, please ask the advisory committee representatives 
from Recording for the Blind and Dyslexic and TIAA-CREF to 
contact me.

Cheers,
James Salsman



From owner-ietf-outbound  Sat Apr  1 04:51:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA07476
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 04:50:01 -0500 (EST)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA07453
	for <ietf@ietf.org>; Sat, 1 Apr 2000 04:46:46 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.05049-0@bells.cs.ucl.ac.uk>; Sat, 1 Apr 2000 10:46:27 +0100
To: Barbara Bao <yabao@utdallas.edu>
cc: ietf@ietf.org
Subject: Re: Topology Discovery in IP Networks
In-reply-to: Your message of "Thu, 30 Mar 2000 10:15:15 MDT." <38E37D93.DC410DCA@utdallas.edu>
Date: Sat, 01 Apr 2000 10:46:26 +0100
Message-ID: <1700.954582386@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


infocom 2000 had 2 sessions (8 papers) from the main people - check
out their web site (papers are online..ia ieee)
In message <38E37D93.DC410DCA@utdallas.edu>, Barbara Bao typed:

 >>Dear Friends,
 >>
 >>For my assignment, I need to know algorithms for discovering layer-3 and
 >>layer-2 network topology. Where can I find those papers? Any information
 >>and advice are highly appreciated.
 >>
 >>Barbara
 >>

 cheers

   jon



From owner-ietf-outbound  Sat Apr  1 06:01:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA08221
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 06:00:02 -0500 (EST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08161
	for <ietf@ietf.org>; Sat, 1 Apr 2000 05:50:31 -0500 (EST)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id FAA27783;
	Sat, 1 Apr 2000 05:50:30 -0500 (EST)
Sender: hgs@cs.columbia.edu
Message-ID: <38E5D476.EC066D65@cs.columbia.edu>
Date: Sat, 01 Apr 2000 05:50:30 -0500
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Graham Klyne <GK@Dial.pipex.com>
CC: ietf@ietf.org
Subject: Re: A thought about patents
References: <4.2.2.20000330230917.00c1b760@pop.dial.pipex.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

In looking in multimedia-related patents, I'm also utterly amazed by the
complete lack of citation of published technical articles or related
work (RFCs, Internet drafts, etc.). The problem with many patents is
that if submitted as a technical paper at even the lowliest conference,
it would be laughed out of the program. Maybe we need a peer review
(under suitable secrecy arrangements) of patent applications by real
experts, not the one patent examiner that seems to have missed the
existence of engineering libraries in his or her undergraduate
education.

Graham Klyne wrote:
> 
> As many of us are finding, it seems to become more and more difficult to
> develop or implement a standard without tripping over somebody-or-other's
> patent for some piece of technology that many of us would regard as fairly
> obvious or lacking in novelty.
> 
> The recent announcement from the U.S. Patent and Trademark Office about
> overhauling their scrutiny of applications for online business patents
> seems to imply a tacit acknowledgement that their is a problem with the
> review process with respect to discovery or prior art or determination of
> novelty in a claimed invention.
> 
> My thought is this:  I'd like to see a presumption of lack of novelty if an
> idea gets raised in a public forum, even if it happens _after_ a patent has
> been applied for, unless it can be shown that the information came from
> leakage of proprietary information.
> 
> Maybe such an approach might ameliorate the "gold rush" mentality to be the
> first to slap a patent on an idea or technique that is coming to be
> accepted art in the normal process of technology evolution.
> 


-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



From owner-ietf-outbound  Sat Apr  1 07:31:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA09013
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 07:30:02 -0500 (EST)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08967
	for <ietf@ietf.org>; Sat, 1 Apr 2000 07:25:23 -0500 (EST)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id HAA02985;
	Sat, 1 Apr 2000 07:23:04 -0500 (EST)
Sender: hgs@cs.columbia.edu
Message-ID: <38E5EA27.BC080E59@cs.columbia.edu>
Date: Sat, 01 Apr 2000 07:23:03 -0500
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: tccc@IEEE.ORG, ietf@ietf.org
CC: Harvey Freeman <HAFREEMAN@aol.com>
Subject: Conflict IEEE Infocom - IETF spring meeting
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

In recent years, IEEE Infocom (www.ieee-infocom.org) and the spring IETF
meeting have clashed repeatedly, including this year. IEEE Infocom is
scheduled several years in advance (through 2004 at this point), so it
is easy to avoid. I've brought up the topic in the past, but was told
that the number of people that were affected by this was just one or
two, so it's just one more of a thousand scheduling conflicts. From
conversations in Israel, it seems that the number of people affected has
grown substantially in the last few years. I'd like to have a better
idea whether this is indeed a real problem affecting core IETF
contributors, and assuming that this is indeed more than a peripheral
problem, at least let the IETF scheduling folks know about it. Thus,
please let me know if you are or have been affected by this scheduling
conflict. Thanks for your help.

Henning
-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



From owner-ietf-outbound  Sat Apr  1 14:57:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA11124
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 14:55:26 -0500 (EST)
Received: from web218.mail.yahoo.com (web218.mail.yahoo.com [128.11.68.118])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA10936
	for <IETF@ietf.org>; Sat, 1 Apr 2000 14:30:28 -0500 (EST)
Received: (qmail 10485 invoked by uid 60001); 1 Apr 2000 19:30:28 -0000
Message-ID: <20000401193028.10484.qmail@web218.mail.yahoo.com>
Received: from [216.185.31.129] by web218.mail.yahoo.com; Sat, 01 Apr 2000 11:30:28 PST
Date: Sat, 1 Apr 2000 11:30:28 -0800 (PST)
From: kysi ferul <redwingblakburdz@yahoo.com>
Subject:  "You have bad breath more often than you think!" 'Mannix'
To: IETF@ietf.org
Cc: nahoku@hotmail.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-412776091-954617428=:2142"
X-Loop: ietf@ietf.org

--0-412776091-954617428=:2142
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline



Note: forwarded message attached.


=====
redwingblakburdz@yahoo.com



__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--0-412776091-954617428=:2142
Content-Type: message/rfc822

X-Apparently-To: redwingblakburdz@yahoo.com via web201.mail.yahoo.com
X-Track2: 2
X-Track: -50
Received: from web1801.mail.yahoo.com (128.11.23.44)
  by mta226.mail.yahoo.com with SMTP; 1 Apr 2000 19:20:17 -0000
Received: (qmail 1439 invoked by uid 60001); 1 Apr 2000 19:20:17 -0000
Message-ID: <20000401192017.1438.qmail@web1801.mail.yahoo.com>
Received: from [216.185.31.129] by web1801.mail.yahoo.com; Sat, 01 Apr 2000 11:20:17 PST
Date: Sat, 1 Apr 2000 11:20:17 -0800 (PST)
From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
Subject: "You have bad breath more often than you think!" 'Mannix'
To: redwingblakburdz@yahoo.com
Cc: letters@bnp.net
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-135497281-954616817=:22608"
Content-Length: 13743

--0-135497281-954616817=:22608
Content-Type: multipart/alternative; boundary="0-511702305-954616817=:22608"

--0-511702305-954616817=:22608
Content-Type: text/plain; charset=us-ascii

  

Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

 This Letter and All Contents Copyright 1999 Casey Farrell
              All Rights Reserved


---------------------------------
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
--0-511702305-954616817=:22608
Content-Type: text/html; charset=us-ascii

 
 <BR><BR>Casey Farrell; Designer<br><br>oh_yeah_dot_net@yahoo.com<br><br> This Letter and All Contents Copyright 1999 Casey Farrell<br>              All Rights Reserved<p><br><hr size=1><b>Do You Yahoo!?</b><br>
Talk to your friends online with <a href="http://im.yahoo.com/">Yahoo! Messenger</a>.
--0-511702305-954616817=:22608--
--0-135497281-954616817=:22608
Content-Type: message/rfc822

Received: from [216.185.31.129] by web1805.mail.yahoo.com; Sat, 01 Apr 2000 11:17:13 PST
Date: Sat, 1 Apr 2000 11:17:13 -0800 (PST)
From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
Subject: "You have bad breath more often than you think!" 'Mannix'
To: nanog@merit.edu
Cc: wb8foz@nrk.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-846930886-954616633=:27884"
Content-Length: 12408

--0-846930886-954616633=:27884
Content-Type: multipart/alternative; boundary="0-1681692777-954616633=:27884"

--0-1681692777-954616633=:27884
Content-Type: text/plain; charset=us-ascii


That was a breath mint commercial by the actor who played the TV 'dick' MANNIX-and I hope I cc'd the right boxes here-this is in allusion to the fact that some of our 'bunkers' are doin' "God Knows WHAT?" Just as in Albania's red commie days-where there was a foxhole and machinegun nest outside of every human habitation, during the 'Cold War' the US and RUSSIA and their partners, went

on a building spree, and we don't today probably have a true accounting of where all the facilities are

that weren't 'decommissioned' PUBLICALLY-that is ANYONE...theoretically could be set-up LARGE in a "1984" kind-of East Berlin/OLD NIKE BASE situation, where 'they' could run their version of an

INTERNET/"memory-hole"...and there is a need to find and monitor ALL the "Hidden Places" in the'

ENTIRE world-find them, and '"spike-'em" or man the site with the reinvestment of new equiptment a 

mission statement, with goals, and work the 'cyber-space frontier' in an ecologicall- friendly manner.

 

There has probably never been another occasion in Man's history, outside of the cooperation myth of Babel, where the opportunities to 'FIX" certain 'LOGISTIC PROBLEM" were at hand, for our "Lost PLanet Airmen?"

Beside the obvious, which is a new call to some standards in education, what is very much needed now

is FULL-GOVERNMENT FUNDING for our  " 'Net Builders" recumbent only on a stipulation that their

work practices be above board and honest. We need tolerate NO more "hackers'" (Signal-'Jackers')

I am calling for the establishment of a new branch of the Armed Services to be a "SIGNAL CORP"

which will locate and remann those distant or hidden communications outposts, or complete put them out of commission, and NO 'CIVILIANS' should be "Authorised" to aquire these properties in the future! Instead of the US Federal Government 'privatising' Military Bases and Outposts, these lands

and buildings should revert to the park system, and the "SIGNAL CORP!" So that schools may benefit, ecology, and the technology! The CURRENT PRACTISE of letting "SCI-FI" writers, Hollywooders & 'puter whiz kids' (in fact just about ANYONE who has MONEY...) glom on to these

sites, has a few DANGEROUS drawbacks for a FREE SOCIETY! One...as with GUN CONTROL...

'you' are 'asking' good people to take it on the chin-for no reason! And more amazoningly, you are doing this after 'going up onto the mountain!' AMERICA is the LIGHT of the WORLD! AND not surprisingly there ALREADY are a LOT of STRANGE CHARACTERS out there trying to RUIN/RUN it

in GOVERNMENT...so to allow a CORPORATE entity...let alone PRIVATE INDIVIDUALS, who have

CORPORATIONS which are larger than MANY NATIONS...to let them have their 'way' with AIR WAVES? No, this is DUMB! The CHANNEL has to be protected, the MESSAGE can be' naughty.'

What must invariable follow if you allow "WINSTON" to run the WEB in your part of the STATE without SUPERVISION, is that he will start thinking in terms of 'getting creative' right where the

MONEY can be had. And that is the COMMONS! (See?) So, PUBLIC SERVICE (ARMED FORCES!)

is what a democracy pivots on. The 'force' here is to rectify the MULTIPLE MISTAKES of the past-

but more importantly resolve current conflicts which allow anymousities and jealousies to grow-while a

veritable cornucopia is available to the major population areas due to the consolidating effects of a

very fast communications system which enable commerce and supports lifestyle choices. Only one 

real matter must be addressed-just as in a society which is 'over policed' there is 'no possibility' for 'crime' so one lives in a very criminalised and dangerous culture-but in a scoiety which is lightly-but CORRECTLY policed, one has the POSSIBILTY of crime, but the numbers remain very low, because FREEDOM is it's OWN reward, the CITIZEN takes advantage of the BLESSINGS and a era of PEACE 

kicks-in,, the other culture has no dearth of turmoil, insurrection, and finally is disassembled. If we can get the Government to put ALL it's RESEARCH monies into the 'NET, and give PRIORITY to real

workers who love the darn thing, and pay them well what they're worth-and give them properties to go with the job, which they will share with Park Rangers, Professors, Scientists, etc.-the 'management' of these formerly CORRUPT areas will fall into line, and even former 'mobsters' can be 'pensioned off' at a rate-of-pay, or by REWARDS (Monetary Spoils) which will induce them to bring forward their many talents to the common good-(they can get to p;lay with their grandchildren at the beach!) we need ALL talents, but we have to hold some standards, and one might be that for the sdake of  DIVERSITY we may have to start to recognise the DIFFERENCES within the abilities of INDIVIDUALS and stop rewarding just those who can spin a good line of bullshit or who lift someone's property when they're not looking?

 Well, that's my suggestions for today-April 1st, our April Fools' Day, and have supplied a few fun reads here-reminding some of you that new proposals always sound a bit strange until you compare them to actual history-"Who knew......?"


Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

 This Letter and All Contents Copyright 1999 Casey Farrell
              All Rights Reserved


---------------------------------
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
--0-1681692777-954616633=:27884
Content-Type: text/html; charset=us-ascii

<P>That was a breath mint commercial by the actor who played the TV 'dick' MANNIX-and I hope I cc'd the right boxes here-this is in allusion to the fact that some of our 'bunkers' are doin' "God Knows WHAT?" Just as in Albania's red commie days-where there was a foxhole and machinegun nest outside of every human habitation, during the 'Cold War' the US and RUSSIA and their partners, went</P>
<P>on a building spree, and we don't today probably have a true accounting of where all the facilities are</P>
<P>that weren't 'decommissioned' PUBLICALLY-that is ANYONE...theoretically could be set-up LARGE in a "1984" kind-of East Berlin/OLD NIKE BASE situation, where 'they' could run their version of an</P>
<P>INTERNET/"memory-hole"...and there is a need to find and monitor ALL the "Hidden Places" in the'</P>
<P>ENTIRE world-find them, and '"spike-'em" or man the site with the reinvestment of new equiptment a </P>
<P>mission statement, with goals, and work the 'cyber-space frontier' in an ecologicall- friendly manner.</P>
<P>&nbsp;</P>
<P>There has probably never been another occasion in Man's history, outside of the cooperation myth of Babel, where the opportunities to 'FIX" certain 'LOGISTIC PROBLEM" were at hand, for our "Lost PLanet Airmen?"</P>
<P>Beside the obvious, which is a new call to some standards in education, what is very much needed now</P>
<P>is FULL-GOVERNMENT FUNDING for&nbsp;our&nbsp; " 'Net Builders" recumbent only on a stipulation that their</P>
<P>work practices be above board and honest. We need tolerate NO more "hackers'" (Signal-'Jackers')</P>
<P>I am calling for the establishment of a new branch of the Armed Services to be a "SIGNAL CORP"</P>
<P>which will locate and remann those distant or hidden communications outposts, or complete put them out of commission, and NO 'CIVILIANS' should be "Authorised" to aquire these properties in the future! Instead of the US Federal Government 'privatising' Military Bases and Outposts, these lands</P>
<P>and buildings should revert to the park system, and the "SIGNAL CORP!" So that schools may benefit, ecology, and the technology! The&nbsp;CURRENT PRACTISE of letting "SCI-FI" writers, Hollywooders&nbsp;&amp; 'puter whiz kids' (in fact just about ANYONE who has MONEY...) glom on to these</P>
<P>sites, has a few DANGEROUS drawbacks for a FREE SOCIETY! One...as with GUN CONTROL...</P>
<P>'you' are 'asking' good people to take it on the chin-for no reason! And more amazoningly, you are doing this after 'going up onto the mountain!' AMERICA is the LIGHT of the WORLD! AND not surprisingly there ALREADY are a LOT of STRANGE CHARACTERS out there trying to RUIN/RUN it</P>
<P>in GOVERNMENT...so to allow a CORPORATE entity...let alone PRIVATE INDIVIDUALS, who have</P>
<P>CORPORATIONS which are larger than MANY NATIONS...to let them have their 'way' with AIR WAVES? No, this is DUMB! The CHANNEL has to be protected, the MESSAGE can be' naughty.'</P>
<P>What must invariable follow if you allow "WINSTON" to run the WEB in your part of the STATE without SUPERVISION, is that he will start thinking in terms of 'getting creative' right where the</P>
<P>MONEY can be had. And that is the COMMONS! (See?) So, PUBLIC SERVICE (ARMED FORCES!)</P>
<P>is what a democracy pivots on. The 'force' here is to rectify the MULTIPLE MISTAKES of the past-</P>
<P>but more importantly resolve current conflicts which allow anymousities and jealousies to grow-while a</P>
<P>veritable cornucopia is available to the major population areas due to the consolidating effects of a</P>
<P>very fast communications system which enable commerce and supports lifestyle choices. Only one </P>
<P>real matter must be addressed-just as in a society which is 'over policed' there is 'no possibility' for 'crime' so one lives in a very criminalised and dangerous culture-but in a scoiety which is lightly-but CORRECTLY policed, one has the POSSIBILTY of crime, but the numbers remain very low, because FREEDOM is it's OWN reward, the CITIZEN takes advantage of the BLESSINGS and a era of PEACE </P>
<P>kicks-in,, the other culture has no dearth of turmoil, insurrection, and finally is disassembled. If we can get the Government to put ALL it's RESEARCH monies into the 'NET, and give PRIORITY to real</P>
<P>workers who love the darn thing, and pay them well what they're worth-and give them properties to go with the job, which they will share with Park Rangers, Professors, Scientists, etc.-the 'management' of these formerly CORRUPT areas will fall into line, and even former 'mobsters' can be 'pensioned off' at a rate-of-pay, or by REWARDS (Monetary Spoils) which will induce them to bring forward their many talents to the common good-(they can get to p;lay with their grandchildren at the beach!) we need ALL talents, but we have to hold some standards, and one might be that for the sdake of&nbsp; DIVERSITY we may have to start to recognise the DIFFERENCES within the abilities of INDIVIDUALS and stop rewarding just those who can spin a good line of bullshit or who lift someone's property when they're not looking?</P>
<P>&nbsp;Well, that's my suggestions for today-April 1st, our April Fools' Day, and have supplied a few fun reads here-reminding some of you that new proposals always sound a bit strange until you compare them to actual history-"Who knew......?"</P><BR><BR>Casey Farrell; Designer<br><br>oh_yeah_dot_net@yahoo.com<br><br> This Letter and All Contents Copyright 1999 Casey Farrell<br>              All Rights Reserved<p><br><hr size=1><b>Do You Yahoo!?</b><br>
Talk to your friends online with <a href="http://im.yahoo.com/">Yahoo! Messenger</a>.
--0-1681692777-954616633=:27884--
--0-846930886-954616633=:27884
Content-Type: message/rfc822

X-Apparently-To: oh_yeah_dot_net@yahoo.com via web1806.mail.yahoo.com
X-Track2: 2
X-Track: -50
Received: from ef.egroups.com (207.138.41.172)
  by mta124.mail.yahoo.com with SMTP; 31 Mar 2000 02:24:02 -0000
X-eGroups-Return: greenjacks@hotmail.com
Received: from [10.1.2.124] by ef.egroups.com with NNFMP; 31 Mar 2000 02:22:41 -0000
Date: Thu, 30 Mar 2000 18:22:33 -0800
From: "Abner Greenjacks" <greenjacks@hotmail.com>
To: oh_yeah_dot_net@yahoo.com
Subject: Strict laws on Encryption for Military Bandwidths
Message-ID: <8c1259$405b@eGroups.com>
User-Agent: eGroups-EW/0.82
Content-Length: 366
X-Mailer: eGroups Message Poster
MIME-Version: 1.0

 
Begin forwarded message:

"They'll yub old navy fo this!" "Hey'll buy any load of iths!" "Yhe'..

http://www.codoh.com/bbs/messages/97.html
http://www.codoh.com/bbs/messages/109.html
http://www.codoh.com/bbs/messages/106.html
http://www.codoh.com/bbs/messages/62.html

Read at leisure for rollicking laughs!
______________________________________________________


--0-846930886-954616633=:27884--

--0-135497281-954616817=:22608--

--0-412776091-954617428=:2142--



From owner-ietf-outbound  Sat Apr  1 14:57:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA11089
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 14:53:40 -0500 (EST)
Received: from web218.mail.yahoo.com (web218.mail.yahoo.com [128.11.68.118])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA10936
	for <IETF@ietf.org>; Sat, 1 Apr 2000 14:30:28 -0500 (EST)
Received: (qmail 10485 invoked by uid 60001); 1 Apr 2000 19:30:28 -0000
Message-ID: <20000401193028.10484.qmail@web218.mail.yahoo.com>
Received: from [216.185.31.129] by web218.mail.yahoo.com; Sat, 01 Apr 2000 11:30:28 PST
Date: Sat, 1 Apr 2000 11:30:28 -0800 (PST)
From: kysi ferul <redwingblakburdz@yahoo.com>
Subject:  "You have bad breath more often than you think!" 'Mannix'
To: IETF@ietf.org
Cc: nahoku@hotmail.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-412776091-954617428=:2142"
X-Loop: ietf@ietf.org

--0-412776091-954617428=:2142
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline



Note: forwarded message attached.


=====
redwingblakburdz@yahoo.com



__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--0-412776091-954617428=:2142
Content-Type: message/rfc822

X-Apparently-To: redwingblakburdz@yahoo.com via web201.mail.yahoo.com
X-Track2: 2
X-Track: -50
Received: from web1801.mail.yahoo.com (128.11.23.44)
  by mta226.mail.yahoo.com with SMTP; 1 Apr 2000 19:20:17 -0000
Received: (qmail 1439 invoked by uid 60001); 1 Apr 2000 19:20:17 -0000
Message-ID: <20000401192017.1438.qmail@web1801.mail.yahoo.com>
Received: from [216.185.31.129] by web1801.mail.yahoo.com; Sat, 01 Apr 2000 11:20:17 PST
Date: Sat, 1 Apr 2000 11:20:17 -0800 (PST)
From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
Subject: "You have bad breath more often than you think!" 'Mannix'
To: redwingblakburdz@yahoo.com
Cc: letters@bnp.net
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-135497281-954616817=:22608"
Content-Length: 13743

--0-135497281-954616817=:22608
Content-Type: multipart/alternative; boundary="0-511702305-954616817=:22608"

--0-511702305-954616817=:22608
Content-Type: text/plain; charset=us-ascii

  

Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

 This Letter and All Contents Copyright 1999 Casey Farrell
              All Rights Reserved


---------------------------------
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
--0-511702305-954616817=:22608
Content-Type: text/html; charset=us-ascii

 
 <BR><BR>Casey Farrell; Designer<br><br>oh_yeah_dot_net@yahoo.com<br><br> This Letter and All Contents Copyright 1999 Casey Farrell<br>              All Rights Reserved<p><br><hr size=1><b>Do You Yahoo!?</b><br>
Talk to your friends online with <a href="http://im.yahoo.com/">Yahoo! Messenger</a>.
--0-511702305-954616817=:22608--
--0-135497281-954616817=:22608
Content-Type: message/rfc822

Received: from [216.185.31.129] by web1805.mail.yahoo.com; Sat, 01 Apr 2000 11:17:13 PST
Date: Sat, 1 Apr 2000 11:17:13 -0800 (PST)
From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
Subject: "You have bad breath more often than you think!" 'Mannix'
To: nanog@merit.edu
Cc: wb8foz@nrk.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-846930886-954616633=:27884"
Content-Length: 12408

--0-846930886-954616633=:27884
Content-Type: multipart/alternative; boundary="0-1681692777-954616633=:27884"

--0-1681692777-954616633=:27884
Content-Type: text/plain; charset=us-ascii


That was a breath mint commercial by the actor who played the TV 'dick' MANNIX-and I hope I cc'd the right boxes here-this is in allusion to the fact that some of our 'bunkers' are doin' "God Knows WHAT?" Just as in Albania's red commie days-where there was a foxhole and machinegun nest outside of every human habitation, during the 'Cold War' the US and RUSSIA and their partners, went

on a building spree, and we don't today probably have a true accounting of where all the facilities are

that weren't 'decommissioned' PUBLICALLY-that is ANYONE...theoretically could be set-up LARGE in a "1984" kind-of East Berlin/OLD NIKE BASE situation, where 'they' could run their version of an

INTERNET/"memory-hole"...and there is a need to find and monitor ALL the "Hidden Places" in the'

ENTIRE world-find them, and '"spike-'em" or man the site with the reinvestment of new equiptment a 

mission statement, with goals, and work the 'cyber-space frontier' in an ecologicall- friendly manner.

 

There has probably never been another occasion in Man's history, outside of the cooperation myth of Babel, where the opportunities to 'FIX" certain 'LOGISTIC PROBLEM" were at hand, for our "Lost PLanet Airmen?"

Beside the obvious, which is a new call to some standards in education, what is very much needed now

is FULL-GOVERNMENT FUNDING for our  " 'Net Builders" recumbent only on a stipulation that their

work practices be above board and honest. We need tolerate NO more "hackers'" (Signal-'Jackers')

I am calling for the establishment of a new branch of the Armed Services to be a "SIGNAL CORP"

which will locate and remann those distant or hidden communications outposts, or complete put them out of commission, and NO 'CIVILIANS' should be "Authorised" to aquire these properties in the future! Instead of the US Federal Government 'privatising' Military Bases and Outposts, these lands

and buildings should revert to the park system, and the "SIGNAL CORP!" So that schools may benefit, ecology, and the technology! The CURRENT PRACTISE of letting "SCI-FI" writers, Hollywooders & 'puter whiz kids' (in fact just about ANYONE who has MONEY...) glom on to these

sites, has a few DANGEROUS drawbacks for a FREE SOCIETY! One...as with GUN CONTROL...

'you' are 'asking' good people to take it on the chin-for no reason! And more amazoningly, you are doing this after 'going up onto the mountain!' AMERICA is the LIGHT of the WORLD! AND not surprisingly there ALREADY are a LOT of STRANGE CHARACTERS out there trying to RUIN/RUN it

in GOVERNMENT...so to allow a CORPORATE entity...let alone PRIVATE INDIVIDUALS, who have

CORPORATIONS which are larger than MANY NATIONS...to let them have their 'way' with AIR WAVES? No, this is DUMB! The CHANNEL has to be protected, the MESSAGE can be' naughty.'

What must invariable follow if you allow "WINSTON" to run the WEB in your part of the STATE without SUPERVISION, is that he will start thinking in terms of 'getting creative' right where the

MONEY can be had. And that is the COMMONS! (See?) So, PUBLIC SERVICE (ARMED FORCES!)

is what a democracy pivots on. The 'force' here is to rectify the MULTIPLE MISTAKES of the past-

but more importantly resolve current conflicts which allow anymousities and jealousies to grow-while a

veritable cornucopia is available to the major population areas due to the consolidating effects of a

very fast communications system which enable commerce and supports lifestyle choices. Only one 

real matter must be addressed-just as in a society which is 'over policed' there is 'no possibility' for 'crime' so one lives in a very criminalised and dangerous culture-but in a scoiety which is lightly-but CORRECTLY policed, one has the POSSIBILTY of crime, but the numbers remain very low, because FREEDOM is it's OWN reward, the CITIZEN takes advantage of the BLESSINGS and a era of PEACE 

kicks-in,, the other culture has no dearth of turmoil, insurrection, and finally is disassembled. If we can get the Government to put ALL it's RESEARCH monies into the 'NET, and give PRIORITY to real

workers who love the darn thing, and pay them well what they're worth-and give them properties to go with the job, which they will share with Park Rangers, Professors, Scientists, etc.-the 'management' of these formerly CORRUPT areas will fall into line, and even former 'mobsters' can be 'pensioned off' at a rate-of-pay, or by REWARDS (Monetary Spoils) which will induce them to bring forward their many talents to the common good-(they can get to p;lay with their grandchildren at the beach!) we need ALL talents, but we have to hold some standards, and one might be that for the sdake of  DIVERSITY we may have to start to recognise the DIFFERENCES within the abilities of INDIVIDUALS and stop rewarding just those who can spin a good line of bullshit or who lift someone's property when they're not looking?

 Well, that's my suggestions for today-April 1st, our April Fools' Day, and have supplied a few fun reads here-reminding some of you that new proposals always sound a bit strange until you compare them to actual history-"Who knew......?"


Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

 This Letter and All Contents Copyright 1999 Casey Farrell
              All Rights Reserved


---------------------------------
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
--0-1681692777-954616633=:27884
Content-Type: text/html; charset=us-ascii

<P>That was a breath mint commercial by the actor who played the TV 'dick' MANNIX-and I hope I cc'd the right boxes here-this is in allusion to the fact that some of our 'bunkers' are doin' "God Knows WHAT?" Just as in Albania's red commie days-where there was a foxhole and machinegun nest outside of every human habitation, during the 'Cold War' the US and RUSSIA and their partners, went</P>
<P>on a building spree, and we don't today probably have a true accounting of where all the facilities are</P>
<P>that weren't 'decommissioned' PUBLICALLY-that is ANYONE...theoretically could be set-up LARGE in a "1984" kind-of East Berlin/OLD NIKE BASE situation, where 'they' could run their version of an</P>
<P>INTERNET/"memory-hole"...and there is a need to find and monitor ALL the "Hidden Places" in the'</P>
<P>ENTIRE world-find them, and '"spike-'em" or man the site with the reinvestment of new equiptment a </P>
<P>mission statement, with goals, and work the 'cyber-space frontier' in an ecologicall- friendly manner.</P>
<P>&nbsp;</P>
<P>There has probably never been another occasion in Man's history, outside of the cooperation myth of Babel, where the opportunities to 'FIX" certain 'LOGISTIC PROBLEM" were at hand, for our "Lost PLanet Airmen?"</P>
<P>Beside the obvious, which is a new call to some standards in education, what is very much needed now</P>
<P>is FULL-GOVERNMENT FUNDING for&nbsp;our&nbsp; " 'Net Builders" recumbent only on a stipulation that their</P>
<P>work practices be above board and honest. We need tolerate NO more "hackers'" (Signal-'Jackers')</P>
<P>I am calling for the establishment of a new branch of the Armed Services to be a "SIGNAL CORP"</P>
<P>which will locate and remann those distant or hidden communications outposts, or complete put them out of commission, and NO 'CIVILIANS' should be "Authorised" to aquire these properties in the future! Instead of the US Federal Government 'privatising' Military Bases and Outposts, these lands</P>
<P>and buildings should revert to the park system, and the "SIGNAL CORP!" So that schools may benefit, ecology, and the technology! The&nbsp;CURRENT PRACTISE of letting "SCI-FI" writers, Hollywooders&nbsp;&amp; 'puter whiz kids' (in fact just about ANYONE who has MONEY...) glom on to these</P>
<P>sites, has a few DANGEROUS drawbacks for a FREE SOCIETY! One...as with GUN CONTROL...</P>
<P>'you' are 'asking' good people to take it on the chin-for no reason! And more amazoningly, you are doing this after 'going up onto the mountain!' AMERICA is the LIGHT of the WORLD! AND not surprisingly there ALREADY are a LOT of STRANGE CHARACTERS out there trying to RUIN/RUN it</P>
<P>in GOVERNMENT...so to allow a CORPORATE entity...let alone PRIVATE INDIVIDUALS, who have</P>
<P>CORPORATIONS which are larger than MANY NATIONS...to let them have their 'way' with AIR WAVES? No, this is DUMB! The CHANNEL has to be protected, the MESSAGE can be' naughty.'</P>
<P>What must invariable follow if you allow "WINSTON" to run the WEB in your part of the STATE without SUPERVISION, is that he will start thinking in terms of 'getting creative' right where the</P>
<P>MONEY can be had. And that is the COMMONS! (See?) So, PUBLIC SERVICE (ARMED FORCES!)</P>
<P>is what a democracy pivots on. The 'force' here is to rectify the MULTIPLE MISTAKES of the past-</P>
<P>but more importantly resolve current conflicts which allow anymousities and jealousies to grow-while a</P>
<P>veritable cornucopia is available to the major population areas due to the consolidating effects of a</P>
<P>very fast communications system which enable commerce and supports lifestyle choices. Only one </P>
<P>real matter must be addressed-just as in a society which is 'over policed' there is 'no possibility' for 'crime' so one lives in a very criminalised and dangerous culture-but in a scoiety which is lightly-but CORRECTLY policed, one has the POSSIBILTY of crime, but the numbers remain very low, because FREEDOM is it's OWN reward, the CITIZEN takes advantage of the BLESSINGS and a era of PEACE </P>
<P>kicks-in,, the other culture has no dearth of turmoil, insurrection, and finally is disassembled. If we can get the Government to put ALL it's RESEARCH monies into the 'NET, and give PRIORITY to real</P>
<P>workers who love the darn thing, and pay them well what they're worth-and give them properties to go with the job, which they will share with Park Rangers, Professors, Scientists, etc.-the 'management' of these formerly CORRUPT areas will fall into line, and even former 'mobsters' can be 'pensioned off' at a rate-of-pay, or by REWARDS (Monetary Spoils) which will induce them to bring forward their many talents to the common good-(they can get to p;lay with their grandchildren at the beach!) we need ALL talents, but we have to hold some standards, and one might be that for the sdake of&nbsp; DIVERSITY we may have to start to recognise the DIFFERENCES within the abilities of INDIVIDUALS and stop rewarding just those who can spin a good line of bullshit or who lift someone's property when they're not looking?</P>
<P>&nbsp;Well, that's my suggestions for today-April 1st, our April Fools' Day, and have supplied a few fun reads here-reminding some of you that new proposals always sound a bit strange until you compare them to actual history-"Who knew......?"</P><BR><BR>Casey Farrell; Designer<br><br>oh_yeah_dot_net@yahoo.com<br><br> This Letter and All Contents Copyright 1999 Casey Farrell<br>              All Rights Reserved<p><br><hr size=1><b>Do You Yahoo!?</b><br>
Talk to your friends online with <a href="http://im.yahoo.com/">Yahoo! Messenger</a>.
--0-1681692777-954616633=:27884--
--0-846930886-954616633=:27884
Content-Type: message/rfc822

X-Apparently-To: oh_yeah_dot_net@yahoo.com via web1806.mail.yahoo.com
X-Track2: 2
X-Track: -50
Received: from ef.egroups.com (207.138.41.172)
  by mta124.mail.yahoo.com with SMTP; 31 Mar 2000 02:24:02 -0000
X-eGroups-Return: greenjacks@hotmail.com
Received: from [10.1.2.124] by ef.egroups.com with NNFMP; 31 Mar 2000 02:22:41 -0000
Date: Thu, 30 Mar 2000 18:22:33 -0800
From: "Abner Greenjacks" <greenjacks@hotmail.com>
To: oh_yeah_dot_net@yahoo.com
Subject: Strict laws on Encryption for Military Bandwidths
Message-ID: <8c1259$405b@eGroups.com>
User-Agent: eGroups-EW/0.82
Content-Length: 366
X-Mailer: eGroups Message Poster
MIME-Version: 1.0

 
Begin forwarded message:

"They'll yub old navy fo this!" "Hey'll buy any load of iths!" "Yhe'..

http://www.codoh.com/bbs/messages/97.html
http://www.codoh.com/bbs/messages/109.html
http://www.codoh.com/bbs/messages/106.html
http://www.codoh.com/bbs/messages/62.html

Read at leisure for rollicking laughs!
______________________________________________________


--0-846930886-954616633=:27884--

--0-135497281-954616817=:22608--

--0-412776091-954617428=:2142--



From owner-ietf-outbound  Sat Apr  1 16:42:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA11779
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 16:40:01 -0500 (EST)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11756
	for <ietf@ietf.org>; Sat, 1 Apr 2000 16:36:21 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.22395-0@bells.cs.ucl.ac.uk>; Sat, 1 Apr 2000 22:36:09 +0100
To: Graham Klyne <GK@Dial.pipex.com>
cc: ietf@ietf.org
Subject: Re: A thought about patents
In-reply-to: Your message of "Thu, 30 Mar 2000 23:18:31 BST." <4.2.2.20000330230917.00c1b760@pop.dial.pipex.com>
Date: Sat, 01 Apr 2000 22:36:08 +0100
Message-ID: <11419.954624968@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


 >>My thought is this:  I'd like to see a presumption of lack of novelty if an 
 >>idea gets raised in a public forum, even if it happens _after_ a patent has 
 >>been applied for, unless it can be shown that the information came from 
 >>leakage of proprietary information.
 
intersting idea

i would liek to offer another:-

perhaps the length of patent protection should be directly related to
the cost of developing an idea - in pharmaceutical industry, long
patents make sense because of the large investment in testing a new
drug safely - similar i nthe automotive and aero industries

in software, its pretty obvious that this is silly - one-klik took
someone about 6 nanoseconds to think up, and 3 to test...

 >>Maybe such an approach might ameliorate the "gold rush" mentality to be the 
 >>first to slap a patent on an idea or technique that is coming to be 
 >>accepted art in the normal process of technology evolution.

the ietf has a very good protection in principle against people who
think that a patent is power to "own" a standard - it would be nice
to try to identify the mistaken "stakeholders" who belive that 
patents are a weapon...
 

 cheers

   jon



From owner-ietf-outbound  Sat Apr  1 17:52:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA12177
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 17:50:02 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12132
	for <ietf@ietf.org>; Sat, 1 Apr 2000 17:41:49 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id PAA20994
	for ietf@ietf.org  env-from <vjs>;
	Sat, 1 Apr 2000 15:41:50 -0700 (MST)
Date: Sat, 1 Apr 2000 15:41:50 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004012241.PAA20994@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: A thought about patents
X-Loop: ietf@ietf.org

> From: Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>


> ...
> perhaps the length of patent protection should be directly related to
> the cost of developing an idea - in pharmaceutical industry, long
> patents make sense because of the large investment in testing a new
> drug safely - similar i nthe automotive and aero industries
>
> in software, its pretty obvious that this is silly - one-klik took
> someone about 6 nanoseconds to think up, and 3 to test...

Why should it a priori take decades to check an idea in the automotive
industry but seconds in the computer industry?  What about overlapping
areas, such as computer networks in cars?
Would you have the same people checking the claims of how much it cost
to develop an idea that now check the technical claims, including those
who checked http://patent.womplex.ibm.com/details?&pn=US05446889__ and
http://www.patents.ibm.com/details?&pn=US06025810__&s_all=1#23
(The main purpose of "6025810: Hyper-light-speed antenna" is "to allow
signals to travel great distances at many times the speed of light.")

Patents have been a dire mess for more than 100 years.  Look at the
patent games played with firearms 125 years ago.  Consider the "defensive
patents" in the ink jet printer business in the last 20 years.


> ...
> the ietf has a very good protection in principle against people who
> think that a patent is power to "own" a standard 

"Protection in principle" is right, as plenty of experience in the
IETF demonstrates.  I care a lot more about protections in practice.

>                                                    it would be nice
> to try to identify the mistaken "stakeholders" who belive that 
> patents are a weapon...

The only mistake I see is the idea that patents are other
than very effective weapons.  It sounds like an insane idea to
anyone who reads a newspaper.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Sat Apr  1 18:31:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA12383
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 18:30:02 -0500 (EST)
Received: from mail.hol.gr (mail.hol.gr [194.30.192.21])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA12356
	for <ietf@ietf.org>; Sat, 1 Apr 2000 18:24:37 -0500 (EST)
Received: (qmail 2947 invoked from network); 1 Apr 2000 23:24:15 -0000
Received: from vdp155.ath02.cas.hol.gr (HELO dawn.pipis) (root@195.97.2.156)
  by mail.hol.gr with SMTP; 1 Apr 2000 23:24:15 -0000
Received: from localhost (stephanos@localhost)
	by dawn.pipis (8.9.3/8.9.3) with ESMTP id CAA04713;
	Sun, 2 Apr 2000 02:25:07 +0300
X-Authentication-Warning: dawn.pipis: stephanos owned process doing -bs
Date: Sun, 2 Apr 2000 02:25:06 +0300 (EEST)
From: Stephanos Piperoglou <stephanos@webreference.com>
Sender: stephanos@dawn.pipis
To: "James P. Salsman" <bovik@best.com>
cc: Harald@Alvestrand.no, ietf@ietf.org, www-forms@W3.ORG, www-html@W3.ORG
Subject: Re: HTML forms
In-Reply-To: <200003302103.NAA06774@shell9.ba.best.com>
Message-ID: <Pine.LNX.4.10.10004020144230.4352-100000@dawn.pipis>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Thu, 30 Mar 2000, James P. Salsman wrote:

> The proposal would involve ammending the registration of the
> text/html media type, incorporating the W3C standards extended with
> two attributes of the INPUT element, DEVICE and MAXTIME.

Last time I checked, IANA, and not the IETF, controls the definitions
of Media Types. The entry for text/html [1] says, simply "See RFC
1866". And RFC 1866 [2] is a more or less verbatim copy of the HTML
2.0 Specification (which I couldn't find on w3.org, not that I spent
all that long looking). If it's so important to you that this changes,
I'd suggest you first get working at making this point to HTML 4.01 or
even (shock horror) XHTML 1.0. You can work out extensions later on.

[1] http://www.isi.edu/in-notes/iana/assignments/media-types/text/html
[2] http://www.ietf.org/rfc/rfc1866.txt?number=1866

Oh, and, BTW, extending the spec with two attributes isn't going to be
all that simple. You need detailed definitions, changes to DTDs, and
more. If you have these details, it would be nice to point us all to a
proposal so we know how "DEVICE" and "MAXTIME" would work.

> I understand that.  There might be substantial benefits from
> reconsidering those opinions.  Within the IETF, public debate is
> assured on almost all controversial matters.  The W3C, however,
> constrains meaningful debate to those willing and able to pay
> US$50,000 per year.

OK, maybe 50k is a bit extreme, but do you *really* have a problem
with the W3C's openness? I've been on this list for oh, about 5 years
and I've seen public debate about issues so ridiculous you wouldn't
believe. If I could point out one flaw in the whole W3C process, it's
that "standardization" comes before implementation. Which is not
really a problem, it's a big HINT you should take: The W3C is *NOT* a
standardization body! It comes up with specifications that it
recommends others should try to follow. Software Engineering 101,
people: Specification comes *BEFORE* implementation. And who is more
capable of creating specs but the people that are going to implement
them?

Cover your sensitive parts, because you're about to be hit by a big
cluestick. The W3C is a place where the people who write the software
for the Web come together, come up with common technologies, SUBMIT
THEM TO PUBLIC REVIEW, adjust them according to comments, then
implement them. It's not, I repeat NOT a standardization body.

> I agree that there was a point in the early development of web
> standards when that constraint was beneficial. 

Where you around back then? Do you remember anybody giving a flipping
f*** about the W3C? I was, and I remember software makers making HTML
user agents they just extended as they went along. On their own. And
we got incompatibilities. And the mess we have today.

> Now, however, with Netscape owned by a company shipping MSIE

Why is it that so many people still suffer from the delusion that
Microsoft and Netscape are the only members of the W3C? Especially
today when at least one of them no longer specifically *plans* to
break W3C specs, and the other one seems to be pressured to be the
same due to the competition, does it even matter?

>, and the stagnation or regression of the core HTML standards

Core HTML Standards? Oh, you must mean ISO-HTML. But I'm going to go
out on a limb here and assume you meant "HTML-related recommendations"
instead of "HTML Standards". In which case please go to the W3C's
Technical Reports and Publications page [4] and point out this
"stagnation or regression" that is plaguing the Web.

[4] http://www.w3.org/TR/

> along with the concerns raised in Norman Solomon's article,

WHAT CONCERNS, and HOW DO THEY RELATE TO THIS DISCUSSION? The press
dumped one dumb buzzword and adopted another. The big bad corporate
bogeyman is coming to getcha. Lay your paranoia aside, Fox. If you
want a rest, stop thinking about what business has done to the Web
(expand it and promote the need for interopability, which is an
absolute requirement for growth in a network world, and businesses
LOVE growth) and think about what the Web has done to business
(lowered barriers of entry, promoted globalization, created new
markets and generally levelled the playing field).

> I believe the time has come to return certain aspects of the control
> of HTML to the IETF.

The IETF never controlled HTML. The only people that ever controlled
HTML are those that write the software that uses it. They just decided
to come together and co-operate. Hence the W3C.

> Even if that view is not shared by the IETF, I the only way I would
> not be certain that a debate on the topic would be healthy for the
> Internet communty would be if the W3C were to take an affirmative
> stand on issues involving microphone upload for language instruction
> and asyncronous audio conferencing.

We've HAD this technical discussion here AGES ago. Create a form, give
it an accept type of audio/whatever and let the user agent bother
about how to get it. If that's too primitive for your needs, go and
create a separate protocol. I'm sick and tired of people trying to
extend HTML to do everything from boiling an egg to making
coffee. It's bad enough that HTML is a user interface language in the
first place (South Park fans, sing along: "Blame Mosaic! Blaim
Mosaic!") instead of developers getting a clue and just created an
extensible embedding mechanism in HTML years ago and worked on
complementary technologies to facilitate the creation of "DHTML
Applications".

Next time, before you post such an inflammatory message to a public
mailing list, please do your homework. What you are proposing is
altering a decision-making mechanism that does NOT work as you think
it does to accomplish something completely meaningless. HTML is the
HyperText Markup Language. Before you start another hopeless campaign
against the capitalist oppressors in your head, at least enlighten the
rest of usas to how Microphones and HyperText are related in any way.

I'll shut up now.

-- 
Stephanos Piperoglou                              <stephanos@webreference.com>
Maintainer, HTML with Style                    <http://webreference.com/html/>
  Visit HTML with Style for online HTML and CSS tutorials with step-by-step
   procedures and practical examples to help you author Web pages that are
 full-featured, standards-compliant and backwards-compatible, tools to make a
 Web author's life easier, software reviews, opinions, industry news and more



From owner-ietf-outbound  Sat Apr  1 19:21:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA12732
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 19:20:02 -0500 (EST)
Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12686
	for <ietf@ietf.org>; Sat, 1 Apr 2000 19:12:03 -0500 (EST)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id QAA03185;
	Sat, 1 Apr 2000 16:11:39 -0800 (PST)
Date: Sat, 1 Apr 2000 16:11:39 -0800 (PST)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200004020011.QAA03185@shell9.ba.best.com>
To: stephanos@webreference.com
Subject: Re: HTML forms
Cc: ietf@ietf.org, www-html@W3.ORG
In-Reply-To: <Pine.LNX.4.10.10004020144230.4352-100000@dawn.pipis>
X-Loop: ietf@ietf.org

From stephanos@webreference.com Sat Apr  1 15:25:32 2000
Date: Sun, 2 Apr 2000 02:25:06 +0300 (EEST)
From: Stephanos Piperoglou <stephanos@webreference.com>
To: "James P. Salsman" <bovik@best.com>
cc: Harald@Alvestrand.no, ietf@ietf.org, www-forms@w3.org, www-html@w3.org
Subject: Re: HTML forms

On Thu, 30 Mar 2000, James P. Salsman wrote:

> The proposal would involve ammending the registration of the
> text/html media type, incorporating the W3C standards extended with
> two attributes of the INPUT element, DEVICE and MAXTIME.

Last time I checked, IANA, and not the IETF, controls the definitions
of Media Types. The entry for text/html [1] says, simply "See RFC
1866". And RFC 1866 [2] is a more or less verbatim copy of the HTML
2.0 Specification (which I couldn't find on w3.org, not that I spent
all that long looking). If it's so important to you that this changes,
I'd suggest you first get working at making this point to HTML 4.01 or
even (shock horror) XHTML 1.0. You can work out extensions later on.

[1] http://www.isi.edu/in-notes/iana/assignments/media-types/text/html
[2] http://www.ietf.org/rfc/rfc1866.txt?number=1866

Oh, and, BTW, extending the spec with two attributes isn't going to be
all that simple. You need detailed definitions, changes to DTDs, and
more. If you have these details, it would be nice to point us all to a
proposal so we know how "DEVICE" and "MAXTIME" would work.

> I understand that.  There might be substantial benefits from
> reconsidering those opinions.  Within the IETF, public debate is
> assured on almost all controversial matters.  The W3C, however,
> constrains meaningful debate to those willing and able to pay
> US$50,000 per year.

OK, maybe 50k is a bit extreme, but do you *really* have a problem
with the W3C's openness? I've been on this list for oh, about 5 years
and I've seen public debate about issues so ridiculous you wouldn't
believe. If I could point out one flaw in the whole W3C process, it's
that "standardization" comes before implementation. Which is not
really a problem, it's a big HINT you should take: The W3C is *NOT* a
standardization body! It comes up with specifications that it
recommends others should try to follow. Software Engineering 101,
people: Specification comes *BEFORE* implementation. And who is more
capable of creating specs but the people that are going to implement
them?

Cover your sensitive parts, because you're about to be hit by a big
cluestick. The W3C is a place where the people who write the software
for the Web come together, come up with common technologies, SUBMIT
THEM TO PUBLIC REVIEW, adjust them according to comments, then
implement them. It's not, I repeat NOT a standardization body.

> I agree that there was a point in the early development of web
> standards when that constraint was beneficial. 

Where you around back then? Do you remember anybody giving a flipping
f*** about the W3C? I was, and I remember software makers making HTML
user agents they just extended as they went along. On their own. And
we got incompatibilities. And the mess we have today.

> Now, however, with Netscape owned by a company shipping MSIE

Why is it that so many people still suffer from the delusion that
Microsoft and Netscape are the only members of the W3C? Especially
today when at least one of them no longer specifically *plans* to
break W3C specs, and the other one seems to be pressured to be the
same due to the competition, does it even matter?

>, and the stagnation or regression of the core HTML standards

Core HTML Standards? Oh, you must mean ISO-HTML. But I'm going to go
out on a limb here and assume you meant "HTML-related recommendations"
instead of "HTML Standards". In which case please go to the W3C's
Technical Reports and Publications page [4] and point out this
"stagnation or regression" that is plaguing the Web.

[4] http://www.w3.org/TR/

> along with the concerns raised in Norman Solomon's article,

WHAT CONCERNS, and HOW DO THEY RELATE TO THIS DISCUSSION? The press
dumped one dumb buzzword and adopted another. The big bad corporate
bogeyman is coming to getcha. Lay your paranoia aside, Fox. If you
want a rest, stop thinking about what business has done to the Web
(expand it and promote the need for interopability, which is an
absolute requirement for growth in a network world, and businesses
LOVE growth) and think about what the Web has done to business
(lowered barriers of entry, promoted globalization, created new
markets and generally levelled the playing field).

> I believe the time has come to return certain aspects of the control
> of HTML to the IETF.

The IETF never controlled HTML. The only people that ever controlled
HTML are those that write the software that uses it. They just decided
to come together and co-operate. Hence the W3C.

> Even if that view is not shared by the IETF, I the only way I would
> not be certain that a debate on the topic would be healthy for the
> Internet communty would be if the W3C were to take an affirmative
> stand on issues involving microphone upload for language instruction
> and asyncronous audio conferencing.

We've HAD this technical discussion here AGES ago. Create a form, give
it an accept type of audio/whatever and let the user agent bother
about how to get it. If that's too primitive for your needs, go and
create a separate protocol. I'm sick and tired of people trying to
extend HTML to do everything from boiling an egg to making
coffee. It's bad enough that HTML is a user interface language in the
first place (South Park fans, sing along: "Blame Mosaic! Blaim
Mosaic!") instead of developers getting a clue and just created an
extensible embedding mechanism in HTML years ago and worked on
complementary technologies to facilitate the creation of "DHTML
Applications".

Next time, before you post such an inflammatory message to a public
mailing list, please do your homework. What you are proposing is
altering a decision-making mechanism that does NOT work as you think
it does to accomplish something completely meaningless. HTML is the
HyperText Markup Language. Before you start another hopeless campaign
against the capitalist oppressors in your head, at least enlighten the
rest of usas to how Microphones and HyperText are related in any way.

I'll shut up now.

-- 
Stephanos Piperoglou                              <stephanos@webreference.com>
Maintainer, HTML with Style                    <http://webreference.com/html/>
  Visit HTML with Style for online HTML and CSS tutorials with step-by-step
   procedures and practical examples to help you author Web pages that are
 full-featured, standards-compliant and backwards-compatible, tools to make a
 Web author's life easier, software reviews, opinions, industry news and more




From owner-ietf-outbound  Sat Apr  1 19:31:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA12865
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 19:30:02 -0500 (EST)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12842
	for <ietf@ietf.org>; Sat, 1 Apr 2000 19:29:34 -0500 (EST)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id TAA23585;
        Sat, 1 Apr 2000 19:28:51 -0500 (EST)
Message-Id: <200004020028.TAA23585@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Stephanos Piperoglou <stephanos@webreference.com>
cc: "James P. Salsman" <bovik@best.com>, Harald@Alvestrand.no, ietf@ietf.org,
        www-forms@W3.ORG, www-html@W3.ORG
Subject: Re: HTML forms 
In-reply-to: Your message of "Sun, 02 Apr 2000 02:25:06 +0300."
             <Pine.LNX.4.10.10004020144230.4352-100000@dawn.pipis> 
Date: Sat, 01 Apr 2000 19:28:51 -0500
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Last time I checked, IANA, and not the IETF, controls the definitions
> of Media Types. 

yes, but IANA follows IETF rules in assignment and updating of media types.

> The entry for text/html [1] says, simply "See RFC
> 1866". And RFC 1866 [2] is a more or less verbatim copy of the HTML
> 2.0 Specification (which I couldn't find on w3.org, not that I spent
> all that long looking). If it's so important to you that this changes,
> I'd suggest you first get working at making this point to HTML 4.01 or
> even (shock horror) XHTML 1.0. You can work out extensions later on.

This is already in the process of being changed - see
draft-connolly-text-html-02.txt
for the latest version.  IIRC this is ready for IESG ballot
(though it might already be in the RFC Editor queue)

I presume that IANA will update the text/html registration once this
document is published as an RFC.

Keith

p.s. As for updating this along the lines that Mr. Salsman suggests - 
the problem as I see it is that Mr. Salsman has not been able to obtain
much community support, much less consensus, for his idea.     I am
not so sure that it's a fundamentally bad idea, but perhaps it needs
tweaking in order to gain widespread support.  Or perhaps it's just not 
high enough on anyone's priority list except Mr. Salsman's.  Regardless,
it needs a great deal more support than Mr. Salsman's to be approved, and
neither does such support seem to be forthcoming from the IETF list members.

Note that since IETF does acknowledge W3C as the "owner" of the HTML
specifications, IESG is extremely unlikely to approve a version of a 
text/html media type registration without prior W3C approval of that 
registration.



From owner-ietf-outbound  Sat Apr  1 19:41:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA13038
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 19:40:03 -0500 (EST)
Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12887
	for <ietf@ietf.org>; Sat, 1 Apr 2000 19:30:51 -0500 (EST)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id QAA07416;
	Sat, 1 Apr 2000 16:30:23 -0800 (PST)
Date: Sat, 1 Apr 2000 16:30:23 -0800 (PST)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200004020030.QAA07416@shell9.ba.best.com>
To: stephanos@webreference.com
Subject: ACCEPT and DEVICE (was Re: HTML forms)
Cc: ietf@ietf.org, www-forms@W3.ORG, www-html@W3.ORG
In-Reply-To: <Pine.LNX.4.10.10004020144230.4352-100000@dawn.pipis>
X-Loop: ietf@ietf.org

Stephanos,

Thanks for your message:

>... You need detailed definitions, changes to DTDs, and more.
> If you have these details, it would be nice to point us all to a
> proposal so we know how "DEVICE" and "MAXTIME" would work.

Sorry about not pointing to this document:

  http://www.bovik.org/device-upload.html

in every message.  It started out as an Internet Draft in late 1997.

> WHAT CONCERNS [from Norman Solomon's article in FAIR's _Extra!_],
> and HOW DO THEY RELATE TO THIS DISCUSSION?

The same concerns I had after participating in the W3C's extended 
forms working group for most of last year -- that they care far 
more about e-commerce that they should (to the point of wanting to 
completely overhaul perfectly serviceable HTML forms as the are) 
and at the same time are seriously neglecting educational needs.

>... We've HAD this technical discussion here AGES ago. Create a form,
> give it an accept type of audio/whatever and let the user agent 
> bother about how to get it. If that's too primitive for your needs,
> go and create a separate protocol....

Not only does the chair of the HTML Working Group and everyone 
else in the W3C who has spoken out on the topic, including 
Tim Berners-Lee, agree with these sentiments, SO DO I!!!  In 
a perfect world, all of the browser authors would implement
device upload using the ACCEPT attribute within INPUT TYPE=FILE.

However, in the world we live in, NONE of them have done that.  
The only reason why that I've been able to find, after years 
of communication with them and studying their code, when it has 
been available, is that many major releases of the big-two 
browsers have interpreted the ACCEPT attribute as a filename 
pattern.  The underlying reason is that at for a long while, 
the official HTML 3.2 specification suggested ACCEPT was 
supposed to be a filename pattern, so that was the correct 
behavior as interpreted by the browser developers, and it has 
probably become part of some legacy application somewhere.

So people have a choice, between idealism, where everybody 
faithfully implements the specs exactly as they are handed 
down (even if they don't remain consistent between revisions 
of the same version number), and pragmatism, where the 
introduction of an extra attribute (such as DEVICE) would 
allow the browser authors to rest easy that they aren't 
breaking anyone's legacy implementations of a ACCEPT, while 
at the same time providing a way to specify a default device 
selection.  Setting aside the fact that the HTML Working 
Group claims it would be bad user interface design to allow 
for the selection of a default (a position I find untenable),
which is the practical choice?

Which is better for spoken language instruction?

Which makes it more likely that mass-market portable wireless 
boxes will implement high-quality asynchronous voice messaging
even under very-low-bandwidth conditions?

Cheers,
James

P.S. sorry about the echoed message sans my reply



From owner-ietf-outbound  Sat Apr  1 20:01:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA13250
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 20:00:02 -0500 (EST)
Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13214
	for <ietf@ietf.org>; Sat, 1 Apr 2000 19:54:58 -0500 (EST)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id QAA12704;
	Sat, 1 Apr 2000 16:54:25 -0800 (PST)
Date: Sat, 1 Apr 2000 16:54:25 -0800 (PST)
Message-Id: <200004020054.QAA12704@shell9.ba.best.com>
From: James Salsman <bovik@best.com>
To: Keith Moore <moore@cs.utk.edu>
Cc: www-html@W3.ORG, www-forms@W3.ORG, ietf@ietf.org
Subject: support for device upload (was Re: HTML forms) 
X-Loop: ietf@ietf.org

Keith,

Thanks for your message:

> the problem as I see it is that Mr. Salsman has not been able to obtain
> much community support, much less consensus, for his idea.     I am
> not so sure that it's a fundamentally bad idea, but perhaps it needs
> tweaking in order to gain widespread support.  Or perhaps it's just not 
> high enough on anyone's priority list except Mr. Salsman's.  Regardless,
> it needs a great deal more support than Mr. Salsman's to be approved, and
> neither does such support seem to be forthcoming from the IETF list members.

I had been able to get the explicit support of about two dozen 
generally respected and directly affected people before I 
published this petition, on which they are listed:

  http://www.bovik.org/devup-petition

After posing the issue as one of platform-independence (instead 
of spoken language education as I had been) multiple hundreds of 
people endorsed (and are still endorsing) on that petition.  
Many of those people wrote to the www-html list last month, as 
is recorded in the W3C archives for early March.

If there needs to be a formal proposal to the IETF, it should
not be submitted by me alone.  Experience has shown that an 
outspoken geek with no apparent interest is not taken as 
seriously as would be, for example, the officers in charge of 
teaching spoken languages to cadets at West Point, with their 
immediate mission-critical interest with profound life-or-death 
implications affecting communities throughout the world.

Cheers,
James



From owner-ietf-outbound  Sat Apr  1 20:51:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA13582
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 20:50:02 -0500 (EST)
Received: from mail.nbn.net (root@nbn.net [207.51.86.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13549
	for <ietf@ietf.org>; Sat, 1 Apr 2000 20:41:31 -0500 (EST)
Received: from server-1 (dial2-25.nbn.net [208.139.67.67])
	by mail.nbn.net (8.9.3/8.9.3) with SMTP id UAA23238
	for <ietf@ietf.org>; Sat, 1 Apr 2000 20:41:30 -0500
Message-ID: <38E6A749.1BE0@nbn.net>
Date: Sat, 01 Apr 2000 20:50:01 -0500
From: Betsy Brennan <bbrennan@nbn.net>
Reply-To: bbrennan@nbn.net
X-Mailer: Mozilla 3.04 (Win95; U)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: hacker invasions
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Can anyone help me find documentation of a hacker attack that includes
details of the attack and what was done to prevent similar attacks in
the future? Respectfully, Betsy B.



From owner-ietf-outbound  Sat Apr  1 21:31:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA13912
	for ietf-outbound.10@ietf.org; Sat, 1 Apr 2000 21:30:03 -0500 (EST)
Received: from localhost.localdomain (pool0860.cvx11-bradley.dialup.earthlink.net [209.178.191.95])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13874
	for <ietf@ietf.org>; Sat, 1 Apr 2000 21:27:14 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id SAA12574;
	Sat, 1 Apr 2000 18:25:32 -0800
Sender: francis@localhost.localdomain
Message-ID: <38E6AF9B.9E5CBCC5@ecal.com>
Date: Sat, 01 Apr 2000 18:25:31 -0800
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
CC: www-forms@W3.ORG, www-html@W3.ORG
Subject: Re: HTML forms
References: <200004020028.TAA23585@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Keith Moore wrote:

> Note that since IETF does acknowledge W3C as the "owner" of the HTML
> specifications

...much as the ITU acknowledges the IETF as the "owner" of the
IP specifications.  Let's not set a precedent we can't live with.  :-)

--
/=================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.   |
|Chief Scientist |================================================|
|eCal Corp.      |When rats leave a sinking ship, where exactly do|
|francis@ecal.com|they think they're going?                       |
\=================================================================/





From owner-ietf-outbound  Sun Apr  2 00:01:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA17158
	for ietf-outbound.10@ietf.org; Sun, 2 Apr 2000 00:00:04 -0500 (EST)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17086
	for <ietf@ietf.org>; Sat, 1 Apr 2000 23:52:05 -0500 (EST)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id XAA24232;
        Sat, 1 Apr 2000 23:51:35 -0500 (EST)
Message-Id: <200004020451.XAA24232@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: James Salsman <bovik@best.com>
cc: Keith Moore <moore@cs.utk.edu>, www-html@W3.ORG, www-forms@W3.ORG,
        ietf@ietf.org
Subject: Re: support for device upload (was Re: HTML forms) 
In-reply-to: Your message of "Sat, 01 Apr 2000 16:54:25 PST."
             <200004020054.QAA12704@shell9.ba.best.com> 
Date: Sat, 01 Apr 2000 23:51:35 -0500
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

James,

bottom line is, this is a W3C matter.  you need to convince *them*.

Keith



From owner-ietf-outbound  Sun Apr  2 01:41:58 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA21332
	for ietf-outbound.10@ietf.org; Sun, 2 Apr 2000 01:40:06 -0500 (EST)
Received: from mauve.innosoft.com (mauve.innosoft.com [192.160.253.247])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20514
	for <ietf@ietf.org>; Sun, 2 Apr 2000 01:32:34 -0500 (EST)
From: ned.freed@innosoft.com
Received: from MAUVE.INNOSOFT.COM by MAUVE.INNOSOFT.COM (PMDF V6.1-1 #35243)
 id <01JNQC0TX10G0005K1@MAUVE.INNOSOFT.COM> for ietf@ietf.org; Sat,
 01 Apr 2000 22:31:55 -0800 (PST)
Date: Sat, 01 Apr 2000 22:30:07 -0800 (PST)
Subject: Re: support for device upload (was Re: HTML forms)
In-reply-to: "Your message dated Sat, 01 Apr 2000 16:54:25 -0800 (PST)"
 <200004020054.QAA12704@shell9.ba.best.com>
To: James Salsman <bovik@best.com>
Cc: Keith Moore <moore@cs.utk.edu>, www-html@W3.ORG, www-forms@W3.ORG,
        ietf@ietf.org
Message-id: <01JNQKMM5YNS0005K1@MAUVE.INNOSOFT.COM>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
X-Loop: ietf@ietf.org

> If there needs to be a formal proposal to the IETF, it should
> not be submitted by me alone.  Experience has shown that an
> outspoken geek with no apparent interest is not taken as
> seriously as would be, for example, the officers in charge of
> teaching spoken languages to cadets at West Point, with their
> immediate mission-critical interest with profound life-or-death
> implications affecting communities throughout the world.

On the contrary, a cogent and technically sound proposal from a single person
describing a technical change within the IETF's purview is likely to be taken a
lot more seriously than a petition with prominent names and no real techincal
content.

				Ned



From owner-ietf-outbound  Sun Apr  2 03:11:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA22906
	for ietf-outbound.10@ietf.org; Sun, 2 Apr 2000 03:10:04 -0400 (EDT)
Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22763
	for <ietf@ietf.org>; Sun, 2 Apr 2000 01:58:25 -0500 (EST)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id WAA29120;
	Sat, 1 Apr 2000 22:58:17 -0800 (PST)
Date: Sat, 1 Apr 2000 22:58:17 -0800 (PST)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200004020658.WAA29120@shell9.ba.best.com>
To: timbl@W3.ORG
Subject: Re: support for Salsman proposal for form-based device input
Cc: Bob.Wohlsen@Schwab.com, dsr@W3.ORG, ietf@ietf.org, www-html@W3.ORG
In-Reply-To: <011101bf9b59$40a8c460$84001d12@politburo.w3.org>
X-Loop: ietf@ietf.org

Dear Dr. Berners-Lee,

Thanks for your message:

> Rather than trying to change The HTML specification, one needs to
> encourage this feature to be implemented, and implemented well.

I completely agree with that end goal, whether the means involve 
extending HTML or not.
 
> Ways to do this include:
> 
> 1. lobbying browser manufacturers;

I've tried this, spending solid weeks on the phone, writing email, 
and talking in person to developers from Microsoft and Netscape, 
without any luck.  Microsoft has been the most frustrating, with 
people all over Redmond phoning me, talking for half an hour, and 
then never returning any further phone calls or emails.  At least 
Netscape has never even led me on like that (or shown any real 
interest.)  I kept quiet on the OBJECT/EMBED issues for so long 
partly because I thought Microsoft didn't realize how much wintel
was benefiting from them, which seems very stupid of me in hindsight.

My impression is that *you*, however, could have them all scrambling 
to implement pure-HTML4-based microphone upload if you simply took a 
public stand on it.

> 2. doing it yourself to an open source browser such as Amaya or Mozilla;

Amaya doesn't even have the most rudimentary form of file upload.
Mozilla's was broken for most of the past six months --
  http://bugzilla.mozilla.org/show_bug.cgi?id=8209
-- and I'm still working on it.

> 3. sponsoring someone to do (2) on the open source exchange;
> 4. doing a great facility specification for it with simulated bitmaps to
> guide

It's occurred to me in the past couple days that integration with 
the layout engines could be a lot simpler.  Currently INPUT TYPE=FILE 
widgets are rendered with a text entry box for a filename, and a 
"Browse..." button.

Suppose that when ACCEPT includes "audio/*" that another button, 
labeled "Record...", for example, would be rendered, set up to 
launch an external recorder helper application instead of set 
within the layout.  And for "image/*" there would be a button 
with "Capture photo..." or something like that, and "text/*" could 
have an "Editor..." button, and so on for the other types.  That 
could be done much faster than anything I've seen proposed by 
anyone previously.

> It may be that a NOTE simply pointing to the need and making a spec for
> doing it as above *according to the HTML4 spec*  would be a good idea too.

The motivations section of the device upload NOTE points out the 
need, but do you think that the big browsers would pay as much 
heed to another NOTE than to a direct request from you?

Tim, how about if you just wrote an open letter to Microsoft and 
Netscape, asking that they correct their interpretations of the 
ACCEPT attribute (not a filename pattern!), and allow for 
launching customizable file-input helper applications, with the 
default for "audio/*" being the Microsoft Sound Recorder on 
their wintel platforms, as a starter.  Would you please do that?

For as many benefits as I think the device upload proposal has, 
with the Content headers, security considerations, default device
selection, MAXTIME, client buffer maxlength exposure, etc., I 
would drop my advocacy for all those factors, because they amount 
to nothing more than distractions until the major browsers just 
*do something* to at least make microphone upload real.
 
> To suggest an alternative way of  doing this (as for example in Mr Salsman's
> note) will of course lead to the possibility of two companies implementing
> it in different ways, which is something very counter-productive and which
> we try very hard to avoid.

That's not entirely fair, because there is nothing in the device 
upload proposal that would preclude device upload when the DEVICE 
attribute is not specified.  It is clear that your goal is to 
prevent problems from cropping up within HTML.  Won't you please 
ask Microsoft and Netscape to correct their problems with the 
ACCEPT attribute before they keep us all from these important 
features any longer?  Thank you.

Cheers,
James



From owner-ietf-outbound  Mon Apr  3 00:34:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA01636
	for ietf-outbound.10@ietf.org; Mon, 3 Apr 2000 00:30:02 -0400 (EDT)
Received: from faui40.informatik.uni-erlangen.de (eckert@faui40.informatik.uni-erlangen.de [131.188.34.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01608
	for <ietf@ietf.org>; Mon, 3 Apr 2000 00:27:12 -0400 (EDT)
Received: (from eckert@localhost)
	by faui40.informatik.uni-erlangen.de (8.9.1/8.1.37-FAU) id GAA27017; Mon, 3 Apr 2000 06:27:07 +0200 (MET DST)
From: Toerless Eckert <Toerless.Eckert@Informatik.Uni-Erlangen.de>
Message-Id: <200004030427.GAA27017@faui40.informatik.uni-erlangen.de>
Subject: Re: A thought about patents
In-Reply-To: <38E5D476.EC066D65@cs.columbia.edu> from Henning Schulzrinne at "Apr 1, 2000  5:50:30 am"
To: schulzrinne@CS.COLUMBIA.EDU (Henning Schulzrinne)
Date: Mon, 3 Apr 2000 06:27:05 +0200 (MET DST)
Cc: GK@Dial.pipex.com, ietf@ietf.org
Organisation: CSD IMMD IV, University of Erlangen, Germany
X-Mailer: ELM [version 2.4ME+ PL42 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> not the one patent examiner that seems to have missed the
> existence of engineering libraries in his or her undergraduate
> education.

That's a bold presumption, and even though i don't know any of those guys whom
you put the blame upon, i'd rather think that you're trying to come up with
a much too simple explanation of the problem. First of all, there's an
inquality of weapons. The patent lawyers working on persuading the patent
office of the worthyness of the application get paid huge amounts by the
hour, the patent office examiners have to get through a specific amount of
applications per unit of time for a fixed income. "Resistance is futile,
your objections will just be out-processed by us" is what the lawyer will
just say.

Please don't forget that the requirement is just "non-obviousness" for the
typical person working in the field. Not for the experts after appliying
the insights that they've learned from the patent application itself. 

And if i read that "peer review" of yours, then this reminds me very much
of the stuff that happens in the scientific community. Read: Your paper get's
accepted in peer review for a conference, if your professor is good buddy
with all the peer reviewers, or your name is already well known. Else not.
Just look at how many european paper submissions get accepted by america
n conferences, then you know what i am talking about. I think there's less
justice in "peer review" than even in the broken patent process we
have today.

Just split the money someone pays for a patent application equally 
between the patent lawer and the patent office and make both of them get less
the longer it takes. Then give both type of people equal success money for the
amount of patent applications they refused (for the patent office) or
managed to get through (lawyers). That should already give a much more
equal and incentive battlefield.

Cheers
	Toerless



From owner-ietf-outbound  Mon Apr  3 00:51:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA01882
	for ietf-outbound.10@ietf.org; Mon, 3 Apr 2000 00:50:02 -0400 (EDT)
Received: from illyana.qualcomm.com (illyana.qualcomm.com [129.46.2.83])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01859
	for <ietf@ietf.org>; Mon, 3 Apr 2000 00:48:16 -0400 (EDT)
Received: from davespc (primemover-client09.qualcomm.com [129.46.86.74]) by illyana.qualcomm.com (8.9.3/8.9.3/1.0) with SMTP id VAA06132; Sun, 2 Apr 2000 21:48:09 -0700 (PDT)
From: "Dave Miller" <dave@buyutree.com>
To: "Vernon Schryver" <vjs@calcite.rhyolite.com>, <ietf@ietf.org>
Subject: RE: A thought about patents
Date: Sun, 2 Apr 2000 21:48:09 -0700
Message-ID: <002001bf9d27$cf197260$0400a8c0@qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-reply-to: <200004012241.PAA20994@calcite.rhyolite.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> Would you have the same people checking the claims of how much it cost
> to develop an idea that now check the technical claims...?

Excellent point.  The problem, as usual, is in the execution.

So could self-regulation be the answer?

(I'm not a lawyer, but...) Consider a voluntary public invention-protection
forum operating on principles very similar to those of the USPTO, but run by
a board comprised of elected members.

- Members submit ideas in confidence for evaluations by engineering types
"skilled in the art".  The process is very simple, and versatile in it's use
of communications such as e-mail, personal interview, etc.

- The board's responsibility is to ensure competent and fair evaluation.

- Ideas considered to bare the essential attributes of a true invention are
declared such.

- Ideas not considered to be true inventions are released into the public
domain  :-!

- Members agree to honor the evaluation, which means not suing anyone who
implements a non-invention and not using anyone's true invention without
negotiating compensation.

- Anyone who's not a member gets a raspberry.

- I wonder how much of government we can get rid of if we keep chipping away
at it?





From owner-ietf-outbound  Mon Apr  3 01:51:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA07131
	for ietf-outbound.10@ietf.org; Mon, 3 Apr 2000 01:50:02 -0400 (EDT)
Received: from localhost.localdomain (pool0894.cvx17-bradley.dialup.earthlink.net [209.179.235.129])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06971
	for <ietf@ietf.org>; Mon, 3 Apr 2000 01:41:29 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id VAA13765
	for <ietf@ietf.org>; Sun, 2 Apr 2000 21:39:54 -0700
Sender: francis@localhost.localdomain
Message-ID: <38E82095.D566CAA7@ecal.com>
Date: Sun, 02 Apr 2000 21:39:49 -0700
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A thought about patents
References: <200004030427.GAA27017@faui40.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Toerless Eckert wrote:

> Please don't forget that the requirement is just "non-obviousness" for the
> typical person working in the field.

Side note: I think I've been told (by patent lawyers) that it's non-obviousness
for a skilled, even expert practicioner in the field.

> Just split the money someone pays for a patent application equally
> between the patent lawer and the patent office and make both of them get less
> the longer it takes.

Can't be done--at least, not in the US.  A lawyer is hired by the applicant.  It
more or less has to be that way; a lawyer is someone I hire to represent me, to
speak for me in the complex language of the law.  To keep me from hiring whoever
I want to speak for me might well be unconstitutional; it would certainly run
against the common-law tradition (tracing back, oh, 500-100 years).  The Roman
Republic had such a system; only designated people could bring a legal action,
and they could only use prescribed forms of language.  It was a wonderfully
designed form of job security; but it wasn't justice.

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |We want forty million helicopters and a dollar!|
|francis@ecal.com|--"Dinosaurs"                                  |
\================================================================/





From owner-ietf-outbound  Mon Apr  3 03:40:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA14304
	for ietf-outbound.10@ietf.org; Mon, 3 Apr 2000 03:40:02 -0400 (EDT)
Received: from acme.penta3.es ([195.171.34.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14281
	for <ietf@ietf.org>; Mon, 3 Apr 2000 03:39:22 -0400 (EDT)
Received: from dark (mazingerdmz.penta3.es [195.171.34.8])
	by acme.penta3.es (8.9.3/8.9.3) with SMTP id KAA03972;
	Mon, 3 Apr 2000 10:36:39 +0200
Message-ID: <001201bf9d3f$18112320$2c00000a@crypto>
From: "Javier Torres Seco de Herrera" <jtorres@penta3.es>
To: <bbrennan@nbn.net>, <ietf@ietf.org>
References: <38E6A749.1BE0@nbn.net>
Subject: RE: hacker invasions
Date: Mon, 3 Apr 2000 09:34:49 +0200
Organization: Penta3
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.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

www.argo.es
----- Original Message ----- 
From: Betsy Brennan <bbrennan@nbn.net>
To: <ietf@ietf.org>
Sent: Sunday, April 02, 2000 3:50 AM
Subject: hacker invasions


> Can anyone help me find documentation of a hacker attack that includes
> details of the attack and what was done to prevent similar attacks in
> the future? Respectfully, Betsy B.
> 



From owner-ietf-outbound  Mon Apr  3 05:40:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA15328
	for ietf-outbound.10@ietf.org; Mon, 3 Apr 2000 05:40:02 -0400 (EDT)
Received: from proxy2.ba.best.com (root@proxy2.ba.best.com [206.184.139.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15275
	for <ietf@ietf.org>; Mon, 3 Apr 2000 05:37:24 -0400 (EDT)
Received: from best.com (bovik.vip.best.com [205.149.161.94])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id CAA04010;
	Mon, 3 Apr 2000 02:37:05 -0700 (PDT)
Message-ID: <38E8662B.AC21F664@best.com>
Date: Mon, 03 Apr 2000 02:36:43 -0700
From: James Salsman <j.salsman@bovik.org>
Reply-To: www-html@W3.ORG
Organization: Bovik Research
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: aclover@1VALUE.com
CC: www-html@W3.ORG, ietf@ietf.org
Subject: SourceXchange wish (was Re: support for...)
References: <5F78AA062F6AD311A59000508B4AAF6D092AF1@pcs02>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Andrew,

Thank you for your kind reply:

>> Suppose that when ACCEPT includes "audio/*" that another button,
>> labeled "Record...", for example, would be rendered, set up to
>> launch an external recorder helper application instead of set
>> within the layout.  And for "image/*" there would be a button
>> with "Capture photo..." or something like that [...]
> 
> This is a great idea. The only change needed would be a Note in
> the HTML to say that user agents MAY choose to do it, where an
> API exists on the host platform for device capture of that type.

I've put a corresponding wish up on SourceXchange:
  http://www.sourcexchange.com/WishDetail?wishID=227
Anybody who would like to sponsor this development should please 
submit an official SourceXchange RFP and/or comment the wish.

As for any more NOTEs, I am out of that business but I encourage 
anyone with a friendly W3C Advisory Committee representative to 
do whatever needs to be done.

>> [MS and Netscape should fix ACCEPT]
> 
> Quite so. Even with a DEVICE attribute, the ACCEPT setting would
> *still* have to implemented properly; giving it a different
> syntax for file and device as in device-upload.html loooks like
> an unnecessary and confusing wart to me, not to mention it
> breaking the HTML 4 definition.

Agreed; in pursuit of backward-compatibility it is best to 
emphasize compatibility over backwardness.  If MSIE and NS 
stop interpreting ACCEPT as a filename pattern (which I hope 
they both already have; I haven't checked lately) then I will 
expunge that wart from the versions over which I have control.

> I can't see anything a server could usefully do with
> Client-file-maxlength or Content-type-alternates, and I can't
> think of any reason it should need to know Content-source-device.
> Are there any particular circumstances where these could be used?

Yes, Client-file-maxlength would be useful for an ultra-thin 
client with limited buffer memory, for example a wireless phone 
with only a few MB of recording RAM.  Lets hope Moore's law 
buries that need.

Content-type-alternates was for lightweight content negotiation, 
and depended on the server regenerating (or redirecting) the HTML 
with different ACCEPT parameters; more trouble than it has been 
worth, for certain.

As for Content-source-device (which I've accidentally called 
"Content-device" once on these lists.)  There is probably some 
OCR application that could benefit from figuring different optical 
contrast expectations from scanners and cameras, but that is 
near the least of my worries.  If anyone ever ends up needing 
that, it could be done with creative use of x-tra parameters on 
the Content-type header of the multipart/form-data submission, e.g:
  Content-type: audio/... ;x-source-device=microphone

> Then there's only MAXTIME left in the specification. Could you
> suggest an application where this might be useful?

The guy who suggested it used to put together television shows. 
All of these pie-in-the-sky features are distractions until the 
basics are implemented on common browsers.  Since SMIL seems to 
want to be just like teevee, lets wait until browsers implement 
a user-specified maximum time that SMIL presentations are 
allowed to play before bothering device upload with MAXTIME.

And about the security considerations, lets just hope that 
Java/J/ECMAscript and the DOMs aren't allowing write access to 
the INPUT TYPE=FILE VALUE attributes and submitting forms by 
themselves these days.

Cheers,
James



From owner-ietf-outbound  Mon Apr  3 11:21:02 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA18587
	for ietf-outbound.10@ietf.org; Mon, 3 Apr 2000 11:20:02 -0400 (EDT)
Received: from janus.cypress.com ([157.95.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18494
	for <ietf@ietf.org>; Mon, 3 Apr 2000 11:12:48 -0400 (EDT)
Received: from cobweb.mis.cypress.com (cobweb.mis.cypress.com [172.16.2.5])
	by janus.cypress.com (8.9.1a/8.9.1) with ESMTP id IAA24314;
	Mon, 3 Apr 2000 08:12:19 -0700 (PDT)
Received: from cypress.com ([157.95.237.179])
	by cobweb.mis.cypress.com (8.8.8/8.8.8) with ESMTP id IAA08329;
	Mon, 3 Apr 2000 08:11:59 -0700 (PDT)
Message-ID: <38E8B526.A4E0640B@cypress.com>
Date: Mon, 03 Apr 2000 08:13:42 -0700
From: Pankaj K Jha <pkj@cypress.com>
Organization: Cypress  Semiconductor Corp.
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
CC: ietf@ietf.org
Subject: Re: A thought about patents
References: <4.2.2.20000330230917.00c1b760@pop.dial.pipex.com> <38E5D476.EC066D65@cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

On thought of 'peer review' I remember going to ATM Conference a few years ago
where at the end of a joint paper by three 'well-known' contributors a
'not-at-all-known' engineer from another company got up from the rear rows of the
audience and complained that his paper had been stolen and was being resubmitted.

When he was told there might have been a confusion, he pointed out that he
presented an exactly the same concept, in the same sequence, and with similar
examples a few months ago and was voted down unanimously by the 'gurus' on the
grounds that the idea wasn't good enough.

He demanded withdrawal of the paper, with a public apology. Despite protests, he
lodged his formal complaints. They budged, offering to include his name in the
author list. He wouldn't settle initially, but later he accepted after receiving
an apology. Later either his name was added to the author list or to the
acknowledgment section, I do not remember.

This kind of "peer review" is common. There is a common resistance by frequent
contributors to a newcomer's bold new ideas. Especially when it challenges other
technologies developed by established companies. And this is human nature. People
love credit, and sharing the glory is not part of usual human psychology.

Companies use patents to guard exactly that - if you don't think it's good
enough, don't worry, you do not have to use it. If you think otherwise, we're
willing to sell you results of our investment in R&D. Unfortunately, people don't
mind buying products for a price but they don't like buying a technology for a
price. They both cost money and are of value to the company that owns them.

As far as some patents being laughed out of lowliest of technical conferences, I
agree. By the same token, however, I find some technical contributions in
respected technical journals by "well-known" people that I can only laugh at. So
it goes both ways. (Can you ever imagine a famous person submitting a draft/paper
and not being accepted by the technical committee? For them, it's an honor to
have the paper.)

Although many times the stupidity of patents does surpass every limit, often it
helps a company secure a place for its own credibility. It also allows it time to
develop products. If a new technology is given to public for general education
the big companies will immediately copy it and come out with a new product. They
already have everything else. The startup company, however, has to build
everything else before it has a chance to put its own technology into its
products.

Most startup companies take a third approach - they do not announce their product
or technology until they are done. Their websites have nothing more than
directions to their office. And they hope that no one will invent the method
before they are out with their products.

I think the policy of allowing patented ideas to appear in technical journals (on
way to standards development), with a permission to other companies to use the
technology on a non-discriminatory, open licensing terms is quite fair. Two
benefits are: companies get the credit they deserve, and they are able to swap
their patents for free with some other company for some other patents that they
would like to have. Patents are often used to cross-license technology, and are
as good as cash in that regard. This, I feel, is a fair way for a company to
benefit from the technology that they have developed.

Peer review may not do much to achieve the objective.

Patents that are technically stupid are of no use to anyone anyway. If patents
cover too broad an issue, they will anyway get challenged successfully.

-Pankaj

Henning Schulzrinne wrote:

> In looking in multimedia-related patents, I'm also utterly amazed by the
> complete lack of citation of published technical articles or related
> work (RFCs, Internet drafts, etc.). The problem with many patents is
> that if submitted as a technical paper at even the lowliest conference,
> it would be laughed out of the program. Maybe we need a peer review
> (under suitable secrecy arrangements) of patent applications by real
> experts, not the one patent examiner that seems to have missed the
> existence of engineering libraries in his or her undergraduate
> education.
>
> Graham Klyne wrote:
> >
> > As many of us are finding, it seems to become more and more difficult to
> > develop or implement a standard without tripping over somebody-or-other's
> > patent for some piece of technology that many of us would regard as fairly
> > obvious or lacking in novelty.
> >
> > The recent announcement from the U.S. Patent and Trademark Office about
> > overhauling their scrutiny of applications for online business patents
> > seems to imply a tacit acknowledgement that their is a problem with the
> > review process with respect to discovery or prior art or determination of
> > novelty in a claimed invention.
> >
> > My thought is this:  I'd like to see a presumption of lack of novelty if an
> > idea gets raised in a public forum, even if it happens _after_ a patent has
> > been applied for, unless it can be shown that the information came from
> > leakage of proprietary information.
> >
> > Maybe such an approach might ameliorate the "gold rush" mentality to be the
> > first to slap a patent on an idea or technique that is coming to be
> > accepted art in the normal process of technology evolution.
> >
>
> --
> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



From owner-ietf-outbound  Mon Apr  3 11:30:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA18762
	for ietf-outbound.10@ietf.org; Mon, 3 Apr 2000 11:30:02 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18697
	for <ietf@ietf.org>; Mon, 3 Apr 2000 11:28:01 -0400 (EDT)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id LAA29445;
	Mon, 3 Apr 2000 11:26:05 -0400 (EDT)
Sender: hgs@cs.columbia.edu
Message-ID: <38E8B80D.5F6FBC69@cs.columbia.edu>
Date: Mon, 03 Apr 2000 11:26:05 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Pankaj K Jha <pkj@cypress.com>
CC: ietf@ietf.org
Subject: Re: A thought about patents
References: <4.2.2.20000330230917.00c1b760@pop.dial.pipex.com> <38E5D476.EC066D65@cs.columbia.edu> <38E8B526.A4E0640B@cypress.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I suppose it depends which conferences you attend. I can tell you from
personal experience (and the angry phone calls...) that papers from
"famous" people do get rejected, frequently. Are you arguing that there
should be no peer review, given that it fails on occasion or because
some people are unethical? Indeed, peer review can help catch the case
of intentional or otherwise duplication of earlier work.

The problem is that a patent provides a presumption of validity. Thus,
even if the patent ignores prior non-patent art, the creator of that
prior (published) art has to spend time and money defending himself in
court. Ultimately, that favors the big corporation with a standing army
of lawyers over any small or not-for-profit outfit. I'm not worried
about the stupid ideas (yes, there's a patent on including a list of
destination network addresses in a packet header to do multicast), but
rather the previously published and slightly non-obvious results.

Henning 
-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



From owner-ietf-outbound  Mon Apr  3 12:10:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA19332
	for ietf-outbound.10@ietf.org; Mon, 3 Apr 2000 12:10:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19274
	for <ietf@ietf.org>; Mon, 3 Apr 2000 12:04:45 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id MAA01369
	for <ietf@ietf.org>; Mon, 3 Apr 2000 12:04:01 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: <ietf@ietf.org>
Subject: RE: A thought about patents
Date: Mon, 3 Apr 2000 12:07:25 -0400
Message-ID: <000001bf9d86$b45f82c0$d001010a@tst.ennovatenetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <38E5D476.EC066D65@cs.columbia.edu>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


Henning Schulzrinne [schulzrinne@cs.columbia.edu]> writes
>
> In looking in multimedia-related patents, I'm also utterly
> amazed by the
> complete lack of citation of published technical articles or related
> work (RFCs, Internet drafts, etc.). The problem with many patents is
> that if submitted as a technical paper at even the lowliest
> conference,
> it would be laughed out of the program.

I have been on internal patent evaluation committees of my previous
employers (that doesn't mean I support idea of software patents.).
I would like to clarify a bit on the subject.

Granting of patents only means that a person grated a particular patent
was first to make "a claim" about the novelty of an idea or technique
as far as the patent office knows on the basis of "previous claims submitted
to it.". It is impossible for them to evaluate every  claim  on its
scientific
or intrinsic merits (even then they do a fairly decent job). The patent
office
basically notarizes the claim, date of a claim and the person who made a
claim.
It doesn't guarantee any usefulness or scientific merits of a claim (though
the person making a claim has to justify usefulness of a claim). It doesn't
mean that there are no better ideas already published or known to others in
the field, or the patent is of any great use to others. How do you expect
them
to know just about every thing under the sun?

> Maybe we need a peer review
> (under suitable secrecy arrangements) of patent applications by real
> experts, not the one patent examiner that seems to have missed the
> existence of engineering libraries in his or her undergraduate
> education.

Remember, a patent office works within a legal framework and is not a
ACM/IEEE technical review committee. Only a US law can stop software
patents.

All said, software patents should be declared crime against software
engineers (if not against, humanity.). The problem is that no big company
is likely to lobby for banning software patents because of their
vested interests since they already have a number of patents in their
portfolios.

Cheers,

--brijesh




From owner-ietf-outbound  Mon Apr  3 13:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA20141
	for ietf-outbound.10@ietf.org; Mon, 3 Apr 2000 13:10:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20082
	for <ietf@ietf.org>; Mon, 3 Apr 2000 13:07:06 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12cAJV-0004QZ-00; Mon, 03 Apr 2000 18:06:57 +0100
Date: Mon, 3 Apr 2000 18:06:54 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Brijesh Kumar <bkumar@ennovatenetworks.com>
cc: ietf@ietf.org
Subject: RE: A thought about patents
In-Reply-To: <000001bf9d86$b45f82c0$d001010a@tst.ennovatenetworks.com>
Message-ID: <Pine.GSO.4.21.0004031759170.25067-100000@petra.ee.surrey.ac.uk>
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-Loop: ietf@ietf.org

On Mon, 3 Apr 2000, Brijesh Kumar wrote:

> Remember, a patent office works within a legal framework and is not a
> ACM/IEEE technical review committee. Only a US law can stop software
> patents.

Only a *US* law?

What is http://www.wipo.int/ for? WIPO's getting involved in e.g.
domain names, and is probably a better place to raise the issue of
software patents than some navel-gazing backwater which has only
recently grasped the idea of copyright and has yet to abolish 'design
patents'.

L.

software design patents can be incredibly trivial:
http://www.patents.ibm.com/details?&pn=USD0421974__

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




From owner-ietf-outbound  Mon Apr  3 14:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA21700
	for ietf-outbound.10@ietf.org; Mon, 3 Apr 2000 14:40:03 -0400 (EDT)
Received: from smtp1a.ispchannel.com ([24.142.63.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21663
	for <ietf@ietf.org>; Mon, 3 Apr 2000 14:39:35 -0400 (EDT)
Received: from Elaine.ispchannel.com ([24.142.94.116])
          by smtp1a.ispchannel.com
          (InterMail vK.4.02.00.00 201-232-116 license 7d3764cdaca754bf8ae20adf0db2aa60)
          with SMTP
          id <20000403184025.PLCQ2325.smtp1a@Elaine.ispchannel.com>
          for <ietf@ietf.org>; Mon, 3 Apr 2000 11:40:25 -0700
Message-Id: <3.0.5.32.20000403111509.00a6f830@popd.csrstds.com>
X-Sender: krechmer@popd.csrstds.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Mon, 03 Apr 2000 11:15:09 -0700
To: ietf@ietf.org
From: Ken Krechmer <krechmer@csrstds.com>
Subject: test
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org




From owner-ietf-outbound  Mon Apr  3 16:00:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA23565
	for ietf-outbound.10@ietf.org; Mon, 3 Apr 2000 16:00:03 -0400 (EDT)
Received: from wren.prod.itd.earthlink.net (wren.prod.itd.earthlink.net [207.217.121.64])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23332
	for <ietf@ietf.org>; Mon, 3 Apr 2000 15:54:31 -0400 (EDT)
Received: from directavision.com (dialup-63.208.243.162.LosAngeles1.Level3.net [63.208.243.162])
	by wren.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id MAA06411
	for <ietf@ietf.org>; Mon, 3 Apr 2000 12:53:23 -0700 (PDT)
Message-ID: <38E8F674.548DE1E2@directavision.com>
Date: Mon, 03 Apr 2000 12:52:20 -0700
From: "direct-a-vision of..DIRECTV" <dan@directavision.com>
Organization: DIRECT-A-VISION, IND. (Direct-a-vision, into your Business Office & HomeTheater!) 
X-Mailer: Mozilla 4.04 [en] (Win95; I)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: firstuse.com for Invention protection registry service.Check for yourself 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

To whom it may concern:
A electronic date/time STAMP service available on-line. You will not
disclose your file contents! A alternative to a NONDISCLOSURE form and
faith in trust. Goto www.firstuse.com
d.



From owner-ietf-outbound  Tue Apr  4 01:12:51 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA08744
	for ietf-outbound.10@ietf.org; Tue, 4 Apr 2000 01:10:03 -0400 (EDT)
Received: from atlas.csd.net (root@atlas.csd.net [204.181.152.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07982
	for <ietf@ietf.org>; Tue, 4 Apr 2000 01:03:22 -0400 (EDT)
Received: from boulder.net (56ppp58.csd.net [204.151.43.160])
	by atlas.csd.net (8.9.1a/8.9.1) with ESMTP id XAA25471
	for <ietf@ietf.org>; Mon, 3 Apr 2000 23:03:17 -0600 (MDT)
Message-ID: <38E97804.34A1780F@boulder.net>
Date: Mon, 03 Apr 2000 22:05:10 -0700
From: karen marx <marx@boulder.net>
X-Mailer: Mozilla 4.7 (Macintosh; U; PPC)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Cartridges
Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I have a customer wanting to purchase 400 or more new cartridges, as an
initial order, for sale in Africa.   The model numbers are as follows:

HP 29A
HP 45A
HP 40A
HP 23A

I did not see these numbers on the HP list.   Are they only available in
Europe or do you have these?   If so, please provide quantity pricing.

They also want to purchase "Tambourd G1" (French).  Do you know what
this is?  Can you get it?   Pricing?

Thank you,

Karen Marx

I need the info asap - of course!



From owner-ietf-outbound  Tue Apr  4 01:21:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA10304
	for ietf-outbound.10@ietf.org; Tue, 4 Apr 2000 01:20:04 -0400 (EDT)
Received: from smtp1a.ispchannel.com (smtp.ispchannel.com [24.142.63.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08251
	for <ietf@ietf.org>; Tue, 4 Apr 2000 01:06:37 -0400 (EDT)
Received: from Elaine.ispchannel.com ([24.142.94.116])
          by smtp1a.ispchannel.com
          (InterMail vK.4.02.00.00 201-232-116 license 7d3764cdaca754bf8ae20adf0db2aa60)
          with SMTP
          id <20000404050727.SLAC2325.smtp1a@Elaine.ispchannel.com>
          for <ietf@ietf.org>; Mon, 3 Apr 2000 22:07:27 -0700
Message-Id: <3.0.5.32.20000403220703.00acf500@popd.csrstds.com>
X-Sender: krechmer@popd.csrstds.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Mon, 03 Apr 2000 22:07:03 -0700
To: ietf@ietf.org
From: Ken Krechmer <krechmer@csrstds.com>
Subject: Standards and patents
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

All,

Knowing my interest in this subject, Randy Bloomfield of the International
Center for Standards Research (university of Colorado, Boulder
International Telecommunications Program) has been kind enough to forward a
number of e-mails on this issue.  Enough, so that I thought I might try to
contribute.

The IETF has taken a unique position in the world of standardization
organizations.  The IETF is not a formal nationally recognized
standardization organization, yet the IETF is far too important to operate
as a fora or consortia.  By way of explanation, fora or consortia are
almost always commercially funded and quite often have, as part of their
"ground rules," a requirement that all participants enter into some form of
technology sharing (cross licensing or negotiated).  In other words, IPR is
not only identified in most fora or consortia, it is also negotiated.  This
is a distinct difference from the formal standardization (recognized by one
or more governments) organizations where IPR is usually identified, but
negotiation is not allowed.

The IETF, in regard to IPR, acts like a little like a formal
standardization organization.  It identifies intellectual property rights
(IPR) but leaves off requiring negotiation of IPR.  This, as is being shown
in many formal standardization organizations, may cause standards
development to migrate to organizations that identify and negotiate.  I
don't offer this approach as a solution, only an alternative, as such
negotiation in some fora or consortia smacks of coercion (IMO) when smaller
companies are negotiating with larger.

I make no arguments that the current patent system is useful to any but
lawyers.  But changing such a system is a lengthy political process.  I
suggest that the grounds for changing the existing patent system may be
based on the concept that patents were designed to award value to the
inventor of "similar" products. That is, for each incarnation of a product
that was "similar" to the invention, the inventor could receive a new form
of value (credit creation for the economists in the crowd).

Now patents are being used to control a different property -
"compatibility" and controlling "compatibility" feels more like controlling
access and therefore unfair.  Of course, there is enormous value in
controlling compatibility (e.g., Microsoft APIs, Intel software
compatibility, IBM data communications until recently) and so companies
attempt to do so.  Some day, likely far in the future, possibly patent law
can change to recognize that allowing commercial control of compatibility,
except in most unique circumstances, is of less benefit to society.  But
the patent law for the control of similarity for over 200 years has worked
reasonably well to reward inventors, yet distribute their inventions more
widely and more rapidly. For further comments on this topic please see
Communications Standards and Patent Rights: Conflict or Coordination?
http://www.csrstds.com/star.html


Ken Krechmer
Fellow
International Center for Standards Research
Interdisciplinary Telecommunications Program
University of Colorado at Boulder



From owner-ietf-outbound  Tue Apr  4 01:31:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA11852
	for ietf-outbound.10@ietf.org; Tue, 4 Apr 2000 01:30:02 -0400 (EDT)
Received: from faui40.informatik.uni-erlangen.de (eckert@faui40.informatik.uni-erlangen.de [131.188.34.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09160
	for <ietf@ietf.org>; Tue, 4 Apr 2000 01:12:58 -0400 (EDT)
Received: (from eckert@localhost)
	by faui40.informatik.uni-erlangen.de (8.9.1/8.1.37-FAU) id HAA15623; Tue, 4 Apr 2000 07:12:23 +0200 (MET DST)
From: Toerless Eckert <Toerless.Eckert@Informatik.Uni-Erlangen.de>
Message-Id: <200004040512.HAA15623@faui40.informatik.uni-erlangen.de>
Subject: Re: A thought about patents
In-Reply-To: <38E8B80D.5F6FBC69@cs.columbia.edu> from Henning Schulzrinne at "Apr 3, 2000 11:26: 5 am"
To: schulzrinne@CS.COLUMBIA.EDU (Henning Schulzrinne)
Date: Tue, 4 Apr 2000 07:12:23 +0200 (MET DST)
Cc: pkj@cypress.com, ietf@ietf.org
Organisation: CSD IMMD IV, University of Erlangen, Germany
X-Mailer: ELM [version 2.4ME+ PL42 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> The problem is that a patent provides a presumption of validity. Thus,
> even if the patent ignores prior non-patent art, the creator of that
> prior (published) art has to spend time and money defending himself in
> court. Ultimately, that favors the big corporation with a standing army
> of lawyers over any small or not-for-profit outfit. I'm not worried
> about the stupid ideas (yes, there's a patent on including a list of
> destination network addresses in a packet header to do multicast), but
> rather the previously published and slightly non-obvious results.

True. Which still doesn't say that any "peers" would be the more favourable
choice of review. What's needed is a prior-art database run by the PTO
into which people can submit their pointers. Without that the PTO can really
only well look up prior art that has been filed for patent. And the
knowledge of prior art by "peers" is very selective too.

Cheers
	Toerless



From owner-ietf-outbound  Tue Apr  4 03:01:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA22325
	for ietf-outbound.10@ietf.org; Tue, 4 Apr 2000 03:00:02 -0400 (EDT)
Received: from roma.axis.se (roma.axis.se [193.13.178.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22261
	for <ietf@ietf.org>; Tue, 4 Apr 2000 02:58:36 -0400 (EDT)
Received: from klatt2.axis.se (klatt2.axis.se [193.13.178.104])
	by roma.axis.se (8.9.3/8.9.3) with ESMTP id IAA24745;
	Tue, 4 Apr 2000 08:58:34 +0200 (MEST)
Received: by klatt2.axis.se with Internet Mail Service (5.5.2650.21)
	id <HPWG5LQQ>; Tue, 4 Apr 2000 09:00:12 +0200
Message-ID: <151F3D2AE9F0D3119E480004ACB8EA37126932@cluster01.axis.se>
From: Lars Viklund <lars.viklund@axis.com>
To: "'David Wang'" <david.wang@metro-optix.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Carry IP Packet in Ethernet Frame in IEEE 802.3 LLC Encapsula
	tion Format
Date: Tue, 4 Apr 2000 08:57:02 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org


> I never see or heard any product use 802.3 LLC frame format 
> to carry IP
> packet. But I am not sure I am correct. Does anyone knows 
> that some product
> does use the LLC frame to carry IP packets and why?

Our boxes (http://www.axis.com/products/) can use both 
Ethernet and 802.3 (RFC 1042) encapsulation. That way they
interoperates with systems using either frame type.
I'm not sure that anyone still needs this feature though...

--
Lars Viklund
Axis Communications AB
SE-223 70 Lund, Sweden



From owner-ietf-outbound  Tue Apr  4 05:30:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA25929
	for ietf-outbound.10@ietf.org; Tue, 4 Apr 2000 05:30:02 -0400 (EDT)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25872
	for <ietf@ietf.org>; Tue, 4 Apr 2000 05:28:41 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.9.3/8.9.3) id FAA15540;
	Tue, 4 Apr 2000 05:26:05 -0400 (EDT)
Date: Tue, 4 Apr 2000 05:26:05 -0400 (EDT)
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200004040926.FAA15540@newdev.harvard.edu>
To: krechmer@csrstds.com
Subject: Re: Standards and patents
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

you might study history - our process used to be that way & we changed it
to avoid problems that we found 

1/ refusal to negotiate
2/ false patent claims to delay the process
3/ patent claims from people who have nothing to do with the standards process
   and the claim could be years after the standard was adopted
4/ bringing the IETF into the business of determining the fairness of
   licensing terms

if you look at the current rules (rfc 2026) you will see that things
are not quite as simple as you imply - IPR is taken into account 
when it is time to advance a standard on the standards track

Scott

---
Date: Mon, 03 Apr 2000 22:07:03 -0700
To: ietf@ietf.org
From: Ken Krechmer <krechmer@csrstds.com>
Subject: Standards and patents

All,

Knowing my interest in this subject, Randy Bloomfield of the International
Center for Standards Research (university of Colorado, Boulder
International Telecommunications Program) has been kind enough to forward a
number of e-mails on this issue.  Enough, so that I thought I might try to
contribute.

The IETF has taken a unique position in the world of standardization
organizations.  The IETF is not a formal nationally recognized
standardization organization, yet the IETF is far too important to operate
as a fora or consortia.  By way of explanation, fora or consortia are
almost always commercially funded and quite often have, as part of their
"ground rules," a requirement that all participants enter into some form of
technology sharing (cross licensing or negotiated).  In other words, IPR is
not only identified in most fora or consortia, it is also negotiated.  This
is a distinct difference from the formal standardization (recognized by one
or more governments) organizations where IPR is usually identified, but
negotiation is not allowed.

The IETF, in regard to IPR, acts like a little like a formal
standardization organization.  It identifies intellectual property rights
(IPR) but leaves off requiring negotiation of IPR.  This, as is being shown
in many formal standardization organizations, may cause standards
development to migrate to organizations that identify and negotiate.  I
don't offer this approach as a solution, only an alternative, as such
negotiation in some fora or consortia smacks of coercion (IMO) when smaller
companies are negotiating with larger.

I make no arguments that the current patent system is useful to any but
lawyers.  But changing such a system is a lengthy political process.  I
suggest that the grounds for changing the existing patent system may be
based on the concept that patents were designed to award value to the
inventor of "similar" products. That is, for each incarnation of a product
that was "similar" to the invention, the inventor could receive a new form
of value (credit creation for the economists in the crowd).

Now patents are being used to control a different property -
"compatibility" and controlling "compatibility" feels more like controlling
access and therefore unfair.  Of course, there is enormous value in
controlling compatibility (e.g., Microsoft APIs, Intel software
compatibility, IBM data communications until recently) and so companies
attempt to do so.  Some day, likely far in the future, possibly patent law
can change to recognize that allowing commercial control of compatibility,
except in most unique circumstances, is of less benefit to society.  But
the patent law for the control of similarity for over 200 years has worked
reasonably well to reward inventors, yet distribute their inventions more
widely and more rapidly. For further comments on this topic please see
Communications Standards and Patent Rights: Conflict or Coordination?
http://www.csrstds.com/star.html


Ken Krechmer
Fellow
International Center for Standards Research
Interdisciplinary Telecommunications Program
University of Colorado at Boulder




From owner-ietf-outbound  Tue Apr  4 06:41:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA27707
	for ietf-outbound.10@ietf.org; Tue, 4 Apr 2000 06:40:02 -0400 (EDT)
Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27378
	for <ietf@ietf.org>; Tue, 4 Apr 2000 06:30:00 -0400 (EDT)
Received: from laptop.ix.netcom.com (tfx-us15-121.ix.netcom.com [207.94.236.121])
	by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id GAA14388
	for <ietf@ietf.org>; Tue, 4 Apr 2000 06:29:57 -0400 (EDT)
Message-Id: <4.3.2.20000329184829.00cb7a60@127.0.0.1>
X-Sender: rshockey/popd.ix.netcom.com@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Mon, 03 Apr 2000 18:51:01 -0500
To: ietf@ietf.org
From: Richard Shockey <rshockey@ix.netcom.com>
Subject: Does anyone have the URL for the WIERD doc on Wireless?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org



The Wireless Hot topic discussed IAB BOF in OZ.

tks.


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey
Shockey Consulting LLC
8045 Big Bend Blvd. Suite 110
St. Louis, MO 63119
Voice 314.918.9020
eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
INTERNET Mail & IFAX : rshockey@ix.netcom.com
GSTN Fax 314.918.9015
MediaGate iPost VoiceMail and Fax 800.260.4464
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<



From owner-ietf-outbound  Tue Apr  4 07:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA28222
	for ietf-outbound.10@ietf.org; Tue, 4 Apr 2000 07:00:02 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA28152
	for <ietf@ietf.org>; Tue, 4 Apr 2000 06:58:08 -0400 (EDT)
Received: from eucharisto.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.13417-0@bells.cs.ucl.ac.uk>; Tue, 4 Apr 2000 11:57:44 +0100
To: Graham Klyne <GK@Dial.pipex.com>
cc: ietf@ietf.org, J.Crowcroft@CS.UCL.AC.UK
Subject: Re: A thought about patents
In-reply-to: Your message of "Thu, 30 Mar 2000 23:18:31 BST." <4.2.2.20000330230917.00c1b760@pop.dial.pipex.com>
Date: Tue, 04 Apr 2000 11:57:43 +0100
Message-ID: <617.954845863@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <4.2.2.20000330230917.00c1b760@pop.dial.pipex.com>, Graham Klyne typ
ed:

 >>As many of us are finding, it seems to become more and more difficult to 
 >>develop or implement a standard without tripping over somebody-or-other's 
 >>patent for some piece of technology that many of us would regard as fairly 
 >>obvious or lacking in novelty.

prior art can be in the eye of the beholder

for example, i remember distinctly havign a discussio nwith a bunch of
cambridge university computer lab people about 
Noke Lick [TM] (sorry, Zero Click) technology based on eyetraxx ideas
(apologies to pat cadigan) -
basically, by using specular reflection analysis, its possibler to see
where on a screen someone is looking (quite easy) - by tracking this
over tiem as they browse, its possible to come up with a 
"signature" for when someone is about to click on "buy", and avoid
mouse use altogether

one of the grad students in cambrisdge on the nemesys project hacked
up a demonstrator (cool operating system work btw) - this would
predate a certain companies claim, and was certainly talked about in
public at a UK national, open workshop.... it is also
more obviosuly innovative, contains actual technology and
developement and testing time, and  is possibly not obvious (some of
the details at least are quite tricky)

i would claim that this undermines any system with clicks>0,
but some people might not....
 
 >>The recent announcement from the U.S. Patent and Trademark Office about 
 >>overhauling their scrutiny of applications for online business patents 
 >>seems to imply a tacit acknowledgement that their is a problem with the 
 >>review process with respect to discovery or prior art or determination of 
 >>novelty in a claimed invention.
 >
 >>My thought is this:  I'd like to see a presumption of lack of novelty if an 
 >>idea gets raised in a public forum, even if it happens _after_ a patent has 
 >>been applied for, unless it can be shown that the information came from 
 >>leakage of proprietary information.
 
 >>Maybe such an approach might ameliorate the "gold rush" mentality to be the 
 >>first to slap a patent on an idea or technique that is coming to be 
 >>accepted art in the normal process of technology evolution.
 
the other problem with patents is that challenging a patent after the
fact is typically as expensive as the lawyers that the richest
companies are prepared to pay for

given the intention of patents (to avoid company secrets, and to
promote reward for genuine innovation), this is the real problem, and
reflects  a mainly US problem with the way that lawyers are usually
rewarded and not punished for litigation - a profit/loss share
approach to defending patents might make this a more level playing
field....or a professional peer review process

 cheers

   jon

p.s. can we get below 0 clicks? perhaps: one small delta
is for us to have to do a noke-lick to NOT buy something online...

p.p.s this mail was composed on 1/4/00, if not sent then:-)



From owner-ietf-outbound  Tue Apr  4 07:30:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA29067
	for ietf-outbound.10@ietf.org; Tue, 4 Apr 2000 07:30:02 -0400 (EDT)
Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA28986
	for <ietf@ietf.org>; Tue, 4 Apr 2000 07:27:12 -0400 (EDT)
Received: (qmail 19482 invoked from network); 4 Apr 2000 11:27:12 -0000
Received: from userb681.uk.uudial.com (HELO GK-VAIO) (193.149.83.156)
  by smtp.dial.pipex.com with SMTP; 4 Apr 2000 11:27:12 -0000
Message-Id: <4.2.2.20000404111840.00b69740@pop.dial.pipex.com>
X-Sender: xex41@pop.dial.pipex.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 04 Apr 2000 11:22:40 +0100
To: ietf@ietf.org
From: Graham Klyne <GK@Dial.pipex.com>
Subject: Internet draft submissions
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

I have received conflicting statements on Internet draft submissions 
following the Adelaide cut-off:

 From the IETF-announce list:

   We will begin accepting submissions during the IETF (beginning March
   27), but remember we are all in Adelaide and the processing will not
   begin until the first week of April.

And in response to an attempted submission:

   We are sorry, but the cut-off for Internet-Draft submissions was Friday,
   March 10 at 5pm ET. Your submission will not be retained (i.e. you
   need to resubmit) after April 7th.

   Any submissions received prior to March 26, 2000 will not be retained;
   they must be resubmitted. Internet-Draft submissions received on or after
   March 27 will be processed. However, Internet-Draft announcements will
   not be sent until after the meeting concludes.

So when SHOULD we be able to submit?  March 27, or April 7?

#g

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound  Tue Apr  4 08:40:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA01127
	for ietf-outbound.10@ietf.org; Tue, 4 Apr 2000 08:40:03 -0400 (EDT)
Received: from mex.italtel.it (mex.italtel.it [138.132.117.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00918
	for <ietf@ietf.org>; Tue, 4 Apr 2000 08:32:49 -0400 (EDT)
Received: .(iltws72 [138.132.52.82]) by mex.italtel.it (8.9.0/8.9.0) with ESMTP id OAA11648
Received: .(localhost [127.0.0.1]) by iltws72.settimo.italtel.it (8.9.1a/8.9.1) with ESMTP
 id OAA10309
Received: from ic8u32.settimo.italtel.it (ic8u32.settimo.italtel.it [138.132.1.1])
	by mix.italtel.it (8.9.3/8.9.3) with SMTP id OAA25301;
	Tue, 4 Apr 2000 14:31:34 +0200 (MET DST)
Received: by ic8u32.settimo.italtel.it id AA31472; Tue, 4 Apr 2000 14:49:55 +0200
Received: from iltws09.settimo.italtel.it by ilt9h01.settimo.italtel.it with SMTP
	(1.38.193.5/16.2) id AA15404; Tue, 4 Apr 2000 14:22:33 +0200
Sender: buschman@icn.siemens.it
Message-Id: <38E9E14B.1022BCBD@icn.siemens.it>
Date: Tue, 04 Apr 2000 14:34:20 +0200
From: Jonathan Buschmann <Jonathan.Buschmann@icn.siemens.it>
Reply-To: Jonathan.Buschmann@icn.siemens.it
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
Mime-Version: 1.0
To: Richard Shockey <rshockey@ix.netcom.com>
Cc: ietf@ietf.org
Subject: Re: Does anyone have the URL for the WIERD doc on Wireless?
References: <4.3.2.20000329184829.00cb7a60@127.0.0.1>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Richard Shockey wrote:

> The Wireless Hot topic discussed IAB BOF in OZ.
>
> tks.
>

http://home.earthlink.net/~serotonin/HotTopicWireless.htm



From owner-ietf-outbound  Tue Apr  4 09:00:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA01708
	for ietf-outbound.10@ietf.org; Tue, 4 Apr 2000 09:00:02 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01496
	for <ietf@ietf.org>; Tue, 4 Apr 2000 08:52:02 -0400 (EDT)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id IAA13320;
	Tue, 4 Apr 2000 08:51:21 -0400 (EDT)
Sender: hgs@cs.columbia.edu
Message-ID: <38E9E549.B18EDB6E@cs.columbia.edu>
Date: Tue, 04 Apr 2000 08:51:21 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Toerless Eckert <Toerless.Eckert@Informatik.Uni-Erlangen.de>
CC: pkj@cypress.com, ietf@ietf.org
Subject: Re: A thought about patents
References: <200004040512.HAA15623@faui40.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Toerless Eckert wrote:
> 
> > The problem is that a patent provides a presumption of validity. Thus,
> > even if the patent ignores prior non-patent art, the creator of that
> > prior (published) art has to spend time and money defending himself in
> > court. Ultimately, that favors the big corporation with a standing army
> > of lawyers over any small or not-for-profit outfit. I'm not worried
> > about the stupid ideas (yes, there's a patent on including a list of
> > destination network addresses in a packet header to do multicast), but
> > rather the previously published and slightly non-obvious results.
> 
> True. Which still doesn't say that any "peers" would be the more favourable
> choice of review. What's needed is a prior-art database run by the PTO
> into which people can submit their pointers. Without that the PTO can really
> only well look up prior art that has been filed for patent. And the
> knowledge of prior art by "peers" is very selective too.

These databases are readily available and have been for years (inter
alia, the ISI (the other one) and databases licensable from IEEE and
ACM). If a patent examiner working in the area of networks does not
consult ITU, IETF and standard research conference publications, there
is no excuse. We expect any graduate student to know these sources. Peer
review will not identify all prior art, but more than it does now. As
far as I can tell (having been involved with a number of conferences), I
don't remember ever seeing an employee of the PTO show up at one of
these major conferences. Why not?

-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



From owner-ietf-outbound  Tue Apr  4 09:10:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA02089
	for ietf-outbound.10@ietf.org; Tue, 4 Apr 2000 09:10:01 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01502
	for <ietf@ietf.org>; Tue, 4 Apr 2000 08:52:03 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id HAA20984;
	Tue, 4 Apr 2000 07:51:10 -0500 (CDT)
Message-Id: <200004041251.HAA20984@rgfsparc.cr.usgs.gov>
Date: Tue, 4 Apr 2000 07:51:10 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: Does anyone have the URL for the WIERD doc on Wireless?
To: ietf@ietf.org, rshockey@ix.netcom.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: YNUyNjS32cD9FiTk2UoVaw==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>The Wireless Hot topic discussed IAB BOF in OZ.

You mean this one?

http://home.earthlink.net/~serotonin/HotTopicWireless.htm

RGF

Robert G. Ferrell, CISSP
Information Security Officer
National Business Center, US DoI
Robert_G_Ferrell@nbc.gov
------------------------------------------------------------
Nothing I have ever said should be construed as even vaguely
representing an official statement by the NBC or DoI.
------------------------------------------------------------



From owner-ietf-outbound  Tue Apr  4 12:51:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA08660
	for ietf-outbound.10@ietf.org; Tue, 4 Apr 2000 12:50:01 -0400 (EDT)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA08451
	for <ietf@ietf.org>; Tue, 4 Apr 2000 12:42:23 -0400 (EDT)
Received: (qmail 7867 invoked from network); 4 Apr 2000 16:42:19 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 4 Apr 2000 16:42:18 -0000
Received: (qmail 5593 invoked from network); 4 Apr 2000 16:42:17 -0000
Received: from ppp-46-225.lander.es (HELO salva) (195.76.46.225)
  by lince.lander.es with SMTP; 4 Apr 2000 16:42:17 -0000
Message-Id: <3.0.6.32.20000404184845.0079bd70@lince.lander.es>
X-Sender: svidal@lince.lander.es
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Tue, 04 Apr 2000 18:48:45 +0200
To: ietf@ietf.org
From: Salvador Vidal <svidal@lander.es>
Subject: Privacy & law
In-Reply-To: <Pine.LNX.4.10.10004020144230.4352-100000@dawn.pipis>
References: <200003302103.NAA06774@shell9.ba.best.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA08451
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Hi folks and all,

I think that as much conflicts that can be solved without the traditional
way: regulation + represion = burocracy + injustice, will be better for users.

Of course that always will remain Gansters that will require traditional
represion ways, i.e.:
At 02:25 02/04/00 +0300, Stephanos Piperoglou wrote:
>
>Cover your sensitive parts, because you're about to be hit by a big
>cluestick.

But on privacy questions we can try first to give technical solutions, i.e.
ways  to follow stamped data to oversee companies behavior and then inform
users about it automaticaly when they get in contact with these
companies,..., well I don´t know which utilities will work, but I think is
worthy to try some before being driven to legal solutions that only will be
able to reapir damages not to avoid them.

Does anyone know about any woorking group about this, that cost least than
50.000 $?

Thank you,

Salva



From owner-ietf-outbound  Tue Apr  4 18:40:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA19206
	for ietf-outbound.10@ietf.org; Tue, 4 Apr 2000 18:40:01 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19008
	for <ietf@ietf.org>; Tue, 4 Apr 2000 18:31:27 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id SAA29967;
        Tue, 4 Apr 2000 18:30:34 -0400 (EDT)
Message-Id: <200004042230.SAA29967@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Scott Bradner <sob@harvard.edu>
cc: krechmer@csrstds.com, ietf@ietf.org
Subject: Re: Standards and patents 
In-reply-to: Your message of "Tue, 04 Apr 2000 05:26:05 EDT."
             <200004040926.FAA15540@newdev.harvard.edu> 
Date: Tue, 04 Apr 2000 18:30:34 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

>  IPR is taken into account 
> when it is time to advance a standard on the standards track

and in practice, IPR is also taken into account by individual
participants (if they know about it) when they decide whether 
to contribute to a consensus for Proposed Standard. 

Keith




From owner-ietf-outbound  Wed Apr  5 00:30:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA24627
	for ietf-outbound.10@ietf.org; Wed, 5 Apr 2000 00:30:03 -0400 (EDT)
Received: from arcc.or.ke (root@[212.49.87.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24588
	for <ietf@ietf.org>; Wed, 5 Apr 2000 00:24:50 -0400 (EDT)
Received: from 199.2.222.254 ([212.49.87.152])
	by arcc.or.ke (8.9.3/8.9) with SMTP id HAA23886
	for <ietf@ietf.org>; Wed, 5 Apr 2000 07:40:12 +0300 (EAT)
Date: Wed, 5 Apr 2000 07:40:12 +0300 (EAT)
Message-Id: <200004050440.HAA23886@arcc.or.ke>
X-Sender: musandu@199.2.222.254
X-Mailer: Windows Eudora Pro Version 2.1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: Musandu <musandu@arcc.or.ke>
Subject: GSM 900 /1800, UMTS bandwidth
X-Loop: ietf@ietf.org

If you are using a GSM 900/1800 network for internet access what are the
optimal bandwidth qualities, and what are the bandwidth qualities of
existing UMTS networks?

Yours truly,
Nyagudi Musandu



From owner-ietf-outbound  Wed Apr  5 14:01:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA13893
	for ietf-outbound.10@ietf.org; Wed, 5 Apr 2000 14:00:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13735
	for <ietf@ietf.org>; Wed, 5 Apr 2000 13:50:29 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id NAA09337;
	Wed, 5 Apr 2000 13:49:09 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: "'Musandu'" <musandu@arcc.or.ke>, <ietf@ietf.org>
Subject: RE: GSM 900 /1800, UMTS bandwidth
Date: Wed, 5 Apr 2000 13:52:38 -0400
Message-ID: <002901bf9f27$bbf50080$d001010a@tst.ennovatenetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-reply-to: <200004050440.HAA23886@arcc.or.ke>
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



> If you are using a GSM 900/1800 network for internet access 
> what are the
> optimal bandwidth qualities, and what are the bandwidth qualities of
> existing UMTS networks?
> 

I don't know if I really understand your questions. If you connect with 
appropriate modem/device you should be able to get the following 
channel bandwidth for data applications.:

2+ = GSM Phase 2+
GSM CSD = GSM Circuit Switched Data (14.4kbps * n) 
GPRS = General Packet Radio System Data (up to 164 kbps)
EDGE = Enhanced Data GSM Environment (up to 560 kbps)
UMTS = Universal Mobile Telephone Service (up to 2 Mbps but only 
in a micro cell.)


Cheers,

--brijesh



From owner-ietf-outbound  Wed Apr  5 17:30:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA16736
	for ietf-outbound.10@ietf.org; Wed, 5 Apr 2000 17:30:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16658
	for <ietf@ietf.org>; Wed, 5 Apr 2000 17:25:51 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12cxJ6-0000fn-00
	for ietf@ietf.org; Wed, 05 Apr 2000 22:25:48 +0100
Date: Wed, 5 Apr 2000 22:25:40 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: ietf@ietf.org
Subject: end-of-rfc-index.txt
Message-ID: <Pine.GSO.4.21.0004052217440.138-100000@petra.ee.surrey.ac.uk>
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-Loop: ietf@ietf.org

I'd like to suggest that rfc/rfc-index.txt
have at its end a terminating

'this list of RFCs was valid as of $Date$'.

so that you have some idea of the freshness of your chosen mirror.

(It would make more sense to me if this was at the top and the list
 was ordered reverse-chronologically so that the first search for a
 keyword found the obsoleting rather than the several-times-obsoleted,
 but I can't see much chance of that happening. Being forced to read
 history is probably good for you, in any case.)

L.

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




From owner-ietf-outbound  Wed Apr  5 19:10:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA17494
	for ietf-outbound.10@ietf.org; Wed, 5 Apr 2000 19:10:02 -0400 (EDT)
Received: from tesla.umkc.edu (hilbert.umkc.edu [134.193.4.60])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA17456
	for <ietf@ietf.org>; Wed, 5 Apr 2000 19:06:32 -0400 (EDT)
Received: (qmail 486488 invoked from network); 5 Apr 2000 23:04:52 -0000
Received: from lucy.ssb.umkc.edu (HELO kasey.umkc.edu) (david@134.193.69.99)
  by hilbert.umkc.edu with SMTP; 5 Apr 2000 23:04:52 -0000
Sender: david
Message-ID: <38EBC6B7.116B423E@kasey.umkc.edu>
Date: Wed, 05 Apr 2000 23:05:27 +0000
From: "David L. Nicol" <david@kasey.umkc.edu>
Organization: University of Missouri - Kansas City network operations
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-mosix i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Miller <dave@buyutree.com>
CC: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: A thought about patents
References: <002001bf9d27$cf197260$0400a8c0@qualcomm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Dave Miller wrote:

> - I wonder how much of government we can get rid of if we keep chipping away
> at it?


I see this a lot in discussions of government reform: Imagine your
reform happens, and bureaucratic rot sets in.  After a hundred years
or so, you will have something very similar to the present system you
are complaining about.

After publishing your idea somewhere, for public critique, you have
a year to file your patent application.  After that it becomes a
public prior art.

Am I wrong?


Getting a patent costs money -- maybe not enough to hire good patent
clerks,
but enough to keep today's garage tinkerers from doing it -- with some
obvious exceptions


 
____________________________________________________________________
                            David Nicol 816.235.1187 nicold@umkc.edu



From owner-ietf-outbound  Wed Apr  5 20:10:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA17905
	for ietf-outbound.10@ietf.org; Wed, 5 Apr 2000 20:10:02 -0400 (EDT)
Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17797
	for <ietf@ietf.org>; Wed, 5 Apr 2000 20:00:25 -0400 (EDT)
Received: from Software.com ([207.175.94.182]) by mta1biz.bizmailsrvcs.net
          with ESMTP
          id <20000405235955.NNSU851310.mta1biz.bizmailsrvcs.net@Software.com>
          for <ietf@ietf.org>; Wed, 5 Apr 2000 18:59:55 -0500
Sender: droyer
Message-ID: <38EBC45E.F00C0C88@Software.com>
Date: Wed, 05 Apr 2000 15:55:26 -0700
From: Doug Royer <Doug.Royer@Software.com>
Reply-To: ietf@ietf.org
Organization: Software.com
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A thought about patents
References: <002001bf9d27$cf197260$0400a8c0@qualcomm.com> <38EBC6B7.116B423E@kasey.umkc.edu>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msCEE70B338CC2E7C64EF9FF5F"
X-Loop: ietf@ietf.org

This is a cryptographically signed message in MIME format.

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

"David L. Nicol" wrote:
>
> After publishing your idea somewhere, for public critique, you have
> a year to file your patent application.  After that it becomes a
> public prior art.
> 
> Am I wrong?

Or if it is a little past a year, and you can show that you
have done your best - you can also get the patent. It's not
a hard set time limit.

-Doug
--------------msCEE70B338CC2E7C64EF9FF5F
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIIKVQYJKoZIhvcNAQcCoIIKRjCCCkICAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CCIwggTsMIIEVaADAgECAhA2tOutfntkPZeWwhSMC60VMA0GCSqGSIb3DQEBBAUAMIHMMRcw
FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5
IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp
dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAwMDExNzAwMDAw
MFoXDTAwMTAxMzIzNTk1OVowggEZMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE
CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y
ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO
ZXRzY2FwZSBGdWxsIFNlcnZpY2UxGDAWBgNVBAMUD0RvdWdsYXMgTSBSb3llcjEmMCQGCSqG
SIb3DQEJARYXZG91Zy5yb3llckBzb2Z0d2FyZS5jb20wXDANBgkqhkiG9w0BAQEFAANLADBI
AkEA8b+/7AusCQc89McoXWlPBDcEaOyt/e2NdL+lPypsoauWxoLohWrk708y93xfziOVZ/Jh
3yF9Dq43K9rW9m8SewIDAQABo4IBwTCCAb0wCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGe
BgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t
L0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3Mg
Q1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJ
YIZIAYb4QgEBBAQDAgeAMIGGBgpghkgBhvhFAQYDBHgWdmQ0NjUyYmQ2M2YyMDQ3MDI5Mjk4
NzYzYzlkMmYyNzUwNjljNzM1OWJlZDFiMDU5ZGE3NWJjNGJjOTcwMTc0N2RhNWQzZjIxNDFi
ZWFkYjJiZDJlODkyMWZhODZiZjFkMTExNDk5ZmEzYmE0N2ZkZjNlYTQ1MDYwMAYKYIZIAYb4
RQEGBwQiFiA2NWVlMGM5M2RkNDY2OGJjNGViOGM2OWNiMDliZWYxNzAzBgNVHR8ELDAqMCig
JqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0GCSqGSIb3DQEBBAUA
A4GBAIfiBv6wsXfERKczHkNCZ3zPRgSs/eOEutA2lnTtejz+sHTm3XWcEEx0zcEkYafFIOCK
GFgFsy6cR4czApnWlILPzDAyT+FcDsAqTtSGDL8jTVMo/7MW6CHReAc0oSzGtapMxWcLgaMh
/D0lM5vSddVM7EgNhGLWQPoAvxKe4PExMIIDLjCCApegAwIBAgIRANJ2Lo0UDD19sqglXa/u
DXUwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0
aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZl
cmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQL
Ez13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFC
LkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vi
c2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ
AoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJvnFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI
4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpdtrA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqO
f2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMBAAGjfDB6MBEGCWCGSAGG+EIBAQQEAwIBBjBH
BgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0wKwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5j
b20vcmVwb3NpdG9yeS9SUEEwDwYDVR0TBAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZI
hvcNAQECBQADgYEAiLg3O93alDcAraqf4YEBcR6Sam0v9vGd08pkONwbmAwHhluFFWoPuUmF
pJXxF31ntH8tLN2aQp7DPrSOquULBt7yVir6M8e+GddTTMO9yOMXtaRJQmPswqYXD11YGkk8
kFxVo2UgAP0YIOVfgqaxqJLFWGrBjQM868PNBaKQrm4xggH7MIIB9wIBATCB4TCBzDEXMBUG
A1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
RjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBS
ZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0EgSW5kaXZp
ZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQNrTrrX57ZD2XlsIUjAut
FTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkF
MQ8XDTAwMDQwNTIyNTUyOFowIwYJKoZIhvcNAQkEMRYEFLC0JV6IInZ1ElxX1DWN2LT+UNja
MFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMAcGBSsOAwIH
MA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3DQEBAQUABEAzUrK0XhpL
pMSoTMQHf4WIkpqO0iNh31M278aEeCUqNtR5DHaKXFXoWd8x/boIkvIJnFIzUT9WXoO4sGfL
YY56
--------------msCEE70B338CC2E7C64EF9FF5F--



From owner-ietf-outbound  Wed Apr  5 21:20:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA18593
	for ietf-outbound.10@ietf.org; Wed, 5 Apr 2000 21:20:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18493
	for <ietf@ietf.org>; Wed, 5 Apr 2000 21:11:54 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200004060104.KAA18753@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id KAA18753; Thu, 6 Apr 2000 10:04:22 +0900
Subject: Re: A thought about patents
To: GK@Dial.pipex.com (Graham Klyne)
Date: Thu, 6 Apr 0 10:04:20 JST
Cc: ietf@ietf.org
In-Reply-To: <4.2.2.20000330230917.00c1b760@pop.dial.pipex.com>; from "Graham Klyne" at Mar 31, 100 7:32 am
X-Mailer: ELM [version 2.3 PL11]
X-Loop: ietf@ietf.org

Graham;

> The recent announcement from the U.S. Patent and Trademark Office about 
> overhauling their scrutiny of applications for online business patents 
> seems to imply a tacit acknowledgement that their is a problem with the 
> review process with respect to discovery or prior art or determination of 
> novelty in a claimed invention.

The Internet solves the problem.

Online business patents are, at large, ineffective and harmless.

We can have servers outside of US and there is no legislation (even
under US laws. note that the servers can serve yet another countries)
to make the servers illegal.

Clients in US may still be a target of a patent, if claims of the
patents do not cover servers and cover the clients only.

However, virtually no one can control downloading of software from
the servers to the clients at home.

As the Internet is not a collection of private IP networks connected
by NAT boxes, ISP has no knowledge nor responsibility on what their
customers are doing.

It's like copyright, so called, piracy, against which Holywood is
fighting seemingly in vain.

But, in this case, there is no problem of copyright violation.

The only effect of the patents is that they drive servers outside
of US and makes the Internet a lot more globally connected. :-)

							Masataka Ohta

PS

I don't protect this message by patents or by copyright. :-)



From owner-ietf-outbound  Thu Apr  6 06:00:45 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA06223
	for ietf-outbound.10@ietf.org; Thu, 6 Apr 2000 06:00:01 -0400 (EDT)
Received: from jaws.cisco.com (jaws.cisco.com [198.135.0.150])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06190
	for <ietf@ietf.org>; Thu, 6 Apr 2000 05:58:13 -0400 (EDT)
Received: from cisco.com (lon-sto4-lan-vlan132-dhcp52.cisco.com [144.254.108.55])
	by jaws.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id KAA20937;
	Thu, 6 Apr 2000 10:57:44 +0100 (BST)
Message-ID: <38EC5F7E.BE9090F1@cisco.com>
Date: Thu, 06 Apr 2000 10:57:18 +0100
From: Stewart Bryant <stbryant@cisco.com>
Reply-To: stbryant@cisco.com
Organization: Cisco Systems, Inc.
X-Mailer: Mozilla 4.5 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A thought about patents
References: <002001bf9d27$cf197260$0400a8c0@qualcomm.com> <38EBC6B7.116B423E@kasey.umkc.edu> <38EBC45E.F00C0C88@Software.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Check with the lawyers, but I think that you will find that this 
is strictly a US view of patents. In every other country any public 
disclosure anywhere immediately voids the right to patent. Even 
NDA disclosure can be tricky, because an offer for sale counts 
as a disclosure.

Stewart

Doug Royer wrote:
> 
> "David L. Nicol" wrote:
> >
> > After publishing your idea somewhere, for public critique, you have
> > a year to file your patent application.  After that it becomes a
> > public prior art.
> >
> > Am I wrong?
> 
> Or if it is a little past a year, and you can show that you
> have done your best - you can also get the patent. It's not
> a hard set time limit.
> 
> -Doug



From owner-ietf-outbound  Thu Apr  6 10:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08398
	for ietf-outbound.10@ietf.org; Thu, 6 Apr 2000 10:00:02 -0400 (EDT)
Received: from un1b.satlink.com (un1b.satlink.com [200.9.212.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08368
	for <ietf@ietf.org>; Thu, 6 Apr 2000 09:58:13 -0400 (EDT)
Received: from un7.satlink.com (root@un7.satlink.com [200.9.212.4])
	by un1b.satlink.com (8.9.3/8.9.3) with ESMTP id LAA26610
	for <ietf@ietf.org>; Thu, 6 Apr 2000 11:02:55 -0300
Received: from famiq.UUCP (Ufamiq@localhost)
	by un7.satlink.com (8.9.3/8.9.1) with UUCP id KAA01666
	for ietf.org!ietf; Thu, 6 Apr 2000 10:41:38 -0300
X-Authentication-Warning: un7.satlink.com: Ufamiq set sender to famiq!martin!famiq.com.ar!smm using -f
Received: from martin by famiq.com.ar id ab12757; 6 Apr 100 10:04 EST
Message-Id: <3.0.1.32.20000406100001.006fdbec@193.0.0.50>
X-Sender: smm@193.0.0.50
X-Mailer: Windows Eudora Pro Version 3.0.1 (32) [S]
Date: Thu, 06 Apr 2000 10:00:01 -0300
To: ietf@ietf.org
From: Martin Montenegro <smm@famiq.com.ar>
Subject: Re: Privacy & law
In-Reply-To: <3.0.6.32.20000404184845.0079bd70@lince.lander.es>
References: <Pine.LNX.4.10.10004020144230.4352-100000@dawn.pipis>
 <200003302103.NAA06774@shell9.ba.best.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA08368
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Salvador Vidal <svidal@lander.es> wrote:
>I think that as much conflicts that can be solved without the traditional
>way: regulation + represion = burocracy + injustice, will be better for
users.
>But on privacy questions we can try first to give technical solutions, i.e.
>ways  to follow stamped data to oversee companies behavior and then inform
>users about it automaticaly when they get in contact with these
>companies,..., well I don´t know which utilities will work, but I think is
>worthy to try some before being driven to legal solutions that only will be
>able to reapir damages not to avoid them.

I think that we are in front of the progress ´s victory over the politics
's ideas.
See the advance of technology like a flood and the politics like a glass.
The humanity is really in front of the product of the knowledge of some
persons and is trying to save your houses of the flood with a small glass.
That bring an inevitable break of the actually concepts about the limits
and jurisdictions of the law.
Some countries(goverments) are afraid to lose the domain on commerce and 
in a future they will take acctions(any action!!) to regulate all in this
actually paradise of finances.



Martin Montenegro



From owner-ietf-outbound  Thu Apr  6 11:30:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA09833
	for ietf-outbound.10@ietf.org; Thu, 6 Apr 2000 11:30:03 -0400 (EDT)
Received: from mailhost.metro-optix.com (nat129.metro-optix.com [63.91.47.129])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09740
	for <ietf@ietf.org>; Thu, 6 Apr 2000 11:23:27 -0400 (EDT)
Received: by mailhost.axa100.am.ericsson.se with Internet Mail Service (5.5.2650.21)
	id <2H9NPYAX>; Thu, 6 Apr 2000 10:19:12 -0500
Message-ID: <D7F6115661E9D311834F006008F5C83C096304@mailhost.axa100.am.ericsson.se>
From: David Wang <david.wang@metro-optix.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: MPLS and Private Network
Date: Thu, 6 Apr 2000 10:19:12 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BF9FDB.76767B56"
X-Loop: ietf@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BF9FDB.76767B56
Content-Type: text/plain;
	charset="iso-8859-1"

Dear Friends,

A company consists of 2 remotely separated sites, A and B. A leased T1 line
connects the networks on these 2 sites together. We generally call the
company's network a private network since the connection between the 2 sites
are private leased line. 

Now the service provider replace this leased T1 line with a 1.544 mbps MPLS
LSP (Label Switched Path). Is this company's network still a private
network? Is it still as secure as it was before ? why ? 

We know that the MPLS LSP has gone through many LSR (Label Switch Router)
and has been manipulated by the service providers. But the leased T1 line
has been manipulated by the service providers too. The signal may be
multiplex into DS3, OC-3, OC-12, OC-48, OC-192 then de-multiplex back to
OC-48, OC-12, OC-3, DS3, DS1.

Please help me if you know the answers.

Thanks
David


------_=_NextPart_001_01BF9FDB.76767B56
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>MPLS and Private Network</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Dear Friends,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">A company consists of 2 remotely =
separated sites, A and B. A leased T1 line connects the networks on =
these 2 sites together. We generally call the company's network a =
private network since the connection between the 2 sites are private =
leased line. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Now the service provider replace this =
leased T1 line with a 1.544 mbps MPLS LSP (Label Switched Path). Is =
this company's network still a private network? Is it still as secure =
as it was before ? why ? </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">We know that the MPLS LSP has gone =
through many LSR (Label Switch Router) and has been manipulated by the =
service providers. But the leased T1 line has been manipulated by the =
service providers too. The signal may be multiplex into DS3, OC-3, =
OC-12, OC-48, OC-192 then de-multiplex back to OC-48, OC-12, OC-3, DS3, =
DS1.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Please help me if you know the =
answers.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">David</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BF9FDB.76767B56--



From owner-ietf-outbound  Thu Apr  6 12:20:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA10563
	for ietf-outbound.10@ietf.org; Thu, 6 Apr 2000 12:20:02 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10446
	for <ietf@ietf.org>; Thu, 6 Apr 2000 12:12:09 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id MAA17595
	for <ietf@ietf.org>; Thu, 6 Apr 2000 12:08:17 -0400
Sender: francis@localhost.localdomain
Message-ID: <38ECB670.62E6377E@ecal.com>
Date: Thu, 06 Apr 2000 12:08:17 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A thought about patents
References: <000001bf9d86$b45f82c0$d001010a@tst.ennovatenetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Brijesh Kumar wrote:

> Granting of patents only means that a person grated a particular patent
> was first to make "a claim" about the novelty of an idea or technique
> as far as the patent office knows on the basis of "previous claims submitted
> to it.".

At least in the US, at least sometimes, the examiners do at least some
literature search.  I remember being involved in a patent where the examiner
sent it back with an article clipped from the trade press.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Among animals, it's eat or be eaten. Among   |
|francis@ecal.com|people, it's define or be defined.           |
\==============================================================/





From owner-ietf-outbound  Thu Apr  6 12:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA10721
	for ietf-outbound.10@ietf.org; Thu, 6 Apr 2000 12:30:03 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10494
	for <ietf@ietf.org>; Thu, 6 Apr 2000 12:15:41 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id MAA17601
	for <ietf@ietf.org>; Thu, 6 Apr 2000 12:11:49 -0400
Sender: francis@localhost.localdomain
Message-ID: <38ECB745.35C6E37F@ecal.com>
Date: Thu, 06 Apr 2000 12:11:49 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A thought about patents
References: <200004060104.KAA18753@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Masataka Ohta wrote:

> We can have servers outside of US and there is no legislation (even
> under US laws. note that the servers can serve yet another countries)
> to make the servers illegal.

Mmm...that sounds like a grey area.  A company using patented tech to do
business in the US may be subject to US law even if the tech is not resident
in the US (under the same sort of theory used against Internet gambling).
Even if it's not true in the general case, a sufficiently expensive lawyer
might be able to convince the court that, since the Internet makes location
irrelevant, the location of the infringement is irrelevant.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Among animals, it's eat or be eaten. Among   |
|francis@ecal.com|people, it's define or be defined.           |
\==============================================================/





From owner-ietf-outbound  Thu Apr  6 12:50:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA11211
	for ietf-outbound.10@ietf.org; Thu, 6 Apr 2000 12:50:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11003;
	Thu, 6 Apr 2000 12:42:31 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA15198;
        Thu, 6 Apr 2000 12:41:33 -0400 (EDT)
Message-Id: <200004061641.MAA15198@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
X-PGP-Key: 2F07A741 ; 78 15 8E 8B C0 06 5D D1  BC 08 05 7F 42 81 7E 90 
To: rfc-ed@rfc-editor.org
Subject: recommendation against publication of draft-cerpa-necp-02.txt
cc: moore@cs.utk.edu, iesg@ietf.org, ietf@ietf.org
From: Keith Moore <moore@cs.utk.edu>
Date: Thu, 06 Apr 2000 12:41:33 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

I am writing to request that the RFC Editor not publish 
draft-cerpa-necp-02.txt as an RFC in its current form,
for the following reasons:

1. The document repeatedly, and misleadingly, refers to NECP as a 
standard.  I do not believe this is appropriate for a document
which is not on the IETF standards track.  It also refers to
some features as "mandatory" even though it's not clear what
it means for a non-standard to have mandatory features.


2. A primary purpose of the NECP protocol appears to be to 
facilitate the operation of so-called interception proxies.  Such 
proxies violate the Internet Protocol in several ways: 

(1) they redirect traffic to a destination other than the one 
specified in the IP header, 

(2) they impersonate other IP hosts by using those hosts' IP addresses 
as source addresses in traffic they generate,

(3) for some interception proxies, traffic which is passed on to the 
destination host, is modified in transit, and any packet-level
checksums are regenerated.

IP allows for the network to delay, drop, or duplicate IP packets,
as part of a best effort to route them to their intended destination.
But it does not allow the above practices.

This document implicitly treats such behavior as legitimate even
though it violates the primary standard on which all Internet
interoperability depends.


3. Aside from the technical implications of intercepting traffic, 
redirecting it to unintended destinations, or forging traffic from
someone else's IP address - there are also legal, social, moral
and commercial implications of doing so.

In my opinion IETF should not be lending support to such dubious
practices by publishing an RFC which implicitly endorses them,
even though the authors are employed by major research institutions 
and hardware vendors.


4. Furthermore, while any of the above practice might be deemed "morally"
acceptable in limited circumstances (such as when the interception proxy 
is being operated by the same party as the one which operates the host being 
impersonated) in general these are very dangerous.  There have been numerous 
cases where network elements employing practices similar to the above have 
been demonstrated to harm interoperability.  (e.g. there is a widely-used
SMTP firewall product which breaks SMTP extension negotiation, and a 
traffic shaping product was recently found to corrupt data in TCP streams
generated by certain kinds of hosts) 

This document contains language touting the benefits of NECP but very 
little language describing the danger of using the above techniques which 
NECP was designed to support.   Where the document does mention the 
problems, it is misleading or incomplete.  For example, the Introduction says 

   However, it [an interception proxy] can cause problems: users
   have no way to go directly to origin servers, as may be required in
   some cases (e.g., servers that authenticate using a client's source
   IP address).  The proxy has a high-level understanding of the
   application protocol; it can detect these cases and decide which
   flows should be cut through to origin servers.  

The latter sentence is a false assertion - even though the proxy has
a high level understanding of the protocol, the proxy is not generally
able to determine when cut-through is required.   For example, the
service being impersonated by the interception proxy may have uses for
the client's source address which are outside of the protocol being
intercepted and for which the proxy cannot be knowledgable.
Such uses may be both active (in that they involve attempts to establish
other traffic between the origin server and the client, or between the
client and other hosts on the network), or passive (in which the origin 
server uses the client's IP address without attempting to communicate
with it), or even deferred (in which an attempt is made to communicate
with the client's IP address at a later time).  In addition, the *user* 
may have a requirement for his client to talk directly to an origin server, 
or the content provider may have a requirement for the origin server to 
talk directly to a client, simply because they expect communications 
integrity.  By its very nature an interception proxy ignores the 
requirements of the user and/or the content provider.

The document refers to two other documents which it says further
describe the dangers of interception proxies: "Internet Web Replication 
and Caching Taxonomy" [reference 3], and "Known HTTP Proxy/Caching Problems".
Both of these appear to be works in progress, and the latter document does 
not even have a reference.  Until such documents are published, or 
at least until they are deemed ready for publication by their creators, 
it is impossible to evaluate whether they contain sufficient and
accurate information to inform readers of the NECP document about
the dangers of interception proxies.


5. While in one sense NECP is an attempt to alleviate some of the harm done 
by interception proxies, this document is clearly intended to encourage 
and promote the use of such proxies by providing a uniform cross-vendor 
interface between such proxies and network elements.

Given that NECP is intended to support violations of the Internet Protocol,
and that such violations are known to harm interoperability, such promotion 
is a misuse of the RFC document series.  



In summary, my recommendation is that the document not be published until:

- the promotional material is removed, leaving only technical justification
  and specification

- the document is changed to point out that interception proxies are
  nonstandard, that they violate the Internet Protocol, and that they
  are known to degrade interoperability

- a disclaimer is added, which points out that interception proxies 
  are engaged in interception, misrepresentation, and forgery of network
  traffic, that such practices are not endorsed by IETF, and that they
  may be illegal in some jurisdictions.

- the documents describing the dangers of interception proxies
  which are referenced by the NECP document are ready for 
  publication, and are deemed reasonably complete and accurate.


But I would also recommend that the document not be published at all, 
as I believe that publication of this document will do far more to
degrade the interoperability of the Internet than it can do to help it.

There may indeed be value in publishing the document as a contribution
to the historic record of Internet development, as it certainly reflects 
some current trends.  However this goal could be accomplished by 
delaying publication of the NECP document by several years, or at least,
until the publication of technically sound, standardized, solutions for 
the problems that interception proxies attempt to address.

best regards,

Keith Moore



From owner-ietf-outbound  Thu Apr  6 14:42:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA12623
	for ietf-outbound.10@ietf.org; Thu, 6 Apr 2000 14:40:03 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12591
	for <ietf@ietf.org>; Thu, 6 Apr 2000 14:38:12 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id OAA14038;
	Thu, 6 Apr 2000 14:37:42 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: "'David Wang'" <david.wang@metro-optix.com>, <ietf@ietf.org>
Subject: RE: MPLS and Private Network
Date: Thu, 6 Apr 2000 14:41:11 -0400
Message-ID: <001501bf9ff7$aee75d40$d001010a@tst.ennovatenetworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0016_01BF9FD6.27D5BD40"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <D7F6115661E9D311834F006008F5C83C096304@mailhost.axa100.am.ericsson.se>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0016_01BF9FD6.27D5BD40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

MPLS and Private NetworkDavid Wang writes:
  A company consists of 2 remotely separated sites, A and B. A leased T1
line connects the networks on these 2 sites together. We generally call the
company's network a private network since the connection between the 2 sites
are private leased line.

  Now the service provider replace this leased T1 line with a 1.544 mbps
MPLS LSP (Label Switched Path). Is this company's network still a private
network? Is it still as secure as it was before ? why ?

  We know that the MPLS LSP has gone through many LSR (Label Switch Router)
and has been manipulated by the service providers. But the leased T1 line
has been manipulated by the service providers too. The signal may be
multiplex into DS3, OC-3, OC-12, OC-48, OC-192 then de-multiplex back to
OC-48, OC-12, OC-3, DS3, DS1.

If the carrer backbone network is seggregated as before, the signalling or
forwarding mechanism used in the
core network shouldn't make any difference to you. Security and throughput
should remain same.

Cheers,

--brijesh

------=_NextPart_000_0016_01BF9FD6.27D5BD40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>MPLS and Private Network</TITLE>

<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D210452118-06042000>David=20
Wang writes:</SPAN></FONT></DIV><SPAN class=3D210452118-06042000>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px">
  <P><FONT color=3D#0000ff face=3DArial size=3D2>A company consists of 2 =
remotely=20
  separated sites, A and B. A leased T1 line connects the networks on =
these 2=20
  sites together. We generally call the company's network a private =
network=20
  since the connection between the 2 sites are private leased line. =
</FONT></P>
  <P><FONT color=3D#0000ff face=3DArial size=3D2>Now the service =
provider replace this=20
  leased T1 line with a 1.544 mbps MPLS LSP (Label Switched Path). Is =
this=20
  company's network still a private network? Is it still as secure as it =
was=20
  before ? why ? </FONT></P>
  <P><FONT color=3D#0000ff face=3DArial size=3D2>We know that the MPLS =
LSP has gone=20
  through many LSR (Label Switch Router) and has been manipulated by the =
service=20
  providers. But the leased T1 line has been manipulated by the service=20
  providers too. The signal may be multiplex into DS3, OC-3, OC-12, =
OC-48,=20
  OC-192 then de-multiplex back to OC-48, OC-12, OC-3, DS3,=20
DS1.</FONT></P></BLOCKQUOTE>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2>If the carrer backbone =
network is=20
seggregated as before,&nbsp;the signalling or forwarding =
mechanism&nbsp;used in=20
the </FONT></DIV>
<DIV><FONT size=3D2><FONT color=3D#0000ff><FONT face=3DArial>core =
network shouldn't=20
make any difference to you.<SPAN =
class=3D210452118-06042000>&nbsp;</SPAN><SPAN=20
class=3D210452118-06042000>Security and&nbsp;throughput should remain =
same.=20
</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT color=3D#0000ff><FONT face=3DArial><SPAN=20
class=3D210452118-06042000></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D210452118-06042000>Cheers,</SPAN></FONT></DIV>
<DIV><SPAN class=3D210452118-06042000></SPAN>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D210452118-06042000>--brijesh</SPAN></FONT></DIV></SPAN></BODY></H=
TML>

------=_NextPart_000_0016_01BF9FD6.27D5BD40--



From owner-ietf-outbound  Thu Apr  6 19:00:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA16417
	for ietf-outbound.10@ietf.org; Thu, 6 Apr 2000 19:00:05 -0400 (EDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16371
	for <ietf@ietf.org>; Thu, 6 Apr 2000 18:57:23 -0400 (EDT)
Received: from fedex.cisco.com (fedex.cisco.com [171.69.198.220])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id PAA10126
	for <ietf@ietf.org>; Thu, 6 Apr 2000 15:56:57 -0700 (PDT)
Received: from cisco.com ([10.19.253.250])
	by fedex.cisco.com (Mirapoint)
	with ESMTP id AAG08934 (AUTH abierman);
	Thu, 6 Apr 2000 15:56:51 -0700 (PDT)
Message-ID: <38ED16D6.E6B219F4@cisco.com>
Date: Thu, 06 Apr 2000 15:59:34 -0700
From: Andy Bierman <abierman@cisco.com>
Organization: Cisco Systems, Inc.
X-Mailer: Mozilla 4.72 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: [Fwd: RMONMIB WG interim meeting announcement]
Content-Type: multipart/mixed;
 boundary="------------BC97A638DEF9C17501ECCE81"
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.
--------------BC97A638DEF9C17501ECCE81
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

 
--------------BC97A638DEF9C17501ECCE81
Content-Type: message/rfc822
Content-Disposition: inline

Return-Path: <list-owner-incoming-rlanmib@kickme.cisco.com>
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42])
	by fedex.cisco.com (Mirapoint)
	with ESMTP id AAG08596;
	Thu, 6 Apr 2000 15:43:06 -0700 (PDT)
Received: from domohead.cisco.com (domohead.cisco.com [171.69.2.97])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id PAA01361
	for <incoming-rlanmib@domestic.cisco.com>; Thu, 6 Apr 2000 15:42:11 -0700 (PDT)
Received: by domohead.cisco.com (8.9.1/8.9.1) id PAA09982
	for Rmonmib-outgoing; Thu, 6 Apr 2000 15:30:31 -0700 (PDT)
Received: by domohead.cisco.com (8.9.1/8.9.1) id PAA09977
	for mailto-rmonmib@domohead.cisco.com; Thu, 6 Apr 2000 15:30:29 -0700 (PDT)
Received: from sj-mailhub-3.cisco.com (sj-mailhub-3.cisco.com [171.68.224.215])
	by domohead.cisco.com (8.9.1/8.9.1) with ESMTP id PAA09973
	for <rmonmib-proc@domohead.cisco.com>; Thu, 6 Apr 2000 15:30:28 -0700 (PDT)
Received: from fedex.cisco.com (fedex.cisco.com [171.69.198.220])
	by sj-mailhub-3.cisco.com (8.9.1a/8.9.1) with ESMTP id PAA24011;
	Thu, 6 Apr 2000 15:35:20 -0700 (PDT)
Received: from cisco.com ([10.19.253.250])
	by fedex.cisco.com (Mirapoint)
	with ESMTP id AAG08403 (AUTH abierman);
	Thu, 6 Apr 2000 15:33:54 -0700 (PDT)
Message-ID: <38ED1176.7B1FB621@cisco.com>
Date: Thu, 06 Apr 2000 15:36:38 -0700
From: Andy Bierman <abierman@cisco.com>
Organization: Cisco Systems, Inc.
X-Mailer: Mozilla 4.72 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-announce@ietf.org, rmonmib@cisco.com
CC: Bert Wijnen <WIJNEN@VNET.IBM.COM>, Randy Bush <randy@psg.com>
Subject: RMONMIB WG interim meeting announcement
Content-Type: text/plain; charset=us-ascii
Sender: owner-rmonmib@cisco.com
Precedence: bulk
X-Mozilla-Status2: 00000000
Content-Transfer-Encoding: 7bit

Hi,

The RMONMIB WG intends to hold an interim meeting to
work on all aspects of the new charter. This includes:
  - Application Performance Monitoring (APM)
  - Transport Performance Metrics (TPM)
  - User-Defined TopN Monitoring MIB (UsrTopN)
  - DIFFSERV Monitoring MIB (DS-MON)

Meeting Dates: 
   Monday, May 15 9am - 6pm
   Tuesday, May 16 9am - 6pm

Location:
   (Meeting Site TBD)
   San Francisco or San Jose, CA

Sponsor:
   A sponsor or co-sponsors are needed to host this meeting.
   A hotel meeting room is preferred, but corporate facilities
   will be good enough. Please contact me at abierman@cisco.com
   if you can help.

--------------BC97A638DEF9C17501ECCE81--



From owner-ietf-outbound  Thu Apr  6 21:00:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA17701
	for ietf-outbound.10@ietf.org; Thu, 6 Apr 2000 21:00:03 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17636
	for <ietf@ietf.org>; Thu, 6 Apr 2000 20:51:48 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200004070042.JAA22858@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id JAA22858; Fri, 7 Apr 2000 09:42:40 +0900
Subject: Re: A thought about patents
To: francis@ecal.com (John Stracke)
Date: Fri, 7 Apr 0 9:42:39 JST
Cc: ietf@ietf.org
In-Reply-To: <38ECB745.35C6E37F@ecal.com>; from "John Stracke" at Apr 7, 100 1:32 am
X-Mailer: ELM [version 2.3 PL11]
X-Loop: ietf@ietf.org

John;

> > We can have servers outside of US and there is no legislation (even
> > under US laws. note that the servers can serve yet another countries)
> > to make the servers illegal.
> 
> Mmm...that sounds like a grey area.  A company using patented tech to do
> business in the US may be subject to US law even if the tech is not resident
> in the US (under the same sort of theory used against Internet gambling).

Legislation logic around patent does not allow US patents applicable
to servers outside of US.

If US tries to change its law, companies in US may be affected by
US laws, which will drive servers and companies away from US.

> Even if it's not true in the general case, a sufficiently expensive lawyer
> might be able to convince the court that, since the Internet makes location
> irrelevant, the location of the infringement is irrelevant.

that US patents are applicable even if both servers, clients and network
inbetween are all located outside of US?

							Masataka Ohta



From owner-ietf-outbound  Thu Apr  6 23:55:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA21357
	for ietf-outbound.10@ietf.org; Thu, 6 Apr 2000 23:54:41 -0400 (EDT)
Received: from web3902.mail.yahoo.com (web3902.mail.yahoo.com [204.71.203.198])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA21264
	for <IETF@ietf.org>; Thu, 6 Apr 2000 23:46:50 -0400 (EDT)
Message-ID: <20000406062647.27165.qmail@web3902.mail.yahoo.com>
Received: from [216.185.31.12] by web3902.mail.yahoo.com; Wed, 05 Apr 2000 23:26:47 PDT
Date: Wed, 5 Apr 2000 23:26:47 -0700 (PDT)
From: Ben Davis <visible_butt_crack@yahoo.com>
Subject: RE: Digital Copyright Law & Industrial Espionage 'Hacking'
To: fir_blog@hotmail.com
Cc: IETF@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1649760492-955002407=:24786"
X-Loop: ietf@ietf.org

--0-1649760492-955002407=:24786
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline



Note: forwarded message attached.


=====
Ben Davis

visible_butt_crack@yahoo.com

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--0-1649760492-955002407=:24786
Content-Type: message/rfc822

Received: from [216.185.31.12] by web3902.mail.yahoo.com; Wed, 05 Apr 2000 23:21:08 PDT
Date: Wed, 5 Apr 2000 23:21:07 -0700 (PDT)
From: Ben Davis <visible_butt_crack@yahoo.com>
Subject: RE: Digital Copyright Law & Industrial Espionage 'Hacking'
To: johnr@thestandards.com
Cc: support@cybersettle.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 19806

Attn: Mr.John Roemer; Reporter for the Pacific
Standard
   and  Ms. Donna Soto; VP for CyberSettle Lawyers:

  I am addressing you anonymously, as I believe that
my
Copyrighted works Registered at Library of Congress &
other works in progress, some deriving from these and 
all original in their entire scope with what I believe
to be the sole result of my efforts over many
years-these I think have been subjected to
compromising and/or intrusive liberties from Party of
Parties Unknown, whom I suspect to be working in
concert one with the other-a small group of teens &
twenties aged 
boy 'gamers' who are most probably being assited by
older 'businessmen' and all I believe reside close
enough to me to share the same telephone junction box.
Although I repeatedly tried to appeal to the Phone Co.
and other authorites about this important matter ( the
IMPORTANCE also was in that we have had what appears
to be "FAUX PHONEMEN"... 'on the line' so to speak,
for SEVERAL YEARS!) We tried US Immigration (INS) as
these people all seem to be from the country we once 
referred to in our schools as 'Red China,' because we
have NO IDEA WHATSOEVER as to the CITIZENSHIP of these
people-we DO KNOW that these few blocks are a KNOWN
AREA where many 'safe-houses' harbor these Illegal
Alien Chinese, in fact we could say that as many as
have come up into our neighborhood from Ocean Beach,
the same amount and MORE of our Native-Born Citizens
of Chinese-American descent seem to just 'DISAPPEAR!'
We have NO IDEA what has become of the American
Chinese
or where that they've gone to? To continue-the adults
in this neighborhood speak NO ENGLISH...their kids,
ALMOST ALL are 15-year old boys, attending LOWELL HIGH
SCHOOL, in the neighborhood, San Francisco's finest,
and with a school newspaper over 100-years old, is
also
granted by the City of San Francisco a 'special
charter' which maintains a strict RACIAL status quo...
98% CHINA MAINLAND BORN (Beijing)...and almost NO
OTHER
RACIAL MAKEUP to this school! As 'exposed' by TV
reporter Emilio Guillermo on his PBS, KQED channel 9,
show, "New California Media"...a show ABOUT
minorities!
And further, these kids' parents mostly got here about
nine years ago from China, so the kids could possibly 
be CHINESE PASSPORTED ILLEGAL ALIENS! (Although
speaking real good "GI JOE" ENGLISH!..ie, Rap
Music,etc
they are nevertheless NOT CITIZENS BY BIRTH....and the
PARENTS ARE MOST PROBABLY "WETBACKS"....? So? Well,
this old world can change till it's blue in the face-
but the Copyright Laws which we created and upon which

for instance the Swiss laws have their basis, and the
'new media' which we hear so much about-they're ALL in
the end based on Library of Congress & US CONSTITUTION

so it is in THIS MANNER in which AMERICA can best help

the rest of the world, and cure the "Digital Divide!"
However, NO ONE WANTS TO WORK FOR FREE...especially
the
truly gifted, as they are ALWAYS 'giving away
freebies'
here and there as they go along their merry way, at
one
point or other they must draw the line at PIRACY &
INVASION of PRIVACY! I'm going to tell it "LIKE IT
IS!"
I am a US CITIZEN. My family has resided continuoulsy
in this neighborhood for over a century. We helped in
both the creation of this City, and pioneering the
West
we have NOTHING to "APOLOGISE FOR' to ANYONE! EVER!
So,
with that in mind, there are few things which honest
people anywhere can tolerate, and one is
ESPIONAGE...whether it be IDENTITY THEFT or stealing
"SECRETS" concerning one's National Security, no one
can stand such a sneak! But, it is all the more
important that we nip the IDEA of this kind of "1984" 
in the bud immediately, as the whole INTERNET itself
must be controlled by those who "OWN" it! YES, the
'Net
is INDEED still "AMERICAN OWNED & OPERATED!" The only
question is which portions are "PRIVATE" and which are
"PUBLIC." Now, to the 'touchy' part of the message,
and
please understand this in the way it was intended for
all to "grok" who are "REASONABLE!" What if ALL OF A
SUDDEN...we got a new government? What if they said;
"You can relax now, and forget all of that
'Politically
Correct' NONSENSE!"  Wouldn't you blow the old welcome
'sigh of relief?'...."Wheew!" HONESTLY? Okay!

Then believe me when I tell you, that that is ABOUT
what may happen sometime soon, BECAUSE the "BUSINESS
of
the INTERNET"...CANNOT tolerate 'Computer Hackers!'
And
there is a storm gathering on the 'cyber-space
horizon'
where-in, the Clinton administration, with it's
ineffectual & antiquated Federal 'Communications'
Commission ( the guy that wrote 'The Godfather' has
the same intitials! By coincidence, that 'says' ALOT!)
and misunderstanding of the situation throughout the 
Far East, has built a house of Yellow Jackets, and
will have to either come up with watermelon for lunch,
or run like hell for deeper water! So, by trying to
create a relationship with cheap labor in China, and
the Silicon Valley, they have pretty much secluded the
sponsors and promoters of the administration from
"direct participation" in the INTERNET ECONOMY!
What I would like to find out as a simple question-
if my neighbors at say, 27 Lakeshore, or 33 Lakeshore,
or in fact maybe several of these as I stated are
"mobbing" me and 'running interference' for each other
while it is obvious that my e-mail is being 'tapped'
and all my confidential materials seem to be under
going some scrutiny by an observation team
that definitely appears to be a 'gang' of some kind, 
and even if not able to conclusively prove ALL of
this-
would a LIEN be possible against their considerable
amount of property in houses & luxury automobiles, and
electronic gadgetry and surveillance equiptment? Next,
could I sue the various government agencies who
refused to check these guys out, such as the San
Francisco Police, especially the Taraval Station,
which seem to have an 'affinity' with BOTH
NON-ENGLISH SPEAKERS (Illegal Aliens from RED CHINA)
and their 'gang-banging kids' (I am not even sure that
there would be a way to prove with new DNA testing if
these are ACTUALLY their offspring, or simply a
'match'
for their 'mission'...a "Potemkin Village" family?) We
have noted that among other goings on, the roofers
they employed jammed up the city sewers for a
month-they were 'dumping'...Environmental Protection
Agency 
simply took the call-NO ACTION! (KIM Rooofers,
Mexicans
working for the Chinese)and that closed down HIGHWAY 1
and the San Francisco Zoo! The dealership which sells
the Chinese their cars, "SHEN"...he was 'whacked' last
month, kjust when everyone in town was trying to
figure out where all these "HIT AND RUN" accidents
were
coming from? Seems as if the Chinese kids get a NEW
LEXUS, MERCEDES, BMW, etc everytime they DENT A FENDER
so then ALSO, they NEVER HAVE PLATES ON THEIR
VEHICLES!
Crap, there must be at least FIFTY cars, parked on the
street at LOWELL HIGH SCHOOL very single day, which
are
improperly marked /identified, by plates, permits,
etc)
Even my Internet Service Provider SLIPNET was recently
purchased by BEST INTERNET who in turn who acquired by
VERIO, and ALL of them refused to help me figure out
HOW the 'phone bill' could be so "pumped up!" Our
phones were 'crammed & slammed' and my DOMAIN NAMES
were all 'screwed up'...ALTHOUGH PAID FOR
ELECTRONICALLY BY PHONE...and the "Tech-Reps" and
"Billing Depts." would NOT ONLY REFUSE TO ASSIST ME IN
MY INQIRIES ( I MEAN... I WANTED TO FIND OUT WHAT WAS
THE MATTER...?) But, instead tried in various
RUDE, DEMEANING, and INSULTING ways, to INSINUATE that
I 'had'nt PAID, or was MISTAKEN, or "STUPID"...AND
MORE! Now, imagine my chagrin, throiugh all this NOT
KNOWING FOR "SURE" if I EVEN got the Phone Co. or
VERIO
or whomever, as there would be at that time, BOTH a 
"Guy" working on the phone box outside, and a funny 
"DOUBLE-CLICK" on my 'mouse,'so I had some time of
it!)
Okay, let's see we have the possible illegal alien
kids at 27 lakeshore and 33 Lakeshore, in San
Francisco
and possibly several other neighbors who are their
friends, and on the same phonelines. Then we have the
people at VERIO, and so forth. If for the 'civilians'
we went with the LIEN approach, what fees would you 
charge for that service? Your list at CyberSettle says
it can be done for $50? And for the Corporate? I would
like to find a legal-beagle outfit, which could help
me with that in the area of Letters of Demand. The
truly odd and 'goofy' circumstance with one of my
woirks is that the VERY SAME PHONE COMPANY WHICH WAS
"messing" with the 'equiptment' and givin' me BIG
PHONE BILLS for the 'run-a-round' to take my mind off 
of the fact hat I was trying to sell something to the
Ball Park which just happened to allow the park to be
named after the PHONE CO? Gee, that sounds liek maybe
a few of these 'folks' is all workin' together, and
you are still 'alive' just so's they can continue to
"RIP YOU OFF" and ridicule you? Well, that sounds
funny, butr I spent a lot of time trying to get
PACIFIC BELL and CHINA BASIN BALL CLUB (PAC BELL PARK)
to give a quick look at my proposal. Yep! Lot of darn 
'coincidences!' PHONE, CHINA, (and a BASEBALL DESIGN!)
and not forgetting too, that the kids seem to follow
my family in their cars, and seem ed to do so with
some
kind of precision, and accuracy, which they'd only
have if done through some kind of electronic aid...
say as in WIRE-TAPPING? WELL, DAMNDEST DARN
COINCIDENCE... SENATOR PAUL MCCLOSKEY SUED PAC BELL
FOR
TAPPING HIS PHONE! HE LIVES IN SAN MATEO...which is
just south ON OUR CABLE, which incidentally was just
'replaced' for about the 3rd time! When the BIG
NEWSPAPER STORY BROKE ABOUT THE SF POLICE DEPT LETTIN'
"CIVILIAN OUTFITS" tap OUR PHONES...? "Yipes!" So all
the stuff has kind stopped, for a whgile a phone guy
would do somethimng all day, and five minutes after he
left a truck would pull up, JACKHAMMER the thing, and
put in a BRAND NEW BOX! I repeorted ALL THESE GOINGS
ON AND HAVE CORROBRATIVE EYEWITNESSES BY THE DOZEN!
For
both the strange 'bivuoac' of RED ARMY OFFICERS? and
their families, in the SUNSET AND RICHMOMND DISTRCTS
OF SAN FRANCISCO, but especially for the higher
ECHELON
to be 'stationed' in the LAKESHORE PLAZA area of the
SUNSET DISTRICT, and soem strange "PUBLIC WORKS" out
here, such as the 'new sewer' which goes out to SEA
like "THE CHUNNEL" (English Channle Tunnel-AND IT WAS
DUG BY THE SAME EXACT EQUIPTMENT!)And this tunnel is
near the SHIPS, and has TRUCK TRAFFIC AT NIGHT, and
TRAIN SOUNDING NOISES, but 'SEWERS' don't have
"GARBAGE
DELIVERIES"...do they? These houses out here all are
loaded with TELEVISON CAMERAS spying on us AMERICANS-
BURGLUR ALARMS, as though WE WERE THE 'PERPS'...and
the sniggering that goes on, either they had possibly
jsut listend to you on the fun, 'tailed you by car, 
or 'stalked' your SITUATION? We think that some of
their wrecked cars of the results ogf their botched
attempts at HOME INVASION, COMPUTER CHIP ROBBERY, and
CAR JACKINGS,...HIT AND RUN DEATHS;( "Body snatching
for organ 'donation'...? ..."Yech!")Who knows> But
there have been reports of all these, and SEX SLAVERY
CHILD PORN, GAMBLING, ABORTIONS, FETUS SELLING FOR
FOOD?...('PINK MICE?"... "YECH!") So, here is the
deal-what IF the CLINTON ADMINISTRATION; an
'EXPRESSION' left-over from the "Greatest Generation"
a 50-year REGIME, in which NO NEW BLOOD ever got into
the POLITICAL RING, and which now, is being
CASATIGATED as
an INSULT to the AMERICAN PEOPLE, and the GREAT
NATION,
because, as with McCarthy, these were a highly 'sexed'
bunch of ADULT WHITE MALE HOMOSEXUALS ( Yes, I know,
we were all told in 'school' that 'you ain't supposed'
to talk 'bout anything important when you are trying
to
earn-a-living, because then they won't like you', etc.
WELL, that's what got us into this mess in the first
place, and just as with the easy to figure out
"VIETNAM"...that was there to 'bump-off' any AMBITIOUS
FOOLHARDY PATRIOTIC IDIOTS in the next generation who
asked to many damn questions such as "How come you
don't take me to work Dad?" Because the answer would
have been...."Heck, Son, you can't come down to the
office because we are doin' somethin' important at
this time..." Which as you know, Mom was blown away
when she found out that the "red-head" she was
suspicious of was "PAUL DRAKE!""Heh heh heh heh..!"
To think that schools teach that Cleopatra was Black,
and EVERYBODY...literally, who was MALE, and nifty,
and who is NO LONGER ALIVE IN ORDER TO DEFEND HIMSELF'
was 'gay?' She it! ( oh, forgot to mention, NEVER
MESSED with the NEIGHBORS, the one boy has both a
BOY-FRIEND and a LOOK ALIKE who does a "changing
places" act. I thought maybe "bodyguard?" For TRIAD?
Still cannot figure how these Chinese earn MILLION
BUCKS FOR TWO HOUSES FORTY GRAND EACH FOR SIX CARS,
etc? "Hey! Pretty good for someone who doesn't speak
English!"
But, what if an ALL GAY SOCIETY TOOK OVER THE WORLD
VAI THE US MILITARY ESTABLISHMENT? WHAT IF HOLLYWOOD
MADE IT WORK? WHAT IF THE JEWS ARE NOT A SEPARATE RACE
FROM OTHER WHITE PEOPLE? WHAT IF LESBIANS ARE NOT
HOMOSEXUALS? WHAT IF JUDAISM RECOGNISED LESBIANISM AS
A
VERY NORMAL FUNCTION OF WOMEN? YET STILL OUTLAWED
ADULT WHITE MALE HOMOSEXUALITY? WHAT IF JUDAISM
REFUSED
TO RECOGNISE THE KHAZAR RACE AS JEWISH? WHAT IF
EVERYONE LOVED EVERYONE EXCEPT THAT BLACK MALES WERE
NOT ALLOWED TO MARRY CAUCASIAN JEWISH WOMEN? WHAT IF
GENERALLY SPEAKING THE WORLD AT LARGE TOLERATED ALL
KINDS OF DIVERSITY...EXCEPTING ABOUT THREE? (3!) COULD
YOU "LIVE" IF "GOD" ASKED YOU TO GIVE UP JUST "THREE"
RELATIONSHIPS? WHY THE HELL NOT? HOW WOULD THAT BE
RACIST SEXIST OR WHAT EVER? WHAT IF YOU JUST FOUND OUT
THAT THAT ACTUALLY IS THE MAIN TENENT OF THE MOST OF
ALL THE PEOPLE ON THE PLANET? "YES!" Believe it or
not!
In Judaism, Lesbians are "okay, but NO QUEERS
ALLOWED!"
In Christianity, the belief is that the Khazar ( A
very minor race, which is rather reddish in color,
resembling some North American Indians,as those in New
York, they many times are noted as appearing somewhat
like the Gypsies or Mexicans, but unlike the former
have NO CAUCASIAN DNA, origianally, so can NOT
possibly have been Jewish as they weren' EUROPEANS,
and EVERYONE in THE ANCIENT MEDITERANEAN was
EUROPEAN!)
is NOT ONLY NOT REALLY "JEWISH" ( or only to the
degree
that they are of European descended DNA) but that they
may be working with the 'other-Devil' whom the REAL
JEWS are 'fightin' (religiously!)...the Homosexual!
Who is representative of the 'spirit' of "FALSE
RELIGION!" And finally in all this is the Muslim view
that ISLAM is a direct revealment of the Will of God-
and ALL are welcome, but a few things are asked of
Man-
that he pray, and give to the poor, and soforth, very
little is demanded, except truth-searching, and in the
Traditions of the Prophet, where a man may marry four
wives, and all may intermarry racially, what one
SINGLE
combination, is Man asked to abstain from, as were the
fruit in the Garden of Eden? Yes, NO darker MAN, when
a NEGRO may marry a LIGHTER woman! And the reasoning
here is that God KNOWS all things, in him is LIGHT!
How easy and true and good all this seems! Yes, it ALL
makes sense for the People of the Book! Why wouldn't
America want to 
follow this kind of thinking? ( Just as ONE Example!)
Well, it is quite obvious that MANY of us are getting
to look MORE and MORE like our "GOVERNMENT!" And what
a poor picture that would be! For instance, for FIFTY
years we have had the 'wool' pulled over our eyes-did
Roosevelt let the Japanese bomb Pearl Harbor? Well,
NOW we are being told he did! Is the 'British" Royal
Family a 'NAZI-German' outfit? Apparently so, the U.K.
has had 'privatising' the Windsors on the ballots many
times, now-and why not, after all how would you feel
if you found out just today that Mr. Clinton owned ALL
of Canada, that would kind of wake you up, wouldn't
it?
How about if Patty Hearst owned ALL of Australia? Gee!
Well, I have news for you. 1. Queen Elizabeth OWNS all
of CANADA and AUSTRALIA! 2. She is NOT related to
QUEEN ELIZABETH of SHAKESPEARE's day, and of whom it
is said he 'wrote' the King James Bible (translated)
and the BOOK "ROYALTIES"...go to the "WRONG QUEEN"...
YES! This one is a "GERMAN!" You have to be "IRISH" to

run "ENGLAND!" (Dear Reader, please look all this up I
assure you ANY ONE IN ENGLAND can VERIFY these facts
as COMMON KNOWLEDGE!)3. BILL CLINTON, and PATTY HEARST
are COUSINS to QUEEN ELIZABETH (WINDSOR!)"She it!" Now
last question..."Did you know that the DECLARATION of
INDEPENDENCE was printed by a WOMAN? KATHERINE
GODDARD!
1776! And do you know what it says in that document?
..."...The 'Prince' (WINDSORS a German family which
'took over' England in the 1700's, they're the
"English" the Scottish Highlanders were fightin'! So
that tells you that the Irish who were supporting
"Bonnie Prince Charlie" ...NO relation whatsoever to
the current queer'...were DOUBLE PATRIOTS
They weren't fighting 'other 'Brits' ...ie other CELTS
but GERMANS...not from either BRITISH ISLE! Get it?)
So as an AMERICAN you may be interested in knowing
that the "SPANISH" (Another bunch of
CELTS!...BASQUES!)
Started SAN FRANCISCO in ...1776! That's right; as an 
'ace-up-the-sleeve' in case our America didn't make
it!
And so everything sort of makes sense, once you cast
off all that 'crap you learned in High School' as
Simon and Garfunkel so aptly explained, both America
and belief in the God of the Jews, Christians and
Muslims seems to make sense, that is why we are free,
why we have room for everyone who seeks the right
path.
But we cannot tolerate SUPERSTITION, and EVIL! And as
you may have guessed most of the stuff on TV is pure
bunk! But to raise the populace on this you wonder
whether the idea of RIGHT to PRIVACY and FREEDOM from
TYRANNY is important anymore-it is! There can be no
Internet development, w/o Intellectual Property
Rights.
And the Internet 'means' commerce. And also education.
Because we have had a very 'dirty' government and it
has conspired from just before WWII right up to TODAY
where the people in Washington are 'hob-nobbing' with 
Bill Gates, AFTER he was just reprimanded for
MONOPOLY!
I would like anyone who agrees with this
conceptualization of how it is with the 'Net, and how
it might be soon after the very necessary world
changes come into play and we are once again trying to
invent and innovate-will we be able to do so with out
having foreign agent saboteurs & espionage specialists
getting into our computers through the phonelines, and

generally exhibting behaviors which can only be the
result of planned surveillance and long-studied spying
on Americans as both a 'hooby' and 'blood-sport' as
though this were the heighth of the Cold War, & we 're
smack dab in the middel between North and South Korea!
Well, if you get what I'm saying, and you YOURSELF
are not a FAKE or PHONY like our President who had the
"Monica" thing out there just to throw everyone off of
the fact that he wasn't going to be "IMPEACHED" but 
rather arrested-YES! AS WAS BROUGHT UP ON FRIDAY...as
a TRAITOR! ( A CRIME PUNISHABLE BY DEATH UNDER THE
U.S. CONSTITUTION- THE ONLY ONE MENTION OF CAPITAL
PUNISHMENT IN OUR FOUNDERS' DOCUMENTS!)People didin't
think O.J. SIMPSON was a queer either-now we know
different! Or Jesse Jackson! Or George Lucas. Jerry
Brown. There are a BIZZILION of them! "The devil is
making them do it?" Who knows, but it AIN'T "KOSHER!"
Please let me know if you have any ideas as to which
strategy might give best results in this matter. Thank
you very much for you time and I hope that this has
reached 'Good Folk.' I pray for everyone anyway.
Peace.


=====
Ben Davis

visible_butt_crack@yahoo.com

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

--0-1649760492-955002407=:24786--



From owner-ietf-outbound  Fri Apr  7 00:40:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA21845
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 00:40:02 -0400 (EDT)
Received: from npax.cavebear.com (npax.cavebear.com [192.203.17.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21695;
	Fri, 7 Apr 2000 00:30:53 -0400 (EDT)
Received: from hari-seldon.cavebear.com (npax.cavebear.com [192.203.17.71])
	by npax.cavebear.com (8.9.3/8.9.3) with ESMTP id VAA17823;
	Thu, 6 Apr 2000 21:29:40 -0700
Date: Thu, 6 Apr 2000 21:29:40 -0700 (Pacific Daylight Time)
From: Karl Auerbach <karl@cavebear.com>
To: Keith Moore <moore@cs.utk.edu>
cc: rfc-ed@rfc-editor.org, iesg@ietf.org, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
In-Reply-To: <200004061641.MAA15198@astro.cs.utk.edu>
Message-ID: <Pine.WNT.4.21.0004062120070.964-100000@hari-seldon.cavebear.com>
X-X-Sender: karl@[127.0.0.1]
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


> I am writing to request that the RFC Editor not publish 
> draft-cerpa-necp-02.txt as an RFC in its current form,
> for the following reasons:
 
> 2. A primary purpose of the NECP protocol appears to be to 
> facilitate the operation of so-called interception proxies.  Such 
> proxies violate the Internet Protocol in several ways: 
 
> 3. Aside from the technical implications of intercepting traffic,
> redirecting it to unintended destinations, or forging traffic from
> someone else's IP address - there are also legal, social, moral and
> commercial implications of doing so.

You will need to be far more specific here.  I see absolutely nothing that
is not legal, is not social, or is not moral.  I do see commercial
implications, but whether those are is "good" or "bad" is not a technical
judgement.
 
> In my opinion IETF should not be lending support to such dubious
> practices by publishing an RFC which implicitly endorses them, even
> though the authors are employed by major research institutions and
> hardware vendors.

I take the contrary position.  The IETF ought to be encouraging the
documentation of *all* practices on the net.  It is far better that they
are documented where people can find useful information when they see this
kind of packet activity rather than have them known only to a few
cognescenti.

May I suggest that one treat this in its classical sense - as a Request
for Comments and that those who have technical objections or technical
enhancements publish those comments in an additional document rather than
try to suppress the original one.

Having a document trail that shows what paths and ideas have been found
wanting is nearly as important has having a trail that show what paths
have been found useful.

		--karl--



From owner-ietf-outbound  Fri Apr  7 04:10:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA04522
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 04:10:03 -0400 (EDT)
Received: from monitor.internaut.com (mg-206253202-59.ricochet.net [206.253.202.59])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04465;
	Fri, 7 Apr 2000 04:03:18 -0400 (EDT)
Received: from vaiobean ([204.57.137.66])
	by monitor.internaut.com (8.9.2/8.8.8) with SMTP id AAA31987;
	Fri, 7 Apr 2000 00:49:56 -0700 (PDT)
Reply-To: <aboba@internaut.com>
From: "Bernard Aboba" <aboba@internaut.com>
To: "'Keith Moore'" <moore@cs.utk.edu>, <rfc-ed@rfc-editor.org>
Cc: <iesg@ietf.org>, <ietf@ietf.org>
Subject: RE: recommendation against publication of draft-cerpa-necp-02.txt
Date: Fri, 7 Apr 2000 01:05:14 -0700
Message-ID: <002501bfa068$01d432b0$428939cc@ntdev.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6700
In-Reply-To: <200004061641.MAA15198@astro.cs.utk.edu>
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

The use of "load balancing" technologies is growing rapidly
because these devices provide useful functionality. These
devices utilize many different techniques, only some of which
can be characterized as "interception proxies" or "reverse
network address translation." For example, using MAC address
translation (MAT) it is possible to provide load balancing
and failover without breaking IPSEC or violating other
basic principles.

Thus it strikes me that this is a legitimate topic for
inquiry and that cannot be so easily dismissed as "morally"
unacceptable. As we have done with the NAT WG, it is
often useful to accurately document the drawbacks of a
common practice as well as to encourage exploration of
alternatives.

If seen within this context, it is conceivable that we
might well want to publish draft-cerpa-necp-0x.txt at
some future date as a documentation of existing practice
with the correct caveats and references. While there are
clearly elements of the document which are misleading,
overall it does not seem unredeemable to me.

My recommendation would be to explore formation of a WG to
deal with the issues in this area, and to remand
draft-cerpa-necp-02.txt to that WG if and when it is formed.

-----Original Message-----
From: Keith Moore [mailto:moore@cs.utk.edu]
Sent: Thursday, April 06, 2000 9:42 AM
To: rfc-ed@rfc-editor.org
Cc: moore@cs.utk.edu; iesg@ietf.org; ietf@ietf.org
Subject: recommendation against publication of draft-cerpa-necp-02.txt


I am writing to request that the RFC Editor not publish
draft-cerpa-necp-02.txt as an RFC in its current form,
for the following reasons:

1. The document repeatedly, and misleadingly, refers to NECP as a
standard.  I do not believe this is appropriate for a document
which is not on the IETF standards track.  It also refers to
some features as "mandatory" even though it's not clear what
it means for a non-standard to have mandatory features.


2. A primary purpose of the NECP protocol appears to be to
facilitate the operation of so-called interception proxies.  Such
proxies violate the Internet Protocol in several ways:

(1) they redirect traffic to a destination other than the one
specified in the IP header,

(2) they impersonate other IP hosts by using those hosts' IP addresses
as source addresses in traffic they generate,

(3) for some interception proxies, traffic which is passed on to the
destination host, is modified in transit, and any packet-level
checksums are regenerated.

IP allows for the network to delay, drop, or duplicate IP packets,
as part of a best effort to route them to their intended destination.
But it does not allow the above practices.

This document implicitly treats such behavior as legitimate even
though it violates the primary standard on which all Internet
interoperability depends.


3. Aside from the technical implications of intercepting traffic,
redirecting it to unintended destinations, or forging traffic from
someone else's IP address - there are also legal, social, moral
and commercial implications of doing so.

In my opinion IETF should not be lending support to such dubious
practices by publishing an RFC which implicitly endorses them,
even though the authors are employed by major research institutions
and hardware vendors.


4. Furthermore, while any of the above practice might be deemed "morally"
acceptable in limited circumstances (such as when the interception proxy
is being operated by the same party as the one which operates the host being
impersonated) in general these are very dangerous.  There have been numerous
cases where network elements employing practices similar to the above have
been demonstrated to harm interoperability.  (e.g. there is a widely-used
SMTP firewall product which breaks SMTP extension negotiation, and a
traffic shaping product was recently found to corrupt data in TCP streams
generated by certain kinds of hosts)

This document contains language touting the benefits of NECP but very
little language describing the danger of using the above techniques which
NECP was designed to support.   Where the document does mention the
problems, it is misleading or incomplete.  For example, the Introduction
says

   However, it [an interception proxy] can cause problems: users
   have no way to go directly to origin servers, as may be required in
   some cases (e.g., servers that authenticate using a client's source
   IP address).  The proxy has a high-level understanding of the
   application protocol; it can detect these cases and decide which
   flows should be cut through to origin servers.

The latter sentence is a false assertion - even though the proxy has
a high level understanding of the protocol, the proxy is not generally
able to determine when cut-through is required.   For example, the
service being impersonated by the interception proxy may have uses for
the client's source address which are outside of the protocol being
intercepted and for which the proxy cannot be knowledgable.
Such uses may be both active (in that they involve attempts to establish
other traffic between the origin server and the client, or between the
client and other hosts on the network), or passive (in which the origin
server uses the client's IP address without attempting to communicate
with it), or even deferred (in which an attempt is made to communicate
with the client's IP address at a later time).  In addition, the *user*
may have a requirement for his client to talk directly to an origin server,
or the content provider may have a requirement for the origin server to
talk directly to a client, simply because they expect communications
integrity.  By its very nature an interception proxy ignores the
requirements of the user and/or the content provider.

The document refers to two other documents which it says further
describe the dangers of interception proxies: "Internet Web Replication
and Caching Taxonomy" [reference 3], and "Known HTTP Proxy/Caching
Problems".
Both of these appear to be works in progress, and the latter document does
not even have a reference.  Until such documents are published, or
at least until they are deemed ready for publication by their creators,
it is impossible to evaluate whether they contain sufficient and
accurate information to inform readers of the NECP document about
the dangers of interception proxies.


5. While in one sense NECP is an attempt to alleviate some of the harm done
by interception proxies, this document is clearly intended to encourage
and promote the use of such proxies by providing a uniform cross-vendor
interface between such proxies and network elements.

Given that NECP is intended to support violations of the Internet Protocol,
and that such violations are known to harm interoperability, such promotion
is a misuse of the RFC document series.



In summary, my recommendation is that the document not be published until:

- the promotional material is removed, leaving only technical justification
  and specification

- the document is changed to point out that interception proxies are
  nonstandard, that they violate the Internet Protocol, and that they
  are known to degrade interoperability

- a disclaimer is added, which points out that interception proxies
  are engaged in interception, misrepresentation, and forgery of network
  traffic, that such practices are not endorsed by IETF, and that they
  may be illegal in some jurisdictions.

- the documents describing the dangers of interception proxies
  which are referenced by the NECP document are ready for
  publication, and are deemed reasonably complete and accurate.


But I would also recommend that the document not be published at all,
as I believe that publication of this document will do far more to
degrade the interoperability of the Internet than it can do to help it.

There may indeed be value in publishing the document as a contribution
to the historic record of Internet development, as it certainly reflects
some current trends.  However this goal could be accomplished by
delaying publication of the NECP document by several years, or at least,
until the publication of technically sound, standardized, solutions for
the problems that interception proxies attempt to address.

best regards,

Keith Moore

-
This message was passed through ietf+censored@alvestrand.no, which
is a sublist of ietf@ietf.org. Not all messages are passed.
Decisions on what to pass are made solely by Harald Alvestrand.



From owner-ietf-outbound  Fri Apr  7 05:00:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA04919
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 05:00:03 -0400 (EDT)
Received: from cs.utk.edu (CS.UTK.EDU [128.169.94.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04806;
	Fri, 7 Apr 2000 04:50:44 -0400 (EDT)
Received:  
        by cs.utk.edu (cf v2.9s-UTK)
	id EAA24352; Fri, 7 Apr 2000 04:50:41 -0400 (EDT)
Date: Fri, 7 Apr 2000 04:50:41 -0400 (EDT)
From: Keith Moore <moore@cs.utk.edu>
Message-Id: <200004070850.EAA24352@cs.utk.edu>
To: karl@cavebear.com
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Cc: iesg@ietf.org, ietf@ietf.org, moore@cs.utk.edu, rfc-ed@rfc-editor.org
X-Loop: ietf@ietf.org

> > I am writing to request that the RFC Editor not publish 
> > draft-cerpa-necp-02.txt as an RFC in its current form,
> > for the following reasons:
>  
> > 2. A primary purpose of the NECP protocol appears to be to 
> > facilitate the operation of so-called interception proxies.  Such 
> > proxies violate the Internet Protocol in several ways: 
>  
> > 3. Aside from the technical implications of intercepting traffic,
> > redirecting it to unintended destinations, or forging traffic from
> > someone else's IP address - there are also legal, social, moral and
> > commercial implications of doing so.
> 
> You will need to be far more specific here.  I see absolutely nothing that
> is not legal, is not social, or is not moral.  

Okay, I'll offer a few specific examples, by no means the only ones:

1. an Internet service provider which deliberately intercepts traffic 
(say, an IP packet) which was intended for one address or service, 
and delivers it to another address or service (say that of an interception 
proxy) may be misrepresenting the service it provides (it's not really
providing IP datagram delivery service because IP doesn't work this way).

2. an internet service provider which deliberately forges IP datagrams
using the source address of a content provider, to make it appear
that the traffic was originated by that content provider
(interception proxies do this), may be misrepresenting that content
provider by implicitly claiming that the service conveyed to the user
by the ISP is the one provided by the content provider.

3. an internet service provider which deliberately alters IP traffic 
in transit, and deliberately makes it appear that the traffic was not 
altered (by recomputing the checksum) may be misrepresenting the 
service it provides (because IP doesn't work that way) and it may
also be violating the traffic orignator's right to make derivative 
works of its copyrighted material.  (in particular an interception 
proxy that modified the content in transit - say to convert one
data format to another - might be held to violate that right because
content conversions almost always degrade the content and thereby
degrade the expression)

now whether any of these is actually illegal would be up to a court
to decide, and different courts in different jurisdictions might rule 
differently (especially depending on the particulars of a test case)
but each of these is similar to behavior that in other communications
domains would be illegal.  and regardless of whether the grounds is
technical, legal, or moral, none of these behaviors seems like 
something that IETF should support.

> I do see commercial
> implications, but whether those are is "good" or "bad" is not a technical
> judgement.

I agree that we are safest when we can rely purely on technical arguments,
and I believe that all of the above practices are in general technically 
unsound.  Still, I don't think there is a definite boundary between 
technical judgement and moral judgement.    Technical judgements are
often based on moral sensibilities.

> > In my opinion IETF should not be lending support to such dubious
> > practices by publishing an RFC which implicitly endorses them, even
> > though the authors are employed by major research institutions and
> > hardware vendors.
> 
> I take the contrary position.  The IETF ought to be encouraging the
> documentation of *all* practices on the net.  It is far better that they
> are documented where people can find useful information when they see this
> kind of packet activity rather than have them known only to a few
> cognescenti.

Actually I share the belief that it is a good thing to document any 
widespread practice, or any idea which is believed to be useful.   
However it's also clear that publication of all such pratices in RFCs
is beyond IETF's meager resources, and would dilute the value of 
the RFC document collection. And the reality is that a protocol
documented in an RFC is often treated as if it were a standard, or 
at least, as if the practice were endorsed by IETF.    When a poor
protocol is apparently endorsed in this way it does harm to IETF's 
reputation and to its work of promoting interoperability.

> May I suggest that one treat this in its classical sense - as a Request
> for Comments and that those who have technical objections or technical
> enhancements publish those comments in an additional document rather than
> try to suppress the original one.

RFCs have not been treated in this sense for many years.  And while
such treatment may have made sense in the early days of the ARPAnet
with a community of a few hundred users, it does not make sense in 
an Internet with tens of millions of users.

The reality is that today, many documents submitted for RFCs are rejected.
I'm simply arguing that this document should be added to that set.
or at least, that it needs substantial revision before it is found 
acceptable.

> Having a document trail that shows what paths and ideas have been found
> wanting is nearly as important has having a trail that show what paths
> have been found useful.

agreed, but that doesn't mean that it's IETF's or the RFC Editor's job 
to organize and maintain the definitive collection of such documents.

Keith



From owner-ietf-outbound  Fri Apr  7 10:40:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA09251
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 10:40:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09039;
	Fri, 7 Apr 2000 10:33:36 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id KAA00707;
        Fri, 7 Apr 2000 10:31:55 -0400 (EDT)
Message-Id: <200004071431.KAA00707@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: aboba@internaut.com
cc: "'Keith Moore'" <moore@cs.utk.edu>, rfc-ed@rfc-editor.org, iesg@ietf.org,
        ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Fri, 07 Apr 2000 01:05:14 PDT."
             <002501bfa068$01d432b0$428939cc@ntdev.microsoft.com> 
X-SUBJECT-MSG-FROM: "Bernard Aboba" <aboba@internaut.com> 
Date: Fri, 07 Apr 2000 10:31:55 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> The use of "load balancing" technologies is growing rapidly
> because these devices provide useful functionality. These
> devices utilize many different techniques, only some of which
> can be characterized as "interception proxies" or "reverse
> network address translation." For example, using MAC address
> translation (MAT) it is possible to provide load balancing
> and failover without breaking IPSEC or violating other
> basic principles.
> 
> Thus it strikes me that this is a legitimate topic for
> inquiry and that cannot be so easily dismissed as "morally"
> unacceptable. 

I agree that this is a legitimate topic for inquiry.  the thing
I want to avoid is having IETF encourage deployment of
interception proxies by publishing this or similar RFCs that
(implicitly or explicitly) support the concept - at least,
until we have community consensus on which such practices are
harmful to the Internet and when they are mostly harmless.

load balancing technologies, at least as I've seen them used, 
don't bother me.  if you front-end your own servers with a 
load-balancing box, you are presumably in a position to determine
whether the box actually suits your needs for the service you
are providing from those servers.  if it doesn't suit your needs,
switch to something else.  and the fact that they "forge" source
IP addresses doesn't bother me as long as the only addresses
that they are forging belong to the same people as those who
are operating the load-balancing box.  to the extent that such
boxes are doing harm they're probably only hurting those who
operate them.  

again, this doesn't mean that IETF should standardize such
practices (since they're a local matter).  but I don't see this
as a moral issue.  my real concern is about boxes are intended
to affect third-party traffic.

> As we have done with the NAT WG, it is
> often useful to accurately document the drawbacks of a
> common practice as well as to encourage exploration of
> alternatives.

From my point of view there were significant forces within the 
NAT group attempting to keep the extent of these drawbacks from 
being accurately documented and to mislead the readers of those
documents into thinking that NATs worked better than they do -
for instance, the repeated assertions that NATs are "transparent".
So I'm not sure that this is a good model on which to base future work.

> If seen within this context, it is conceivable that we
> might well want to publish draft-cerpa-necp-0x.txt at
> some future date as a documentation of existing practice
> with the correct caveats and references. While there are
> clearly elements of the document which are misleading,
> overall it does not seem unredeemable to me.

I also suspect that the document is redeemable, but that it 
needs significant modification.  As currently written it
does not seem intended to document current practice, but rather,
to encourage deployment of certain kinds of products, some
of which are arguably harmful.

> My recommendation would be to explore formation of a WG to
> deal with the issues in this area, and to remand
> draft-cerpa-necp-02.txt to that WG if and when it is formed.

wrec already exists, and the intention was that it would eventually
define technically sounds mechanisms for web replication and caching.

while the technology in necp may have other uses besides web replication,
I really wonder if IETF should put its energies into defining
how to violate the Internet Protocol - especially when it seems to
me that legitmiate violations of IP (i.e. when it only affects your
own services) are likely to be "local matters" and therefore not
really candidates for internet standardization.  

And as a practical matter I think it would be really difficult to 
attract a balanced constituency to the working group.

But I agree that a dialog of some form is needed, which is why I
cc'ed the IETF list on my note to the RFC Editor in the first place.

Keith



From owner-ietf-outbound  Fri Apr  7 11:10:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA10046
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 11:10:03 -0400 (EDT)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09836;
	Fri, 7 Apr 2000 11:05:41 -0400 (EDT)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id LAA21330;
	Fri, 7 Apr 2000 11:05:24 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v04220806b513a760398e@[171.78.30.107]>
In-Reply-To: <200004070850.EAA24352@cs.utk.edu>
References: <200004070850.EAA24352@cs.utk.edu>
Date: Fri, 7 Apr 2000 11:00:02 -0400
To: Keith Moore <moore@cs.utk.edu>
From: Stephen Kent <kent@bbn.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Cc: karl@cavebear.com, iesg@ietf.org, ietf@ietf.org, moore@cs.utk.edu,
        rfc-ed@rfc-editor.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Keith,

Without comments on other aspects of the technology in question, I 
would like to make some observations about the security aspects of 
the processing you cite as violating IP.

By now we all should know that it is a bad idea to rely on an 
unauthenticated IP address as a basis for determining the source of a 
packet. Similarly. the IP header checksum offers no security.  We 
have a variety of IETF standard protocols (e.g., IPsec and TLS) that 
provide suitable assurance for data origin authentication and 
integrity for application data sent via IP.  Thus, if anyone is 
really concerned about know with whom they are communicating, and 
whether a packet was modified in transit, they should be using these 
standards security technologies.  Many web sites for which these 
security concerns are significant already make use of SSL/TLS anyway.

Steve



From owner-ietf-outbound  Fri Apr  7 12:00:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA10990
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 12:00:02 -0400 (EDT)
Received: from tor-smtp2.netcom.ca (tor-smtp2.netcom.ca [207.181.101.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10880;
	Fri, 7 Apr 2000 11:54:19 -0400 (EDT)
Received: from thinkingcat.com (mon-pq15-18.netcom.ca [216.123.104.146])
	by tor-smtp2.netcom.ca (8.8.7-s-4/8.8.7) with ESMTP id LAA20623;
	Fri, 7 Apr 2000 11:53:33 -0400 (EDT)
Message-ID: <38EE04CA.C7E0BF39@thinkingcat.com>
Date: Fri, 07 Apr 2000 11:54:50 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
Organization: Thinking Cat Enterprises
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Stephen Kent <kent@bbn.com>
CC: Keith Moore <moore@cs.utk.edu>, iesg@ietf.org, ietf@ietf.org,
        rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <200004070850.EAA24352@cs.utk.edu> <v04220806b513a760398e@[171.78.30.107]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Howdy,

Stephen Kent wrote:
> Thus, if anyone is
> really concerned about know with whom they are communicating, and
> whether a packet was modified in transit, they should be using these
> standards security technologies.  Many web sites for which these
> security concerns are significant already make use of SSL/TLS anyway.

I think the point was that this will impact many more casual 
interactions, where one wouldn't necessarily think to have to employ
authentication technologies.  

There are times when I and my ISP, or the ISPs it peers with, have 
different opinions about what is sufficiently recent/authentic
(of a copy of a resource, or even of a final destination address).
If unrelated entities in the chain each get to "assert an opinion"
about what's "good enough", for their own purposes, it is not at
all clear that I get the end-result that I deserve, or am even aware
of the fact that things have been changed midstream.


Leslie.

-- 

-------------------------------------------------------------------
"My body obeys Aristotelian laws of physics."
   -- ThinkingCat

Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------



From owner-ietf-outbound  Fri Apr  7 12:50:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA12230
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 12:50:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11994;
	Fri, 7 Apr 2000 12:41:21 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA01226;
        Fri, 7 Apr 2000 12:39:35 -0400 (EDT)
Message-Id: <200004071639.MAA01226@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Stephen Kent <kent@bbn.com>
cc: Keith Moore <moore@cs.utk.edu>, karl@cavebear.com, iesg@ietf.org,
        ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Fri, 07 Apr 2000 11:00:02 EDT."
             <v04220806b513a760398e@[171.78.30.107]> 
Date: Fri, 07 Apr 2000 12:39:35 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> By now we all should know that it is a bad idea to rely on an 
> unauthenticated IP address as a basis for determining the source of a 
> packet. Similarly. the IP header checksum offers no security.  We 
> have a variety of IETF standard protocols (e.g., IPsec and TLS) that 
> provide suitable assurance for data origin authentication and 
> integrity for application data sent via IP.  Thus, if anyone is 
> really concerned about know with whom they are communicating, and 
> whether a packet was modified in transit, they should be using these 
> standards security technologies.  Many web sites for which these 
> security concerns are significant already make use of SSL/TLS anyway.

While I naturally agree that one should not use unauthenticated
IP addresses to determine the source of a packet, I think it's a 
big stretch to say that the existence of IPsec and TLS means that 
it's okay for third parties to forge source addresses.

and for different reasons, both IPsec and TLS are of fairly limited 
applicability for application-level security - we are still missing
lots of pieces.

Keith



From owner-ietf-outbound  Fri Apr  7 13:20:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA12989
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 13:20:03 -0400 (EDT)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12694;
	Fri, 7 Apr 2000 13:07:11 -0400 (EDT)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id NAA09585;
	Fri, 7 Apr 2000 13:07:06 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v04220803b513c46d8615@[171.78.30.107]>
In-Reply-To: <200004071639.MAA01226@astro.cs.utk.edu>
References: <200004071639.MAA01226@astro.cs.utk.edu>
Date: Fri, 7 Apr 2000 13:04:15 -0400
To: Keith Moore <moore@cs.utk.edu>
From: Stephen Kent <kent@bbn.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Cc: Keith Moore <moore@cs.utk.edu>, karl@cavebear.com, iesg@ietf.org,
        ietf@ietf.org, rfc-ed@rfc-editor.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Keith,

Applications can gain a lot of security by building on top of a lower 
layer secure communication substrate, such as that provided by IPsec 
or TLS.  Such substrates allow the application developer to make 
assumptions about the security of the basic communication path, and 
have these assumptions be valid.  Precisely the sorts of things you 
are citing as "bad" can be addressed in this way.  Fancier 
application security requires some level of customization, perhaps in 
an application-specific fashion, as you noted.

Steve



From owner-ietf-outbound  Fri Apr  7 13:30:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA13204
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 13:30:04 -0400 (EDT)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12695;
	Fri, 7 Apr 2000 13:07:11 -0400 (EDT)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id NAA09592;
	Fri, 7 Apr 2000 13:07:07 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v04220805b513c5bbd477@[171.78.30.107]>
In-Reply-To: <38EE04CA.C7E0BF39@thinkingcat.com>
References: <200004070850.EAA24352@cs.utk.edu>
 <v04220806b513a760398e@[171.78.30.107]>
 <38EE04CA.C7E0BF39@thinkingcat.com>
Date: Fri, 7 Apr 2000 13:07:29 -0400
To: Leslie Daigle <leslie@thinkingcat.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Cc: Keith Moore <moore@cs.utk.edu>, iesg@ietf.org, ietf@ietf.org,
        rfc-ed@rfc-editor.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Leslie,

I understand your point, but we leave ourselves open to many forms of 
attacks, or errors, by assuming that "what you receive is what was 
sent" in this era of the Internet.  Security is not black and white, 
but the gray area we're discussing does bother me.  If one cares 
about knowing where the data originated, and that it has not been 
altered, then one needs to make use of the tools provided to address 
that concern.  if one doesn't use the tools, then one does not care 
very much, and the results may be surprising :-).

Steve



From owner-ietf-outbound  Fri Apr  7 13:50:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA13609
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 13:50:03 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13495
	for <ietf@ietf.org>; Fri, 7 Apr 2000 13:43:21 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1.Beta1/8.10.1.Beta1) with ESMTP id e37HhJk25662;
	Fri, 7 Apr 2000 13:43:19 -0400
Message-Id: <200004071743.e37HhJk25662@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Stephen Kent <kent@bbn.com>
cc: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Fri, 07 Apr 2000 13:07:29 EDT."
             <v04220805b513c5bbd477@[171.78.30.107]> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200004070850.EAA24352@cs.utk.edu> <v04220806b513a760398e@[171.78.30.107]> <38EE04CA.C7E0BF39@thinkingcat.com>
            <v04220805b513c5bbd477@[171.78.30.107]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 07 Apr 2000 13:43:15 -0400
X-Loop: ietf@ietf.org

On Fri, 07 Apr 2000 13:07:29 EDT, Stephen Kent said:
> but the gray area we're discussing does bother me.  If one cares 
> about knowing where the data originated, and that it has not been 
> altered, then one needs to make use of the tools provided to address 
> that concern.  if one doesn't use the tools, then one does not care 
> very much, and the results may be surprising :-).

The sad part is that in this day and age, we had to publish the SANS
DDOS Roadmap, which suggested that things would be a lot better if sites
installed the patches and did ingress/egress filtering.

I suspect that there is a *very large* portion of the Internet community that
does "care very much" (or at least enough to worry a little bit), but is
too new/clueless/whatever to properly find/install/configure the tools.

I encounter a lot of sites that install spam filters and firewalls because
they ARE concerned about spam, hackers, etc.  Unfortunately, a lot of them
Get It Very Wrong, and do stuff like bounce SMTP 'MAIL FROM:<>', or Do The
Wrong Thing with NTP traffic, etc etc.

I have to conclude that there's a lot of sites that *do* care very much, but
are lacking the technical expertise to use the tools.

Remember: There's 4 million .coms.  There's not 4 million experienced sysadmins.

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Fri Apr  7 14:00:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA13784
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 14:00:03 -0400 (EDT)
Received: from tor-smtp2.netcom.ca (tor-smtp2.netcom.ca [207.181.101.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13503;
	Fri, 7 Apr 2000 13:43:38 -0400 (EDT)
Received: from thinkingcat.com (mon-pq15-18.netcom.ca [216.123.104.146])
	by tor-smtp2.netcom.ca (8.8.7-s-4/8.8.7) with ESMTP id NAA22153;
	Fri, 7 Apr 2000 13:42:52 -0400 (EDT)
Message-ID: <38EE1E68.4046AF2C@thinkingcat.com>
Date: Fri, 07 Apr 2000 13:44:08 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
Organization: Thinking Cat Enterprises
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Stephen Kent <kent@bbn.com>
CC: Keith Moore <moore@cs.utk.edu>, iesg@ietf.org, ietf@ietf.org,
        rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <200004070850.EAA24352@cs.utk.edu>
	 <v04220806b513a760398e@[171.78.30.107]>
	 <38EE04CA.C7E0BF39@thinkingcat.com> <v04220805b513c5bbd477@[171.78.30.107]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


A fine argument in the abstract, but reality bites. 

Stephen Kent wrote:
> sent" in this era of the Internet.  Security is not black and white,
> but the gray area we're discussing does bother me.  If one cares
> about knowing where the data originated, and that it has not been
> altered, then one needs to make use of the tools provided to address
> that concern.  if one doesn't use the tools, then one does not care
> very much, and the results may be surprising :-).

Who is "one", in your mind?  Mail, web, WAP client application
writers?  Or the poor end-user who gets the surprise without having
a clue what hit him?

As an end-user, I can be as aware as I like about the security issues,
but if client software doesn't support security, and/or my ISP, services
don't support it, there's nothing I can do.  

I am not saying that security isn't the answer -- but I do think you're
looking at your chalkboard, not deployed reality, when you suggest
it isn't a problem because there are technologies for authenticating
packets.

Leslie.

-- 

-------------------------------------------------------------------
"My body obeys Aristotelian laws of physics."
   -- ThinkingCat

Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------



From owner-ietf-outbound  Fri Apr  7 14:10:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA14074
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 14:10:03 -0400 (EDT)
Received: from peridot.cisco.com (peridot.cisco.com [171.69.198.64])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13517;
	Fri, 7 Apr 2000 13:44:04 -0400 (EDT)
Received: from cisco.com (dhcp-171-69-44-215.cisco.com [171.69.44.215])
	by peridot.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id KAA21817;
	Fri, 7 Apr 2000 10:43:31 -0700 (PDT)
Message-ID: <38EE1DF7.87FE780D@cisco.com>
Date: Fri, 07 Apr 2000 10:42:15 -0700
From: Peter Deutsch <pdeutsch@cisco.com>
Reply-To: pdeutsch@cisco.com
Organization: Cisco Systems
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: karl@CAVEBEAR.COM, iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <200004070850.EAA24352@cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Keith Moore wrote:
.  .  .
> > > 3. Aside from the technical implications of intercepting traffic,
> > > redirecting it to unintended destinations, or forging traffic from
> > > someone else's IP address - there are also legal, social, moral and
> > > commercial implications of doing so.
> >
> > You will need to be far more specific here.  I see absolutely nothing that
> > is not legal, is not social, or is not moral.
> 
> Okay, I'll offer a few specific examples, by no means the only ones:
> 
> 1. an Internet service provider which deliberately intercepts traffic
> (say, an IP packet) which was intended for one address or service,
> and delivers it to another address or service (say that of an interception
> proxy) may be misrepresenting the service it provides (it's not really
> providing IP datagram delivery service because IP doesn't work this way).

Okay, I think I see the mistake you're making. You're crossing
abstraction layers and conflating two different things (the name of
a service with the end point of the connection to that service). You
are criticizing the moving of an endpoint when what you really
object to is the misrepresentation of a service. Or do you also
object to HTTP redirects, dynamic URL rewriting, CNAMEs, telephone
Call Forwarding, or post office redirecting of mail after you move? 

A while ago Fedex tried an advertizing campaign in which they
explained to people that when you send a packet from New York to
Chicago, the package is actually routed down to Tennessee (or where
ever it is) and then sent back up to the destination. They wanted
people to see how clever they were, in sending all their packets on
this round-about trip, thus getting it there *much* faster. 

The campaign apparently confused people, and made them nervous, so
they dropped it, but the point is still valid. If what you want is a
particular service (fast information delivery), don't confuse that
with the lower lever transport layer issues (packet delivery). It
may well be desireable to reroute things to get improved service at
a higher abstraction layer. I see nothing "illegal" about Fedex
sending my packet to Tennessee and I see nothing immoral about
Earthlink, MCI, Cisco and CNN all getting together to route my
packets to whichever one of Akami's caches is the most appropriate
one for me to go to today. After all, I didn't ask CNN to send me
packets, I asked CNN for today's news.

Now, misrepresenting myself as someone else may well be fraud, a
well defined crime, so someone else offering me news and pretending
it's from CNN is wrong, but that's nothing to do with IP packet
delivery. You're thinking at the wrong abstraction layer. Changing
IP addresses may *result* in fraud, depending upon why you do it,
but it doesn't constitute fraud in and of itself ("routers don't
mislead people, people mislead people..." ;-) 

Bottom line is, you seem pretty confused here. Sadly, you take this
in really strange directions (see below).


> 2. an internet service provider which deliberately forges IP datagrams
> using the source address of a content provider, to make it appear
> that the traffic was originated by that content provider
> (interception proxies do this), may be misrepresenting that content
> provider by implicitly claiming that the service conveyed to the user
> by the ISP is the one provided by the content provider.

Keith, this is a legal issue. We don't do legal issues here. If
someone is misrepresenting themselves, and causing harm, there are
very clearly defined legal mechanisms to address that. This is *so*
far outside the purvue of the IETF that I can't figure out what
you're even trying to accomplish. Out of curiosity, do you even have
any legal training??


.  .  .
> now whether any of these is actually illegal would be up to a court
> to decide, and different courts in different jurisdictions might rule
> differently (especially depending on the particulars of a test case)
> but each of these is similar to behavior that in other communications
> domains would be illegal.  and regardless of whether the grounds is
> technical, legal, or moral, none of these behaviors seems like
> something that IETF should support.

So because someone can pick up a router and beat someone to death
with it, we shouldn't build routers? Or do you honestly think it
appropriate that we add a "legal" section to RFCs?


.  .  .
> > May I suggest that one treat this in its classical sense - as a Request
> > for Comments and that those who have technical objections or technical
> > enhancements publish those comments in an additional document rather than
> > try to suppress the original one.
> 
> RFCs have not been treated in this sense for many years.  And while
> such treatment may have made sense in the early days of the ARPAnet
> with a community of a few hundred users, it does not make sense in
> an Internet with tens of millions of users.
> 
> The reality is that today, many documents submitted for RFCs are rejected.
> I'm simply arguing that this document should be added to that set.
> or at least, that it needs substantial revision before it is found
> acceptable.

So you are arguing for explicit censorship of ideas based upon your
own moral assessment of the potential misuse of those ideas? Wow.
Now *that* is a dangerous notion indeed. I sincerely hope it is not
a widely held one within the echelons of the IETF...


				- peterd



-- 
----------------------------------------------------------------------
Peter Deutsch                     work email:  pdeutsch@cisco.com
Technical Leader
Content Services Business Unit       private: 
pdeutsch@earthlink.net
Cisco Systems                           or  :  peterd@the.web

         Alcohol and calculus don't mix. Never drink and derive.
----------------------------------------------------------------------



From owner-ietf-outbound  Fri Apr  7 14:20:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA14263
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 14:20:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14158
	for <ietf@ietf.org>; Fri, 7 Apr 2000 14:16:04 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id MAA05824
	for ietf@ietf.org  env-from <vjs>;
	Fri, 7 Apr 2000 12:16:05 -0600 (MDT)
Date: Fri, 7 Apr 2000 12:16:05 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004071816.MAA05824@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
X-Loop: ietf@ietf.org

> From: Valdis.Kletnieks@vt.edu

> ...
> they ARE concerned about spam, hackers, etc.  Unfortunately, a lot of them
> Get It Very Wrong, and do stuff like bounce SMTP 'MAIL FROM:<>', or Do The
> Wrong Thing with NTP traffic, etc etc.
>
> I have to conclude that there's a lot of sites that *do* care very much, but
> are lacking the technical expertise to use the tools.
>
> Remember: There's 4 million .coms.  There's not 4 million experienced sysadmins.


It's worse than that, as AOL is demonstrating with their port 25 redirecting.
If your skin doesn't crawl at the thought of a third party adding headers
to your SMTP messages, you need to take some time out to think about things.
There need be no significant implementation difference between adding
headers and making improvements to the body of an SMTP message.

Then there is the collateral damage.  I don't know if the AOL redirectors
store and forward, but if they do, think about what that does to SMTP AUTH
challenges and responses.   (yes, assuming that SMTP AUTH runs on port 25
or that AOL expands their redirecting to other ports).

If you haven't seen wierd effects from HTTP redirecting including clients
getting the wrong (i.e. old) pages, then you need to look around.

I think a bigger worry than a shortage of experience administrators is an
abundance of people who prefer the easiest, cheapest in the short term
solution instead of a long view, such as redirecting SMTP instead of
enforcing serious anti-spam terms of service.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Fri Apr  7 14:30:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA14590
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 14:30:03 -0400 (EDT)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14479;
	Fri, 7 Apr 2000 14:26:59 -0400 (EDT)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id OAA21390;
	Fri, 7 Apr 2000 14:26:57 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v04220809b513d79c07ee@[171.78.30.107]>
In-Reply-To: <38EE1E68.4046AF2C@thinkingcat.com>
References: <200004070850.EAA24352@cs.utk.edu>	
 <v04220806b513a760398e@[171.78.30.107]>	
 <38EE04CA.C7E0BF39@thinkingcat.com>
 <v04220805b513c5bbd477@[171.78.30.107]>
 <38EE1E68.4046AF2C@thinkingcat.com>
Date: Fri, 7 Apr 2000 14:27:57 -0400
To: Leslie Daigle <leslie@thinkingcat.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Cc: Keith Moore <moore@cs.utk.edu>, iesg@ietf.org, ietf@ietf.org,
        rfc-ed@rfc-editor.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

In my 20+ years of security experience in the Internet community, it 
has often been the arguments for the need to make do with existing 
features or to adopt quick fix solutions that have retarded the 
deployment of better security technology.  In retrospect, this 
approach has not served us well.

Steve



From owner-ietf-outbound  Fri Apr  7 14:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA14937
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 14:40:03 -0400 (EDT)
Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14477;
	Fri, 7 Apr 2000 14:26:58 -0400 (EDT)
Received: from software-munitions.com (fwiw.plaintalk.bellevue.wa.us [206.129.5.157])
	by btw.plaintalk.bellevue.wa.us (8.10.0/8.9.3) with ESMTP id e37IPeH04801;
	Fri, 7 Apr 2000 11:25:48 -0700 (PDT)
Message-ID: <38EE2824.F6E36729@software-munitions.com>
Date: Fri, 07 Apr 2000 11:25:40 -0700
From: Dennis Glatting <dennis.glatting@software-munitions.com>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Leslie Daigle <leslie@THINKINGCAT.COM>
CC: Stephen Kent <kent@bbn.com>, Keith Moore <moore@cs.utk.edu>, iesg@ietf.org,
        ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <200004070850.EAA24352@cs.utk.edu>
		 <v04220806b513a760398e@[171.78.30.107]>
		 <38EE04CA.C7E0BF39@thinkingcat.com> <v04220805b513c5bbd477@[171.78.30.107]> <38EE1E68.4046AF2C@thinkingcat.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms55BC5C9229D5F8965D86FB5A"
X-Loop: ietf@ietf.org

This is a cryptographically signed message in MIME format.

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

Leslie Daigle wrote:
> 

> As an end-user, I can be as aware as I like about the security issues,
> but if client software doesn't support security, and/or my ISP, services
> don't support it, there's nothing I can do.
> 

Huh? You have a choice: (a) obtain a client that does support
security; and (b) get a new ISP. Both are plentiful.
--------------ms55BC5C9229D5F8965D86FB5A
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIIKLgYJKoZIhvcNAQcCoIIKHzCCChsCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
B7owggSEMIID7aADAgECAhBkri59tvkxtYKkoLhk1DpkMA0GCSqGSIb3DQEBBAUAMIHMMRcw
FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5
IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp
dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAwMDMxODAwMDAw
MFoXDTAxMDMxODIzNTk1OVowggEoMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE
CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y
ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO
ZXRzY2FwZSBGdWxsIFNlcnZpY2UxGDAWBgNVBAMUD0Rlbm5pcyBHbGF0dGluZzE1MDMGCSqG
SIb3DQEJARYmZGVubmlzLmdsYXR0aW5nQHNvZnR3YXJlLW11bml0aW9ucy5jb20wgZ8wDQYJ
KoZIhvcNAQEBBQADgY0AMIGJAoGBALIHuKw5XXJUSbc5EJJf9EvuRmzi6hDpPOQ7ZK1xM4/w
kLjboQgvmyw2JIyDZo/xyMyyGyiyYLOKzti03yZJ0hufZQZrxrNFlgY9NwdBnP14CGjBmFfz
kvtBj+sw7RbEbmGWN5o8iZEOyOOFZ/ocNStPZNFWNXZknLsBPUSrjSTXAgMBAAGjggEGMIIB
AjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUF
BwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVy
aVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2Ug
bGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwMwYDVR0fBCww
KjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0B
AQQFAAOBgQBS65IE6SU4NGmhHk3vegakv/owvCAc0JE+y9hBKCUKPCV49mq6KboDKxVolCYk
/FBVZtbA9WBRALtsV2RBbIgQO0cZO007VQHNNtZQ8fuQQmWImM2JbXSnTKTwP/HZcbiRhrsK
+9f6mzz8NRYA8OCDrbZzcALSCm0AkqyakKUo9DCCAy4wggKXoAMCAQICEQDSdi6NFAw9fbKo
JV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2ln
biwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9u
IEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5NTlaMIHMMRcwFQYDVQQK
Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQG
A1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4s
TElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFs
IFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0GCSqGSIb3DQEBAQUAA4GN
ADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqdufBou5XZMUFweoFLuUgT
Vi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIztW5UiE+HSr8Z2vkV6A+Hthzj
zMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQABo3wwejARBglghkgBhvhCAQEEBAMC
AQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUFBwIBFh93d3cudmVyaXNp
Z24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAwCwYDVR0PBAQDAgEGMA0G
CSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bxndPKZDjcG5gMB4ZbhRVq
D7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPHvhnXU0zDvcjjF7WkSUJj7MKmFw9d
WBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWikK5uMYICPDCCAjgCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEGSuLn22+TG1gqSg
uGTUOmQwCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0wMDA0MDcxODI1NDBaMCMGCSqGSIb3DQEJBDEWBBR5Ud45/5eS2R198S2XCw5i
z4BodTBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDAHBgUr
DgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASBgCVK
uhisSktFzCiuPzQN9FdGfzZ+/Gb4oAgbFIHmrrfAFrGSGxLVXYnqigBxpfZqxNG7YD7VRGxC
05Rd+QIPpoXCBIosmzUCLhF3mfjDFKmCH+SIlQVSKBgNA2b62Rog7ZurttEgNGCpCRCkZqyb
P4H9ZKOFeh0ZH0Nv6fLaRPMz
--------------ms55BC5C9229D5F8965D86FB5A--



From owner-ietf-outbound  Fri Apr  7 14:50:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA15136
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 14:50:03 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14712
	for <ietf@ietf.org>; Fri, 7 Apr 2000 14:33:11 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1.Beta1/8.10.1.Beta1) with ESMTP id e37IWsk25702;
	Fri, 7 Apr 2000 14:32:54 -0400
Message-Id: <200004071832.e37IWsk25702@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Fri, 07 Apr 2000 12:16:05 MDT."
             <200004071816.MAA05824@calcite.rhyolite.com> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200004071816.MAA05824@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 07 Apr 2000 14:32:54 -0400
X-Loop: ietf@ietf.org

On Fri, 07 Apr 2000 12:16:05 MDT, Vernon Schryver <vjs@calcite.rhyolite.com>  said:
> It's worse than that, as AOL is demonstrating with their port 25 redirecting.

Hmm.. I don't correspond with that many AOL people.  What are they doing NOW?

> If your skin doesn't crawl at the thought of a third party adding headers
> to your SMTP messages, you need to take some time out to think about things.

You mean *other* than the required RFC822 Received: headers, and/or the
RFC2476-approved re-writing?  Gaak if so.

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Fri Apr  7 15:00:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA15402
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 15:00:04 -0400 (EDT)
Received: from corpmail.galaxyscientific.com ([38.221.233.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14755;
	Fri, 7 Apr 2000 14:35:25 -0400 (EDT)
Received: from BELLOPEM (igate.tc.faa.gov [155.178.180.5]) by corpmail.galaxyscientific.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id 2KDCMMAF; Fri, 7 Apr 2000 14:34:29 -0400
From: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
To: "Peter Deutsch" <pdeutsch@cisco.com>, "Keith Moore" <moore@CS.UTK.EDU>
Cc: <karl@CAVEBEAR.COM>, <iesg@ietf.org>, <ietf@ietf.org>,
        <rfc-ed@rfc-editor.org>
Subject: RE: recommendation against publication of draft-cerpa-necp-0
Date: Fri, 7 Apr 2000 14:34:14 -0400
Message-ID: <PPECLLOGBEPHLOMKLNAMGEGOCAAA.Michael.CTR.Bellopede@tc.faa.gov>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
In-Reply-To: <8545@tc.faa.gov>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


>>
>> 1. an Internet service provider which deliberately intercepts traffic
>> (say, an IP packet) which was intended for one address or service,
>> and delivers it to another address or service (say that of an
interception
>> proxy) may be misrepresenting the service it provides (it's not really
>> providing IP datagram delivery service because IP doesn't work this way).
>
>Okay, I think I see the mistake you're making. You're crossing
>abstraction layers and conflating two different things (the name of
>a service with the end point of the connection to that service). You
>are criticizing the moving of an endpoint when what you really
>object to is the misrepresentation of a service. Or do you also
>object to HTTP redirects, dynamic URL rewriting, CNAMEs, telephone
>Call Forwarding, or post office redirecting of mail after you move?


I think we are confusing the issue here.  Earlier in this thread I found the
following written by Keith Moore:

>2. A primary purpose of the NECP protocol appears to be to
>facilitate the operation of so-called interception proxies.  Such
>proxies violate the Internet Protocol in several ways:
>
>(1) they redirect traffic to a destination other than the one
>specified in the IP header,
>
>(2) they impersonate other IP hosts by using those hosts' IP addresses
>as source addresses in traffic they generate,
>(3) for some interception proxies, traffic which is passed on to the
>destination host, is modified in transit, and any packet-level
>checksums are regenerated.

Regardless of what occurs at higher layers, there is still the problem of
changing the source address in an IP packet which occurs at the network(IP)
layer.

Michael B. Bellopede
Michael.CTR.Bellopede@tc.faa.gov
"There is no spoon."



From owner-ietf-outbound  Fri Apr  7 15:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA15715
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 15:10:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14777;
	Fri, 7 Apr 2000 14:36:20 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA01784;
        Fri, 7 Apr 2000 14:35:36 -0400 (EDT)
Message-Id: <200004071835.OAA01784@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Stephen Kent <kent@bbn.com>
cc: Keith Moore <moore@cs.utk.edu>, karl@cavebear.com, iesg@ietf.org,
        ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Fri, 07 Apr 2000 13:04:15 EDT."
             <v04220803b513c46d8615@[171.78.30.107]> 
Date: Fri, 07 Apr 2000 14:35:36 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Applications can gain a lot of security by building on top of a lower 
> layer secure communication substrate, such as that provided by IPsec 
> or TLS.  Such substrates allow the application developer to make 
> assumptions about the security of the basic communication path, and 
> have these assumptions be valid.  Precisely the sorts of things you 
> are citing as "bad" can be addressed in this way.  Fancier 
> application security requires some level of customization, perhaps in 
> an application-specific fashion, as you noted.

I beg to differ.  Few applications can use IPsec or TLS authentication 
as-is.   A few more can get away with using username/password schemes
on top of IPsec or TLS privacy.  But neither IPsec nor TLS is anything
resembling a generally applicable authentication solution.  

Keith



From owner-ietf-outbound  Fri Apr  7 15:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA16020
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 15:20:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14819;
	Fri, 7 Apr 2000 14:37:19 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA01795;
        Fri, 7 Apr 2000 14:36:52 -0400 (EDT)
Message-Id: <200004071836.OAA01795@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Stephen Kent <kent@bbn.com>
cc: Leslie Daigle <leslie@thinkingcat.com>, Keith Moore <moore@cs.utk.edu>,
        iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Fri, 07 Apr 2000 13:07:29 EDT."
             <v04220805b513c5bbd477@[171.78.30.107]> 
Date: Fri, 07 Apr 2000 14:36:52 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

Stephen,

perhaps the reason that the tools are not used is that they are not
adequate for the task.  but it certainly does not follow that "if 
one doesn't use the tools, then one does not care very much".

Keith

> If one cares 
> about knowing where the data originated, and that it has not been 
> altered, then one needs to make use of the tools provided to address 
> that concern.  if one doesn't use the tools, then one does not care 
> very much, and the results may be surprising :-).



From owner-ietf-outbound  Fri Apr  7 15:30:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA16284
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 15:30:03 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15309;
	Fri, 7 Apr 2000 14:57:25 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1.Beta1/8.10.1.Beta1) with ESMTP id e37IuYk23228;
	Fri, 7 Apr 2000 14:56:34 -0400
Message-Id: <200004071856.e37IuYk23228@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Dennis Glatting <dennis.glatting@software-munitions.com>
cc: Leslie Daigle <leslie@THINKINGCAT.COM>, Stephen Kent <kent@bbn.com>,
        Keith Moore <moore@CS.UTK.EDU>, iesg@ietf.org, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Fri, 07 Apr 2000 11:25:40 PDT."
             <38EE2824.F6E36729@software-munitions.com> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200004070850.EAA24352@cs.utk.edu> <v04220806b513a760398e@[171.78.30.107]> <38EE04CA.C7E0BF39@thinkingcat.com> <v04220805b513c5bbd477@[171.78.30.107]> <38EE1E68.4046AF2C@thinkingcat.com>
            <38EE2824.F6E36729@software-munitions.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 07 Apr 2000 14:56:34 -0400
X-Loop: ietf@ietf.org

On Fri, 07 Apr 2000 11:25:40 PDT, Dennis Glatting said:
> Huh? You have a choice: (a) obtain a client that does support
> security; and (b) get a new ISP. Both are plentiful.

Only if a client supporting security is available for your software
(which might be be something other than Netscape/IE - the Web and the
Internet are not the same thing.  There are platforms that (for instance)
have a telnet client, but no ssh client.

Only if a client supporting security is available in your country.  Some
countries still have issues regarding cryptography.

Only if a new ISP is available in *your area*.  In many parts of the country,
if you require ISDN, DSL, cable modem, or anything else that's faster than
a 56K-over-POTS, your choices are severely limited, and may in fact be zero
for some technologies.

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Fri Apr  7 15:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA16528
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 15:40:02 -0400 (EDT)
Received: from garlic.amaranth.net ([216.235.243.195])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15442
	for <ietf@ietf.org>; Fri, 7 Apr 2000 15:00:39 -0400 (EDT)
Received: from senie.com (garlic.amaranth.net [216.235.243.195])
	(authenticated)
	by garlic.amaranth.net (8.10.0/8.10.0) with ESMTP id e37J0Le06179;
	Fri, 7 Apr 2000 15:00:22 -0400
Message-ID: <38EE3046.3E7AFC73@senie.com>
Date: Fri, 07 Apr 2000 15:00:22 -0400
From: Daniel Senie <dts@senie.com>
Organization: Amaranth Networks Inc.
X-Mailer: Mozilla 4.72 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dennis Glatting <dennis.glatting@SOFTWARE-MUNITIONS.COM>
CC: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <200004070850.EAA24352@cs.utk.edu>
			 <v04220806b513a760398e@[171.78.30.107]>
			 <38EE04CA.C7E0BF39@thinkingcat.com> <v04220805b513c5bbd477@[171.78.30.107]> <38EE1E68.4046AF2C@thinkingcat.com> <38EE2824.F6E36729@software-munitions.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Dennis Glatting wrote:
> 
> Leslie Daigle wrote:
> >
> 
> > As an end-user, I can be as aware as I like about the security issues,
> > but if client software doesn't support security, and/or my ISP, services
> > don't support it, there's nothing I can do.
> >
> 
> Huh? You have a choice: (a) obtain a client that does support
> security; and (b) get a new ISP. Both are plentiful.

Ah, no. In the real world of the Internet today, we have LOTS of folks
who get their Internet connectivity via cable modems and DSL. Many
vendors of such services, in order to help preserve IP address space,
give out only a single IP address to each customer. Since this is
incompatible with the way people use the Internet in many cases (e.g.
MANY homes have more than one computer), Network Address Translation is
used.

NAT is the reality of the Internet today. IPSec was developed for an
Internet that existed some years back, before address allocation
policies forced NAT to become commonplace. We now are in need of
security solutions which can survive such an environment. SSL is one
such example.

NAT presents a lot of problems to the Internet architecture. It's ugly
architecturally. We all know that. We can't make it go away by
complaining about it. We could fix IPSec to survive in the current
environment, or find ways to get more people interested in IPv6, do
both, or find alternate forms of security.

Getting a new ISP, however, is NOT necessarily an option. You'd argue I
give up a cable modem for a dialup ISP? I don't think so. Application
level security (SSL, TLS, SSH) work fine for my needs and transit the
equipment I must use to exist on a cable modem.

-- 
-----------------------------------------------------------------
Daniel Senie                                        dts@senie.com
Amaranth Networks Inc.                    http://www.amaranth.com



From owner-ietf-outbound  Fri Apr  7 15:50:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA16745
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 15:50:05 -0400 (EDT)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15597;
	Fri, 7 Apr 2000 15:07:01 -0400 (EDT)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id PAA28495;
	Fri, 7 Apr 2000 15:06:56 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v0422080db513e04c1250@[171.78.30.107]>
In-Reply-To: <200004071836.OAA01795@astro.cs.utk.edu>
References: <200004071836.OAA01795@astro.cs.utk.edu>
Date: Fri, 7 Apr 2000 14:59:31 -0400
To: Keith Moore <moore@cs.utk.edu>
From: Stephen Kent <kent@bbn.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Cc: Leslie Daigle <leslie@thinkingcat.com>, Keith Moore <moore@cs.utk.edu>,
        iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Keith,

>Stephen,
>
>perhaps the reason that the tools are not used is that they are not
>adequate for the task.  but it certainly does not follow that "if
>one doesn't use the tools, then one does not care very much".

or perhaps, one does not care enough ...

Steve



From owner-ietf-outbound  Fri Apr  7 16:00:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA16962
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 16:00:03 -0400 (EDT)
Received: from baboon.aciri.org (baboon.aciri.org [192.150.187.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15801;
	Fri, 7 Apr 2000 15:12:30 -0400 (EDT)
Received: (from pfrancis@localhost)
	by baboon.aciri.org (8.9.3/8.9.3) id MAA25306;
	Fri, 7 Apr 2000 12:12:30 -0700 (PDT)
	(envelope-from pfrancis)
Date: Fri, 7 Apr 2000 12:12:30 -0700 (PDT)
From: Paul Francis <pfrancis@aciri.org>
Message-Id: <200004071912.MAA25306@baboon.aciri.org>
To: kent@bbn.com, leslie@thinkingcat.com
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Cc: iesg@ietf.org, ietf@ietf.org, moore@cs.utk.edu, rfc-ed@rfc-editor.org
In-Reply-To: <v04220809b513d79c07ee@[171.78.30.107]>
X-Loop: ietf@ietf.org

>  
>  In my 20+ years of security experience in the Internet community, it 
>  has often been the arguments for the need to make do with existing 
>  features or to adopt quick fix solutions that have retarded the 
>  deployment of better security technology.  In retrospect, this 
>  approach has not served us well.
>  

I have a time machine.

I just went back 20 years in time, convinced everybody that it
was always more important to implement proper security than to
make do with existing features and quick fix solutions.  Having
thus changed the future, I went back forward in time.
Guess what---there was no internet!

PF



From owner-ietf-outbound  Fri Apr  7 16:10:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA17208
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 16:10:04 -0400 (EDT)
Received: from corpmail.galaxyscientific.com ([38.221.233.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15859;
	Fri, 7 Apr 2000 15:14:55 -0400 (EDT)
Received: from BELLOPEM (igate.tc.faa.gov [155.178.180.5]) by corpmail.galaxyscientific.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id 2KDCMMC5; Fri, 7 Apr 2000 15:13:59 -0400
From: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
To: "Dennis Glatting" <dennis.glatting@software-munitions.com>,
        "Leslie Daigle" <leslie@THINKINGCAT.COM>
Cc: "Stephen Kent" <kent@bbn.com>, "Keith Moore" <moore@CS.UTK.EDU>,
        <iesg@ietf.org>, <ietf@ietf.org>
Subject: RE: recommendation against publication of draft-cerpa-necp-0
Date: Fri, 7 Apr 2000 15:13:44 -0400
Message-ID: <PPECLLOGBEPHLOMKLNAMOEGPCAAA.Michael.CTR.Bellopede@tc.faa.gov>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
In-Reply-To: <8555@tc.faa.gov>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Dennis-

That is not a fair statement to make to an end-user.  My end-users have no
say about what client software, services, or ISP solutions provided.

-Michael B. Bellopede
 Michael.CTR.Bellopede@tc.faa.gov


Leslie Daigle wrote:
>

> As an end-user, I can be as aware as I like about the security issues,
> but if client software doesn't support security, and/or my ISP, services
> don't support it, there's nothing I can do.
>

Huh? You have a choice: (a) obtain a client that does support
security; and (b) get a new ISP. Both are plentiful.



From owner-ietf-outbound  Fri Apr  7 16:20:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA17369
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 16:20:04 -0400 (EDT)
Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15903
	for <ietf@ietf.org>; Fri, 7 Apr 2000 15:16:37 -0400 (EDT)
Received: from software-munitions.com (fwiw.plaintalk.bellevue.wa.us [206.129.5.157])
	by btw.plaintalk.bellevue.wa.us (8.10.0/8.9.3) with ESMTP id e37JFpH04929;
	Fri, 7 Apr 2000 12:15:53 -0700 (PDT)
Message-ID: <38EE33E7.2EC883EB@software-munitions.com>
Date: Fri, 07 Apr 2000 12:15:51 -0700
From: Dennis Glatting <dennis.glatting@software-munitions.com>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Daniel Senie <dts@senie.com>, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <200004070850.EAA24352@cs.utk.edu>
				 <v04220806b513a760398e@[171.78.30.107]>
				 <38EE04CA.C7E0BF39@thinkingcat.com> <v04220805b513c5bbd477@[171.78.30.107]> <38EE1E68.4046AF2C@thinkingcat.com> <38EE2824.F6E36729@software-munitions.com> <38EE3046.3E7AFC73@senie.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms534287799AB839ABE3C29C3F"
X-Loop: ietf@ietf.org

This is a cryptographically signed message in MIME format.

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

 
> Getting a new ISP, however, is NOT necessarily an option. You'd argue I
> give up a cable modem for a dialup ISP? I don't think so. Application
> level security (SSL, TLS, SSH) work fine for my needs and transit the
> equipment I must use to exist on a cable modem.
> 

You have made the choice to have no choice but you do have a choice.
--------------ms534287799AB839ABE3C29C3F
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIIKLgYJKoZIhvcNAQcCoIIKHzCCChsCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
B7owggSEMIID7aADAgECAhBkri59tvkxtYKkoLhk1DpkMA0GCSqGSIb3DQEBBAUAMIHMMRcw
FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5
IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp
dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAwMDMxODAwMDAw
MFoXDTAxMDMxODIzNTk1OVowggEoMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE
CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y
ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO
ZXRzY2FwZSBGdWxsIFNlcnZpY2UxGDAWBgNVBAMUD0Rlbm5pcyBHbGF0dGluZzE1MDMGCSqG
SIb3DQEJARYmZGVubmlzLmdsYXR0aW5nQHNvZnR3YXJlLW11bml0aW9ucy5jb20wgZ8wDQYJ
KoZIhvcNAQEBBQADgY0AMIGJAoGBALIHuKw5XXJUSbc5EJJf9EvuRmzi6hDpPOQ7ZK1xM4/w
kLjboQgvmyw2JIyDZo/xyMyyGyiyYLOKzti03yZJ0hufZQZrxrNFlgY9NwdBnP14CGjBmFfz
kvtBj+sw7RbEbmGWN5o8iZEOyOOFZ/ocNStPZNFWNXZknLsBPUSrjSTXAgMBAAGjggEGMIIB
AjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUF
BwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVy
aVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2Ug
bGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwMwYDVR0fBCww
KjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0B
AQQFAAOBgQBS65IE6SU4NGmhHk3vegakv/owvCAc0JE+y9hBKCUKPCV49mq6KboDKxVolCYk
/FBVZtbA9WBRALtsV2RBbIgQO0cZO007VQHNNtZQ8fuQQmWImM2JbXSnTKTwP/HZcbiRhrsK
+9f6mzz8NRYA8OCDrbZzcALSCm0AkqyakKUo9DCCAy4wggKXoAMCAQICEQDSdi6NFAw9fbKo
JV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2ln
biwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9u
IEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5NTlaMIHMMRcwFQYDVQQK
Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQG
A1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4s
TElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFs
IFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0GCSqGSIb3DQEBAQUAA4GN
ADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqdufBou5XZMUFweoFLuUgT
Vi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIztW5UiE+HSr8Z2vkV6A+Hthzj
zMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQABo3wwejARBglghkgBhvhCAQEEBAMC
AQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUFBwIBFh93d3cudmVyaXNp
Z24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAwCwYDVR0PBAQDAgEGMA0G
CSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bxndPKZDjcG5gMB4ZbhRVq
D7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPHvhnXU0zDvcjjF7WkSUJj7MKmFw9d
WBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWikK5uMYICPDCCAjgCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEGSuLn22+TG1gqSg
uGTUOmQwCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0wMDA0MDcxOTE1NTFaMCMGCSqGSIb3DQEJBDEWBBSynxzeF1o7TvSQieU5y+Np
eQMpSzBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDAHBgUr
DgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASBgIdY
BGFmt8DKfLy160+13Fi9kXJ57QB1/BdWeQM4qQJ44vdiLmC67QbVpxmy8i350dl9y/VBmndf
pVcswchgNJkjwvBc/YLHUDp3jw24sC41FqYzBcOVRhwWlv1u0Q4QwUed4MzigiO8mfgXJje2
mk8zM7XnBL9Th7OSxYCDbmOY
--------------ms534287799AB839ABE3C29C3F--



From owner-ietf-outbound  Fri Apr  7 16:31:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA17738
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 16:31:26 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15910;
	Fri, 7 Apr 2000 15:16:53 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA01895;
        Fri, 7 Apr 2000 15:15:57 -0400 (EDT)
Message-Id: <200004071915.PAA01895@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: pdeutsch@cisco.com
cc: Keith Moore <moore@cs.utk.edu>, karl@CAVEBEAR.COM, iesg@ietf.org,
        ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Fri, 07 Apr 2000 10:42:15 PDT."
             <38EE1DF7.87FE780D@cisco.com> 
X-SUBJECT-MSG-FROM: Peter Deutsch <pdeutsch@cisco.com> 
Date: Fri, 07 Apr 2000 15:15:57 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Keith Moore wrote:
> .  .  .
> > > > 3. Aside from the technical implications of intercepting traffic,
> > > > redirecting it to unintended destinations, or forging traffic from
> > > > someone else's IP address - there are also legal, social, moral and
> > > > commercial implications of doing so.
> > >
> > > You will need to be far more specific here.  I see absolutely nothing that
> > > is not legal, is not social, or is not moral.
> > 
> > Okay, I'll offer a few specific examples, by no means the only ones:
> > 
> > 1. an Internet service provider which deliberately intercepts traffic
> > (say, an IP packet) which was intended for one address or service,
> > and delivers it to another address or service (say that of an interception
> > proxy) may be misrepresenting the service it provides (it's not really
> > providing IP datagram delivery service because IP doesn't work this way).
> 
> Okay, I think I see the mistake you're making. You're crossing
> abstraction layers and conflating two different things (the name of
> a service with the end point of the connection to that service). You
> are criticizing the moving of an endpoint when what you really
> object to is the misrepresentation of a service. Or do you also
> object to HTTP redirects, dynamic URL rewriting, CNAMEs, telephone
> Call Forwarding, or post office redirecting of mail after you move? 

I don't object to redirects at all, as long as they are carefully 
designed.   I do object to misrepresenting the service.    As I've 
said elsewhere, if the service wants to set up an interception proxy 
on its own network to help make its service more scalable, I have 
no problem with that.  I do have a problem with unauthorized third 
parties setting up interception proxies.  (which is according to
my understanding all the most common application of such devices)

> It may well be desireable to reroute things to get improved service at
> a higher abstraction layer. 

the problem is that one person's idea of improved service may be
another person's idea of degraded service.  getting stale data
to me faster may not be much help.  I would argue that it
is up to the producer and consumer, not the ISP, to decide what
level of service is appropriate.

> I see nothing "illegal" about Fedex
> sending my packet to Tennessee and I see nothing immoral about
> Earthlink, MCI, Cisco and CNN all getting together to route my
> packets to whichever one of Akami's caches is the most appropriate
> one for me to go to today. After all, I didn't ask CNN to send me
> packets, I asked CNN for today's news.

If CNN is okay with this, I have no problem with it.  They get to
decide what content delivery mechanisms are appropriate for their
content.  Other content providers might make different decisions.
Where I have a problem is when J. Random ISP unilaterally decides 
that some content delivery mechanism other than standard IP routing
is appropriate for CNN's data (or my data).  

And on some level, yes, you did ask CNN to send you packets.  Or you
sent packets to CNN and the network sent you some packets back purporting
to be from CNN.  You and your web client presumably knew what you were
asking for, and CNN's web server (if it was even in the loop) presumably
knew what kind of response to give.  But the network in the middle does
not know for sure how to interpret your request and CNN's response.
Just because you are sending port 80 does not even mean that you are 
using HTTP, and it certanily doesn't mean that you're using the same
version of HTTP that the interception proxy just happens to support,
and it certainly doesn't mean that you're willing to tolerate whatever
data corruption the interception proxy (whether by design or by accident)
happens to introduce.


> Now, misrepresenting myself as someone else may well be fraud, a
> well defined crime, so someone else offering me news and pretending
> it's from CNN is wrong, but that's nothing to do with IP packet
> delivery. You're thinking at the wrong abstraction layer. Changing
> IP addresses may *result* in fraud, depending upon why you do it,
> but it doesn't constitute fraud in and of itself ("routers don't
> mislead people, people mislead people..." ;-) 

You seem to be saying that because we have a higher service layered 
on top of IP that we can disregard the IP service model.  I disagree.
There are two separate problems here:

1. An interception proxy, unless it is acting with authorization 
of the content provider, is misrepresenting itself as the content 
provider.  IP address spoofing as just one particular mechanism 
by which this can be done, but regardless of the mechanism, it's 
wrong to misrepresent yourself as someone else.

2. At a different level, IP networks that don't behave like IP 
networks are supposed to behave violate the assumptions on which 
higher level protocols are based.  This degrades interoperability
and increases the complexity of higher level protocols as they
try to work around the damage done when clean layering is destroyed.
(for example of increased complexity consider the suggestions to
solve the problem by having everyone use IPsec or TLS)

(as a friend of mine said many years ago, the problem with intelligent
networks is that the network has to be smarter than the applications.)

now it happens that both of these problems are caused by interception
proxies, which is why I choose to mention both of them in the same
discussion.
 
> Bottom line is, you seem pretty confused here. 

only if you think that discussing several related topics in a single
mail message is a sign of confusion.

> > 2. an internet service provider which deliberately forges IP datagrams
> > using the source address of a content provider, to make it appear
> > that the traffic was originated by that content provider
> > (interception proxies do this), may be misrepresenting that content
> > provider by implicitly claiming that the service conveyed to the user
> > by the ISP is the one provided by the content provider.
> 
> Keith, this is a legal issue. We don't do legal issues here. 

that's BS.  IETF has every reason to be concerned about publishing
documents that promote illegal or clearly immoral behavior.  While it 
is true that it is not for us to judge fine points of law, it's also 
true that promoting illegal or clearly immoral behavior reflects poorly 
on IETF as an institution and would impair IETF's ability to do its work.
It is not useful to direct IETF's energies in these directions.

The alternative  - to pretend that there are no social implications
to what we are doing in IETF - strikes me as dangerous and irresponsible.

> So because someone can pick up a router and beat someone to death
> with it, we shouldn't build routers? 

no, if someone designed a router whose primary purpose were to beat
someone to death, we shouldn't endorse such a product.

> > RFCs have not been treated in this sense for many years.  And while
> > such treatment may have made sense in the early days of the ARPAnet
> > with a community of a few hundred users, it does not make sense in
> > an Internet with tens of millions of users.
> > 
> > The reality is that today, many documents submitted for RFCs are rejected.
> > I'm simply arguing that this document should be added to that set.
> > or at least, that it needs substantial revision before it is found
> > acceptable.
> 
> So you are arguing for explicit censorship of ideas based upon your
> own moral assessment of the potential misuse of those ideas? Wow.
> Now *that* is a dangerous notion indeed. I sincerely hope it is not
> a widely held one within the echelons of the IETF...

Your use of the word "censorship" is incorrect.  I'm not arguing that 
IETF should try to prevent anybody from publishing their own ideas 
in any forum willing to support them.  Instead I'm arguing that IETF 
and the RFC Editor should not serve as that forum.  I belive that to 
do so would do harm to and the Internet and that IETF's and the RFC 
Editor's meager resources are better spent on more socially useful endeavors.

And absolutely I am making an argument based on my own assessment of 
both the morality of the practice and the technical issues associated
with that practice.  Why should it be dangerous or wrong to argue for 
what one believes is right?

Keith



From owner-ietf-outbound  Fri Apr  7 16:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA17915
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 16:40:04 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15929
	for <ietf@ietf.org>; Fri, 7 Apr 2000 15:17:09 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id NAA06797
	for ietf@ietf.org  env-from <vjs>;
	Fri, 7 Apr 2000 13:17:10 -0600 (MDT)
Date: Fri, 7 Apr 2000 13:17:10 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004071917.NAA06797@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
X-Loop: ietf@ietf.org

> From: Valdis.Kletnieks@vt.edu

> ...
> > If your skin doesn't crawl at the thought of a third party adding headers
> > to your SMTP messages, you need to take some time out to think about things.
>
> You mean *other* than the required RFC822 Received: headers, and/or the
> RFC2476-approved re-writing?  Gaak if so.

Consider the following:

] From: jay@aol.com (Jay Levitt)
] Newsgroups: news.admin.net-abuse.email
] Subject: Re: AOL Spammer online now, now what?
] Date: 30 Mar 2000 05:18:23 GMT
] Message-ID: <20000330001823.01291.00003030@ng-md1.aol.com>

] ...
] rly-ip* are the new hosts that will catch all port 25 connections from
] *.ipt.aol.com and attempt to filter spam.  They will also add the
] X-Apparently-From: header with the real AOL/CS/whatever screen name. ...


That all sounds fine, if you worry only about reducing spam in the
cheapest way possible.  I think their modifications would be compliant
if they the were done by a host that legitimately answers the IP address
to which the SMTP sender thinks it is connection.  As it stands, how
can these redirectors comply with the postmaster mailbox requirement?
Assuming you figure out what's been done to your SMTP stream, how would
you contact postmaster at the stealthy redirector/filter.

I think it's certifiably crazy to assume that all TCP connections to a
distant port 25 involve SMTP.  Assigned numbers doesn't say you can run
only SMTP on port 25.

It's even crazier to not consider the inevitable next step, stealth SMTP
and HTTP redirector/filters to deal with dirty words or taboo subjects,
and not just sex but politics.

And that's based on the best possible, content-neutral interpretation of
Mr. Levitt's words "filter spam."   I hope AOL would not look for telltale
spam keywords and only do connection rate limiting, if only because I hope
AOL knows that reports of spam would trigger content filters.  I'm even
less confident about other outfits.  

Think about port 25 redirecting used for other kinds of filtering
at certain national borders.

On the other hand, if this doesn't get IPSEC as well as application
layer encryption going, nothing will.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Fri Apr  7 16:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA18134
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 16:50:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16073;
	Fri, 7 Apr 2000 15:21:28 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA01966;
        Fri, 7 Apr 2000 15:21:00 -0400 (EDT)
Message-Id: <200004071921.PAA01966@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Stephen Kent <kent@bbn.com>
cc: Keith Moore <moore@cs.utk.edu>, Leslie Daigle <leslie@thinkingcat.com>,
        iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Fri, 07 Apr 2000 14:59:31 EDT."
             <v0422080db513e04c1250@[171.78.30.107]> 
Date: Fri, 07 Apr 2000 15:21:00 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> >perhaps the reason that the tools are not used is that they are not
> >adequate for the task.  but it certainly does not follow that "if
> >one doesn't use the tools, then one does not care very much".
> 
> or perhaps, one does not care enough ...

or perhaps, that building tools that actually solve these problems
as opposed to chipping away at the edges is (a) fundamentally difficult
(b) requires many kinds of expertise, most of them scarce, (c) has 
been frustrated by governments and patent holders who were bent 
on trying to control things, and (d) has not kept pace with the
development of the 'net.

Keith



From owner-ietf-outbound  Fri Apr  7 17:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA18312
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 17:00:03 -0400 (EDT)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16157;
	Fri, 7 Apr 2000 15:27:01 -0400 (EDT)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id PAA01451;
	Fri, 7 Apr 2000 15:26:49 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v0422080eb513e58b4dcc@[171.78.30.107]>
In-Reply-To: <200004071912.MAA25306@baboon.aciri.org>
References: <200004071912.MAA25306@baboon.aciri.org>
Date: Fri, 7 Apr 2000 15:21:24 -0400
To: Paul Francis <pfrancis@aciri.org>
From: Stephen Kent <kent@bbn.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Cc: leslie@thinkingcat.com, iesg@ietf.org, ietf@ietf.org, moore@cs.utk.edu,
        rfc-ed@rfc-editor.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Paul,


>I have a time machine.
>
>I just went back 20 years in time, convinced everybody that it
>was always more important to implement proper security than to
>make do with existing features and quick fix solutions.  Having
>thus changed the future, I went back forward in time.
>Guess what---there was no internet!

You need a better time machine, or you need to stop complaining. 
either will work for me.

Steve



From owner-ietf-outbound  Fri Apr  7 17:10:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA18567
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 17:10:03 -0400 (EDT)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16176;
	Fri, 7 Apr 2000 15:27:03 -0400 (EDT)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id PAA01483;
	Fri, 7 Apr 2000 15:26:56 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v0422080fb513e5cd5d81@[171.78.30.107]>
In-Reply-To: <BB61526CDE70D2119D0F00805FBECA2F13D9B412@RED-MSG-55>
References: <BB61526CDE70D2119D0F00805FBECA2F13D9B412@RED-MSG-55>
Date: Fri, 7 Apr 2000 15:23:23 -0400
To: Christian Huitema <huitema@microsoft.com>
From: Stephen Kent <kent@bbn.com>
Subject: RE: recommendation against publication of draft-cerpa-necp-02.txt
Cc: Leslie Daigle <leslie@thinkingcat.com>, Keith Moore <moore@cs.utk.edu>,
        iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

  Christian,

>Suppose, rhetorically, that we were to encrypt every IP packet using IPSEC.
>What happens if a box takes your packet and deliver it to the "wrong"
>address, for example to an ISP controlled cache? Well, the cache cannot do
>anything with it, except drop it to the floor. We are thus faced with a
>dilemma: not use IPSEC because it breaks the ISP provided "enhancement," or

If it delivered to the "wrong" address then the security technology 
will have done its job, the user will become aware of the problems, 
and the ISP will have been prevented from doing, in an undetectable 
way, what folks were complaining about. sounds like success to me.

Steve



From owner-ietf-outbound  Fri Apr  7 17:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA18770
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 17:20:03 -0400 (EDT)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16664;
	Fri, 7 Apr 2000 15:46:45 -0400 (EDT)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id PAA04268;
	Fri, 7 Apr 2000 15:46:44 -0400 (EDT)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v04220810b513e9563213@[171.78.30.107]>
In-Reply-To: <200004071921.PAA01966@astro.cs.utk.edu>
References: <200004071921.PAA01966@astro.cs.utk.edu>
Date: Fri, 7 Apr 2000 15:38:34 -0400
To: Keith Moore <moore@cs.utk.edu>
From: Stephen Kent <kent@bbn.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Cc: Keith Moore <moore@cs.utk.edu>, Leslie Daigle <leslie@thinkingcat.com>,
        iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Keith,
>
>or perhaps, that building tools that actually solve these problems
>as opposed to chipping away at the edges is (a) fundamentally difficult
>(b) requires many kinds of expertise, most of them scarce, (c) has
>been frustrated by governments and patent holders who were bent
>on trying to control things, and (d) has not kept pace with the
>development of the 'net.


OK, I'll call it quits now, before we begin to explore who has 
contributed to addressing these problems in any visible fashion, and 
what the relative levels of security expertise are among the folks 
sending these messages.

Steve



From owner-ietf-outbound  Fri Apr  7 17:30:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA19326
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 17:30:04 -0400 (EDT)
Received: from tsx-prime.MIT.EDU (TSX-PRIME.MIT.EDU [18.86.0.76])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA17433
	for <ietf@ietf.org>; Fri, 7 Apr 2000 16:21:31 -0400 (EDT)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id QAA13809; Fri, 7 Apr 2000 16:21:22 -0400
Date: Fri, 7 Apr 2000 16:21:22 -0400
Message-Id: <200004072021.QAA13809@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Daniel Senie <dts@senie.com>
CC: Dennis Glatting <dennis.glatting@SOFTWARE-MUNITIONS.COM>, ietf@ietf.org
In-reply-to: Daniel Senie's message of Fri, 07 Apr 2000 15:00:22 -0400,
	<38EE3046.3E7AFC73@senie.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   Date: Fri, 07 Apr 2000 15:00:22 -0400
   From: Daniel Senie <dts@senie.com>

   Ah, no. In the real world of the Internet today, we have LOTS of folks
   who get their Internet connectivity via cable modems and DSL. Many
   vendors of such services, in order to help preserve IP address space,
   give out only a single IP address to each customer. Since this is
   incompatible with the way people use the Internet in many cases (e.g.
   MANY homes have more than one computer), Network Address Translation is
   used.

   NAT is the reality of the Internet today. IPSec was developed for an
   Internet that existed some years back, before address allocation
   policies forced NAT to become commonplace. We now are in need of
   security solutions which can survive such an environment. SSL is one
   such example.

   NAT presents a lot of problems to the Internet architecture. It's ugly
   architecturally. We all know that. We can't make it go away by
   complaining about it. We could fix IPSec to survive in the current
   environment, or find ways to get more people interested in IPv6, do
   both, or find alternate forms of security.

Actually, there are other solutions to this problem --- in fact, one in
which IPSEC plays a starring role.  I've been hearing more and more
people who are using IPSEC to tunnel from their cable modem to some site
which has (a) plenty of addresses, and (b) is well connected to the
internet.  They can thus get a /28, /27, or sometimes even a /24 block
of addresses, even though their cable modem or DSL provider either won't
provide that service, or would force the customer to pay through the
nose for the block of the addresses.  One advantage of using IPSEC to
solve this problem is that the ISP can't peer inside the packets to
figure out this is what's going on, so won't know that the customer is
using mutliple computers through what they thought was the single
computer rate.

The downside is that your packets may take a longer than normal routing
to get to their destination, but that's happening already even without
this hack.  For example, until I changed my DSL provider out of sheer
disgust and appallingly bad service, my packets from my home in Medford,
Massachusetts, to MIT in Cambridge, Massachusetts were going by way of
Washington, D.C. and MAE-East.

							- Ted



From owner-ietf-outbound  Fri Apr  7 17:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA19610
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 17:40:03 -0400 (EDT)
Received: from mail5.microsoft.com (mail5.microsoft.com [131.107.3.121])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA17538
	for <ietf@ietf.org>; Fri, 7 Apr 2000 16:26:29 -0400 (EDT)
Received: from 157.54.9.108 by mail5.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 07 Apr 2000 12:08:33 -0700 (Pacific Daylight Time)
Received: by INET-IMC-05 with Internet Mail Service (5.5.2651.58)
	id <2LBGBN7V>; Fri, 7 Apr 2000 12:08:33 -0700
Message-ID: <BB61526CDE70D2119D0F00805FBECA2F13D9B412@RED-MSG-55>
From: Christian Huitema <huitema@microsoft.com>
To: "'Stephen Kent'" <kent@bbn.com>, Leslie Daigle <leslie@thinkingcat.com>
Cc: Keith Moore <moore@cs.utk.edu>, iesg@ietf.org, ietf@ietf.org,
        rfc-ed@rfc-editor.org
Subject: RE: recommendation against publication of draft-cerpa-necp-02.txt
Date: Fri, 7 Apr 2000 12:08:32 -0700 
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

Steve,

Suppose, rhetorically, that we were to encrypt every IP packet using IPSEC.
What happens if a box takes your packet and deliver it to the "wrong"
address, for example to an ISP controlled cache? Well, the cache cannot do
anything with it, except drop it to the floor. We are thus faced with a
dilemma: not use IPSEC because it breaks the ISP provided "enhancement," or
tell the ISP to stop this denial of service attack.

> -----Original Message-----
> From: Stephen Kent [mailto:kent@bbn.com]
> Sent: Friday, April 07, 2000 10:07 AM
> To: Leslie Daigle
> Cc: Keith Moore; iesg@ietf.org; ietf@ietf.org; rfc-ed@rfc-editor.org
> Subject: Re: recommendation against publication of
> draft-cerpa-necp-02.txt
> 
> 
> Leslie,
> 
> I understand your point, but we leave ourselves open to many forms of 
> attacks, or errors, by assuming that "what you receive is what was 
> sent" in this era of the Internet.  Security is not black and white, 
> but the gray area we're discussing does bother me.  If one cares 
> about knowing where the data originated, and that it has not been 
> altered, then one needs to make use of the tools provided to address 
> that concern.  if one doesn't use the tools, then one does not care 
> very much, and the results may be surprising :-).
> 
> Steve
> 



From owner-ietf-outbound  Fri Apr  7 18:10:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA20165
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 18:10:03 -0400 (EDT)
Received: from tsx-prime.MIT.EDU (TSX-PRIME.MIT.EDU [18.86.0.76])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA18474;
	Fri, 7 Apr 2000 17:07:38 -0400 (EDT)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id RAA13819; Fri, 7 Apr 2000 17:07:23 -0400
Date: Fri, 7 Apr 2000 17:07:23 -0400
Message-Id: <200004072107.RAA13819@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Keith Moore <moore@cs.utk.edu>
CC: pdeutsch@cisco.com, Keith Moore <moore@cs.utk.edu>, karl@CAVEBEAR.COM,
        iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
In-reply-to: Keith Moore's message of Fri, 07 Apr 2000 15:15:57 -0400,
	<200004071915.PAA01895@astro.cs.utk.edu>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   From: Keith Moore <moore@cs.utk.edu>
   Date: Fri, 07 Apr 2000 15:15:57 -0400

   the problem is that one person's idea of improved service may be
   another person's idea of degraded service.  getting stale data
   to me faster may not be much help.  I would argue that it
   is up to the producer and consumer, not the ISP, to decide what
   level of service is appropriate.

Speaking of which, in Adelaide, at the IETF terminal room, there were
http "transparent" proxies running.  It turns out that if you bypassed
them, you got faster service than if you used the transparent proxy
servers provided expressly for the IETF terminal room.

I'm told it saved 15% of the overall bandwidth consumed by the IETF, and
given the limited bandwidth in and out of Australia, I'm somewhat
sympathetic to why it was installed.  However, it's still much more
polite ask people to use a proxy server than to just try to sneak in a
"transparent" proxy.

If they had asked nicely, I might have decided to use it.  As it was, I
was annoyed enough to simply bypass the proxy server, and gain for
myself faster web access.

						- Ted



From owner-ietf-outbound  Fri Apr  7 18:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA20285
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 18:20:03 -0400 (EDT)
Received: from orchard.arlington.ma.us (sommerfeld.ne.mediaone.net [24.147.212.81])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19676;
	Fri, 7 Apr 2000 17:42:24 -0400 (EDT)
Received: from thunk.hamachi.org (orchard.hamachi.org [4.255.0.98])
	by  orchard.arlington.ma.us (8.8.8/8.8.8) with ESMTP id RAA25506;
	Fri, 7 Apr 2000 17:42:22 -0400 (EDT)
Received: from thunk.hamachi.org (localhost [[UNIX: localhost]])
	by thunk.hamachi.org (8.9.3/8.8.8) with ESMTP id PAA11236;
	Fri, 7 Apr 2000 15:20:57 -0400 (EDT)
Message-Id: <200004071920.PAA11236@thunk.hamachi.org>
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: Keith Moore <moore@cs.utk.edu>
cc: karl@CAVEBEAR.COM, iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org,
        cerpa@usc.edu, jelson@usc.edu
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-Reply-To: Message from Peter Deutsch <pdeutsch@cisco.com> 
   of "Fri, 07 Apr 2000 10:42:15 PDT." <38EE1DF7.87FE780D@cisco.com> 
Date: Fri, 07 Apr 2000 15:20:56 -0400
Sender: wes@orchard.arlington.ma.us
X-Loop: ietf@ietf.org

The objections I've seen so far to this draft specifically cite
problems from systems such as "transparent web proxies" (which are, in
my experience, usually far from transparent) in the network which
intercept all traffic, regardless of destination address, sent to
specific well-known ports.

A quick read through draft-cerpa-necp-02.txt suggests that it's
primarily targeted at forms of redirection which occur at the request
of service operators.  Such systems are best thought of as a funny
kind of application-layer proxy, and are far less damaging to the
end-to-end internet model than the transparent proxies cited above.

I think it's important to carefully distinguish between these sorts of
redirection.  Some clarifying text in the draft to this effect would
be helpful.

					- Bill



From owner-ietf-outbound  Fri Apr  7 20:40:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA21672
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 20:40:03 -0400 (EDT)
Received: from peridot.cisco.com (peridot.cisco.com [171.69.198.64])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21527;
	Fri, 7 Apr 2000 20:30:50 -0400 (EDT)
Received: from cisco.com (dhcp-171-69-44-215.cisco.com [171.69.44.215])
	by peridot.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id RAA15946;
	Fri, 7 Apr 2000 17:30:17 -0700 (PDT)
Message-ID: <38EE7D4D.8F4457DD@cisco.com>
Date: Fri, 07 Apr 2000 17:29:01 -0700
From: Peter Deutsch <pdeutsch@cisco.com>
Reply-To: pdeutsch@cisco.com
Organization: Cisco Systems
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
CC: Keith Moore <moore@CS.UTK.EDU>, karl@CAVEBEAR.COM, iesg@ietf.org,
        ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-0
References: <PPECLLOGBEPHLOMKLNAMGEGOCAAA.Michael.CTR.Bellopede@tc.faa.gov>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

g'day,

"Michael B. Bellopede" wrote:
...
> Regardless of what occurs at higher layers, there is still the problem of
> changing the source address in an IP packet which occurs at the network(IP)
> layer.

The Content Services Business Unit of Cisco (Fair Disclosure time -
that's my employer  and my business unit) sells a product called
"Local Director". LD is intended to sit in front of a cluster of
cache engines containing similar data, performing automatic
distribution of incoming requests among the multiple caches. It does
this by intercepting the incoming IP packets intended for a specific
IP address and multiplexing it among the caches. Are we doing
something illegal or immoral here? No, we're offering hot spare
capability, load balancing, increased performance, and so on. The
net is a better place than it was a few years ago, when a web page
would contain a list of links and an invitation to "please select
the closest server to you".

We also have a product called "Distributed Director", which is
essentially a DNS server appliance which can receive incoming DNS
requests (e.g for "www.cnn.com") and reroute it to one or more cache
farms for distributed load balancing. If intercepting IP addresses
is evil, then presumably intercepting DNS requests is more evil,
since it's higher up the IP stack? No, it's a legitimate tool for
designing massive Content Service Networks of the scale needed in
the coming years.

Can a combination of DD and LD be misused? Sure, but I hope you're
not suggesting that we should be cancelling these products because
somebody might misuse them? There are all kinds of technologies
which can be used or abused. Banning discussion of such technologies
based upon an individual's sense of what is a moral or legal use of
that technology (when the individual doesn't justify this through
any particular creditials in either morality or the law) strikes me
as somewhat naive, to say the least...

					- peterd


-- 
----------------------------------------------------------------------
Peter Deutsch                     work email:  pdeutsch@cisco.com
Technical Leader
Content Services Business Unit       private: 
pdeutsch@earthlink.net
Cisco Systems                           or  :  peterd@the.web

         Alcohol and calculus don't mix. Never drink and derive.
----------------------------------------------------------------------



From owner-ietf-outbound  Fri Apr  7 20:50:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA21862
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 20:50:44 -0400 (EDT)
Received: from peridot.cisco.com (peridot.cisco.com [171.69.198.64])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21728;
	Fri, 7 Apr 2000 20:43:17 -0400 (EDT)
Received: from cisco.com (dhcp-171-69-44-215.cisco.com [171.69.44.215])
	by peridot.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id RAA17031;
	Fri, 7 Apr 2000 17:42:45 -0700 (PDT)
Message-ID: <38EE803A.4988D478@cisco.com>
Date: Fri, 07 Apr 2000 17:41:30 -0700
From: Peter Deutsch <pdeutsch@cisco.com>
Reply-To: pdeutsch@cisco.com
Organization: Cisco Systems
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: karl@CAVEBEAR.COM, iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <200004071915.PAA01895@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Keith Moore wrote:
.  .  .
> You seem to be saying that because we have a higher service layered
> on top of IP that we can disregard the IP service model.  I disagree.

No, I'm saying you purported to be offended by IP address
redirection when what you really objected to was unauthorized
spoofing of services and the delivery of something other than what
the user and/or information provider would have expected. That in
turn resulted in your calling for a ban on publication of a
technical document describing a technique which you admit has quite
legitimate applications (e.g. when CNN knows that such IP
interception is going on) because it *could* be used in a manner you
judge to be immoral (i.e. in a case when neither client nor server
knew).


> There are two separate problems here:
> 
> 1. An interception proxy, unless it is acting with authorization
> of the content provider, is misrepresenting itself as the content
> provider.  IP address spoofing as just one particular mechanism
> by which this can be done, but regardless of the mechanism, it's
> wrong to misrepresent yourself as someone else.

So write an RFC Draft and call it "IP Address Spoofing Considered
Harmful". Argue eloquently. Convince everyone and you will be famous
to generations of students to come as the person who saved us from
this pernicious practice, right up there with Djkstra and GOTOs.
Fight ideas with ideas. But banning mention of the technique because
it can be misused? Puuleeze.



> 2. At a different level, IP networks that don't behave like IP
> networks are supposed to behave violate the assumptions on which
> higher level protocols are based.  This degrades interoperability
> and increases the complexity of higher level protocols as they
> try to work around the damage done when clean layering is destroyed.
> (for example of increased complexity consider the suggestions to
> solve the problem by having everyone use IPsec or TLS)

You know, I've been pretty uncomfortable over the past few years at
what I perceive as a growing hostility in some quarters towards
innovation in the name of purity and stability. I agree the Internet
is "important", and we must consider the consequences of our
actions, but personally I think you've gone way over a line here...


> (as a friend of mine said many years ago, the problem with intelligent
> networks is that the network has to be smarter than the applications.)
> 
> now it happens that both of these problems are caused by interception
> proxies, which is why I choose to mention both of them in the same
> discussion.

Actually, you mistyped "both problems are caused by the *misuse* of
interception proxies". And you advocate that the IETF prevent
discussion of the very technique because it can be misused. The bad
guys have proved pretty adept at misusing whatever technologies we
create, but the fact that search engines *can* be misused to leak
information wouldn't have been a reason to ban discussion of Archie
10 years ago, and the fact that the Web can carry porn wasn't a
reason to ban the publishing of an RFC on HTTP five years ago. The
final line of the argument is left as an exercise for the reader...

We need to build publishing and distribution services that can scale
to millions, if not billions, of users, and we need them now.
Address interception is a perfectly legitimate technique in our
arsenal of ideas for this task, with some dangers. So document the
dangers, but if you seek to ban the ideas themselves, I will tap my
head, stick out my tongue and speak in a terrible French accent in
your general direction.



> > Bottom line is, you seem pretty confused here.
> 
> only if you think that discussing several related topics in a single
> mail message is a sign of confusion.

Sorry, you're not convincing me you understand my point. You
acknowledge that it's okay to intercept if CNN knows you're doing
it. So why don't we document how to do that? Oh, you say - that's
because the idea can be misused. "Let these dangerous kooks publish
their innovations elsewhere, so we don't sully the IETF brand".
Fine, if we do that, I guarantee that new ideas will simply migrate
out of this forum. Be careful what you ask for, as you're liable to
get it...


> > > 2. an internet service provider which deliberately forges IP datagrams
> > > using the source address of a content provider, to make it appear
> > > that the traffic was originated by that content provider
> > > (interception proxies do this), may be misrepresenting that content
> > > provider by implicitly claiming that the service conveyed to the user
> > > by the ISP is the one provided by the content provider.
> >
> > Keith, this is a legal issue. We don't do legal issues here.
> 
> that's BS.  IETF has every reason to be concerned about publishing
> documents that promote illegal or clearly immoral behavior.  While it
> is true that it is not for us to judge fine points of law, it's also
> true that promoting illegal or clearly immoral behavior reflects poorly
> on IETF as an institution and would impair IETF's ability to do its work.
> It is not useful to direct IETF's energies in these directions.

If we're going to be foul-mouthed about it, then to quote Saturday
Night Live - 
"Jane, you ignorant slut".

Publishing of a technical document is not promoting "illegal or
clearly immoral behaviour", any more than publishing instructions on
driving a car is promoting carjacking. *That's* the conflation of
ideas I charged you with, not simply carrying two ideas in a single
posting.


> The alternative  - to pretend that there are no social implications
> to what we are doing in IETF - strikes me as dangerous and irresponsible.
> 
> > So because someone can pick up a router and beat someone to death
> > with it, we shouldn't build routers?
> 
> no, if someone designed a router whose primary purpose were to beat
> someone to death, we shouldn't endorse such a product.

Okay, I'll see your moral indignation and raise you a moral outrage.
Since when is the publishing of technical information for the
education of the IETF community endorsement of anything other than
the free exchange of ideas? Frankly *I'm* morally offended at that
notion as I think it strikes at the very heart of the IETF and what
made it a successfully organization worthy of my support. If this
were to become the way this organization actually does work in the
future, I would predict its speedy demise as a useful place for the
free interchange of ideas.
 
.  .  .
> > So you are arguing for explicit censorship of ideas based upon your
> > own moral assessment of the potential misuse of those ideas? Wow.
> > Now *that* is a dangerous notion indeed. I sincerely hope it is not
> > a widely held one within the echelons of the IETF...
> 
> Your use of the word "censorship" is incorrect.  I'm not arguing that
> IETF should try to prevent anybody from publishing their own ideas
> in any forum willing to support them.  Instead I'm arguing that IETF
> and the RFC Editor should not serve as that forum.

Fortunately, I don't think your view really reflects the spirit of
the majority, but I will say again I find it dangerous and offensive
in the extreme. You are advocating that the IETF censor ideas, for
what you claim are the best of reasons. Frankly, I think you value
the IETF brand too much, and the free exchange of ideas too little.

.  .  .
> And absolutely I am making an argument based on my own assessment of
> both the morality of the practice and the technical issues associated
> with that practice.  Why should it be dangerous or wrong to argue for
> what one believes is right?

Because nobody died and made you king and TWIAVBP. I'm offended at
the notion that a former Area Director of the IETF would advocate
censoring what others can publish in the Internet's premier
technical exchange forum based not on the quality of the technical
information, but on how that information may be misused. Heck, I'm
also offended that you've dropped the 'the" in front of the term
"the IETF", as it always makes me think of the old "Royal We" that
the Queen of England allegedly uses and I don't want to be thinking
of the Queen of England every time I read one of your postings. Why
can't I demand the IETF forbid any mail posted from you without the
leading "the"?

Okay, it's Friday and I'm being silly, but the underlying concept
here is most definitely censorship of ideas in a most pernicious
form. It's the censorship of ideas based upon how those ideas may be
misused. That always the first step justification used by those who
would protect us from ourselves. Shame on you...


					- peterd



-- 
----------------------------------------------------------------------
Peter Deutsch                     work email:  pdeutsch@cisco.com
Technical Leader
Content Services Business Unit       private: 
pdeutsch@earthlink.net
Cisco Systems                           or  :  peterd@the.web

         Alcohol and calculus don't mix. Never drink and derive.
----------------------------------------------------------------------



From owner-ietf-outbound  Fri Apr  7 21:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA21960
	for ietf-outbound.10@ietf.org; Fri, 7 Apr 2000 21:00:04 -0400 (EDT)
Received: from mail1.microsoft.com (mail1.microsoft.com [131.107.3.125])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA21889
	for <ietf@ietf.org>; Fri, 7 Apr 2000 20:51:22 -0400 (EDT)
Received: from 157.54.9.101 by mail1.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 07 Apr 2000 17:50:19 -0700 (Pacific Daylight Time)
Received: by INET-IMC-01 with Internet Mail Service (5.5.2651.58)
	id <2LZS7DJT>; Fri, 7 Apr 2000 17:50:18 -0700
Message-ID: <D5922CA42F8CD31189D800805F19A16C04B7B011@RED-MSG-48>
From: Ian King <iking@microsoft.com>
To: "'Paul Francis'" <pfrancis@aciri.org>, kent@bbn.com,
        leslie@thinkingcat.com
Cc: iesg@ietf.org, ietf@ietf.org, moore@cs.utk.edu, rfc-ed@rfc-editor.org
Subject: RE: recommendation against publication of draft-cerpa-necp-02.txt
Date: Fri, 7 Apr 2000 17:50:17 -0700 
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

I have a hammer.  

It's been driving nails just fine for twenty years.  It's a first rate
hammer, for which I paid top dollar.  It's a really useful tool.  But when I
try to open beer bottles with it, I end up with glass splinters in my beer.
What gives?  

As has been pointed out many times in many ways, the Internet was not
originally designed as a secure network, nor for many of the other tasks we
now wish it to perform.  Should we have implemented something in another
way?  Moot question, we have what we have.  Should we learn from our
mistakes, and when we can see something that appears to be yet another
mistake (no matter how appealing it is as a "quick fix"), avoid making that
mistake?  

We clever, clever engineers have come up with a number of interesting
"solutions" (workarounds?) for the limitations of the network we have
created.  Some of them are, in the long run, not good ideas, although they
are useful as interim solutions.  Some of them are just too violent to the
rules of the game as they are defined (by us!), and/or establish technical
or process precedents that are too dangerous to be allowed.  

-- Ian King

-----Original Message-----
From: Paul Francis [mailto:pfrancis@aciri.org]
Sent: Friday, April 07, 2000 12:13 PM
To: kent@bbn.com; leslie@thinkingcat.com
Cc: iesg@ietf.org; ietf@ietf.org; moore@cs.utk.edu;
rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of
draft-cerpa-necp-02.txt


>  
>  In my 20+ years of security experience in the Internet community, it 
>  has often been the arguments for the need to make do with existing 
>  features or to adopt quick fix solutions that have retarded the 
>  deployment of better security technology.  In retrospect, this 
>  approach has not served us well.
>  

I have a time machine.

I just went back 20 years in time, convinced everybody that it
was always more important to implement proper security than to
make do with existing features and quick fix solutions.  Having
thus changed the future, I went back forward in time.
Guess what---there was no internet!

PF



From owner-ietf-outbound  Sat Apr  8 00:44:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA25880
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 00:43:51 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25725;
	Sat, 8 Apr 2000 00:30:38 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id AAA03696;
        Sat, 8 Apr 2000 00:29:46 -0400 (EDT)
Message-Id: <200004080429.AAA03696@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: pdeutsch@cisco.com
cc: Keith Moore <moore@cs.utk.edu>, karl@CAVEBEAR.COM, iesg@ietf.org,
        ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Fri, 07 Apr 2000 17:41:30 PDT."
             <38EE803A.4988D478@cisco.com> 
X-SUBJECT-MSG-FROM: Peter Deutsch <pdeutsch@cisco.com> 
Date: Sat, 08 Apr 2000 00:29:46 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Keith Moore wrote:
> .  .  .
> > You seem to be saying that because we have a higher service layered
> > on top of IP that we can disregard the IP service model.  I disagree.
> 
> No, I'm saying you purported to be offended by IP address
> redirection when what you really objected to was unauthorized
> spoofing of services and the delivery of something other than what
> the user and/or information provider would have expected. 

Actually I have objections to both - though the objections
to the former are purely technical and mostly in response
to folks who claim that such redirection is deserving of
standardization, or in general is anything more than a crude
short-term hack.  The objections to the latter are both moral
and technical.

> That in
> turn resulted in your calling for a ban on publication of a
> technical document describing a technique which you admit has quite
> legitimate applications (e.g. when CNN knows that such IP
> interception is going on) because it *could* be used in a manner you
> judge to be immoral (i.e. in a case when neither client nor server
> knew).

I did not call for a ban on publication of any document.  I suggested
that the RFC Editor consider not devoting its energies to publishing
the document - and I only suggested this after I suggested several
things that could be done to "fix" the document.  Clearly the document 
can be published by other means, nor would I try to prevent such publication.

What you may not realize is that fixing the bugs in documents such
as this one - which at best are on the margin of IETF's mission -
tends to consume inordinate amounts of effort on the part of IESG 
and/or the RFC Editor, who already have lots of work on their plates.  
Their effort, I believe, is better spent on getting more deserving
documents out the door.  

(Such waste of resources is especially annoying when the motivation for 
having the document published appears to be lend IETF's imprimatur 
to an approach by having it published as an RFC - and therefore, 
can be cited as if it were a standard - language in the RFC preamble
to the contrary notwithstanding.)  

> So write an RFC Draft and call it "IP Address Spoofing Considered
> Harmful". Argue eloquently. Convince everyone and you will be famous
> to generations of students to come as the person who saved us from
> this pernicious practice, right up there with Djkstra and GOTOs.
> Fight ideas with ideas. But banning mention of the technique because
> it can be misused? Puuleeze.

again, you're using "ban" incorrectly.

> You know, I've been pretty uncomfortable over the past few years at
> what I perceive as a growing hostility in some quarters towards
> innovation in the name of purity and stability. I agree the Internet
> is "important", and we must consider the consequences of our
> actions, but personally I think you've gone way over a line here...

I do take a hostile attitude toward so-called innovations which impair
the flexibility and reliability of the Internet and Internet applications,
and I make no apology for it.

> > now it happens that both of these problems are caused by interception
> > proxies, which is why I choose to mention both of them in the same
> > discussion.
> 
> Actually, you mistyped "both problems are caused by the *misuse* of
> interception proxies". 

tell that to the marketing departments of companaies who are selling
interception proxies to ISPs and as local web caches.  such applications 
of interception proxies *do* cause harm, and yet most of the companies
selling such products would claim that these are legitimate uses.

> And you advocate that the IETF prevent
> discussion of the very technique because it can be misused. 

nope, not prevent discussion - clearly we are discussing it here -
I'm advocating that IETF not spend resources publishing a biased
description of this technique.

> We need to build publishing and distribution services that can scale
> to millions, if not billions, of users, and we need them now.
> Address interception is a perfectly legitimate technique in our
> arsenal of ideas for this task, with some dangers. 

I will agree that legitimate uses of the technique exist, but given 
the widespred misuse of this technique (there seems to be a great
deal more misuse than appropriate use) "perfectly legitimate" 
seems like an oversimplificatiaon.

> 
> > > Bottom line is, you seem pretty confused here.
> > 
> > only if you think that discussing several related topics in a single
> > mail message is a sign of confusion.
> 
> Sorry, you're not convincing me you understand my point. You
> acknowledge that it's okay to intercept if CNN knows you're doing
> it. 

not quite. I said "if it's okay with CNN".  Knowledge != explicit consent.

> So why don't we document how to do that? Oh, you say - that's
> because the idea can be misused. "Let these dangerous kooks publish
> their innovations elsewhere, so we don't sully the IETF brand".
> Fine, if we do that, I guarantee that new ideas will simply migrate
> out of this forum. Be careful what you ask for, as you're liable to
> get it...

sometimes it's useful if new ideas migrate elsewhere. in certain
circles this is known as the Golgafrinchian Ark B principle.

> Publishing of a technical document is not promoting "illegal or
> clearly immoral behaviour", any more than publishing instructions on
> driving a car is promoting carjacking. 

I would argue that publication of this document, regardless of the 
*intent* in doing so, is likely to have the *effect* of promoting 
illegal and/or immoral behavior.  If the decision is made to publish 
the document in some form, the question becomes one of how to minimize 
this negative effect.

> > The alternative  - to pretend that there are no social implications
> > to what we are doing in IETF - strikes me as dangerous and irresponsible.
> > 
> > > So because someone can pick up a router and beat someone to death
> > > with it, we shouldn't build routers?
> > 
> > no, if someone designed a router whose primary purpose were to beat
> > someone to death, we shouldn't endorse such a product.
> 
> Okay, I'll see your moral indignation and raise you a moral outrage.
> Since when is the publishing of technical information for the
> education of the IETF community endorsement of anything other than
> the free exchange of ideas? 

and those who cite such documents as if they were standards, in order
to mislead their customers - they're also contributing to the free 
exchange of ideas?  

it mystifies me how it's quite legitimate to promote dubious and clearly
harmful technical practices (this is defended as the free exchange of 
ideas) but to suggest that such publication is likely to cause harm and 
to consume precious energies which are better spent elsewhere is not 
part of the free exchange of ideas - it is branded as censorship.
I suppose calling it censorship is also part of the free exhcnage of
ideas, but it's not exactly persuasive.

> Frankly *I'm* morally offended at that
> notion as I think it strikes at the very heart of the IETF and what
> made it a successfully organization worthy of my support. If this
> were to become the way this organization actually does work in the
> future, I would predict its speedy demise as a useful place for the
> free interchange of ideas.

Get over it.  The RFC has been exercising editorial discretion - or if 
you prefer - rejecting ideas for RFCs, for many years now.  

> > And absolutely I am making an argument based on my own assessment of
> > both the morality of the practice and the technical issues associated
> > with that practice.  Why should it be dangerous or wrong to argue for
> > what one believes is right?
> 
> Because nobody died and made you king and TWIAVBP. I'm offended at
> the notion that a former Area Director of the IETF would advocate
> censoring what others can publish in the Internet's premier
> technical exchange forum based not on the quality of the technical
> information, but on how that information may be misused. 

as far as I can tell, you think that my having served on the IESG 
means that I have given up the right to speak out against dangerous 
and harmful practices and against poor uses of the IESG's and RFC
Editor's energies.  

IMHO, that's not merely naive, that's delusional.

Keith



From owner-ietf-outbound  Sat Apr  8 03:01:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA07912
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 03:00:03 -0400 (EDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07865;
	Sat, 8 Apr 2000 02:57:29 -0400 (EDT)
Received: from [192.168.111.25] (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id IAA23309; 
          Sat, 8 Apr 2000 08:57:14 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: paf@nix.swip.net
Message-Id: <p04310102b5141dbadaa8@[192.168.111.25]>
In-Reply-To: <200004071920.PAA11236@thunk.hamachi.org>
References: <200004071920.PAA11236@thunk.hamachi.org>
Date: Sat, 8 Apr 2000 08:58:00 +0930
To: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>,
        Keith Moore <moore@cs.utk.edu>
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Cc: karl@CAVEBEAR.COM, iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org,
        cerpa@usc.edu, jelson@usc.edu
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 15.20 -0400 2000-04-07, Bill Sommerfeld wrote:
>I think it's important to carefully distinguish between these sorts of
>redirection.  Some clarifying text in the draft to this effect would
>be helpful.

That is what I have asked the authors to do.

The problems with "intercepting proxies" are that:

(1) It breaks the model we use for IP transport. I.e. an IP package 
with a specific destination address doesn't reach that destination. 
As Christian says,that means among other things that IPSEC will not 
work.

(2) On application layer (as Peter Deutch talks about) the user 
through the browser want to contact the service according to a 
specific URL given. I.e. the user asks to communicate with that 
service. That is not what is happening -- and this with neither 
client nor server knowing about it or being informed.

As Ted said, if it is the case that an ISP or whatever wants to have 
a web-proxy or proxy/cacheing mechanism for some reasons, then that 
have to be communicated to the users so they understand why it is 
better for them (faster, cheaper, whatever) to use that proxy instead 
of talking with services directly.

I have no problem whatsoever to have proxies being part of the 
web-model, but I am strongly opposing someone in the middle of the 
communication path intercepting and redirecting IP-packages, as the 
client will not communicate with whoever he wanted.

     Patrik



From owner-ietf-outbound  Sat Apr  8 03:11:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA08090
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 03:10:03 -0400 (EDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07923;
	Sat, 8 Apr 2000 03:00:25 -0400 (EDT)
Received: from [192.168.111.25] (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id JAA23373; 
          Sat, 8 Apr 2000 09:00:09 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: paf@nix.swip.net
Message-Id: <p04310103b5141fdc5b11@[192.168.111.25]>
In-Reply-To: <38EE7D4D.8F4457DD@cisco.com>
References: 
 <PPECLLOGBEPHLOMKLNAMGEGOCAAA.Michael.CTR.Bellopede@tc.faa.gov>
 <38EE7D4D.8F4457DD@cisco.com>
Date: Sat, 8 Apr 2000 09:00:58 +0930
To: pdeutsch@cisco.com,
        "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Subject: Re: recommendation against publication of draft-cerpa-necp-0
Cc: Keith Moore <moore@CS.UTK.EDU>, karl@CAVEBEAR.COM, iesg@ietf.org,
        ietf@ietf.org, rfc-ed@rfc-editor.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 17.29 -0700 2000-04-07, Peter Deutsch wrote:
>  LD is intended to sit in front of a cluster of
>cache engines containing similar data, performing automatic
>distribution of incoming requests among the multiple caches. It does
>this by intercepting the incoming IP packets intended for a specific
>IP address and multiplexing it among the caches.

What you are doing is giving a product to the service provider, which 
is the one which owns the services which you load balance between.

In the case of a transparent proxy which is discussed in this thread, 
the interception is done neither by the service provider (i.e. CNN or 
whoever) nor by the customer, and neither of them are informed about 
what is happening.

That is a big difference.

    paf



From owner-ietf-outbound  Sat Apr  8 07:10:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA09516
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 07:10:03 -0400 (EDT)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA09493
	for <ietf@ietf.org>; Sat, 8 Apr 2000 07:09:26 -0400 (EDT)
Received: (qmail 20905 invoked from network); 8 Apr 2000 11:09:25 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 8 Apr 2000 11:09:25 -0000
Received: (qmail 17108 invoked from network); 8 Apr 2000 11:09:23 -0000
Received: from ppp-46-251.lander.es (HELO salva) (195.76.46.251)
  by lince.lander.es with SMTP; 8 Apr 2000 11:09:23 -0000
Message-Id: <3.0.6.32.20000408131554.00879b90@lince.lander.es>
X-Sender: svidal@lince.lander.es
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Sat, 08 Apr 2000 13:15:54 +0200
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
From: Salvador Vidal <svidal@lander.es>
Subject: Re: A thought about patents
Cc: ietf@ietf.org
In-Reply-To: <200004060104.KAA18753@necom830.hpcl.titech.ac.jp>
References: <4.2.2.20000330230917.00c1b760@pop.dial.pipex.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA09493
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Hi folks and all,

At 10:04 06/04/00 JST, Masataka Ohta wrote:

>Online business patents are, at large, ineffective and harmless.
>
>We can have servers outside of US and there is no legislation (even
>under US laws. note that the servers can serve yet another countries)
>to make the servers illegal.
>
>Clients in US may still be a target of a patent, if claims of the
>patents do not cover servers and cover the clients only.
>
>However, virtually no one can control downloading of software from
>the servers to the clients at home.
>
>As the Internet is not a collection of private IP networks connected
>by NAT boxes, ISP has no knowledge nor responsibility on what their
>customers are doing.
>
>It's like copyright, so called, piracy, against which Holywood is
>fighting seemingly in vain.

When some irresponsable companies use copyrights like another marketing mix
element, promoting piracy in promotion and begining agresive campaigns
agains it when everybody use their products, it is very difiicult that
people take seriosly this issue!

It doesn`t not have any sense a system where some people don`t pay
copyrights not because money but to avoid that his friends will call him
idiot!.

With the general crash of protection systems I think that the copyrights
will be mainly driven in indirect way, by charging copyrights royaltties to
hardware products, telephone bills,..., some strong points of indirect way
are:

-It is more just that everibody pay, but is expected that the people that
pay now, pay much less becouse there are more people paying, so that
copyright owners dont use it to get more incomes.

-Telecomunications companies that get big profits thanks to webmasters
work, perhaps will now begin to PAY SOMETHING FOR THEIR WORK!

-Indirect incomes impulse copyrights owners goal of have as much audience
as posible, not limited like now by market ofert demand market decisions,
so in this point is worthy to impulse universal cultural access.
...

The weaks points that I see are:

-If rooyalties are based only on trafic, developers will increse their
efforts on products driven to the mass, usually with poor intelectual
value, so we will promote that Internet becomes a Huge garbage TV, the
products with hight intelectual value has small audience but it is worthy
to promote them.

-Indirect incomes give everybody equal treatment but there must be
exceptions, i.e. third world people, schools,..., to promote universal
access to the culture.

-Some people will think that is injust to pay royalties on their
telecomunications when they use telecominications service just for
cominicating with other people, so the amount that comes from comunications
between people must go to services to the comunity not to copyrights owners.
...

The current Internet culture of take things, transform, or not, them and
publish again, have some profits and bad things, like everything, to put
yourself front of culture and say this is not the way, simple does not work
but also don´t get the profits of this culture, so I think that copyright
concept must evolve from the static form, aplieed to finish works, to a
dinamic one for works in evolution, in order to been able to get the
profits of the current culture:

The intelectual work like a work in comun in evolution, evolution that get
that some products incrise their value and other decrease it, and the
market will do the natural selection of them. 

And to avoid the bad things of this culture: 

Mainly that someone gets incomes thanks to other work without reward.

So I think that copyrights will be mainly indiret and dinamic but require
many ajust in order to realy impulse progress, prosperity and culture.

Salva

******************************************************************
"Where money is the measure of everithing, it will be very dificult that
public matters where driven with justice and life with prosperity" ,
Copyright: Thomas More  ;-)
******************************************************************   



From owner-ietf-outbound  Sat Apr  8 10:00:46 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA10736
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 10:00:03 -0400 (EDT)
Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10702
	for <ietf@ietf.org>; Sat, 8 Apr 2000 09:56:24 -0400 (EDT)
Received: from [24.128.60.221] (h0050e460d16d.ne.mediaone.net [24.128.60.221])
	by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id JAA04385;
	Sat, 8 Apr 2000 09:56:24 -0400 (EDT)
Message-Id: <200004081356.JAA04385@chmls05.mediaone.net>
X-Mailer: Microsoft Outlook Express Macintosh Edition - 4.5 (0410)
Date: Sat, 08 Apr 2000 09:59:37 -0400
Subject: SNMPCONF Working Group Interim Meeting Announcement
From: "Jon Saperia" <saperia@mediaone.net>
To: ietf@ietf.org, snmpconf <snmpconf@snmp.com>
CC: Randy Bush <randy@psg.com>, Bert Wijnen <bwijnen@lucent.com>,
        saperia@mediaone.net
Mime-version: 1.0
X-Priority: 3
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

The SNMPCONF Working group intends to hold an interim meeting to work on all
items currently in our charter:

  - The Best Current Practices Document
  - The Differentiated Services Policy MIB Module
  - The General Policy MIB Module

To better coordinate with other meetings, the location has changed since it
was last discussed at the Adelaide IETF Meeting. Details available at this
time are:

Meeting Dates:
   Wednesday, May 17 9am - 6pm
   Thursday, May 18 9am - 6pm
   Friday, May 19 9am - 3pm

Location:
   (Meeting Site TBD)
   San Francisco or San Jose, CA

Sponsor:
   A sponsor or co-sponsors are desired to host this meeting. A hotel
meeting room is preferred, but corporate facilities would be fine. Please
contact me at saperia@mediaone.net if you can help.



From owner-ietf-outbound  Sat Apr  8 14:20:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA12314
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 14:20:03 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12268
	for <ietf@ietf.org>; Sat, 8 Apr 2000 14:13:57 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id LAA01169
	for <ietf@ietf.org>; Sat, 8 Apr 2000 11:03:58 -0400
Sender: francis@localhost.localdomain
Message-ID: <38EF4A5E.2C57B890@ecal.com>
Date: Sat, 08 Apr 2000 11:03:58 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A thought about patents
References: <200004070042.JAA22858@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Masataka Ohta wrote:

> > Even if it's not true in the general case, a sufficiently expensive lawyer
> > might be able to convince the court that, since the Internet makes location
> > irrelevant, the location of the infringement is irrelevant.
>
> that US patents are applicable even if both servers, clients and network
> inbetween are all located outside of US?

No, not that; but, if the server is outside the US and the client is inside, then
maybe.

--
/=================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.   |
|Chief Scientist |================================================|
|eCal Corp.      |"Where's your sense of adventure?" "Hiding under|
|francis@ecal.com|the bed."                                       |
\=================================================================/





From owner-ietf-outbound  Sat Apr  8 14:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA12465
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 14:30:02 -0400 (EDT)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12349;
	Sat, 8 Apr 2000 14:23:18 -0400 (EDT)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id LAA07391;
	Sat, 8 Apr 2000 11:16:33 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 8 Apr 2000 18:23:11 UT
Received: from porky (porky.ascend.com [192.207.23.83])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id LAA11437;
	Sat, 8 Apr 2000 11:23:10 -0700 (PDT)
Received: from ascend.com by ascend.com
Message-Id: <4.2.2.20000408111551.00b0b510@porky>
X-Sender: mhold@porky
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sat, 08 Apr 2000 11:22:46 -0700
To: Keith Moore <moore@cs.utk.edu>
From: Matt Holdrege <holdrege@lucent.com>
Subject: Re: recommendation against publication of
  draft-cerpa-necp-02.txt 
Cc: rfc-ed@rfc-editor.org, iesg@ietf.org, ietf@ietf.org
In-Reply-To: <200004071431.KAA00707@astro.cs.utk.edu>
References: <Your message of "Fri, 07 Apr 2000 01:05:14 PDT." <002501bfa068$01d432b0$428939cc@ntdev.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 10:31 AM 4/7/00 -0400, Keith Moore wrote:
> > As we have done with the NAT WG, it is
> > often useful to accurately document the drawbacks of a
> > common practice as well as to encourage exploration of
> > alternatives.
>
> From my point of view there were significant forces within the
>NAT group attempting to keep the extent of these drawbacks from
>being accurately documented and to mislead the readers of those
>documents into thinking that NATs worked better than they do -
>for instance, the repeated assertions that NATs are "transparent".
>So I'm not sure that this is a good model on which to base future work.

I hate to extend this long thread, but since aspersions were cast...

There were no forces in NAT attempting to mislead readers. There were 
disagreements on terminology. Extensive review fixed these terminology 
issues. Perhaps as others have said draft-cerpa-necp-02.txt suffers a bit 
from misunderstandings and will benefit now from the IETF review.

Matt - NAT WG co-chair



From owner-ietf-outbound  Sat Apr  8 14:54:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA12862
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 14:53:47 -0400 (EDT)
Received: from avocet.prod.itd.earthlink.net (avocet.prod.itd.earthlink.net [207.217.121.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12710;
	Sat, 8 Apr 2000 14:41:03 -0400 (EDT)
Received: from earthlink.net (pool0560.cvx7-bradley.dialup.earthlink.net [209.178.166.50])
	by avocet.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id LAA26351;
	Sat, 8 Apr 2000 11:40:46 -0700 (PDT)
Message-ID: <38EEAA69.9673426@earthlink.net>
Date: Fri, 07 Apr 2000 23:41:30 -0400
From: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
X-Mailer: Mozilla 4.08 [en] (Win95; I)
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>, karl@CAVEBEAR.COM, iesg@ietf.org,
        ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

g'day,

Keith Moore wrote:
> .  .  . I did not call for a ban on publication of any document.  I
suggested
> that the RFC Editor consider not devoting its energies to publishing
> the document - and I only suggested this after I suggested several
> things that could be done to "fix" the document.  Clearly the document

> can be published by other means, nor would I try to prevent such
publication.


Okay, I'll be a little more pedantic - you called for a ban on
publishing this document within the IETF. If it makes you feel better,
load up my previous post in vi and:

     s/document/document within the IETF/

I still object to your notion that it's not censorship since people can
always go elsewhere. Where does this lead? I see the day when people
can't publish a new  directory service protocol because "The IETF has
endorsed LDAP for directory services", or would ban the publication of
an extension to DNS because "it must prevent the misuse of the protocol
in creating inappropriate services". One by one, you'd be chasing
innovation to other foums.

"Danger, Will Robinson! Danger!"


.  .  .
> (Such waste of resources is especially annoying when the motivation
for
> having the document published appears to be lend IETF's imprimatur
> to an approach by having it published as an RFC - and therefore,
> can be cited as if it were a standard - language in the RFC preamble2
> to the contrary notwithstanding.


Hmmm I've read through the Draft again and I can't see the paragraph
which says that the motivation for publishing it is to lend the IETF's
imprimatur to the approach; I must have missed it. Or perhaps you have
first-hand knowledge of the motivations of the authors that you'd care
to share with us?

In any event, without attempting to speak for the authors, most of whom
work for competitors and all of whom I assume are quite capable of
speaking for themselves, I would add that since joining Cisco I've
already heard several conversations of the form "well, the IETF  isn't
the place to take this kind of work anymore. We'll probably develop it
outside and then just work with the industry to standardize it, and look
at whether it's worth taking to the IETF later if the climate changes".

Note, nobody talks in terms of getting something "blessed by the IETF",
but in terms of how the IETF would slow the work down and get in the way
so shouldn't be a part of the process.

If you can't see the long term danger for the IETF in such an attitude
taking root, then you're missing the entire point of my argument. You
can block dissemination of ideas you disagree with and cast aspersions
upon the motivations of participants if you must, but I feel obligated
to point out that I for one think you have crossed a line here and are
harming the IETF. Remember, the net regards censorship as failure and
routes around it....


> > So write an RFC Draft and call it "IP Address Spoofing Considered
> > Harmful". Argue eloquently. Convince everyone and you will be famous

> > to generations of students to come as the person who saved us from
> > this pernicious practice, right up there with Djkstra and GOTOs.
> > Fight ideas with ideas. But banning mention of the technique because

> > it can be misused? Puuleeze.
>
> again, you're using "ban" incorrectly.

Again, I assumed it was obvious that I was speaking within the IETF
context. So please apply:

      s/technique/technique within the IETF/

.  .  .
> I do take a hostile attitude toward so-called innovations which impair

> the flexibility and reliability of the Internet and Internet
applications,
> and I make no apology for it.

When we started running Archie it quickly filled the pipe to our
university (50 percent of all traffic to Montreal at one point was going
to the Archie machine). By your argument we should have shut it down and
banned discussion about automated data gathering and distributed search
engines as clearly we were impairing the "flexibilty and reliability of
the Internet".

Instead, we were prompted to develop new techniques to make good the
problems that the innovation was causing. We worked with other sites to
set up mirror servers, we developed data flooding algorithms, etc. Today
such techniques are regarded as important parts of the infrastructure
and more importantly the innovation showed the way to whole new classes
of Internet use. I'm not trying to beat our drum here, but point out
that I heard many of your arguments back then from conservative
Computing Centre types who felt we were dangerous and yes, evil. Hearing
it all again now from a former IETF Area Director is pretty sad.

In the climate you seem to want to create, we probably would never have
gone to the IETF to meet collaborators or used it as an exchange point
for ideas. We used to say that the most important part of the meetings
were the corridor talks and beer BOFs but you'd ensure that, in
reviewing the drafts and RFCs before a meeting today, many Internet
innovators are not going to see anyone working on technologies relevant
to them. I wonder how many people say nowadays "oh, it's just not worth
while going this time..."?

.  .  .
> > We need to build publishing and distribution services that can scale

> > to millions, if not billions, of users, and we need them now.
> > Address interception is a perfectly legitimate technique in our
> > arsenal of ideas for this task, with some dangers.
>
> I will agree that legitimate uses of the technique exist, but given
> the widespred misuse of this technique (there seems to be a great
> deal more misuse than appropriate use) "perfectly legitimate"
> seems like an oversimplificatiaon.

I fail to see the delicate degrees of shading that you draw between
"legitimate" and "perfectly legitimate". Or do you merely want a chance
to accuse me of oversimplification?

Given how much **I* see of legitimate uses of the technique in
commercial settings, I'd suggest that you're horizons are pretty
limited. Maybe you need to get out a bit more. (note, I'm not talking
about the specific protocol in the Draft in question, but the general
technique of IP address interception - TWIAVBP)


> > > > Bottom line is, you seem pretty confused here.
> > >
> > > only if you think that discussing several related topics in a
single
> > > mail message is a sign of confusion.
> >
> > Sorry, you're not convincing me you understand my point. You
> > acknowledge that it's okay to intercept if CNN knows you're doing
> > it.
>
> not quite. I said "if it's okay with CNN".  Knowledge != explicit
consent.

<sigh>

Okay,
            s/knows/gives its explicit consent/


Is this what you did all day as an Area Director? No wonder you claim
you didn't have any time...


> > So why don't we document how to do that? Oh, you say - that's
> > because the idea can be misused. "Let these dangerous kooks publish
> > their innovations elsewhere, so we don't sully the IETF brand".
> > Fine, if we do that, I guarantee that new ideas will simply migrate
> > out of this forum. Be careful what you ask for, as you're liable to
> > get it...
>
> sometimes it's useful if new ideas migrate elsewhere. in certain
> circles this is known as the Golgafrinchian Ark B principle.

Well, look at the list of signatories to the Draft in question. I see
people working for a major research university, and a roster of
significant players in the content services networking industry. Throw
in my own employer (because although as far as I know we don't use the
technology in question, we do use the technique of address interception
in such technologies as WCCP) and you've got an entire industry you'd
like to rule "out of scope" for the IETF. Yeeesh. Wouldn't it be easier
if you just write an RFC letting us all know what is actually considered
suitable family entertainment for this organization? Then the rest of us
could stop wasting your valuable time with undesireable experimentation
and possibly fruitless innovation.


> > Publishing of a technical document is not promoting "illegal or
> > clearly immoral behaviour", any more than publishing instructions on

> > driving a car is promoting carjacking.
>
> I would argue that publication of this document, regardless of the
> *intent* in doing so, is likely to have the *effect* of promoting
> illegal and/or immoral behavior.  If the decision is made to publish
> the document in some form, the question becomes one of how to minimize

> this negative effect.

Other than responding with a Draft of your own, what would you propose?
A letter-writing campaign to Congress? A Department of Commerce ban on
IP address interception, a la the crypto ban? I'm fascinated to see what
you'll come up with next...

.  .  .
> > Frankly *I'm* morally offended at that
> > notion as I think it strikes at the very heart of the IETF and what
> > made it a successfully organization worthy of my support. If this
> > were to become the way this organization actually does work in the
> > future, I would predict its speedy demise as a useful place for the
> > free interchange of ideas.
>
> Get over it.  The RFC has been exercising editorial discretion - or if

> you prefer - rejecting ideas for RFCs, for many years now.

Yes, and those of us who object to this degradation of the original
concept of the IETF probably have some obligation to engage and at least
point out their concern over this trend. So here I am, wasting my
Saturday when I should be doing other things trying to protect an
organization I admire from what I see as a very dangerous trend indeed.

I'd add that your obsessive concern over the purity of the "IETF brand"
actually contributes to the very phenomenon you're citing - by
preventing any but fully formed and suitably blessed publications, you
allow the Marketers to use the annoiting power of an RFC number, since
the IETF itself is guaranteeing the purity of its "product". You've also
increased your own workload to the point where you can use the lack of
time as a justification for chasing away ideas which are not fully
formed and judged to be safe enough to pursue a priori. I see an
interesting feedback loop forming here.

And the real killer is that you're more concerned about what Marketing
types will do with the document than what technologists will do with it.
Wow...

Frankly, I hope we are going to be able to arrest this dangerous trend.
So, I engaged last year when I saw the broadcast industry being run out
of town over the TV: URL draft, and I'm engaging now because I see the
content services networking industry being told they can't play in this
sand box with their dangerous notions of abstracting service requests
from transport.

To me the appropriate reponse when someone sees danger in a technology
is another document, making your case. After all, if the technique is so
dangerous, it's not enough to surpress it at the IETF. We need to hear
why it shouldn't be out there are all. Those of us in positions of
influence could then do something about it. Right now you've certainly
not convinced *me* there should be a ban on such work...

And if we fail to arrest this trend towards self-censorship, at least
we'll have addressed the workload issue for overworked Area Directors,
as all the major inovations and initiatives will have been driven to
outside consortia and the IETF will be able to point out that it had
nothing to do with bringing them to life or addressing their
short-comings. Sounds like a pretty bleak future to me, but as my
daughter would say, "hey, whatever..."


> > . . . I'm offended at
> > the notion that a former Area Director of the IETF would advocate
> > censoring what others can publish in the Internet's premier
> > technical exchange forum based not on the quality of the technical
> > information, but on how that information may be misused.
>
> as far as I can tell, you think that my having served on the IESG
> means that I have given up the right to speak out against dangerous
> and harmful practices and against poor uses of the IESG's and RFC
> Editor's energies.
>
> IMHO, that's not merely naive, that's delusional.

First you would ban technical information because it can be misued
(rather than documenting such misuse to help avoid it). Now you add
name-calling and intimidation to your arsenal. Way to go, Keith.

I think I might go to POISED and propose that we limit name-calling on
IETF lists to within the bounds of quoting appropriate snippets of Monty
Python. You'd be free to publish elsewhere, so it's not censorship, and
we'd be sure not to sully the IETF's reputation for quality of
discourse. At the same time, I'm going to propose that the RFC Editor be
told to insert at the front of each new RFC the words "nil obstatum" (or
whatever the Latin term is), to make clear the role the IETF sees itself
playing here. That should ensure the health and relevance of this
organization for years to come...

(and would a classicist in the crowd who recognizes this rather obscure
reference please give me the actual words, since I expect a flood of
flames and corrections to my egregous misuse of the Latin?
AD-thanks-VANCE...)


                                                                  -
peterd

----------------------------------------------------------------------
Peter Deutsch                     work email:  pdeutsch@cisco.com
Technical Leader
Content Services Business Unit       private:
pdeutsch@earthlink.net
Cisco Systems                           or  :  peterd@the.web

         Alcohol and calculus don't mix. Never drink and derive.
----------------------------------------------------------------------





From owner-ietf-outbound  Sat Apr  8 15:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA12927
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 15:00:03 -0400 (EDT)
Received: from avocet.prod.itd.earthlink.net (avocet.prod.itd.earthlink.net [207.217.121.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12748
	for <ietf@ietf.org>; Sat, 8 Apr 2000 14:44:03 -0400 (EDT)
Received: from earthlink.net (pool0560.cvx7-bradley.dialup.earthlink.net [209.178.166.50])
	by avocet.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id LAA03580;
	Sat, 8 Apr 2000 11:44:02 -0700 (PDT)
Message-ID: <38EEAB2D.7C3032F4@earthlink.net>
Date: Fri, 07 Apr 2000 23:44:45 -0400
From: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
X-Mailer: Mozilla 4.08 [en] (Win95; I)
MIME-Version: 1.0
To: ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Hi Patrik,

Patrik Fältström wrote:
>
> At 17.29 -0700 2000-04-07, Peter Deutsch wrote:
> >  LD is intended to sit in front of a cluster of
> >cache engines containing similar data, performing automatic
> >distribution of incoming requests among the multiple caches. It does
> >this by intercepting the incoming IP packets intended for a specific
> >IP address and multiplexing it among the caches.
>
> What you are doing is giving a product to the service provider, which
> is the one which owns the services which you load balance between.
>
> In the case of a transparent proxy which is discussed in this thread,
> the interception is done neither by the service provider (i.e. CNN or
> whoever) nor by the customer, and neither of them are informed about
> what is happening.
>
> That is a big difference.

I agree, and would welcome a BCP document pointing out this distinction
and explaining why the later is harmful. Banning publication of
technologies a priori (as I argue elsewhere) wont stop the technology
being developed, wont stop the practice and just leads to the IETF
abdicating it role as a meeting point for technical innovation.

     - peterd





From owner-ietf-outbound  Sat Apr  8 15:30:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA13309
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 15:30:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13278;
	Sat, 8 Apr 2000 15:29:01 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA24738;
        Sat, 8 Apr 2000 15:28:12 -0400 (EDT)
Message-Id: <200004081928.PAA24738@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
cc: Keith Moore <moore@cs.utk.edu>, karl@CAVEBEAR.COM, iesg@ietf.org,
        ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Fri, 07 Apr 2000 23:41:30 EDT."
             <38EEAA69.9673426@earthlink.net> 
Date: Sat, 08 Apr 2000 15:28:12 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

Peter,

I think that by now I've made my points and defended them adequately and 
that there is little more to be acheived by continuing a public,
and largely personal, point-by-point argument.  If you want to continue 
this in private mail I'll consider it.

The simple fact is that I believe that the idea of interception proxies 
does not have sufficient technical merit to be published by IETF, and 
that IETF's publication of a document that tends to promote the use 
of such devices would actually be harmful to Internet operation and 
its ability to support applications.  Reasonable people can disagree
about the utility of an idea and I certainly don't expect that my 
notion of the utility of interception proxies will be accepted by everyone.
(especially not folks who are making money by selling these things...)
But I thought it was valuable to try to raise awareness about the issue.

Keith

p.s. I think the term you're looking for is "nihil obstat".



From owner-ietf-outbound  Sat Apr  8 15:40:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA13531
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 15:40:04 -0400 (EDT)
Received: from web1406.mail.yahoo.com (web1406.mail.yahoo.com [128.11.23.170])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA13498
	for <ietf@ietf.org>; Sat, 8 Apr 2000 15:39:47 -0400 (EDT)
Received: (qmail 14255 invoked by uid 60001); 8 Apr 2000 19:39:47 -0000
Message-ID: <20000408193947.14254.qmail@web1406.mail.yahoo.com>
Received: from [38.186.47.9] by web1406.mail.yahoo.com; Sat, 08 Apr 2000 12:39:47 PDT
Date: Sat, 8 Apr 2000 12:39:47 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
To: Keith Moore <moore@cs.utk.edu>, aboba@internaut.com
Cc: "'Keith Moore'" <moore@cs.utk.edu>, rfc-ed@rfc-editor.org, iesg@ietf.org,
        ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

--- Keith Moore <moore@cs.utk.edu> wrote:
<... stuff deleted>
> > As we have done with the NAT WG, it is
> > often useful to accurately document the drawbacks of a
> > common practice as well as to encourage exploration of
> > alternatives.
> 
> From my point of view there were significant forces within the 
> NAT group attempting to keep the extent of these drawbacks from 
> being accurately documented and to mislead the readers of those
> documents into thinking that NATs worked better than they do -
> for instance, the repeated assertions that NATs are "transparent".

Keith - I argued to keep the term "transparent routing" in the 
NAT terminology RFC (RFC 2663). The arguments I put forth were
solely mine and not influenced by my employer or anyone else. 
I donot know who else you are refering to as the "significant 
forces in NAT group attempting to mislead readers into 
thinkining NATs are transparent".
  
Clearly, your point of view is skewed against NATs. It is rather 
hypocritical and unfair to say that those opposed to your view 
point are misleading the readers, while you apparently do not 
purport to mislead.

> So I'm not sure that this is a good model on which to base future work.
> 
NAT WG has made substantial progress in the form of demystifying 
the FUD surrounding NATs. We still have work to do and intend to stay 
focussed to continue presening a balanced view point.

regards,
suresh

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com



From owner-ietf-outbound  Sat Apr  8 16:01:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA13754
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 16:00:04 -0400 (EDT)
Received: from harrier.prod.itd.earthlink.net (harrier.prod.itd.earthlink.net [207.217.121.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13712;
	Sat, 8 Apr 2000 15:59:51 -0400 (EDT)
Received: from earthlink.net (pool0125.cvx7-bradley.dialup.earthlink.net [209.178.164.125])
	by harrier.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id MAA03289;
	Sat, 8 Apr 2000 12:59:46 -0700 (PDT)
Message-ID: <38EEBCED.ACE0FC61@earthlink.net>
Date: Sat, 08 Apr 2000 01:00:29 -0400
From: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
X-Mailer: Mozilla 4.08 [en] (Win95; I)
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: karl@CAVEBEAR.COM, iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <200004081928.PAA24738@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

g'day,

Keith Moore wrote:

> Peter,
>
> I think that by now I've made my points and defended them adequately and
> that there is little more to be acheived by continuing a public,
> and largely personal, point-by-point argument.  If you want to continue
> this in private mail I'll consider it.

Okay, but I'd like to make clear that I don't regard this as a "largely
personal...argument". On the contrary, I've drunk beer with you, I like you as
a person and would be happy to drink beer with you again. I am engaging here
*only* because I think the principles I'm defending are so important. It really
is nothing personal.

>
> The simple fact is that I believe that the idea of interception proxies
> does not have sufficient technical merit to be published by IETF, and
> that IETF's publication of a document that tends to promote the use
> of such devices would actually be harmful to Internet operation and
> its ability to support applications.

Fair enough, but my primary goal was not to justify this particular technique,
but to address the issue of whether we should be preventing the publication of
particular techniques, and under what ground rules. The industry and their
customers have already decided against you on this one. I'm wondering about the
future of an IETF that consistently takes itself out of play in this way. I'm
sure there are other techniques on their way that are going to allow us to find
out...


> p.s. I think the term you're looking for is "nihil obstat".

Yup, that's it. Thanks...

                                                                          -
peterd



From owner-ietf-outbound  Sat Apr  8 16:10:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA13921
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 16:10:03 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@[128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13724
	for <ietf@ietf.org>; Sat, 8 Apr 2000 15:59:58 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1.Beta1/8.10.1.Beta1) with ESMTP id e38Jxvk12760;
	Sat, 8 Apr 2000 15:59:57 -0400
Message-Id: <200004081959.e38Jxvk12760@black-ice.cc.vt.edu>
To: Keith Moore <moore@CS.UTK.EDU>
cc: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Sat, 08 Apr 2000 15:28:12 EDT."
             <200004081928.PAA24738@astro.cs.utk.edu> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200004081928.PAA24738@astro.cs.utk.edu>
Date: Sat, 08 Apr 2000 15:59:57 -0400
X-Loop: ietf@ietf.org

On Sat, 08 Apr 2000 15:28:12 EDT, Keith Moore said:
> The simple fact is that I believe that the idea of interception proxies 
> does not have sufficient technical merit to be published by IETF, and 
> that IETF's publication of a document that tends to promote the use 
> of such devices would actually be harmful to Internet operation and 
> its ability to support applications.  Reasonable people can disagree

Keith:  I think that there's been sufficient commentary here that
interception proxies *do* have a place, both at the "server" end (for
load-balancing server, etc), and at the "client" end.  However, I am
fully in agreement that interception proxies imposed anyplace other
than either endpoint of the connection is a Bad Idea, because a third
party can't be sure of the connection.  I'm willing to do something at
my end, because I know that I wanted to connect to foobar.sprocket.com,
and what semantics that involves.  foobar.sprocket.com can make
decisions, based on its knowledge that any packet on port 7952 is
either for their monkey-widget server, or invalid.  But my transit
providers don't have any basis for making such decisions.

I'd have to vote against progressing it without language making this
distinction as clear as possible.

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Sat Apr  8 16:20:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA14128
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 16:20:03 -0400 (EDT)
Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14011;
	Sat, 8 Apr 2000 16:16:15 -0400 (EDT)
Received: from Software.com ([207.175.94.182]) by mta1biz.bizmailsrvcs.net
          with ESMTP
          id <20000408201545.PSIO851310.mta1biz.bizmailsrvcs.net@Software.com>;
          Sat, 8 Apr 2000 15:15:45 -0500
Sender: droyer
Message-ID: <38EF843D.F1E4C791@Software.com>
Date: Sat, 08 Apr 2000 12:10:53 -0700
From: Doug Royer <Doug.Royer@Software.com>
Reply-To: ietf@ietf.org
Organization: Software.com
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
CC: iesg@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <38EEAA69.9673426@earthlink.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Peter Deutsch in Mountain View wrote:
>
[in part you said]

> I still object to your notion that it's not censorship since people can
> always go elsewhere. Where does this lead? I see the day when people
> can't publish a new  directory service protocol because "The IETF has
> endorsed LDAP for directory services", or would ban the publication of
> an extension to DNS because "it must prevent the misuse of the protocol
> in creating inappropriate services". One by one, you'd be chasing
> innovation to other foums.
> 
> "Danger, Will Robinson! Danger!"

The above information is nonsense.

You seem to be objecting to Keith's right to object to the draft
as it is written. So using your logic (As I understand what you
are saying above) - you are also guilty of censorship by not
wanting Keith to object.

I understand you frustration as many of us in the IETF have
been frustrated from time to time. If you want to convince
me and others then please ignore anything you feel is a non-technical
issue. And address the technical issues.

Many in the IETF *are* swayed by technical content.

I am undecided on this issue and I am personally glad to see this
debate. I do find it an important discussion when it remains
technical. 

Questions I have:

Does this solve a problem that is not already solved by another method?
Not that it has to be unique as you point out above, but if you could
compare it against other known solutions (if any) then perhaps its
advantages (that I have not seen yet) could help you cause?

If this were not done - what could you not do?
I have worked for large corporations and I have worked on large to huge
scaleability problems. Why do I want this?

-Doug



From owner-ietf-outbound  Sat Apr  8 16:50:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA14514
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 16:50:03 -0400 (EDT)
Received: from relay2.sion.com (root@[200.43.36.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14385
	for <ietf@ietf.org>; Sat, 8 Apr 2000 16:41:27 -0400 (EDT)
Received: from PROXY (smtp.sion.com [200.43.36.110])
	by relay2.sion.com (8.9.3/8.9.3) with ESMTP id RAA17595
	for <ietf@ietf.org>; Sat, 8 Apr 2000 17:56:35 -0300
Received: from intranet - 200.43.37.94 by sion.net with Microsoft SMTPSVC;
	 Sat, 8 Apr 2000 17:38:19 -0300
From: "PortalProfesional.com" <info@portalprofesional.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Sat, 08 Apr 2000 17:40:02 -0300
Subject: LEAME, ES IMPORTANTE - www.portalprofesional.com
Reply-To: info@portalprofesional.com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
X-Priority: 1
Message-ID: <013001938200840PROXY@sion.net>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Muchas Preguntas:
- Estas Buscando Empleo?
- Tienes empleo pero quieres uno mejor?
- No sabes donde dejar tu Curriculum?
- Eres Profesional o a punto de egresar?
- Ud es una Empresa y necesita hacer publicidad?
- Necesitas EMAIL Gratis?
- Necesitas Pagina Web Gratis?
- Ud es una Consultora o Empresa y necesita publicar sus Busquedas Laborales?
- Nunca encuentras lo que buscas en Internet?

UNA SOLA RESPUESTA: www.portalprofesional.com


VISITANOS. No te vas a arrepentir!
ICQ: 64451825
www.portalprofesional.com.ar





From owner-ietf-outbound  Sat Apr  8 17:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA14644
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 17:00:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14403;
	Sat, 8 Apr 2000 16:44:50 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA24921;
        Sat, 8 Apr 2000 16:43:00 -0400 (EDT)
Message-Id: <200004082043.QAA24921@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Pyda Srisuresh <srisuresh@yahoo.com>
cc: Keith Moore <moore@cs.utk.edu>, aboba@internaut.com, rfc-ed@rfc-editor.org,
        iesg@ietf.org, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Sat, 08 Apr 2000 12:39:47 PDT."
             <20000408193947.14254.qmail@web1406.mail.yahoo.com> 
Date: Sat, 08 Apr 2000 16:43:00 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Keith - I argued to keep the term "transparent routing" in the 
> NAT terminology RFC (RFC 2663). The arguments I put forth were
> solely mine and not influenced by my employer or anyone else. 

didn't say that they were.

> Clearly, your point of view is skewed against NATs. It is rather 
> hypocritical and unfair to say that those opposed to your view 
> point are misleading the readers, while you apparently do not 
> purport to mislead.

I've tried to get an accurate assessment of the harm done by NATs.
Not surprisingly, NAT developers have tried to downplay these problems.

the problem with a "NAT working group" is that it attracts NAT
developers far more than it does the people whose interests
are harmed by NATs - which is to say, Internet users in general.
so by its very nature a "focused" NAT working group will produce
misleading results.

Keith



From owner-ietf-outbound  Sat Apr  8 17:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA14937
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 17:10:03 -0400 (EDT)
Received: from joy.songbird.com (IDENT:root@joy.songbird.com [208.184.79.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14437;
	Sat, 8 Apr 2000 16:45:30 -0400 (EDT)
Received: from free.88.106.bayarea.net (free.88.106.bayarea.net [205.219.88.106])
	by joy.songbird.com (8.9.3/8.9.3) with SMTP id NAA11105;
	Sat, 8 Apr 2000 13:45:26 -0700
X-Authentication-Warning: joy.songbird.com: free.88.106.bayarea.net [205.219.88.106] didn't use HELO protocol
Message-Id: <4.3.0.20000408133812.00c6acc0@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Sat, 08 Apr 2000 13:45:02 -0700
To: Keith Moore <moore@cs.utk.edu>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: recommendation against publication of
  draft-cerpa-necp-02.txt 
Cc: iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
In-Reply-To: <200004081928.PAA24738@astro.cs.utk.edu>
References: <Your message of "Fri, 07 Apr 2000 23:41:30 EDT." <38EEAA69.9673426@earthlink.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 03:28 PM 4/8/00 -0400, Keith Moore wrote:
>does not have sufficient technical merit to be published by IETF, and
>that IETF's publication of a document that tends to promote the use


Publication under Informational and Experimental has typically been open to 
all wishing it.  It is deemed an essential public service to afford that 
publication channel to anyone feeling that the Internet Community needs 
access to an archival copy of an Internet-related document, proprietary or 
otherwise.

The "IETF" imprimatur applies only to Proposed, Draft, Standard and BCP 
RFCs.  At most, the IETF has typically seen fit only to attach its own 
disclaimer text to other drafts about which it has concerns.

Concern for public misunderstanding of "RFC" vs. "IETF standard" is very 
long-standing and unresolved.  To date, this concern has not been used as a 
reason for entirely refusing publication.  (Making sure that there is no 
misleading text in the document and that the document has an appropriate 
title are different matters.)

Now, if the authors of the draft in question are seeking standardization, 
then the matter of acceptable technical merit is appropriate.  However I 
don't recall seeing a Last Call from the IESG.

d/

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA



From owner-ietf-outbound  Sat Apr  8 17:20:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15155
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 17:20:02 -0400 (EDT)
Received: from web1406.mail.yahoo.com (web1406.mail.yahoo.com [128.11.23.170])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA14669
	for <ietf@ietf.org>; Sat, 8 Apr 2000 17:00:28 -0400 (EDT)
Received: (qmail 24343 invoked by uid 60001); 8 Apr 2000 21:00:26 -0000
Message-ID: <20000408210026.24342.qmail@web1406.mail.yahoo.com>
Received: from [38.186.47.9] by web1406.mail.yahoo.com; Sat, 08 Apr 2000 14:00:26 PDT
Date: Sat, 8 Apr 2000 14:00:26 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
To: Keith Moore <moore@cs.utk.edu>
Cc: Keith Moore <moore@cs.utk.edu>, aboba@internaut.com, rfc-ed@rfc-editor.org,
        iesg@ietf.org, ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org


--- Keith Moore <moore@cs.utk.edu> wrote:
> > Keith - I argued to keep the term "transparent routing" in the 
> > NAT terminology RFC (RFC 2663). The arguments I put forth were
> > solely mine and not influenced by my employer or anyone else. 
> 
> didn't say that they were.
> 
> > Clearly, your point of view is skewed against NATs. It is rather 
> > hypocritical and unfair to say that those opposed to your view 
> > point are misleading the readers, while you apparently do not 
> > purport to mislead.
> 
> I've tried to get an accurate assessment of the harm done by NATs.
> Not surprisingly, NAT developers have tried to downplay these problems.
> 
> the problem with a "NAT working group" is that it attracts NAT
> developers far more than it does the people whose interests
> are harmed by NATs - which is to say, Internet users in general.

That is just not true. NAT WG attracts NAT users just as much and
often more than NAT developers. It is perhaps your opinion that
NAT harms more people than it benefits that is tainted.

> so by its very nature a "focused" NAT working group will produce
> misleading results.
> 

Sorry.. Your conclusion is based on a wrong premise. 

> Keith
> 

regards,
suresh

=====


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com



From owner-ietf-outbound  Sat Apr  8 17:30:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15304
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 17:30:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14705;
	Sat, 8 Apr 2000 17:00:59 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA25033;
        Sat, 8 Apr 2000 17:00:17 -0400 (EDT)
Message-Id: <200004082100.RAA25033@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
cc: Keith Moore <moore@cs.utk.edu>, karl@CAVEBEAR.COM, iesg@ietf.org,
        ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Sat, 08 Apr 2000 01:00:29 EDT."
             <38EEBCED.ACE0FC61@earthlink.net> 
Date: Sat, 08 Apr 2000 17:00:17 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Fair enough, but my primary goal was not to justify this particular technique,
> but to address the issue of whether we should be preventing the publication of
> particular techniques, and under what ground rules

As I see it, the issue is only one of where to have the debate - at
the RFC publication level or on IETF mailing lists.  

> The industry and their customers have already decided against you on 
> this one. 

Industry people love to make such claims.  They're just marketing BS.  
The Internet isn't in final form yet and I don't expect it to stabilize 
for at least another decade.  There's still lots of time for people to 
correct brain damage.

> I'm wondering about the future of an IETF that consistently takes itself 
> out of play in this way. 

IETF's job is to promote technical sanity, not to support unsound vendor 
practices.

Keith



From owner-ietf-outbound  Sat Apr  8 17:40:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15557
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 17:40:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14856;
	Sat, 8 Apr 2000 17:07:27 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA25072;
        Sat, 8 Apr 2000 17:06:54 -0400 (EDT)
Message-Id: <200004082106.RAA25072@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: Keith Moore <moore@cs.utk.edu>, iesg@ietf.org, ietf@ietf.org,
        rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Sat, 08 Apr 2000 13:45:02 PDT."
             <4.3.0.20000408133812.00c6acc0@mail.bayarea.net> 
Date: Sat, 08 Apr 2000 17:06:54 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Publication under Informational and Experimental has typically been 
> open to all wishing it.  

uh, no.   this is a common myth, but it's not true, and hasn't been
true for many years.

I hope (and believe) that the *potential* for publication is open 
to all, and that the process isn't biased according to who is asking,
but my understanding is that a great many drafts which are submitted 
for publication are rejected.  Like any other publication series
which has value as a compilation, the RFC series requires editorial 
oversight and filtering.  

For those that want an unfiltered publication series, there's always the web.
Or Usenet.

Keith  



From owner-ietf-outbound  Sat Apr  8 17:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15777
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 17:50:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14952;
	Sat, 8 Apr 2000 17:10:17 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA25096;
        Sat, 8 Apr 2000 17:08:27 -0400 (EDT)
Message-Id: <200004082108.RAA25096@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Pyda Srisuresh <srisuresh@yahoo.com>
cc: Keith Moore <moore@cs.utk.edu>, aboba@internaut.com, rfc-ed@rfc-editor.org,
        iesg@ietf.org, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Sat, 08 Apr 2000 14:00:26 PDT."
             <20000408210026.24342.qmail@web1406.mail.yahoo.com> 
Date: Sat, 08 Apr 2000 17:08:27 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Sorry.. Your conclusion is based on a wrong premise. 

The NAT group's draft documents speak for themselves.



From owner-ietf-outbound  Sat Apr  8 18:00:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA15959
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 18:00:03 -0400 (EDT)
Received: from web1406.mail.yahoo.com (web1406.mail.yahoo.com [128.11.23.170])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA14981
	for <ietf@ietf.org>; Sat, 8 Apr 2000 17:10:39 -0400 (EDT)
Received: (qmail 25430 invoked by uid 60001); 8 Apr 2000 21:10:40 -0000
Message-ID: <20000408211040.25429.qmail@web1406.mail.yahoo.com>
Received: from [38.186.47.9] by web1406.mail.yahoo.com; Sat, 08 Apr 2000 14:10:40 PDT
Date: Sat, 8 Apr 2000 14:10:40 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
To: Keith Moore <moore@cs.utk.edu>
Cc: Keith Moore <moore@cs.utk.edu>, aboba@internaut.com, rfc-ed@rfc-editor.org,
        iesg@ietf.org, ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org



--- Keith Moore <moore@cs.utk.edu> wrote:
> > Sorry.. Your conclusion is based on a wrong premise. 
> 
> The NAT group's draft documents speak for themselves.
> 
My point exactly.

regards,
suresh

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com



From owner-ietf-outbound  Sat Apr  8 18:10:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA16210
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 18:10:03 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15002
	for <ietf@ietf.org>; Sat, 8 Apr 2000 17:10:49 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12e2UR-0005ci-00; Sat, 08 Apr 2000 22:09:59 +0100
Date: Sat, 8 Apr 2000 22:09:52 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Peter Deutsch in Mountain View <pdeutsch@EARTHLINK.NET>
cc: Keith Moore <moore@cs.utk.edu>, karl@CAVEBEAR.COM, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
In-Reply-To: <38EEAA69.9673426@earthlink.net>
Message-ID: <Pine.GSO.4.21.0004082112300.8135-100000@petra.ee.surrey.ac.uk>
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-Loop: ietf@ietf.org

On Fri, 7 Apr 2000, Peter Deutsch in Mountain View wrote:
[much ad hominem snipped]
> Okay, I'll be a little more pedantic - you called for a ban on
> publishing this document within the IETF. If it makes you feel better,
> load up my previous post in vi and:
> 
>      s/document/document within the IETF/
> 
> I still object to your notion that it's not censorship since people can
> always go elsewhere. Where does this lead?

This leads to peer review and advancing the state of the art by
criticism, feedback and selection.


> Well, look at the list of signatories to the Draft in question.

technical merits, please.


> Frankly, I hope we are going to be able to arrest this dangerous
> trend. So, I engaged last year when I saw the broadcast industry
> being run out of town over the TV: URL draft

whose technical content I recall as being a few lines of incorrect
EBNF notation that didn't parse. But hey, they were generating a _lot_
of signatories with their write-in campaign.


> Yes, and those of us who object to this degradation of the original
> concept of the IETF 

I'd like a reference for the original concept of the IETF, please; I
worry about history being rewritten. What was the original concept of
'RFC Editor', exactly?


> To me the appropriate reponse when someone sees danger in a technology
> is another document, making your case.

...which is why Keith began this thread in the first place. Or don't
mailing list posts count as documents?


> Note, nobody talks in terms of getting something "blessed by the
> IETF", but in terms of how the IETF would slow the work down and get
> in the way so shouldn't be a part of the process.

Peer review slows things down. This is unavoidable in exposing the
work to a larger audience, but has long-term societal benefits
unfortunately not quantifiable on a balance sheet.

L.

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















From owner-ietf-outbound  Sat Apr  8 18:20:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA16360
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 18:20:03 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA15199
	for <ietf@ietf.org>; Sat, 8 Apr 2000 17:23:58 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.23423-0@bells.cs.ucl.ac.uk>; Sat, 8 Apr 2000 22:23:57 +0100
to: ietf@ietf.org
Subject: Re: A thought about patents
In-reply-to: Your message of "Sat, 08 Apr 2000 11:03:58 EDT." <38EF4A5E.2C57B890@ecal.com>
Date: Sat, 08 Apr 2000 22:23:53 +0100
Message-ID: <4889.955229033@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


as ye sow, so shall ye weep...in reading this thread i guess i saw
several problems:

oxymoron alert
"thought...patent"

tautology alert
"sufficiently expensive...lawyer"

internet bogon alert
"find the server"

is a server where the ip address, DNS name, lat/long of the CPU,
memory, disk, or cache, transprent or otherwise is"

sorry,
all bets are off about this dicussion except in the presence of the
european union, where all bets are subject to VAT 

:-)



In message <38EF4A5E.2C57B890@ecal.com>, John Stracke typed:

 >>Masataka Ohta wrote:
 >>
 >>> > Even if it's not true in the general case, a sufficiently expensive lawyer
 >>> > might be able to convince the court that, since the Internet makes location
 >>> > irrelevant, the location of the infringement is irrelevant.
 >>>
 >>> that US patents are applicable even if both servers, clients and network
 >>> inbetween are all located outside of US?
 >>
 >>No, not that; but, if the server is outside the US and the client is inside, then
 >>maybe.
 >>
 >>--
 >>/=================================================================\
 >>|John Stracke    | http://www.ecal.com |My opinions are my own.   |
 >>|Chief Scientist |================================================|
 >>|eCal Corp.      |"Where's your sense of adventure?" "Hiding under|
 >>|francis@ecal.com|the bed."                                       |
 >>\=================================================================/
 >>
 >>
 >>

 cheers

   jon



From owner-ietf-outbound  Sat Apr  8 18:30:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA16529
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 18:30:04 -0400 (EDT)
Received: from joy.songbird.com (IDENT:root@joy.songbird.com [208.184.79.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15268;
	Sat, 8 Apr 2000 17:29:22 -0400 (EDT)
Received: from free.88.106.bayarea.net (free.88.106.bayarea.net [205.219.88.106])
	by joy.songbird.com (8.9.3/8.9.3) with SMTP id OAA11360;
	Sat, 8 Apr 2000 14:29:21 -0700
X-Authentication-Warning: joy.songbird.com: free.88.106.bayarea.net [205.219.88.106] didn't use HELO protocol
Message-Id: <4.3.0.20000408142118.00d31d50@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Sat, 08 Apr 2000 14:29:04 -0700
To: Keith Moore <moore@cs.utk.edu>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: prohibiting RFC publication
Cc: Keith Moore <moore@cs.utk.edu>, iesg@ietf.org, ietf@ietf.org,
        rfc-ed@rfc-editor.org
In-Reply-To: <200004082106.RAA25072@astro.cs.utk.edu>
References: <Your message of "Sat, 08 Apr 2000 13:45:02 PDT." <4.3.0.20000408133812.00c6acc0@mail.bayarea.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 05:06 PM 4/8/00 -0400, Keith Moore wrote:
> > Publication under Informational and Experimental has typically been
> > open to all wishing it.
>
>uh, no.   this is a common myth, but it's not true, and hasn't been
>true for many years.

First, let's be clear that your statement includes a contradiction:  If 
something "hasn't been true for many years" then it is not a myth but, 
rather, a poorly-known change in policy.

That's not nit-picking, it is intended to emphasize that the policy WAS in 
force.

RFC 223, "Instructions to RFC Authors" is a bit vague on this, though it 
does contain an essential statement, in Section 2, along with various other 
qualifiers:

>In some cases it may be determined that the submitted document is not
>    appropriate material to be published as an RFC.


So this does make clear that publication is not an absolute guarantee.

The guiding policy "for may years" has been relevance/interest for the 
Internet community.

One would be hard-pressed to inspect the author-list of 
draft-cerpa-necp-02.txt, the work of the associated companies, and the 
clear need for optimizations of application performance, and then deem this 
document not relevant.

That moves us back to 'technical adequacy'.  Again, that distinguishes 
between "interest value" and "IETF standardization", rather than "publish" 
vs. "do not publish".

d/

ps.  I'm done.  There are more important aspects to the debate about this 
draft.

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA



From owner-ietf-outbound  Sat Apr  8 18:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA16757
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 18:40:03 -0400 (EDT)
Received: from hawk.prod.itd.earthlink.net (hawk.prod.itd.earthlink.net [207.217.120.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15393;
	Sat, 8 Apr 2000 17:31:13 -0400 (EDT)
Received: from earthlink.net (pool0060.cvx21-bradley.dialup.earthlink.net [209.179.192.60])
	by hawk.prod.itd.earthlink.net (8.9.3-ELN-3.0/8.9.3) with ESMTP id OAA00394;
	Sat, 8 Apr 2000 14:29:42 -0700 (PDT)
Message-ID: <38EED201.D3C5C279@earthlink.net>
Date: Sat, 08 Apr 2000 02:30:25 -0400
From: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
X-Mailer: Mozilla 4.08 [en] (Win95; I)
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: karl@CAVEBEAR.COM, iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <200004082100.RAA25033@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Keith Moore wrote:

> > The industry and their customers have already decided against you on
> > this one.
>
> Industry people love to make such claims.  They're just marketing BS.
> The Internet isn't in final form yet and I don't expect it to stabilize
> for at least another decade.  There's still lots of time for people to
> correct brain damage.

Well, I don't share the view of a monotonic march towards the "correct" Internet.
Just as the first single celled giving off massive amounts of waste oxygen created
an environment which led eventually to the furry mammals, the Internet responds and
evolves from instantiation to instantiation. I hear talk about products which people
expect to only have a lifetime of a few years, or even a period of months, until
evolution moves us all on. Some of the things that you find so offensive may not
even be relevant in a couple of years.

But (you knew they'd be a but, didn't you?) there is a substantial market for
products based upon interception or redirection technologies today. I don't offer
this as a technical argument for their adoption. I was merely pointing out that the
market has voted on this technique and judged it useful despite what the IETF might
or might not decree. Short of punishing those poor misguided users, I don't know
what else you can accomplish on this one...


> > I'm wondering about the future of an IETF that consistently takes itself
> > out of play in this way.
>
> IETF's job is to promote technical sanity, not to support unsound vendor
> practices.

Well there you go. You think the IETF's Seal of Approval and promotion of technical
sanity can prevent our unsound vendor practices  from perpetrating Marketing BS on
poor users. You're right - the positions are fairly clear at this point. I'll try to
quieten down now...


                                                                  - peterd



From owner-ietf-outbound  Sat Apr  8 18:50:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA17017
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 18:50:04 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15488
	for <ietf@ietf.org>; Sat, 8 Apr 2000 17:36:18 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12e2q4-0005ip-00; Sat, 08 Apr 2000 22:32:20 +0100
Date: Sat, 8 Apr 2000 22:32:16 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Keith Moore <moore@cs.utk.edu>
cc: Pyda Srisuresh <srisuresh@yahoo.com>, aboba@internaut.com, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
In-Reply-To: <200004082043.QAA24921@astro.cs.utk.edu>
Message-ID: <Pine.GSO.4.21.0004082223210.8135-100000@petra.ee.surrey.ac.uk>
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-Loop: ietf@ietf.org

On Sat, 8 Apr 2000, Keith Moore wrote:

> > Clearly, your point of view is skewed against NATs. It is rather 
> > hypocritical and unfair to say that those opposed to your view 
> > point are misleading the readers, while you apparently do not 
> > purport to mislead.
> 
> I've tried to get an accurate assessment of the harm done by NATs.
> Not surprisingly, NAT developers have tried to downplay these problems.
> 
> the problem with a "NAT working group" is that it attracts NAT
> developers far more than it does the people whose interests
> are harmed by NATs - which is to say, Internet users in general.
> so by its very nature a "focused" NAT working group will produce
> misleading results.

This bias holds for any working group, be it IPSEC, header
compression, or anything else. Why pick on NAT?

L.

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




From owner-ietf-outbound  Sat Apr  8 19:00:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA17281
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 19:00:05 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15593;
	Sat, 8 Apr 2000 17:41:07 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA25358;
        Sat, 8 Apr 2000 17:40:34 -0400 (EDT)
Message-Id: <200004082140.RAA25358@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: Keith Moore <moore@cs.utk.edu>, iesg@ietf.org, ietf@ietf.org,
        rfc-ed@rfc-editor.org
Subject: Re: prohibiting RFC publication 
In-reply-to: Your message of "Sat, 08 Apr 2000 14:29:04 PDT."
             <4.3.0.20000408142118.00d31d50@mail.bayarea.net> 
Date: Sat, 08 Apr 2000 17:40:34 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> One would be hard-pressed to inspect the author-list of 
> draft-cerpa-necp-02.txt, the work of the associated companies, and the 
> clear need for optimizations of application performance, and then deem this 
> document not relevant.

I'm not hard-pressed to do this at all.  In fact I find it quite easy,
because I don't care who the authors work for.  

IMHO, we should base not publication decisions on the authors' employers.
We should base them on technical merit.

The trade press is quite good at fawning over vendors' products;
I don't think IETF needs to take on that role.

Keith



From owner-ietf-outbound  Sat Apr  8 19:10:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA17499
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 19:10:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16254
	for <ietf@ietf.org>; Sat, 8 Apr 2000 18:12:09 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id SAA25429;
        Sat, 8 Apr 2000 18:10:18 -0400 (EDT)
Message-Id: <200004082210.SAA25429@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: L.Wood@eim.surrey.ac.uk
cc: Keith Moore <moore@cs.utk.edu>, Pyda Srisuresh <srisuresh@yahoo.com>,
        aboba@internaut.com, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Sat, 08 Apr 2000 22:32:16 BST."
             <Pine.GSO.4.21.0004082223210.8135-100000@petra.ee.surrey.ac.uk> 
Date: Sat, 08 Apr 2000 18:10:18 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> > the problem with a "NAT working group" is that it attracts NAT
> > developers far more than it does the people whose interests
> > are harmed by NATs - which is to say, Internet users in general.
> > so by its very nature a "focused" NAT working group will produce
> > misleading results.
> 
> This bias holds for any working group, be it IPSEC, header
> compression, or anything else. Why pick on NAT?

good question.

Most IETF working groups are working on things that are 
more-or-less harmless, in that their effects are likely
to be isolated to those who choose to use them.  Their greatest 
potential for harm is that they will displace something better 
that might crop up in the same space.   The fact that such a WG
is biased toward its own problem space isn't of much consequence 
because their solution isn't likely to affect people trying to
solve different problems.

NATs (and interception proxies) have much higher risk - they attempt
to address certain real problems but they do so at the expense of 
flexibility, generality, predictability, and reliability of the
network.  They also violate long-established conventions about
the separation of functions between network layers, and in doing so,
break higher level applications that (quite reasonably) assume
that the lower layers of the network are working within their
design constraints.  

Within the current IP architecture, the notion of a "technically
sound NAT" is an oxymoron - NATs inhernetly violate fundamental
design constraints of the architecture.  The technically sound 
way to solve the problems that NATs attempt to address is not to 
alter the behavior of NATs but to provide alternatives outside
of the NAT space.  But a group that's NAT-centric is inherently
focused inside that space, and thus has a very limited ability to
promote technical soundness.

(and there are those who think that the Internet architecture
should be changed to incorporate NATs and that all of those applications
which don't work in the presence of NATs should be deemed obsolete.
but the effect of such a change is so widespread that it is far beyond the 
ability of the NAT working group - or any single working group - to evaluate)

Keith



From owner-ietf-outbound  Sat Apr  8 19:20:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA17677
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 19:20:03 -0400 (EDT)
Received: from gull.prod.itd.earthlink.net (gull.prod.itd.earthlink.net [207.217.121.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16555
	for <ietf@ietf.org>; Sat, 8 Apr 2000 18:30:51 -0400 (EDT)
Received: from earthlink.net (pool0060.cvx21-bradley.dialup.earthlink.net [209.179.192.60])
	by gull.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id PAA14243;
	Sat, 8 Apr 2000 15:30:43 -0700 (PDT)
Message-ID: <38EEE04E.8801053E@earthlink.net>
Date: Sat, 08 Apr 2000 03:31:26 -0400
From: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
X-Mailer: Mozilla 4.08 [en] (Win95; I)
MIME-Version: 1.0
To: L.Wood@eim.surrey.ac.uk
CC: Keith Moore <moore@cs.utk.edu>, karl@CAVEBEAR.COM, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <Pine.GSO.4.21.0004082112300.8135-100000@petra.ee.surrey.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

g'day,

Lloyd Wood wrote:

> > Well, look at the list of signatories to the Draft in question.
>
> technical merits, please.

I was not arguing for the merits of the technology in question based upon who
signed it. In fact, I haven't tried to address the technical merits of the
specific document at all. I was addressing the issue that Keith was declaring
a technique (IP address interception) as out of scope for the IETF and was,
in doing so, cutting the IETF off from an area of work that finds widespread
application on the net. This seemed inappropriate considering the claims for
the organization in such places as:

                   <http://www.ietf.org/tao.html#What_Is_IETF>

Note in particular the claims " It is the principal body engaged in the
development of new Internet standard specifications" and "Its mission
includes: ... Providing a forum for the exchange of information within the
Internet community between  vendors, users, researchers, agency contractors
and network managers."

IP address interception is a widely used technique that would not be
developed or documented through the IETF if Keith had his way. Since it is a
widely used technique for vendors and network managers, we'd have to ask Gary
Malkin to revise his document if we agree to Keith's request.

To be explicit, this is a metadiscussion about the IETF. I specifically
disclaim any interest or standing in a debate about NECP itself.


> > Frankly, I hope we are going to be able to arrest this dangerous
> > trend. So, I engaged last year when I saw the broadcast industry
> > being run out of town over the TV: URL draft
>
> whose technical content I recall as being a few lines of incorrect
> EBNF notation that didn't parse. But hey, they were generating a _lot_
> of signatories with their write-in campaign.

Again, I did not engage in a debate about the technical merits of their
claims, I was (and am) pointing out that the IETF claims to be a gathering
place to educate and exchange ideas and is not as good at that as it used to
be (IMHO).


> > Yes, and those of us who object to this degradation of the original
> > concept of the IETF
>
> I'd like a reference for the original concept of the IETF, please; I
> worry about history being rewritten. What was the original concept of
> 'RFC Editor', exactly?

I'm away from my archives, and my history only goes back about 10 years, so
I'll leave that for others who were there, but I refer you again to the Tao
of the IETF.


> > To me the appropriate reponse when someone sees danger in a technology
> > is another document, making your case.
>
> ...which is why Keith began this thread in the first place. Or don't
> mailing list posts count as documents?

Well, that's not the way I read his initial messages. He basically said "I
tried to stop them at the drafting stage, but couldn't so I ask that we not
let this go out the door with our name on it".

Originally the response to an RFC you disagreed with was an RFC explaining
the problems you perceive. It is true that things have become more formal
over time, but nowhere is it carved in stone tablets that we can't identify
problems with current trends and make some adjustments to our processes.
That's not a call for less peer review. It's a call for less of a single
world view, and more tolerance for multiple world views. In effect, I'd also
rather we worry more about what technical people do with our documents and
less with what marketing people do with our documents.


> > Note, nobody talks in terms of getting something "blessed by the
> > IETF", but in terms of how the IETF would slow the work down and get
> > in the way so shouldn't be a part of the process.
>
> Peer review slows things down. This is unavoidable in exposing the
> work to a larger audience, but has long-term societal benefits
> unfortunately not quantifiable on a balance sheet.

I guess I didn't explain that very well. The question was not whether the
work would be submited to peer review, but whether the IETF was an
appropriate forum for that peer review. The view I've heard expressed several
times has been that the IETF has ossified and would not be receptive to new
ideas so just slowed things down. The implication being that the IETF was no
longer relevant to the engineering process. You are not going to hear this
opinion expressed here from people who have already moved on, so I thought
I'd pass it on.

Note, I am *not* suggesting Cisco has abandoned the IETF. Heck, such a
decision would be so way out of my pay grade (and not the way I see this
company working  at all).  I'm just suggesting that at least some individuals
I know (and not just at Cisco) are starting to feel that the IETF is less
relevant to their needs than it used to be. Some people are going to say
"great, that'll cut down on the marketing BS".. I happen to say "Houston, we
have a problem here..."

                                                                            -
peterd


----------------------------------------------------------------------
Peter Deutsch                     work email:  pdeutsch@cisco.com
Technical Leader
Content Services Business Unit       private:
pdeutsch@earthlink.net
Cisco Systems                           or  :  peterd@the.web

         Alcohol and calculus don't mix. Never drink and derive.
----------------------------------------------------------------------




From owner-ietf-outbound  Sat Apr  8 19:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA17868
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 19:30:03 -0400 (EDT)
Received: from npax.cavebear.com (npax.cavebear.com [192.203.17.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17071;
	Sat, 8 Apr 2000 18:51:44 -0400 (EDT)
Received: from localhost (karl@localhost)
	by npax.cavebear.com (8.9.3/8.9.3) with ESMTP id PAA25467;
	Sat, 8 Apr 2000 15:51:15 -0700
Date: Sat, 8 Apr 2000 15:51:15 -0700 (PDT)
From: Karl Auerbach <karl@CaveBear.com>
Reply-To: Karl Auerbach <karl@CaveBear.com>
To: IETF <ietf@ietf.org>
cc: iesg@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: prohibiting RFC publication
In-Reply-To: <4.3.0.20000408142118.00d31d50@mail.bayarea.net>
Message-ID: <Pine.LNX.4.21.0004081546410.25353-100000@npax.cavebear.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


I'd like note my agreement with to the comments made by Dave Crocker.

And I would like to suggest that there is perhaps yet another aspect of
this debate:

The IETF recently made a strong moral statement against CALEA.  That
statement carried weight; it was noticed; it had impact.

And that statement carried weight precisely because it was unique - it was
a statement of morality that carried weight because such statements are
reserved for the worst of the worst.

If the IETF engages in routine non-acceptance of "informational" documents
on the basis of non-technical concerns the IETF will, I believe, lose its
clear and loud voice when that voice is most needed to be heard.

		--karl--






From owner-ietf-outbound  Sat Apr  8 19:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA18127
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 19:40:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17572
	for <ietf@ietf.org>; Sat, 8 Apr 2000 19:14:56 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id TAA25587;
        Sat, 8 Apr 2000 19:14:12 -0400 (EDT)
Message-Id: <200004082314.TAA25587@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
cc: L.Wood@eim.surrey.ac.uk, Keith Moore <moore@cs.utk.edu>, karl@CAVEBEAR.COM,
        ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Sat, 08 Apr 2000 03:31:26 EDT."
             <38EEE04E.8801053E@earthlink.net> 
Date: Sat, 08 Apr 2000 19:14:11 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

Peter,

I don't think I would agree that NECP is out of scope for IETF.
I think it's pefectly valid for IETF to say things like "NECP
is intended to support interception proxies.  Such proxies 
violate the IP architecture in the following ways: ... and 
therefore cause the following problems... the only acceptable 
things for an interception proxy to do within the current 
architecture are those things which are already allowed by the
IP layer (route packets without change to their intended 
destination, delay packets, duplicate packets, or drop them)
and the use (if at all) of devices that do more than this should 
be limited to the following situations..."  But it's difficult to 
say things like this if you start with a document that assumes 
that interception proxies are fundamentally a good thing.  

IETF tries to make the Internet work well.  If you propose something
that fundamentally violates the design of the Internet Protocol,
and which harms the ability of Internet applications to work well,
is that really something that the IETF should take on?  Granted
that the Internet can and should evolve over time, but proposals that
fundamentally change the architecture need to be examined from a 
big-picture point of view and not in a piecemeal fashion.

> Note, I am *not* suggesting Cisco has abandoned the IETF. Heck, such a
> decision would be so way out of my pay grade (and not the way I see this
> company working  at all).  I'm just suggesting that at least some 
> individuals I know (and not just at Cisco) are starting to feel that the 
> IETF is less relevant to their needs than it used to be. 

then perhaps they misunderstand the IETF.  IETF doesn't exist to
meet the needs of cisco or any other single group.  IETF exists 
to help the Internet work well for the benefit of all Internet users.  
When vendors produce products that harm the ability of the Internet
to work well, they're quite naturally putting themselves in conflict
with the IETF.  This shouldn't surprise anyone.

Keith 



From owner-ietf-outbound  Sat Apr  8 19:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA18292
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 19:50:03 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17759
	for <ietf@ietf.org>; Sat, 8 Apr 2000 19:24:28 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200004082316.IAA22750@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id IAA22750; Sun, 9 Apr 2000 08:15:52 +0859
Subject: Re: A thought about patents
To: svidal@lander.es (Salvador Vidal)
Date: Sun, 9 Apr 0 8:15:51 JST
Cc: mohta@necom830.hpcl.titech.ac.jp, ietf@ietf.org
In-Reply-To: <3.0.6.32.20000408131554.00879b90@lince.lander.es>; from "Salvador Vidal" at Apr 8, 100 8:14 pm
X-Mailer: ELM [version 2.3 PL11]
X-Loop: ietf@ietf.org

Salvador;

Yes, they are individuals, not companies. Individuals can not be
effectively controlled with patent or copyright.

> With the general crash of protection systems I think that the copyrights
> will be mainly driven in indirect way, by charging copyrights royaltties =
> to
> hardware products, telephone bills,..., some strong points of indirect wa=
> y
> are:

Indirect way does not work.

If major form of distribution is through uncontrolled copying on the
Internet, which can not be illeagal if royalities are charged, it is
impossible to know the fair share of the royalties for each copyrighted
material.

							Masataka Ohta



From owner-ietf-outbound  Sat Apr  8 21:10:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA19163
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 21:10:03 -0400 (EDT)
Received: from hawk.prod.itd.earthlink.net (hawk.prod.itd.earthlink.net [207.217.120.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19097;
	Sat, 8 Apr 2000 21:03:02 -0400 (EDT)
Received: from videotron.ca (pool0060.cvx21-bradley.dialup.earthlink.net [209.179.192.60])
	by hawk.prod.itd.earthlink.net (8.9.3-ELN-3.0/8.9.3) with ESMTP id SAA15329;
	Sat, 8 Apr 2000 18:02:57 -0700 (PDT)
Message-ID: <38EF03FB.7C35C7A3@videotron.ca>
Date: Sat, 08 Apr 2000 06:03:39 -0400
From: Peter Deutsch <peterd@videotron.ca>
Reply-To: pdeutsch@earthlink.net
X-Sender: "Peter Deutsch" <vlopqxyh@pop.videotron.ca> (Unverified)
X-Mailer: Mozilla 4.08 [en]C-NECCK  (Win95; I)
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Dave Crocker <dcrocker@brandenburg.com>, iesg@ietf.org, ietf@ietf.org,
        rfc-ed@rfc-editor.org
Subject: Re: prohibiting RFC publication
References: <200004082140.RAA25358@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

g'day,



Keith Moore wrote:

> 

> > One would be hard-pressed to inspect the author-list of

> > draft-cerpa-necp-02.txt, the work of the associated companies, and the

> > clear need for optimizations of application performance, and then deem this

> > document not relevant.

> 

> I'm not hard-pressed to do this at all.  In fact I find it quite easy,

> because I don't care who the authors work for.

> 

> IMHO, we should base not publication decisions on the authors' employers.

> We should base them on technical merit.



Okay, I did some digging. Here are a few relevant excerpts from RFC
2026:



...

   The RFC series of documents on networking began in 1969 as part of

   the original ARPA wide-area networking (ARPANET) project (see

   Appendix A for glossary of acronyms).  RFCs cover a wide range of

   topics in addition to Internet Standards, from early discussion of

   new research concepts to status memos about the Internet. 

...

   Not all specifications of protocols or services for the Internet

   should or will become Internet Standards or BCPs.  Such non-standards

   track specifications are not subject to the rules for Internet

   standardization.  Non-standards track specifications may be published

   directly as "Experimental" or "Informational" RFCs at the discretion

   of the RFC Editor in consultation with the IESG (see section 4.2).

...

      ********************************************************

      *                                                      *

      *   It is important to remember that not all RFCs      *

      *   are standards track documents, and that not all    *

      *   standards track documents reach the level of       *

      *   Internet Standard. In the same way, not all RFCs   *

      *   which describe current practices have been given   *

      *   the review and approval to become BCPs. See        *

      *   RFC-1796 [6] for further information.              *

      *                                                      *

      ********************************************************

...



4.2.1  Experimental



   The "Experimental" designation typically denotes a specification that

   is part of some research or development effort.  Such a specification

   is published for the general information of the Internet technical

   community and as an archival record of the work, subject only to

   editorial considerations and to verification that there has been

   adequate coordination with the standards process (see below).  An

   Experimental specification may be the output of an organized Internet

   research effort (e.g., a Research Group of the IRTF), an IETF Working

   Group, or it may be an individual contribution.

...



4.2.2  Informational



   An "Informational" specification is published for the general

   information of the Internet community, and does not represent an

   Internet community consensus or recommendation.  The Informational

   designation is intended to provide for the timely publication of a

   very broad range of responsible informational documents from many

   sources, subject only to editorial considerations and to verification

   that there has been adequate coordination with the standards process

   (see section 4.2.3).



   Specifications that have been prepared outside of the Internet

   community and are not incorporated into the Internet Standards

   Process by any of the provisions of section 10 may be published as

   Informational RFCs, with the permission of the owner and the

   concurrence of the RFC Editor.

...



   If (a) the IESG recommends that the document be brought within the

   IETF and progressed within the IETF context, but the author declines

   to do so, or (b) the IESG considers that the document proposes

   something that conflicts with, or is actually inimical to, an

   established IETF effort, the document may still be published as an

   Experimental or Informational RFC.  In these cases, however, the IESG

   may insert appropriate "disclaimer" text into the RFC either in or

   immediately following the "Status of this Memo" section in order to

   make the circumstances of its publication clear to readers.





Seems pretty clear to me. Given that one of the roles of the IETF is

"Providing a forum for the exchange of information within the Internet

community between vendors, users, researchers, agency contractors and

network managers" (ref: RFC 1718), it would seem appropriate to publish

material from vendors that is finding widespread use, even if it

violates some individuals' personal view of the how the Internet should

be built.





> The trade press is quite good at fawning over vendors' products;

> I don't think IETF needs to take on that role.



You seem quite afraid of the IETF being hijacked by vendors' marketing
people, but I submit you are denying a documented role of the IETF to be
a clearing house for information in the process. If you want the
appropriate words of RFC 22026 and 1718 deleted that you take the
appropriate steps to initiate the change, but I suggest that meanwhile
you shouldn't be denying the documented evidence for such a role within
the IETF.



					- peterd




-- 
----------------------------------------------------------------------
Peter Deutsch                     work email:  pdeutsch@cisco.com
Technical Leader
Content Services Business Unit       private: 
pdeutsch@earthlink.net
Cisco Systems                           or  :  peterd@the.web

   A specification that has been superseded by a more recent

   specification or is for any other reason considered to be obsolete is

   assigned to the "Historic" level.  (Purists have suggested that the

   word should be "Historical"; however, at this point the use of

   "Historic" is historical.)
----------------------------------------------------------------------



From owner-ietf-outbound  Sat Apr  8 23:10:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA22177
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 23:10:03 -0400 (EDT)
Received: from tsx-prime.MIT.EDU (TSX-PRIME.MIT.EDU [18.86.0.76])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA22053;
	Sat, 8 Apr 2000 23:03:41 -0400 (EDT)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id XAA13980; Sat, 8 Apr 2000 23:03:34 -0400
Date: Sat, 8 Apr 2000 23:03:34 -0400
Message-Id: <200004090303.XAA13980@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
CC: Keith Moore <moore@cs.utk.edu>, karl@CAVEBEAR.COM, iesg@ietf.org,
        ietf@ietf.org, rfc-ed@rfc-editor.org
In-reply-to: Peter Deutsch in Mountain View's message of Sat, 08 Apr 2000
	02:30:25 -0400, <38EED201.D3C5C279@earthlink.net>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   Date: Sat, 08 Apr 2000 02:30:25 -0400
   From: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>

   Well there you go. You think the IETF's Seal of Approval and
   promotion of technical sanity can prevent our unsound vendor
   practices from perpetrating Marketing BS on poor users. You're right
   - the positions are fairly clear at this point. I'll try to quieten
   down now...

Whether or not the withholding of IETF's Seal of Approval would
influence the vendors is a separable question from whether or not it
would be responsible for the IETF to give such a Seal of Approval for
something which is a bad idea from a technical point of view.

							- Ted



From owner-ietf-outbound  Sat Apr  8 23:50:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA23023
	for ietf-outbound.10@ietf.org; Sat, 8 Apr 2000 23:50:03 -0400 (EDT)
Received: from hose.pipex.net (hose.mail.pipex.net [158.43.128.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22898
	for <ietf@ietf.org>; Sat, 8 Apr 2000 23:42:06 -0400 (EDT)
Received: from bigfoot.com (userbi66.uk.uudial.com [62.188.143.130])
	by hose.pipex.net (Postfix) with ESMTP
	id 411FB4501; Sun,  9 Apr 2000 04:42:06 +0100 (BST)
Message-ID: <38EFFB6A.7919A599@bigfoot.com>
Date: Sun, 09 Apr 2000 04:39:22 +0100
From: "Martin J.G. Williams" <martin.jg.williams@bigfoot.com>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <200004090303.XAA13980@tsx-prime.MIT.EDU>
Content-Type: multipart/mixed;
 boundary="------------D2871AE07F0514ED0656E14C"
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.
--------------D2871AE07F0514ED0656E14C
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I've come into this discussion rather late, however there is at least one
salient point which I believe that
Keith Moore has argued rather well...

In my understanding the role of the IETF is to promote the logical growth
and evolution of the Internet Protocols.
Whilst 'vendors' have massive technical resources at their disposal, one
thing that they are not, is impartial...this
is what I have always believed that the IETF's role is!

There is no denying the benefits that companies like Cisco have brought to
the Internet, but their kotive is, quite simply,
profit based....no more, no less.

On another note - to the guy who said 'this is way out of my pay grade' - I
would have to say...since when did pay reflect IQ?
Knowledge and insight are a valuable and rare commodity anyway...if we
start discriminating an the basis of income then
all of these discussion will become irrelevent within ten years, if not
less! (i'm not gonna name any names here! :-)  )

Kind regards
Martin


--------------D2871AE07F0514ED0656E14C
Content-Type: text/x-vcard; charset=us-ascii;
 name="martin.jg.williams.vcf"
Content-Description: Card for Martin J.G. Williams
Content-Disposition: attachment;
 filename="martin.jg.williams.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Williams;Martin
tel;cell:+44 (0)7971 018413
tel;fax:+44 (0)7092 245455
tel;home:+44 (0)1672 514508
tel;work:+44 (0)7971 018413
x-mozilla-html:TRUE
adr:;;;Marlborough;;;United Kingdom
version:2.1
email;internet:martin.jg.williams@bigfoot.com
title:UNIX Systems Consultant
fn:Martin Williams
end:vcard

--------------D2871AE07F0514ED0656E14C--



From owner-ietf-outbound  Sun Apr  9 00:00:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA23204
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 00:00:06 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23063
	for <ietf@ietf.org>; Sat, 8 Apr 2000 23:52:42 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id VAA12790
	for ietf@ietf.org  env-from <vjs>;
	Sat, 8 Apr 2000 21:52:43 -0600 (MDT)
Date: Sat, 8 Apr 2000 21:52:43 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004090352.VAA12790@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
X-Loop: ietf@ietf.org

Why isn't the technical notion of stealth SMTP proxies intended and
currently used by third parties to "filter" objectionable email at least
as much anathema in the IETF as the technical notion of modifying voice/IP
protocols to someday facilitate "monitoring" of "criminal" voice traffic?

Am I weird in worrying even more about not being able to speak than about
the privacy of my words?


Vernon Schryver    vjs@rhyolite.com

P.S. if you aren't bothered by the notion of third parties imposing what
 they consider "proxies" for your HTTP, SMTP, or other traffic, then the
 draft looks interesting.  As with the wiretapping controversy, the issue
 has nothing to do with the technical quality of the draft.

P.P.S. I don't like spam and have done more than many people to combat it,
  including having built and operated automated filters that rejected (and
  might still be rejecting) 1000's of messages per day from the network
  of a large corporation.  That filtering was not by a stealth proxy or
  by a third party and so was ok by my lights, but I'm beginning to wonder
  if it was such a good precedent.



From owner-ietf-outbound  Sun Apr  9 00:41:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA23687
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 00:40:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23645;
	Sun, 9 Apr 2000 00:35:16 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id AAA26512;
        Sun, 9 Apr 2000 00:34:38 -0400 (EDT)
Message-Id: <200004090434.AAA26512@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: pdeutsch@earthlink.net
cc: Keith Moore <moore@cs.utk.edu>, Dave Crocker <dcrocker@brandenburg.com>,
        iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: prohibiting RFC publication 
In-reply-to: Your message of "Sat, 08 Apr 2000 06:03:39 EDT."
             <38EF03FB.7C35C7A3@videotron.ca> 
Date: Sun, 09 Apr 2000 00:34:38 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> You seem quite afraid of the IETF being hijacked by vendors' marketing
> people, but I submit you are denying a documented role of the IETF to be
> a clearing house for information in the process. 

I have no problem with IETF having that role, and I agree that it is useful.
My objection was not about IETF having this role, but about publication of 
this specific document, in its current form.

2026 never says that all industry contributions are automatically 
worthy of publciation.  Neither does it say that the purpose of
RFCs is to serve as a way for vendors to claim legitimacy for 
techincally dubious ideas - as happens all too often.

This one, I think, is not worthy.  Or at least, it's on the margin.

Keith



From owner-ietf-outbound  Sun Apr  9 00:51:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA23807
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 00:50:03 -0400 (EDT)
Received: from hose.pipex.net (hose.mail.pipex.net [158.43.128.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23708;
	Sun, 9 Apr 2000 00:40:57 -0400 (EDT)
Received: from bigfoot.com (userac32.uk.uudial.com [62.188.130.230])
	by hose.pipex.net (Postfix) with ESMTP
	id 4620E4503; Sun,  9 Apr 2000 05:40:55 +0100 (BST)
Message-ID: <38F0094B.99071F39@bigfoot.com>
Date: Sun, 09 Apr 2000 05:38:35 +0100
From: "Martin J.G. Williams" <martin.jg.williams@bigfoot.com>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
Cc: Dave Crocker <dcrocker@BRANDENBURG.COM>, iesg@ietf.org, ietf@ietf.org,
        rfc-ed@rfc-editor.org
Subject: Re: prohibiting RFC publication
References: <200004082140.RAA25358@astro.cs.utk.edu>
Content-Type: multipart/mixed;
 boundary="------------498FFDB5508D50EADEBEEE36"
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.
--------------498FFDB5508D50EADEBEEE36
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I couldn't agree more Keith,

As far as i'm concerned (IMHO) if the standards bodies were to be driven by the
vendors, then they would become no more
than sanitised purveyors of de facto standards, and je jure standards would be
relegated to being nothing more than "misty-eyed" memories.
(Apologies if my spelling isn't up to scratch, but it's late!)

Martin

Keith Moore wrote:

> > One would be hard-pressed to inspect the author-list of
> > draft-cerpa-necp-02.txt, the work of the associated companies, and the
> > clear need for optimizations of application performance, and then deem this
> > document not relevant.
>
> I'm not hard-pressed to do this at all.  In fact I find it quite easy,
> because I don't care who the authors work for.
>
> IMHO, we should base not publication decisions on the authors' employers.
> We should base them on technical merit.
>
> The trade press is quite good at fawning over vendors' products;
> I don't think IETF needs to take on that role.
>
> Keith

--------------498FFDB5508D50EADEBEEE36
Content-Type: text/x-vcard; charset=us-ascii;
 name="martin.jg.williams.vcf"
Content-Description: Card for Martin J.G. Williams
Content-Disposition: attachment;
 filename="martin.jg.williams.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Williams;Martin
tel;cell:+44 (0)7971 018413
tel;fax:+44 (0)7092 245455
tel;home:+44 (0)1672 514508
tel;work:+44 (0)7971 018413
x-mozilla-html:TRUE
adr:;;;Marlborough;;;United Kingdom
version:2.1
email;internet:martin.jg.williams@bigfoot.com
title:UNIX Systems Consultant
fn:Martin Williams
end:vcard

--------------498FFDB5508D50EADEBEEE36--



From owner-ietf-outbound  Sun Apr  9 10:33:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08535
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 10:30:02 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08512
	for <ietf@ietf.org>; Sun, 9 Apr 2000 10:26:22 -0400 (EDT)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id KAA20508
	for <ietf@ietf.org>; Sun, 9 Apr 2000 10:26:23 -0400 (EDT)
Sender: hgs@cs.columbia.edu
Message-ID: <38F0930F.1E42D638@cs.columbia.edu>
Date: Sun, 09 Apr 2000 10:26:23 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Patents
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

The current issue of The Economist discusses the state of the current
patent system. It refers to a site www.bustpatents.com, which may be of
interest in this regard.
-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



From owner-ietf-outbound  Sun Apr  9 14:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA09756
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 14:00:03 -0400 (EDT)
Received: from episteme-software.com (resnick1.qualcomm.com [63.250.90.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09671;
	Sun, 9 Apr 2000 13:55:10 -0400 (EDT)
Received: from resnick2.qualcomm.com (63.250.90.99) by 
 episteme-software.com with ESMTP (Eudora
 Internet Mail Server 3.0); Sun, 9 Apr 2000 12:54:31 -0500
Mime-Version: 1.0
X-Sender: resnick (Unverified)
Message-Id: <p04311401b51671988383@resnick2.qualcomm.com>
In-Reply-To: <200004082140.RAA25358@astro.cs.utk.edu>
References: <200004082140.RAA25358@astro.cs.utk.edu>
X-Mailer: Eudora [Macintosh version 4.3a?]
Date: Sun, 9 Apr 2000 12:54:28 -0500
To: Keith Moore <moore@cs.utk.edu>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: prohibiting RFC publication
Cc: Dave Crocker <dcrocker@brandenburg.com>, Keith Moore <moore@cs.utk.edu>,
        iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

On 4/8/00 at 5:40 PM -0400, Keith Moore wrote:

>  > One would be hard-pressed to inspect the author-list of
>>  draft-cerpa-necp-02.txt, the work of the associated companies, and the
>>  clear need for optimizations of application performance, and then deem this
>  > document not relevant.
>
>I'm not hard-pressed to do this at all.  In fact I find it quite easy,
>because I don't care who the authors work for.

You should care. Who the authors work for may have no impact 
whatsoever on *technical merit* (I would claim it never does), but it 
very often does indicate something about *relevance to the Internet 
community*. If lots of people from companies that have impact on the 
working of the Internet are doing something on the Internet and want 
to publish the existence of that practice, it is bloody well 
*relevant*, regardless of its technical merit.

>IMHO, we should base not publication decisions on the authors' employers.
>We should base them on technical merit.

You need to go back and read the message to which you are responding 
again. Technical merit is specifically *not* a factor in deciding 
publication of an Experimental or Informational document.

>The trade press is quite good at fawning over vendors' products;
>I don't think IETF needs to take on that role.

3 straw men in one message. Impressive.

Dave's message only said that technical merit has no bearing on 
publication of Informational or Experimental RFCs. He (nor anyone 
else in this thread as far as I can tell) mad no claim that we ought 
to determine technical merit on the basis of the vendors, nor that we 
base a decision for publication based solely on who those vendors 
are, nor that we fawn over vendors products. He suggested that we 
allow them to document current practice. Unless (cf. 2026) "the IESG 
considers that the document proposes something that conflicts with, 
or is actually inimical to, an established IETF effort" (which I have 
not heard out of the IESG yet), the RFC editor should (with the 
required changes of getting rid of "implied standardhood") publish 
the document.

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
Eudora Engineering - QUALCOMM Incorporated
Ph: (217)337-6377 or (858)651-4478, Fax: (858)651-1102



From owner-ietf-outbound  Sun Apr  9 14:10:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA09909
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 14:10:03 -0400 (EDT)
Received: from joy.songbird.com (IDENT:root@joy.songbird.com [208.184.79.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09700
	for <IETF@ietf.org>; Sun, 9 Apr 2000 13:57:54 -0400 (EDT)
Received: from free.88.106.bayarea.net (free.88.106.bayarea.net [205.219.88.106])
	by joy.songbird.com (8.9.3/8.9.3) with SMTP id KAA20929
	for <IETF@ietf.org>; Sun, 9 Apr 2000 10:57:53 -0700
X-Authentication-Warning: joy.songbird.com: free.88.106.bayarea.net [205.219.88.106] didn't use HELO protocol
Message-Id: <4.3.0.20000409103208.00c71430@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Sun, 09 Apr 2000 10:39:27 -0700
To: IETF@ietf.org
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Constructive IETF patent action(s)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Folks,

The time between ietf list discussions about patent issues seems to be 
getting smaller.  Unfortunately, there is not much that the IETF can do 
about patent law, in the U.S. or elsewhere.

(Also, based on my own very limited exposure to that realm, it seems clear 
that only a very small percentage of those participating in these 
discussions have much detailed knowledge about realities of patent 
processes.  That's not a criticism, just an added reason we should limit 
our discussion of the general issues.)

In the U.S., government patent officers DO, in fact, search outside 
databases, such as related to the IEEE.  A number of notes on this recent 
thread suggested searching RFCs and Internet Drafts.

The problem is that it is not currently possible to search "the Internet 
Drafts" except for those that are currently active.  It is possible to 
retrieve a prior draft, if you know its name, but not to search for it.

The data base of all Internet Drafts, past and present, is an incredibly 
rich reservoir of prior art.  It would be enormously helpful, both to 
government patent officers and to patent infringement defense attorneys, to 
have easy searching access to the IETF's I-D data base.

d/

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA



From owner-ietf-outbound  Sun Apr  9 14:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10091
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 14:30:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10041
	for <ietf@ietf.org>; Sun, 9 Apr 2000 14:24:25 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id MAA27489
	for ietf@ietf.org  env-from <vjs>;
	Sun, 9 Apr 2000 12:24:27 -0600 (MDT)
Date: Sun, 9 Apr 2000 12:24:27 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004091824.MAA27489@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: prohibiting RFC publication
X-Loop: ietf@ietf.org

> From: Pete Resnick <presnick@QUALCOMM.COM>

> ...
> Dave's message only said that technical merit has no bearing on 
> publication of Informational or Experimental RFCs. He (nor anyone 
> else in this thread as far as I can tell) mad no claim that we ought 
> to determine technical merit on the basis of the vendors, nor that we 
> base a decision for publication based solely on who those vendors 
> are, nor that we fawn over vendors products. He suggested that we 
> allow them to document current practice. Unless (cf. 2026) "the IESG 
> considers that the document proposes something that conflicts with, 
> or is actually inimical to, an established IETF effort" (which I have 
> not heard out of the IESG yet), the RFC editor should (with the 
> required changes of getting rid of "implied standardhood") publish 
> the document.


Do I understand correctly that you think that 
draft-terrell-ip-spec-ipv7-ipv8-addr-cls-02.txt
should have been published as an RFC?

Since technical merit is irrelevant, you must be in favor of
publishing draft-terrell-logic-analy-bin-ip-spec-ipv7-ipv8-04.txt.
Do you prefer Informational or Experimental?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Sun Apr  9 14:40:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10240
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 14:40:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10199
	for <ietf@ietf.org>; Sun, 9 Apr 2000 14:33:10 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id UAA27527;
	Sun, 9 Apr 2000 20:32:56 +0200
Message-Id: <4.3.1.2.20000409201728.021a3ce8@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sun, 09 Apr 2000 20:21:40 +0200
To: Pete Resnick <presnick@qualcomm.com>, Keith Moore <moore@cs.utk.edu>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: prohibiting RFC publication
Cc: ietf@ietf.org
In-Reply-To: <p04311401b51671988383@resnick2.qualcomm.com>
References: <200004082140.RAA25358@astro.cs.utk.edu>
 <200004082140.RAA25358@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 12:54 09.04.2000 -0500, Pete Resnick wrote:
>You need to go back and read the message to which you are responding 
>again. Technical merit is specifically *not* a factor in deciding 
>publication of an Experimental or Informational document.
For those who believe this, please check out the technical merit of
draft-terrell-logic-analy-bin-ip-spec-ipv7-ipv8-05.txt, and ask yourselves
if this should be published as an RFC.

After that little exercise, you will appreciate that technical merit *is*
a factor in deciding publication of an Experimental or Informational document.
But - and this is important - THE DECISION IS MADE BY THE RFC EDITOR.
All we're doing here is creating advice.

                    Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Sun Apr  9 14:50:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10486
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 14:50:03 -0400 (EDT)
Received: from episteme-software.com (resnick1.qualcomm.com [63.250.90.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10433
	for <ietf@ietf.org>; Sun, 9 Apr 2000 14:46:38 -0400 (EDT)
Received: from resnick2.qualcomm.com (63.250.90.99) by 
 episteme-software.com with ESMTP (Eudora
 Internet Mail Server 3.0); Sun, 9 Apr 2000 13:46:10 -0500
Mime-Version: 1.0
X-Sender: resnick (Unverified)
Message-Id: <p04311404b5167f81c84f@resnick2.qualcomm.com>
In-Reply-To: <200004091824.MAA27489@calcite.rhyolite.com>
References: <200004091824.MAA27489@calcite.rhyolite.com>
X-Mailer: Eudora [Macintosh version 4.3a?]
Date: Sun, 9 Apr 2000 13:46:08 -0500
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: prohibiting RFC publication
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

On 4/9/00 at 12:24 PM -0600, Vernon Schryver wrote:

>>From: Pete Resnick <presnick@QUALCOMM.COM>
>>
>>...He suggested that we allow them to document current practice.
>
>Do I understand correctly that you think that 
>draft-terrell-ip-spec-ipv7-ipv8-addr-cls-02.txt
>should have been published as an RFC?

Uh, no. I see no deployed support for this document and therefore see 
no relevance to the Internet community to have this document 
published. If noone on the Internet is doing it and I'm therefore not 
going to see these packets on the Internet, then it's not relevant to 
me as a member of the community, which is the only test for 
Informational or Experimental.

>Since technical merit is irrelevant, you must be in favor of 
>publishing draft-terrell-logic-analy-bin-ip-spec-ipv7-ipv8-04.txt.

Did Eugene go and write some code I don't know about? Did you start 
routing this crap out on the net?

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
Eudora Engineering - QUALCOMM Incorporated
Ph: (217)337-6377 or (858)651-4478, Fax: (858)651-1102



From owner-ietf-outbound  Sun Apr  9 15:00:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA10618
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 15:00:03 -0400 (EDT)
Received: from episteme-software.com (resnick1.qualcomm.com [63.250.90.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10546
	for <ietf@ietf.org>; Sun, 9 Apr 2000 14:51:38 -0400 (EDT)
Received: from resnick2.qualcomm.com (63.250.90.99) by 
 episteme-software.com with ESMTP (Eudora
 Internet Mail Server 3.0); Sun, 9 Apr 2000 13:51:11 -0500
Mime-Version: 1.0
X-Sender: resnick (Unverified)
Message-Id: <p04311405b51680ab0e35@resnick2.qualcomm.com>
In-Reply-To: <4.3.1.2.20000409201728.021a3ce8@dokka.kvatro.no>
References: <200004082140.RAA25358@astro.cs.utk.edu>
 <200004082140.RAA25358@astro.cs.utk.edu>
 <4.3.1.2.20000409201728.021a3ce8@dokka.kvatro.no>
X-Mailer: Eudora [Macintosh version 4.3a?]
Date: Sun, 9 Apr 2000 13:51:09 -0500
To: Harald Tveit Alvestrand <Harald@Alvestrand.no>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: prohibiting RFC publication
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

On 4/9/00 at 8:21 PM +0200, Harald Tveit Alvestrand wrote:

>For those who believe this, please check out the technical merit of 
>draft-terrell-logic-analy-bin-ip-spec-ipv7-ipv8-05.txt, and ask 
>yourselves if this should be published as an RFC.

It should not. See my message to Vernon. But it's not because it 
lacks technical merit that it shouldn't be published.

>After that little exercise, you will appreciate that technical merit 
>*is* a factor in deciding publication of an Experimental or 
>Informational document.

Not if RFC 2026 is respected. I see nothing in 2026 allowing for this 
possibility.

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
Eudora Engineering - QUALCOMM Incorporated
Ph: (217)337-6377 or (858)651-4478, Fax: (858)651-1102



From owner-ietf-outbound  Sun Apr  9 16:00:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA11123
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 16:00:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11081
	for <ietf@ietf.org>; Sun, 9 Apr 2000 15:56:09 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id VAA28495;
	Sun, 9 Apr 2000 21:56:00 +0200
Message-Id: <4.3.1.2.20000409213951.09680780@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sun, 09 Apr 2000 21:41:50 +0200
To: Pete Resnick <presnick@qualcomm.com>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: prohibiting RFC publication
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
In-Reply-To: <p04311405b51680ab0e35@resnick2.qualcomm.com>
References: <4.3.1.2.20000409201728.021a3ce8@dokka.kvatro.no>
 <200004082140.RAA25358@astro.cs.utk.edu>
 <200004082140.RAA25358@astro.cs.utk.edu>
 <4.3.1.2.20000409201728.021a3ce8@dokka.kvatro.no>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 13:51 09.04.2000 -0500, Pete Resnick wrote:
>On 4/9/00 at 8:21 PM +0200, Harald Tveit Alvestrand wrote:
>
>>For those who believe this, please check out the technical merit of 
>>draft-terrell-logic-analy-bin-ip-spec-ipv7-ipv8-05.txt, and ask 
>>yourselves if this should be published as an RFC.
>
>It should not. See my message to Vernon. But it's not because it lacks 
>technical merit that it shouldn't be published.
>
>>After that little exercise, you will appreciate that technical merit *is* 
>>a factor in deciding publication of an Experimental or Informational document.
>
>Not if RFC 2026 is respected. I see nothing in 2026 allowing for this 
>possibility.

Section 4.2.3:

    The RFC Editor
    is expected to exercise his or her judgment concerning the editorial
    suitability of a document for publication with Experimental or
    Informational status, and may refuse to publish a document which, in
    the expert opinion of the RFC Editor, is unrelated to Internet
    activity or falls below the technical and/or editorial standard for
    RFCs.


                     Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Sun Apr  9 16:10:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA11322
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 16:10:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11258
	for <ietf@ietf.org>; Sun, 9 Apr 2000 16:04:08 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200004091953.EAA26781@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id EAA26781; Mon, 10 Apr 2000 04:53:40 +0900
Subject: Re: Patents
To: schulzrinne@cs.columbia.edu (Henning Schulzrinne)
Date: Mon, 10 Apr 0 4:53:39 JST
Cc: ietf@ietf.org
In-Reply-To: <38F0930F.1E42D638@cs.columbia.edu>; from "Henning Schulzrinne" at Apr 9, 100 11:44 pm
X-Mailer: ELM [version 2.3 PL11]
X-Loop: ietf@ietf.org

Henning;

> The current issue of The Economist discusses the state of the current
> patent system. It refers to a site www.bustpatents.com, which may be of
> interest in this regard.

As usual, the articles there are useless, because:

	Only a very small percentage of those participating in writing
	the articles have much detailed knowledge about technical
	realities of the Internet

	A very large percentage of those participating in writing
	the articles increase their income a lot, if business model
	patents were valid

	They lack international perspective, even though there is
	a small number of references to non-US patent systems.

							Masataka Ohta



From owner-ietf-outbound  Sun Apr  9 16:20:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA11483
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 16:20:02 -0400 (EDT)
Received: from mauve.innosoft.com (DSL107-055.brandx.net [209.55.107.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11268
	for <ietf@ietf.org>; Sun, 9 Apr 2000 16:05:56 -0400 (EDT)
From: ned.freed@innosoft.com
Received: from MAUVE.INNOSOFT.COM by MAUVE.INNOSOFT.COM (PMDF V6.1-1 #35243)
 id <01JO14NQF2SW00004F@MAUVE.INNOSOFT.COM> for ietf@ietf.org; Sun,
 09 Apr 2000 13:05:47 -0800 (PST)
Date: Sun, 09 Apr 2000 12:39:11 -0800 (PST)
Subject: Re: prohibiting RFC publication
In-reply-to: "Your message dated Sun, 09 Apr 2000 13:51:09 -0500"
 <p04311405b51680ab0e35@resnick2.qualcomm.com>
To: Pete Resnick <presnick@qualcomm.com>
Cc: Harald Tveit Alvestrand <Harald@Alvestrand.no>,
        Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Message-id: <01JO176H3M7K00004F@MAUVE.INNOSOFT.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
References: <200004082140.RAA25358@astro.cs.utk.edu>
 <200004082140.RAA25358@astro.cs.utk.edu>
 <4.3.1.2.20000409201728.021a3ce8@dokka.kvatro.no>
 <4.3.1.2.20000409201728.021a3ce8@dokka.kvatro.no>
X-Loop: ietf@ietf.org

> > For those who believe this, please check out the technical merit of
> > draft-terrell-logic-analy-bin-ip-spec-ipv7-ipv8-05.txt, and ask
> > yourselves if this should be published as an RFC.

> It should not. See my message to Vernon. But it's not because it
> lacks technical merit that it shouldn't be published.

> > After that little exercise, you will appreciate that technical merit
> > *is* a factor in deciding publication of an Experimental or
> > Informational document.

> Not if RFC 2026 is respected. I see nothing in 2026 allowing for this
> possibility.

You need to look harder. From RFC 2026:

  RFC publication is the direct responsibility of the
  RFC Editor, under the general direction of the IAB. 

And from RFC 1601bis:

   The RFC Editor executes editorial management and publication of the
   IETF "Request for Comment" (RFC) document series, which is the
   permanent document repository of the IETF. 

This makes it clear that the RFC Editor exercises editorial control over the
RFC series, but doesn't specify exactly what editorial control means. However,
the RFC Editor has interpreted its editorial responsibilities as involving
review with the distinct possibility of not publishing documents not believed
to be worth publishing for at least as long as I've been involved in the IETF.

I can recall discussions regarding the RFC Editor's refusal to publish
documents as early as 1992. And I suspect the lateness of this date is simply
due to my not having been involved in the IETF prior to 1989, faulty memory on
my part, or both.

Once again RFC 2026 doesn't specify the criteria the RFC Editor uses to decide
not to publish. But speaking as an observer of the process for over a decade,
the criteria I've seen the RFC Editor apply to potential RFCs over the years
has most definitely included an assessment of technical merit, among other
things.

Now, in recent years the RFC Editor, rather than simply accepting contributions
directly from authors and publishing them without community input, has chosen
to use the Internet Drafts mechanism as a means of getting community input on
whether or not a given document should be published. This is what is happening
here. 

I haven't always agreed with the RFC Editor's decision as to whether or not to
publish something (sometimes things have been published that I didn't think
were of sufficient quality, other times things have been rejected I didn't
think should have been), but I have never questioned the right of the RFC
Editor to refuse to publish something.

				Ned



From owner-ietf-outbound  Sun Apr  9 16:30:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA11591
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 16:30:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11275
	for <ietf@ietf.org>; Sun, 9 Apr 2000 16:06:22 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id OAA29431
	for ietf@ietf.org  env-from <vjs>;
	Sun, 9 Apr 2000 14:06:22 -0600 (MDT)
Date: Sun, 9 Apr 2000 14:06:22 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004092006.OAA29431@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: prohibiting RFC publication
X-Loop: ietf@ietf.org

> From: Pete Resnick <presnick@QUALCOMM.COM>

> >>...He suggested that we allow them to document current practice.


> >Do I understand correctly that you think that 
> >draft-terrell-ip-spec-ipv7-ipv8-addr-cls-02.txt
> >should have been published as an RFC?
>
> Uh, no. I see no deployed support for this document and therefore see 
> no relevance to the Internet community to have this document 
> published. If noone on the Internet is doing it and I'm therefore not 
> going to see these packets on the Internet, then it's not relevant to 
> me as a member of the community, which is the only test for 
> Informational or Experimental.

I guess your previous words were imprecise:

] Dave's message only said that technical merit has no bearing on 
] publication of Informational or Experimental RFCs.


> >Since technical merit is irrelevant, you must be in favor of 
> >publishing draft-terrell-logic-analy-bin-ip-spec-ipv7-ipv8-04.txt.
>
> Did Eugene go and write some code I don't know about? Did you start 
> routing this crap out on the net?

Exactly how much currently deployed support is needed to make technical
merit irrelevant?  I don't understand any of the three series of documents
from E.Terrell well enough to say they don't concern currently deployed
protocols.  Do you?

Do you mean to require that every RFC describe a currently deployed
protocol?  That would imply that a lot of RFC's should not be and should
have been published.

Since draft-cerpa-necp-02.txt seems to be more a proposal to extend and
replace ICP than a description of current practice, and therefore you're
not likely to have seen relevant packets, have you also changed your mind
about whether draft-cerpa-necp-02.txt should be published as an RFC?

If whether something is or is likely to be deployed is the primary
criterion for whether an I-D should be advanced, then techical merit is
relevant, provided you agree that technical merit can still affects
deployment.  Furthermore, non-technical questions such as the wisdom of
sanctioning wiretapping can affect deployment, and so by your criterion
and contrary to your summary of Dave's (Crocker?), must affect publication.

    ...

It is at best naive to say that the employeers of authors of I-D's are
irrelevant or that big companies don't cause documents to be proposed
regardless of technical merit.  It is silly to claim that an I-D that
comes from big companies is necessarily worthy of publication, or that
big companies don't hire more than their share of induhviduals.  Which
companies are pushing something is primary in trade rag editorial policies
(as it should be), but not (yet?) the IETF's.
It would be silly to say it is not good to document the worst big company
ideas (e.g. Microsoft's PPP wreckage) if they're popular.
It would be at best ignorant of history to claim publication by a
consortium is sufficient to cause a protocol to be deployed or even
implemented.

Are USC, Radware, Network Appliance, Akamai, Foundry Networks, Inktomi,
Alteon, and Novell such a consortium?  I'm mystified by the dueling
implications that this group represents a commercially or intellectually
dominant slice of the industry or that they're trying to push a brand
new idea on the net.

The affliations listed for authors of any I-D only weakly disclose their
professional afflications.  Many people, particularly those who've been
around a while, write from other than their current employeer's or
clients's domains.  Anyone who wants to make employers relevant needs to
get the rules changed to require explicit disclosure, and to realize
that many of us would oppose such a rule.

None of that is to say that the IETF can no long have have an editorial
policy with some human wisdom.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Sun Apr  9 16:50:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA11891
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 16:50:02 -0400 (EDT)
Received: from episteme-software.com (resnick1.qualcomm.com [63.250.90.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11839
	for <ietf@ietf.org>; Sun, 9 Apr 2000 16:46:04 -0400 (EDT)
Received: from resnick2.qualcomm.com (63.250.90.99) by 
 episteme-software.com with ESMTP (Eudora
 Internet Mail Server 3.0); Sun, 9 Apr 2000 15:45:33 -0500
Mime-Version: 1.0
X-Sender: resnick (Unverified)
Message-Id: <p04311407b516960d149a@resnick2.qualcomm.com>
In-Reply-To: <01JO176H3M7K00004F@MAUVE.INNOSOFT.COM>
References: <200004082140.RAA25358@astro.cs.utk.edu>
 <200004082140.RAA25358@astro.cs.utk.edu>
 <4.3.1.2.20000409201728.021a3ce8@dokka.kvatro.no>
 <4.3.1.2.20000409201728.021a3ce8@dokka.kvatro.no>
 <01JO176H3M7K00004F@MAUVE.INNOSOFT.COM>
X-Mailer: Eudora [Macintosh version 4.3a?]
Date: Sun, 9 Apr 2000 15:45:31 -0500
To: ned.freed@innosoft.com
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: prohibiting RFC publication
Cc: Harald Tveit Alvestrand <Harald@Alvestrand.no>,
        Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

On 4/9/00 at 12:39 PM -0800, ned.freed@innosoft.com wrote:

>[...]the RFC Editor exercises editorial control over the RFC series, 
>but doesn't specify exactly what editorial control means.

Actually, Harald's quote from 2026 does make it pretty clear:

Section 4.2.3:

    The RFC Editor
    is expected to exercise his or her judgment concerning the editorial
    suitability of a document for publication with Experimental or
    Informational status, and may refuse to publish a document which, in
    the expert opinion of the RFC Editor, is unrelated to Internet
    activity or falls below the technical and/or editorial standard for
    RFCs.

>However, the RFC Editor has interpreted its editorial 
>responsibilities as involving review with the distinct possibility 
>of not publishing documents not believed to be worth publishing for 
>at least as long as I've been involved in the IETF.

Absolutely. The question is on what basis that decision is made. 2026 
gives basically two criteria by which the RFC Editor may refuse 
publication:

1. It's unrelated to Internet activity. That's the one Dave and I 
(and others) have been pointing to. Clearly this draft is related to 
Internet activity; it's deployed technology, for better or for worse.

2. It falls below the technical and/or editorial standard for RFCs. 
Now, I think we all agree that the current document *does* fall below 
editorial standards insofar as it plays the "I am a standard" game in 
the text, making itself out to sound like a standard even though it's 
not. The document should be held up until that is fixed. But again, 
that's not Keith's main issue. He's complaining about "technical 
merit" (and sometimes legal or moral merit).

So, here I want to split a hair, but I think it's one worthy of 
splitting: RFC 2026 says "falls below the technical *standard* for 
RFCs". I don't believe what it's referring to here is whether the RFC 
Editor thinks that the document is describing a technically a bad 
idea, but rather whether the technical *quality* of the document 
(e.g., whether it is technically coherent, describes the protocol in 
appropriate detail, doesn't have the classic Gary Larson "...and then 
a miracle occurs..." clause in the middle of equation, etc.) is up to 
snuff. This seems like a good criterion to base publication on, 
whereas the other does not: It is always good to publish what I'm 
likely to have to deal with on the net, whether or not it's a good 
thing that it actually is going on.

It is of course a good thing not to standardize things that are 
technically bad ideas. But standardization is not at issue here. This 
is a question of how the RFC Editor should exercise its editorial 
judgement. 2026 lays out a reasonable guideline. I think Keith's 
request falls outside that (admittedly loose) bound.

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
Eudora Engineering - QUALCOMM Incorporated
Ph: (217)337-6377 or (858)651-4478, Fax: (858)651-1102



From owner-ietf-outbound  Sun Apr  9 17:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA12022
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 17:00:03 -0400 (EDT)
Received: from joy.songbird.com (IDENT:root@joy.songbird.com [208.184.79.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11958;
	Sun, 9 Apr 2000 16:53:30 -0400 (EDT)
Received: from free.88.106.bayarea.net (free.88.106.bayarea.net [205.219.88.106])
	by joy.songbird.com (8.9.3/8.9.3) with SMTP id NAA21827;
	Sun, 9 Apr 2000 13:53:23 -0700
X-Authentication-Warning: joy.songbird.com: free.88.106.bayarea.net [205.219.88.106] didn't use HELO protocol
Message-Id: <4.3.0.20000409134410.00c667b0@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Sun, 09 Apr 2000 13:52:31 -0700
To: Pete Resnick <presnick@qualcomm.com>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: prohibiting RFC publication
Cc: iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
In-Reply-To: <p04311401b51671988383@resnick2.qualcomm.com>
References: <200004082140.RAA25358@astro.cs.utk.edu>
 <200004082140.RAA25358@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 12:54 PM 4/9/00 -0500, Pete Resnick wrote:
>Dave's message only said that technical merit has no bearing on 
>publication of Informational or

This is a good example of the reason this apsect of debate is a major waste 
of time.

Although Pete is attempting to support my comments -- and I equally concur 
with his point of view -- in fact I did not say what he offers as the 
summary of my statement.  What I said was actually quite 
different.  However, further debating who said what is not where things 
should go.

In other words, folks, we all -- and Pete is better than average readers of 
this list, not worse -- tend to mis-read was is written and to argue 
polemically, rather than attentively and incrementally.

It is my understanding that the draft in question has been referred to a 
working group (wrec).  So, debate about that draft should move to that 
working group's list.

Except that...

That working group does not have this topic on it's charter and this seems 
an extraordinarily major and difficult topic, to leave as only an 
incidental goal of a working group.

It strikes me that it would be much, much more productive to fire up a 
working group focused on this topic, since we have known of the application 
level need for about 12 years, if not longer.

d/

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA



From owner-ietf-outbound  Sun Apr  9 17:20:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA12343
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 17:20:02 -0400 (EDT)
Received: from mauve.innosoft.com (DSL107-055.brandx.net [209.55.107.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12251
	for <ietf@ietf.org>; Sun, 9 Apr 2000 17:15:18 -0400 (EDT)
From: ned.freed@innosoft.com
Received: from MAUVE.INNOSOFT.COM by MAUVE.INNOSOFT.COM (PMDF V6.1-1 #35243)
 id <01JO14NQF2SW00004F@MAUVE.INNOSOFT.COM> for ietf@ietf.org; Sun,
 09 Apr 2000 14:15:14 -0800 (PST)
Date: Sun, 09 Apr 2000 13:39:24 -0800 (PST)
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
In-reply-to: "Your message dated Sat, 08 Apr 2000 15:59:57 -0400"
 <200004081959.e38Jxvk12760@black-ice.cc.vt.edu>
To: Valdis.Kletnieks@vt.edu
Cc: Keith Moore <moore@CS.UTK.EDU>, ietf@ietf.org
Message-id: <01JO19LLD80E00004F@MAUVE.INNOSOFT.COM>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
References: <200004081928.PAA24738@astro.cs.utk.edu>
 <200004081928.PAA24738@astro.cs.utk.edu>
X-Loop: ietf@ietf.org

> On Sat, 08 Apr 2000 15:28:12 EDT, Keith Moore said:
> > The simple fact is that I believe that the idea of interception proxies
> > does not have sufficient technical merit to be published by IETF, and
> > that IETF's publication of a document that tends to promote the use
> > of such devices would actually be harmful to Internet operation and
> > its ability to support applications.  Reasonable people can disagree

> Keith:  I think that there's been sufficient commentary here that
> interception proxies *do* have a place, both at the "server" end (for
> load-balancing server, etc), and at the "client" end.

I certainly agree that interception proxies at the server end are very useful,
and also note that as they are necessarily under the same administrative
control as the servers themselves, the various issues regarding content
alteration do not arise. In addition, since all users are likely to be
subjected to the sae proxy experience, it doesn't cause unecessary user
surprise. Indeed, this sort of thing seems to be an essential ingredient in
building really large "virtual servers", and having specifications that
facilitate doing this correctly would be a very good thing.

I also agree that interception proxies at the client end have their place,
although in such a case I don't think NECP is going to be applicable.

>  However, I am
> fully in agreement that interception proxies imposed anyplace other
> than either endpoint of the connection is a Bad Idea, because a third
> party can't be sure of the connection.  I'm willing to do something at
> my end, because I know that I wanted to connect to foobar.sprocket.com,
> and what semantics that involves.  foobar.sprocket.com can make
> decisions, based on its knowledge that any packet on port 7952 is
> either for their monkey-widget server, or invalid.  But my transit
> providers don't have any basis for making such decisions.

Exactly. And after having read this specification, I also think these issues
are glossed over.

> I'd have to vote against progressing it without language making this
> distinction as clear as possible.

Agreed. I think the right thing to do at this point is to revise the
specification. One possible approach, and the one I'd prefer, is to simply call
for NECP to only be used on the server side. Alternately, the distinction of
the location of the service could be made clearer and the perils of arbitrary
intermediate use spelled out.

I also see some technical issues in the protocol itself. For example, the
performance metric set seems inadequate, at least based on my past experience
with other load balancing systems. OTOH, the set is extensible, so this
could be corrected fairly easily.

I also don't see a way for servers to pass information about what security
options to use when a proxy routes a connection back to that server. This sort
of thing has proved to be quite useful in practice. Even worse, doing this
properly would require an encryption option; as far as I can see the present
protocol only allows for integrity checks. I'm also not entirely comfortable
with how integrity checking gets turned on to begin with -- it seems to me that
there are some loopholes that would allow unauthorized interceptions under
some allowed circumstances.

Finally, the mechansisms for controlling which connection get routed
where seem inadequate. In practice it is common to have a need for
proxies to do authentication and based on the authentication they do,
route the connection to a particular server. Some hooks for specifying
this sort of thing as the server comes online will be essential in many
applications.

However, I don't see any of these technical issues as impediments to
publication as informational or experimental.

				Ned



From owner-ietf-outbound  Sun Apr  9 17:30:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA12427
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 17:30:03 -0400 (EDT)
Received: from episteme-software.com (resnick1.qualcomm.com [63.250.90.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12383
	for <ietf@ietf.org>; Sun, 9 Apr 2000 17:23:29 -0400 (EDT)
Received: from resnick2.qualcomm.com (63.250.90.99) by 
 episteme-software.com with ESMTP (Eudora
 Internet Mail Server 3.0); Sun, 9 Apr 2000 16:23:00 -0500
Mime-Version: 1.0
X-Sender: resnick (Unverified)
Message-Id: <p04311408b5169c84997c@resnick2.qualcomm.com>
In-Reply-To: <200004092006.OAA29431@calcite.rhyolite.com>
References: <200004092006.OAA29431@calcite.rhyolite.com>
X-Mailer: Eudora [Macintosh version 4.3a?]
Date: Sun, 9 Apr 2000 16:22:55 -0500
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: prohibiting RFC publication
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

On 4/9/00 at 2:06 PM -0600, Vernon Schryver wrote:

>  > From: Pete Resnick <presnick@QUALCOMM.COM>
>
>  > Uh, no. I see no deployed support for this document and therefore see
>  > no relevance to the Internet community to have this document
>  > published. If noone on the Internet is doing it and I'm therefore not
>  > going to see these packets on the Internet, then it's not relevant to
>  > me as a member of the community, which is the only test for
>  > Informational or Experimental.
>
>I guess your previous words were imprecise:
>
>] Dave's message only said that technical merit has no bearing on
>] publication of Informational or Experimental RFCs.

Perhaps they were. My only intention was to say that Dave claimed 
only "relevance/interest for the Internet community" and not 
"technical merit" as the criterion for publication has Informational 
or Experimental. Total lack of deployment (or in this case of 
draft-terrell-, any indication that there even will be deployment) 
makes it irrelevant/uninteresting and therefore unsuitable for 
publication. (This leaves aside the issue of editorial reasons for 
not publishing, which apply to draft-cerpa-, and probably apply to 
draft-terrell- as well.)

>  > >Since technical merit is irrelevant, you must be in favor of
>  > >publishing draft-terrell-logic-analy-bin-ip-spec-ipv7-ipv8-04.txt.
>  >
>  > Did Eugene go and write some code I don't know about? Did you start
>  > routing this crap out on the net?
>
>Exactly how much currently deployed support is needed to make technical
>merit irrelevant?

Anywhere from zero to infinity. My argument is that technical merit 
is *always* irrelevant to suitability for publication as 
Informational or Experimental. The only criterion in the case of the 
Terrell documents is relevance/interest to the Internet community. 
None has (in those documents) been demonstrated.

>I don't understand any of the three series of documents from 
>E.Terrell well enough to say they don't concern currently deployed 
>protocols.  Do you?

I find our mutual lack of understanding (mine perhaps worse than 
your's), noone else's public claim of understanding, and the lack of 
documentation in these documents for where it is being used or what 
it effects a damn good indication of that lack of concern to 
currently deployed protocols.

>Do you mean to require that every RFC describe a currently deployed protocol?

No. Again, it's not deployment, but relevance/interest to the 
Internet community, that governs here. Sometimes that's squishy to 
get a hold of, I know, but I think we might both agree that Terrell 
doesn't have it.

>Since draft-cerpa-necp-02.txt seems to be more a proposal to extend and
>replace ICP than a description of current practice, and therefore you're
>not likely to have seen relevant packets, have you also changed your mind
>about whether draft-cerpa-necp-02.txt should be published as an RFC?

It depends. My understanding is that it is being deployed and has 
some high likelihood (given its proponents) of getting some wider 
spread use. If that understanding is incorrect and this protocol is 
heading for the dust bin, I would in fact change my mind about its 
suitability (on relevance grounds) for publication.

>If whether something is or is likely to be deployed is the primary
>criterion for whether an I-D should be advanced, then techical merit is
>relevant, provided you agree that technical merit can still affects
>deployment.

And here I was thinking that I was splitting hairs. Yes, technical 
merit may have impact on deployment, and therefore relevancy, and 
therefore worthiness of publication. But similarly I don't think that 
the earth's spinning is the cause of plant growth even though the 
earth's spinning does cause the sun to rise and the sun does cause 
plants to grow.

>It would be silly to say it is not good to document the worst big company
>ideas (e.g. Microsoft's PPP wreckage) if they're popular.

Absolutely. Exactly my point.

>It would be at best ignorant of history to claim publication by a
>consortium is sufficient to cause a protocol to be deployed or even
>implemented.
>
>Are USC, Radware, Network Appliance, Akamai, Foundry Networks, Inktomi,
>Alteon, and Novell such a consortium?  I'm mystified by the dueling
>implications that this group represents a commercially or intellectually
>dominant slice of the industry or that they're trying to push a brand
>new idea on the net.

Several members of that group do have an interesting dominance in an 
interesting slice of the industry which (given my minimal 
understanding of what the draft says) makes me believe that we are 
going to see these things widely enough deployed to be of interest, 
document or no document. Given that, the documentation seems like a 
good idea.

>Anyone who wants to make employers relevant...

Something of which I am not in favor. I was not saying that these 
folks employers are relevant to the publication decision; I was 
simply saying that the names caused me to believe that deployment was 
likely and therefore that the document was of interest and hence 
worthy of publication.

>None of that is to say that the IETF can no long have have an 
>editorial policy with some human wisdom.

Agreed.

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
Eudora Engineering - QUALCOMM Incorporated
Ph: (217)337-6377 or (858)651-4478, Fax: (858)651-1102



From owner-ietf-outbound  Sun Apr  9 17:40:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA12658
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 17:40:01 -0400 (EDT)
Received: from episteme-software.com (resnick1.qualcomm.com [63.250.90.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12431
	for <ietf@ietf.org>; Sun, 9 Apr 2000 17:30:07 -0400 (EDT)
Received: from resnick2.qualcomm.com (63.250.90.99) by 
 episteme-software.com with ESMTP (Eudora
 Internet Mail Server 3.0); Sun, 9 Apr 2000 16:29:38 -0500
Mime-Version: 1.0
X-Sender: resnick (Unverified)
Message-Id: <p04311409b516a593ba3f@resnick2.qualcomm.com>
In-Reply-To: <4.3.0.20000409134410.00c667b0@mail.bayarea.net>
References: <200004082140.RAA25358@astro.cs.utk.edu>
 <200004082140.RAA25358@astro.cs.utk.edu>
 <4.3.0.20000409134410.00c667b0@mail.bayarea.net>
X-Mailer: Eudora [Macintosh version 4.3a?]
Date: Sun, 9 Apr 2000 16:29:35 -0500
To: Dave Crocker <dcrocker@brandenburg.com>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: prohibiting RFC publication
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

[Removed IESG and RFC Editor from the recipients]

On 4/9/00 at 1:52 PM -0700, Dave Crocker wrote:

>Although Pete is attempting to support my comments -- and I equally 
>concur with his point of view -- in fact I did not say what he 
>offers as the summary of my statement.  What I said was actually 
>quite different.

I agree. I apologize for any mischaracterization, and I think my most 
recent response to Vernon explains my understanding of your position 
fairly. However:

>So, debate about that draft should move to that working group's list.

I will heed your advice and henceforth take any required discussion 
to private mail or to that list.

pr



From owner-ietf-outbound  Sun Apr  9 17:50:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA12798
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 17:50:02 -0400 (EDT)
Received: from joy.songbird.com (IDENT:root@joy.songbird.com [208.184.79.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12596
	for <ietf@ietf.org>; Sun, 9 Apr 2000 17:35:10 -0400 (EDT)
Received: from free.88.106.bayarea.net (free.88.106.bayarea.net [205.219.88.106])
	by joy.songbird.com (8.9.3/8.9.3) with SMTP id OAA22070
	for <ietf@ietf.org>; Sun, 9 Apr 2000 14:35:09 -0700
X-Authentication-Warning: joy.songbird.com: free.88.106.bayarea.net [205.219.88.106] didn't use HELO protocol
Message-Id: <4.3.0.20000409142730.00b88340@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Sun, 09 Apr 2000 14:35:15 -0700
To: ietf@ietf.org
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: recommendation against publication of
  draft-cerpa-necp-02.txt
In-Reply-To: <01JO19LLD80E00004F@MAUVE.INNOSOFT.COM>
References: <"Your message dated Sat, 08 Apr 2000 15:59:57 -0400" <200004081959.e38Jxvk12760@black-ice.cc.vt.edu>
 <200004081928.PAA24738@astro.cs.utk.edu>
 <200004081928.PAA24738@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 01:39 PM 4/9/00 -0800, ned.freed@innosoft.com wrote:
> >  However, I am
> > fully in agreement that interception proxies imposed anyplace other
> > than either endpoint of the connection is a Bad Idea, because a third
>
>Exactly. And after having read this specification, I also think these issues
>are glossed over.
>
> > I'd have to vote against progressing it without language making this
> > distinction as clear as possible.
>
>Agreed. I think the right thing to do at this point is to revise the
>specification. One possible approach, and the one I'd prefer, is to simply 
>call
>for NECP to only be used on the server side. Alternately, the distinction of

Let's remember that a major goal of these facilities is to get a user to a 
server that is 'close' to the user.  Having interception done only at 
distant, localized server farm facilities will not achieve that goal.

Further, I'm unclear about the architectural difference between (and 
apologies if things don't quite line up):

client --> Internet -> ISP -> Intercept -> subnet1 -> Server1
                                         -> subnet2 -> Server2
                                         -> subnet3 -> Server3

versus

client --> Internet -> ISP -> Intercept -> Internet -> Server1
                                         -> Internet -> Server2
                                         -> Internet -> Server3

>the location of the service could be made clearer and the perils of arbitrary
>intermediate use spelled out.

Perhaps the issue is not location, but coherent administration?


>I also see some technical issues in the protocol itself. For example, the
>performance metric set seems inadequate, at least based on my past experience
>with other load balancing systems. OTOH, the set is extensible, so this
>could be corrected fairly easily.

This would seem to walk down the path of considering this spec as a BASIS 
for pursuing a standard?

(The usual caveats, proscriptions, etc. apply with respect to IETF change 
control.  What we see now is likely not what they will get later...)


>However, I don't see any of these technical issues as impediments to
>publication as informational or experimental.

ack.

d/

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA



From owner-ietf-outbound  Sun Apr  9 18:40:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA13796
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 18:40:03 -0400 (EDT)
Received: from harrier.prod.itd.earthlink.net (harrier.prod.itd.earthlink.net [207.217.121.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13686;
	Sun, 9 Apr 2000 18:34:45 -0400 (EDT)
Received: from earthlink.net (pool0256.cvx19-bradley.dialup.earthlink.net [209.179.245.1])
	by harrier.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id PAA27570;
	Sun, 9 Apr 2000 15:34:43 -0700 (PDT)
Message-ID: <38F032B9.5B6B9403@earthlink.net>
Date: Sun, 09 Apr 2000 03:35:22 -0400
From: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
X-Mailer: Mozilla 4.08 [en] (Win95; I)
MIME-Version: 1.0
To: Dave Crocker <dcrocker@brandenburg.com>
CC: Pete Resnick <presnick@qualcomm.com>, iesg@ietf.org, ietf@ietf.org,
        rfc-ed@rfc-editor.org
Subject: Re: prohibiting RFC publication
References: <200004082140.RAA25358@astro.cs.utk.edu>
	 <200004082140.RAA25358@astro.cs.utk.edu> <4.3.0.20000409134410.00c667b0@mail.bayarea.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

g'day,

Dave Crocker wrote:
.  .  .

> It strikes me that it would be much, much more productive to fire up a
> working group focused on this topic, since we have known of the application
> level need for about 12 years, if not longer.

Which raises the interesting question as to what the participants would hope to
be the outcome of such a working group and whether we could possibly move
towards something ressembling a technical consensus, given the current polarity
of the debate. There are certainly more people than Keith who would brand the
relevant practices as evil and immoral. For sure you'd hear strong views
against endorsing transparent proxies, NATs and other things already touched
upon here over the past few months. I could mention a few more, at least as
controversial, which I'd see as coming into scope in the near future but
frankly I'm not personally willing to spend any energy trying to engage in any
form of consensus building on such things right now. The parties are simply too
far apart for me to expect there to be anything but grief at the other end.

I've seen us spend a lot of time engaging in working groups in which some
number of the participants has as their goal the invalidating of the underlying
concept or torpedoing the process itself. Having been there, done that and
collected the T-shirt a couple of times myself, I wouldn't go through that
again just because I have a soft spot, either for the IETF or in my head.

That isn't to say I disagree with you, Dave. There's definitely work to be done
here. It's just that this is one hairy tarball, and although there's going to
be lots done in this area over the next couple of years we've probably reached
a fork in the road where the IETF has to take stock of itself before it can
play a useful role. If it doesn't do that I predict that some of the major
architectural and implementation decisions in this particular subspace will be
taking place outside the IETF. And clearly, some would think that a good thing.




- peterd

--

----------------------------------------------------------------------
Peter Deutsch                           work email:  pdeutsch@cisco.com
Technical Leader
Content Services Business Unit       private: pdeutsch@earthlink.net
Cisco Systems                                     or  :  peterd@the.web

         Alcohol and calculus don't mix. Never drink and derive.
----------------------------------------------------------------------




From owner-ietf-outbound  Sun Apr  9 19:00:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA14041
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 19:00:03 -0400 (EDT)
Received: from mauve.innosoft.com (DSL107-055.brandx.net [209.55.107.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13965
	for <ietf@ietf.org>; Sun, 9 Apr 2000 18:54:25 -0400 (EDT)
From: ned.freed@innosoft.com
Received: from MAUVE.INNOSOFT.COM by MAUVE.INNOSOFT.COM (PMDF V6.1-1 #35243)
 id <01JO1CBTC14W0001TO@MAUVE.INNOSOFT.COM> for ietf@ietf.org; Sun,
 09 Apr 2000 15:54:21 -0800 (PST)
Date: Sun, 09 Apr 2000 15:42:41 -0800 (PST)
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
In-reply-to: "Your message dated Sun, 09 Apr 2000 14:35:15 -0700"
 <4.3.0.20000409142730.00b88340@mail.bayarea.net>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: ietf@ietf.org
Message-id: <01JO1D2H6IPG0001TO@MAUVE.INNOSOFT.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
References: <200004081928.PAA24738@astro.cs.utk.edu>
 <200004081928.PAA24738@astro.cs.utk.edu>
 <01JO19LLD80E00004F@MAUVE.INNOSOFT.COM>
X-Loop: ietf@ietf.org

> At 01:39 PM 4/9/00 -0800, ned.freed@innosoft.com wrote:
> > >  However, I am
> > > fully in agreement that interception proxies imposed anyplace other
> > > than either endpoint of the connection is a Bad Idea, because a third
> >
> >Exactly. And after having read this specification, I also think these issues
> >are glossed over.
> >
> > > I'd have to vote against progressing it without language making this
> > > distinction as clear as possible.
> >
> >Agreed. I think the right thing to do at this point is to revise the
> >specification. One possible approach, and the one I'd prefer, is to simply
> >call
> >for NECP to only be used on the server side. Alternately, the distinction of

> Let's remember that a major goal of these facilities is to get a user to a
> server that is 'close' to the user.  Having interception done only at
> distant, localized server farm facilities will not achieve that goal.

You are confusing topological locality with administrative locality. I was
talking about the latter, and so, I believe, was Valdis.

Indeed, the only reason I raised the security issues I did was to accomodate
the case where the proxies aren't topologically local to the servers. And
one of the things I see as missing from performance metric set is a means
of factoring in network QOS.

> Further, I'm unclear about the architectural difference between (and
> apologies if things don't quite line up):

> client --> Internet -> ISP -> Intercept -> subnet1 -> Server1
>                                          -> subnet2 -> Server2
>                                          -> subnet3 -> Server3

> versus

> client --> Internet -> ISP -> Intercept -> Internet -> Server1
>                                          -> Internet -> Server2
>                                          -> Internet -> Server3

> >the location of the service could be made clearer and the perils of arbitrary
> >intermediate use spelled out.

> Perhaps the issue is not location, but coherent administration?

In the case of proxies being "close" to the server, absolutely.

> >I also see some technical issues in the protocol itself. For example, the
> >performance metric set seems inadequate, at least based on my past experience
> >with other load balancing systems. OTOH, the set is extensible, so this
> >could be corrected fairly easily.

> This would seem to walk down the path of considering this spec as a BASIS
> for pursuing a standard?

I would not have a problem with pursuing standards work on protocols for load
balancing within a single administrative area. (This is not to say that
defining a protocol that can span administrations would be useless. It would be
very useful indeed, but I see so many potential ratholes it isn't funny.)

I suspect a case could be made for working on client-administered proxies, but
it seems fairly clear to me that this isn't what the present protocol
is about.

				Ned



From owner-ietf-outbound  Sun Apr  9 19:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA14403
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 19:20:01 -0400 (EDT)
Received: from joy.songbird.com (IDENT:root@joy.songbird.com [208.184.79.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14268;
	Sun, 9 Apr 2000 19:10:09 -0400 (EDT)
Received: from free.88.106.bayarea.net (free.88.106.bayarea.net [205.219.88.106])
	by joy.songbird.com (8.9.3/8.9.3) with SMTP id QAA22555;
	Sun, 9 Apr 2000 16:10:01 -0700
X-Authentication-Warning: joy.songbird.com: free.88.106.bayarea.net [205.219.88.106] didn't use HELO protocol
Message-Id: <4.3.0.20000409160229.00b83250@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Sun, 09 Apr 2000 16:09:47 -0700
To: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: prohibiting RFC publication
Cc: iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
In-Reply-To: <38F032B9.5B6B9403@earthlink.net>
References: <200004082140.RAA25358@astro.cs.utk.edu>
 <200004082140.RAA25358@astro.cs.utk.edu>
 <4.3.0.20000409134410.00c667b0@mail.bayarea.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 03:35 AM 4/9/00 -0400, Peter Deutsch in Mountain View wrote:
>Which raises the interesting question as to what the participants would 
>hope to
>be the outcome of such a working group and whether we could possibly move
>towards something ressembling a technical consensus, given the current 
>polarity

we've done it more than once, before.


>I've seen us spend a lot of time engaging in working groups in which some
>number of the participants has as their goal the invalidating of the 
>underlying
>concept or torpedoing the process itself. Having been there, done that and

First, let me compliment you on getting the 'has' correct.  I'm envious, 
since it took some time to parse the sentence carefully and discover that, 
once again, Canadian education beats the tar out of average US education...

There are always some people who object to the details of any interesting 
work.  Hence the real question is a) whether there is a substantially 
larger, interested constituency interested in making progress, and b) 
whether that larger constituency has the benefit of a working group chair 
able to manage the process well enough to keep the disrupters under 
control.  The larger and more diverse IETF does make this management task 
more difficult, but it is not impossible.


>That isn't to say I disagree with you, Dave. There's definitely work to be 
>done
>here. It's just that this is one hairy tarball, and although there's going to

Yes.  Lots of legitimate opportunity to get bogged down in the difficulty 
and complexity.  That also makes the task more interesting, doesn't it?


>be lots done in this area over the next couple of years we've probably reached
>a fork in the road where the IETF has to take stock of itself before it can
>play a useful role. If it doesn't do that I predict that some of the major
>architectural and implementation decisions in this particular subspace will be
>taking place outside the IETF. And clearly, some would think that a good 
>thing.

"some" always do.  however, while the IETF can not and should not try to do 
everything, this task seems entirely appropriate, since it requires a broad 
range of technical talents, across most of the stack, to get it right.

d/

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA



From owner-ietf-outbound  Sun Apr  9 19:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA14516
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 19:30:03 -0400 (EDT)
Received: from mauve.innosoft.com (DSL107-055.brandx.net [209.55.107.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14342
	for <ietf@ietf.org>; Sun, 9 Apr 2000 19:14:14 -0400 (EDT)
From: ned.freed@innosoft.com
Received: from MAUVE.INNOSOFT.COM by MAUVE.INNOSOFT.COM (PMDF V6.1-1 #35243)
 id <01JO1CBTC14W0001TO@MAUVE.INNOSOFT.COM> for ietf@ietf.org; Sun,
 09 Apr 2000 16:14:07 -0800 (PST)
Date: Sun, 09 Apr 2000 15:55:15 -0800 (PST)
Subject: Re: prohibiting RFC publication
In-reply-to: "Your message dated Sun, 09 Apr 2000 15:45:31 -0500"
 <p04311407b516960d149a@resnick2.qualcomm.com>
To: Pete Resnick <presnick@qualcomm.com>
Cc: ned.freed@innosoft.com, Harald Tveit Alvestrand <Harald@Alvestrand.no>,
        Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Message-id: <01JO1DQYP0RO0001TO@MAUVE.INNOSOFT.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
References: <200004082140.RAA25358@astro.cs.utk.edu>
 <200004082140.RAA25358@astro.cs.utk.edu>
 <4.3.1.2.20000409201728.021a3ce8@dokka.kvatro.no>
 <4.3.1.2.20000409201728.021a3ce8@dokka.kvatro.no>
 <01JO176H3M7K00004F@MAUVE.INNOSOFT.COM> <01JO176H3M7K00004F@MAUVE.INNOSOFT.COM>
X-Loop: ietf@ietf.org

> On 4/9/00 at 12:39 PM -0800, ned.freed@innosoft.com wrote:

> >[...]the RFC Editor exercises editorial control over the RFC series,
> >but doesn't specify exactly what editorial control means.

> Actually, Harald's quote from 2026 does make it pretty clear:

> Section 4.2.3:

>     The RFC Editor
>     is expected to exercise his or her judgment concerning the editorial
>     suitability of a document for publication with Experimental or
>     Informational status, and may refuse to publish a document which, in
>     the expert opinion of the RFC Editor, is unrelated to Internet
>     activity or falls below the technical and/or editorial standard for
>     RFCs.

> >However, the RFC Editor has interpreted its editorial
> >responsibilities as involving review with the distinct possibility
> >of not publishing documents not believed to be worth publishing for
> >at least as long as I've been involved in the IETF.

> Absolutely. The question is on what basis that decision is made. 2026
> gives basically two criteria by which the RFC Editor may refuse
> publication:

> 1. It's unrelated to Internet activity. That's the one Dave and I
> (and others) have been pointing to. Clearly this draft is related to
> Internet activity; it's deployed technology, for better or for worse.

> 2. It falls below the technical and/or editorial standard for RFCs.
> Now, I think we all agree that the current document *does* fall below
> editorial standards insofar as it plays the "I am a standard" game in
> the text, making itself out to sound like a standard even though it's
> not. The document should be held up until that is fixed. But again,
> that's not Keith's main issue. He's complaining about "technical
> merit" (and sometimes legal or moral merit).

Well, there's at least one more that's clearly called out in RFC 2026: If a
document is directly related to an area where there's ongoing IETF standards
activity it should not be published. (It isn't clear to me whether or not the
present document falls into this category.)

But regardless of the specifics in RFC 2026, my point is I've seen past cases
where the RFC Editor has refused publication where the apparent basis was none
of these things. And in particular, there have been cases where it was clearly
technical merit in Keith's sense of the term that was at issue. (I've also seen
cases where there were clear technical merit issues but publication happened
anyway.)

And nowhere does RFC 2026 say that the list of criteria for rejection it
provides is deemed to be exhaustive.

> So, here I want to split a hair, but I think it's one worthy of
> splitting: RFC 2026 says "falls below the technical *standard* for
> RFCs". I don't believe what it's referring to here is whether the RFC
> Editor thinks that the document is describing a technically a bad
> idea, but rather whether the technical *quality* of the document
> (e.g., whether it is technically coherent, describes the protocol in
> appropriate detail, doesn't have the classic Gary Larson "...and then
> a miracle occurs..." clause in the middle of equation, etc.) is up to
> snuff. This seems like a good criterion to base publication on,
> whereas the other does not: It is always good to publish what I'm
> likely to have to deal with on the net, whether or not it's a good
> thing that it actually is going on.

I'm sorry, but I think splitting this particular hair is a place we really
don't want to go. I'd much rather rely on the RFC Editor's judgement
as to whether or not to publish something than try to nail down an
exhaustive list of criteria for rejection (or acceptance).

And if you don't believe this is a really bad idea, I suggest that you read
"The Death of Common Sense". It argues this point rather forcefully IMO.

> It is of course a good thing not to standardize things that are
> technically bad ideas. But standardization is not at issue here. This
> is a question of how the RFC Editor should exercise its editorial
> judgement. 2026 lays out a reasonable guideline. I think Keith's
> request falls outside that (admittedly loose) bound.

I'm afraid I have to disagree. I think that Keith's assessment of technical
merit is a completely valid input to the decision process. The furthest I'd go
is to say it is by no means a decisive factor. However, in the case of the
present document I also think its more or less a moot point, as there are
plenty of other reasons why the document should not be published in its present
form, and once those are addressed the technical merit issue will have been
addressed as well, one way or the other.

				Ned



From owner-ietf-outbound  Sun Apr  9 19:40:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA14831
	for ietf-outbound.10@ietf.org; Sun, 9 Apr 2000 19:40:02 -0400 (EDT)
Received: from joy.songbird.com (IDENT:root@joy.songbird.com [208.184.79.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14623
	for <ietf@ietf.org>; Sun, 9 Apr 2000 19:32:15 -0400 (EDT)
Received: from free.88.106.bayarea.net (free.88.106.bayarea.net [205.219.88.106])
	by joy.songbird.com (8.9.3/8.9.3) with SMTP id QAA22671;
	Sun, 9 Apr 2000 16:32:15 -0700
X-Authentication-Warning: joy.songbird.com: free.88.106.bayarea.net [205.219.88.106] didn't use HELO protocol
Message-Id: <4.3.0.20000409162752.00b894c0@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Sun, 09 Apr 2000 16:31:58 -0700
To: ned.freed@innosoft.com
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: recommendation against publication of
  draft-cerpa-necp-02.txt
Cc: ietf@ietf.org
In-Reply-To: <01JO1D2H6IPG0001TO@MAUVE.INNOSOFT.COM>
References: <"Your message dated Sun, 09 Apr 2000 14:35:15 -0700" <4.3.0.20000409142730.00b88340@mail.bayarea.net>
 <200004081928.PAA24738@astro.cs.utk.edu>
 <200004081928.PAA24738@astro.cs.utk.edu>
 <01JO19LLD80E00004F@MAUVE.INNOSOFT.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 03:42 PM 4/9/00 -0800, ned.freed@innosoft.com wrote:

>You are confusing topological locality with administrative locality. I was
>talking about the latter, and so, I believe, was Valdis.

As my later comment meant to convey, I too was clear about the distinction, 
but yes I was definitely confused about the discussion underway.


>>This would seem to walk down the path of considering this spec as a BASIS
>>for pursuing a standard?
>
>I would not have a problem with pursuing standards work on protocols for load
>balancing within a single administrative area. (This is not to say that
>defining a protocol that can span administrations would be useless. It 
>would be
>very useful indeed, but I see so many potential ratholes it isn't funny.)

Sounds like a conveniently healthy constraint, then.


d/

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA



From owner-ietf-outbound  Mon Apr 10 01:31:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA23187
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 01:30:04 -0400 (EDT)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21787;
	Mon, 10 Apr 2000 01:20:18 -0400 (EDT)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id WAA17451;
	Sun, 9 Apr 2000 22:18:06 -0700 (PDT)
Received: from p7020-img-nt.cisco.com (fred-hm-dhcp1.cisco.com [171.69.128.116]) by rhino (SMI-8.6/CISCO.WS.1.1) with ESMTP id WAA02265; Sun, 9 Apr 2000 22:24:22 -0700
Message-Id: <4.3.1.2.20000409131927.02a6c100@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sun, 09 Apr 2000 10:33:14 -0400
To: Karl Auerbach <karl@CAVEBEAR.COM>
From: Fred Baker <fred@cisco.com>
Subject: Re: prohibiting RFC publication
Cc: IETF <ietf@ietf.org>, iesg@ietf.org, rfc-ed@rfc-editor.org
In-Reply-To: <Pine.LNX.4.21.0004081546410.25353-100000@npax.cavebear.com
 >
References: <4.3.0.20000408142118.00d31d50@mail.bayarea.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 03:51 PM 4/8/00 -0700, Karl Auerbach wrote:
>If the IETF engages in routine non-acceptance of "informational" documents
>on the basis of non-technical concerns the IETF will, I believe, lose its
>clear and loud voice when that voice is most needed to be heard.

That's a valid concern. The trade-off of interest to me is the one between 
publishing standards and publishing other documents. If you look at other 
bodies, their standards are clearly identifies - they only publish 
standards. We also publish other things, but do so under a nomenclature 
that is readily wrestled to the appearance of support as standards. We're 
all aware of cases where something was poublished as informational, 
experimental, etc, and the next press release announced support of that 
"standard", and of cases where RFCs, like IP on Avian Carriers, started 
winding up on RFPs simply because it was an RFC, and therefore "must" be 
the standard. This is another case of meaning dilution that I worry about.

To my recollection, the IESG has recommended very rarely that the RFC 
Editor literally not publish a document. We have added wording changes in 
the title, added IESG notes that say in effect "the IESG thinks this is a 
profoundly bad idea", and so on. The cases of not publishing at all that 
come quickly to mind are limited to Bill Simpson's documents about which 
there was an appeal last year. We didn't publish them because they did not 
give us license to change the text, the text said "this is the one true way 
to do" certain things related to IPSEC, and the IPSEC Working Group had 
similar-but-not-the-same documents. We felt that publishing both was likely 
to give the impression that Bill's informational documents were updating 
and changing the documents that the working group produced, and introduce a 
high probability of non-interoperable implementation. We didn't publish 
because we were of the opinion that it was better for the community.

I believe that the RFC Editor's also decides to not publish quite apart 
from IESG input, and does so when documents that come their lack substance. 
But their ethic tends to be that the RFC Series is the community memory, so 
recording things that do have substance is good even if they are bad ideas, 
because it let's someone else learn from the experiment.



From owner-ietf-outbound  Mon Apr 10 01:41:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA24488
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 01:40:04 -0400 (EDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23018
	for <ietf@ietf.org>; Mon, 10 Apr 2000 01:29:03 -0400 (EDT)
Received: from [192.168.124.51] (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id HAA29429; 
          Mon, 10 Apr 2000 07:28:49 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: paf@nix.swip.net
Message-Id: <p04310103b516abfc0577@[192.168.124.51]>
In-Reply-To: <4.3.0.20000409142730.00b88340@mail.bayarea.net>
References: <"Your message dated Sat, 08 Apr 2000 15:59:57 -0400"
 <200004081959.e38Jxvk12760@black-ice.cc.vt.edu>
 <200004081928.PAA24738@astro.cs.utk.edu>
 <200004081928.PAA24738@astro.cs.utk.edu>
 <4.3.0.20000409142730.00b88340@mail.bayarea.net>
Date: Mon, 10 Apr 2000 07:26:17 +0930
To: Dave Crocker <dcrocker@brandenburg.com>, ietf@ietf.org
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Subject: Re: recommendation against publication of  
 draft-cerpa-necp-02.txt
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 14.35 -0700 2000-04-09, Dave Crocker wrote:
>Let's remember that a major goal of these facilities is to get a 
>user to a server that is 'close' to the user.  Having interception 
>done only at distant, localized server farm facilities will not 
>achieve that goal.
>
>Further, I'm unclear about the architectural difference between (and 
>apologies if things don't quite line up):
>
>client --> Internet -> ISP -> Intercept -> subnet1 -> Server1
>                                         -> subnet2 -> Server2
>                                         -> subnet3 -> Server3
>
>versus
>
>client --> Internet -> ISP -> Intercept -> Internet -> Server1
>                                         -> Internet -> Server2
>                                         -> Internet -> Server3

In the first case, which Peter Deutch brought up with the cisco local 
director, I understand your picture being that the entity which 
provides the service running on Server1, Server2 and Server3 do 
provide either a hostname and/or IP-address which goes to a virtual 
host which resides "inside" the box which is doing the intercept. 
That box rewrites the IP headers including destination address etc 
and ships the packet to one of Server1, Server2 or Server3.

I.e. the client ask to contact the virtual host, and the virtual host 
is contacted.

In the second case (which is what I am opposing) the server provider 
does not have anything to do with the interception. He runs only 
Server1, while Server2 and Server3 are caches which the ISP chooses 
to redirect the packages to which are addressed to Server1.

That is from my point of view a big difference.

In the first case, the packets sent from the client reaches the 
destination (i.e. the interceptor, which really is not an interceptor 
at all, but some kind of NAT box like the cisco Local Director) while 
in the second case packages addressed to Server1 might not reach 
Server1 but Server2 or Server3.

     paf



From owner-ietf-outbound  Mon Apr 10 02:11:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA01692
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 02:10:02 -0400 (EDT)
Received: from scaup.prod.itd.earthlink.net (scaup.prod.itd.earthlink.net [207.217.121.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01644;
	Mon, 10 Apr 2000 02:08:40 -0400 (EDT)
Received: from earthlink.net (pool0898.cvx7-bradley.dialup.earthlink.net [209.178.167.133])
	by scaup.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id XAA23244;
	Sun, 9 Apr 2000 23:08:24 -0700 (PDT)
Message-ID: <38F09D18.FDE09076@earthlink.net>
Date: Sun, 09 Apr 2000 11:09:12 -0400
From: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
X-Mailer: Mozilla 4.08 [en] (Win95; I)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
CC: Karl Auerbach <karl@CAVEBEAR.COM>, IETF <ietf@ietf.org>, iesg@ietf.org,
        rfc-ed@rfc-editor.org
Subject: Re: prohibiting RFC publication
References: <4.3.0.20000408142118.00d31d50@mail.bayarea.net> <4.3.1.2.20000409131927.02a6c100@flipper.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

g'day,

Fred Baker wrote:

> At 03:51 PM 4/8/00 -0700, Karl Auerbach wrote:
> >If the IETF engages in routine non-acceptance of "informational" documents
> >on the basis of non-technical concerns the IETF will, I believe, lose its
> >clear and loud voice when that voice is most needed to be heard.
>
> That's a valid concern. The trade-off of interest to me is the one between
> publishing standards and publishing other documents. If you look at other
> bodies, their standards are clearly identifies - they only publish
> standards. We also publish other things, but do so under a nomenclature
> that is readily wrestled to the appearance of support as standards.

.  .  .

> I believe that the RFC Editor's also decides to not publish quite apart
> from IESG input, and does so when documents that come their lack substance.
> But their ethic tends to be that the RFC Series is the community memory, so
> recording things that do have substance is good even if they are bad ideas,
> because it let's someone else learn from the experiment.

Well put. As Dave has pointed out earlier this weekend, there is a burning need
for better, permanent access to the Drafts collection. If we had that, perhaps
much of this discussion might become moot, since some of the out-on-a-limb
stuff may be circulated in a less "official" form, but remain permanently and
readily accessible. I still see value in having documents come out as "Request
For Comments" in the traditional sense, but it certainly wouldn't  hurt to find
ways to better distinguish between the Standards track and other documents.

                                                    - peterd

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

Peter Deutsch                               work email:  pdeutsch@cisco.com
Technical Leader
Content Services Business Unit                 private: pdeutsch@earthlink.net
Cisco Systems                                     or  : peterd@the.web

             Alcohol and calculus don't mix. Never drink and derive.
--------------------------------------------------------------------------------





From owner-ietf-outbound  Mon Apr 10 02:31:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA01916
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 02:30:02 -0400 (EDT)
Received: from mail.perspex.com (IDENT:tlilley@mail.perspex.com [12.5.16.108])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01828;
	Mon, 10 Apr 2000 02:23:07 -0400 (EDT)
Received: from localhost (tlilley@localhost) by mail.perspex.com (8.8.7/8.7.3) with SMTP id GAA32123; Mon, 10 Apr 2000 06:33:06 GMT
Date: Mon, 10 Apr 2000 06:33:06 +0000 (/etc/localtime)
From: Tripp Lilley <tlilley@perspex.com>
To: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
cc: Fred Baker <fred@cisco.com>, Karl Auerbach <karl@CAVEBEAR.COM>,
        IETF <ietf@ietf.org>, iesg@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: prohibiting RFC publication
In-Reply-To: <38F09D18.FDE09076@earthlink.net>
Message-ID: <Pine.LNX.3.96.1000410063131.32096A-100000@mail.perspex.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Sun, 9 Apr 2000, Peter Deutsch in Mountain View wrote:

> readily accessible. I still see value in having documents come out as "Request
> For Comments" in the traditional sense, but it certainly wouldn't  hurt to find
> ways to better distinguish between the Standards track and other documents.

Here's a novel idea: we could stop calling them all "RFCs". Call them by
the designators they get once they're blessed (ie: STD, INF, EXP, etc.),
and stop ourselves citing them as RFC [0-9]+.

Change begins at home, as they say...

-- 
   Tripp Lilley  *  tripp@perspex.com  *  http://stargate.sg505.net/~tlilley/
------------------------------------------------------------------------------
  "I only counted on today's sunlight and snow,
   on the rain that dampened my face."

   - L.E. Modesitt, Jr., Adiamante



From owner-ietf-outbound  Mon Apr 10 02:41:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA02190
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 02:40:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01957;
	Mon, 10 Apr 2000 02:30:44 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3A6Ugj25898;
	Mon, 10 Apr 2000 02:30:42 -0400
Message-Id: <200004100630.e3A6Ugj25898@black-ice.cc.vt.edu>
To: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
cc: IETF <ietf@ietf.org>, iesg@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: prohibiting RFC publication 
In-reply-to: Your message of "Sun, 09 Apr 2000 11:09:12 EDT."
             <38F09D18.FDE09076@earthlink.net> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <4.3.0.20000408142118.00d31d50@mail.bayarea.net> <4.3.1.2.20000409131927.02a6c100@flipper.cisco.com>
            <38F09D18.FDE09076@earthlink.net>
Date: Mon, 10 Apr 2000 02:30:38 -0400
X-Loop: ietf@ietf.org

On Sun, 09 Apr 2000 11:09:12 EDT, Peter Deutsch in Mountain View said:
> Well put. As Dave has pointed out earlier this weekend, there is a burning need
> for better, permanent access to the Drafts collection. If we had that, perhaps
> much of this discussion might become moot, since some of the out-on-a-limb
> stuff may be circulated in a less "official" form, but remain permanently and

What would be *really* helpful is if the various revisions of the
drafts and the working group e-mail archives were together, so that
I could answer questions with "That doesn't work, it was tried in
draft-ietf-foobar-07.txt, tossed in -08.txt, see <here> for the
discussion why..."

What would it take to make it doable?

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Mon Apr 10 02:51:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA02306
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 02:50:02 -0400 (EDT)
Received: from scaup.prod.itd.earthlink.net (scaup.prod.itd.earthlink.net [207.217.121.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01977;
	Mon, 10 Apr 2000 02:30:58 -0400 (EDT)
Received: from earthlink.net (pool0898.cvx7-bradley.dialup.earthlink.net [209.178.167.133])
	by scaup.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id XAA29723;
	Sun, 9 Apr 2000 23:30:52 -0700 (PDT)
Message-ID: <38F0A25D.B446A5A1@earthlink.net>
Date: Sun, 09 Apr 2000 11:31:41 -0400
From: Peter Deutsch in Mountain View <pdeutsch@earthlink.net>
X-Mailer: Mozilla 4.08 [en] (Win95; I)
MIME-Version: 1.0
To: Tripp Lilley <tlilley@perspex.com>
CC: Fred Baker <fred@cisco.com>, Karl Auerbach <karl@CAVEBEAR.COM>,
        IETF <ietf@ietf.org>, iesg@ietf.org, rfc-ed@rfc-editor.org
Subject: Re: prohibiting RFC publication
References: <Pine.LNX.3.96.1000410063131.32096A-100000@mail.perspex.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

g'day,

Tripp Lilley wrote:

> On Sun, 9 Apr 2000, Peter Deutsch in Mountain View wrote:
>
> > readily accessible. I still see value in having documents come out as "Request
> > For Comments" in the traditional sense, but it certainly wouldn't  hurt to find
> > ways to better distinguish between the Standards track and other documents.
>
> Here's a novel idea: we could stop calling them all "RFCs". Call them by
> the designators they get once they're blessed (ie: STD, INF, EXP, etc.),
> and stop ourselves citing them as RFC [0-9]+.
>
> Change begins at home, as they say...

Yeah, although I'd personally hum for keeping the RFC nomencalture for the Standard
and Experimental class RFCs, as the name is understand to encompass that anyways. The
rest we could lump under something like "OFI" (Offered For Information? The marketing
guys here agree that they wont write code if I don't name products... ;-) Anyways, we
need to draw a clearer line between the standards which have been wrought by the
IETF, and information which has been captured and tamed, so to speak...

                    - peterd

--
--------------------------------------------------------------------------------
Peter Deutsch                                     work email:  pdeutsch@cisco.com
Technical Leader
Content Services Business Unit                 private: pdeutsch@earthlink.net
Cisco Systems                                              or  : peterd@the.web

             Alcohol and calculus don't mix. Never drink and derive.
--------------------------------------------------------------------------------




From owner-ietf-outbound  Mon Apr 10 03:01:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA02456
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 03:00:02 -0400 (EDT)
Received: from joy.songbird.com (IDENT:root@joy.songbird.com [208.184.79.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02244;
	Mon, 10 Apr 2000 02:44:48 -0400 (EDT)
Received: from free.88.106.bayarea.net (free.88.106.bayarea.net [205.219.88.106])
	by joy.songbird.com (8.9.3/8.9.3) with SMTP id XAA25333;
	Sun, 9 Apr 2000 23:44:43 -0700
X-Authentication-Warning: joy.songbird.com: free.88.106.bayarea.net [205.219.88.106] didn't use HELO protocol
Message-Id: <4.3.0.20000409225758.00ba5480@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Sun, 09 Apr 2000 23:01:38 -0700
To: IETF <ietf@ietf.org>, iesg@ietf.org, rfc-ed@rfc-editor.org
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: prohibiting RFC publication
In-Reply-To: <4.3.1.2.20000409131927.02a6c100@flipper.cisco.com>
References: <Pine.LNX.4.21.0004081546410.25353-100000@npax.cavebear.com >
 <4.3.0.20000408142118.00d31d50@mail.bayarea.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 10:33 AM 4/9/00 -0400, Fred Baker wrote:
>wrestled to the appearance of support as standards. We're all aware of 
>cases where something was poublished as informational, experimental, etc, 
>and the next press release announced support of that "standard", and of 
>cases where RFCs, like IP on Avian Carriers, started winding up on RFPs 
>simply because it was an RFC, and therefore "must" be the standard. This 
>is another case of meaning dilution that I worry about.

In absolute terms, these misuses/abuses of RFC reference are quite 
bothersome.

However they have been a fact of life pretty much forever.  Absent evidence 
that they have become a more serious problem than usual, the noise-factor 
of the misuses does not seem to cause enough community damage to warrant 
changing existing practise.

(I didn't read your note, Fred, as promoting a change, but others have been 
in favor of it.)

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA



From owner-ietf-outbound  Mon Apr 10 03:40:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA02960
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 03:40:01 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02898
	for <ietf@ietf.org>; Mon, 10 Apr 2000 03:31:57 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3A7Vsj06736;
	Mon, 10 Apr 2000 03:31:54 -0400
Message-Id: <200004100731.e3A7Vsj06736@black-ice.cc.vt.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: IETF <ietf@ietf.org>
Subject: Re: prohibiting RFC publication 
In-reply-to: Your message of "Sun, 09 Apr 2000 23:01:38 PDT."
             <4.3.0.20000409225758.00ba5480@mail.bayarea.net> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <Pine.LNX.4.21.0004081546410.25353-100000@npax.cavebear.com> <4.3.0.20000408142118.00d31d50@mail.bayarea.net>
            <4.3.0.20000409225758.00ba5480@mail.bayarea.net>
Date: Mon, 10 Apr 2000 03:31:54 -0400
X-Loop: ietf@ietf.org

On Sun, 09 Apr 2000 23:01:38 PDT, Dave Crocker <dcrocker@brandenburg.com>  said:
> At 10:33 AM 4/9/00 -0400, Fred Baker wrote:
> >cases where RFCs, like IP on Avian Carriers, started winding up on RFPs 
> >simply because it was an RFC, and therefore "must" be the standard. This 
> >is another case of meaning dilution that I worry about.
> 
> In absolute terms, these misuses/abuses of RFC reference are quite 
> bothersome.

The important question is "Does RFC2549 support prove to be self-limiting
in the marketplace".

I'm afraid I know the answer, and don't like it... ;(

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Mon Apr 10 07:01:50 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA04726
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 07:00:02 -0400 (EDT)
Received: from kediri.webindonesia.com (kediri.webindonesia.com [207.106.122.14])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA04664
	for <ietf@ietf.org>; Mon, 10 Apr 2000 06:53:12 -0400 (EDT)
Received: (qmail 8107 invoked by uid 1003); 10 Apr 2000 10:53:12 -0000
Date: Mon, 10 Apr 2000 06:53:12 -0400
From: "Rahmat M. Samik-Ibrahim" <ibrahim@kediri.webindonesia.com>
To: Milis IETF <ietf@ietf.org>
Subject: Need Clue: What for are I-Ds?
Message-ID: <20000410065312.A8062@kediri.webindonesia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95us
X-Loop: ietf@ietf.org


Hello:

For a while I have put an IETF-Announce archive that can be 
accessed through http://ittf.vlsm.org/announce.html

This archive is split into several categories. For example:
I-D Action      http://www.eGroups.com/messages/ietf-i-d_action/
Last Call       http://www.eGroups.com/messages/ietf-last_call/
Protocol Action http://www.eGroups.com/messages/ietf-protocol_action/
Document Action http://www.eGroups.com/messages/ietf-document_action/

However, I am still confused about what to do with an I-D since 
section 2.2 of BCP-9/1996 (the Internet Standard Process 3.00) 
and section 8 of BCP-25/1998 (IETF Working Group Guidelines 
and Procedures) do not say much about this issue.


1. Where to post a comment?

Should I send it to an author, all authors, the IETF list, 
the IESG, the RFC-Editor, or what? Or should I wait until 
a last call?


2. What for is a Last Call ?

I believe that section 8 of BCP-25 is widely accepted by
the community:
   "It is important to note that a Last-Call is intended
   as a brief, final check with the Internet community,
   to make sure that no important concerns have been
   missed or misunderstood. The Last-Call should
   not serve as a more general, in-depth review".
Therefore, what will be the point to review an I-D
at the Last Call stage?


3. What is the point to argue in the IETF list?

Section 3 of BCP-25 hinted that someone (the chair) should 
periodically post a summary, and another one (the document 
writer) should write down something. Since no one 
(publicly) summarized the IETF list and I-D drafts are 
seldomly written based on the discussion; what is the 
point to participate in a > 100 email burst discussion?


4. How to recognize the intention of the I-D author(s)?

An I-D has not always sufficent clues of the author(s)
intention. How to know that an I-D is on Standard Track?
(PS. AFAIK, individuals can submit I-Ds for an
Standard Track).


thanks,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- Bye bye Redmond! Next stop: San Jose...  http://linux.vlsm.org --



From owner-ietf-outbound  Mon Apr 10 07:10:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA04965
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 07:10:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04835
	for <ietf@ietf.org>; Mon, 10 Apr 2000 07:01:52 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id HAA10341;
        Mon, 10 Apr 2000 07:00:57 -0400 (EDT)
Message-Id: <200004101100.HAA10341@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Sun, 09 Apr 2000 14:35:15 PDT."
             <4.3.0.20000409142730.00b88340@mail.bayarea.net> 
Date: Mon, 10 Apr 2000 07:00:56 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Let's remember that a major goal of these facilities is to get a user to a 
> server that is 'close' to the user.  Having interception done only at 
> distant, localized server farm facilities will not achieve that goal.

granted, but...

an interception proxy that gets the user to a server that is 'close'
to that user (in the sense of network proximity), but 'distant' from the  
content provider (in the sense that it has a significant chance of
misrepresenting or damaging the content) is of dubious value.

and a technology that only works correctly on the server end seems
like a matter for the server's network rather than the public 
Internet - and therefore not something which should be standardized by IETF.

I do think there is potential for standardizing content replication
and the location of nearby servers which act on behalf of the content 
provider (with their explicit authorization, change-control, etc).

But IP-layer interception has some fairly significant limitations
for this application.  For one thing, different kinds of content on
the same server often have different consistency requirements, 
which become significant when your replicas are topologically distant
from one another.  If you treat an entire server as having a single 
IP address you probably don't get the granularity you need to implement 
efficient replication - you may spend more effort keeping your replicas
consistent (and propagating the necessary state from one to another)
than you save by replicating the content in the first place.  Obviously 
you can use multiple IP addresses, assigning different addresses to 
different kinds of content, but this also has limitations.  You can also 
get into problems when the network routing changes during a session or 
when the client itself is mobile. 

Bottom line is that IP-layer interception - even when done "right" - 
has fairly limited applicability for location of nearby content.
Though the technique is so widely mis-applied that it might still be 
useful to define what "right" means.

Keith



From owner-ietf-outbound  Mon Apr 10 08:00:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA06281
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 08:00:02 -0400 (EDT)
Received: from poptart.corp.home.net (poptart.svr.home.net [24.0.26.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06217
	for <ietf@ietf.org>; Mon, 10 Apr 2000 07:58:07 -0400 (EDT)
Received: from c8-a.snvl1.sfba.home.com ([24.0.25.50])
          by poptart.corp.home.net (Netscape Messaging Server 3.54)
           with ESMTP id AAA6E1; Mon, 10 Apr 2000 04:57:58 -0700
Message-Id: <4.2.0.58.20000410075207.0095d970@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Mon, 10 Apr 2000 07:59:24 +0100
To: Peter Deutsch in Mountain View <pdeutsch@EARTHLINK.NET>
From: RJ Atkinson <rja@inet.org>
Subject: Re: prohibiting RFC publication
Cc: IETF <ietf@ietf.org>
In-Reply-To: <38F09D18.FDE09076@earthlink.net>
References: <4.3.0.20000408142118.00d31d50@mail.bayarea.net>
 <4.3.1.2.20000409131927.02a6c100@flipper.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 16:09 09-04-00 , Peter Deutsch in Mountain View wrote:

>Well put. As Dave has pointed out earlier this weekend, there is a burning need
>for better, permanent access to the Drafts collection. If we had that, perhaps
>much of this discussion might become moot, since some of the out-on-a-limb
>stuff may be circulated in a less "official" form, but remain permanently and
>readily accessible. I still see value in having documents come out as "Request
>For Comments" in the traditional sense, but it certainly wouldn't  hurt to find
>ways to better distinguish between the Standards track and other documents.

         The notion of resurrecting the IEN series was mooted several years ago.  
However, the community as a whole did not support that notion with any significant
vigour.  So that hasn't happened.  My personal view is that there would be some
value to having the IENs alive and well, but there are issues with such an
idea.  Also, some items put out as I-Ds really well and truly ought not be in
any IETF-related archival documents.  While the folks in this discussion might
disagree on which drafts fall in that category, everyone believes that at least
some documents ought not be published in an IETF-related archival document series.

         That all noted, I think this conversation isn't really productive any longer
(if it ever was).  The I-D in question has been referred to an existing IETF
WG for review, which is a very normal kind of process that we're all familiar with.
I've never seen a draft document that failed to benefit from broad review, so I think
this has to be a good thing.

         All IMHO.

Ran
rja@inet.org



From owner-ietf-outbound  Mon Apr 10 08:10:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA06796
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 08:10:02 -0400 (EDT)
Received: from A4.JCK.COM (ns.jck.com [209.187.148.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06508
	for <ietf@ietf.org>; Mon, 10 Apr 2000 08:02:58 -0400 (EDT)
Received: from P2 ("port 2055"@[209.187.148.217])
 by a4.jck.com (PMDF V6.0-23 #40360) with ESMTP id <0FSS00A5NUTYP5@a4.jck.com>
 for ietf@ietf.org; Mon, 10 Apr 2000 08:03:35 -0400 (EDT)
Date: Mon, 10 Apr 2000 08:02:56 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: Need Clue: What for are I-Ds?
In-reply-to: <20000410065312.A8062@kediri.webindonesia.com>
To: "Rahmat M. Samik-Ibrahim" <ibrahim@kediri.webindonesia.com>
Cc: IETF <ietf@ietf.org>
Message-id: <1871036998.955353776@P2>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.0 (Win32)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

--On Monday, 10 April, 2000 06:53 -0400 "Rahmat M.
Samik-Ibrahim" <ibrahim@kediri.webindonesia.com> wrote:

> For a while I have put an IETF-Announce archive that can be 
> accessed through http://ittf.vlsm.org/announce.html
>...
> However, I am still confused about what to do with an I-D
> since  section 2.2 of BCP-9/1996 (the Internet Standard
> Process 3.00)  and section 8 of BCP-25/1998 (IETF Working
> Group Guidelines  and Procedures) do not say much about this
> issue.

In the general case, they are just drafts the author wants
exposed for general observation.   In principle, comments may
not even be of interest, although there would be little point in
posting one otherwise.   I-Ds are not publications of record and
have no intrinsic status.

> 1. Where to post a comment?
> 
> Should I send it to an author, all authors, the IETF list, 
> the IESG, the RFC-Editor, or what? Or should I wait until 
> a last call?

The instructions to I-D authors suggest that they include
explicit contact/ comment information (see
http://www.ietf.org/ietf/1id-guidelines.txt).  In its absence,
send notes to the authors or authors (your preference) -- the
author address information is there for a reason, and I-Ds will
not be posted (except in error) without it.  If it is a WG
document (draft-ietf-WGNAME-...) and your comments are
substantive, it would be reasonable to post to the WG list, but
the usual rules about interacting with WGs --watch for a while
first to try to be sure your comments are informed and on-topic
before general postings or meeting comments--- should apply.

Please do not copy the IETF, IESG, or RFC-Editor unless a notice
has been issued on IETF-announce soliciting such comments (or
they are the authors0: as long as they meet format, etc.,
requirements, I-Ds can be posted by anyone on just about any
topic and none of those groups need more clutter about documents
for which they are not, and may never be, responsible.

> 2. What for is a Last Call ?
> 
> I believe that section 8 of BCP-25 is widely accepted by
> the community:
>     "It is important to note that a Last-Call is intended
>     as a brief, final check with the Internet community,
>     to make sure that no important concerns have been
>     missed or misunderstood. The Last-Call should
>     not serve as a more general, in-depth review".
> Therefore, what will be the point to review an I-D
> at the Last Call stage?

Just what it says.   Note that there are really several
different types of Last Call (aounced by their text).  For WG
docs, or others for which there has already been announced prior
public, the expectation is that Last Calls will catch only
critical and overlooked issues.  For documents that are proposed
for Standards Track (including BCP in this case)  and that have
not been generally reviewed previously, the Last Call period is
longer, and more general comments are expected.  And the IESG
can choose to post anything --even Informational Documents-- for
Last Call: those postings generally indicate what information
the IESG is looking for and why.

> 3. What is the point to argue in the IETF list?
> 
> Section 3 of BCP-25 hinted that someone (the chair) should 
> periodically post a summary, and another one (the document 
> writer) should write down something. Since no one 
> (publicly) summarized the IETF list and I-D drafts are 
> seldomly written based on the discussion; what is the 
> point to participate in a > 100 email burst discussion?

An excellent question.  In my personal opinion, and in general,
the IETF list should be used for such general discussions only
if there is no other reasonable place to have it or if the topic
is so important as to need general community discussion (e.g.,
if one believes the WG has lost track of general issues or
principles and attempts to refocus it internally have failed.
Others have a broader view, and bring things to the IETF list
earlier, but such discussions can easily run wild (as we have
seen in recent days on other topics).  Each of these
high-traffic, repetitive, discussions causes people whose
opinions might be needed on future subjects to desubscribe,
which is usually a net loss to the IETF community.

> 4. How to recognize the intention of the I-D author(s)?
> 
> An I-D has not always sufficent clues of the author(s)
> intention. How to know that an I-D is on Standard Track?
> (PS. AFAIK, individuals can submit I-Ds for an
> Standard Track).

If it isn't clear, and it is important, ask the author in
private email.  But, as we have discussed at some length
privately, unless the document is working group material, be
prepared to accept the author's answer: the nature of
non-WG-I-Ds is that neither you, nor anyone else, have the right
to insist that the author include material, other than that
required by RFC-2026, that lies outside the author's
preferences/ intent for the document. 

    john




From owner-ietf-outbound  Mon Apr 10 09:00:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA08922
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 09:00:03 -0400 (EDT)
Received: from mx01-ext.netapp.com (mx01-ext.netapp.com [198.95.224.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA08885
	for <ietf@ietf.org>; Mon, 10 Apr 2000 08:59:39 -0400 (EDT)
Received: (qmail 19675 invoked from network); 10 Apr 2000 13:17:40 -0000
Received: from herra.netapp.com (HELO herra.corp.netapp.com) (198.95.224.184)
  by mx01-ext.netapp.com with SMTP; 10 Apr 2000 13:17:40 -0000
Received: from johnm ([192.168.199.78])
	by herra.corp.netapp.com (8.9.3/8.9.3/NTAP-1.0) with ESMTP id FAA23565;
	Mon, 10 Apr 2000 05:58:57 -0700 (PDT)
Message-Id: <4.2.0.58.20000410141804.00c35ab0@pop.netapp.com>
X-Sender: jmartin@pop.netapp.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Mon, 10 Apr 2000 14:57:19 +0200
To: Keith Moore <moore@cs.utk.edu>, rfc-ed@rfc-editor.org
From: John Martin <jmartin@netapp.com>
Subject: Re: recommendation against publication of
  draft-cerpa-necp-02.txt
Cc: iesg@ietf.org, ietf@ietf.org
In-Reply-To: <200004061641.MAA15198@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

I have held off commenting until I saw what the IETF community at large 
would have to say. Disclosure: I work for Network Appliance, was involved 
in the very early stages (though not latterly) of NECP and fully support 
its publication as an Informational RFC. I am also co-chair of WREC.

As has happened when this document was previously discussed by the IESG, 
the discussion inevitably takes a turn towards a discussion of 
"transparent" caching (latterly renamed "interception proxies" by WREC). 
Let me be absolutely clear, NECP is about communication between server 
load-balancers (SLB) and the back-end servers they speak to. Nothing more, 
nothing less. The fact that one common use of these is for caching proxies, 
and that these are used as an example, does not mean that NECP in any way 
specifies how "transparent" or "redirection" takes place.

[In fact, the most common deployment of these type of service load 
balancers is non-transparent (i.e. where the user configures their browser 
with a proxy IP address which is, in fact, a load-balancing element talking 
to a number of back-end servers). For a discussion of "transparent" versus 
"non-transparent" proxies, please refer to draft-ietf-wrec-taxonomy-03.txt.]

However, that is by far not the only application. DNS, web servers and 
firewall load balancing are the three other main applications for SLBs.

Now, let me address each of the original concerns in turn. Note that I have 
done this privately to Keith on many occasions as well as to the IESG, IAB 
and others on the WREC WG list.

At 12:41 PM 06/04/00 -0400, Keith Moore wrote:
>1. The document repeatedly, and misleadingly, refers to NECP as a
>standard.  I do not believe this is appropriate for a document
>which is not on the IETF standards track.  It also refers to
>some features as "mandatory" even though it's not clear what
>it means for a non-standard to have mandatory features.

The document is not an IETF standard but it does describe a protocol. For 
protocols to work correctly, there must be certain "mandatory" minimal 
requirements on those implementing that protocol.

I can see one or two places where the word "standard" might be 
misinterpreted by readers if used out of context.

Section 5.2, 5.2.1, 5.2.2, 5.5.1

       "The version number of the protocol defined by this standard is 1."

       "All implementations that adhere to the standard specified in
        this document MUST set the version number to 0x1."

       "This type of payload has no structure imposed by this standard."

         "For reasons explained in Section 6.11, this standard only
        defines a single performance query type that MUST be
        implemented by all NECP nodes:"

I see no problem with changing these. In most cases, simply replacing the 
word "standard" with the word "protocol" would convey the correct meaning 
beyond any reasonable doubt.

>2. A primary purpose of the NECP protocol appears to be to
>facilitate the operation of so-called interception proxies.

Wrong. The primary purpose of NECP is to facilitate a load-balancing 
between SLBs and the services to which they direct traffic. "so-called 
interception proxies" are just one such service.

>Such  proxies violate the Internet Protocol in several ways:

This is not about those proxies - that is a different argument.

I  don't think it is appropriate to be drawn into an argument about the 
rights and wrongs of "interception proxies" when discussing NECP. I am more 
than happy to justify their existence - with hard facts, of course - in a 
separate thread.

Regards,
John

---------------------------------------------------------------
Network Appliance           Direct / Voicemail: +31 23 567 9615
Kruisweg 799                               Fax: +31 23 567 9699
NL-2132 NG Hoofddorp               Main Office: +31 23 567 9600
---------------------------------------------------------------



From owner-ietf-outbound  Mon Apr 10 09:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA11693
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 09:50:03 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11330
	for <ietf@ietf.org>; Mon, 10 Apr 2000 09:42:27 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3ADgLj24462;
	Mon, 10 Apr 2000 09:42:21 -0400
Message-Id: <200004101342.e3ADgLj24462@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Keith Moore <moore@CS.UTK.EDU>
cc: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Mon, 10 Apr 2000 07:00:56 EDT."
             <200004101100.HAA10341@astro.cs.utk.edu> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200004101100.HAA10341@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 10 Apr 2000 09:42:21 -0400
X-Loop: ietf@ietf.org

On Mon, 10 Apr 2000 07:00:56 EDT, Keith Moore said:
> and a technology that only works correctly on the server end seems
> like a matter for the server's network rather than the public 
> Internet - and therefore not something which should be standardized by IETF.

Much the same logic can be applied to NAT (the way it's usually implemented).

Both have issues, both have proponents, and both will be done even more brokenly
if there's no standard for them.

Personally, I'd rather have the IETF issue verbiage saying "Do it this way",
than have 50 million content providers all implement it in subtly different
and broken ways.

"You are trapped in a twisty little maze of proxies, all different..." ;)

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Mon Apr 10 10:10:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA12930
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 10:10:02 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12514
	for <ietf@ietf.org>; Mon, 10 Apr 2000 10:03:18 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id KAA06678
	for <ietf@ietf.org>; Mon, 10 Apr 2000 10:02:24 -0400
Sender: francis@localhost.localdomain
Message-ID: <38F1DEEF.9C25643A@ecal.com>
Date: Mon, 10 Apr 2000 10:02:24 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: prohibiting RFC publication
References: <4.3.0.20000408142118.00d31d50@mail.bayarea.net>
	 <4.3.1.2.20000409131927.02a6c100@flipper.cisco.com> <4.2.0.58.20000410075207.0095d970@avarice.inner.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

RJ Atkinson wrote:

> While the folks in this discussion might
> disagree on which drafts fall in that category, everyone believes that at least
> some documents ought not be published in an IETF-related archival document series.

Mmm...I think the patent thread pointed out that, if we archived all the I-Ds, it'd be a
good repository for patent examiners to search.  Since some people patent bad ideas,
archiving bad ideas would be useful there.

--
/===============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own. |
|Chief Scientist |==============================================|
|eCal Corp.      |All your problems can be solved by not caring!|
|francis@ecal.com|                                              |
\===============================================================/





From owner-ietf-outbound  Mon Apr 10 10:41:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA14668
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 10:40:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14519
	for <ietf@ietf.org>; Mon, 10 Apr 2000 10:37:32 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id KAA11152;
        Mon, 10 Apr 2000 10:36:50 -0400 (EDT)
Message-Id: <200004101436.KAA11152@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Valdis.Kletnieks@vt.edu
cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Mon, 10 Apr 2000 09:42:21 EDT."
             <200004101342.e3ADgLj24462@black-ice.cc.vt.edu> 
Date: Mon, 10 Apr 2000 10:36:50 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> > and a technology that only works correctly on the server end seems
> > like a matter for the server's network rather than the public 
> > Internet - and therefore not something which should be standardized by IETF.
> 
> Much the same logic can be applied to NAT (the way it's usually implemented).

true.
 
> Both have issues, both have proponents, and both will be done even more 
> brokenly if there's no standard for them.

yes, this is the dilemma.  IETF has a hard time saying "if you're going to 
do this bad thing, please do it in this way".  for example, it's unlikely
that the vendors of products which do the bad thing would consent to
such a statement.  and if you take out the language that says "this is bad"
then the vendors will cite the RFC as if it were a standard.

and given that NATs are already in blatent violation of the standards,
it's not clear why NAT vendors would adhere to standards for NATs.
nor is it clear how reasonable standards for NATs could say anything 
other than "modification of IP addresses violates the IP standard;
you therefore MUST NOT do this".

> Personally, I'd rather have the IETF issue verbiage saying "Do it this way",
> than have 50 million content providers all implement it in subtly different
> and broken ways.

not sure what content providers have to do with this -
if content providers harm their own content, it's not clear why IETF 
should care - there are ample incentives for them to fix their own problems.

Keith



From owner-ietf-outbound  Mon Apr 10 10:50:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA15373
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 10:50:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14645
	for <ietf@ietf.org>; Mon, 10 Apr 2000 10:40:00 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id KAA11242;
        Mon, 10 Apr 2000 10:39:07 -0400 (EDT)
Message-Id: <200004101439.KAA11242@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: RJ Atkinson <rja@inet.org>
cc: Peter Deutsch in Mountain View <pdeutsch@EARTHLINK.NET>,
        IETF <ietf@ietf.org>
Subject: Re: prohibiting RFC publication 
In-reply-to: Your message of "Mon, 10 Apr 2000 07:59:24 BST."
             <4.2.0.58.20000410075207.0095d970@avarice.inner.net> 
Date: Mon, 10 Apr 2000 10:39:06 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> The I-D in question has been referred to an existing IETF WG for review,

that assertion was made, but not confirmed by the ADs.
is it really true?  it seems odd because it really isn't in scope for wrec.

Keith



From owner-ietf-outbound  Mon Apr 10 11:10:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA16476
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 11:10:03 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16366
	for <ietf@ietf.org>; Mon, 10 Apr 2000 11:07:57 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id JAA27991
	for ietf@ietf.org  env-from <vjs>;
	Mon, 10 Apr 2000 09:07:58 -0600 (MDT)
Date: Mon, 10 Apr 2000 09:07:58 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004101507.JAA27991@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
X-Loop: ietf@ietf.org

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

> ...
> But IP-layer interception has some fairly significant limitations
> for this application. ...

There's a technical problem with IP intercepting that I've not seen
mentioned, including in the draft.  Any intercepting based on TCP or UDP
port numbers or that makes any assumptions about TCP or UDP port numbers
will have problems, because of IPv4 fragmentation.  It seems plausible
that intercepting done by/for the server(s) would want to redirect all
traffic for a given IP address, and so not be affected by port numbers.
(Thus, it may make sense for the draft to not mention the issue.)

However, "transparent" HTTP proxy and email filtering and rewriting schemes
such as AOL's that need to intercept only traffic to a particular port
cannot do the right thing if the client has a private FDDI or 802.5 network
(e.g.  behind a NAT box) or has an ordinary 802.3 network but follows the
widespread, bogus advice to use a small PPP MTU.

Yes, I realize IPv6 doesn't have fragmentation, but most if not all of
the distant-from-server IP interception schemes sound unlikely to work
with IPv6 for other reasons.


> Bottom line is that IP-layer interception - even when done "right" - 
> has fairly limited applicability for location of nearby content.
> Though the technique is so widely mis-applied that it might still be 
> useful to define what "right" means.

That sounds overly optimistic.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Mon Apr 10 11:50:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA19366
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 11:50:03 -0400 (EDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18787
	for <ietf@ietf.org>; Mon, 10 Apr 2000 11:39:52 -0400 (EDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e3AFawF25205;
	Mon, 10 Apr 2000 17:36:58 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id RAA12973;
	Mon, 10 Apr 2000 17:36:57 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id RAA14274;
	Mon, 10 Apr 2000 17:42:16 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200004101542.RAA14274@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of Mon, 10 Apr 2000 09:07:58 MDT.
             <200004101507.JAA27991@calcite.rhyolite.com> 
Date: Mon, 10 Apr 2000 17:42:16 +0200
Sender: Francis.Dupont@enst-bretagne.fr
X-Loop: ietf@ietf.org

 In your previous mail you wrote:

   > But IP-layer interception has some fairly significant limitations
   > for this application. ...
   
   There's a technical problem with IP intercepting that I've not seen
   mentioned, including in the draft.  Any intercepting based on TCP or UDP
   port numbers or that makes any assumptions about TCP or UDP port numbers
   will have problems, because of IPv4 fragmentation.  It seems plausible
   that intercepting done by/for the server(s) would want to redirect all
   traffic for a given IP address, and so not be affected by port numbers.
   (Thus, it may make sense for the draft to not mention the issue.)
   
=> the first fragment has 8 bytes or more of payload, then the port numbers.
And other fragments share the same ID then it is possible to apply
the same action on all the fragments if they follow the same path at
the interception point.
 This can be hairy if fragments are not in the usual order, for instance
if someone sends the last one first (this is not as stupid as it seems
because the last fragment provides the whole length of the packet).

   However, "transparent" HTTP proxy and email filtering and rewriting schemes
   such as AOL's that need to intercept only traffic to a particular port
   cannot do the right thing if the client has a private FDDI or 802.5 network
   (e.g.  behind a NAT box) or has an ordinary 802.3 network but follows the
   widespread, bogus advice to use a small PPP MTU.
   
=> but fragmentation is not the best way to fight against "transparent"
proxies (:-)...

   Yes, I realize IPv6 doesn't have fragmentation
   
=> IPv6 has fragmentation, but only from end to end (no fragmentation
en route). Packet IDs are used by IPv6 only with fragmentation (they
are in fragmentation headers) too...

   but most if not all of the distant-from-server IP interception
   schemes sound unlikely to work with IPv6 for other reasons.

=> I'd like that this is true (another reason to switch to IPv6 :-)
but the only thing which is broken by interception is authentication
(IPSec is mandatory to implement, not (yet) to use with IPv6).
Encryption isn't really "transparent" proxies friendly too (:-).

Regards

Francis.Dupont@enst-bretagne.fr



From owner-ietf-outbound  Mon Apr 10 12:00:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA20254
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 12:00:03 -0400 (EDT)
Received: from gallium.network-alchemy.com (Gallium.Network-Alchemy.COM [199.46.17.139])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19105
	for <ietf@ietf.org>; Mon, 10 Apr 2000 11:45:11 -0400 (EDT)
Received: from gallium.network-alchemy.com (localhost.network-alchemy.com [127.0.0.1])
	by gallium.network-alchemy.com (8.8.8/8.8.8) with ESMTP id IAA07027;
	Mon, 10 Apr 2000 08:44:40 -0700 (PDT)
	(envelope-from ddp@network-alchemy.com)
Message-Id: <200004101544.IAA07027@gallium.network-alchemy.com>
To: Keith Moore <moore@cs.utk.edu>
cc: Dave Crocker <dcrocker@brandenburg.com>, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Mon, 10 Apr 2000 07:00:56 EDT."
             <200004101100.HAA10341@astro.cs.utk.edu> 
Date: Mon, 10 Apr 2000 08:44:40 -0700
From: "Derrell D. Piper" <ddp@Network-Alchemy.COM>
X-Loop: ietf@ietf.org

> Bottom line is that IP-layer interception - even when done "right" - 
> has fairly limited applicability for location of nearby content.
> Though the technique is so widely mis-applied that it might still be 
> useful to define what "right" means.

And there you have the argument for publishing this document.  I much prefer a
model where we allow for free exchange of ideas, even bad ones.  I tend to
believe that if someone took the time to write up a document that there's
probably some reason for it.  So let's call this an experimental RFC and get
on with life.  Isn't that what the experimental category denotes?

Derrell



From owner-ietf-outbound  Mon Apr 10 12:10:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA21176
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 12:10:02 -0400 (EDT)
Received: from saint.heaven.net (saint.heaven.net [198.69.28.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19395
	for <ietf@ietf.org>; Mon, 10 Apr 2000 11:50:16 -0400 (EDT)
Received: (from stpeters@localhost)
	by saint.heaven.net (8.9.3/8.9.3) id LAA19732;
	Mon, 10 Apr 2000 11:50:06 -0400
From: "Dick St.Peters" <stpeters@NetHeaven.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14577.63533.727116.329186@saint.heaven.net>
Date: Mon, 10 Apr 2000 11:50:05 -0400 (EDT)
To: ietf@ietf.org
Reply-To: <ietf@ietf.org>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
In-Reply-To: <p04310103b516abfc0577@[192.168.124.51]>
References: <"Your message dated Sat, 08 Apr 2000 15:59:57 -0400"
 <200004081959.e38Jxvk12760@black-ice.cc.vt.edu>
	<200004081928.PAA24738@astro.cs.utk.edu>
	<4.3.0.20000409142730.00b88340@mail.bayarea.net>
	<p04310103b516abfc0577@[192.168.124.51]>
X-Mailer: VM 6.72 under Emacs 19.34.1
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> >Let's remember that a major goal of these facilities is to get a 
> >user to a server that is 'close' to the user.  Having interception 
> >done only at distant, localized server farm facilities will not 
> >achieve that goal.
 ...
> >client --> Internet -> ISP -> Intercept -> Internet -> Server1
> >                                         -> Internet -> Server2
> >                                         -> Internet -> Server3
> 
> In the second case (which is what I am opposing) the server provider 
> does not have anything to do with the interception. He runs only 
> Server1, while Server2 and Server3 are caches which the ISP chooses 
> to redirect the packages to which are addressed to Server1.

That's an assumption that's not always valid.  There are cases in
existence now where a service provider *pays* the ISP to run a local
mirror, leading to

client --> Internet -> ISP -> Intercept -> Internet -> Server1
                                        ->  subnet  -> Server2

It would be entirely possible for the service provider, having paid
the ISP not to get traffic from the ISP's clients, to block that
traffic - or limit its bandwidth.

Consider the progession:

client --> Internet -> ISP -> Router -> 56k  -> Server1
                                     -> T3   -> Server1

client --> Internet -> ISP -> Intercept -> 56k  -> Server1
                                        -> T3   -> Server2

client --> Internet -> ISP -> Intercept -> Internet -> Server1
                                        ->  subnet  -> Server2

What is the fundamental difference between choosing the best path and
choosing the best source?  Arguments that the latter breaks the IP
model are simply arguments that the IP model is broken for today's
Internet and will be even more broken for tomorrow's.  The IETF can
fix the model ... or leave that to someone else.

--
Dick St.Peters, stpeters@NetHeaven.com 
Gatekeeper, NetHeaven, Saratoga Springs, NY
Saratoga/Albany/Amsterdam/BoltonLanding/Cobleskill/Greenwich/
GlensFalls/LakePlacid/NorthCreek/Plattsburgh/...
    Oldest Internet service based in the Adirondack-Albany region



From owner-ietf-outbound  Mon Apr 10 12:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA22016
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 12:20:02 -0400 (EDT)
Received: from mx01-ext.netapp.com (mx01-ext.netapp.com [198.95.224.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA20193
	for <ietf@ietf.org>; Mon, 10 Apr 2000 11:59:22 -0400 (EDT)
Received: (qmail 19133 invoked from network); 10 Apr 2000 16:17:27 -0000
Received: from herra.netapp.com (HELO herra.corp.netapp.com) (198.95.224.184)
  by mx01-ext.netapp.com with SMTP; 10 Apr 2000 16:17:27 -0000
Received: from johnm ([192.168.199.78])
	by herra.corp.netapp.com (8.9.3/8.9.3/NTAP-1.0) with ESMTP id IAA28819;
	Mon, 10 Apr 2000 08:58:48 -0700 (PDT)
Message-Id: <4.2.0.58.20000410175038.00a84890@pop.netapp.com>
X-Sender: jmartin@pop.netapp.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Mon, 10 Apr 2000 17:57:09 +0200
To: Keith Moore <moore@cs.utk.edu>, RJ Atkinson <rja@inet.org>
From: John Martin <jmartin@netapp.com>
Subject: Re: prohibiting RFC publication 
Cc: Peter Deutsch in Mountain View <pdeutsch@EARTHLINK.NET>,
        IETF <ietf@ietf.org>
In-Reply-To: <200004101439.KAA11242@astro.cs.utk.edu>
References: <Your message of "Mon, 10 Apr 2000 07:59:24 BST." <4.2.0.58.20000410075207.0095d970@avarice.inner.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA20193
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

At 10:39 AM 10/04/00 -0400, Keith Moore wrote:
> > The I-D in question has been referred to an existing IETF WG for review,
>
>that assertion was made, but not confirmed by the ADs.
>is it really true?  it seems odd because it really isn't in scope for wrec.

Let me jog your memory:

At 06:29 PM 30/12/99 +0100, Patrik Fältström wrote:
>A request has arrived to publish the named document as informational RFC. 
>The IESG wants all documents in this area to explicitely pass the WREC 
>working group, ...

I then sought clarification, re-sent the document to WREC (it had been sent 
before), to determine if there was a conflict - there wasn't. The authors 
re-submitted it.

John

---------------------------------------------------------------
Network Appliance           Direct / Voicemail: +31 23 567 9615
Kruisweg 799                               Fax: +31 23 567 9699
NL-2132 NG Hoofddorp               Main Office: +31 23 567 9600
---------------------------------------------------------------



From owner-ietf-outbound  Mon Apr 10 12:30:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA22862
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 12:30:02 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA20315
	for <ietf@ietf.org>; Mon, 10 Apr 2000 12:00:52 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.07547-0@bells.cs.ucl.ac.uk>; Mon, 10 Apr 2000 16:59:59 +0100
to: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
In-reply-to: Your message of "Mon, 10 Apr 2000 09:07:58 MDT." <200004101507.JAA27991@calcite.rhyolite.com>
Date: Mon, 10 Apr 2000 16:59:58 +0100
Message-ID: <4193.955382398@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


 >>> Bottom line is that IP-layer interception - even when done "right" - 
 >>> has fairly limited applicability for location of nearby content.
 >>> Though the technique is so widely mis-applied that it might still be 
 >>> useful to define what "right" means.
 
 >>That sounds overly optimistic.


user experience/expectation& context is verything

TCP end2end ness?
if you access a web page from our server, chances are its fectehc by one
of several httpds from one of a LOT of NFS or samba servers, which,
depending on local conditions.....

if you send audio on the net, its quite possible it goes through several
a2d and d2a conversions (.. thru a PSTN/SIP or 323 gateway) - in fact,

if you speak on an apparently end2end PSTN
transatlantic phone call, chances are your voice 
is digitzed and re-digitzed several times by transcoder/compressers....

its the 21st century:
f you dont use end2end crypto, then you  gotta expect people to optimize
their resources to give you the best service money can buy for the least
they have to spend.

hey, when you buy a book written by the author, it was usually typeset,
proofread, and re-edited by several other people....

even this email may not be from me...

 cheers

   jon
"every decoding is an encoding"
maurice zapp from the Euphoric State University, in small world, by david lodge



From owner-ietf-outbound  Mon Apr 10 12:50:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA24219
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 12:50:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23544
	for <ietf@ietf.org>; Mon, 10 Apr 2000 12:41:43 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id KAA00847
	for ietf@ietf.org  env-from <vjs>;
	Mon, 10 Apr 2000 10:41:43 -0600 (MDT)
Date: Mon, 10 Apr 2000 10:41:43 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004101641.KAA00847@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
X-Loop: ietf@ietf.org

> From: Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>

> ...
> its the 21st century:
> f you dont use end2end crypto, then you  gotta expect people to optimize
> their resources to give you the best service money can buy for the least
> they have to spend.
> ...

That's an interesting idea.  People might eventually finally start
using end2end crpyto not for privacy or authnetication where they
really care about either, but for performance and correctness, to
defend against the ISP's who find it cheaper to give you the front
page of last week's newspaper instead of today's.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Mon Apr 10 13:10:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA25400
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 13:10:03 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24874
	for <ietf@ietf.org>; Mon, 10 Apr 2000 13:00:29 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 12ehXx-000BO5-00; Mon, 10 Apr 2000 10:00:21 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Vernon Schryver <vjs@CALCITE.RHYOLITE.COM>
Cc: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <200004101641.KAA00847@calcite.rhyolite.com>
Message-Id: <E12ehXx-000BO5-00@rip.psg.com>
Date: Mon, 10 Apr 2000 10:00:21 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>> From: Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>
>> ...
>> its the 21st century:
>> f you dont use end2end crypto, then you  gotta expect people to optimize
>> their resources to give you the best service money can buy for the least
>> they have to spend.
>> ...
> That's an interesting idea.  People might eventually finally start
> using end2end crpyto not for privacy or authnetication where they
> really care about either, but for performance and correctness, to
> defend against the ISP's who find it cheaper to give you the front
> page of last week's newspaper instead of today's.

and, since we're into exaggeration and hyperbole, i imagine you won't
complain about paying seven times as much for connectivity.

all these oh so brilliant folk on the anti-cacheing crusade should be
sentenced to live in a significantly less privileged country for a year,
where dialup ppp costs per megabyte of international traffic and an
engineer's salary is $100-200 per month.  we are spoiled brats.

randy



From owner-ietf-outbound  Mon Apr 10 13:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA25846
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 13:20:03 -0400 (EDT)
Received: from alemail1.firewall.lucent.com (alemail1.lucent.com [192.11.221.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24923
	for <ietf@ietf.org>; Mon, 10 Apr 2000 13:01:00 -0400 (EDT)
Received: from alemail1.firewall.lucent.com (localhost [127.0.0.1])
	by alemail1.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id NAA12792
	for <ietf@ietf.org>; Mon, 10 Apr 2000 13:00:53 -0400 (EDT)
Received: from uk0006exch001h.wins.lucent.com (h135-86-160-150.lucent.com [135.86.160.150])
	by alemail1.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id NAA12764
	for <ietf@ietf.org>; Mon, 10 Apr 2000 13:00:51 -0400 (EDT)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2448.0)
	id <2PATJFDQ>; Mon, 10 Apr 2000 18:00:50 +0100
Message-ID: <976F7C55E3B2D111A0720008C728549C04876B47@en0060exch001u.uk.lucent.com>
From: "Casati, Alessio (Alessio)" <acasati@lucent.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Cc: "'peter.lewis@upperside.fr'" <peter.lewis@upperside.fr>
Subject: Peter Lewis
Date: Mon, 10 Apr 2000 18:00:40 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01BFA30E.5211BEAC"
X-Loop: ietf@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01BFA30E.5211BEAC
Content-Type: text/plain

 <<[IPTEL] IP Policing 2000>> 

This gentleman, in doing his job, which I understand he must do
and so I don't blame him much, quite frequently sends ads
to a bunch of IETF mailing lists. Maybe I'm not lucky, but
I receive as many as 5 copies of this sort of messages
per each conference he happens to organize times the
number of refreshes and reminders he thinks appropriate.

Isn't it possible
to organize a list for folks willing to post ads, so 
that we don't have to get dozens of messages for the 
same conference? I know that sometimes we get some use of
knowing what's going on, so we should somehow give 
an access point to folks interested in conferences and
similar things.

Peter, would you like to volunteer to host such a list,
since you would seem to benefit a lot?

Apologies for this one-off Spam.

thanks
alessio





------_=_NextPart_000_01BFA30E.5211BEAC
Content-Type: message/rfc822

Message-ID: <010001bfa2fd$caa06c80$0401a8c0@oleane.com>
From: Peter Lewis <peter.lewis@upperside.fr>
To: iptel@lists.research.bell-labs.com
Subject: [IPTEL] IP Policing 2000
Date: Mon, 10 Apr 2000 16:02:25 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"

IP Policing 2000, Paris, 12-15 September

 
The need to police IP networks has grown in importance with the rise of a
new generation of applications such as VPNs, VoIP or IPSec.
Approaches under consideration include COPS, DEN/LDAP and PIB, but their
ultimate potential remains undecided.
 
See:
http://www.upperside.fr/baippol.htm <http://www.upperside.fr/baippol.htm> 
 
 

------_=_NextPart_000_01BFA30E.5211BEAC--



From owner-ietf-outbound  Mon Apr 10 13:30:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA26466
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 13:30:03 -0400 (EDT)
Received: from ernst.netinsight.se (ernst.netinsight.se [194.16.221.130])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA25903
	for <ietf@ietf.org>; Mon, 10 Apr 2000 13:21:05 -0400 (EDT)
Received: from localhost (unverified [10.100.1.11]) by ernst.netinsight.se
 (EMWAC SMTPRS 0.83) with SMTP id <B0000634205@ernst.netinsight.se>;
 Mon, 10 Apr 2000 19:20:00 +0200
To: vjs@calcite.rhyolite.com
Cc: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
In-Reply-To: <200004101641.KAA00847@calcite.rhyolite.com>
References: <200004101641.KAA00847@calcite.rhyolite.com>
X-Mailer: Mew version 1.94.1 on Emacs 20.4 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000410192026U.magda@netinsight.se>
Date: Mon, 10 Apr 2000 19:20:26 +0200
From: Magnus Danielson <magda@NETINSIGHT.SE>
X-Dispatcher: imput version 991025(IM133)
Lines: 23
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

From: Vernon Schryver <vjs@calcite.rhyolite.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Date: Mon, 10 Apr 2000 10:41:43 -0600 (MDT)

> > From: Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>
> 
> > ...
> > its the 21st century:
> > f you dont use end2end crypto, then you  gotta expect people to optimize
> > their resources to give you the best service money can buy for the least
> > they have to spend.
> > ...
> 
> That's an interesting idea.  People might eventually finally start
> using end2end crpyto not for privacy or authnetication where they
> really care about either, but for performance and correctness, to
> defend against the ISP's who find it cheaper to give you the front
> page of last week's newspaper instead of today's.

Maybe this is a reason for these ISPs to filter such traffic out...

Cheers,
Magnus



From owner-ietf-outbound  Mon Apr 10 13:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA27090
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 13:40:01 -0400 (EDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26734
	for <ietf@ietf.org>; Mon, 10 Apr 2000 13:33:52 -0400 (EDT)
Received: from [192.168.124.51] (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id TAA28646; 
          Mon, 10 Apr 2000 19:33:37 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: paf@nix.swip.net
Message-Id: <p04310114b5175696a55b@[192.168.124.51]>
In-Reply-To: <14577.63533.727116.329186@saint.heaven.net>
References: <"Your message dated Sat, 08 Apr 2000 15:59:57 -0400"
 <200004081959.e38Jxvk12760@black-ice.cc.vt.edu>
 <200004081928.PAA24738@astro.cs.utk.edu>
 <4.3.0.20000409142730.00b88340@mail.bayarea.net>
 <p04310103b516abfc0577@[192.168.124.51]>
 <14577.63533.727116.329186@saint.heaven.net>
Date: Mon, 10 Apr 2000 19:31:51 +0930
To: "Dick St.Peters" <stpeters@NetHeaven.com>, ietf@ietf.org
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 11.50 -0400 2000-04-10, Dick St.Peters wrote:
>What is the fundamental difference between choosing the best path and
>choosing the best source?  Arguments that the latter breaks the IP
>model are simply arguments that the IP model is broken for today's
>Internet and will be even more broken for tomorrow's.  The IETF can
>fix the model ... or leave that to someone else.

The difference between what you describe and a random transparent 
proxy is that in your case it is the service provider which is 
building a service with whatever technology he chooses. It is not a 
random ISP in the middle which intercepts and changes IP-packages 
without neither of client nor service provider knowing anything about 
it. If the service provider knows about it, he can choose software 
(or whatever) which can stand the intercept.

Yes, it is the same technology which is used, but not in the same 
ways in both cases.

I.e. for me it is a question _who_ is managing the interception.

   paf



From owner-ietf-outbound  Mon Apr 10 13:50:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA27607
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 13:50:01 -0400 (EDT)
Received: from ns1.aplatform.com (gem@ns1.aplatform.com [204.29.139.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27178
	for <ietf@ietf.org>; Mon, 10 Apr 2000 13:42:13 -0400 (EDT)
Received: from localhost (gem@localhost)
	by ns1.aplatform.com (8.9.3/8.9.3) with ESMTP id KAA06358;
	Mon, 10 Apr 2000 10:42:11 -0700
Date: Mon, 10 Apr 2000 10:42:11 -0700 (PDT)
From: "Gary E. Miller" <gem@rellim.com>
X-Sender: gem@ns1.aplatform.com
Reply-To: gary miller <gem@rellim.com>
To: Randy Bush <randy@PSG.COM>
cc: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
In-Reply-To: <E12ehXx-000BO5-00@rip.psg.com>
Message-ID: <Pine.LNX.4.21.0004101040160.5656-100000@ns1.aplatform.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

Yo Randy!

On Mon, 10 Apr 2000, Randy Bush wrote:

> all these oh so brilliant folk on the anti-cacheing crusade should be
> sentenced to live in a significantly less privileged country for a year,
> where dialup ppp costs per megabyte of international traffic and an
> engineer's salary is $100-200 per month.  we are spoiled brats.

Been there, done that, the LEGALLY required cache did NOT help.  I 
bypassed it whenever possible.  Cacheing is NOT the answer.  

Reports from the recent Adelaide meeting confirm this.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 20340 Empire Ave, Suite E-3, Bend, OR 97701
	gem@rellim.com  Tel:+1(541)382-8588 Fax: +1(541)382-8676



From owner-ietf-outbound  Mon Apr 10 14:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA27956
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 14:00:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27241;
	Mon, 10 Apr 2000 13:43:40 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA20060;
	Mon, 10 Apr 2000 10:40:12 -0700 (PDT)
Message-ID: <38F211D4.9EB37D05@isi.edu>
Date: Mon, 10 Apr 2000 10:39:32 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: aboba@internaut.com, rfc-ed@rfc-editor.org, iesg@ietf.org, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <200004071431.KAA00707@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


One other item:

	Neither this, nor many NAT I-D's, address the particular
	issue of sourcing IP addresses not assigned or owned by 
	the host/gateway, e.g., as they affect the standards
	of RFCs 1122, 1123, and 1812.

	If a device creates (rewrites) IP source addresses with
	addresses not its own, it would be useful to see a section
	specifically addressing the resulting implications.

Joe



From owner-ietf-outbound  Mon Apr 10 14:20:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA28821
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 14:20:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28788
	for <ietf@ietf.org>; Mon, 10 Apr 2000 14:19:30 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA11783;
        Mon, 10 Apr 2000 14:18:43 -0400 (EDT)
Message-Id: <200004101818.OAA11783@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Derrell D. Piper" <ddp@Network-Alchemy.COM>
cc: Keith Moore <moore@cs.utk.edu>, Dave Crocker <dcrocker@brandenburg.com>,
        ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Mon, 10 Apr 2000 08:44:40 PDT."
             <200004101544.IAA07027@gallium.network-alchemy.com> 
Date: Mon, 10 Apr 2000 14:18:43 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> > Bottom line is that IP-layer interception - even when done "right" - 
> > has fairly limited applicability for location of nearby content.
> > Though the technique is so widely mis-applied that it might still be 
> > useful to define what "right" means.
> 
> And there you have the argument for publishing this document.  

no, this document doesn't try to do that - the protocol it proposes
is an attempt to work around one of the many problem associated
with interception proxies, but it's hardly a blueprint for how
to do them "right" (nor does it purport to be).

Keith



From owner-ietf-outbound  Mon Apr 10 14:30:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA29178
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 14:30:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28900
	for <ietf@ietf.org>; Mon, 10 Apr 2000 14:21:56 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA11819;
        Mon, 10 Apr 2000 14:21:01 -0400 (EDT)
Message-Id: <200004101821.OAA11819@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: John Martin <jmartin@netapp.com>
cc: Keith Moore <moore@cs.utk.edu>, RJ Atkinson <rja@inet.org>,
        Peter Deutsch in Mountain View <pdeutsch@EARTHLINK.NET>,
        IETF <ietf@ietf.org>
Subject: Re: prohibiting RFC publication 
In-reply-to: Your message of "Mon, 10 Apr 2000 17:57:09 +0200."
             <4.2.0.58.20000410175038.00a84890@pop.netapp.com> 
Date: Mon, 10 Apr 2000 14:21:01 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> > > The I-D in question has been referred to an existing IETF WG for review,
> >
> >that assertion was made, but not confirmed by the ADs.
> >is it really true?  it seems odd because it really isn't in scope for wrec.
> 
> Let me jog your memory:

yes, I remember that wrec said there wasn't a conflict with its work.
that's not the same thing as wrec discussing whether the approach
is technically sound or whether the document is worthy of publication.

IMHO, that discussion doesn't belong in wrec.  but it's up to the ADs.

Keith



From owner-ietf-outbound  Mon Apr 10 14:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA29947
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 14:50:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29808
	for <ietf@ietf.org>; Mon, 10 Apr 2000 14:42:02 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id MAA03084
	for ietf@ietf.org  env-from <vjs>;
	Mon, 10 Apr 2000 12:42:00 -0600 (MDT)
Date: Mon, 10 Apr 2000 12:42:00 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004101842.MAA03084@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
X-Loop: ietf@ietf.org

> From: Randy Bush <randy@psg.com>

> ...
> > That's an interesting idea.  People might eventually finally start
> > using end2end crpyto not for privacy or authnetication where they
> > really care about either, but for performance and correctness, to
> > defend against the ISP's who find it cheaper to give you the front
> > page of last week's newspaper instead of today's.
>
> and, since we're into exaggeration and hyperbole, i imagine you won't
> complain about paying seven times as much for connectivity.

Most of the exaggeration and hyperbole comes from the caching sales
people.  They'd have you believe that caches never miss, or that
cache filling is free.

The news services I watch have front pages with significant (e.g. editorial
and not just DJI numbers) changes every hour or so.


> all these oh so brilliant folk on the anti-cacheing crusade should be
> sentenced to live in a significantly less privileged country for a year,
> where dialup ppp costs per megabyte of international traffic and an
> engineer's salary is $100-200 per month.  we are spoiled brats.

Cachine won't increase those low salaries.

Many people think we should pay for the bandwidth we use, although not
all favor accounting for each bit.  That one now talks about paying per
MByte instead of Kbit of traffic is a radical change due in part to
using instead of conserving.  Undersea fiber isn't paid for by caching.

The primary waste (and perhaps use) of bandwidth is advertising that
almost no one sees, unless you think single-digit response rates amount
to more than almost no one.  Check the source of the next dozen web
pages you fetch.  Even if you use junk filters, chances are that more
of the bits are advertising than content.  Caching that drivel sounds
good, but its providers are already doing things that merely start with
caching to get it to you faster and cheaper.

Caching and proxying with the cooperation of the content provider
can help the costs of long pipes.  No one has said anything bad
about that kind of caching, when done competently.

"Transparent" caching and proxying without the permission of the content
provider will soon be used for political censorship, if not already, and
likely against your $100/month engineers.  How much "transparent proxy"
hardware and software has already been sold to authoritarian governments?

Yes, it's quixotic to worry about that last.  Everyone who feels
comfortable with the IETF's fine words about wiretapping should stop to
think about reality, and do their part in the real battle by putting
end2end encryption into everything they code, specify, or install.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Mon Apr 10 15:00:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA00257
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 15:00:02 -0400 (EDT)
Received: from corpmail.galaxyscientific.com ([38.221.233.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29972
	for <ietf@ietf.org>; Mon, 10 Apr 2000 14:50:40 -0400 (EDT)
Received: from BELLOPEM (igate.tc.faa.gov [155.178.180.5]) by corpmail.galaxyscientific.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id 2KDCM3SK; Mon, 10 Apr 2000 14:49:40 -0400
From: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
To: "Jon Crowcroft" <J.Crowcroft@CS.UCL.AC.UK>, <ietf@ietf.org>
Subject: RE: A thought about patents
Date: Mon, 10 Apr 2000 14:49:13 -0400
Message-ID: <PPECLLOGBEPHLOMKLNAMGEIMCAAA.Michael.CTR.Bellopede@tc.faa.gov>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <8627@tc.faa.gov>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

network devices are assigned IP addresses, DNS names.  Network devices may
have memory, disks, cache, and CPU/s.


>-----Original Message-----
>From: Jon Crowcroft [mailto:J.Crowcroft@cs.ucl.ac.uk]
>Sent: Saturday, April 08, 2000 10:24 PM
>To: ietf@ietf.org
>Subject: Re: A thought about patents
>
>
>internet bogon alert
>"find the server"
>
>is a server where the ip address, DNS name, lat/long of the CPU,
>memory, disk, or cache, transprent or otherwise is"
>
no, above you describe devices, their possible network attributes, and
hardware components.  A server, by definition, is software that provides a
service, and is run on a device such >>as the one described above.

8>)

-Michael B. Bellopede
 Michael.CTR.Bellopede@tc.faa.gov
  "There is no spoon."




From owner-ietf-outbound  Mon Apr 10 15:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA01764
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 15:50:02 -0400 (EDT)
Received: from mx01-ext.netapp.com (mx01-ext.netapp.com [198.95.224.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA01710
	for <ietf@ietf.org>; Mon, 10 Apr 2000 15:49:18 -0400 (EDT)
Received: (qmail 26166 invoked from network); 10 Apr 2000 20:07:26 -0000
Received: from herra.netapp.com (HELO herra.corp.netapp.com) (198.95.224.184)
  by mx01-ext.netapp.com with SMTP; 10 Apr 2000 20:07:26 -0000
Received: from johnm ([192.168.199.78])
	by herra.corp.netapp.com (8.9.3/8.9.3/NTAP-1.0) with ESMTP id MAA24531;
	Mon, 10 Apr 2000 12:48:41 -0700 (PDT)
Message-Id: <4.2.0.58.20000410213953.063bd680@pop.netapp.com>
X-Sender: jmartin@pop.netapp.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Mon, 10 Apr 2000 21:43:12 +0200
To: Keith Moore <moore@cs.utk.edu>
From: John Martin <jmartin@netapp.com>
Subject: Re: prohibiting RFC publication 
Cc: RJ Atkinson <rja@inet.org>,
        Peter Deutsch in Mountain View <pdeutsch@EARTHLINK.NET>,
        IETF <ietf@ietf.org>
In-Reply-To: <200004101821.OAA11819@astro.cs.utk.edu>
References: <Your message of "Mon, 10 Apr 2000 17:57:09 +0200." <4.2.0.58.20000410175038.00a84890@pop.netapp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 02:21 PM 10/04/00 -0400, Keith Moore wrote:
> > > > The I-D in question has been referred to an existing IETF WG for 
> review,
> > >
> > >that assertion was made, but not confirmed by the ADs.
> > >is it really true?  it seems odd because it really isn't in scope for 
> wrec.
> >
> > Let me jog your memory:
>
>yes, I remember that wrec said there wasn't a conflict with its work.
>that's not the same thing as wrec discussing whether the approach
>is technically sound or whether the document is worthy of publication.

I appreciate that you cannot attend every working group meeting but the 
document, the approach and the implementation were discussed at all but one 
WREC face-to-face meeting and on the mailing list. We received comments and 
made changes as a result of discussions on WREC.

Note: many of those who are / were active within WREC were / are also 
active in discussing NECP.

John

---------------------------------------------------------------
Network Appliance           Direct / Voicemail: +31 23 567 9615
Kruisweg 799                               Fax: +31 23 567 9699
NL-2132 NG Hoofddorp               Main Office: +31 23 567 9600
---------------------------------------------------------------



From owner-ietf-outbound  Mon Apr 10 16:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA02670
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 16:20:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02422
	for <ietf@ietf.org>; Mon, 10 Apr 2000 16:13:07 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA12359
        for <ietf@ietf.org>; Mon, 10 Apr 2000 16:12:27 -0400 (EDT)
Message-Id: <200004102012.QAA12359@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: ietf@ietf.org
Subject: breaking the IP model (or not)
In-reply-to: Your message of "Mon, 10 Apr 2000 11:50:05 EDT."
             <14577.63533.727116.329186@saint.heaven.net> 
X-SUBJECT-MSG-FROM: "Dick St.Peters" <stpeters@NetHeaven.com> 
Date: Mon, 10 Apr 2000 16:12:27 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Arguments that the latter breaks the IP
> model are simply arguments that the IP model is broken for today's
> Internet and will be even more broken for tomorrow's.  

those two statements aren't equivalent.  the fact that people want 
to break the IP model may mean that it's easier (at least initially)
to deploy a broken solution than to deploy a technically sound one 
(just like it's easier to dump your toxic waste in the local stream
than it is to clean it up) 

but the fact that IP doesn't do everything that people want doesn't 
mean that the IP model is broken, any more than the stream is broken 
because it doesn't solve your waste disposal problem.  

some approaches to solving problems seem simple at first but 
really are a lot more complex than they look.

NATs seem like a simple solution to address exhaustion...until 
you figure in the additional complexity of application-level 
gateways inside the NAT, and of the additional code that ends
up in applications that try to work around the problems caused 
by NATs, and (in some cases) of the additional middleware that 
you need to deploy to solve those problems.  with enough work
you can get around most of the problems that NATs cause, but
it would have been a lot simpler, more efficient, more flexible,
and more reliable if you had just solved the address space
problem in a sane way.  (and regardless of what some folks think 
about IPv6, it's a LOT saner than NAT).  and in addition to the
complexity and increased operating costs and reduced reliability
etc. required by those workarounds, you also end up with an
increased effort requried to deploy new applications (e.g. IP
telephony).

interception proxies seem like a simple solution to automatic
location of services, until you figure in the additional complexity
(of things like NECP) required to make them work in something 
resembling the fashion that the applications expect, and the 
additional complexity of things (like IPsec) that applications and 
services need to do to defeat interception proxies that get in 
their way.  

similar arguments apply to content-modifying firewalls and 
probably apply to traffic shaping.

it's completely natural that people will try such approaches -
they are trying to address real problems and they want quick 
solutions to those problems.  but if the quick fix solutions  
get entrenched then they cause their own set of problems which
are worse then the original problems.  this is not progress.

IMHO we need to see these things for what they are:

- quick fixes with limited applicability and future
- indicators that there is an important problem that needs to be
  solved in a technically sound fashion

Keith



From owner-ietf-outbound  Mon Apr 10 16:30:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA03438
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 16:30:03 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02439;
	Mon, 10 Apr 2000 16:15:08 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id NAA13997;
	Mon, 10 Apr 2000 13:14:53 -0700 (PDT)
Message-ID: <38F23615.AFE3B2B1@isi.edu>
Date: Mon, 10 Apr 2000 13:14:13 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: pdeutsch@cisco.com
CC: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>,
        Keith Moore <moore@CS.UTK.EDU>, karl@CAVEBEAR.COM, iesg@ietf.org,
        ietf@ietf.org, rfc-ed@rfc-editor.org, touch@ISI.EDU
Subject: Re: recommendation against publication of draft-cerpa-necp-0
References: <PPECLLOGBEPHLOMKLNAMGEGOCAAA.Michael.CTR.Bellopede@tc.faa.gov> <38EE7D4D.8F4457DD@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Peter Deutsch wrote:
> 
> g'day,
> 
> "Michael B. Bellopede" wrote:
> ...
> > Regardless of what occurs at higher layers, there is still the problem of
> > changing the source address in an IP packet which occurs at the network(IP)
> > layer.
> 
> The Content Services Business Unit of Cisco (Fair Disclosure time -
> that's my employer  and my business unit) sells a product called
> "Local Director". LD is intended to sit in front of a cluster of
> cache engines containing similar data, performing automatic
> distribution of incoming requests among the multiple caches. It does
> this by intercepting the incoming IP packets intended for a specific
> IP address and multiplexing it among the caches. Are we doing
> something illegal or immoral here? No, we're offering hot spare
> capability, load balancing, increased performance, and so on. The
> net is a better place than it was a few years ago, when a web page
> would contain a list of links and an invitation to "please select
> the closest server to you".
> 
> We also have a product called "Distributed Director", which is
> essentially a DNS server appliance which can receive incoming DNS
> requests (e.g for "www.cnn.com") and reroute it to one or more cache
> farms for distributed load balancing. If intercepting IP addresses
> is evil, then presumably intercepting DNS requests is more evil,
> since it's higher up the IP stack? No, it's a legitimate tool for
> designing massive Content Service Networks of the scale needed in
> the coming years.

These are both conformant with RFC 1122/1123 (together STD-3) because
they redistribute IP addresses within a stub network. Same with DHCP.
The questionable practices (wrt STD-3) arise when sourcing IP addresses
not delegated to your authority (i.e., running these services on transit
to someone else's server), rather than running them as a head-end to
your own stub.

Joe



From owner-ietf-outbound  Mon Apr 10 16:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA03767
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 16:40:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02466
	for <ietf@ietf.org>; Mon, 10 Apr 2000 16:16:25 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA12372;
        Mon, 10 Apr 2000 16:15:36 -0400 (EDT)
Message-Id: <200004102015.QAA12372@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Mon, 10 Apr 2000 10:41:43 MDT."
             <200004101641.KAA00847@calcite.rhyolite.com> 
Date: Mon, 10 Apr 2000 16:15:36 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> > > its the 21st century:
> > f you dont use end2end crypto, then you  gotta expect people to optimize
> > their resources to give you the best service money can buy for the least
> > they have to spend.
> > ...
> 
> That's an interesting idea.  People might eventually finally start
> using end2end crpyto not for privacy or authnetication where they
> really care about either, but for performance and correctness, to
> defend against the ISP's who find it cheaper to give you the front
> page of last week's newspaper instead of today's.

or ISPs might start penalizing encrypted packets.

I just don't buy the argument that we can solve these problems by
adding more complexity.  That's like saying that a country can 
get more security by building more planes, tanks, bombs, etc.
It might work, but then again, it might fuel an arms race.

Keith



From owner-ietf-outbound  Mon Apr 10 16:50:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA03989
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 16:50:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03102
	for <ietf@ietf.org>; Mon, 10 Apr 2000 16:23:30 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA12406;
        Mon, 10 Apr 2000 16:22:36 -0400 (EDT)
Message-Id: <200004102022.QAA12406@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Randy Bush <randy@psg.com>
cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Mon, 10 Apr 2000 10:00:21 PDT."
             <E12ehXx-000BO5-00@rip.psg.com> 
Date: Mon, 10 Apr 2000 16:22:36 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> all these oh so brilliant folk on the anti-cacheing crusade should be
> sentenced to live in a significantly less privileged country for a year,
> where dialup ppp costs per megabyte of international traffic and an
> engineer's salary is $100-200 per month. 

and as long as we're talking about just deserts...all of those ISPs that
put an interception proxy between their dialup customers and the rest 
of the Internet should be required to put another interception proxy
on the other side of their international links, between those clients 
and the ISP's local server customers.  that way, they will do the same 
degree of harm to their own business customers that they are doing 
to other ISPs' business customers.

Keith



From owner-ietf-outbound  Mon Apr 10 23:00:40 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA11395
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 23:00:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11264
	for <ietf@ietf.org>; Mon, 10 Apr 2000 22:50:39 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id UAA10323
	for ietf@ietf.org  env-from <vjs>;
	Mon, 10 Apr 2000 20:50:35 -0600 (MDT)
Date: Mon, 10 Apr 2000 20:50:35 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004110250.UAA10323@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
X-Loop: ietf@ietf.org

I tried to send this earlier, but got a response from
Majordomo-Owner@ietf.org complaining that every line is a bogus majordomo
command.  My logs say I sent to ietf@ietf.org and not majordomo@ietf.org
or anything smilar.  I did use the word "s-u-b-s-c-r-i-b-e-r-s" 3 times.
This time I've replaced all with "[users]".

I suspect a serious or at least irritating bug in a defense against stupid
"u-n-s-u-b-s-c-r-i-b-e" requests.  If I'm right, then someone needs to
stop and think a little.



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


> > That's an interesting idea.  People might eventually finally start
> > using end2end crpyto not for privacy or authnetication where they

> or ISPs might start penalizing encrypted packets.

Why not?  ISP's that figure that last week's or even this morning's Wall
Street Journal front page is good enough might well charge more for traffic
that goes outside their networks to get the current WSJ, or the WSJ with
the Doubleclick ads that Dow Jones prefers.

I wonder how long before an ISP with a transparent proxy uses it to modify
the stream of ads, replacing some with more profitable bits.  It's not as
if "commercial insertion" is a new idea.  The local TV affliate or cable
operator's computers replace a lot of dead air and other people's ads with
their own....as I think about it, I realize I've got to be behind the
times.  I bet many of the so called free ISP's and perhaps others must
already be optimizing the flow of information to their [users].  There's
only so much screen real estate and conscious attention behind those
eyeballs.  They'd not want to be blatant about it, unlike "framing", to
avoid moot excitment among lawyers and [users].  If you must pay for your
[users]' web surfing by posting ads, where better but on top or instead
of other people's ads?


> I just don't buy the argument that we can solve these problems by
> adding more complexity.  That's like saying that a country can 
> get more security by building more planes, tanks, bombs, etc.
> It might work, but then again, it might fuel an arms race.

You've written today about the complications of simplistic solutions to
problems that are not as simple as they sound.  You're right, of course.
The reasons why no one uses real encryption now do not include it being
free or as easy as not using it.

For example, simply using HTTPS if you want to read the WSJ without local
improvements might not be a good enough, depend on how much you can trust
that the public key you get from the nearby PKI servers really belongs to
Dow Jones and not the local ministry of information.  What?--you say the
public key infrastructure is invulnerable to bureaucrats in the middle
with very large purses and bigger sticks?--well, if you say so...

The problem with transparent proxies is that they are men in the middle,
and so are very good at wire tapping, censoring, and improving information.
And even harder to trust.  Stealth proxies are vastly more powerful than
remote controlled taps on everyone's routers and PBX's.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Mon Apr 10 23:10:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA11590
	for ietf-outbound.10@ietf.org; Mon, 10 Apr 2000 23:10:02 -0400 (EDT)
Received: from monitor.internaut.com (mg-206253202-59.ricochet.net [206.253.202.59])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11567
	for <ietf@ietf.org>; Mon, 10 Apr 2000 23:09:38 -0400 (EDT)
Received: from vaiobean (vaiobean.ntdev.microsoft.com [204.57.137.66] (may be forged))
	by monitor.internaut.com (8.9.2/8.8.8) with SMTP id TAA42635;
	Mon, 10 Apr 2000 19:56:24 -0700 (PDT)
Reply-To: <aboba@internaut.com>
From: "Bernard Aboba" <aboba@internaut.com>
To: "'Keith Moore'" <moore@cs.utk.edu>, <ietf@ietf.org>
Subject: RE: breaking the IP model (or not)
Date: Mon, 10 Apr 2000 20:11:58 -0700
Message-ID: <010901bfa363$b3a79f60$428939cc@ntdev.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6700
In-Reply-To: <200004102012.QAA12359@astro.cs.utk.edu>
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>it's completely natural that people will try such approaches -
>they are trying to address real problems and they want quick 
>solutions to those problems.  

In particular, they will try such approaches if they are not
presented with better alternatives. 

>but if the quick fix solutions get entrenched then they cause 
>their own set of problems which are worse then the original 
>problems.  this is not progress.

Progress is created by the development of
solutions that do not cause their own set of problems. 
This does not happen merely by condemning other less
desirable solutions. It happens by presenting a better
alternative. 

>- indicators that there is an important problem that needs to be
>  solved in a technically sound fashion

If this mail thread is any indication, I'd say the indicator is 
shining brightly. 



From owner-ietf-outbound  Tue Apr 11 00:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA12713
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 00:10:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12668
	for <ietf@ietf.org>; Tue, 11 Apr 2000 00:07:37 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3B474j27594;
	Tue, 11 Apr 2000 00:07:04 -0400
Message-Id: <200004110407.e3B474j27594@black-ice.cc.vt.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Mon, 10 Apr 2000 20:50:35 MDT."
             <200004110250.UAA10323@calcite.rhyolite.com> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200004110250.UAA10323@calcite.rhyolite.com>
Date: Tue, 11 Apr 2000 00:07:04 -0400
X-Loop: ietf@ietf.org

On Mon, 10 Apr 2000 20:50:35 MDT, Vernon Schryver <vjs@calcite.rhyolite.com>  said:
> if "commercial insertion" is a new idea.  The local TV affliate or cable
> operator's computers replace a lot of dead air and other people's ads with
> their own....as I think about it, I realize I've got to be behind the
> times.  I bet many of the so called free ISP's and perhaps others must

Well, on the TV front, not only are they injecting ads over the
top of other less-profitable ads, but they're even doing on-the-fly
manipulation of sports events, injecting faked banners onto shots of
stadium walls..

Makes you wonder who to trust, if a tennis match is being altered in
real time....

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Tue Apr 11 02:00:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA18519
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 02:00:02 -0400 (EDT)
Received: from mx01-ext.netapp.com (mx01-ext.netapp.com [198.95.224.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA18444
	for <ietf@ietf.org>; Tue, 11 Apr 2000 01:50:14 -0400 (EDT)
Received: (qmail 19252 invoked from network); 11 Apr 2000 06:08:32 -0000
Received: from herra.netapp.com (HELO herra.corp.netapp.com) (198.95.224.184)
  by mx01-ext.netapp.com with SMTP; 11 Apr 2000 06:08:32 -0000
Received: from johnm ([192.168.199.71])
	by herra.corp.netapp.com (8.9.3/8.9.3/NTAP-1.0) with ESMTP id WAA26446
	for <ietf@ietf.org>; Mon, 10 Apr 2000 22:49:37 -0700 (PDT)
Message-Id: <4.2.0.58.20000411073442.00ab6d00@pop.netapp.com>
X-Sender: jmartin@pop.netapp.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Tue, 11 Apr 2000 07:45:20 +0200
To: IETF <ietf@ietf.org>
From: John Martin <jmartin@netapp.com>
Subject: interception proxies
In-Reply-To: <200004102022.QAA12406@astro.cs.utk.edu>
References: <Your message of "Mon, 10 Apr 2000 10:00:21 PDT." <E12ehXx-000BO5-00@rip.psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

There has been a lot of discussion about the problems associated with 
so-called "interception proxies". This discussion is very much within the 
charter of the WREC WG. In fact, we even have a current draft whose sole 
purpose is to document such problems.

The known problems draft is at: draft-ietf-wrec-known-prob-01.txt

This is the first of two very useful documents being produced by WREC; the 
first, a taxonomy of terminology is available as: 
draft-ietf-wrec-taxonomy-03.txt; I would suggest you read this first.

To join WREC, use the following:
	mailto:wrec-request@cs.utk.edu?Subject=subscribe

...or send a note to wrec-request@cs.utk.edu with "subscribe" in the subject.

I suggest we move this particular discussion to WREC.

Rgds,
John
---------------------------------------------------------------
Network Appliance           Direct / Voicemail: +31 23 567 9615
Kruisweg 799                               Fax: +31 23 567 9699
NL-2132 NG Hoofddorp               Main Office: +31 23 567 9600
---------------------------------------------------------------



From owner-ietf-outbound  Tue Apr 11 03:30:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA25682
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 03:30:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25631
	for <ietf@ietf.org>; Tue, 11 Apr 2000 03:25:10 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id DAA14555;
        Tue, 11 Apr 2000 03:23:08 -0400 (EDT)
Message-Id: <200004110723.DAA14555@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: aboba@internaut.com
cc: "'Keith Moore'" <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: breaking the IP model (or not) 
In-reply-to: Your message of "Mon, 10 Apr 2000 20:11:58 PDT."
             <010901bfa363$b3a79f60$428939cc@ntdev.microsoft.com> 
Date: Tue, 11 Apr 2000 03:23:08 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> >it's completely natural that people will try such approaches -
> >they are trying to address real problems and they want quick 
> >solutions to those problems.  
> 
> In particular, they will try such approaches if they are not
> presented with better alternatives. 

there's something odd to my ear about people needing to 
*be presented* with better alternatives than doing harm to the architecture
as opposed to those people *developing* better alternatives.

I suspect there's something about the current economic climate that
favors development of quick fixes over development of sane ones.
but the apparent shortsightedness still bothers me.

Keith



From owner-ietf-outbound  Tue Apr 11 04:40:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA26444
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 04:40:02 -0400 (EDT)
Received: from cesium.clock.org (IDENT:6431-ident-is-a-completely-pointless-protocol-that-offers-no-security-or-traceability-at-all-so-take-this-and-log-it!@cesium.clock.org [209.179.181.185])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26421
	for <ietf@ietf.org>; Tue, 11 Apr 2000 04:39:46 -0400 (EDT)
Received: from mg136-223.ricochet.net ([204.179.136.223]:49174 "EHLO [216.240.40.200]" ident: "NO-IDENT-SERVICE[2]") by cesium.clock.org with ESMTP id <3140-9103>; Tue, 11 Apr 2000 01:39:32 -0700
Mime-Version: 1.0
X-Sender: eef-info@pop
Message-Id: <v04220804b51889bf518a@[216.240.40.200]>
In-Reply-To: <200004110723.DAA14555@astro.cs.utk.edu>
References: <200004110723.DAA14555@astro.cs.utk.edu>
To: Keith Moore <moore@cs.utk.edu>
From: Erik Fair <fair@CLOCK.ORG>
Subject: Re: breaking the IP model (or not)
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Date: 	Tue, 11 Apr 2000 01:39:32 -0700
X-Loop: ietf@ietf.org

It's much worse than that.

In the End to End model, far too many of our problems require 
changing all the end systems to solve. However, that's extremely 
difficult to do, particularly as there is little or no incentive (the 
DCA/DISA had guns, and control of the IMPs in 1982/1983 to force the 
NCP->TCP/IP conversion - there is no equivalent agency today).

Almost all of the pressure created by the growth of the Internet is 
on the network operators and their vendors (e.g. router vendors), 
rather than on the users and the end systems (and the end system 
vendors, e.g. PCs, Macs, Suns, etc).

It's also bad that there is little or no integration of intermediate 
system vendors with end system vendors (or vice versa), because that 
results in insufficient sharing of information between those two 
industry segments. The IETF should be facilitating information 
exchange, but it isn't working as well as it should (otherwise we 
wouldn't have these problems, right?).

So, with nearly all the pressure on the operators and the vendors 
that serve them, the "solutions" they come up with are necessarily 
pretty ugly hacks (e.g. NAT, TCP spoofing, Firewalls) because they 
have to deal with the reality that they can't change the end systems 
themselves, or require them to be changed.

This is a structural problem. Until the situation changes, we're 
going to keep on seeing ugly hacks that do violence to the Internet 
architectural model deployed, marketed, touted as "solutions."

	an author of RFC 1627,

	Erik <fair@clock.org>



From owner-ietf-outbound  Tue Apr 11 10:10:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA05182
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 10:10:01 -0400 (EDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04867
	for <ietf@ietf.org>; Tue, 11 Apr 2000 10:06:22 -0400 (EDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id PAA14540; Tue, 11 Apr 2000 15:05:42 +0100
Received: from hursley.ibm.com (gsine04.us.sine.ibm.com [9.14.6.44]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id PAA18448; Tue, 11 Apr 2000 15:05:48 +0100 (BST)
Message-ID: <38F33143.783EB244@hursley.ibm.com>
Date: Tue, 11 Apr 2000 09:05:55 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: aboba@internaut.com
CC: ietf@ietf.org
Subject: Re: breaking the IP model (or not)
References: <010901bfa363$b3a79f60$428939cc@ntdev.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Bernard Aboba wrote:
...
> >- indicators that there is an important problem that needs to be
> >  solved in a technically sound fashion
> 
> If this mail thread is any indication, I'd say the indicator is
> shining brightly.

There are many people wearing 3-month goggles who still just can't see it.

   Brian



From owner-ietf-outbound  Tue Apr 11 11:12:05 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA08159
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 11:10:01 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07675
	for <ietf@ietf.org>; Tue, 11 Apr 2000 11:00:43 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id KAA04985;
        Tue, 11 Apr 2000 10:59:51 -0400 (EDT)
Message-Id: <200004111459.KAA04985@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Erik Fair <fair@CLOCK.ORG>
cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: breaking the IP model (or not) 
In-reply-to: Your message of "Tue, 11 Apr 2000 01:39:32 PDT."
             <v04220804b51889bf518a@[216.240.40.200]> 
Date: Tue, 11 Apr 2000 10:59:50 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> It's also bad that there is little or no integration of intermediate 
> system vendors with end system vendors (or vice versa), because that 
> results in insufficient sharing of information between those two 
> industry segments. The IETF should be facilitating information 
> exchange, but it isn't working as well as it should (otherwise we 
> wouldn't have these problems, right?).

it's not clear that the problems are caused by lack of information
exchange, given time-to-market pressures that cause folks to ship 
product now and deny causing problems later.



From owner-ietf-outbound  Tue Apr 11 11:50:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA10074
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 11:50:03 -0400 (EDT)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09918;
	Tue, 11 Apr 2000 11:46:55 -0400 (EDT)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id IAA26930;
	Tue, 11 Apr 2000 08:44:39 -0700 (PDT)
Received: from p7020-img-nt.cisco.com (dhcp-171-69-70-161.cisco.com [171.69.70.161]) by rhino (SMI-8.6/CISCO.WS.1.1) with ESMTP id IAA02446; Tue, 11 Apr 2000 08:51:03 -0700
Message-Id: <4.3.1.2.20000411065536.02631be0@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 11 Apr 2000 06:59:12 -0700
To: "Martin J.G. Williams" <martin.jg.williams@bigfoot.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: prohibiting RFC publication
Cc: iesg@ietf.org, ietf@ietf.org, rfc-ed@rfc-editor.org
In-Reply-To: <38F0094B.99071F39@bigfoot.com>
References: <200004082140.RAA25358@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 02:38 AM 4/9/00 +0100, Martin J.G. Williams wrote:
>As far as i'm concerned (IMHO) if the standards bodies were to be driven 
>by the
>vendors, then they would become no more
>than sanitised purveyors of de facto standards, and je jure standards would be
>relegated to being nothing more than "misty-eyed" memories.

Are you saying that IETF specifications are de jure standards? If so, don't 
tell the State Department, they don't know that :^)

IETF Specifications are indeed de facto standards - they are standards in 
part because the community calls them such, but mostly because the 
community implements them and uses them.

I think what you meant to say is that they would be nothing more than 
purveyors of the proprietary protocols that vendors chose to make semi-public.



From owner-ietf-outbound  Tue Apr 11 12:20:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA11247
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 12:20:01 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11025
	for <ietf@ietf.org>; Tue, 11 Apr 2000 12:12:52 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id KAA22474
	for ietf@ietf.org  env-from <vjs>;
	Tue, 11 Apr 2000 10:12:44 -0600 (MDT)
Date: Tue, 11 Apr 2000 10:12:44 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004111612.KAA22474@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: interception proxies
X-Loop: ietf@ietf.org

> From: John Martin <jmartin@netapp.com>

> There has been a lot of discussion about the problems associated with 
> so-called "interception proxies". This discussion is very much within the 
> charter of the WREC WG. In fact, we even have a current draft whose sole 
> purpose is to document such problems.
>
> The known problems draft is at: draft-ietf-wrec-known-prob-01.txt
>
> This is the first of two very useful documents being produced by WREC; the 
> first, a taxonomy of terminology is available as: 
> draft-ietf-wrec-taxonomy-03.txt; I would suggest you read this first.

The problems draft is interesting and depressing.  All of the problems
listed are technical nits.  If you assume that "traffic redirection"
and an "interception proxy" are good things, then you might well worry
about the "lack of HTTP/1.1 compliance for proxy caches" or whether
"interception proxies break client cache directives."  You will not
question their desirability or even their long term utility in the face
of actions by users to protect their privacy or defend against censorship.
You won't even worry about what's going to hit the fan when the big
advertisers realize that their wonderful ads are being filtered and
overwritten with other people's ads by interception proxies.

I don't know whether to be depressed, encouraged, or neutral that WREC
seems to not be about port 25 traffic redirection and interception proxies,
such as AOL's effort.  That there is no mention of the problems that IP
fragmentation can cause interception proxies is depressing.


> To join WREC, use the following:
> 	mailto:wrec-request@cs.utk.edu?Subject=subscribe
>
> ...or send a note to wrec-request@cs.utk.edu with "subscribe" in the subject.
>
> I suggest we move this particular discussion to WREC.

Joining that mailing list would not be useful, prudent, or honest for
people with sentiments like mine.  Moving the question of the wisdom of
such proxies to WREC would be equivalent to moving the question of the
wisdom of wiretapping to the wiretapping working group.  At best the group
WG consensus can be predicted.  At worst, the discussion would legitimately
be considered disruptive and irrelevant.

It appears that the WREC working group is doing exactly as someone
lamented a day or two ago about working groups in general, and not
considering the question of whether the mechanisms they are working are
good ideas in the larger scheme of things.  WREC is only concerned with
making them as good as possible.  (Yes, I checked recent months of the
archives at ftp://cs.utk.edu/pub/wrec/)

It is interesting, but consistent with that observation that the problems
draft contains no mention of problems should clients use end to end
encryption or even just authentication with message authentication codes
that care about the current time or the particular client.  I don't know
what to think of the absence of the string "https" in all three drafts.
The passing, convoluted reference to encryption and SSL in section 9.2.2
of the taxonomy draft confuses me.  If I were optimistic, I would hope
that the taxonomy document is the wrong location is the reason its privacy
section is so shallow.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Tue Apr 11 12:40:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA12167
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 12:40:05 -0400 (EDT)
Received: from mail.xybridge.com (IDENT:root@[209.111.160.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12069
	for <ietf@ietf.org>; Tue, 11 Apr 2000 12:37:14 -0400 (EDT)
Received: from yixin ([10.10.13.107])
	by mail.xybridge.com (8.9.3/8.9.3) with SMTP id KAA05029
	for <ietf@ietf.org>; Tue, 11 Apr 2000 10:45:09 -0500
From: "Yixin Zhu" <yixin@xybridge.com>
To: <ietf@ietf.org>
Subject: OSP
Date: Tue, 11 Apr 2000 11:37:07 -0700
Message-ID: <NDBBIFGHKLHKNCMEKGHAIEEMCAAA.yixin@xybridge.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <200004111612.KAA22474@calcite.rhyolite.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


Hi ,

I am interested in the Open Settlement Protocol for VoIP. I have check the
web site for GRIC and  TransNexus, and got some information. It will be
appreciated if someone here can point to  me more places to get  info on
this topic.

Thanks,


Yixin (James) Zhu



From owner-ietf-outbound  Tue Apr 11 13:20:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA13709
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 13:20:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13293
	for <ietf@ietf.org>; Tue, 11 Apr 2000 13:10:05 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id NAA21177;
	Tue, 11 Apr 2000 13:10:01 -0400
Date: Tue, 11 Apr 2000 13:10:01 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200004111710.NAA21177@ginger.lcs.mit.edu>
To: fair@CLOCK.ORG, moore@cs.utk.edu
Subject: Re: breaking the IP model (or not)
Cc: ietf@ietf.org, jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

    > From: Erik Fair <fair@clock.org>

    > Almost all of the pressure created by the growth of the Internet is
    > on the network operators and their vendors (e.g. router vendors),
    > rather than on the users and the end systems (and the end system
    > vendors

Well, there are rational (?) structural reasons for this. i) There are more
end systems than infrastructure boxes, so it's more work to change the
former. ii) The end system boxes are often under the control of people who
have less technical expertise, contacts, organization, etc than the
infrastructure boxes, so it's more work to change them.

All of which leads to solutions being jammed into the infrastructure boxes,
which are easier to get to, rather than the end system boxes, where it may
be desirable for architectural reasons. I wish a had some idea how to
change this, but I don't (short of finding some killer app and bundling it
with an end system architectural upgrade).

    > So, with nearly all the pressure on the operators and the vendors
    > that serve them, the "solutions" they come up with are necessarily
    > pretty ugly hacks (e.g. NAT, TCP spoofing, Firewalls) because they
    > have to deal with the reality that they can't change the end systems
    > themselves, or require them to be changed.

There's another factor, which is that short-term fixes are less expensive
in the here-and-now than fixes with a longer horizon. You see this effect
operating even in areas that *don't* involve the end systems (e.g. routing).

    > This is a structural problem. Until the situation changes, we're
    > going to keep on seeing ugly hacks that do violence to the Internet
    > architectural model deployed, marketed, touted as "solutions."

In the past, it has been a truism of system architecture that systems
usually die because i) the basic architecture had things missing; ii) the
'improvements' done to rectify these problem are usually poorly
thought-out/intergrated "warts" added by programmers who are new hires and
don't really have the vision/confidence to fundamentally alter things; and
iii) eventually the system crumbles under the addition of all these warts,
and you have to throw it all out and start again from scratch.

What's novel about the Internet is that i) the people making the additions
are not all working for one company, but are a large collection of people
without any central control, and ii) the process of "starting from scratch"
will be even more painful, since you not only have to keep the old system
running, but have it interoperate with the new one while the changeover is
happening. (Think NCP->TCP conversion, but ^69th.)


I'm not sure what the model is to make this happen, but I've come to the
conclusion that the IETF process, as the IETF has evolved, is not the way
to do it.

	Noel



From owner-ietf-outbound  Tue Apr 11 13:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA14056
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 13:30:03 -0400 (EDT)
Received: from lara200.laratech.ca (mail.laratech.ca [207.236.91.222])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13919
	for <ietf@ietf.org>; Tue, 11 Apr 2000 13:25:40 -0400 (EDT)
Received: from empowertel.com (lara30 [172.16.1.30])
	by lara200.laratech.ca (8.8.8+Sun/8.8.8) with ESMTP id NAA06463;
	Tue, 11 Apr 2000 13:25:02 -0400 (EDT)
Sender: hsaxena@lara200.laratech.ca
Message-ID: <38F35FEE.2D089B3@empowertel.com>
Date: Tue, 11 Apr 2000 13:25:02 -0400
From: Himanshoo Saxena <hsaxena@empowertel.com>
Reply-To: hsaxena@empowertel.com
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Yixin Zhu <yixin@xybridge.com>
CC: ietf@ietf.org
Subject: Re: OSP
References: <652568BE.005B2D26.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Yixin Zhu wrote:
> 
> Hi ,
> 
> I am interested in the Open Settlement Protocol for VoIP. I have check the
> web site for GRIC and  TransNexus, and got some information. It will be
> appreciated if someone here can point to  me more places to get  info on
> this topic.
> 
> Thanks,
> 
> Yixin (James) Zhu

Hi,
I have another link in my bookmarks which may be of som ehelp;
http://www.oasis-open.org/cover/openSetProt.html
Regards
Himanshoo



From owner-ietf-outbound  Tue Apr 11 14:00:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA15127
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 14:00:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14988
	for <ietf@ietf.org>; Tue, 11 Apr 2000 13:55:56 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA05839;
        Tue, 11 Apr 2000 13:55:06 -0400 (EDT)
Message-Id: <200004111755.NAA05839@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: interception proxies 
In-reply-to: Your message of "Tue, 11 Apr 2000 10:12:44 MDT."
             <200004111612.KAA22474@calcite.rhyolite.com> 
Date: Tue, 11 Apr 2000 13:55:06 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

wrec is supposed to be about *web* replication and caching.
which probably doesn't include email.  so I can hardly
blame them for not talking about port 25.  since other kinds
of interception proxies exist, perhaps they should clarify their 
document slightly to say it's about web interception proxies.

naturally I would encourage folks who are concerned about web
interception proxies to join the wrec group and/or to submit 
comments and corrections about their documents.  

Keith



From owner-ietf-outbound  Tue Apr 11 16:10:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA19240
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 16:10:01 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19120
	for <ietf@ietf.org>; Tue, 11 Apr 2000 16:03:38 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id NAA26568;
	Tue, 11 Apr 2000 13:03:35 -0700 (PDT)
Message-ID: <38F384F6.B0238438@isi.edu>
Date: Tue, 11 Apr 2000 13:03:02 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: ietf@ietf.org, touch@ISI.EDU
Subject: Re: interception proxies
References: <200004111612.KAA22474@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Vernon Schryver wrote:
> 
> > From: John Martin <jmartin@netapp.com>
> 
> > There has been a lot of discussion about the problems associated with
> > so-called "interception proxies". This discussion is very much within the
> > charter of the WREC WG. In fact, we even have a current draft whose sole
> > purpose is to document such problems.
> >
> > The known problems draft is at: draft-ietf-wrec-known-prob-01.txt
> >
> > This is the first of two very useful documents being produced by WREC; the
> > first, a taxonomy of terminology is available as:
> > draft-ietf-wrec-taxonomy-03.txt; I would suggest you read this first.
> 
> The problems draft is interesting and depressing.  All of the problems
> listed are technical nits.  

This was a choice - in some larger sense, if sourcing other-owned IP
addresses or TCP connections is considered an architectural problem,
needs to come down from above, rather than up from WREC. f

> I don't know whether to be depressed, encouraged, or neutral that WREC
> seems to not be about port 25 traffic redirection and interception proxies,
> such as AOL's effort.  That there is no mention of the problems that IP
> fragmentation can cause interception proxies is depressing.

The problems of IP fragmentation are not unique to web caching or
replication proxies. They affect all interception proxies. The issue of
inteception proxies was around long before WREC, and is more than just a
caching or replication issue. 

> Joining that mailing list would not be useful, prudent, or honest for
> people with sentiments like mine.  Moving the question of the wisdom of
> such proxies to WREC would be equivalent to moving the question of the
> wisdom of wiretapping to the wiretapping working group.  At best the group
> WG consensus can be predicted.  At worst, the discussion would legitimately
> be considered disruptive and irrelevant.

WREC is about proxies - there are plenty of 'architecturally conformant'
ways to do proxies. If the problems with transparent proxies is an
issue, WREC may be a good place (but not the only place) to solicit
input.

> It appears that the WREC working group is doing exactly as someone
> lamented a day or two ago about working groups in general, and not
> considering the question of whether the mechanisms they are working are
> good ideas in the larger scheme of things.  WREC is only concerned with
> making them as good as possible.  (Yes, I checked recent months of the
> archives at ftp://cs.utk.edu/pub/wrec/)

That's the property of WGs in general, by construction. These questions
sometimes get addressed in BOFs, but there is also often too much
momentum or political interest in establishing a 'standardizing
presence' in an area. By the time a WG is formed, the time for 'whether'
has often passed in favor of 'which'.

Joe



From owner-ietf-outbound  Tue Apr 11 17:00:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA20265
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 17:00:02 -0400 (EDT)
Received: from doberman.cwusa.com (doberman-dmz.cwusa.com [146.135.88.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20206
	for <ietf@ietf.org>; Tue, 11 Apr 2000 16:56:41 -0400 (EDT)
Received: from us-cwi-iis-a02.cwusa.com ([146.135.85.100])
	by doberman.cwusa.com (8.9.1/8.9.1) with SMTP id QAA23746
	for <ietf@ietf.org>; Tue, 11 Apr 2000 16:56:11 -0400 (EDT)
Received: FROM us-cwi-exc-a10.cwusa.com BY us-cwi-iis-a02.cwusa.com ; Tue Apr 11 16:53:41 2000 -0400
Received: by us-cwi-exc-a10.cwi.cablew.com with Internet Mail Service (5.5.2650.21)
	id <2XXZNP5S>; Tue, 11 Apr 2000 16:56:07 -0400
Message-ID: <F685A00DB7B4D111B2400020AFFC2D580847EF3B@us-cwi-exc-a03.cwi.cablew.com>
From: "BookIII, Robert" <Robert.BookIII@cwusa.com>
To: "'Joe Touch'" <touch@ISI.EDU>,
        Vernon Schryver
	 <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: RE: interception proxies
Date: Tue, 11 Apr 2000 16:56:05 -0400
Return-Receipt-To: "BookIII, Robert" <Robert.BookIII@cwusa.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Joe,
	Am I to presume by your statement that you are of the mind that the
time for considering whether vs. which has already come and gone? Is there
anyone on this list who thinks that?

		-----Original Message-----
		From:	Joe Touch [mailto:touch@ISI.EDU]
		Sent:	Tuesday, April 11, 2000 4:03 PM
		To:	Vernon Schryver
		Cc:	ietf@ietf.org; touch@ISI.EDU
		Subject:	Re: interception proxies

		Vernon Schryver wrote:
		> 
		> > From: John Martin <jmartin@netapp.com>
		> 
		> > There has been a lot of discussion about the problems
associated with
		> > so-called "interception proxies". This discussion is
very much within the
		> > charter of the WREC WG. In fact, we even have a current
draft whose sole
		> > purpose is to document such problems.
		> >
		> > The known problems draft is at:
draft-ietf-wrec-known-prob-01.txt
		> >
		> > This is the first of two very useful documents being
produced by WREC; the
		> > first, a taxonomy of terminology is available as:
		> > draft-ietf-wrec-taxonomy-03.txt; I would suggest you
read this first.
		> 
		> The problems draft is interesting and depressing.  All of
the problems
		> listed are technical nits.  

		This was a choice - in some larger sense, if sourcing
other-owned IP
		addresses or TCP connections is considered an architectural
problem,
		needs to come down from above, rather than up from WREC. f

		> I don't know whether to be depressed, encouraged, or
neutral that WREC
		> seems to not be about port 25 traffic redirection and
interception proxies,
		> such as AOL's effort.  That there is no mention of the
problems that IP
		> fragmentation can cause interception proxies is
depressing.

		The problems of IP fragmentation are not unique to web
caching or
		replication proxies. They affect all interception proxies.
The issue of
		inteception proxies was around long before WREC, and is more
than just a
		caching or replication issue. 

		> Joining that mailing list would not be useful, prudent, or
honest for
		> people with sentiments like mine.  Moving the question of
the wisdom of
		> such proxies to WREC would be equivalent to moving the
question of the
		> wisdom of wiretapping to the wiretapping working group.
At best the group
		> WG consensus can be predicted.  At worst, the discussion
would legitimately
		> be considered disruptive and irrelevant.

		WREC is about proxies - there are plenty of 'architecturally
conformant'
		ways to do proxies. If the problems with transparent proxies
is an
		issue, WREC may be a good place (but not the only place) to
solicit
		input.

		> It appears that the WREC working group is doing exactly as
someone
		> lamented a day or two ago about working groups in general,
and not
		> considering the question of whether the mechanisms they
are working are
		> good ideas in the larger scheme of things.  WREC is only
concerned with
		> making them as good as possible.  (Yes, I checked recent
months of the
		> archives at ftp://cs.utk.edu/pub/wrec/)

		That's the property of WGs in general, by construction.
These questions
		sometimes get addressed in BOFs, but there is also often too
much
		momentum or political interest in establishing a
'standardizing
		presence' in an area. By the time a WG is formed, the time
for 'whether'
		has often passed in favor of 'which'.

		Joe



From owner-ietf-outbound  Tue Apr 11 17:10:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA20964
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 17:10:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20724
	for <ietf@ietf.org>; Tue, 11 Apr 2000 17:06:00 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id NAA05604;
	Tue, 11 Apr 2000 13:59:03 -0700 (PDT)
Message-ID: <38F391F6.92BFDEF8@isi.edu>
Date: Tue, 11 Apr 2000 13:58:30 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "BookIII, Robert" <Robert.BookIII@cwusa.com>
CC: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: interception proxies
References: <F685A00DB7B4D111B2400020AFFC2D580847EF3B@us-cwi-exc-a03.cwi.cablew.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



"BookIII, Robert" wrote:
> 
> Joe,
>         Am I to presume by your statement that you are of the mind that the
> time for considering whether vs. which has already come and gone? Is there
> anyone on this list who thinks that?

With respect to 'inside the WG', yes, the assumption has been (to me)
that the time had passed, with respect to the WG charter.

There is always time outside the WG to do so, or (if directed) to
recharter, pending interest and approval of the WG as well.

Joe



From owner-ietf-outbound  Tue Apr 11 18:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA23544
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 18:50:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23491
	for <ietf@ietf.org>; Tue, 11 Apr 2000 18:47:02 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id QAA29258
	for ietf@ietf.org  env-from <vjs>;
	Tue, 11 Apr 2000 16:47:04 -0600 (MDT)
Date: Tue, 11 Apr 2000 16:47:04 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004112247.QAA29258@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: interception proxies
X-Loop: ietf@ietf.org

> From: Joe Touch <touch@ISI.EDU>

> ...
> > The problems draft is interesting and depressing.  All of the problems
> > listed are technical nits.  
>
> This was a choice - in some larger sense, if sourcing other-owned IP
> addresses or TCP connections is considered an architectural problem,
> needs to come down from above, rather than up from WREC. f

Call me a non-team playing scab, but I refuse to the honor the old guild
work rule that limits the questions I can consider.  If sourcing
other-owned etc. or anything else is an architectural or other problem,
then professional pride ought to force one to raise the issue insetad of
waiting for the AD, IESG, IAB, or a plenary to redirect things.  But I
realize that's a minority view, and not just in IETF working groups or
even the IETF.
If only I could have had one pre-IPO share for every time I've been told
"we can't think about that; we'll have to ask to marketing" ...  on the
other hand, most of those shares would be merely expensive wallpaper.



> >                    ... That there is no mention of the problems that IP
> > fragmentation can cause interception proxies is depressing.
>
> The problems of IP fragmentation are not unique to web caching or
> replication proxies. They affect all interception proxies. The issue of
> inteception proxies was around long before WREC, and is more than just a
> caching or replication issue. 

Which is why it was depressing.  Oh, well, perhaps a future version of
the Problems draft will consider that issue and say as others wrote, it's
not a problem and can be fixed with big buffers watching IP ID's, avoiding
UDP, assuming good MSS's or discovery prevent TCP/IP fragmentation, or
whatever.


> ...
> That's the property of WGs in general, by construction. These questions
> sometimes get addressed in BOFs, but there is also often too much
> momentum or political interest in establishing a 'standardizing
> presence' in an area. By the time a WG is formed, the time for 'whether'
> has often passed in favor of 'which'.

Which was exactly the lament the other day.  By the time a Last Call rolls
around, it's months and $B of market cap late to worry about "whether?"
There are always screams about the unfairness of raising "whether" at such
a late date and vague reference to nearly completed implementations that
will have billions of installations by the end of the quarter, or when
IPv8 replaces IPv4 at the latest, exactly as we heard in response to the
initial comments about draft-cerpa-necp-02.txt.

I don't have a fix for the problem, except to steadfastly refuse to heed
cries from partisans that "whether?" is out of order until it really is.

 ...


] From: "BookIII, Robert" <Robert.BookIII@cwusa.com>

] Joe,
]        Am I to presume by your statement that you are of the mind that the
] time for considering whether vs. which has already come and gone? Is there
] anyone on this list who thinks that?

I don't speak for Joe, but it's clearly over.  Unlike the wiretapping
question, interception proxies are too near to the technical interests
(and pocketbooks) of too many IETF participants.  You must admit that they
sound like cool hacks, unlike merely forwarding copies of bits.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Tue Apr 11 19:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA24110
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 19:50:02 -0400 (EDT)
Received: from lint.cisco.com (lint.cisco.com [171.68.224.209])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24051
	for <ietf@ietf.org>; Tue, 11 Apr 2000 19:45:27 -0400 (EDT)
Received: from elearhomepc (elear-dsl3.cisco.com [10.19.144.52]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id QAA23245; Tue, 11 Apr 2000 16:44:30 -0700 (PDT)
Message-ID: <004701bfa410$0e8e44e0$3490130a@cisco.com>
From: "Eliot Lear" <lear@cisco.com>
To: "John Martin" <jmartin@netapp.com>
Cc: <ietf@ietf.org>
References: <200004061641.MAA15198@astro.cs.utk.edu> <4.2.0.58.20000410141804.00c35ab0@pop.netapp.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Date: Tue, 11 Apr 2000 16:45:45 -0700
Organization: Cisco Systems
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

This whole thread is perhaps the best reason to have protocols go through
working groups, so that concerns can be raised and documented, and so that
the IESG can weigh in on correctness, risks, and yes, to a certain extent
morality.

I wonder if any of the authors has explored the risks of modifying data in
flight.  How could this be abused by interlopers and evil doers?  If I
could hack into a router implementing NECP, what damage could I do?  Could
I start a nasty little JavaScript/Java/Shockwave/... applet in an
advertisement?
And who would know it was me?

Quoth John Martin:
> [...]
> Let me be absolutely clear, NECP is about communication between server
> load-balancers (SLB) and the back-end servers they speak to.

Were this so clear in your document my mailbox wouldn't be full of this
stuff.

> The document is not an IETF standard but it does describe a protocol. For
> protocols to work correctly, there must be certain "mandatory" minimal
> requirements on those implementing that protocol.

If it looks like a duck and quacks like a duck, but it's not supposed to be
a duck, the IESG ought to point out that it's a turkey by so indicating at
the top of the document.  Also, I'd like to understand why you're not going
experimental, where it would be expected that you'll correct your mistakes.
Your choice of "informational" seems unfortunate at best and as
disingenuous marketing at worst.  I can't tell which.

> I can see one or two places where the word "standard" might be
> misinterpreted by readers if used out of context.

You somehow missed Section 1:

...  NECP provides a standard method for this signaling.

>
> >2. A primary purpose of the NECP protocol appears to be to
> >facilitate the operation of so-called interception proxies.
>
> Wrong. The primary purpose of NECP is to facilitate a load-balancing
> between SLBs and the services to which they direct traffic. "so-called
> interception proxies" are just one such service.

The document says:

   NECP now provides a
   standard server-to-network signalling interface.  This allows
   network elements in heterogenous environments to perform load
   balancing across a server farm, redirection to interception
   proxies, and cut-through of flows that can not be served by the
   farm.

The fact that you mention interception proxies in the introduction has led
to this flame war.  Having used the words, you've mentioned none of the
risks associated with such services both from the server side and the
client side.

> >Such  proxies violate the Internet Protocol in several ways:
>
> This is not about those proxies - that is a different argument.
>
> I  don't think it is appropriate to be drawn into an argument about the
> rights and wrongs of "interception proxies" when discussing NECP. I am
more
> than happy to justify their existence - with hard facts, of course - in a
> separate thread.

In whatever thread, the document fails to mention the legitimate security
concerns of those people who are concerned about interception.  I would
argue that our other flame war on wire tapping is (unfortunately) relevant.

Eliot Lear
Cisco Systems




From owner-ietf-outbound  Tue Apr 11 20:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA24284
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 20:00:01 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24192
	for <ietf@ietf.org>; Tue, 11 Apr 2000 19:56:03 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id QAA28981;
	Tue, 11 Apr 2000 16:55:59 -0700 (PDT)
Message-ID: <38F3BB6D.C78A0690@isi.edu>
Date: Tue, 11 Apr 2000 16:55:25 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org, touch@ISI.EDU
Subject: Re: interception proxies
References: <200004111612.KAA22474@calcite.rhyolite.com> <38F384F6.B0238438@isi.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

...
> > Joining that mailing list would not be useful, prudent, or honest for
> > people with sentiments like mine.  Moving the question of the wisdom of
> > such proxies to WREC would be equivalent to moving the question of the
> > wisdom of wiretapping to the wiretapping working group.  At best the group
> > WG consensus can be predicted.  At worst, the discussion would legitimately
> > be considered disruptive and irrelevant.
> 
> WREC is about proxies - there are plenty of 'architecturally conformant'
> ways to do proxies. If the problems with transparent proxies is an
> issue, WREC may be a good place (but not the only place) to solicit
> input.

Correction - slip of the keyboard. What I meant was that WREC is _NOT_
about proxies. It's about caching and replication. Proxies are one part
of the architecture, but not the only part.

Joe



From owner-ietf-outbound  Tue Apr 11 20:10:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA24488
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 20:10:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24312
	for <ietf@ietf.org>; Tue, 11 Apr 2000 20:00:38 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id TAA07437;
        Tue, 11 Apr 2000 19:59:45 -0400 (EDT)
Message-Id: <200004112359.TAA07437@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Joe Touch <touch@ISI.EDU>
cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: interception proxies 
In-reply-to: Your message of "Tue, 11 Apr 2000 13:03:02 PDT."
             <38F384F6.B0238438@isi.edu> 
Date: Tue, 11 Apr 2000 19:59:45 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> This was a choice - in some larger sense, if sourcing other-owned IP
> addresses or TCP connections is considered an architectural problem,
> needs to come down from above, rather than up from WREC. 

sounds like a convenient excuse to me...
where did the wrec folks get the idea that the IP specification was obsolete?

Keith



From owner-ietf-outbound  Tue Apr 11 20:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA24663
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 20:20:01 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24382
	for <ietf@ietf.org>; Tue, 11 Apr 2000 20:03:21 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id UAA07469;
        Tue, 11 Apr 2000 20:02:31 -0400 (EDT)
Message-Id: <200004120002.UAA07469@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: interception proxies 
In-reply-to: Your message of "Tue, 11 Apr 2000 16:47:04 MDT."
             <200004112247.QAA29258@calcite.rhyolite.com> 
Date: Tue, 11 Apr 2000 20:02:31 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Call me a non-team playing scab, but I refuse to the honor the old guild
> work rule that limits the questions I can consider.  If sourcing
> other-owned etc. or anything else is an architectural or other problem,
> then professional pride ought to force one to raise the issue insetad of
> waiting for the AD, IESG, IAB, or a plenary to redirect things.

agree entirely.  but for this to work there have to be folks within
the WG who are willing to raise a fuss.  

Keith



From owner-ietf-outbound  Tue Apr 11 20:30:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA24835
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 20:30:03 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24515
	for <ietf@ietf.org>; Tue, 11 Apr 2000 20:10:32 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id RAA00529;
	Tue, 11 Apr 2000 17:10:29 -0700 (PDT)
Message-ID: <38F3BED4.26704EFD@isi.edu>
Date: Tue, 11 Apr 2000 17:09:56 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: interception proxies
References: <200004112359.TAA07437@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

FWIW, there _was_ discussion in WREC of the hazards of transparent web
caching. I dug up an old e-mail, describing the hazards of transparent
web caching which I summarized at the time, when WREC was forming.

A copy of the note, admittedly very rough (just an outline, and a very
rough one at that) is at:

	http://www.isi.edu/touch/pubs/hazards-outline.txt

I would be glad to host further discussion on the WREC maillist as to
how to augment the list and flesh it out to a full I-D before the next
IETF, if there is sufficient interest.

Joe



From owner-ietf-outbound  Tue Apr 11 20:40:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA25021
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 20:40:02 -0400 (EDT)
Received: from breakaway.Stanford.EDU (breakaway.Stanford.EDU [171.64.20.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24774
	for <ietf@ietf.org>; Tue, 11 Apr 2000 20:26:06 -0400 (EDT)
Received: from localhost (hodges@localhost)
	by breakaway.Stanford.EDU (8.9.3/8.9.3) with ESMTP id RAA00756;
	Tue, 11 Apr 2000 17:26:06 -0700 (PDT)
Message-Id: <200004120026.RAA00756@breakaway.Stanford.EDU>
X-Mailer: exmh version 2.0.2 2/24/98
Subject: rfc-editor?
To: ietf@ietf.org
cc: Jeff.Hodges@kingsmountain.com
From: Jeff.Hodges@kingsmountain.com
Reply-to: Jeff.Hodges@kingsmountain.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 11 Apr 2000 17:26:06 -0700
Sender: hodges@Wind.Stanford.EDU
X-Loop: ietf@ietf.org

I have a question: so ~who~ is the RFC-Editor these days given that The 
RFC-Editor (aka Jon Postel) has passed on? I've groveled thru the www.ietf.org 
and the www.rfc-editor.org pages and can't see who all is presently acting in 
this role, but perhaps I simply missed it.

Am just overall curious.

thanks,

JeffH




From owner-ietf-outbound  Tue Apr 11 20:50:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA25194
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 20:50:02 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25080
	for <ietf@ietf.org>; Tue, 11 Apr 2000 20:42:00 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 12fBEF-0009d5-00; Tue, 11 Apr 2000 17:41:59 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Jeff.Hodges@kingsmountain.com
Cc: ietf@ietf.org
Subject: Re: rfc-editor?
References: <200004120026.RAA00756@breakaway.Stanford.EDU>
Message-Id: <E12fBEF-0009d5-00@rip.psg.com>
Date: Tue, 11 Apr 2000 17:41:59 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> I have a question: so ~who~ is the RFC-Editor these days given that The
> RFC-Editor (aka Jon Postel) has passed on? I've groveled thru the
> www.ietf.org and the www.rfc-editor.org pages and can't see who all is
> presently acting in this role, but perhaps I simply missed it.

brought to you by most of the same folk it has been for years, sadly minus
one.

randy



From owner-ietf-outbound  Tue Apr 11 21:20:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA25687
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 21:20:02 -0400 (EDT)
Received: from breakaway.Stanford.EDU (breakaway.Stanford.EDU [171.64.20.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25663
	for <ietf@ietf.org>; Tue, 11 Apr 2000 21:19:32 -0400 (EDT)
Received: from localhost (hodges@localhost)
	by breakaway.Stanford.EDU (8.9.3/8.9.3) with ESMTP id SAA01230
	for <ietf@ietf.org>; Tue, 11 Apr 2000 18:19:33 -0700 (PDT)
Message-Id: <200004120119.SAA01230@breakaway.Stanford.EDU>
X-Mailer: exmh version 2.0.2 2/24/98
Subject: Re: rfc-editor? 
To: ietf@ietf.org
In-reply-to: Your message of Tue, 11 Apr 2000 17:41:59 -0700
Reply-to: ietf@ietf.org
From: Jeff.Hodges@kingsmountain.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 11 Apr 2000 18:19:33 -0700
Sender: hodges@Wind.Stanford.EDU
X-Loop: ietf@ietf.org

I found the following in rfc2028..

> 2.1  The Request for Comments Editor
>
>    The RFC publication series [B] is managed by an Editor (which may in
>    practice be one or more individuals) responsible both for the
>    mechanics of RFC publication and for upholding the traditionally 
>    high technical and editorial standards of the RFC series.

>    The functions of the RFC Editor are performed by one or more
>    individuals or organizations selected in accordance with the
>    procedures defined by the RFC Editor charter [G].

And [G] is simply..

>    [G] RFC Editor Charter, Work in Progress.

..and perusal with various search engines/tools yields no further information 
about "RFC Editor Charter", and rfc2028 was written in late 1996.

randy@psg.com said:
> brought to you by most of the same folk it has been for years

Well, uh, besides Joyce Reynolds, I'm curious as to who all are actively 
contributing to that role. Is it folks on the IAB? Is it folks at IANA (and, 
uh, who zactly these days is affiliated with IANA besides the well-known 
board? who're the doers?)? Is it just anybody at ISI? Is it part of being on 
the IESG being an AD? Is it WG chairs? Who gets to decide?

How is it presently decided who may participate in acting in the RFC-Editor 
role?

I'm just sorta curious cuz it seems to be an opaque object in the otherwise 
fairly well-defined works (of the IETF et al).

thanks,

JeffH




From owner-ietf-outbound  Tue Apr 11 22:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA27366
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 22:30:02 -0400 (EDT)
Received: from bartman.ic.sunysb.edu (bartman.ic.sunysb.edu [129.49.1.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27314
	for <ietf@ietf.org>; Tue, 11 Apr 2000 22:24:26 -0400 (EDT)
Received: from sparky.ic.sunysb.edu (vdutta@sparky.ic.sunysb.edu [129.49.1.3])
	by bartman.ic.sunysb.edu (8.9.3/8.9.3) with ESMTP id WAA23640
	for <ietf@ietf.org>; Tue, 11 Apr 2000 22:24:26 -0400 (EDT)
Received: from localhost (vdutta@localhost)
	by sparky.ic.sunysb.edu (8.9.3/8.9.1) with ESMTP id WAA27589
	for <ietf@ietf.org>; Tue, 11 Apr 2000 22:24:26 -0400 (EDT)
X-Authentication-Warning: sparky.ic.sunysb.edu: vdutta owned process doing -bs
Date: Tue, 11 Apr 2000 22:24:26 -0400 (EDT)
From: Vishal Dutta MCP <vdutta@ic.sunysb.edu>
To: ietf@ietf.org
Subject: Re: rfc-editor? 
In-Reply-To: <200004120119.SAA01230@breakaway.Stanford.EDU>
Message-ID: <Pine.GSO.4.21.0004112223570.22471-100000@sparky.ic.sunysb.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

  Can anyone send the faq that was sent out a few months ago..
thanks




From owner-ietf-outbound  Tue Apr 11 23:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA29567
	for ietf-outbound.10@ietf.org; Tue, 11 Apr 2000 23:40:02 -0400 (EDT)
Received: from tsx-prime.MIT.EDU (TSX-PRIME.MIT.EDU [18.86.0.76])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA29530
	for <ietf@ietf.org>; Tue, 11 Apr 2000 23:37:26 -0400 (EDT)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id XAA14939; Tue, 11 Apr 2000 23:37:24 -0400
Date: Tue, 11 Apr 2000 23:37:24 -0400
Message-Id: <200004120337.XAA14939@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: ietf@ietf.org
In-reply-to: Vernon Schryver's message of Tue, 11 Apr 2000 16:47:04 -0600
	(MDT), <200004112247.QAA29258@calcite.rhyolite.com>
Subject: Re: interception proxies
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   Date: Tue, 11 Apr 2000 16:47:04 -0600 (MDT)
   From: Vernon Schryver <vjs@calcite.rhyolite.com>

   Which is why it was depressing.  Oh, well, perhaps a future version of
   the Problems draft will consider that issue and say as others wrote, it's
   not a problem and can be fixed with big buffers watching IP ID's, avoiding
   UDP, assuming good MSS's or discovery prevent TCP/IP fragmentation, or
   whatever.

And the latest kludge which has been called to my attention is ISP's
that tamper with the MSS values in TCP SYN packets in flight.  This is
done to work around smaller MTU's caused by PPP over Ethernet (and other
tunnelling mechanisms) interacting badly with Path MTU discovery
failures, which in turn are caused by firewalls that filter out the
wrong sorts of ICMP packets.

Hmmm, yet another thing which IPSEC will break.....

							- Ted



From owner-ietf-outbound  Wed Apr 12 00:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA00316
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 00:30:02 -0400 (EDT)
Received: from mailserver-ng.cs.umbc.edu (mailserver-ng.cs.umbc.edu [130.85.100.230])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00021
	for <ietf@ietf.org>; Wed, 12 Apr 2000 00:03:21 -0400 (EDT)
Received: from localhost (wrath@localhost)
	by mailserver-ng.cs.umbc.edu (8.9.3/8.9.3) with SMTP id AAA10207;
	Wed, 12 Apr 2000 00:03:11 -0400 (EDT)
Date: Wed, 12 Apr 2000 00:03:08 -0400 (EDT)
From: Vijay Gill <wrath@cs.umbc.edu>
To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: interception proxies
In-Reply-To: <200004120337.XAA14939@tsx-prime.MIT.EDU>
Message-ID: <Pine.SOL.3.95.1000411235335.6281P-100000@mailserver-ng.cs.umbc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Tue, 11 Apr 2000, Theodore Y. Ts'o wrote:


> And the latest kludge which has been called to my attention is ISP's
> that tamper with the MSS values in TCP SYN packets in flight.  This is
> done to work around smaller MTU's caused by PPP over Ethernet (and other
> tunnelling mechanisms) interacting badly with Path MTU discovery
> failures, which in turn are caused by firewalls that filter out the
> wrong sorts of ICMP packets.
> 
> Hmmm, yet another thing which IPSEC will break.....

Any specific ISP's that one could care to name?  Coming from an ISP, what
I've seen in general is that most routers have just enough cycles in the
forwarding path to keep up with the offered traffic, much less sit around
watching for SYN's in flight so as to mutate the MSS values.  In fact, I'd
think this would be more of an end system issue rather than a "core" or a
"backbone" issue, where the end system is the box prior to the ISP handoff
and not quite under the ISP's control and not the end system as in the
end2end tcp/ip sense of the word.


/vijay








From owner-ietf-outbound  Wed Apr 12 01:10:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA01413
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 01:10:04 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00773
	for <ietf@ietf.org>; Wed, 12 Apr 2000 01:04:26 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id XAA05262
	for ietf@ietf.org  env-from <vjs>;
	Tue, 11 Apr 2000 23:04:26 -0600 (MDT)
Date: Tue, 11 Apr 2000 23:04:26 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004120504.XAA05262@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: interception proxies
X-Loop: ietf@ietf.org

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

> ...
> agree entirely.  but for this to work there have to be folks within
> the WG who are willing to raise a fuss.  

That's a good point, but there is another question that must always be
asked.  When there is no hope of influencing something, then it can be
important to not participate.  Participation even in opposition inevitably
supports the official position.  30 years ago the word "co-opted" was used
to describe the problem.

My impression from the two WG documents is that in the WG consensus is
that HTTP interception proxies are at least tolerable and often necessary
and good, and by extension probably also for SMTP and everything else.

Yes, I noticed that "W" in "WREC" doesn't stand for "mail".  It's also
clear that intercepting or proxying are at most aspects of the "RE" and
the "C", although I don't see how that is relevant to whether the WG is
committed to interception proxies.  Draft-cerpa-necp-02.txt must be read
as advocating them, and not only for HTTP or whatever is meant by "Web."
Yes, I realize that draft wasn't a product of the WREC WG.  The two WREC
documents cannot be read as deprecating interception proxies and can be
read as advocating them by what they fail to say.


    ....

] From: Joe Touch <touch@ISI.EDU>

] FWIW, there _was_ discussion in WREC of the hazards of transparent web
] caching. I dug up an old e-mail, describing the hazards of transparent
] web caching which I summarized at the time, when WREC was forming.
]
] A copy of the note, admittedly very rough (just an outline, and a very
] rough one at that) is at:
]
] 	http://www.isi.edu/touch/pubs/hazards-outline.txt

I really like "in effect, it is a use of IP spoofing to do replay attacks."

(Why a 3rd document instead of added to Problems?)

] I would be glad to host further discussion on the WREC maillist as to
] how to augment the list and flesh it out to a full I-D before the next
] IETF, if there is sufficient interest.

Do you two think that either the IETF or the WREC working group might
agree with the thrust of that outline?  It sounds as if your answer is
"yes" and that my sense of WREC, IETF, and maybe industry sentiment is
wrong.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Wed Apr 12 08:30:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA17020
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 08:30:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16930
	for <ietf@ietf.org>; Wed, 12 Apr 2000 08:27:03 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id IAA00981;
        Wed, 12 Apr 2000 08:26:39 -0400 (EDT)
Message-Id: <200004121226.IAA00981@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: interception proxies 
In-reply-to: Your message of "Tue, 11 Apr 2000 23:04:26 MDT."
             <200004120504.XAA05262@calcite.rhyolite.com> 
Date: Wed, 12 Apr 2000 08:26:39 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> > From: Keith Moore <moore@cs.utk.edu>
> 
> > ...
> > agree entirely.  but for this to work there have to be folks within
> > the WG who are willing to raise a fuss.  
> 
> That's a good point, but there is another question that must always be
> asked.  When there is no hope of influencing something, then it can be
> important to not participate.  

My experience is that it's usually possible for an active participate
in an IETF group to influence it in a favorable way.  Despite my pessimism
about wrec, I think it may still be possible for it to produce useful
things.  If that's found to not be the case, one can ask the ADs to shut 
down the group - but the only fair thing to do is to try first.

> Participation even in opposition inevitably supports the official position.  
> 30 years ago the word "co-opted" was used to describe the problem.

at some point you need to decide whether you will go along with the
rest of the group or whether you will dissent.  but I would argue that
failure to participate in the discussion does more to support the
"official" [your word, not mine] position than participation in the
discussion.

> My impression from the two WG documents is that in the WG consensus is
> that HTTP interception proxies are at least tolerable and often necessary
> and good, and by extension probably also for SMTP and everything else.

the documents aren't published yet.  this can serve as a heads-up.

I will note that the wrec list has several new subscribers in the last
day or two.

> Yes, I noticed that "W" in "WREC" doesn't stand for "mail".  It's also
> clear that intercepting or proxying are at most aspects of the "RE" and
> the "C", although I don't see how that is relevant to whether the WG is
> committed to interception proxies.  Draft-cerpa-necp-02.txt must be read
> as advocating them, and not only for HTTP or whatever is meant by "Web."

perhaps that is something else that should be fixed...
(or another argument against publication)

> Yes, I realize that draft wasn't a product of the WREC WG.  The two WREC
> documents cannot be read as deprecating interception proxies and can be
> read as advocating them by what they fail to say.

yep, and this should be fixed also.

Keith



From owner-ietf-outbound  Wed Apr 12 09:00:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA18021
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 09:00:03 -0400 (EDT)
Received: from saint.heaven.net (saint.heaven.net [198.69.28.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17987
	for <ietf@ietf.org>; Wed, 12 Apr 2000 08:59:33 -0400 (EDT)
Received: (from stpeters@localhost)
	by saint.heaven.net (8.9.3/8.9.3) id IAA27363;
	Wed, 12 Apr 2000 08:59:25 -0400
From: "Dick St.Peters" <stpeters@NetHeaven.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14580.29485.86029.635273@saint.heaven.net>
Date: Wed, 12 Apr 2000 08:59:25 -0400 (EDT)
To: ietf@ietf.org
Reply-To: <ietf@ietf.org>
Subject: Re: interception proxies 
In-Reply-To: <200004112359.TAA07437@astro.cs.utk.edu>
References: <38F384F6.B0238438@isi.edu>
	<200004112359.TAA07437@astro.cs.utk.edu>
X-Mailer: VM 6.72 under Emacs 19.34.1
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Keith Moore writes:
> > This was a choice - in some larger sense, if sourcing other-owned IP
> > addresses or TCP connections is considered an architectural problem,
> > needs to come down from above, rather than up from WREC. 
> 
> sounds like a convenient excuse to me...
> where did the wrec folks get the idea that the IP specification was obsolete?

Quoted from RFC791, the IP specification, in the section on loose
source routing, page 19 [emphasis added]:

   If the address in destination address field has been reached and
   the pointer is not greater than the length, the next address in
   the source route replaces the address in the destination address
   field, and the recorded route address REPLACES THE SOURCE
   ADDRESS just used, and pointer is increased by four.
   
   The recorded route address is the internet module's own internet
   address as known in the environment into which this datagram is
   being forwarded.

An end-to-end-inviolate source address is not a required part of the
IP spec.

The authors of the standard had the vision to foresee that rewriting
the source address might be desireable under some circumstances.  They
were off target about when this might be used, but they designed a
protocol flexible enough to encompass things they could not foresee.

--
Dick St.Peters, stpeters@NetHeaven.com 
Gatekeeper, NetHeaven, Saratoga Springs, NY
Saratoga/Albany/Amsterdam/BoltonLanding/Cobleskill/Greenwich/
GlensFalls/LakePlacid/NorthCreek/Plattsburgh/...
    Oldest Internet service based in the Adirondack-Albany region



From owner-ietf-outbound  Wed Apr 12 10:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA20708
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 10:00:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20398
	for <ietf@ietf.org>; Wed, 12 Apr 2000 09:51:10 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA01576
        for <ietf@ietf.org>; Wed, 12 Apr 2000 09:50:48 -0400 (EDT)
Message-Id: <200004121350.JAA01576@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: ietf@ietf.org
Subject: Re: interception proxies 
In-reply-to: Your message of "Wed, 12 Apr 2000 08:59:25 EDT."
             <14580.29485.86029.635273@saint.heaven.net> 
X-SUBJECT-MSG-FROM: "Dick St.Peters" <stpeters@NetHeaven.com> 
Date: Wed, 12 Apr 2000 09:50:48 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> The authors of the standard had the vision to foresee that rewriting
> the source address might be desireable under some circumstances.

the authors of the IP standard provided for loose source routing.
this should not be interpreted as license to impersonate a host
when source routing was not requested by the source.



From owner-ietf-outbound  Wed Apr 12 10:20:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA21649
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 10:20:02 -0400 (EDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21378
	for <ietf@ietf.org>; Wed, 12 Apr 2000 10:14:25 -0400 (EDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id PAA22974 for <ietf@ietf.org>; Wed, 12 Apr 2000 15:13:43 +0100
Received: from hursley.ibm.com (lig32-227-11-59.us.lig-dial.ibm.com [32.227.11.59]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id PAA23358 for <ietf@ietf.org>; Wed, 12 Apr 2000 15:13:55 +0100 (BST)
Message-ID: <38F484A3.AE0002A2@hursley.ibm.com>
Date: Wed, 12 Apr 2000 09:13:55 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: rfc-editor?
References: <200004120119.SAA01230@breakaway.Stanford.EDU>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Jeff,

The RFC Editor function is the subject of a contract, paid for and 
issued by the Internet Society on behalf of the IETF. The IAB, which
I chaired until 2 weeks ago, by its latest charter "must approve the 
appointment of an organization to act as RFC Editor and the general 
policy followed by the RFC Editor."

The current contractor is the Information Sciences Institute of the
University of Southern California, where the late Jon Postel worked.

There is no individual human acting as RFC Editor; it's a team effort
at ISI.

The charter never got written; it was on Jon's to do list when he passed
away. But of course there is a statement of work in the ISOC contract,
and a member of the RFC Editor team reports at each IETF meeting.
You can see the current status of the RFC Editor's queue at
http://www.rfc-editor.org/queue.html

   Brian Carpenter

Jeff.Hodges@kingsmountain.com wrote:
> 
> I found the following in rfc2028..
> 
> > 2.1  The Request for Comments Editor
> >
> >    The RFC publication series [B] is managed by an Editor (which may in
> >    practice be one or more individuals) responsible both for the
> >    mechanics of RFC publication and for upholding the traditionally
> >    high technical and editorial standards of the RFC series.
> 
> >    The functions of the RFC Editor are performed by one or more
> >    individuals or organizations selected in accordance with the
> >    procedures defined by the RFC Editor charter [G].
> 
> And [G] is simply..
> 
> >    [G] RFC Editor Charter, Work in Progress.
> 
> ..and perusal with various search engines/tools yields no further information
> about "RFC Editor Charter", and rfc2028 was written in late 1996.
> 
> randy@psg.com said:
> > brought to you by most of the same folk it has been for years
> 
> Well, uh, besides Joyce Reynolds, I'm curious as to who all are actively
> contributing to that role. Is it folks on the IAB? Is it folks at IANA (and,
> uh, who zactly these days is affiliated with IANA besides the well-known
> board? who're the doers?)? Is it just anybody at ISI? Is it part of being on
> the IESG being an AD? Is it WG chairs? Who gets to decide?
> 
> How is it presently decided who may participate in acting in the RFC-Editor
> role?
> 
> I'm just sorta curious cuz it seems to be an opaque object in the otherwise
> fairly well-defined works (of the IETF et al).
> 
> thanks,
> 
> JeffH



From owner-ietf-outbound  Wed Apr 12 10:40:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA22638
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 10:40:03 -0400 (EDT)
Received: from CLYNN.BBN.COM (CLynn.BBN.COM [128.89.1.209])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA22307
	for <ietf@ietf.org>; Wed, 12 Apr 2000 10:32:58 -0400 (EDT)
Message-Id: <200004121432.KAA22307@ietf.org>
Date:     Wed, 12 Apr 2000 10:21:43 +0500 (EDT)
From: Charles Lynn <clynn@BBN.COM>
To: "Dick St.Peters" <stpeters@netheaven.com>
cc: ietf@ietf.org
Subject:  Re:  interception proxies
X-Loop: ietf@ietf.org

Dick,

> Quoted from RFC791, the IP specification, in the section on loose
> source routing, page 19 [emphasis added]:
> 
>    If the address in destination address field has been reached and
>    the pointer is not greater than the length, the next address in
>    the source route replaces the address in the destination address
>    field, and the recorded route address REPLACES THE SOURCE
>    ADDRESS just used, and pointer is increased by four. 

You have misread the specification.  That "source" is not (IP Header)
"Source Address" that you imply, but the "source" mentioned earlier in
the sentence, i.e., "address in the source route" (option).

The IP Header Source Address is not changed by the source routing options.
(Nor in the case of IPv6 style source routing.)

[If you think about it, the interpretation you emphasized above will
not result in a capability for bi-directional communication.]

Charlie



From owner-ietf-outbound  Wed Apr 12 10:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA23035
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 10:50:02 -0400 (EDT)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22700
	for <ietf@ietf.org>; Wed, 12 Apr 2000 10:41:28 -0400 (EDT)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id JAA05445
	for <ietf@ietf.org>; Wed, 12 Apr 2000 09:41:29 -0500 (CDT)
Message-Id: <200004121441.JAA05445@gungnir.fnal.gov>
To: ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: interception proxies 
In-reply-to: Your message of Wed, 12 Apr 2000 08:59:25 EDT.
             <14580.29485.86029.635273@saint.heaven.net> 
Date: Wed, 12 Apr 2000 09:41:28 -0500
Sender: crawdad@gungnir.fnal.gov
X-Loop: ietf@ietf.org

Dick St.Peters says:
> Quoted from RFC791, the IP specification, in the section on loose
> source routing, page 19 [emphasis added]:
> 
>    If the address in destination address field has been reached and
>    the pointer is not greater than the length, the next address in
>    the source route replaces the address in the destination address
>    field, and the recorded route address REPLACES THE SOURCE
>    ADDRESS just used, and pointer is increased by four.
>    ...
> An end-to-end-inviolate source address is not a required part of the
> IP spec.

If you look upward two paragraphs from the part you quoted, you'll
see that "source address" does not mean the first address in the
fixed part of the IP header, but the address in the "route data"
provided by the source.
______________________________________________________________________________
Matt Crawford                    crawdad@fnal.gov                     Fermilab
"A5.1.5.2.7.1. Remove all classified and CCI boards from the COMSEC equipment,
thoroughly smash them with a hammer or an ax, and scatter the pieces."



From owner-ietf-outbound  Wed Apr 12 11:40:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA24741
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 11:40:01 -0400 (EDT)
Received: from shell16.ba.best.com (heard@shell16.ba.best.com [206.184.139.148])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24453
	for <ietf@ietf.org>; Wed, 12 Apr 2000 11:30:43 -0400 (EDT)
Received: from localhost (heard@localhost)
	by shell16.ba.best.com (8.9.3/8.9.2/best.sh) with ESMTP id IAA15884
	for <ietf@ietf.org>; Wed, 12 Apr 2000 08:30:43 -0700 (PDT)
X-Authentication-Warning: shell16.ba.best.com: heard owned process doing -bs
Date: Wed, 12 Apr 2000 08:30:43 -0700 (PDT)
From: "C. M. Heard" <heard@vvnet.com>
X-Sender: heard@shell16.ba.best.com
To: ietf@ietf.org
Subject: Re: interception proxies
In-Reply-To: <14580.29485.86029.635273@saint.heaven.net>
Message-ID: <Pine.BSF.4.21.0004120821140.13306-100000@shell16.ba.best.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Wed, 12 Apr 2000, Dick St.Peters wrote:

> Quoted from RFC791, the IP specification, in the section on loose
> source routing, page 19 [emphasis added]:
>
>    If the address in destination address field has been reached and
>    the pointer is not greater than the length, the next address in
>    the source route replaces the address in the destination address
>    field, and the recorded route address REPLACES THE SOURCE
>    ADDRESS just used, and pointer is increased by four.
>
>    The recorded route address is the internet module's own internet
>    address as known in the environment into which this datagram is
>    being forwarded.
>
> An end-to-end-inviolate source address is not a required part of the
> IP spec.
>
> The authors of the standard had the vision to foresee that rewriting
> the source address might be desireable under some circumstances.  They
> were off target about when this might be used, but they designed a
> protocol flexible enough to encompass things they could not foresee.

I think you have misunderstood what the RFC intended to say.  The "source
address" being replaced is the entry in the LSRR option that is being
written into the destination field, not the source address in the IP
header, which is supposed to remain constant throughout its journey.

Anyway, a source route option was intended to be something that the
originating host puts into the datagram, and so the destination address
rewriting that does happen is being done by explicit request of the
originating host.  That's quite different from what an interception
proxy does, isn't it?

C. M. Heard
heard@vvnet.com



From owner-ietf-outbound  Wed Apr 12 11:50:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA25073
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 11:50:02 -0400 (EDT)
Received: from mail.tobit.com ([62.153.121.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24596
	for <ietf@ietf.org>; Wed, 12 Apr 2000 11:35:38 -0400 (EDT)
From: tkuiper@tobit.com
Subject: Cable as Firewall?!
To: ietf@ietf.org
Date: 12 Apr 2000 15:35:42 UT
Priority: normal
X-Priority: 3 (Normal)
Importance: normal
X-Mailer: David by Tobit Software, Germany (0170.0283256686)
X-David-Sym: 0
X-David-Flags: 0
Message-ID: <38F497CE@mail.tobit.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1DD2510B41FE"
X-Loop: ietf@ietf.org


--------------1DD2510B41FE
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

I'm at the end of all my knowledge and I can't find any explaination
for the following issue. So I hope anyone of you Network Guru's can
give me an idea why this would happen.

I have this scenario in a Network:

A couple of PC's are connected to a 3300 Switch made by 3COM
which are connected using 3 metres long TP (normal CAT5) cables.
The stations have diffrent OS'es like Linux and Novell Netware.
However the problem seems to be the cable not the operating systems.

I use diffrent protocols over this network to establish a communication,
like IPX and of course TCP/IP. Now the weird thing is if I use one cable,
IPX data comes through, but no TCP/IP traffic. If I exchange the cables
again, both TCP/IP and IPX work. I tried with tcpdump (filtering UDP and
diffrent ethernet protocols), but I only get IPX through with this cable!
I used diffrent stuff to test this cable, like fluke 2000 dsp pro and
fluke 1000 dsp and a lot of diffrent volt/ohm testers. The cable seems
to function ok. I tried other switches such as 3COM 3300,
HP pro curve 4000, DLink 10/100, but I only get IPX through with that cable.
This cable doesn't have a chip and ethernet is ethernet, no? I would really
like to know what makes this cable diffrent. Its not the operating systems
since I tried some Windows and other Netware 4.x server too. Both only
get IPX through it. How can a cable filter specific ethernet protocols?

Best Regards,
Thomas Kuiper

Thomas Kuiper        |   tkuiper@tobit.com   |  www.tobit.com     __
Core Development     |   TK3680-RIPE         |                   /__/\
Tobit Software       |   ICQ #8345483        |  ask your server. \__\/



--------------1DD2510B41FE--



From owner-ietf-outbound  Wed Apr 12 12:20:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA26140
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 12:20:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25717
	for <ietf@ietf.org>; Wed, 12 Apr 2000 12:10:48 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id MAA24298;
	Wed, 12 Apr 2000 12:10:46 -0400
Date: Wed, 12 Apr 2000 12:10:46 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200004121610.MAA24298@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: interception proxies
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

    > From: "Dick St.Peters" <stpeters@NetHeaven.com>

    > The authors of the standard had the vision to foresee ...
    > they designed a protocol flexible enough to encompass things they
    > could not foresee.

Pardon me if I emit a "balderdash".

There's this tendency to act like IPv4 was handed down on stone tablets by
Athena, the Goddess of Wisdom, herself - and I want to stamp it out. *I was
there*, and trust me, it wasn't a much (any?) different case of sausage
production than the average standard today. (Trivia question: what's the
connection between 32-bit IP addresses and the number of registers
available at interrupt time in Tenex?)

They had great foresight, huh? The foresight to see the need for more
address bits (funnily enough, IP2.5 *had* this, and they *ripped it out* -
great vision there), traffic flows, etc (I could go on but what's the
point).

Yes, IPv4 had some good ideas, ideas that have turned out well. It also has
some woeful deficiencies. (In some cases these are deficiencies that not
even Einstein could have forseen, so don't get me wrong, I'm not trying to
throw rocks about them.)

However, let's not mythologize anything, OK? It gets in the way of
objective analysis.

	Noel



From owner-ietf-outbound  Wed Apr 12 12:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA26345
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 12:30:03 -0400 (EDT)
Received: from smtp.mail.yahoo.com (smtp.mail.yahoo.com [128.11.68.32])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA25780
	for <ietf@ietf.org>; Wed, 12 Apr 2000 12:13:14 -0400 (EDT)
Received: from cci-209150224086.clarityconnect.net (HELO KHERMANN-NT2.yahoo.com) (209.150.224.86)
  by smtp.mail.yahoo.com with SMTP; 12 Apr 2000 09:13:15 -0700
X-Apparently-From: <ncc1701v@yahoo.com>
Message-Id: <4.3.1.2.20000412120700.00b0adb0@pop.mail.yahoo.com>
X-Sender: ncc1701v@pop.mail.yahoo.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 12 Apr 2000 12:13:06 -0400
To: Keith Moore <moore@cs.utk.edu>
From: Scott Brim <ncc1701v@yahoo.com>
Subject: Re: breaking the IP model (or not)
Cc: ietf@ietf.org
In-Reply-To: <200004102012.QAA12359@astro.cs.utk.edu>
References: <Your message of "Mon, 10 Apr 2000 11:50:05 EDT." <14577.63533.727116.329186@saint.heaven.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 04:12 PM 4/10/00 -0400, Keith Moore wrote:
>it's completely natural that people will try such approaches -
>they are trying to address real problems and they want quick
>solutions to those problems.  but if the quick fix solutions
>get entrenched then they cause their own set of problems which
>are worse then the original problems.  this is not progress.
>
>IMHO we need to see these things for what they are:
>
>- quick fixes with limited applicability and future
>- indicators that there is an important problem that needs to be
>   solved in a technically sound fashion

Agreed completely ... but this still doesn't lead to your 
conclusion.  Suppose we had suppressed every kludge that's come up since 
we started working on a new Internet design as a group?  Let me see, ROAD 
gave their report, where they recommended CLNP, in Santa Fe, right?  That 
was (let me look at the back of my shirt a second ...) in 1991.  OK, OK, 
I'm being a bit extreme but the point is that just because something is 
architecturally bad doesn't mean you shouldn't do it, since these days it 
takes us years to make any architectural enhancements.  Peter Deutsch is 
right: let the work go forward and *in addition* be sure you document 
very well what its limitations are.  Stick that documentation in the same 
RFCs whenever possible.

...Scott


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com



From owner-ietf-outbound  Wed Apr 12 12:50:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA27222
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 12:50:02 -0400 (EDT)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA27095
	for <ietf@ietf.org>; Wed, 12 Apr 2000 12:45:21 -0400 (EDT)
Received: (qmail 30526 invoked from network); 12 Apr 2000 16:45:20 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 12 Apr 2000 16:45:20 -0000
Received: (qmail 27393 invoked from network); 12 Apr 2000 16:45:18 -0000
Received: from ppp-46-195.lander.es (HELO salva) (195.76.46.195)
  by lince.lander.es with SMTP; 12 Apr 2000 16:45:18 -0000
Message-Id: <3.0.6.32.20000412185151.00811d50@lince.lander.es>
X-Sender: svidal@lince.lander.es
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Wed, 12 Apr 2000 18:51:51 +0200
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Salvador Vidal <svidal@lander.es>
Subject: Re: interception proxies
Cc: ietf@ietf.org
In-Reply-To: <200004111612.KAA22474@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA27095
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Hello Vernon,

>listed are technical nits.  If you assume that "traffic redirection"
>and an "interception proxy" are good things, then you might well worry
>about the "lack of HTTP/1.1 compliance for proxy caches" or whether
>"interception proxies break client cache directives."  You will not
>question their desirability or even their long term utility in the face
>of actions by users to protect their privacy or defend against censorship.

There are also good uses for interception, I think that ONGs, churchs, and
other organizations and people will want to become Internet trusters soon,
to defend their values throught Internet, and not only values there will be
also fun aplications of trusters.

The point is that the truster must be selected by the user not by
authoritarian impositon!.

i.e. I talk about ecology.

May be the first step of a ecologist truster will be to devolop a black
list of companies that are very agresive agains nature, the people that
join this truster will be able to have censorship of this companies in
order to presure them to change their behavior.

Perhaps later they will think that to get some ecological level is not
enought, that they want to develop a ecological ranking so people can
transmit the market the message that they must compite to be the eco-leader
on their sector if they want these customers, that is to get the strenth of
compititivity aplaied to ecology.

(Companies should heritage values from their supliers, in order to avoid
the trick that a very dirty industrie uses a very clean distribuitor for
their products, so let the end customer to pull all the prodution and
ditribution chain to ecologist positions)

This respect companies privacy if you don´t want an ecological evaluation
Ok you get a cero!.

Whith ranking values people will be able to weight them from different mix
of trusters that they select.

May be, later trusters will incrise their interactivity with their
customers, things like this information is Ok if that happends, or this
information is worthy combenid with this other, I don´t have idea of
trusters future evolution but almost sure that they will be adding more
inteligence and interactivity to their system.

At 10:00 06/04/00 -0300, Marin Montenegro wrote:
>The humanity is really in front of the product of the knowledge of some
>persons and is trying to save your houses of the flood with a small glass.

As world problems are getting more and more complex we don´t need some
iluminated people, with need everybodi feedback in order to see the all
picture, and perhaps trusters will be a good way to organize the knowlege
of the people, perhaps ecological trusters were unable to stop climatic
change, but sure they will be much more usefull than TO BURN GAS-STATIONS!.

As long as doesn´t look viable that trusters send huge updated databases to
users, I think that the information interception has to be done at ISP,
anyway I think that interception must be balence with the information owner
desires, He (I don´t write the slash he/she because is obius) has the right
that his information don´t pass trusters cesorship/filters/inteligent
system or whatever, as well as the user has the right to don´t attend any
information that don´t cross his trusters, of course there are positons in
between i.e. allowing the truster to put labels but not to change the
publicity ...

At 08:15 09/04/00 JST, Masataka Ohta wrote:
> it is impossible to ...

Impossible is just a small delay on Internet, thinking on it Mas.

Salva

>
>Vernon Schryver    vjs@rhyolite.com
>




From owner-ietf-outbound  Wed Apr 12 13:10:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA27936
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 13:10:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27891
	for <ietf@ietf.org>; Wed, 12 Apr 2000 13:08:55 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3CH8mB27342;
	Wed, 12 Apr 2000 13:08:48 -0400
Message-Id: <200004121708.e3CH8mB27342@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Salvador Vidal <svidal@LANDER.ES>
cc: ietf@ietf.org
Subject: Re: interception proxies 
In-reply-to: Your message of "Wed, 12 Apr 2000 18:51:51 +0200."
             <3.0.6.32.20000412185151.00811d50@lince.lander.es> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <3.0.6.32.20000412185151.00811d50@lince.lander.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0
Date: Wed, 12 Apr 2000 13:08:47 -0400
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA27891
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

On Wed, 12 Apr 2000 18:51:51 +0200, Salvador Vidal said:
> May be the first step of a ecologist truster will be to devolop a black
> list of companies that are very agresive agains nature, the people that
> join this truster will be able to have censorship of this companies in
> order to presure them to change their behavior.

This is unfortunately a Nice Idea, but probably well into the NP-messy category
of things.  The problem is that eliminating a sufficient amount of what the
statisticians call "false positives" will be quite challenging, and probably
involve a large amount of natural-language processing.

Typical scenarios you need to address:

1) If you are censoring company XYZ-Example.Com because of their dumping of
nuclear wastes into the local drinking supply, you need to make sure that your
censorship doesn't accidentally censor the press release they issue stating
that they have stopped doing it, and will pay to clean the drinking supply.

2) If you are censoring company ABC-Example.Com because of their CEO's viewpoint
on <insert touchy social topic here>, you want to be careful not to accidentally
censor a message from their chief networking manager that contains the technical
information that you asked for on a mailing list....

It would be a shame if you failed to get my commentary on your ideas because
you were censoring my employer because of their failure to rename a dormitory
currently named for a famous and illustrious person who has been alledged to
have been a racist at one time...

Remember - I may work for the University, but I'm almost always stating my OWN
opinions unless I specifically flag something as being "The Party Line".


-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Wed Apr 12 13:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA28623
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 13:30:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28272
	for <ietf@ietf.org>; Wed, 12 Apr 2000 13:21:58 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id LAA15969
	for ietf@ietf.org  env-from <vjs>;
	Wed, 12 Apr 2000 11:21:57 -0600 (MDT)
Date: Wed, 12 Apr 2000 11:21:57 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004121721.LAA15969@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: interception proxies
X-Loop: ietf@ietf.org

Yes, IP is not the perfect protocol, general rules can lead to trouble, and
so forth.

However, the IESG, AD's and IAB should consider tatooing the following
rule on all WG chairs or the foreheads those who sit in them:

 If IPSEC or other strong end-to-end encryption or authentication would
 interfere with a protocol or application, then it is almost certainly
 fatally flawed idea on other technical, administrative, legal, political,
 or ethical grounds.


 ...........


> From: Salvador Vidal <svidal@lander.es>

> ...
> There are also good uses for interception, I think that ONGs, churchs, and
> other organizations and people will want to become Internet trusters soon,
> to defend their values throught Internet, and not only values there will be
> also fun aplications of trusters.
> ...

That is based on a fundamental misunderstanding of interception proxies.
Unless your ONGs, churges, other organizations, and so forth operate
geographically non-trivial IP networks, they need not and should not use
interception proxies to censor the Internet.  It makes little sense to run
interception proxies only for computers that you also control.  For
example, a church that wants to censor the Internet would be better served
by configuring all of its computers to use its own explicit proxies than
using stealthy interception proxies.  The explicit proxies will be easier
to maintain and harder for backsliders to evade.  They're also more honest,
which some churches claim to consider a virtue.

That you support a goal (e.g. censorship or fighting spam) does not imply
that any mechanism that can be used for that goal is the right tool.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Wed Apr 12 13:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA29314
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 13:40:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28550
	for <ietf@ietf.org>; Wed, 12 Apr 2000 13:27:32 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA02386;
        Wed, 12 Apr 2000 13:27:06 -0400 (EDT)
Message-Id: <200004121727.NAA02386@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Scott Brim <ncc1701v@yahoo.com>
cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: breaking the IP model (or not) 
In-reply-to: Your message of "Wed, 12 Apr 2000 12:13:06 EDT."
             <4.3.1.2.20000412120700.00b0adb0@pop.mail.yahoo.com> 
Date: Wed, 12 Apr 2000 13:27:06 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> I'm being a bit extreme but the point is that just because something is 
> architecturally bad doesn't mean you shouldn't do it, since these days it 
> takes us years to make any architectural enhancements.

perhaps architectural impurity alone shouldn't keep you from doing 
something, but the fact that something violates fundamental design 
assumptions should cause you to do some analysis and hard thinking
about the likely consequences of using them.  and if you are in the
business of selling boxes that violate the design assumptions you 
shouldn't misrepresent these to your customers.

most of these hacks can be employed in ways that are mostly harmless,
but knowing when they are harmless and when they will cause harm
can be quite difficult.  NATs seemed mostly harmless when they were 
first deployed; now they're a huge problem.

Keith



From owner-ietf-outbound  Wed Apr 12 14:10:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA29954
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 14:10:03 -0400 (EDT)
Received: from saint.heaven.net (saint.heaven.net [198.69.28.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29814
	for <ietf@ietf.org>; Wed, 12 Apr 2000 14:02:23 -0400 (EDT)
Received: (from stpeters@localhost)
	by saint.heaven.net (8.9.3/8.9.3) id OAA31994;
	Wed, 12 Apr 2000 14:01:37 -0400
From: "Dick St.Peters" <stpeters@NetHeaven.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14580.47617.154623.427207@saint.heaven.net>
Date: Wed, 12 Apr 2000 14:01:37 -0400 (EDT)
To: ietf@ietf.org
Reply-To: <ietf@ietf.org>
Subject: Re:  interception proxies
In-Reply-To: <200004121433.KAA11030@angels.heaven.net>
References: <200004121433.KAA11030@angels.heaven.net>
X-Mailer: VM 6.72 under Emacs 19.34.1
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Charles Lynn writes:

> You have misread the specification.  That "source" is not (IP Header)
> "Source Address" that you imply, but the "source" mentioned earlier in
> the sentence, i.e., "address in the source route" (option).

Apparently so - though given that the part I emphasized immediately
follows mention of rewriting the destination address, this isn't
obvious.

> [If you think about it, the interpretation you emphasized above will
> not result in a capability for bi-directional communication.]

Actually, I've always thought that the first recorded-route address
was the original source address so the route would indeed be
reversible, but I'll admit to never having actually seen a recorded
route.

J. Noel Chiappa writes:

> Pardon me if I emit a "balderdash".
 ...
> They had great foresight, huh? The foresight to see the need for more
> address bits (funnily enough, IP2.5 *had* this, and they *ripped it out* -
> great vision there), traffic flows, etc (I could go on but what's the
> point).

Yes, just what was your point?

> However, let's not mythologize anything, OK? It gets in the way of
> objective analysis.

Actually, the view that everything about IP was cast in stone forever
in the IP spec is exactly the view that is being argued about.

Would you settle for "The IP spec authors didn't have enough foresight
to foresee a need to rewrite source addresses" ? :)

Whatever anyone thinks of it, people are doing it.  On the right are
people saying it is immoral, evil, and dangerous, not to mention
prohibited by the gods, and they refuse to talk about it.  On the left
are people doing it, each their own way because there is no standard
and not even any public discussion.

Only a few months after I first used the net, IP replaced NCP, giving
me an instant impression that network protocols are ephemeral things,
replaceable if they don't measure up.  Presumably if they can be
replaced, they can be adapted when necessary.

--
Dick St.Peters, stpeters@NetHeaven.com 



From owner-ietf-outbound  Wed Apr 12 14:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA00266
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 14:20:01 -0400 (EDT)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA29836
	for <ietf@ietf.org>; Wed, 12 Apr 2000 14:04:18 -0400 (EDT)
Received: (qmail 8705 invoked from network); 12 Apr 2000 18:04:17 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 12 Apr 2000 18:04:17 -0000
Received: (qmail 22805 invoked from network); 12 Apr 2000 18:04:16 -0000
Received: from ppp-47-239.lander.es (HELO salva) (195.76.47.239)
  by lince.lander.es with SMTP; 12 Apr 2000 18:04:16 -0000
Message-Id: <3.0.6.32.20000412201049.0088fea0@lince.lander.es>
X-Sender: svidal@lince.lander.es
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Wed, 12 Apr 2000 20:10:49 +0200
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Salvador Vidal <svidal@lander.es>
Subject: Re: interception proxies
Cc: ietf@ietf.org
In-Reply-To: <200004121721.LAA15969@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA29836
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Hello Vernon,

At 11:21 12/04/00 -0600, you wrote:
>Yes, IP is not the perfect protocol, general rules can lead to trouble, and
>so forth.
>
>However, the IESG, AD's and IAB should consider tatooing the following
>rule on all WG chairs or the foreheads those who sit in them:
>
> If IPSEC or other strong end-to-end encryption or authentication would
> interfere with a protocol or application, then it is almost certainly
> fatally flawed idea on other technical, administrative, legal, political,
> or ethical grounds.
>
>
> ...........
>
>
>> From: Salvador Vidal <svidal@lander.es>
>
>> ...
>> There are also good uses for interception, I think that ONGs, churchs, and
>> other organizations and people will want to become Internet trusters soon,
>> to defend their values throught Internet, and not only values there will be
>> also fun aplications of trusters.
>> ...
>
>That is based on a fundamental misunderstanding of interception proxies.
>Unless your ONGs, churges, other organizations, and so forth operate
>geographically non-trivial IP networks, they need not and should not use
>interception proxies to censor the Internet.  It makes little sense to run
>interception proxies only for computers that you also control.  For
>example, a church that wants to censor the Internet would be better served
>by configuring all of its computers to use its own explicit proxies than
>using stealthy interception proxies.  

I´m not talking about the computers inside a organization, but people
computers anywhere that trust in these organizations or persons to do
censor, ranking to do their purchases decisions or whatever they want!, and
probabily some people want to have more than one truster and balance them.

>The explicit proxies will be easier
>to maintain and harder for backsliders to evade.  They're also more honest,
>which some churches claim to consider a virtue.
>
>That you support a goal (e.g. censorship or fighting spam) does not imply
>that any mechanism that can be used for that goal is the right tool.

So please, which will be the right tool for a truster service?

Salva
>
>Vernon Schryver    vjs@rhyolite.com
>
>
>



From owner-ietf-outbound  Wed Apr 12 15:20:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA01519
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 15:20:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01427
	for <ietf@ietf.org>; Wed, 12 Apr 2000 15:12:24 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA03200
        for <ietf@ietf.org>; Wed, 12 Apr 2000 15:12:00 -0400 (EDT)
Message-Id: <200004121912.PAA03200@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: ietf@ietf.org
Subject: Re: interception proxies 
In-reply-to: Your message of "Wed, 12 Apr 2000 14:01:37 EDT."
             <14580.47617.154623.427207@saint.heaven.net> 
X-SUBJECT-MSG-FROM: "Dick St.Peters" <stpeters@NetHeaven.com> 
Date: Wed, 12 Apr 2000 15:12:00 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Actually, the view that everything about IP was cast in stone forever
> in the IP spec is exactly the view that is being argued about.

nobody has said anything about IP being cast in stone forever.

Keith



From owner-ietf-outbound  Wed Apr 12 16:30:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA02640
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 16:30:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02555
	for <ietf@ietf.org>; Wed, 12 Apr 2000 16:25:26 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id NAA00632;
	Wed, 12 Apr 2000 13:25:17 -0700 (PDT)
Message-ID: <38F4DB8A.8F35DC70@isi.edu>
Date: Wed, 12 Apr 2000 13:24:42 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: interception proxies
References: <200004112359.TAA07437@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Keith Moore wrote:
> 
> > This was a choice - in some larger sense, if sourcing other-owned IP
> > addresses or TCP connections is considered an architectural problem,
> > needs to come down from above, rather than up from WREC.
> 
> sounds like a convenient excuse to me...
> where did the wrec folks get the idea that the IP specification was obsolete?

(speaking not for the entire WREC, but my impression of the meetings) I
did get the impression (mistakenly or not) that addressing the whole of
the IP spec was not particularly in scope (e.g., from our area director,
who discussed scope at nearly every meeting).

Joe



From owner-ietf-outbound  Wed Apr 12 16:40:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA02896
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 16:40:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02801
	for <ietf@ietf.org>; Wed, 12 Apr 2000 16:37:04 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id NAA02675;
	Wed, 12 Apr 2000 13:37:02 -0700 (PDT)
Message-ID: <38F4DE4B.19597105@isi.edu>
Date: Wed, 12 Apr 2000 13:36:27 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: ietf@ietf.org
Subject: Re: interception proxies
References: <200004120504.XAA05262@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Vernon Schryver wrote:
> 
> My impression from the two WG documents is that in the WG consensus is
> that HTTP interception proxies are at least tolerable and often necessary
> and good, and by extension probably also for SMTP and everything else.

The arch document defines, it doesn't condone or condemn.

As to the known-probs doc, that focuses on problems of the sort that
TCPIMPL did - errors in the implementation, not deliberately changing
specs. 

> Yes, I noticed that "W" in "WREC" doesn't stand for "mail".  It's also
> clear that intercepting or proxying are at most aspects of the "RE" and
> the "C", although I don't see how that is relevant to whether the WG is
> committed to interception proxies.  

Intercepting is also done in other contexts:

	- DNS
	- email
	- TCP for relay over subnets
		e.g., over wireless or intermittently-connected links

> Yes, I realize that draft wasn't a product of the WREC WG.  The two WREC
> documents cannot be read as deprecating interception proxies and can be
> read as advocating them by what they fail to say.

I do not agree with this statement. Failing to condemn cannot be taken
as an endorsement. It means only that the documents define, rather than
compare or advocate, architectural components.

> ] From: Joe Touch <touch@ISI.EDU>
> 
> ] FWIW, there _was_ discussion in WREC of the hazards of transparent web
> ] caching. I dug up an old e-mail, describing the hazards of transparent
> ] web caching which I summarized at the time, when WREC was forming.
> ]
> ] A copy of the note, admittedly very rough (just an outline, and a very
> ] rough one at that) is at:
> ]
> ]       http://www.isi.edu/touch/pubs/hazards-outline.txt
> 
> I really like "in effect, it is a use of IP spoofing to do replay attacks."
> 
> (Why a 3rd document instead of added to Problems?)

Because problems focuses on errors of implementation, not of
architectural design.
I would advocate that there is the need for a separate statement on
design in this case.

> ] I would be glad to host further discussion on the WREC maillist as to
> ] how to augment the list and flesh it out to a full I-D before the next
> ] IETF, if there is sufficient interest.
> 
> Do you two think that either the IETF or the WREC working group might
> agree with the thrust of that outline?  It sounds as if your answer is
> "yes" and that my sense of WREC, IETF, and maybe industry sentiment is
> wrong.

I'll take that over to WREC, and we can have that discussion there
first.

Joe



From owner-ietf-outbound  Wed Apr 12 17:00:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA03302
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 17:00:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03157
	for <ietf@ietf.org>; Wed, 12 Apr 2000 16:52:03 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id NAA05406;
	Wed, 12 Apr 2000 13:52:03 -0700 (PDT)
Message-ID: <38F4E1D0.20A08E0B@isi.edu>
Date: Wed, 12 Apr 2000 13:51:28 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: ietf@ietf.org, wrec@cs.utk.edu
Subject: Re: interception proxies
References: <200004121433.KAA11030@angels.heaven.net> <14580.47617.154623.427207@saint.heaven.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



"Dick St.Peters" wrote:
> 
> Would you settle for "The IP spec authors didn't have enough foresight
> to foresee a need to rewrite source addresses" ? :)
> 
> Whatever anyone thinks of it, people are doing it.  On the right are
> people saying it is immoral, evil, and dangerous, not to mention
> prohibited by the gods, and they refuse to talk about it.  On the left
> are people doing it, each their own way because there is no standard
> and not even any public discussion.

Intercepting connections and sourcing packets with addresses not owned
by you (or within your stub subnet) violates one of the few standards we
have (STD003 - the combination of RFCs 1122 and 1123).

Intercepting connections by rewriting IP headers in a gateway violates a
proposed staandard (RFC 1812).

It is not immoral, evil or dangerous; there are standards (existing and
proposed), and they are being violated.

Joe



From owner-ietf-outbound  Wed Apr 12 17:10:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA03531
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 17:10:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03500
	for <ietf@ietf.org>; Wed, 12 Apr 2000 17:09:40 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA03839;
        Wed, 12 Apr 2000 17:09:09 -0400 (EDT)
Message-Id: <200004122109.RAA03839@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Joe Touch <touch@ISI.EDU>
cc: Keith Moore <moore@cs.utk.edu>, Vernon Schryver <vjs@calcite.rhyolite.com>,
        ietf@ietf.org
Subject: Re: interception proxies 
In-reply-to: Your message of "Wed, 12 Apr 2000 13:24:42 PDT."
             <38F4DB8A.8F35DC70@isi.edu> 
Date: Wed, 12 Apr 2000 17:09:09 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> > where did the wrec folks get the idea that the IP specification was 
> > obsolete?
> 
> (speaking not for the entire WREC, but my impression of the meetings) I
> did get the impression (mistakenly or not) that addressing the whole of
> the IP spec was not particularly in scope (e.g., from our area director,
> who discussed scope at nearly every meeting).

I would agree on that point ... but as long as wrec recognizes (correctly)
that revising IP is not within its purview then it also seems reasonable 
for wrec to assume that things that violate IP are of dubious value.

Keith



From owner-ietf-outbound  Wed Apr 12 17:20:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA03714
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 17:20:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03604
	for <ietf@ietf.org>; Wed, 12 Apr 2000 17:12:48 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA03933;
        Wed, 12 Apr 2000 17:12:14 -0400 (EDT)
Message-Id: <200004122112.RAA03933@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Joe Touch <touch@ISI.EDU>
cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: interception proxies 
In-reply-to: Your message of "Wed, 12 Apr 2000 13:36:27 PDT."
             <38F4DE4B.19597105@isi.edu> 
Date: Wed, 12 Apr 2000 17:12:14 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> As to the known-probs doc, that focuses on problems of the sort that
> TCPIMPL did - errors in the implementation, not deliberately changing
> specs. 

yes, but given that there are no specs for interception proxies,
how do you judge what is and is not an error in the implementation?
or given that all interception proxies violate the IP specifications,
isn't an interception proxy by its very nature an implementation error?

Keith



From owner-ietf-outbound  Wed Apr 12 17:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA03860
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 17:30:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03760
	for <ietf@ietf.org>; Wed, 12 Apr 2000 17:23:31 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id XAA00411
	for <ietf@ietf.org>; Wed, 12 Apr 2000 23:23:32 +0200
Message-Id: <4.3.1.2.20000412231309.0238b008@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 12 Apr 2000 23:21:18 +0200
To: <ietf@ietf.org>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Source address (offtopic)
In-Reply-To: <14580.47617.154623.427207@saint.heaven.net>
References: <200004121433.KAA11030@angels.heaven.net>
 <200004121433.KAA11030@angels.heaven.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 14:01 12.04.2000 -0400, Dick St.Peters wrote:
>Would you settle for "The IP spec authors didn't have enough foresight
>to foresee a need to rewrite source addresses" ? :)
My standard architectural wish-it-could-be-changed:

The source address of a datagram was an architectural mistake, and should 
never have been in the mandatory packet format.

                   Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Wed Apr 12 18:10:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA04417
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 18:10:02 -0400 (EDT)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04376
	for <ietf@ietf.org>; Wed, 12 Apr 2000 18:07:55 -0400 (EDT)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id RAA07804;
	Wed, 12 Apr 2000 17:07:50 -0500 (CDT)
Message-Id: <200004122207.RAA07804@gungnir.fnal.gov>
To: Harald Tveit Alvestrand <Harald@alvestrand.no>
Cc: ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: Source address (offtopic) 
In-reply-to: Your message of Wed, 12 Apr 2000 23:21:18 +0200.
             <4.3.1.2.20000412231309.0238b008@dokka.kvatro.no> 
Date: Wed, 12 Apr 2000 17:07:50 -0500
Sender: crawdad@gungnir.fnal.gov
X-Loop: ietf@ietf.org

> The source address of a datagram was an architectural mistake, and should 
> never have been in the mandatory packet format.

Nahh, the mistake was ignoring the source address when routing & forwarding.



From owner-ietf-outbound  Wed Apr 12 18:20:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA04526
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 18:20:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04394
	for <ietf@ietf.org>; Wed, 12 Apr 2000 18:08:55 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA17747;
	Wed, 12 Apr 2000 15:08:53 -0700 (PDT)
Message-ID: <38F4F3D2.9CD70AB4@isi.edu>
Date: Wed, 12 Apr 2000 15:08:18 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: interception proxies
References: <200004122112.RAA03933@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Keith Moore wrote:
> 
> > As to the known-probs doc, that focuses on problems of the sort that
> > TCPIMPL did - errors in the implementation, not deliberately changing
> > specs.
> 
> yes, but given that there are no specs for interception proxies,
> how do you judge what is and is not an error in the implementation?
> or given that all interception proxies violate the IP specifications,
> isn't an interception proxy by its very nature an implementation error?

This is related to TCPIMPL - new modifications to TCP are not considered
in the known-problems doc. Even if there are problems in the design of
the modification.

Joe



From owner-ietf-outbound  Wed Apr 12 20:10:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA05572
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 20:10:02 -0400 (EDT)
Received: from web1406.mail.yahoo.com (web1406.mail.yahoo.com [128.11.23.170])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA05516
	for <ietf@ietf.org>; Wed, 12 Apr 2000 20:02:29 -0400 (EDT)
Received: (qmail 18258 invoked by uid 60001); 13 Apr 2000 00:02:28 -0000
Message-ID: <20000413000228.18257.qmail@web1406.mail.yahoo.com>
Received: from [38.186.47.9] by web1406.mail.yahoo.com; Wed, 12 Apr 2000 17:02:28 PDT
Date: Wed, 12 Apr 2000 17:02:28 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: Re: breaking the IP model (or not) 
To: Keith Moore <moore@cs.utk.edu>, Scott Brim <ncc1701v@yahoo.com>
Cc: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org



--- Keith Moore <moore@cs.utk.edu> wrote:
> > I'm being a bit extreme but the point is that just because something is 
> > architecturally bad doesn't mean you shouldn't do it, since these days it 
> > takes us years to make any architectural enhancements.
> 
> perhaps architectural impurity alone shouldn't keep you from doing 
> something, but the fact that something violates fundamental design 
> assumptions should cause you to do some analysis and hard thinking
> about the likely consequences of using them.  and if you are in the
> business of selling boxes that violate the design assumptions you 
> shouldn't misrepresent these to your customers.
> 
> most of these hacks can be employed in ways that are mostly harmless,
> but knowing when they are harmless and when they will cause harm
> can be quite difficult.  NATs seemed mostly harmless when they were 
> first deployed; now they're a huge problem.
                                ^^^^^^^^^^^^

Hmm... Depends on one's perspective. Do not underestimate the
timeliness of a solution. Timeliness is operational reality.

It could have been catastrphic had we not had a timely solution 
with no addresses to issue. NAT is the reason we have had this much
time to work on IPng.
 
> 
> Keith
> 
> 

regards,
suresh

=====


__________________________________________________
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com



From owner-ietf-outbound  Wed Apr 12 22:10:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA07695
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 22:10:02 -0400 (EDT)
Received: from tipgwy.erv.ericsson.net (tipgwy.erv.ericsson.se [194.17.213.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07610
	for <ietf@ietf.org>; Wed, 12 Apr 2000 22:02:25 -0400 (EDT)
From: RAMAIL-ADM@im.erv.ericsson.se
Received: (from smap@localhost)
	by tipgwy.erv.ericsson.net (8.8.8+Sun/8.8.8) id EAA01203
	for <ietf@ietf.org>; Thu, 13 Apr 2000 04:01:53 +0200 (MET DST)
Received: from <RAMAIL-ADM@im.erv.ericsson.se> (voyager.im.erv.ericsson.se [192.168.16.10]) by tipgwy via smap (V2.0)
	id xma001051; Thu, 13 Apr 00 04:00:57 +0200
Received: (root@localhost) by voyager.im.erv.ericsson.se (8.8.8/SCA-6.6) 
	id CAA02322; Thu, 13 Apr 2000 02:00:17 GMT
Date: Thu, 13 Apr 2000 02:00:17 GMT
Message-Id: <200004130200.CAA02322@voyager.im.erv.ericsson.se>
To: ietf@ietf.org
Subject: Mail to ervjb Returned
X-Loop: ietf@ietf.org


The following message is being returned unread.

The message is addressed properly but the addressee
has not accessed their mailbox for at least 4 days

******
******  Message To: ervjb@im.erv.ericsson.se (Joakim Bergstrom)
******
******  Unread Message Follows:
******

From: Doug.Royer@Software.com
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Date: Sat, 9 Apr 2000 12:10:53 -0700
Reply-To: ietf@ietf.org
Sender: droyer@ietf.org
Message-ID: <38EF843D.F1E4C791@Software.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-20 i686)
To: ietf@ietf.org
CC: iesg@ietf.org, rfc-ed@rfc-editor.org

Peter Deutsch in Mountain View wrote:
>
[in part you said]

> I still object to your notion that it's not censorship since people can
> always go elsewhere. Where does this lead? I see the day when people
> can't publish a new  directory service protocol because "The IETF has
> endorsed LDAP for directory services", or would ban the publication of
> an extension to DNS because "it must prevent the misuse of the protocol
> in creating inappropriate services". One by one, you'd be chasing
> innovation to other foums.
> 
> "Danger, Will Robinson! Danger!"

The above information is nonsense.

You seem to be objecting to Keith's right to object to the draft
as it is written. So using your logic (As I understand what you
are saying above) - you are also guilty of censorship by not
wanting Keith to object.

I understand you frustration as many of us in the IETF have
been frustrated from time to time. If you want to convince
me and others then please ignore anything you feel is a non-technical
issue. And address the technical issues.

Many in the IETF *are* swayed by technical content.

I am undecided on this issue and I am personally glad to see this
debate. I do find it an important discussion when it remains
technical. 

Questions I have:

Does this solve a problem that is not already solved by another method?
Not that it has to be unique as you point out above, but if you could
compare it against other known solutions (if any) then perhaps its
advantages (that I have not seen yet) could help you cause?

TRUNCATED BY ERV_IMS.



From owner-ietf-outbound  Wed Apr 12 22:20:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA07819
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 22:20:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07779
	for <ietf@ietf.org>; Wed, 12 Apr 2000 22:17:50 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id WAA04677;
        Wed, 12 Apr 2000 22:17:24 -0400 (EDT)
Message-Id: <200004130217.WAA04677@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Pyda Srisuresh <srisuresh@yahoo.com>
cc: Keith Moore <moore@cs.utk.edu>, Scott Brim <ncc1701v@yahoo.com>,
        ietf@ietf.org
Subject: Re: breaking the IP model (or not) 
In-reply-to: Your message of "Wed, 12 Apr 2000 17:02:28 PDT."
             <20000413000228.18257.qmail@web1406.mail.yahoo.com> 
Date: Wed, 12 Apr 2000 22:17:24 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Hmm... Depends on one's perspective. Do not underestimate the
> timeliness of a solution. Timeliness is operational reality.

I'm very much aware of this.  timelinesss is what gives you
(or denies you) the opportunity to deploy a new technology.
but just because something is timely (in the sense that
there is an opportunity to deploy it) does not mean that 
deploying it leaves the world in a better place.
 
> It could have been catastrphic had we not had a timely solution 
> with no addresses to issue. NAT is the reason we have had this much
> time to work on IPng.

it's not at all clear whether NAT provided additional time for
IPng development or whether such time was really needed.  IPv6 was 
largely developed before NAT enjoyed significant deployment, and 
arguably NAT has delayed adoption of IPv6.  and because of the NAT 
deployment it is now somewhat "untimely" to deploy applications like 
IP telephony.  whereas if IPv6 had been adopted a bit earlier 
(because NAT had not filled the vacuum, so to speak) IP telephony 
would work just fine with it.

of course, IPv6 might have moved along slowly even without NAT.
but it would probably have moved faster had NATs not existed.

best thing I can say about NAT is that it motivated me to work on 6to4.

Keith



From owner-ietf-outbound  Wed Apr 12 23:10:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA09352
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 23:10:02 -0400 (EDT)
Received: from smtp.mail.yahoo.com (smtp.mail.yahoo.com [128.11.68.32])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA09286
	for <ietf@ietf.org>; Wed, 12 Apr 2000 23:02:53 -0400 (EDT)
Received: from cci-209150224065.clarityconnect.net (HELO KHERMANN-NT2.yahoo.com) (209.150.224.65)
  by smtp.mail.yahoo.com with SMTP; 12 Apr 2000 20:02:29 -0700
X-Apparently-From: <ncc1701v@yahoo.com>
Message-Id: <4.3.1.2.20000412225557.00b0e300@pop.mail.yahoo.com>
X-Sender: ncc1701v@pop.mail.yahoo.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 12 Apr 2000 23:02:17 -0400
To: Keith Moore <moore@cs.utk.edu>
From: Scott Brim <ncc1701v@yahoo.com>
Subject: Re: breaking the IP model (or not) 
Cc: ietf@ietf.org
In-Reply-To: <200004121727.NAA02386@astro.cs.utk.edu>
References: <Your message of "Wed, 12 Apr 2000 12:13:06 EDT." <4.3.1.2.20000412120700.00b0adb0@pop.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 01:27 PM 4/12/00 -0400, Keith Moore wrote:
> > I'm being a bit extreme but the point is that just because something is
> > architecturally bad doesn't mean you shouldn't do it, since these 
> days it
> > takes us years to make any architectural enhancements.
>
>perhaps architectural impurity alone shouldn't keep you from doing
>something, but the fact that something violates fundamental design
>assumptions should cause you to do some analysis and hard thinking
>about the likely consequences of using them.

Yes.  So why don't we have a new design which decouples all the meanings 
for an IP "address"?

>and if you are in the
>business of selling boxes that violate the design assumptions you
>shouldn't misrepresent these to your customers.

Sounds like we have some agreement on the list.

>most of these hacks can be employed in ways that are mostly harmless,
>but knowing when they are harmless and when they will cause harm
>can be quite difficult.

There is precedent for the IESG getting draft authors to include caveats 
and limitations.

>NATs seemed mostly harmless when they were
>first deployed; now they're a huge problem.

Just wait until mobile IP-based "phones" take off!

...Scott


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com



From owner-ietf-outbound  Wed Apr 12 23:40:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA09989
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 23:40:03 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09919
	for <ietf@ietf.org>; Wed, 12 Apr 2000 23:32:08 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 12faMU-000Lhe-00
	for ietf@ietf.org; Wed, 12 Apr 2000 20:32:10 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: ietf <ietf@ietf.org>
Subject: eating our own dogfood
Message-Id: <E12faMU-000Lhe-00@rip.psg.com>
Date: Wed, 12 Apr 2000 20:32:10 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

rip.psg.com:/usr/home/randy/mp3/neil_young> nslookup ietf.org.
Server:  cache.psg.com
Address:  147.28.0.3

*** No address (A) records available for ietf.org.

rip.psg.com:/usr/home/randy/mp3/neil_young> ns ietf.org.
Default Server:  cache.psg.com
Address:  147.28.0.3

Server:  cache.psg.com
Address:  147.28.0.3

Non-authoritative answer:
ietf.org        nameserver = ns.ietf.org
ietf.org        nameserver = ns.CNRI.Reston.VA.US

Authoritative answers can be found from:
ns.ietf.org     internet address = 132.151.1.19
ns.CNRI.Reston.VA.US    internet address = 132.151.1.1



rfc2182 ignored, both servers on same backbone, probably in same site.

dns hosed, ietf.org was an A RR just a few hours ago.

randy



From owner-ietf-outbound  Wed Apr 12 23:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA10226
	for ietf-outbound.10@ietf.org; Wed, 12 Apr 2000 23:50:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10168
	for <ietf@ietf.org>; Wed, 12 Apr 2000 23:48:26 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id VAA26478
	for ietf@ietf.org  env-from <vjs>;
	Wed, 12 Apr 2000 21:48:28 -0600 (MDT)
Date: Wed, 12 Apr 2000 21:48:28 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004130348.VAA26478@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: interception proxies
X-Loop: ietf@ietf.org

] From: "Dick St.Peters" <stpeters@NetHeaven.com>

] ...
] Actually, I've always thought that the first recorded-route address
] was the original source address so the route would indeed be
] reversible, but I'll admit to never having actually seen a recorded
] route. ...

Try `ping -R` between reasonable UNIX boxes on a private network,
and either use something like dbx or gdb to look at the bits that
`ping` gets or use tcpdump or similar to see the bits on the wire.


  ........

> From: Salvador Vidal <svidal@lander.es>

> ...
> >> There are also good uses for interception, I think that ONGs, churchs, and
> >> other organizations and people will want to become Internet trusters soon,

> ...
> I'm not talking about the computers inside a organization, but people
> computers anywhere that trust in these organizations or persons to do
> censor, ranking to do their purchases decisions or whatever they want!, and
> probabily some people want to have more than one truster and balance them.

> ...
> So please, which will be the right tool for a truster service?

Please read the two WREC drafts to discover the technical meaning
of "interception proxy."  Interception proxies are useless in the
circumstances you care about.  An interception proxy can affect
only traffic directed to it by a router in the path between IP
peers (e.g. HTTP client and server).  Your "computers anywhere"
won't be using the very few routers that would intercept traffic
for your trustors and send it to your trustees.
I'm reminded of statements during the wiretapping dicussions that
imagined the Internet as a big phone system using a single CO in a room
somewhere in the The Netherlands.  That seems to be like the problem here.

An explicit proxy is the right tool for part of your goal.  Simply build
proxies that filters according to your taste, and then configure the HTTP
browsers of trusting people to use your proxies.  That solution has a
characteristic that is either a fatal flaw or an enormous virtue, depending
on your philosphy.  It is that using or ignoring your proxy would be the
choice of the people in charge of the client computers instead of those
in charge of the proxies.

For the rest of your goal, the parts that involve balancing evaluations
and choosing whom to trust, interception proxies are tools for the opposite
notions.  They are tools for authoritarian censoring, and that is
intrinsically opposed to people making their choices in trust, ranking,
balancing and so forth.  I also think you need to give up the idea of
having computers make value judgements, but maybe that's just my lack of
imagination.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu Apr 13 00:00:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA10347
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 00:00:05 -0400 (EDT)
Received: from goose.prod.itd.earthlink.net (goose.prod.itd.earthlink.net [207.217.120.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10267
	for <ietf@ietf.org>; Wed, 12 Apr 2000 23:54:30 -0400 (EDT)
Received: from earthlink.net (pool0399.cvx19-bradley.dialup.earthlink.net [209.179.245.144])
	by goose.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id UAA19044;
	Wed, 12 Apr 2000 20:54:20 -0700 (PDT)
Message-ID: <38F47231.73FE9AD5@earthlink.net>
Date: Wed, 12 Apr 2000 08:55:13 -0400
From: Peter Deutsch <peterd@earthlink.net>
X-Sender: "Peter Deutsch" <vlopqxyh@pop.videotron.ca> (Unverified)
X-Mailer: Mozilla 4.08 [en]C-NECCK  (Win95; I)
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: breaking the IP model (or not)
References: <200004130217.WAA04677@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

g'day,

Keith Moore wrote:
> 
> > Hmm... Depends on one's perspective. Do not underestimate the
> > timeliness of a solution. Timeliness is operational reality.
> 
> I'm very much aware of this.  timelinesss is what gives you
> (or denies you) the opportunity to deploy a new technology.
> but just because something is timely (in the sense that
> there is an opportunity to deploy it) does not mean that
> deploying it leaves the world in a better place.

I'm reminded of that scene in "Butch Cassiddy and the Sundance Kid"
where Paul Newman and Robert Redford have been cornered at the top of
the cliff by the pursuing posse ("who *are* thoe guys?") There is no way
out except the 100 foot drop into the raging river below. Newman is
trying to encourage Redford to jump, with the idea that they can then
swim to safety. Redford just keeps saying no, finally confessing that he
can't swim and is afraid of drowning. Newman laughs, and points out that
he should stop worrying, as the fall will probably kill him.

The relevance, for those who miss my obscure references, is that we were
faced with a 100 foot fall into a river, and we made the jump to NATs
and address translation. Sure, it was a horrible thing to do, but we're
still alive and dog paddling to the next crisis, which may well be the
horrors you can forsee awaiting in the raging rapids of IP address
renaming.

This is, believe it or not, progress. Sure, in the ideal world we'd have
found a row boat when we got here, or even stairs down the ciff, but
where we are now is still better than the alternatives we wee facing
before. And this may not be the engineering you want to see us do, but
to quoe the old farmer, "if we wanted to be there, we wouldn't be
starting from here"...

Keith, give it up, you're beating a dead horse. Accept that you're not
going to get perfection in the real world, nor convince those of us who
live the real world that perfection tomorrow is preferable to working
today. I would *love* to see you document the known problems with
paddling in this direction, but please stop trying to pretend the
horrors of this violation of the IP model means we must ban its use. 
Given your choice, we'd still be up at the top of the cliff, with a
noose around our necks...

					- peterd


> 
> > It could have been catastrphic had we not had a timely solution
> > with no addresses to issue. NAT is the reason we have had this much
> > time to work on IPng.
> 
> it's not at all clear whether NAT provided additional time for
> IPng development or whether such time was really needed.  IPv6 was
> largely developed before NAT enjoyed significant deployment, and
> arguably NAT has delayed adoption of IPv6.  and because of the NAT
> deployment it is now somewhat "untimely" to deploy applications like
> IP telephony.  whereas if IPv6 had been adopted a bit earlier
> (because NAT had not filled the vacuum, so to speak) IP telephony
> would work just fine with it.
> 
> of course, IPv6 might have moved along slowly even without NAT.
> but it would probably have moved faster had NATs not existed.
> 
> best thing I can say about NAT is that it motivated me to work on 6to4.
> 
> Keith

-- 
--------------------------------------------------------------------------------
Peter Deutsch                               work email: 
pdeutsch@cisco.com
Technical Leader
Content Services Business Unit                 private:
pdeutsch@earthlink.net
Cisco Systems                                     or  : peterd@the.web

             Alcohol and calculus don't mix. Never drink and derive.
--------------------------------------------------------------------------------



From owner-ietf-outbound  Thu Apr 13 00:10:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA10535
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 00:10:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10282
	for <ietf@ietf.org>; Wed, 12 Apr 2000 23:55:27 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3D3tHB22654;
	Wed, 12 Apr 2000 23:55:17 -0400
Message-Id: <200004130355.e3D3tHB22654@black-ice.cc.vt.edu>
To: Pyda Srisuresh <srisuresh@yahoo.com>
cc: ietf@ietf.org
Subject: Re: breaking the IP model (or not) 
In-reply-to: Your message of "Wed, 12 Apr 2000 17:02:28 PDT."
             <20000413000228.18257.qmail@web1406.mail.yahoo.com> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <20000413000228.18257.qmail@web1406.mail.yahoo.com>
Date: Wed, 12 Apr 2000 23:55:16 -0400
X-Loop: ietf@ietf.org

On Wed, 12 Apr 2000 17:02:28 PDT, Pyda Srisuresh said:
> --- Keith Moore <moore@cs.utk.edu> wrote:
> > can be quite difficult.  NATs seemed mostly harmless when they were 
> > first deployed; now they're a huge problem.
> Hmm... Depends on one's perspective. Do not underestimate the
> timeliness of a solution. Timeliness is operational reality.

I think Keith meant "huge problem" in the same sense that a kidney
dialysis machine is a huge problem.  They keep the patient alive,
but never in the greatest of health or comfort.

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Thu Apr 13 00:20:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA10664
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 00:20:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10455
	for <ietf@ietf.org>; Thu, 13 Apr 2000 00:04:33 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3D44EB31796;
	Thu, 13 Apr 2000 00:04:14 -0400
Message-Id: <200004130404.e3D44EB31796@black-ice.cc.vt.edu>
To: Matt Crawford <crawdad@fnal.gov>
cc: Harald Tveit Alvestrand <Harald@alvestrand.no>, ietf@ietf.org,
        valdis@black-ice.cc.vt.edu
Subject: Re: Source address (offtopic) 
In-reply-to: Your message of "Wed, 12 Apr 2000 17:07:50 CDT."
             <200004122207.RAA07804@gungnir.fnal.gov> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200004122207.RAA07804@gungnir.fnal.gov>
Date: Thu, 13 Apr 2000 00:04:14 -0400
X-Loop: ietf@ietf.org

On Wed, 12 Apr 2000 23:21:18 +0200, Harald Tveit Alvestrand said:
> > The source address of a datagram was an architectural mistake, and should 
> > never have been in the mandatory packet format.
OK, I'll bite - either I'm missing something, or it's 11 days past the
traditional time for such statements.  If the source address wasn't
in the mandatory packet, what would we use for the 4-tuple identifying
a connection?

On Wed, 12 Apr 2000 17:07:50 CDT, Matt Crawford said:
> Nahh, the mistake was ignoring the source address when routing & forwarding.
I may be dense, but I don't remember seeing an absolute prohibition
against checking the source address.  Otherwise, RFC2267 on Network
Ingress Filtering would be in violation all over the place....

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Thu Apr 13 00:30:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA10836
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 00:30:03 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10696
	for <ietf@ietf.org>; Thu, 13 Apr 2000 00:21:24 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3D4LAB25632;
	Thu, 13 Apr 2000 00:21:10 -0400
Message-Id: <200004130421.e3D4LAB25632@black-ice.cc.vt.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: interception proxies 
In-reply-to: Your message of "Wed, 12 Apr 2000 21:48:28 MDT."
             <200004130348.VAA26478@calcite.rhyolite.com> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200004130348.VAA26478@calcite.rhyolite.com>
Date: Thu, 13 Apr 2000 00:21:10 -0400
X-Loop: ietf@ietf.org

On Wed, 12 Apr 2000 21:48:28 MDT, Vernon Schryver <vjs@calcite.rhyolite.com>  said:
> circumstances you care about.  An interception proxy can affect
> only traffic directed to it by a router in the path between IP
> peers (e.g. HTTP client and server).  Your "computers anywhere"
> won't be using the very few routers that would intercept traffic
> for your trustors and send it to your trustees.

Well.. as long as you are very careful to define "computers anywhere"
to specifically not be co-located at MAE-East or other similar
peering location where they'd be on a whoe LOT of paths between IP peers.

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Thu Apr 13 02:10:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA23145
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 02:10:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21130
	for <ietf@ietf.org>; Thu, 13 Apr 2000 02:03:17 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id IAA04751;
	Thu, 13 Apr 2000 08:03:10 +0200
Message-Id: <4.3.1.2.20000413073724.04187ec8@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Thu, 13 Apr 2000 07:57:00 +0200
To: Valdis.Kletnieks@vt.edu, Matt Crawford <crawdad@fnal.gov>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: Source address (offtopic) 
Cc: ietf@ietf.org, valdis@black-ice.cc.vt.edu
In-Reply-To: <200004130404.e3D44EB31796@black-ice.cc.vt.edu>
References: <Your message of "Wed, 12 Apr 2000 17:07:50 CDT." <200004122207.RAA07804@gungnir.fnal.gov>
 <200004122207.RAA07804@gungnir.fnal.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 00:04 13.04.2000 -0400, Valdis.Kletnieks@vt.edu wrote:
>On Wed, 12 Apr 2000 23:21:18 +0200, Harald Tveit Alvestrand said:
> > > The source address of a datagram was an architectural mistake, and 
> should
> > > never have been in the mandatory packet format.
>OK, I'll bite - either I'm missing something, or it's 11 days past the
>traditional time for such statements.  If the source address wasn't
>in the mandatory packet, what would we use for the 4-tuple identifying
>a connection?

ok :-)

that statement illustrates the reason I think so.
The source address fulfils about 4 purposes:

- the address to which a response should be sent.
   For connection oriented stuff, this is part of connection establishment.
   For connectionless stuff, it needs to be only in an initial fragment.
   In one-way transport ("broadcast") it's not needed.
   In transports with feedback on a different channel (RTP/RTSP), it's
   simply the wrong address for this purpose.
   In all cases, it's an application layer thing, thus placing it at the
   network level is a layering violation.

- the address to which network layer error reports (ICMP) should be sent.
   This is not clearly the same as the above one.

- the address of the entity which authorizes the transmission of the message
   (as in "ingress filtering").
   Being unprotected and guessable means that it's not a particularly well
   suited identifier for this. DDOS attacks and SYN spoofs, anyone?

- a simple debugging aid for making trace logs easier to read.
   This is worth 4% of our network traffic volume??????
   (based on 100-byte average packet size, that's what 4 bytes amounts to)

I don't want to change it (as if I could!), my purpose was to point out 
that our current network is the sum of our mistakes, not the network 
equivalent of the Mount Sinai tablets.

                    Harald







--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Thu Apr 13 03:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA24058
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 03:50:02 -0400 (EDT)
Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24034
	for <ietf@ietf.org>; Thu, 13 Apr 2000 03:49:07 -0400 (EDT)
Received: from nma.com (adsl-63-204-17-82.dsl.snfc21.pacbell.net)
 by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with ESMTP id <0FSY000212P0XS@mta5.snfc21.pbi.net> for ietf@ietf.org; Thu,
 13 Apr 2000 00:41:24 -0700 (PDT)
Date: Thu, 13 Apr 2000 00:41:21 -0700
From: Ed Gerck <egerck@nma.com>
Subject: Newsletter on Internet voting, privacy and security issues
To: ietf@ietf.org
Message-id: <38F57A21.FDEE0D7A@nma.com>
MIME-version: 1.0
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


List:

I would like to extend an invitation to the IETF list to read "The 
Bell" -- the first newsletter entirely dedicated to Internet voting and 
collaborative decision-making in Internet protocols (including the use 
of digital certificates and the resulting security/privacy concerns from
potentially non-anonymous voting). Electronic and hard copy subscriptions 
are available at www.thebell.net

Safevote [1] is sponsoring the newsletter as an open forum.  Regarding 
the name "The Bell", the idea was to use the image of a bell because 
mission bells were used in colonial California for telling time, 
announcing events, and for passing on news from one city to another. 
This newsletter intends to serve similar purposes and is also a public 
service open and free for all who may want it.

With monthly 16-page issues, the "The Bell" will focus on privacy, 
security and technology used in Internet voting. 

In Internet tradition, the newsletter is available free over the 
Internet (PDF format), or at an annual cost of $30 for first class 
mail delivery in hard copy.   The first issue contains an extensive 
marketing study of the year 2000 U.S. public elections market - a 
study that will be serialized in upcoming issues.  It also includes 
an article on today's public voting systems used in the United States 
by election expert Roy G. Saltman and an essay by myself outlining the
need for a strong separation between identification and authentication
in order to ensure fair Internet voting protocols.

Internet voting and its potential impact on society will increasingly
call upon us to understand and keep abreast of the latest developments 
in various fields of work. As a developer in this market, I see a 
widening gap between the 100-year-old voting technologies in use today 
and what Internet voting protocols need to take into account. The Bell is 
dedicated to help fill this gap -- perhaps with your help as well.

Cheers,

Ed Gerck

[1] Safevote (www.safevote.com) is a founding member of the Internet 
Voting Technology Alliance (www.ivta.org) and develops OEM (Original 
Equipment Manufacturer) systems for Internet voting, polling, public 
elections, bidding, consensus assessment and other Internet decision-
making applications. The Bell is edited at Safevote. The May 2000 issue 
is now available at the "The Bell" Web site, www.thebell.net



From owner-ietf-outbound  Thu Apr 13 04:30:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA24631
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 04:30:02 -0400 (EDT)
Received: from horowitz.ne.mediaone.net (horowitz.ne.mediaone.net [24.147.233.208])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24553
	for <ietf@ietf.org>; Thu, 13 Apr 2000 04:20:38 -0400 (EDT)
Received: (from marc@localhost)
	by horowitz.ne.mediaone.net (8.8.8/8.8.8) id EAA12068;
	Thu, 13 Apr 2000 04:20:37 -0400 (EDT)
From: Marc Horowitz <marc@mit.edu>
To: Vijay Gill <wrath@cs.umbc.edu>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
        Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: interception proxies
References: <Pine.SOL.3.95.1000411235335.6281P-100000@mailserver-ng.cs.umbc.edu>
Date: 13 Apr 2000 04:20:36 -0400
In-Reply-To: Vijay Gill's message of "Wed, 12 Apr 2000 00:03:08 -0400 (EDT)"
Message-ID: <t537le2l8dn.fsf@horowitz.ne.mediaone.net>
Lines: 39
X-Mailer: Gnus v5.5/Emacs 20.3
X-Loop: ietf@ietf.org

Vijay Gill <wrath@cs.umbc.edu> writes:

>> Any specific ISP's that one could care to name?  Coming from an ISP, what
>> I've seen in general is that most routers have just enough cycles in the
>> forwarding path to keep up with the offered traffic, much less sit around
>> watching for SYN's in flight so as to mutate the MSS values.  In fact, I'd
>> think this would be more of an end system issue rather than a "core" or a
>> "backbone" issue, where the end system is the box prior to the ISP handoff
>> and not quite under the ISP's control and not the end system as in the
>> end2end tcp/ip sense of the word.

As the person who mentioned this to Ted in the first place, it's
BellAtlantic InfoSpeed DSL:

04:07:18.626618 ppp0 > badsl.1886 > home.finger: S 3981264130:3981264130(0) win 31944 <mss 1452,sackOK,timestamp 57597532 0,nop,wscale 0> (DF)
04:07:18.720702 ppp0 < home.finger > badsl.1886: S 295466136:295466136(0) ack 3981264131 win 16384 <mss 1412,nop,wscale 0,nop,nop,timestamp 7390358 57597532>
04:07:18.720725 ppp0 > badsl.1886 > home.finger: . 1:1(0) ack 1 win 31944 <nop,nop,timestamp 57597542 7390358> (DF)

04:08:17.797647 badsl.1886 > home.79: S 3981264130:3981264130(0) win 31944 <mss 1412,sackOK,timestamp 57597532 0,nop,wscale 0> (DF)
04:08:17.798118 home.79 > badsl.1886: S 295466136:295466136(0) ack 3981264131 win 16384 <mss 1460,nop,wscale 0,nop,nop,timestamp 7390358 57597532>
04:08:17.839552 badsl.1886 > home.79: . ack 1 win 31944 <nop,nop,timestamp 57597542 7390358> (DF)

Of course, it's hard to tell exactly where this is happening.  I
suspect either the DSL modem or the DSLAM.

I've considered bringing up IPsec using AH on the two endpoints, but
I'm sure that will involve far more pain dealing with incompetent
technical "support" droids than I have time to deal with.

On the other side, I can name over a dozen major web sites which
create a black hole by setting DF on outgoing TCP segments, but block
ICMP fragmentation required messages going the other way.

If anybody at Cisco is listening (a rhetorical question to be sure), a
great feature for a future version of IOS would be one which causes
TCP to be blocked completely if ICMP fragmentation required packets
are blocked.  At least then the black hole would be easy to spot :-)

		Marc



From owner-ietf-outbound  Thu Apr 13 06:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA25614
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 06:20:04 -0400 (EDT)
Received: from mx01-ext.netapp.com (mx01-ext.netapp.com [198.95.224.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25552
	for <ietf@ietf.org>; Thu, 13 Apr 2000 06:13:37 -0400 (EDT)
Received: (qmail 14490 invoked from network); 13 Apr 2000 10:32:52 -0000
Received: from herra.netapp.com (HELO herra.corp.netapp.com) (198.95.224.184)
  by mx01-ext.netapp.com with SMTP; 13 Apr 2000 10:32:52 -0000
Received: from johnm (jfm-laptop.europe.netapp.com [192.168.10.134])
	by herra.corp.netapp.com (8.9.3/8.9.3/NTAP-1.0) with ESMTP id DAA25793;
	Thu, 13 Apr 2000 03:13:06 -0700 (PDT)
Message-Id: <4.2.0.58.20000413115846.03f11c00@pop.netapp.com>
X-Sender: jmartin@pop.netapp.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 13 Apr 2000 12:07:39 +0200
To: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
From: John Martin <jmartin@netapp.com>
Subject: Re: interception proxies
Cc: wrec@cs.utk.edu
In-Reply-To: <200004112247.QAA29258@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Vernon,

At 04:47 PM 11/04/00 -0600, Vernon Schryver wrote:
>Call me a non-team playing scab, but I refuse to the honor the old guild
>work rule that limits the questions I can consider.  If sourcing
>other-owned etc. or anything else is an architectural or other problem,
>then professional pride ought to force one to raise the issue insetad of
>waiting for the AD, IESG, IAB, or a plenary to redirect things.  But I
>realize that's a minority view, and not just in IETF working groups or
>even the IETF.

When WREC was originally proposed to the IESG, its scope was much 
broader.     Since the area was, at the time, the subject of much 
confusion, our charter was changed by the IESG to begin with a taxonomy and 
a list of known problems with caching and replication as is done today. At 
the time, I disagreed but complied. With hindsight - and given recent 
discussions - I think that their decision was correct. (If for no other 
reason that we now know what to call these "interception proxy" things).

Most of us who started WREC have indeed an interest in caching and 
replication but not necessarily "interceptions proxies". This type of proxy 
is only one way to do caching / replication - and certainly by no means the 
most common. (The most common - by far - are actually standard, 
run-of-the-mill proxies configured explicitly in users' browsers).

Rgds,
John (WREC co-chair)
---------------------------------------------------------------
Network Appliance           Direct / Voicemail: +31 23 567 9615
Kruisweg 799                               Fax: +31 23 567 9699
NL-2132 NG Hoofddorp               Main Office: +31 23 567 9600
---------------------------------------------------------------



From owner-ietf-outbound  Thu Apr 13 06:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA25732
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 06:30:02 -0400 (EDT)
Received: from mx01-ext.netapp.com (mx01-ext.netapp.com [198.95.224.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25558
	for <ietf@ietf.org>; Thu, 13 Apr 2000 06:13:39 -0400 (EDT)
Received: (qmail 8975 invoked from network); 13 Apr 2000 10:32:54 -0000
Received: from herra.netapp.com (HELO herra.corp.netapp.com) (198.95.224.184)
  by mx01-ext.netapp.com with SMTP; 13 Apr 2000 10:32:54 -0000
Received: from johnm (jfm-laptop.europe.netapp.com [192.168.10.134])
	by herra.corp.netapp.com (8.9.3/8.9.3/NTAP-1.0) with ESMTP id DAA25801;
	Thu, 13 Apr 2000 03:13:08 -0700 (PDT)
Message-Id: <4.2.0.58.20000413120755.00c46f00@pop.netapp.com>
X-Sender: jmartin@pop.netapp.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 13 Apr 2000 12:11:10 +0200
To: Keith Moore <moore@cs.utk.edu>, Joe Touch <touch@ISI.EDU>
From: John Martin <jmartin@netapp.com>
Subject: Re: interception proxies 
Cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
In-Reply-To: <200004112359.TAA07437@astro.cs.utk.edu>
References: <Your message of "Tue, 11 Apr 2000 13:03:02 PDT." <38F384F6.B0238438@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Keith,

At 07:59 PM 11/04/00 -0400, Keith Moore wrote:
> > This was a choice - in some larger sense, if sourcing other-owned IP
> > addresses or TCP connections is considered an architectural problem,
> > needs to come down from above, rather than up from WREC.
>
>sounds like a convenient excuse to me...
>where did the wrec folks get the idea that the IP specification was obsolete?

I'm not sure what you are trying to say here but as co-chair of WREC, I can 
tell you that such a concept was never discussed. We stuck pretty rigidly 
to our charter, in fact.

John


---------------------------------------------------------------
Network Appliance           Direct / Voicemail: +31 23 567 9615
Kruisweg 799                               Fax: +31 23 567 9699
NL-2132 NG Hoofddorp               Main Office: +31 23 567 9600
---------------------------------------------------------------



From owner-ietf-outbound  Thu Apr 13 07:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA26891
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 07:30:01 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26756
	for <ietf@ietf.org>; Thu, 13 Apr 2000 07:22:44 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id HAA24458;
        Thu, 13 Apr 2000 07:22:14 -0400 (EDT)
Message-Id: <200004131122.HAA24458@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Peter Deutsch <peterd@earthlink.net>
cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: breaking the IP model (or not) 
In-reply-to: Your message of "Wed, 12 Apr 2000 08:55:13 EDT."
             <38F47231.73FE9AD5@earthlink.net> 
Date: Thu, 13 Apr 2000 07:22:14 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

Peter,

you are missing the point, and your arguments are unpersuasive.

Keith



From owner-ietf-outbound  Thu Apr 13 08:11:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA27927
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 08:10:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27866
	for <ietf@ietf.org>; Thu, 13 Apr 2000 08:07:36 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id IAA24861;
        Thu, 13 Apr 2000 08:07:02 -0400 (EDT)
Message-Id: <200004131207.IAA24861@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Harald Tveit Alvestrand <Harald@Alvestrand.no>
cc: Valdis.Kletnieks@VT.EDU, Matt Crawford <crawdad@fnal.gov>, ietf@ietf.org,
        valdis@black-ice.cc.vt.edu
Subject: Re: Source address (offtopic) 
In-reply-to: Your message of "Thu, 13 Apr 2000 07:57:00 +0200."
             <4.3.1.2.20000413073724.04187ec8@dokka.kvatro.no> 
Date: Thu, 13 Apr 2000 08:07:02 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> I don't want to change it (as if I could!), my purpose was to point out 
> that our current network is the sum of our mistakes, not the network 
> equivalent of the Mount Sinai tablets.

no disagreement there.  but the original mistakes in TCP/IP were more-or-less
designed to work together.  when people start deploying their own mistakes
in an ad hoc fashion, and when multiple mistakes get added concurrently,
not only do they break things that assumed that the only mistakes in the 
network were those originally designed-in, the combined effect of those 
new mistakes is far worse than the effect of any of them taken individually.

Keith

p.s. I will also argue that the complexities of adding a separate 
application-level identifer and doing without the source address,
are such that had this been done in the original TCP/IP design, 
it would have had a much more difficult time getting deployed 
in the first place.



From owner-ietf-outbound  Thu Apr 13 08:30:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA28394
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 08:30:01 -0400 (EDT)
Received: from mx01-ext.netapp.com (mx01-ext.netapp.com [198.95.224.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA28269
	for <ietf@ietf.org>; Thu, 13 Apr 2000 08:23:38 -0400 (EDT)
Received: (qmail 6831 invoked from network); 13 Apr 2000 12:42:54 -0000
Received: from herra.netapp.com (HELO herra.corp.netapp.com) (198.95.224.184)
  by mx01-ext.netapp.com with SMTP; 13 Apr 2000 12:42:54 -0000
Received: from johnm (jfm-laptop.europe.netapp.com [192.168.10.134])
	by herra.corp.netapp.com (8.9.3/8.9.3/NTAP-1.0) with ESMTP id FAA08110;
	Thu, 13 Apr 2000 05:23:05 -0700 (PDT)
Message-Id: <4.2.0.58.20000413140521.00d3bf00@pop.netapp.com>
X-Sender: jmartin@pop.netapp.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 13 Apr 2000 14:20:44 +0200
To: "Eliot Lear" <lear@CISCO.COM>
From: John Martin <jmartin@netapp.com>
Subject: Re: recommendation against publication of
  draft-cerpa-necp-02.txt
Cc: <ietf@ietf.org>
In-Reply-To: <004701bfa410$0e8e44e0$3490130a@cisco.com>
References: <200004061641.MAA15198@astro.cs.utk.edu>
 <4.2.0.58.20000410141804.00c35ab0@pop.netapp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 04:45 PM 11/04/00 -0700, Eliot Lear wrote:
>I wonder if any of the authors has explored the risks of modifying data in
>flight.  How could this be abused by interlopers and evil doers?  If I
>could hack into a router implementing NECP, what damage could I do?  Could
>I start a nasty little JavaScript/Java/Shockwave/... applet in an
>advertisement?
>And who would know it was me?

Do you mean the authors of NECP? If so, then I'm confused because NECP is 
not about "modifying data in flight" - it is about load balancing multiple 
services which sit behind e.g. a single IP address. (i.e. DNS server farms, 
firewalls, proxies). As I have said repeatedly, "interception proxies" is 
only one of these applications and by no means the most widely used.

Are you confusing this with WCCP (which *only* works with "interception 
proxies").

>Quoth John Martin:
> > [...]
> > Let me be absolutely clear, NECP is about communication between server
> > load-balancers (SLB) and the back-end servers they speak to.
>
>Were this so clear in your document my mailbox wouldn't be full of this
>stuff.

The very first sentance says:

    "This document describes "NECP", a lightweight protocol for
    signalling between servers and the network elements that forward
    traffic to them.  It is intended for use in a wide variety of
    server applications, including for origin servers, proxies, and
    interception proxies."

Despite the fact that "interception proxies" are listed last, they are the 
only service people are talking about.

But, you are right in general: if this is how people read the document, 
we  need to fix the document.

>If it looks like a duck and quacks like a duck, but it's not supposed to be
>a duck, the IESG ought to point out that it's a turkey by so indicating at
>the top of the document.  Also, I'd like to understand why you're not going
>experimental, where it would be expected that you'll correct your mistakes.
>Your choice of "informational" seems unfortunate at best and as
>disingenuous marketing at worst.  I can't tell which.

We used "informational" because we saw that this is what was used for 
HTTP/0.9 with which there are parallels: NECP has existed for some time 
already in slightly differing implementations and this is a codification of 
existing practice. There was no magic of deceit intended. If the IESG 
thinks we should instead go for experimental, I'd be more than happy to 
pursue that instead and bring this into WREC. However, development is not 
within the current WREC charter so we are stuck, I think?

>The fact that you mention interception proxies in the introduction has led
>to this flame war.  Having used the words, you've mentioned none of the
>risks associated with such services both from the server side and the
>client side.

OK - we can fix that. It is not the goal of NECP to describe "interception 
proxies" or their deficiencies. There is, however, a working group which 
has a document aimed at exactly that (amongst other things) - WREC.

>John

---------------------------------------------------------------
Network Appliance           Direct / Voicemail: +31 23 567 9615
Kruisweg 799                               Fax: +31 23 567 9699
NL-2132 NG Hoofddorp               Main Office: +31 23 567 9600
---------------------------------------------------------------



From owner-ietf-outbound  Thu Apr 13 08:40:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA28830
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 08:40:02 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA28564
	for <ietf@ietf.org>; Thu, 13 Apr 2000 08:33:58 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.19878-0@bells.cs.ucl.ac.uk>; Thu, 13 Apr 2000 13:33:29 +0100
To: Matt Crawford <crawdad@fnal.gov>
cc: Harald Tveit Alvestrand <Harald@alvestrand.no>, ietf@ietf.org
Subject: Re: Source address (offtopic)
In-reply-to: Your message of "Wed, 12 Apr 2000 17:07:50 CDT." <200004122207.RAA07804@gungnir.fnal.gov>
Date: Thu, 13 Apr 2000 13:33:27 +0100
Message-ID: <12811.955629207@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <200004122207.RAA07804@gungnir.fnal.gov>, Matt Crawford typed:

 >>> The source address of a datagram was an architectural mistake, and should 
 >>> never have been in the mandatory packet format.
 
 >>Nahh, the mistake was ignoring the source address when routing & forwarding.

thats an implementation detail not a design mistake.

there's plenty of fast classifier algorithms and data structures now
for the 5-tuple which reender  this debate academic - in fact, i think
the lack of a idee fixe about flow id, versus src or dst or src+dst
based routing, versus route hint +eid and so on is the _strength_ of
the tcp/.ip model-  the very lack lack of strong noel complains about
 foresight led to diversity and design freedom....

 cheers

   jon



From owner-ietf-outbound  Thu Apr 13 09:20:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA00246
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 09:20:02 -0400 (EDT)
Received: from squid10.clearaccess.net (IDENT:root@[204.214.6.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00128
	for <ietf@ietf.org>; Thu, 13 Apr 2000 09:17:29 -0400 (EDT)
Received: from tech20 ([204.214.6.254])
	by squid10.clearaccess.net (8.9.3/8.9.3) with SMTP id JAA23998;
	Thu, 13 Apr 2000 09:18:58 -0400
From: "Scot Mc Pherson" <smcpherson@clearaccess.net>
To: "'Randy Bush'" <randy@psg.com>, "'ietf'" <ietf@ietf.org>
Subject: RE: eating our own dogfood
Date: Thu, 13 Apr 2000 09:17:10 -0400
Message-ID: <003401bfa54a$94179680$4cc8a8c0@clearaccess.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <E12faMU-000Lhe-00@rip.psg.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hehe

-----Original Message-----
From: Randy Bush [mailto:randy@psg.com]
Sent: Wednesday, April 12, 2000 11:32 PM
To: ietf
Subject: eating our own dogfood


rip.psg.com:/usr/home/randy/mp3/neil_young> nslookup ietf.org.
Server:  cache.psg.com
Address:  147.28.0.3

*** No address (A) records available for ietf.org.

rip.psg.com:/usr/home/randy/mp3/neil_young> ns ietf.org.
Default Server:  cache.psg.com
Address:  147.28.0.3

Server:  cache.psg.com
Address:  147.28.0.3

Non-authoritative answer:
ietf.org        nameserver = ns.ietf.org
ietf.org        nameserver = ns.CNRI.Reston.VA.US

Authoritative answers can be found from:
ns.ietf.org     internet address = 132.151.1.19
ns.CNRI.Reston.VA.US    internet address = 132.151.1.1



rfc2182 ignored, both servers on same backbone, probably in same site.

dns hosed, ietf.org was an A RR just a few hours ago.

randy



From owner-ietf-outbound  Thu Apr 13 12:31:40 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA06422
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 12:30:02 -0400 (EDT)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA06140
	for <ietf@ietf.org>; Thu, 13 Apr 2000 12:22:06 -0400 (EDT)
Received: (qmail 2410 invoked from network); 13 Apr 2000 16:22:07 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 13 Apr 2000 16:22:07 -0000
Received: (qmail 2772 invoked from network); 13 Apr 2000 16:22:06 -0000
Received: from ppp-47-148.lander.es (HELO salva) (195.76.47.148)
  by lince.lander.es with SMTP; 13 Apr 2000 16:22:06 -0000
Message-Id: <3.0.6.32.20000413182839.00814100@lince.lander.es>
X-Sender: svidal@lince.lander.es
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Thu, 13 Apr 2000 18:28:39 +0200
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Salvador Vidal <svidal@lander.es>
Subject: Re: interception proxies
Cc: ietf@ietf.org
In-Reply-To: <200004130348.VAA26478@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA06140
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Hello Vernon,

At 21:48 12/04/00 -0600, you wrote:

>I also think you need to give up the idea of
>having computers make value judgements, but maybe that's just my lack of
>imagination.
>

Sure that computers will improve doing judgements, but don´t lost the main
force on Interenet, there are hundres of millons of human brains here able
to do judgements, and for me, the most important Internet goal is how to
get this incredible power running in an usefull way?

For the information that you see the first time before anybodi else you
only have computers for the jugement, but also the computers jugements can
use the people past jugements i.e. about the information font... 

Some questions about people feedback are:

How to feedback? It is required a way to feedback not only to the owner of
the information but to the comunity, about the information that you see,
it´s  requiered to invistigate what atributes want the people to use to
select the information in each categorie, then to ask the people that see
this information before about any of this atributes when they are getting
this information.

Why to feedback? Most people will never feedback unless they don´t get a
reward for it, feedback must be paid, but I don´t agree to: please reply
this question about this information and you get 1$, because people will
reply anything, feedback must be competitive in a feedback game, in the way
that people that are more usefull to other people with their information
will get the greats rewards.

How to organize the feedback to be usefull? with feedback happens that is
as important the jugement as who did this jugement, that´s why I think
trusters can be a usefull way to organize this knowlege, because the people
that join the same trusters seems to have similar values and so similar
jugements.
...

Not only values also e-comerce need people feedback, with the current
Internet stuff mainly comercial brouchures, people will not able to do good
decisions because everyting is gorgeous, wonderfull,..., to been able to
take decisions people need real information not comercial garbage!, it
doesn´t matter how much inteligence you put on people desktop, If you
remove the garbage it will remain garbage, information that comes from
independent people is not so wonderfull about everything because is real
information usefull to do decions, so to impulse the e-comerce.

So yes, we must improve computers jugement but much more people one!

Salva


>Vernon Schryver    vjs@rhyolite.com
>
>
>



From owner-ietf-outbound  Thu Apr 13 13:50:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09510
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 13:50:02 -0400 (EDT)
Received: from lint.cisco.com (lint.cisco.com [171.68.224.209])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09422
	for <ietf@ietf.org>; Thu, 13 Apr 2000 13:48:49 -0400 (EDT)
Received: from elearhomepc (elear-dsl3.cisco.com [10.19.144.52]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id KAA02302; Thu, 13 Apr 2000 10:47:52 -0700 (PDT)
Message-ID: <000c01bfa570$97eee800$3490130a@cisco.com>
From: "Eliot Lear" <lear@cisco.com>
To: "John Martin" <jmartin@netapp.com>
Cc: <ietf@ietf.org>
References: <200004061641.MAA15198@astro.cs.utk.edu><4.2.0.58.20000410141804.00c35ab0@pop.netapp.com> <4.2.0.58.20000413140521.00d3bf00@pop.netapp.com>
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
Date: Thu, 13 Apr 2000 10:49:18 -0700
Organization: Cisco Systems
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Part of the problem here is that a knife may be used as a food utensil or a
weapon.  Safe handling, however, is always required, and should be
documented.

I would add two other comments.  I tried to locate the RFC for HTTP/0.9,
but the best I could find was a reference to a CERN ftp site for the
protocol.  In any case, by the time HTTP got to the IETF it was deployed
over a vast number of end stations, and comparisons to it are probably not
apt.

Finally, rechartering is precisely what you ought to have done, and should
do, IMHO.





From owner-ietf-outbound  Thu Apr 13 15:10:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA11458
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 15:10:02 -0400 (EDT)
Received: from rmx08.globecomm.net (rmx08.iname.net [165.251.8.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11381
	for <ietf@ietf.org>; Thu, 13 Apr 2000 15:04:47 -0400 (EDT)
Received: from web39.pub01  by rmx08.globecomm.net (8.9.1/8.8.0) with SMTP id PAA23607 ; Thu, 13 Apr 2000 15:04:47 -0400 (EDT)
Message-ID: <383799847.955652687119.JavaMail.root@web39.pub01>
Date: Thu, 13 Apr 2000 15:04:47 -0400 (EDT)
From: du pot <mailmeat@europe.com>
To: ietf@ietf.org
Subject: Request for Information
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: mail.com
X-Originating-IP: 128.235.249.43
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hello,

I am doing my Masters in US.  I have a few ideas for my masters' project.

I request you to comment about these ideas, and help me choosing the best
out of these.

1. Real time video transmission using Java.
2. Internet telephony using Java.
3. Remote network management using Java.
4. Video conferencing.
5. e-business service development.

Thanks for your time,
du.

______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup



From owner-ietf-outbound  Thu Apr 13 16:20:40 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA13149
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 16:20:02 -0400 (EDT)
Received: from warspite.cnchost.com (warspite.concentric.net [207.155.248.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12971
	for <ietf@ietf.org>; Thu, 13 Apr 2000 16:12:52 -0400 (EDT)
Received: from ipcell023 ([208.176.101.190])
	by warspite.cnchost.com
	id QAA22245; Thu, 13 Apr 2000 16:12:43 -0400 (EDT)
	[ConcentricHost SMTP Relay 1.8]
Errors-To: <mehul@ipcell.com>
From: "Mehul Shah" <mehul@ipcell.com>
To: "'du pot'" <mailmeat@europe.com>, <ietf@ietf.org>
Subject: RE: Request for Information
Date: Thu, 13 Apr 2000 15:15:29 -0500
Message-ID: <706A42E526E9D311924C00B0D01AC60B0834F9@mail.itn.ipcell.com>
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 CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <706A42E526E9D311924C00B0D01AC60B30C711@mail.itn.ipcell.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

(2) option is the best of all from my view point but you could use some real
time OS like VxWorks
or Nuclues


> -----Original Message-----
> From: du pot [mailto:mailmeat@europe.com]
> Sent: Thursday, April 13, 2000 2:05 PM
> To: ietf@ietf.org
> Subject: Request for Information
>
>
> Hello,
>
> I am doing my Masters in US.  I have a few ideas for my
> masters' project.
>
> I request you to comment about these ideas, and help me
> choosing the best
> out of these.
>
> 1. Real time video transmission using Java.
> 2. Internet telephony using Java.
> 3. Remote network management using Java.
> 4. Video conferencing.
> 5. e-business service development.
>
> Thanks for your time,
> du.
>
> ______________________________________________
> FREE Personalized Email at Mail.com
> Sign up at http://www.mail.com/?sr=signup
>
>



From owner-ietf-outbound  Thu Apr 13 17:20:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA14253
	for ietf-outbound.10@ietf.org; Thu, 13 Apr 2000 17:20:02 -0400 (EDT)
Received: from mx01-ext.netapp.com (mx01-ext.netapp.com [198.95.224.34])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA14215
	for <ietf@ietf.org>; Thu, 13 Apr 2000 17:17:10 -0400 (EDT)
Received: (qmail 10328 invoked from network); 13 Apr 2000 21:36:37 -0000
Received: from herra.netapp.com (HELO herra.corp.netapp.com) (198.95.224.184)
  by mx01-ext.netapp.com with SMTP; 13 Apr 2000 21:36:37 -0000
Received: from johnm ([192.168.199.31])
	by herra.corp.netapp.com (8.9.3/8.9.3/NTAP-1.0) with ESMTP id OAA28108;
	Thu, 13 Apr 2000 14:16:39 -0700 (PDT)
Message-Id: <4.2.0.58.20000413230531.061fa7a0@pop.netapp.com>
X-Sender: jmartin@pop.netapp.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 13 Apr 2000 23:09:00 +0200
To: "Eliot Lear" <lear@cisco.com>
From: John Martin <jmartin@netapp.com>
Subject: Re: recommendation against publication of
  draft-cerpa-necp-02.txt
Cc: <ietf@ietf.org>
In-Reply-To: <000c01bfa570$97eee800$3490130a@cisco.com>
References: <200004061641.MAA15198@astro.cs.utk.edu>
 <4.2.0.58.20000410141804.00c35ab0@pop.netapp.com>
 <4.2.0.58.20000413140521.00d3bf00@pop.netapp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 10:49 AM 13/04/00 -0700, Eliot Lear wrote:
>Part of the problem here is that a knife may be used as a food utensil or a
>weapon.  Safe handling, however, is always required, and should be
>documented.

Granted.

>I would add two other comments.  I tried to locate the RFC for HTTP/0.9,
>but the best I could find was a reference to a CERN ftp site for the
>protocol.

Ooops. s/0.9/1.0 - rfc1945.

>   In any case, by the time HTTP got to the IETF it was deployed
>over a vast number of end stations, and comparisons to it are probably not
>apt.

NECP is a super-set of various load-balancing technologies already deployed 
at thousands of sites.

>Finally, rechartering is precisely what you ought to have done, and should
>do, IMHO.

For the record: this is exactly what we are doing. (We were waiting for the 
two starter documents to be published or at least start their path via the 
IESG).

Rgds,
John

---------------------------------------------------------------
Network Appliance           Direct / Voicemail: +31 23 567 9615
Kruisweg 799                               Fax: +31 23 567 9699
NL-2132 NG Hoofddorp               Main Office: +31 23 567 9600
---------------------------------------------------------------



From owner-ietf-outbound  Fri Apr 14 00:10:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA21026
	for ietf-outbound.10@ietf.org; Fri, 14 Apr 2000 00:10:02 -0400 (EDT)
Received: from mailserver-ng.cs.umbc.edu (mailserver-ng.cs.umbc.edu [130.85.100.230])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20974
	for <ietf@ietf.org>; Fri, 14 Apr 2000 00:07:53 -0400 (EDT)
Received: from localhost (wrath@localhost)
	by mailserver-ng.cs.umbc.edu (8.9.3/8.9.3) with SMTP id AAA17564;
	Fri, 14 Apr 2000 00:07:52 -0400 (EDT)
Date: Fri, 14 Apr 2000 00:07:52 -0400 (EDT)
From: Vijay Gill <wrath@cs.umbc.edu>
To: Marc Horowitz <marc@mit.edu>
cc: "Theodore Y. Ts'o" <tytso@mit.edu>, ietf@ietf.org
Subject: Re: interception proxies
In-Reply-To: <t537le2l8dn.fsf@horowitz.ne.mediaone.net>
Message-ID: <Pine.SOL.3.95.1000414000609.15405J-100000@mailserver-ng.cs.umbc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On 13 Apr 2000, Marc Horowitz wrote:

> Vijay Gill <wrath@cs.umbc.edu> writes:
> 
> >> think this would be more of an end system issue rather than a "core" or a
> >> "backbone" issue, where the end system is the box prior to the ISP handoff
> >> and not quite under the ISP's control and not the end system as in the
> >> end2end tcp/ip sense of the word.
> 
> As the person who mentioned this to Ted in the first place, it's
> BellAtlantic InfoSpeed DSL:



> Of course, it's hard to tell exactly where this is happening.  I
> suspect either the DSL modem or the DSLAM.

Ah yes.  Perhaps it would be interesting if the vendor(s) name(s) were
published, so that when they come touting the hardware to other providers,
some hard questions may be asked.

/vijay





From owner-ietf-outbound  Fri Apr 14 08:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA06819
	for ietf-outbound.10@ietf.org; Fri, 14 Apr 2000 08:50:02 -0400 (EDT)
Received: from mail2.itu.int (mail2.itu.ch [156.106.192.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06693
	for <ietf@ietf.org>; Fri, 14 Apr 2000 08:42:21 -0400 (EDT)
Received: by mail2.itu.ch with Internet Mail Service (5.5.2650.21)
	id <2GFQ0WGK>; Fri, 14 Apr 2000 14:39:01 +0200
Message-ID: <DA5558CC09AED311ABE10000778D757F4C2C2B@mailsrv.itu.ch>
From: "Shaw, Robert" <Robert.Shaw@itu.int>
To: "'Brian E Carpenter'" <brian@hursley.ibm.com>
Cc: ietf@ietf.org
Subject: RE: rfc-editor?
Date: Fri, 14 Apr 2000 14:41:50 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian@hursley.ibm.com]
>
> Jeff,
> 
> The RFC Editor function is the subject of a contract, paid for and 
> issued by the Internet Society on behalf of the IETF. The IAB, which
> I chaired until 2 weeks ago, by its latest charter "must approve the 
[snip]
> 
> The current contractor is the Information Sciences Institute of the
> University of Southern California, where the late Jon Postel worked.
> 
> There is no individual human acting as RFC Editor; it's a team effort
> at ISI.
> 

Brian,

O.K., help me understand this. ISOC paid ISI a few hundred 
thousand dollars (?) for the RFC-Editor functions (wasn't it really
funding for the entire IANA role?). However, since Joyce Reynolds is 
now listed both as a staff member of ICANN ("Manager of Publications") 
at http://www.icann.org/general/abouticann.htm and "liaison" to 
the RFC editor on the IAB pages at http://www.iab.org/members.html
the ISOC funding seems to have been used/absorbed for ICANN staff?

However, since there is a recent MoU between IETF and ICANN "Concerning 
the Technical Work of the Internet Assigned Numbers Authority" at 
http://www.icann.org/general/ietf-icann-mou-01mar00.htm, I'm puzzled
why the scope of this did not include the RFC-Editor function? If the 
the absence is supposed to indicate some IETF independence from 
ICANN, it's certainly not clear this is reality if the IAB RFC-Editor 
liaison contact is working for ICANN.

The above MoU recognizes that the "IANA technical team is now part 
of ICANN" and that the "IAB is chartered to designate the IANA on 
behalf of the IETF". But isn't this agreement only ad hoc recognition 
of reality since the IAB really doesn't have any ability to 
(re)designate the IANA functions? That's because there's this 
strong rumour going around that the US Department of Commerce 
believes it is transferring the IANA functions to ICANN....

Bob
--
Robert Shaw <robert.shaw@itu.int>
ITU Internet Strategy and Policy Advisor
International Telecommunication Union <http://www.itu.int>
Place des Nations, 1211 Geneva, Switzerland



From owner-ietf-outbound  Fri Apr 14 09:30:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA07364
	for ietf-outbound.10@ietf.org; Fri, 14 Apr 2000 09:30:03 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET (nod.Reston.mci.net [166.45.6.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07303
	for <ietf@ietf.org>; Fri, 14 Apr 2000 09:25:51 -0400 (EDT)
Received: from localhost ([135.207.27.137])
 by shoe.reston.mci.net (PMDF V5.2-32 #40475)
 with ESMTPA id <01JO7YYDCI468WW11S@shoe.reston.mci.net> for ietf@ietf.org;
 Fri, 14 Apr 2000 09:25:51 EST
Date: Fri, 14 Apr 2000 09:23:00 -0400
From: John C Klensin - IAB Chair <klensin+iab@jck.com>
Subject: RE: rfc-editor?
To: "Shaw, Robert" <Robert.Shaw@itu.int>
Cc: "'Brian E Carpenter'" <brian@hursley.ibm.com>, ietf@ietf.org
Message-id: <2221440998.955704180@localhost>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.0b12 (Win32)
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
Content-transfer-encoding: 7BIT
Content-Transfer-Encoding: 7BIT
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7BIT

--On Friday, April 14, 2000 14:41 +0200 "Shaw, Robert"
<Robert.Shaw@itu.int> wrote:

> O.K., help me understand this. ISOC paid ISI a few hundred 
> thousand dollars (?) for the RFC-Editor functions (wasn't it
> really funding for the entire IANA role?). 

No.  It is important to understand that the IANA role and the
RFC Editor one were _always_ separate, although some of the same
people were historically involved in both and, again
historically, both operated under Jon Postel's management.

> However, since
> Joyce Reynolds is  now listed both as a staff member of ICANN
> ("Manager of Publications")  at
> http://www.icann.org/general/abouticann.htm and "liaison" to 
> the RFC editor on the IAB pages at
> http://www.iab.org/members.html the ISOC funding seems to have
> been used/absorbed for ICANN staff?

Again, no.  Many of us find ourselves wearing multiple hats.  I
don't know the financial arrangements between ISI and ICANN that
support the two arrangements for Joyce's time, but she is less
than full time on either of them.   I.e., part of her time
involves RFC Editor work (and the related liaison to IAB),
another involves some efforts on ICANN's part.  As described in
the most recent IAB Charter, there is also provision for a
liaison from the IANA: while that position is now vacant, we
assume it will soon be filled and do not expect that Joyce be
the person filling that role.

> However, since there is a recent MoU between IETF and ICANN
> "Concerning  the Technical Work of the Internet Assigned
> Numbers Authority" at 
> http://www.icann.org/general/ietf-icann-mou-01mar00.htm, I'm
> puzzled why the scope of this did not include the RFC-Editor
> function? If the  the absence is supposed to indicate some
> IETF independence from  ICANN, it's certainly not clear this
> is reality if the IAB RFC-Editor  liaison contact is working
> for ICANN.

If she were working full time for ICANN, and not at all for ISI,
or if the RFC Editor function consisted of ICANN (and not ISI)
staff, this would be an interesting observation and conclusion.
But neither is the case.

Again, the RFC Editor and IANA functions are separate and always
have been.  There are useful synergies between the two
activites, which is why we have welcomed close coordination, but
your confusion is due to assuming that the two are really the
same.

> The above MoU recognizes that the "IANA technical team is now
> part  of ICANN" and that the "IAB is chartered to designate
> the IANA on  behalf of the IETF". But isn't this agreement
> only ad hoc recognition  of reality since the IAB really
> doesn't have any ability to  (re)designate the IANA functions?
> That's because there's this  strong rumour going around that
> the US Department of Commerce  believes it is transferring the
> IANA functions to ICANN....

IANA has traditionally had several functions, and some of the
boundaries periodically create confusion.  We are satisfied with
the present relationships and hence see no prospect for having
to change then.   However, we believe that there is a fairly
general understanding among IAB, ICANN, and US DoC that the IAB
could, indeed, transfer the portions of the IANA efforts that
relate to IETF work elsewhere if that were necessary or
desirable.

 John Klensin
 IAB Chair




From owner-ietf-outbound  Fri Apr 14 12:50:51 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA10515
	for ietf-outbound.10@ietf.org; Fri, 14 Apr 2000 12:50:02 -0400 (EDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10419
	for <ietf@ietf.org>; Fri, 14 Apr 2000 12:46:08 -0400 (EDT)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id JAA07143;
	Fri, 14 Apr 2000 09:46:08 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id QAA02267;
	Fri, 14 Apr 2000 16:46:07 GMT
Date: Fri, 14 Apr 2000 16:46:07 GMT
Message-Id: <200004141646.QAA02267@gra.isi.edu>
To: brian@hursley.ibm.com, Robert.Shaw@itu.int
Subject: RE: rfc-editor?
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
X-Loop: ietf@ietf.org

  *> 
  *> O.K., help me understand this. ISOC paid ISI a few hundred 
  *> thousand dollars (?) for the RFC-Editor functions (wasn't it really
  *> funding for the entire IANA role?). However, since Joyce Reynolds is 
  *> now listed both as a staff member of ICANN ("Manager of Publications") 
  *> at http://www.icann.org/general/abouticann.htm and "liaison" to 
  *> the RFC editor on the IAB pages at http://www.iab.org/members.html
  *> the ISOC funding seems to have been used/absorbed for ICANN staff?

Bob:

Let me be very clear about this: none of the ISOC funding that is
supporting the RFC Editor function at ISI has gone, or will go,
for ICANN functions.  One member of the RFC Editor team is principally
supported by DARPA, but that does not mean that DARPA is supporting
RFC Editor functions.   People can perform multiple functions, and
accountants can do the arithmetic, and it all works.

There IS no dark conspiracy here, just people devoting CONSIDERABLE
time and energy (without stock options, I might add) to making the
internet work.

Bob Braden



From owner-ietf-outbound  Fri Apr 14 13:20:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA11285
	for ietf-outbound.10@ietf.org; Fri, 14 Apr 2000 13:20:02 -0400 (EDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11009
	for <ietf@ietf.org>; Fri, 14 Apr 2000 13:10:07 -0400 (EDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id SAA41530; Fri, 14 Apr 2000 18:09:17 +0100
Received: from hursley.ibm.com (gsine03.us.sine.ibm.com [9.14.6.43]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id SAA11490; Fri, 14 Apr 2000 18:09:37 +0100 (BST)
Message-ID: <38F750C9.507B4135@hursley.ibm.com>
Date: Fri, 14 Apr 2000 12:09:29 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: John C Klensin - IAB Chair <klensin+iab@jck.com>
CC: "Shaw, Robert" <Robert.Shaw@itu.int>, ietf@ietf.org
Subject: Re: rfc-editor?
References: <2221440998.955704180@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

A grace note on John's reply:

It is *precisely* because of the complexity of the organizational relationships
that we now have a contract and an MoU defining our relations with the
RFC Editor and the IANA respectively. As long as the contract and the MoU
are respected, it is no concern of ours how the staff concerned divide
their time.

   Brian  

John C Klensin - IAB Chair wrote:
> 
> --On Friday, April 14, 2000 14:41 +0200 "Shaw, Robert"
> <Robert.Shaw@itu.int> wrote:
> 
> > O.K., help me understand this. ISOC paid ISI a few hundred
> > thousand dollars (?) for the RFC-Editor functions (wasn't it
> > really funding for the entire IANA role?).
> 
> No.  It is important to understand that the IANA role and the
> RFC Editor one were _always_ separate, although some of the same
> people were historically involved in both and, again
> historically, both operated under Jon Postel's management.
> 
> > However, since
> > Joyce Reynolds is  now listed both as a staff member of ICANN
> > ("Manager of Publications")  at
> > http://www.icann.org/general/abouticann.htm and "liaison" to
> > the RFC editor on the IAB pages at
> > http://www.iab.org/members.html the ISOC funding seems to have
> > been used/absorbed for ICANN staff?
> 
> Again, no.  Many of us find ourselves wearing multiple hats.  I
> don't know the financial arrangements between ISI and ICANN that
> support the two arrangements for Joyce's time, but she is less
> than full time on either of them.   I.e., part of her time
> involves RFC Editor work (and the related liaison to IAB),
> another involves some efforts on ICANN's part.  As described in
> the most recent IAB Charter, there is also provision for a
> liaison from the IANA: while that position is now vacant, we
> assume it will soon be filled and do not expect that Joyce be
> the person filling that role.
> 
> > However, since there is a recent MoU between IETF and ICANN
> > "Concerning  the Technical Work of the Internet Assigned
> > Numbers Authority" at
> > http://www.icann.org/general/ietf-icann-mou-01mar00.htm, I'm
> > puzzled why the scope of this did not include the RFC-Editor
> > function? If the  the absence is supposed to indicate some
> > IETF independence from  ICANN, it's certainly not clear this
> > is reality if the IAB RFC-Editor  liaison contact is working
> > for ICANN.
> 
> If she were working full time for ICANN, and not at all for ISI,
> or if the RFC Editor function consisted of ICANN (and not ISI)
> staff, this would be an interesting observation and conclusion.
> But neither is the case.
> 
> Again, the RFC Editor and IANA functions are separate and always
> have been.  There are useful synergies between the two
> activites, which is why we have welcomed close coordination, but
> your confusion is due to assuming that the two are really the
> same.
> 
> > The above MoU recognizes that the "IANA technical team is now
> > part  of ICANN" and that the "IAB is chartered to designate
> > the IANA on  behalf of the IETF". But isn't this agreement
> > only ad hoc recognition  of reality since the IAB really
> > doesn't have any ability to  (re)designate the IANA functions?
> > That's because there's this  strong rumour going around that
> > the US Department of Commerce  believes it is transferring the
> > IANA functions to ICANN....
> 
> IANA has traditionally had several functions, and some of the
> boundaries periodically create confusion.  We are satisfied with
> the present relationships and hence see no prospect for having
> to change then.   However, we believe that there is a fairly
> general understanding among IAB, ICANN, and US DoC that the IAB
> could, indeed, transfer the portions of the IANA efforts that
> relate to IETF work elsewhere if that were necessary or
> desirable.
> 
>  John Klensin
>  IAB Chair

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Brian E Carpenter 
Program Director, Internet Standards & Technology, IBM 
On assignment for IBM at http://www.iCAIR.org 
Attend INET 2000: http://www.isoc.org/inet2000
Non-IBM email: brian@icair.org



From owner-ietf-outbound  Fri Apr 14 13:50:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA11774
	for ietf-outbound.10@ietf.org; Fri, 14 Apr 2000 13:50:02 -0400 (EDT)
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11721
	for <ietf@ietf.org>; Fri, 14 Apr 2000 13:45:13 -0400 (EDT)
Received: from laptop.imc.org (ip12.proper.com [165.227.249.12])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA02750
	for <ietf@ietf.org>; Fri, 14 Apr 2000 10:41:23 -0700 (PDT)
Message-Id: <4.3.2.20000414103436.00c2a200@mail.imc.org>
X-Sender: phoffman@mail.imc.org
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Fri, 14 Apr 2000 10:45:35 -0700
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@IMC.ORG>
Subject: RE: rfc-editor?
In-Reply-To: <200004141646.QAA02267@gra.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 04:46 PM 4/14/00 +0000, Bob Braden wrote:
>There IS no dark conspiracy here, just people devoting CONSIDERABLE
>time and energy (without stock options, I might add) to making the
>internet work.

A great idea! Stock options in the RFC Editor function!

- A hot startup of about 25 years (in real time, not Internet time)

- Geekier than Slashdot

- Can change the definition of the Internet by themselves overnight

- Content is created for them by industry leaders for free

- Just look at the demographics of the people who come to their "standards 
portal"

- Imagine how much Cisco or Microsoft would spend to buy them



From owner-ietf-outbound  Fri Apr 14 14:55:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA13003
	for ietf-outbound.10@ietf.org; Fri, 14 Apr 2000 14:54:52 -0400 (EDT)
Received: from mail.mi8.com (mail.mi8.com [63.68.243.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12796
	for <ietf@ietf.org>; Fri, 14 Apr 2000 14:40:06 -0400 (EDT)
Received: from nycexbh01.mi8.com (unverified) by mail.mi8.com
 (Content Technologies SMTPRS 4.1.2) with ESMTP id <B3f44f30d4b91f0557e@mail.mi8.com> for <ietf@ietf.org>;
 Fri, 14 Apr 2000 14:36:34 -0400
Received: by nycexbh01.mi8.com with Internet Mail Service (5.5.2650.21)
	id <28R1XBP3>; Fri, 14 Apr 2000 14:35:16 -0400
Message-ID: <37E1E2BB9C28D311AB390008C707D2A602E93843@nycexis01.mi8.com>
From: Steve Hultquist <ssh@accumedia.com>
To: ietf@ietf.org
Subject: RE: recommendation against publication of draft-cerpa-necp-02.txt
	 
Date: Fri, 14 Apr 2000 14:35:07 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFA640.2CD39126"
X-Loop: ietf@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BFA640.2CD39126
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Keith Moore wrote:
> > .  .  .
> > > > > 3. Aside from the technical implications of intercepting =
traffic,
> > > > > redirecting it to unintended destinations, or forging traffic =
from
> > > > > someone else's IP address - there are also legal, social, =
moral
and
> > > > > commercial implications of doing so.
> > > >
> > > > You will need to be far more specific here.  I see absolutely
nothing that
> > > > is not legal, is not social, or is not moral.
> > >=20
> > > Okay, I'll offer a few specific examples, by no means the only =
ones:
> > >=20
> > > 1. an Internet service provider which deliberately intercepts =
traffic
> > > (say, an IP packet) which was intended for one address or =
service,
> > > and delivers it to another address or service (say that of an
interception
> > > proxy) may be misrepresenting the service it provides (it's not =
really
> > > providing IP datagram delivery service because IP doesn't work =
this
way).
> >=20
> > Okay, I think I see the mistake you're making. You're crossing
> > abstraction layers and conflating two different things (the name of
> > a service with the end point of the connection to that service). =
You
> > are criticizing the moving of an endpoint when what you really
> > object to is the misrepresentation of a service. Or do you also
> > object to HTTP redirects, dynamic URL rewriting, CNAMEs, telephone
> > Call Forwarding, or post office redirecting of mail after you move? =

>
> I don't object to redirects at all, as long as they are carefully=20
> designed.   I do object to misrepresenting the service.    As I've=20
> said elsewhere, if the service wants to set up an interception proxy=20
> on its own network to help make its service more scalable, I have=20
> no problem with that.  I do have a problem with unauthorized third=20
> parties setting up interception proxies.  (which is according to
> my understanding all the most common application of such devices)

I, too, have been watching this conversation from the sidelines, =
primarily
to see the general opinions of the IETF on this topic. However, as one =
who
is considering deploying such devices both topologically close to =
servers
(so-called "Web accelerators") and topologically close to clients of =
the
servers (as an owner of the servers -- so-called "content =
distribution"),
this is of vital interest to me. In both cases that we are considering, =
the
devices are within the same administrative domain as the servers
(effectively administered by the content owner). This is, as a number =
of
people mentioned, a key differentiator in this discussion.=20

For Internet network-based applications such as streaming media and =
rich
content, both of these technique provide significant advantages for the
administrators of the delivery, hence the intent of NECP is important.

And, as Bill Sommerfeld wrote:
> A quick read through draft-cerpa-necp-02.txt suggests that it's
> primarily targeted at forms of redirection which occur at the request
> of service operators.  Such systems are best thought of as a funny
> kind of application-layer proxy, and are far less damaging to the
> end-to-end internet model than the transparent proxies cited above.
>
> I think it's important to carefully distinguish between these sorts =
of
> redirection.  Some clarifying text in the draft to this effect would
> be helpful.

I agree that this is important, as well.

Patrik F=E4ltstr=F6m said
> I have no problem whatsoever to have proxies being part of the=20
> web-model, but I am strongly opposing someone in the middle of the=20
> communication path intercepting and redirecting IP-packages, as the=20
> client will not communicate with whoever he wanted.

With which I also agree.

However, I do not see an appropriate documentation of NECP as =
incompatible
with those two views.

ssh
--
Steve Hultquist
VP Ops
Accumedia, Boulder, CO USA

------_=_NextPart_001_01BFA640.2CD39126
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: recommendation against publication of =
draft-cerpa-necp-02.txt </TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Keith Moore wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; .&nbsp; .&nbsp; .</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; 3. Aside from the technical =
implications of intercepting traffic,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; redirecting it to =
unintended destinations, or forging traffic from</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; someone else's IP address - =
there are also legal, social, moral and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; commercial implications of =
doing so.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; You will need to be far more =
specific here.&nbsp; I see absolutely nothing that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; is not legal, is not social, or =
is not moral.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Okay, I'll offer a few specific =
examples, by no means the only ones:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; 1. an Internet service provider which =
deliberately intercepts traffic</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; (say, an IP packet) which was =
intended for one address or service,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; and delivers it to another address or =
service (say that of an interception</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; proxy) may be misrepresenting the =
service it provides (it's not really</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; providing IP datagram delivery =
service because IP doesn't work this way).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Okay, I think I see the mistake you're =
making. You're crossing</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; abstraction layers and conflating two =
different things (the name of</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; a service with the end point of the =
connection to that service). You</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; are criticizing the moving of an endpoint =
when what you really</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; object to is the misrepresentation of a =
service. Or do you also</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; object to HTTP redirects, dynamic URL =
rewriting, CNAMEs, telephone</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Call Forwarding, or post office =
redirecting of mail after you move? </FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; I don't object to redirects at all, as long as =
they are carefully </FONT>
<BR><FONT SIZE=3D2>&gt; designed.&nbsp;&nbsp; I do object to =
misrepresenting the service.&nbsp;&nbsp;&nbsp; As I've </FONT>
<BR><FONT SIZE=3D2>&gt; said elsewhere, if the service wants to set up =
an interception proxy </FONT>
<BR><FONT SIZE=3D2>&gt; on its own network to help make its service =
more scalable, I have </FONT>
<BR><FONT SIZE=3D2>&gt; no problem with that.&nbsp; I do have a problem =
with unauthorized third </FONT>
<BR><FONT SIZE=3D2>&gt; parties setting up interception proxies.&nbsp; =
(which is according to</FONT>
<BR><FONT SIZE=3D2>&gt; my understanding all the most common =
application of such devices)</FONT>
</P>

<P><FONT SIZE=3D2>I, too, have been watching this conversation from the =
sidelines, primarily to see the general opinions of the IETF on this =
topic. However, as one who is considering deploying such devices both =
topologically close to servers (so-called &quot;Web accelerators&quot;) =
and topologically close to clients of the servers (as an owner of the =
servers -- so-called &quot;content distribution&quot;), this is of =
vital interest to me. In both cases that we are considering, the =
devices are within the same administrative domain as the servers =
(effectively administered by the content owner). This is, as a number =
of people mentioned, a key differentiator in this discussion. =
</FONT></P>

<P><FONT SIZE=3D2>For Internet network-based applications such as =
streaming media and rich content, both of these technique provide =
significant advantages for the administrators of the delivery, hence =
the intent of NECP is important.</FONT></P>

<P><FONT SIZE=3D2>And, as Bill Sommerfeld wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; A quick read through draft-cerpa-necp-02.txt =
suggests that it's</FONT>
<BR><FONT SIZE=3D2>&gt; primarily targeted at forms of redirection =
which occur at the request</FONT>
<BR><FONT SIZE=3D2>&gt; of service operators.&nbsp; Such systems are =
best thought of as a funny</FONT>
<BR><FONT SIZE=3D2>&gt; kind of application-layer proxy, and are far =
less damaging to the</FONT>
<BR><FONT SIZE=3D2>&gt; end-to-end internet model than the transparent =
proxies cited above.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; I think it's important to carefully distinguish =
between these sorts of</FONT>
<BR><FONT SIZE=3D2>&gt; redirection.&nbsp; Some clarifying text in the =
draft to this effect would</FONT>
<BR><FONT SIZE=3D2>&gt; be helpful.</FONT>
</P>

<P><FONT SIZE=3D2>I agree that this is important, as well.</FONT>
</P>

<P><FONT SIZE=3D2>Patrik F=E4ltstr=F6m said</FONT>
<BR><FONT SIZE=3D2>&gt; I have no problem whatsoever to have proxies =
being part of the </FONT>
<BR><FONT SIZE=3D2>&gt; web-model, but I am strongly opposing someone =
in the middle of the </FONT>
<BR><FONT SIZE=3D2>&gt; communication path intercepting and redirecting =
IP-packages, as the </FONT>
<BR><FONT SIZE=3D2>&gt; client will not communicate with whoever he =
wanted.</FONT>
</P>

<P><FONT SIZE=3D2>With which I also agree.</FONT>
</P>

<P><FONT SIZE=3D2>However, I do not see an appropriate documentation of =
NECP as incompatible with those two views.</FONT>
</P>

<P><FONT SIZE=3D2>ssh</FONT>
<BR><FONT SIZE=3D2>--</FONT>
<BR><FONT SIZE=3D2>Steve Hultquist</FONT>
<BR><FONT SIZE=3D2>VP Ops</FONT>
<BR><FONT SIZE=3D2>Accumedia, Boulder, CO USA</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFA640.2CD39126--



From owner-ietf-outbound  Fri Apr 14 20:50:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA16350
	for ietf-outbound.10@ietf.org; Fri, 14 Apr 2000 20:50:02 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16260
	for <ietf@ietf.org>; Fri, 14 Apr 2000 20:41:19 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id RAA19141;
	Fri, 14 Apr 2000 17:41:19 -0700 (PDT)
Date: Fri, 14 Apr 2000 17:41:19 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200004150041.RAA19141@shell5.ba.best.com>
To: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: breaking the IP model (or not)
X-Loop: ietf@ietf.org

Keith Moore wrote:

> it's not at all clear whether NAT provided additional time for
> IPng development or whether such time was really needed.  IPv6 was
> largely developed before NAT enjoyed significant deployment, and
> arguably NAT has delayed adoption of IPv6.  and because of the NAT
> deployment it is now somewhat "untimely" to deploy applications like
> IP telephony.  whereas if IPv6 had been adopted a bit earlier
> (because NAT had not filled the vacuum, so to speak) IP telephony
> would work just fine with it.

True, but you also have to take into account that IPv4 is mature
technology (and was so at the time of NAT deployment).  The user demand
for Internet access made NAT a more attractive avenue because the
industry had confidence that it would work without them having to
make changes.  If you could sell a NAT-compliant box you had an
eager market; not quite so with an IPv6 compliant box.

> of course, IPv6 might have moved along slowly even without NAT.
> but it would probably have moved faster had NATs not existed.

Maybe.  Hard to say.  Depends on how comfortable the industry would
have been with it.

> best thing I can say about NAT is that it motivated me to work on 6to4.

:)

--gregbo



From owner-ietf-outbound  Fri Apr 14 21:10:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA16543
	for ietf-outbound.10@ietf.org; Fri, 14 Apr 2000 21:10:02 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16519
	for <ietf@ietf.org>; Fri, 14 Apr 2000 21:08:22 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id SAA26784;
	Fri, 14 Apr 2000 18:03:12 -0700 (PDT)
Date: Fri, 14 Apr 2000 18:03:12 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200004150103.SAA26784@shell5.ba.best.com>
To: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: breaking the IP model (or not)
X-Loop: ietf@ietf.org

Keith Moore wrote:

> perhaps architectural impurity alone shouldn't keep you from doing
> something, but the fact that something violates fundamental design
> assumptions should cause you to do some analysis and hard thinking
> about the likely consequences of using them.  and if you are in the
> business of selling boxes that violate the design assumptions you
> shouldn't misrepresent these to your customers.

True, however I think at least some of the customers are also to blame.
In their haste to get on the Internet they went out and bought NAT boxes
without understanding their limitations.

I hear about this sort of thing even outside of the context of NAT,
e.g. with people who have non-globally routable IP address blocks and
don't understand why they can't reach certain sites.  They then complain
to their ISPs, who point out that their service does not guarantee
global routing.

--gregbo



From owner-ietf-outbound  Fri Apr 14 22:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA18880
	for ietf-outbound.10@ietf.org; Fri, 14 Apr 2000 22:40:02 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18854
	for <ietf@ietf.org>; Fri, 14 Apr 2000 22:39:40 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id TAA23855;
	Fri, 14 Apr 2000 19:39:40 -0700 (PDT)
Date: Fri, 14 Apr 2000 19:39:40 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200004150239.TAA23855@shell5.ba.best.com>
To: "'Keith Moore'" <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: breaking the IP model (or not)
X-Loop: ietf@ietf.org

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

> there's something odd to my ear about people needing to
> *be presented* with better alternatives than doing harm to the
> architecture as opposed to those people *developing* better alternatives.

With my scientist/engineer hat on, I like to develop architecturally
pure solutions.  They tend to have fewer awkward cases.  The code
evolves straightforwardly from the design.  The boundary conditions are
easier to test.

With my pragmatist hat on, I realize I occasionally need to do things
that will enable me to pay the bills. :(

> I suspect there's something about the current economic climate that
> favors development of quick fixes over development of sane ones.
> but the apparent shortsightedness still bothers me.

My general (cynical) opinion of NAT and other proxy technology is that
the marketplace spoke louder than the voices of the architectural
purists.  (No offense intended.)  However, given recent changes in the
economic climate, perhaps things will head in the opposite direction.

--gregbo, enjoying this thread



From owner-ietf-outbound  Fri Apr 14 23:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA19143
	for ietf-outbound.10@ietf.org; Fri, 14 Apr 2000 23:20:02 -0400 (EDT)
Received: from sirius.ctr.columbia.edu (root@sirius.ctr.columbia.edu [128.59.64.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA19112
	for <ietf@ietf.org>; Fri, 14 Apr 2000 23:12:17 -0400 (EDT)
Received: from comet.columbia.edu (coltrane.ocs.columbia.edu [128.59.240.174]) by sirius.ctr.columbia.edu (8.9.3/8.6.4.287) with ESMTP id XAA02768; Fri, 14 Apr 2000 23:12:02 -0400 (EDT)
Message-ID: <38F7E80B.6C3AF9FC@comet.columbia.edu>
Date: Fri, 14 Apr 2000 23:54:51 -0400
From: campbell <campbell@comet.columbia.edu>
Reply-To: campbell@comet.columbia.edu
Organization: Center for Telecommunications Research, Columbia University
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Greg Skinner <gds@best.com>
CC: "'Keith Moore'" <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: breaking the IP model (or not)
References: <200004150239.TAA23855@shell5.ba.best.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Greg Skinner wrote:

> My general (cynical) opinion of NAT and other proxy technology is that
> the marketplace spoke louder than the voices of the architectural
> purists.  (No offense intended.)  However, given recent changes in the
> economic climate, perhaps things will head in the opposite direction.
> 

Looks like the IPv6.com IPO is on hold until the market picks up .....



From owner-ietf-outbound  Sat Apr 15 00:30:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA19921
	for ietf-outbound.10@ietf.org; Sat, 15 Apr 2000 00:30:02 -0400 (EDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19885
	for <ietf@ietf.org>; Sat, 15 Apr 2000 00:26:26 -0400 (EDT)
Received: from sunmail1.Sun.COM ([129.145.1.2])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id VAA08750;
	Fri, 14 Apr 2000 21:26:17 -0700 (PDT)
Received: from jurassic.eng.sun.com (jurassic.Eng.Sun.COM [129.146.83.130])
	by sunmail1.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6.1-sunmail1) with ESMTP id VAA29770;
	Fri, 14 Apr 2000 21:26:17 -0700 (PDT)
Received: from lillen (awe174-18.AWE.Sun.COM [192.29.174.18])
	by jurassic.eng.sun.com (8.10.1+Sun/8.10.1) with SMTP id e3F4QFw614372;
	Fri, 14 Apr 2000 21:26:16 -0700 (PDT)
Date: Fri, 14 Apr 2000 21:19:59 -0700 (PDT)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: interception proxies
To: Joe Touch <touch@ISI.EDU>
Cc: Keith Moore <moore@cs.utk.edu>, Vernon Schryver <vjs@CALCITE.RHYOLITE.COM>,
        ietf@ietf.org
In-Reply-To: "Your message with ID" <38F3BED4.26704EFD@isi.edu>
Message-ID: <Roam.SIMC.2.0.6.955772399.589.nordmark@jurassic>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
X-Loop: ietf@ietf.org


> A copy of the note, admittedly very rough (just an outline, and a very
> rough one at that) is at:
> 
> 	http://www.isi.edu/touch/pubs/hazards-outline.txt

This doesn't list what I thought was an obvious issue.
If multiple nodes are originating packets with the same source
IP address it will be rather hard for them to ensure the required
uniqueness on the IP ID field (unique for the combination
of source IP, destination IP and protocol).

I suspect that most of boxes that play these games don't worry about
IP ID which might cause garbage reassembly should the same
IP ID be used when multiple such boxes are sending to the same IP address.

  Erik



From owner-ietf-outbound  Sat Apr 15 06:40:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA02894
	for ietf-outbound.10@ietf.org; Sat, 15 Apr 2000 06:40:01 -0400 (EDT)
Received: from anise.tte.vtt.fi (anise.tte.vtt.fi [130.188.52.29])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02856
	for <ietf@ietf.org>; Sat, 15 Apr 2000 06:33:43 -0400 (EDT)
Received: (from msa@localhost)
	by anise.tte.vtt.fi (8.8.5/8.8.5) id NAA15323;
	Sat, 15 Apr 2000 13:33:43 +0300 (EET DST)
Date: Sat, 15 Apr 2000 13:33:43 +0300 (EET DST)
From: Markku Savela <msa@anise.tte.vtt.fi>
Message-Id: <200004151033.NAA15323@anise.tte.vtt.fi>
To: ietf@ietf.org
In-reply-to: <200004150239.TAA23855@shell5.ba.best.com> (message from Greg Skinner on Fri, 14 Apr 2000 19:39:40 -0700 (PDT))
Subject: Re: breaking the IP model (or not)
Reply-to: msa@hemuli.tte.vtt.fi (Markku Savela)
X-Loop: ietf@ietf.org


> From: Greg Skinner <gds@best.com>

> My general (cynical) opinion of NAT and other proxy technology is that
> the marketplace spoke louder than the voices of the architectural
> purists.  (No offense intended.)  However, given recent changes in the
> economic climate, perhaps things will head in the opposite direction.

NAT could also be tempting for some ISPs, becuase that way they will
have captive clients. Anything not especially allowed by the NAT
boxes, must be separately orderd from the ISP (for example, client
cannot send directly mail out to destination based on MX records, they
have to buy mail relaying from ISP).

But, I guess the "marketplace" is the ISP's, not the individual
clients, who don't know what they might miss.



From owner-ietf-outbound  Sun Apr 16 02:52:52 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA23010
	for ietf-outbound.10@ietf.org; Sun, 16 Apr 2000 02:50:03 -0400 (EDT)
Received: from arcc.or.ke (root@[212.49.87.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22980
	for <ietf@ietf.org>; Sun, 16 Apr 2000 02:40:22 -0400 (EDT)
Received: from 199.2.222.254 ([199.2.222.124])
	by arcc.or.ke (8.9.3/8.9.3) with SMTP id JAA24332
	for <ietf@ietf.org>; Sun, 16 Apr 2000 09:58:53 +0300 (EAT)
Date: Sun, 16 Apr 2000 09:58:53 +0300 (EAT)
Message-Id: <200004160658.JAA24332@arcc.or.ke>
X-Sender: musandu@199.2.222.254
X-Mailer: Windows Eudora Pro Version 2.1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: Musandu <musandu@arcc.or.ke>
Subject: Sats vs plain UMTS
X-Loop: ietf@ietf.org

Could hand held satelitte phones kill UMTS even before it takes root, as the
key tools for personal high bandwidth internet access?

Yours truly,
Nyagudi Musandu



From owner-ietf-outbound  Sun Apr 16 07:10:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA06441
	for ietf-outbound.10@ietf.org; Sun, 16 Apr 2000 07:10:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06405
	for <ietf@ietf.org>; Sun, 16 Apr 2000 07:02:26 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id NAA08700;
	Sun, 16 Apr 2000 13:02:03 +0200
Message-Id: <4.3.1.2.20000416130045.02253ee8@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sun, 16 Apr 2000 13:01:13 +0200
To: Musandu <musandu@ARCC.OR.KE>, ietf@ietf.org
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: Sats vs plain UMTS
In-Reply-To: <200004160658.JAA24332@arcc.or.ke>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 09:58 16.04.2000 +0300, Musandu wrote:
>Could hand held satelitte phones kill UMTS even before it takes root, as the
>key tools for personal high bandwidth internet access?

at the moment I think GSM killed Iridium, so the shoe may be on the other 
foot..

                   Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Sun Apr 16 12:20:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA08730
	for ietf-outbound.10@ietf.org; Sun, 16 Apr 2000 12:20:02 -0400 (EDT)
Received: from mta1biz.bizmailsrvcs.net (mta1.bizmailsrvcs.net [206.46.164.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08705
	for <ietf@ietf.org>; Sun, 16 Apr 2000 12:17:13 -0400 (EDT)
Received: from Software.com ([207.175.94.52]) by mta1biz.bizmailsrvcs.net
          with ESMTP
          id <20000416161644.UYXL851310.mta1biz.bizmailsrvcs.net@Software.com>
          for <ietf@ietf.org>; Sun, 16 Apr 2000 11:16:44 -0500
Sender: droyer
Message-ID: <38F9D81A.CC82F5FD@Software.com>
Date: Sun, 16 Apr 2000 08:11:22 -0700
From: Doug Royer <Doug.Royer@Software.com>
Reply-To: itef@ietf.org
Organization: Software.com
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: Sats vs plain UMTS
References: <4.3.1.2.20000416130045.02253ee8@dokka.kvatro.no>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Harald Tveit Alvestrand wrote:
> 
> At 09:58 16.04.2000 +0300, Musandu wrote:
> >Could hand held satelitte phones kill UMTS even before it takes root,
> > as the key tools for personal high bandwidth internet access?
> 
> at the moment I think GSM killed Iridium, so the shoe may be on the other
> foot..

Not only is Iridium dead - The news said they are starting to send
signals to the satellites to force them out of orbit - to splash in
the ocean!

-Doug



From owner-ietf-outbound  Sun Apr 16 14:20:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA09432
	for ietf-outbound.10@ietf.org; Sun, 16 Apr 2000 14:20:02 -0400 (EDT)
Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA09372
	for <ietf@ietf.org>; Sun, 16 Apr 2000 14:13:37 -0400 (EDT)
From: sthaug@nethelp.no
Received: (qmail 18411 invoked by uid 1001); 16 Apr 2000 18:13:38 +0000 (GMT)
To: ietf@ietf.org, Doug.Royer@Software.com
Subject: Re: Sats vs plain UMTS
In-Reply-To: Your message of "Sun, 16 Apr 2000 08:11:22 -0700"
References: <38F9D81A.CC82F5FD@Software.com>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Sun, 16 Apr 2000 20:13:38 +0200
Message-ID: <18409.955908818@verdi.nethelp.no>
X-Loop: ietf@ietf.org

> Not only is Iridium dead - The news said they are starting to send
> signals to the satellites to force them out of orbit - to splash in
> the ocean!

http://www.userfriendly.org/cartoons/archives/00apr/20000402.html

Steinar Haug, Nethelp consulting, sthaug@nethelp.no



From owner-ietf-outbound  Sun Apr 16 16:00:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA10054
	for ietf-outbound.10@ietf.org; Sun, 16 Apr 2000 16:00:02 -0400 (EDT)
Received: from illyana.qualcomm.com (illyana.qualcomm.com [129.46.2.83])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10011
	for <ietf@ietf.org>; Sun, 16 Apr 2000 15:55:56 -0400 (EDT)
Received: from davespc (xanadu-client18.qualcomm.com [129.46.86.147]) by illyana.qualcomm.com (8.9.3/8.9.3/1.0) with SMTP id MAA05890; Sun, 16 Apr 2000 12:55:29 -0700 (PDT)
From: "Dave Miller" <dave@buyutree.com>
To: "Musandu" <musandu@arcc.or.ke>, <ietf@ietf.org>
Subject: RE: Sats vs plain UMTS
Date: Sun, 16 Apr 2000 12:55:23 -0700
Message-ID: <000401bfa7dd$b3efa020$8621fed8@davespc>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-Reply-To: <200004160658.JAA24332@arcc.or.ke>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

There are fundamental laws of physics that make such a proposition a long
way off.

Limits on peak power, energy, RF bandwidth, and aperture (antenna) space
still place very real limitations on peak bandwidth and total capacity in
both the satellite and the personal unit.

There is such a demand for bandwidth that the market can support multiple
coexisting  (symbiotic?) technologies, each adapted to a specific
environment.

> Could hand held satellite phones kill UMTS even before it takes
> root, as the key tools for personal high bandwidth internet access?




From owner-ietf-outbound  Mon Apr 17 05:52:02 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA28015
	for ietf-outbound.10@ietf.org; Mon, 17 Apr 2000 05:50:02 -0400 (EDT)
Received: from mail2.itu.int (mail2.itu.ch [156.106.192.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27988
	for <ietf@ietf.org>; Mon, 17 Apr 2000 05:46:06 -0400 (EDT)
Received: by mail2.itu.ch with Internet Mail Service (5.5.2650.21)
	id <JDF4C8A7>; Mon, 17 Apr 2000 11:42:51 +0200
Message-ID: <DA5558CC09AED311ABE10000778D757F4C2C35@mailsrv.itu.ch>
From: "Shaw, Robert" <Robert.Shaw@itu.int>
To: "'Musandu'" <musandu@ARCC.OR.KE>
Cc: ietf@ietf.org
Subject: RE: Sats vs plain UMTS
Date: Mon, 17 Apr 2000 11:45:38 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

> -----Original Message-----
> From: Musandu [mailto:musandu@ARCC.OR.KE]
> Sent: Sunday, April 16, 2000 8:59 AM
> To: ietf@ietf.org
> Subject: Sats vs plain UMTS
> 
> 
> Could hand held satelitte phones kill UMTS even before it 
> takes root, as the key tools for personal high bandwidth 
> internet access?
> 
> Yours truly,
> Nyagudi Musandu

Extremely unlikely. First, satellite phone systems support 
only low-bitrate data (9.6 kbps). There are planned larger 
bandwidth systems (e.g., Teledesic) but the sat-phone 
business is quite fuzzy following the collapse of Iridium, 
ICO's problems, and constant market repositioning in the
LEOS/MEOS space in which only Globalstar is flying...

Terrestial wireless systems (market leader is now GSM with 
~260 million subscribers and a wide geographical footprint 
except in the Americas) have a huge head start and will very 
likely continue to dominate the market. UMTS is one part of 
the ITU's IMT-2000 family of 3G systems with a limited set 
of radio interfaces (see www.itu.int/imt/ or perhaps 
www.gsmworld.com).

TDMA-based 2.5G systems using GPRS (and perhaps EDGE) will 
clearly be an important mobile data transition platform to 
3G systems (supporting up to 2 Mbps). 3G systems based on 
WCDMA will probably be deployed first in Japan in early 2001. 
One of the first movers will be NTT Docomo: their year-old 
"i-mode" mobile data service, although low-bandwidth, has 
demonstrated the potential market with already around 6 
million subscribers. On that basis, NTT Docomo is now the 
largest ISP in Japan and has over 8,000 i-mode content providers. 
Elsewhere, the bet is on WAP (www.wapforum.com) but expect to 
see much convergence between WAP and "i-mode" (actually a 
simplified HTML) in the next year. 

Bob



From owner-ietf-outbound  Mon Apr 17 08:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA01391
	for ietf-outbound.10@ietf.org; Mon, 17 Apr 2000 08:50:02 -0400 (EDT)
Received: from sj-mailhub-3.cisco.com (sj-mailhub-3.cisco.com [171.68.224.215])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01263
	for <ietf@ietf.org>; Mon, 17 Apr 2000 08:46:37 -0400 (EDT)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by sj-mailhub-3.cisco.com (8.9.1a/8.9.1) with ESMTP id FAA17010;
	Mon, 17 Apr 2000 05:49:01 -0700 (PDT)
Received: from p7020-img-nt.cisco.com (tokyo-ppp-dynamic8.cisco.com [144.254.188.136]) by rhino (SMI-8.6/CISCO.WS.1.1) with ESMTP id FAA00499; Mon, 17 Apr 2000 05:51:05 -0700
Message-Id: <4.3.1.2.20000417195256.0310d530@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Mon, 17 Apr 2000 19:55:54 +0900
To: "Derrell D. Piper" <ddp@Network-Alchemy.COM>
From: Fred Baker <fred@cisco.com>
Subject: Re: recommendation against publication of
  draft-cerpa-necp-02.txt 
Cc: ietf@ietf.org
In-Reply-To: <200004101544.IAA07027@gallium.network-alchemy.com>
References: <Your message of "Mon, 10 Apr 2000 07:00:56 EDT." <200004101100.HAA10341@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 12:44 AM 4/11/00 -0700, Derrell D. Piper wrote:
>And there you have the argument for publishing this document.  I much prefer a
>model where we allow for free exchange of ideas, even bad ones.

hear! hear!

>  I tend to
>believe that if someone took the time to write up a document that there's
>probably some reason for it.  So let's call this an experimental RFC and get
>on with life.  Isn't that what the experimental category denotes?

Well, that's one way to interpret it. I think I'd prefer the words of RFC 
2026, which imply that it is simply an idea, something being experimented 
with, and that the document represents a snapshot of the work at a 
particular point in time. We let time and experience tell us whether it is 
a good idea or a bad one, and if you want to participate in the experiment, 
you had best contact the experimenter, as things may have progressed since 
the document was published.



From owner-ietf-outbound  Mon Apr 17 10:20:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA03256
	for ietf-outbound.10@ietf.org; Mon, 17 Apr 2000 10:20:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03193
	for <ietf@ietf.org>; Mon, 17 Apr 2000 10:14:39 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12hCII-0003zy-00; Mon, 17 Apr 2000 15:14:30 +0100
Date: Mon, 17 Apr 2000 15:14:26 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Harald Tveit Alvestrand <Harald@alvestrand.no>
cc: Musandu <musandu@ARCC.OR.KE>, ietf@ietf.org
Subject: Re: Sats vs plain UMTS
In-Reply-To: <4.3.1.2.20000416130045.02253ee8@dokka.kvatro.no>
Message-ID: <Pine.GSO.4.21.0004171101500.189-100000@petra.ee.surrey.ac.uk>
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-Loop: ietf@ietf.org

On Sun, 16 Apr 2000, Harald Tveit Alvestrand wrote:

> At 09:58 16.04.2000 +0300, Musandu wrote:
> >Could hand held satelitte phones kill UMTS even before it takes root, as the
> >key tools for personal high bandwidth internet access?
> 
> at the moment I think GSM killed Iridium, so the shoe may be on the other 
> foot..
> 
>                    Harald

Harald, you're truly an inspiration.


GSM killed the Satellite Phone
(with apologies to Jonathan 'Buggles' King)

I saw you in the papers back in ninety-two
All of the satellites they'd need just to launch you
the business travellers that would then be phoning through
Oh-a oh 

Technology moved on ahead of your schedule
GSM, GPRS and EDGE - useful tools
and now I understand why they all call you 'fool'
Oh-a oh

I watched your market...

Oh-a oh
What did you tell it?

GSM killed the satellite phone.
GSM killed the satellite phone.
Standards came and broke you down.
Oh-a-a-a oh 

And now they talk about deorbiting your sats
We hired the engineers, they sound so old and sad
They recall the early dreams and all of those ads.

Oh-a oh 
Said 'One world. One phone.'

Oh-a oh
You were the first one...

GSM killed the satellite phone.
GSM killed the satellite phone.
Half-in my pocket when I'm on my feet,
It weighs a lot, it's not that neat.
Oh-a-aho oh, 
Oh-a-aho oh.

GSM killed the satellite phone
GSM killed the satellite phone
In street canyons and on your phone,
I can't receive, there's no dialtone
Cellular grew and took you down,
I'll have to use my mobile phone.

You are a satellite phone.
You are a satellite phone.
GSM killed the satellite phone. (x4)

(...deader than Apple's Newton.)

GSM killed the satellite phone. (You are a satellite phone.)

(fade out.)

[Iridium service stopped being guaranteed on 17 March 2000.
 Motorola's MCSI itself stopped service on 7 April 2000.
 http://www.ee.surrey.ac.uk/Personal/L.Wood/constellations/  ]

L.

and if you think this is bad, you just haven't
sung all the verses of 'Iridium Pie'.

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



From owner-ietf-outbound  Mon Apr 17 11:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA04259
	for ietf-outbound.10@ietf.org; Mon, 17 Apr 2000 11:30:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04136
	for <ietf@ietf.org>; Mon, 17 Apr 2000 11:21:32 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id LAA29149;
        Mon, 17 Apr 2000 11:20:38 -0400 (EDT)
Message-Id: <200004171520.LAA29149@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Fred Baker <fred@cisco.com>
cc: "Derrell D. Piper" <ddp@Network-Alchemy.COM>, ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt 
In-reply-to: Your message of "Mon, 17 Apr 2000 19:55:54 +0900."
             <4.3.1.2.20000417195256.0310d530@flipper.cisco.com> 
Date: Mon, 17 Apr 2000 11:20:38 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

I think various people have made a good case for eventually publishing 
this particular document, once appropriate revisions have been made.

I'm very supportive of the notion of free exchange of ideas, even
through the RFC mechanism - with the understanding that:

- IETF and the RFC Editor have limited resources and cannot publish 
  everything that comes their way
- it's inappropriate to use Experimental or Informational publications in 
  the RFC series to promote or claim legitimacy for ideas that are embroynic 
  or experimental in nature, especially when those ideas are violations of 
  Internet standards.  there should be a clear distinction between
  "this is somebody's idea for an experiment" and "this is the sense
  of the Internet technical community"
- some experiments are better carried out under controlled conditions.

Keith



From owner-ietf-outbound  Mon Apr 17 12:10:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA05218
	for ietf-outbound.10@ietf.org; Mon, 17 Apr 2000 12:10:02 -0400 (EDT)
Received: from msw.mimesweeper.com (msw.mimesweeper.com [194.168.90.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04865
	for <ietf@ietf.org>; Mon, 17 Apr 2000 11:57:46 -0400 (EDT)
Received: from bell.mimesweeper.com (unverified) by msw.mimesweeper.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc2a85a12634ba1e4bfea@msw.mimesweeper.com>;
 Mon, 17 Apr 2000 16:57:50 +0100
Received: from GK-VAIO (gk-vaio.mimesweeper.com [194.168.90.137]) by bell.mimesweeper.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id 2C7NRT57; Mon, 17 Apr 2000 16:57:13 +0100
Message-Id: <4.2.2.20000417153854.00bd3730@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Mon, 17 Apr 2000 15:42:26 +0100
To: L.Wood@eim.surrey.ac.uk
From: Graham Klyne <GK@dial.pipex.com>
Subject: Re: Sats vs plain UMTS
Cc: ietf@ietf.org
In-Reply-To: <Pine.GSO.4.21.0004171101500.189-100000@petra.ee.surrey.ac.
 uk>
References: <4.3.1.2.20000416130045.02253ee8@dokka.kvatro.no>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 03:14 PM 4/17/00 +0100, Lloyd Wood wrote:
>GSM killed the Satellite Phone
>(with apologies to Jonathan 'Buggles' King)

Nice one!

Now can anyone put it together for the next IETF meeting plenary :-)

(An excellent rendition of "My favourite [net] things" was used to intro 
the plenary session in Washington DC last November.)

#g

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound  Mon Apr 17 12:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA05830
	for ietf-outbound.10@ietf.org; Mon, 17 Apr 2000 12:50:02 -0400 (EDT)
Received: from ns2.microwavenetworks.com (ns2.microwavenetworks.com [209.44.144.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05791
	for <ietf@ietf.org>; Mon, 17 Apr 2000 12:47:23 -0400 (EDT)
Received: from mercury.mns (exchmail [172.16.11.6])
	by ns2.microwavenetworks.com (8.9.3/8.9.3) with ESMTP id LAA24950
	for <ietf@ietf.org>; Mon, 17 Apr 2000 11:47:23 -0500
Received: by MERCURY with Internet Mail Service (5.0.1460.8)
	id <CDGQ8GFL>; Mon, 17 Apr 2000 11:45:09 -0500
Message-ID: <CC96542306D7D2119E0B080009EB58FE9582AD@MERCURY>
From: Timothy Behne <TimothyB@microwavenetworks.com>
To: ietf@ietf.org
Subject: Mixed-topology solutions
Date: Mon, 17 Apr 2000 11:45:08 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1460.8)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org


Can anyone help point me in the direction of an RFC, draft, or other
information that might be helpful in sending Ethernet data across a
slower-speed media (such as in a remote bridge implementation)?  For
instance, sending 100 BaseT Ethernet data across a DS3 link.

Thanks in advance,

Tim Behne
Tadiran Microwave Networks



From owner-ietf-outbound  Mon Apr 17 13:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA06252
	for ietf-outbound.10@ietf.org; Mon, 17 Apr 2000 13:20:03 -0400 (EDT)
Received: from mail.nbn.net (root@nbn.net [207.51.86.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06167
	for <ietf@ietf.org>; Mon, 17 Apr 2000 13:15:51 -0400 (EDT)
Received: from server-1 (dial1-43.nbn.net [208.139.67.37])
	by mail.nbn.net (8.9.3/8.9.3) with SMTP id NAA16254
	for <ietf@ietf.org>; Mon, 17 Apr 2000 13:15:47 -0400
Message-ID: <38FB48E9.46D5@nbn.net>
Date: Mon, 17 Apr 2000 13:24:57 -0400
From: Betsy Brennan <bbrennan@nbn.net>
Reply-To: bbrennan@nbn.net
X-Mailer: Mozilla 3.04 (Win95; U)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: vLANs vs VPNs
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Could anyone explain to me the difference between Virtual Privite
networks and Virtual LANs?   Respectfully, Betsy B.



From owner-ietf-outbound  Mon Apr 17 13:40:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA06563
	for ietf-outbound.10@ietf.org; Mon, 17 Apr 2000 13:40:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06348
	for <ietf@ietf.org>; Mon, 17 Apr 2000 13:26:09 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA06119;
	Mon, 17 Apr 2000 10:26:05 -0700 (PDT)
Message-ID: <38FB492B.D6256DD@isi.edu>
Date: Mon, 17 Apr 2000 10:26:03 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Fred Baker <fred@cisco.com>, "Derrell D. Piper" <ddp@Network-Alchemy.COM>,
        ietf@ietf.org
Subject: Re: recommendation against publication of draft-cerpa-necp-02.txt
References: <200004171520.LAA29149@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Keith Moore wrote:
> 
> I think various people have made a good case for eventually publishing
> this particular document, once appropriate revisions have been made.
> 
> I'm very supportive of the notion of free exchange of ideas, even
> through the RFC mechanism - with the understanding that:
> 
> - IETF and the RFC Editor have limited resources and cannot publish
>   everything that comes their way
> - it's inappropriate to use Experimental or Informational publications in
>   the RFC series to promote or claim legitimacy for ideas that are embroynic
>   or experimental in nature, especially when those ideas are violations of
>   Internet standards.  there should be a clear distinction between
>   "this is somebody's idea for an experiment" and "this is the sense
>   of the Internet technical community"
> - some experiments are better carried out under controlled conditions.

I'm in favor of the free exchange of ideas, with the caveat that
breaking existing standards or proposed standards must be addressed
prior to publication.

It is common for the RFC Editor to require augmentation of a proposed
informational RFC prior to publication. E.g., when the Security Issues
section has not been sufficiently developed.

There may be utility in considering a uniform "Standards Issues"
section. Just as the Security Issues must be sufficiently addressed when
an RFC affects or compromises security, the Standards Issues would be
necessary when an RFC affects or compromises current (STANDARD) or
'proposed' (DRAFT STANDARD, PROPOSED STANDARD) Internet standards.

The Standards Issues section could be required even if the RFC is
informational or experimental, as in the case of Security Issues. In
fact, I would prefer if it were always required, as in Sec Iss, even if
stating "this system is conformant with and does not affect any Internet
STANDARD, DRAFT STANDARD, or PROPOSED STANDARD as of this writing."

(e.g., as an update to RFC 2223)

Joe



From owner-ietf-outbound  Mon Apr 17 15:20:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA08046
	for ietf-outbound.10@ietf.org; Mon, 17 Apr 2000 15:20:02 -0400 (EDT)
Received: from escape.com (xelsed@escape.com [198.6.71.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07983
	for <ietf@ietf.org>; Mon, 17 Apr 2000 15:16:57 -0400 (EDT)
Received: from localhost (xelsed@localhost) by escape.com (8.9.0/8.9.1) with ESMTP id PAA27130; Mon, 17 Apr 2000 15:19:45 -0400 (EDT)
Date: Mon, 17 Apr 2000 15:19:45 -0400 (EDT)
From: Jeremy <xelsed@escape.com>
To: Betsy Brennan <bbrennan@nbn.net>
cc: ietf@ietf.org
Subject: Re: vLANs vs VPNs
In-Reply-To: <38FB48E9.46D5@nbn.net>
Message-ID: <Pine.BSI.4.21.0004171518360.25874-100000@escape.com>
Disposition-Notification-To: Jeremy Deutsch <xelsed@escape.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

one is a way of securly talking across o public network, the other is a
way of logically seprating traffic, accross the same physical media, or
equipment.

-jeremy


On Mon, 17 Apr 2000, Betsy Brennan wrote:

> Could anyone explain to me the difference between Virtual Privite
> networks and Virtual LANs?   Respectfully, Betsy B.
> 
> 



From owner-ietf-outbound  Mon Apr 17 16:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA09401
	for ietf-outbound.10@ietf.org; Mon, 17 Apr 2000 16:40:02 -0400 (EDT)
Received: from fw-ra06.raytheon.com (fw-ra06.RAYTHEON.COM [192.27.4.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09323
	for <ietf@ietf.org>; Mon, 17 Apr 2000 16:32:30 -0400 (EDT)
Received: from isra02.rsc.raytheon.com (isra02.rsc.raytheon.com [147.19.2.15])
	by fw-ra06.raytheon.com (8.9.1/8.9.1) with ESMTP id NAA29720
	for <ietf@ietf.org>; Mon, 17 Apr 2000 13:32:24 -0700 (PDT)
Received: from electra.rsc.raytheon.com (mail@electra.RSC.RAYTHEON.COM [147.19.52.42])
	by isra02.rsc.raytheon.com (8.9.1/8.9.1) with ESMTP id NAA01150
	for <ietf@ietf.org>; Mon, 17 Apr 2000 13:32:31 -0700 (PDT)
Received: from (ZFUAA373715) [147.19.54.44] 
	by electra.rsc.raytheon.com with smtp (Exim 2.05 #1 (Debian))
	id 12hIC7-0001gy-00; Mon, 17 Apr 2000 13:32:31 -0700
Received: by localhost with Microsoft MAPI; Mon, 17 Apr 2000 13:32:29 -0700
Message-ID: <01BFA871.60A1CAD0.rascheri@electra.rsc.raytheon.com>
From: "Richard C. Ascheri" <rascheri@electra.rsc.raytheon.com>
Reply-To: "rascheri@electra.rsc.raytheon.com"
	 <rascheri@electra.rsc.raytheon.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Digital Radio Configuration Question
Date: Mon, 17 Apr 2000 13:32:28 -0700
Organization: Raytheon
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Encoding: 54 TEXT
X-Loop: ietf@ietf.org


Hello,

I'm a Systems Engineer at Raytheon Company.  I have been working on the 
development of a digital IP based radio for some time now.  The radio has 
an Ethernet interface, PPP interface, and an ADDSI X.25 interface.

My question relates to the configuration of the radio.  To configure the 
radio we have an implementation of SNMPv2.  This implementation allows the 
radio to be configured over the Ethernet or PPP interfaces using the SNMPv2 
protocol.

My question relates to configuring the radio without knowing it's IP 
address.  I understand that SNMP requires the IP address of the device you 
want to configure.

I am interested in a standard method of announcing the IP address of the 
Ethernet interface.  This would allow a configuration tool to look for the 
announcements and then send SNMP configuration messages to modify the 
radios configuration.  For this scenario you can assume that the radio will 
be attached to a single host over an Ethernet interface.  There will be no 
other hosts or radios on the network.  Assume that the IP address of the 
radio is NOT known.  It could be set to anything, even an address outside 
of the range of the hosts subnet.

I have looked at a number of RFC's but have found these two that may work:

RFC 1256 - ICMP Router Discovery.  This rfc does announce the IP address, 
however, for this scenario I'm not interested in saying that this radio is 
the next hop gateway.  Given that the radio has numerous interfaces and an 
TCP/IP stack you might consider this a router.  However, I don't really 
feel that this RFC directly relates to solving the configuration problem. 
 The host is not really looking for it's next hop gateway.  It's looking 
for devices that can be configured through SNMP.

RFC 2608 - Service Location Protocol v2.  This rfc does imply that I could 
create a "Configuration-Service" and announce its availability using the 
SNMP protocol.  This actually sounds like the right kind of solution to my 
problem.

But now I'm wondering whether or not there is something else that I haven't 
found.  Maybe something in the works, as a draft, or a working group that 
is responsible for looking at these kinds of problems.

Any and all comments would be gratefully appreciated.

Thanks in advance.
Rick.

Richard C. Ascheri					Raytheon Company
Principle Systems Engineer				1801 Hughes Drive
Network Technology Group				Fullerton, CA.  92836
C3I Systems					http://www.raytheon.com
rascheri@electra.rsc.raytheon.com



From owner-ietf-outbound  Mon Apr 17 16:50:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA09641
	for ietf-outbound.10@ietf.org; Mon, 17 Apr 2000 16:50:02 -0400 (EDT)
Received: from fw-ra06.raytheon.com (fw-ra06.RAYTHEON.COM [192.27.4.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09370
	for <ietf@ietf.org>; Mon, 17 Apr 2000 16:35:45 -0400 (EDT)
Received: from isra02.rsc.raytheon.com (isra02.rsc.raytheon.com [147.19.2.15])
	by fw-ra06.raytheon.com (8.9.1/8.9.1) with ESMTP id NAA00420
	for <ietf@ietf.org>; Mon, 17 Apr 2000 13:35:39 -0700 (PDT)
Received: from electra.rsc.raytheon.com (mail@electra.RSC.RAYTHEON.COM [147.19.52.42])
	by isra02.rsc.raytheon.com (8.9.1/8.9.1) with ESMTP id NAA01333
	for <ietf@ietf.org>; Mon, 17 Apr 2000 13:35:46 -0700 (PDT)
Received: from (ZFUAA373715) [147.19.54.44] 
	by electra.rsc.raytheon.com with smtp (Exim 2.05 #1 (Debian))
	id 12hIFG-0001hs-00; Mon, 17 Apr 2000 13:35:46 -0700
Received: by localhost with Microsoft MAPI; Mon, 17 Apr 2000 13:35:44 -0700
Message-ID: <01BFA871.D4A3F930.rascheri@electra.rsc.raytheon.com>
From: "Richard C. Ascheri" <rascheri@electra.rsc.raytheon.com>
Reply-To: "rascheri@electra.rsc.raytheon.com"
	 <rascheri@electra.rsc.raytheon.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Digital Radio Configuration Question
Date: Mon, 17 Apr 2000 13:35:43 -0700
Organization: Raytheon
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Encoding: 54 TEXT
X-Loop: ietf@ietf.org


Hello,

I'm a Systems Engineer at Raytheon Company.  I have been working on the 
development of a digital IP based radio for some time now.  The radio has 
an Ethernet interface, PPP interface, and an ADDSI X.25 interface.

My question relates to the configuration of the radio.  To configure the 
radio we have an implementation of SNMPv2.  This implementation allows the 
radio to be configured over the Ethernet or PPP interfaces using the SNMPv2 
protocol.

My question relates to configuring the radio without knowing it's IP 
address.  I understand that SNMP requires the IP address of the device you 
want to configure.

I am interested in a standard method of announcing the IP address of the 
Ethernet interface.  This would allow a configuration tool to look for the 
announcements and then send SNMP configuration messages to modify the 
radios configuration.  For this scenario you can assume that the radio will 
be attached to a single host over an Ethernet interface.  There will be no 
other hosts or radios on the network.  Assume that the IP address of the 
radio is NOT known.  It could be set to anything, even an address outside 
of the range of the hosts subnet.

I have looked at a number of RFC's but have found these two that may work:

RFC 1256 - ICMP Router Discovery.  This rfc does announce the IP address, 
however, for this scenario I'm not interested in saying that this radio is 
the next hop gateway.  Given that the radio has numerous interfaces and an 
TCP/IP stack you might consider this a router.  However, I don't really 
feel that this RFC directly relates to solving the configuration problem. 
 The host is not really looking for it's next hop gateway.  It's looking 
for devices that can be configured through SNMP.

RFC 2608 - Service Location Protocol v2.  This rfc does imply that I could 
create a "Configuration-Service" and announce its availability using the 
SNMP protocol.  This actually sounds like the right kind of solution to my 
problem.

But now I'm wondering whether or not there is something else that I haven't 
found.  Maybe something in the works, as a draft, or a working group that 
is responsible for looking at these kinds of problems.

Any and all comments would be gratefully appreciated.

Thanks in advance.
Rick.

Richard C. Ascheri					Raytheon Company
Principle Systems Engineer				1801 Hughes Drive
Network Technology Group				Fullerton, CA.  92836
C3I Systems					http://www.raytheon.com
rascheri@electra.rsc.raytheon.com



From owner-ietf-outbound  Mon Apr 17 18:50:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA11079
	for ietf-outbound.10@ietf.org; Mon, 17 Apr 2000 18:50:01 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10991
	for <ietf@ietf.org>; Mon, 17 Apr 2000 18:43:51 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA20733;
	Mon, 17 Apr 2000 15:43:45 -0700 (PDT)
Message-ID: <38FB939F.938B7048@isi.edu>
Date: Mon, 17 Apr 2000 15:43:43 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
CC: Keith Moore <moore@cs.utk.edu>, Vernon Schryver <vjs@CALCITE.RHYOLITE.COM>,
        ietf@ietf.org
Subject: Re: interception proxies
References: <Roam.SIMC.2.0.6.955772399.589.nordmark@jurassic>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Erik Nordmark wrote:
> 
> > A copy of the note, admittedly very rough (just an outline, and a very
> > rough one at that) is at:
> >
> >       http://www.isi.edu/touch/pubs/hazards-outline.txt
> 
> This doesn't list what I thought was an obvious issue.
> If multiple nodes are originating packets with the same source
> IP address it will be rather hard for them to ensure the required
> uniqueness on the IP ID field (unique for the combination
> of source IP, destination IP and protocol).
> 
> I suspect that most of boxes that play these games don't worry about
> IP ID which might cause garbage reassembly should the same
> IP ID be used when multiple such boxes are sending to the same IP address.


Good point.

I suspect they ignore the issue because of how they demux to multiple
boxes;
if the demux is by a hash of source IP address, then there's no need for
coordination thereafter.

I'll certainly add that to the list. There's a corrolary at the TCP
level, of port reuse, etc.

Thanks,

Joe



From owner-ietf-outbound  Tue Apr 18 11:10:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA05920
	for ietf-outbound.10@ietf.org; Tue, 18 Apr 2000 11:10:01 -0400 (EDT)
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05884
	for <ietf@ietf.org>; Tue, 18 Apr 2000 11:06:47 -0400 (EDT)
Received: from malisa2 ([152.148.90.98])
	by alpo.casc.com (8.9.1a/8.9.1) with ESMTP id LAA21522;
	Tue, 18 Apr 2000 11:05:45 -0400 (EDT)
Message-Id: <4.2.2.20000418104343.027f0e00@alpo.casc.com>
X-Sender: amalis@alpo.casc.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 18 Apr 2000 11:04:30 -0400
To: Timothy Behne <TimothyB@microwavenetworks.com>
From: "Andrew G. Malis" <amalis@lucent.com>
Subject: Re: Mixed-topology solutions
Cc: ietf@ietf.org
In-Reply-To: <CC96542306D7D2119E0B080009EB58FE9582AD@MERCURY>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Tim,

Remote bridging over Frame Relay networks is specified in RFC 2427, and 
over PPP by RFC 1638.  RFC 1638 also contains a good introduction to remote 
bridging in general.  You should probably also check out IEEE 802.1D (aka 
ISO/IEC 15802-3) and 802.1G (aka ISO/IEC 15802-5).  The latter two need to 
be downloaded from the IEEE (see http://standards.ieee.org/).

Cheers,
Andy

-------

At 11:45 AM 4/17/00 -0500, Timothy Behne wrote:

>Can anyone help point me in the direction of an RFC, draft, or other
>information that might be helpful in sending Ethernet data across a
>slower-speed media (such as in a remote bridge implementation)?  For
>instance, sending 100 BaseT Ethernet data across a DS3 link.
>
>Thanks in advance,
>
>Tim Behne
>Tadiran Microwave Networks
>
>-
>This message was passed through ietf+censored@alvestrand.no, which
>is a sublist of ietf@ietf.org. Not all messages are passed.
>Decisions on what to pass are made solely by Harald Alvestrand.

________________________________________________________________________
Andrew G. Malis  amalis@lucent.com  phone:978 952-7414  fax:978 392-2074
Lucent Technologies                 1 Robbins Road    Westford, MA 01886



From owner-ietf-outbound  Tue Apr 18 12:10:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA07153
	for ietf-outbound.10@ietf.org; Tue, 18 Apr 2000 12:10:02 -0400 (EDT)
Received: from corpmail.galaxyscientific.com ([38.221.233.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06996
	for <ietf@ietf.org>; Tue, 18 Apr 2000 12:04:46 -0400 (EDT)
Received: from BELLOPEM (igate.tc.faa.gov [155.178.180.5]) by corpmail.galaxyscientific.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id 2KDCMZ8Q; Tue, 18 Apr 2000 12:03:18 -0400
From: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
To: "Betsy Brennan" <bbrennan@nbn.net>, <ietf@ietf.org>
Subject: RE: vLANs vs VPNs
Date: Tue, 18 Apr 2000 12:02:55 -0400
Message-ID: <PPECLLOGBEPHLOMKLNAMCELCCAAA.Michael.CTR.Bellopede@tc.faa.gov>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <9315@tc.faa.gov>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Virtual Private Network (VPN) and a Virtual LAN (VLAN) are two unrelated
terms.

VPN deals with security and connecting nodes in a private network across a
public IP internetwork.  Read RFC 1853 - IP Tunneling.

You can take one physical LAN and split it into multiple virtual LANs, or
you can take  multiple physical LANs and integrate them into a VLAN.  RFC
0824 is good reading.

Michael B. Bellopede

-----Original Message-----
From: Betsy Brennan [mailto:bbrennan@nbn.net]
Sent: Monday, April 17, 2000 1:25 PM
To: ietf@ietf.org
Subject: vLANs vs VPNs


Could anyone explain to me the difference between Virtual Privite
networks and Virtual LANs?   Respectfully, Betsy B.




From owner-ietf-outbound  Tue Apr 18 15:00:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA10108
	for ietf-outbound.10@ietf.org; Tue, 18 Apr 2000 15:00:02 -0400 (EDT)
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10018
	for <ietf@ietf.org>; Tue, 18 Apr 2000 14:55:44 -0400 (EDT)
Received: from malisa2 ([152.148.90.98])
	by alpo.casc.com (8.9.1a/8.9.1) with ESMTP id OAA01177;
	Tue, 18 Apr 2000 14:54:14 -0400 (EDT)
Message-Id: <4.2.2.20000418145204.027d7420@alpo.casc.com>
X-Sender: amalis@alpo.casc.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 18 Apr 2000 14:54:11 -0400
To: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>,
        "Betsy Brennan" <bbrennan@nbn.net>
From: "Andrew G. Malis" <amalis@lucent.com>
Subject: RE: vLANs vs VPNs
Cc: ietf@ietf.org
In-Reply-To: <PPECLLOGBEPHLOMKLNAMCELCCAAA.Michael.CTR.Bellopede@tc.faa.
 gov>
References: <9315@tc.faa.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Michael and Betsy,

Also see RFC 2764.

Cheers,
Andy

-------

At 12:02 PM 4/18/00 -0400, Michael B. Bellopede wrote:
>Virtual Private Network (VPN) and a Virtual LAN (VLAN) are two unrelated
>terms.
>
>VPN deals with security and connecting nodes in a private network across a
>public IP internetwork.  Read RFC 1853 - IP Tunneling.
>
>You can take one physical LAN and split it into multiple virtual LANs, or
>you can take  multiple physical LANs and integrate them into a VLAN.  RFC
>0824 is good reading.
>
>Michael B. Bellopede
>
>-----Original Message-----
>From: Betsy Brennan [mailto:bbrennan@nbn.net]
>Sent: Monday, April 17, 2000 1:25 PM
>To: ietf@ietf.org
>Subject: vLANs vs VPNs
>
>
>Could anyone explain to me the difference between Virtual Privite
>networks and Virtual LANs?   Respectfully, Betsy B.

________________________________________________________________________
Andrew G. Malis  amalis@lucent.com  phone:978 952-7414  fax:978 392-2074
Lucent Technologies                 1 Robbins Road    Westford, MA 01886



From owner-ietf-outbound  Tue Apr 18 16:20:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA11474
	for ietf-outbound.10@ietf.org; Tue, 18 Apr 2000 16:20:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11374
	for <ietf@ietf.org>; Tue, 18 Apr 2000 16:12:35 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id NAA08357;
	Tue, 18 Apr 2000 13:11:21 -0700 (PDT)
Message-ID: <38FCC165.128F1626@isi.edu>
Date: Tue, 18 Apr 2000 13:11:17 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "Andrew G. Malis" <amalis@lucent.com>
CC: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>,
        Betsy Brennan <bbrennan@nbn.net>, ietf@ietf.org
Subject: Re: vLANs vs VPNs
References: <9315@tc.faa.gov> <4.2.2.20000418145204.027d7420@alpo.casc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



> At 12:02 PM 4/18/00 -0400, Michael B. Bellopede wrote:
> >Virtual Private Network (VPN) and a Virtual LAN (VLAN) are two unrelated
> >terms.
> >
> >VPN deals with security and connecting nodes in a private network across a
> >public IP internetwork.  Read RFC 1853 - IP Tunneling.

1853 is informational.

2003 is the standards-track update (though it isn't cross-linked,
because an standard implicitly updates an informational document :-)

Joe



From owner-ietf-outbound  Wed Apr 19 07:50:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA04075
	for ietf-outbound.10@ietf.org; Wed, 19 Apr 2000 07:50:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03902
	for <ietf@ietf.org>; Wed, 19 Apr 2000 07:41:55 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12hsri-000141-00; Wed, 19 Apr 2000 12:41:54 +0100
Date: Wed, 19 Apr 2000 12:41:51 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: L.Wood@eim.surrey.ac.uk
cc: ietf@ietf.org
Subject: Re: Sats vs plain UMTS
In-Reply-To: <Pine.GSO.4.21.0004171101500.189-100000@petra.ee.surrey.ac.uk>
Message-ID: <Pine.GSO.4.21.0004191233530.5736-100000@petra.ee.surrey.ac.uk>
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-Loop: ietf@ietf.org

On Mon, 17 Apr 2000, Lloyd Wood wrote:

> Harald, you're truly an inspiration.
> 
> 
> GSM killed the Satellite Phone
> (with apologies to Jonathan 'Buggles' King)

Sorry, that should be to Trevor 'Buggles/Yes/Frankie/ZTT' Horn.

L.

Invest? Don't do it!

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



From owner-ietf-outbound  Wed Apr 19 14:32:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA11355
	for ietf-outbound.10@ietf.org; Wed, 19 Apr 2000 14:30:02 -0400 (EDT)
Received: from exchsrv1.cosinecom.com (proxy5.cosinecom.com [208.248.148.134])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11306
	for <ietf@ietf.org>; Wed, 19 Apr 2000 14:25:27 -0400 (EDT)
Received: from cosinecom.com (PEORIA [192.168.121.213]) by exchsrv1.cosinecom.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id J1BB60BL; Wed, 19 Apr 2000 11:24:31 -0700
Message-ID: <38FDFA05.7D8820F2@cosinecom.com>
Date: Wed, 19 Apr 2000 11:25:09 -0700
From: Ravi Jonnadula <rjonnadula@cosinecom.com>
Organization: Cosine Communications
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
CC: rjonnadula@cosinecom.com
Subject: Stats for VLAN
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hi,

  Are there any proposed standard statistics for Vlan?

thanks,
Ravi



From owner-ietf-outbound  Wed Apr 19 16:20:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA13622
	for ietf-outbound.10@ietf.org; Wed, 19 Apr 2000 16:20:02 -0400 (EDT)
Received: from foxhound.cisco.com (foxhound.cisco.com [171.69.192.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13548
	for <ietf@ietf.org>; Wed, 19 Apr 2000 16:16:47 -0400 (EDT)
Received: (from kzm@localhost)
	by foxhound.cisco.com (8.8.8/2.5.1/Cisco List Logging/8.8.8) id NAA19748;
	Wed, 19 Apr 2000 13:16:14 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200004192016.NAA19748@foxhound.cisco.com>
Subject: Re: Stats for VLAN
To: rjonnadula@COSINECOM.COM (Ravi Jonnadula)
Date: Wed, 19 Apr 2000 13:16:14 -0700 (PDT)
Cc: ietf@ietf.org, rjonnadula@COSINECOM.COM
In-Reply-To: <38FDFA05.7D8820F2@cosinecom.com> from "Ravi Jonnadula" at Apr 19, 2000 11:25:09 AM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>   Are there any proposed standard statistics for Vlan?
 
See RFC 2674.

Keith.



From owner-ietf-outbound  Wed Apr 19 23:40:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA20644
	for ietf-outbound.10@ietf.org; Wed, 19 Apr 2000 23:40:03 -0400 (EDT)
Received: from kediri.webindonesia.com (kediri.webindonesia.com [207.106.122.14])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA20604
	for <ietf@ietf.org>; Wed, 19 Apr 2000 23:37:09 -0400 (EDT)
Received: (qmail 20135 invoked by uid 1003); 20 Apr 2000 03:37:11 -0000
Date: Wed, 19 Apr 2000 23:37:10 -0400
From: "Rahmat M. Samik-Ibrahim" <ibrahim@kediri.webindonesia.com>
To: ietf@ietf.org
Subject: Best Current DNS Pracitices and our dogfood
Message-ID: <20000419233710.A20036@kediri.webindonesia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95us
X-Loop: ietf@ietf.org

In regard of an engineer salary:
> all these oh so brilliant folk on the anti-cacheing crusade 
> should be sentenced to live in a significantly less privileged 
> country for a year, where dialup ppp costs per megabyte of 
> international traffic and an engineer's salary is $100-200 
> per month.  we are spoiled brats.

I know many fellows that even earn less than $100 :-(.

In regards of DNS:
> Non-authoritative answer:
> ietf.org        nameserver = ns.ietf.org
> ietf.org        nameserver = ns.CNRI.Reston.VA.US

> Authoritative answers can be found from:
> ns.ietf.org     internet address = 132.151.1.19
> ns.CNRI.Reston.VA.US    internet address = 132.151.1.1

> rfc2182 ignored, both servers on same backbone, probably 
> in same site.

This problem sounds very familiar. So, it also happen in
a more privileged country with high paid engineers? 
Ah, what a relief!

Anyway, I would like to know more about what the real best current
DNS practices are (no theory please!). Especially, on how do fellows
practicing RFC-2181 (Clarifications to the DNS Specification), RFC-2182 
(Selection and Operation of Secondary DNS Servers), dan RFC-2317 
(Classless IN-ADDR.ARPA delegation).

For example; how many run a periodic dnswalk; how to handle
lamers; where to keep the record of secondary contacts; 
is misusing CNAME a problem or not; how often it happen, 
the case where nobody remembers where the archive is; etc. 

Please send me comments and especially URLs.
I will add the summary at:

     http://rms46.vlsm.org/00-i-12.html

PS: 
- I was always wondering for what was the Source Address.
  Now, I have got clues! But, I am still wondering on
  why a 32 bit (or 128 bit) low level unique identifier is
  needed. Does it mean that the Klingons, Ferengis, and
  Vulcan have to renumber their advanced network if they
  join the FCANN (Federation Corporation for Assigned
  Names and Numbers)?

PPS:
- OK, it is 20 days too late, but try :-)

http://Ladies.and.Gentlemen.This.is.indeed.the.longest.domain.name.that.is.allowed.by.the.current.BIND.version.If.you.can.not.access.this.website--you.should.contact.your.proxy.administrator.Or.you.can.also.try.the.short.version.of.this.domain.ie.long.vlsm.org

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- You have to let me go, I just wanna tell you! - 5IVE INVINCIBLE -



From owner-ietf-outbound  Thu Apr 20 10:00:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA10707
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 10:00:02 -0400 (EDT)
Received: from watsun.cc.columbia.edu (IDENT:cu51491@watsun.cc.columbia.edu [128.59.39.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10664
	for <ietf@ietf.org>; Thu, 20 Apr 2000 09:59:29 -0400 (EDT)
Received: (from jaltman@localhost)
	by watsun.cc.columbia.edu (8.8.5/8.8.5) id JAA24415
	for ietf@ietf.org; Thu, 20 Apr 2000 09:59:29 -0400 (EDT)
Date: Thu, 20 Apr 2000 9:59:29 EDT
From: Jeffrey Altman <jaltman@columbia.edu>
Reply-To: jaltman@columbia.edu
To: ietf@ietf.org
Subject: draft-ietf-nat-protocol-complications-02.txt
Message-ID: <CMM.0.90.4.956239169.jaltman@watsun.cc.columbia.edu>
X-Loop: ietf@ietf.org

This draft is very incomplete and in my opinion not ready for prime
time.  The working group has in the past requested lists of protocols
and applications which do not work with NATs.  I have replied
discussing those items for which I am most familiar:

  . Telnet (with AUTH, START_TLS, NEW-ENV, and XDISPLOC)

  . FTP (with AUTH and PROT)

  . RSH/RLOGIN/...

  . Kerberos 4

  . Kerberos 5

  . X Windows

None of the information provided in a response to this request by me
is in this document.  The protocols and applications listed above are
hardly unknown in the IETF community so it strikes me as intriguing
that these well known applications would be left out of a document 
that is supposed to document how few problems are caused by NATs.

Telnet:

Transmits IP addresses from the client to the server for the purposes
of setting the DISPLAY variable.  When set the DISPLAY variable is 
used for subsequent connections from X clients on the host to an
X server on the workstation.

When AUTH is used with Kerberos 4 and Kerberos 5 there are issues
related to the IP addresses which are embedded into the Kerberos 
tickets which specify the valid machines from which the tickets are 
valid.

When START_TLS is used there may be client certificate verification
problems caused by the NAT depending on the information provided in
the certificate.

FTP:

As stated FTP, uses multiple sessions.  But what it fails to state
is that if any form of PROT is used to secure the command channel
then it is impossible to implement an ALG to perform IP Address swaps.

When AUTH is used with Kerberos 4, Kerberos 5, and TLS the same
problems that occur with Telnet occur with FTP.

RSH/RLOGIN:

RSH uses multiple sessions to support separate streams for stdout and 
stderr.  The stderr socket is a connection from the server to the
client.  And unlike FTP, there is no equivalent to PASV mode.

RLOGIN does not use multiple sessions.

But the Kerberos protoected versions of RSH and RLOGIN will not work 
in a NAT environment due to the ticket problems and the use of
multiple sessions.

Kerberos 4:

Kerberos 4 tickets are encrypted.  Therefore, an ALG cannot be
written.  The K4 ticket contains a single IP address describing the
interface used by the client to retrieve the ticket from the TGT from
the perspective of the KDC.  If the KDC and all services are on the 
far side of the NAT, the end user will not notice any problems.  But
the ticket will be valid from any IP address inside the NAT (on the 
private network.)  Without a NAT, an attacker needs to be able to 
spoof the source IP addresses of a connection that is being made in
order to use a stolen ticket on a different host.    With a NAT, all 
the attacker needs to do from the near side of the NAT is to simply 
gain possession of a ticket.  

Kerberos 5:

Kerberos 5 tickets are encrypted.  Therefore, an ALG cannot be
written.  The K5 ticket contains a list of IP addresses from which
the ticket is to be considered valid.  The list is generated by the
client machine, not the KDC.  If the services being accessed with
Kerberos authentication are on the public side of the NAT, then 
the Kerberos authentication will fail because the IP address used
by the NAT is not in the list of acceptable addresses.

There are two workarounds in Kerberos 5 both of which reduce the 
security of the tickets.  The first is to have the clients specify 
the public IP address of the NAT in the ticket's IP list.  But this
leads to the same security problem detailed for K4.  Plus, how is
the client supposed to find out what the public IP Address of the NAT
is from the private side?

The second method is to remove all IP addresses from the K5 tickets
but this now makes theft of the ticket even worse since the tickets 
can be used from anywhere.  Not just from within the private network.

X Windows:

There are two problems in the X world.  First, the X clients which are
in the public space need to make connections to the X Server which is
in the private space.  The IP address to which the connections are to
be made is specified by the DISPLAY environment variable which is 
set by the client in some way.    The NAT would have to have an ALG
to replace the IP address and configure a port in the valid display
range (ports 6000 and higher) to act as a gateway.  

But if the NAT listens for incoming connections then it may well 
increase the security risk by providing access to the X server that
would not otherwise be available.  Since the NATs tamper with the
IP addresses it will also not be possible for X Authorization methods
other than MIT-MAGIC-COOKIE-1 to be used.  MIT-MAGIC-COOKIE-1 is the
least secure of all the documented X Authorization methods.

-------

This small sampling of the types of information which are not provided
in this document is most likely just the tip of the iceberg.  I
recommend that this document not be published in its current form due
to the overwhelming impression that is given to the reader that there
are no significant problems with NATs.  Plus the document clearly
mentions areas where further research is required where the necessary
research is not difficult to perform.



    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org




From owner-ietf-outbound  Thu Apr 20 12:30:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15008
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 12:30:05 -0400 (EDT)
Received: from mail.intrcomm.net ([209.173.220.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14887
	for <ietf@ietf.org>; Thu, 20 Apr 2000 12:25:08 -0400 (EDT)
Received: from workstation02 ([12.31.137.1])
	by mail.intrcomm.net (8.9.3/8.9.3) with SMTP id LAA10428
	for <ietf@ietf.org>; Thu, 20 Apr 2000 11:25:02 -0500
Reply-To: <gregg@automationtechies.com>
From: "Gregg Peterson" <gregg@automationtechies.com>
To: <ietf@ietf.org>
Subject: automationtechies.com
Date: Thu, 20 Apr 2000 11:24:18 -0500
Message-ID: <NDBBJGLKLKLOGOKELNONAEPECIAA.gregg@automationtechies.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

EXPAND THE REACH OF YOUR RECRUITING EFFORTS

www.automationtechies.com is a job postings website with an exclusive focus
on the automation and controls industry. It is designed to expand the reach
of your recruiting efforts by directly connecting your company with
established controls and automation professionals.

We market our site only to the professionals who work in automation and
controls.  This reduces the number of non-qualified iquiries you will
receive.  Our current Employer Members are providing us with fantastic
feedback.  With our Techie-Membership growing by 20-30 per day, this
satisfaction will also continue to grow.

Our site is perfect for manfacturers in this industry as we provide
advertising options as well as access to qualified job candidates.

We are currently running a 40 percent discount for sixty day job postings,
with further discounts for multiple listings. If you would like to take
advantage of this discounted offer please call our toll free number at
#877.300.6792, or :

Go to:
www.automationtechies.com

Click on: Employers
Register as a New Employer
You will receive an e-mail with your Username and Password
You may then: Purchase Job Postings
Edit your Job Postings
Request them to be activated

If you have any questions, feel free to contact us:


Gregg Peterson
gregg@automationtechies.com
877.300.6792



From owner-ietf-outbound  Thu Apr 20 12:40:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15347
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 12:40:03 -0400 (EDT)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14967
	for <ietf@ietf.org>; Thu, 20 Apr 2000 12:29:22 -0400 (EDT)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id JAA27612;
	Thu, 20 Apr 2000 09:22:33 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 20 Apr 2000 16:29:17 UT
Received: from porky (porky.ascend.com [192.207.23.83])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id JAA05846;
	Thu, 20 Apr 2000 09:29:17 -0700 (PDT)
Received: from ascend.com by ascend.com
Message-Id: <4.3.1.2.20000420092212.00b84470@porky>
X-Sender: mhold@porky
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Thu, 20 Apr 2000 09:25:39 -0700
To: jaltman@columbia.edu
From: Matt Holdrege <holdrege@lucent.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
In-Reply-To: <CMM.0.90.4.956239169.jaltman@watsun.cc.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 09:59 AM 4/20/00 -0400, Jeffrey Altman wrote:
>This draft is very incomplete and in my opinion not ready for prime
>time.  The working group has in the past requested lists of protocols
>and applications which do not work with NATs.  I have replied
>discussing those items for which I am most familiar:

[...snipped]

I think everyone agrees that the draft is incomplete. I've been begging for 
input for over a year now in the NAT WG meetings and on the NAT list. I've 
also asked every IETF WG chair for input. Our hope is that through IETF 
last call, we will get enough contributions such as yours to get a 
reasonable document together that folks can reference.

Thanks for your help.

-Matt Holdrege



From owner-ietf-outbound  Thu Apr 20 12:50:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15600
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 12:50:01 -0400 (EDT)
Received: from watsun.cc.columbia.edu (IDENT:cu51491@watsun.cc.columbia.edu [128.59.39.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15307
	for <ietf@ietf.org>; Thu, 20 Apr 2000 12:39:09 -0400 (EDT)
Received: (from jaltman@localhost)
	by watsun.cc.columbia.edu (8.8.5/8.8.5) id MAA23514;
	Thu, 20 Apr 2000 12:39:08 -0400 (EDT)
Date: Thu, 20 Apr 2000 12:39:08 EDT
From: Jeffrey Altman <jaltman@columbia.edu>
Reply-To: jaltman@columbia.edu
To: Matt Holdrege <holdrege@lucent.com>
Cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: Your message of Thu, 20 Apr 2000 09:25:39 -0700
Message-ID: <CMM.0.90.4.956248748.jaltman@watsun.cc.columbia.edu>
X-Loop: ietf@ietf.org

> At 09:59 AM 4/20/00 -0400, Jeffrey Altman wrote:
> >This draft is very incomplete and in my opinion not ready for prime
> >time.  The working group has in the past requested lists of protocols
> >and applications which do not work with NATs.  I have replied
> >discussing those items for which I am most familiar:
> 
> [...snipped]
> 
> I think everyone agrees that the draft is incomplete. I've been begging for 
> input for over a year now in the NAT WG meetings and on the NAT list. I've 
> also asked every IETF WG chair for input. Our hope is that through IETF 
> last call, we will get enough contributions such as yours to get a 
> reasonable document together that folks can reference.

I am not on the NAT mailing list; nor do I attend NAT working group
meetings.  I consider NATs to be architecturally unsound and that the
IETF and IESG should in no way endorse their use or development.

All of the energy and money being spent on NATs could and should be
spent to begin the migration to IPv6 instead.  It is my hope now that
Windows 2000 supports IPSec that enough pressure will be applied to
halt the deployment of NATs



    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org




From owner-ietf-outbound  Thu Apr 20 13:00:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA15983
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 13:00:02 -0400 (EDT)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15791
	for <ietf@ietf.org>; Thu, 20 Apr 2000 12:54:46 -0400 (EDT)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id JAA00266;
	Thu, 20 Apr 2000 09:48:01 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 20 Apr 2000 16:54:44 UT
Received: from porky (porky.ascend.com [192.207.23.83])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id JAA17981;
	Thu, 20 Apr 2000 09:54:44 -0700 (PDT)
Received: from ascend.com by ascend.com
Message-Id: <4.3.1.2.20000420095132.00bff510@porky>
X-Sender: mhold@porky
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Thu, 20 Apr 2000 09:55:55 -0700
To: jaltman@columbia.edu
From: Matt Holdrege <holdrege@lucent.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
In-Reply-To: <CMM.0.90.4.956248748.jaltman@watsun.cc.columbia.edu>
References: <Your message of Thu, 20 Apr 2000 09:25:39 -0700>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 12:39 PM 4/20/00 -0400, Jeffrey Altman wrote:
> > At 09:59 AM 4/20/00 -0400, Jeffrey Altman wrote:
> > >This draft is very incomplete and in my opinion not ready for prime
> > >time.  The working group has in the past requested lists of protocols
> > >and applications which do not work with NATs.  I have replied
> > >discussing those items for which I am most familiar:
> >
> > [...snipped]
> >
> > I think everyone agrees that the draft is incomplete. I've been begging 
> for
> > input for over a year now in the NAT WG meetings and on the NAT list. I've
> > also asked every IETF WG chair for input. Our hope is that through IETF
> > last call, we will get enough contributions such as yours to get a
> > reasonable document together that folks can reference.
>
>I am not on the NAT mailing list; nor do I attend NAT working group
>meetings.  I consider NATs to be architecturally unsound and that the
>IETF and IESG should in no way endorse their use or development.

Just so there is no more confusion, in no way is the IETF endorsing the use 
or development of NAT. You've completely missed the point of the draft. 
It's purpose is to clearly point out the problems that NAT causes to a 
given set of protocols.

Also please do not steer this thread towards a NAT bashing-fest. We need to 
complete this document and we need constructive input to this draft. Thanks 
again for your original input.



From owner-ietf-outbound  Thu Apr 20 13:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA16574
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 13:30:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16551
	for <ietf@ietf.org>; Thu, 20 Apr 2000 13:29:42 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id LAA26345
	for ietf@ietf.org  env-from <vjs>;
	Thu, 20 Apr 2000 11:29:42 -0600 (MDT)
Date: Thu, 20 Apr 2000 11:29:42 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004201729.LAA26345@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
X-Loop: ietf@ietf.org

> From: Matt Holdrege <holdrege@lucent.com>

> ...
> Just so there is no more confusion, in no way is the IETF endorsing the use 
> or development of NAT. You've completely missed the point of the draft. 
> It's purpose is to clearly point out the problems that NAT causes to a 
> given set of protocols.
>
> Also please do not steer this thread towards a NAT bashing-fest. We need to 
> complete this document and we need constructive input to this draft. Thanks 
> again for your original input.


If the document is not intended to be read as advocating NAT, it also
needs substantial non-technical changes.  It currently comes across as
a list of fairly minor, generally easily fixed problems or problems that
don't matter.  I don't mean to say that is the intended point of the
document, but is how I read it.  Since I'm among those who feel that the
situation with NAT is not quite as bad things would have been if we had
waited for IPv6, you might expect my prejudices to make me read it the
other way.

Instead of appearing to be a complete list of problem and their complete
and easy solutions, the document needs to have more words in each section
saying that the sublist of problems is probably incomplete.  The
shortcomings of solutions to the problems should be belabored instead of
glossed over.  Seeing that the problems are significant must not require
any technical sophistication in the reader.  For example, most people who
should read this document will see nothing but some opaque acronyms
whose problems surely don't matter in Section 5.  Why should anyone care
that IPCEC doesn't work with NAT?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu Apr 20 13:40:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA16836
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 13:40:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16683
	for <ietf@ietf.org>; Thu, 20 Apr 2000 13:32:29 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id NAA22893;
	Thu, 20 Apr 2000 13:32:29 -0400
Date: Thu, 20 Apr 2000 13:32:29 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200004201732.NAA22893@ginger.lcs.mit.edu>
To: ietf@ietf.org, jaltman@COLUMBIA.EDU
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

    > From: Jeffrey Altman <jaltman@COLUMBIA.EDU>

    > All of the energy and money being spent on NATs could and should be
    > spent to begin the migration to IPv6 instead.

Oh, goody, another round of wasted time and energy arguing about IPv6 and NAT
boxes on the IETF list (triggered, as usual, by more pro-IPv6 propoganda from
desperate IPv6 proponents).

Definitely the most incisive summation of IPv6 I've seen recently was this
one:

    > IPv6 is like the DoD completing the design of a gigaton nuclear bomb in
    > the year 2000; everybody's thinking that it would've been cool to have
    > this in 1963, but who the hell wants to spend all the bucks on it 37
    > years late?

By the way, just out of interest, don't the tops of your knees get kind of
bruised every time to you see the word "NAT", or have you learned to scoot
back from your desk in time?

	Noel



From owner-ietf-outbound  Thu Apr 20 14:00:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA17336
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 14:00:03 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17114
	for <ietf@ietf.org>; Thu, 20 Apr 2000 13:56:28 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id MAA06261
	for <ietf@ietf.org>; Thu, 20 Apr 2000 12:55:20 -0500 (CDT)
Message-Id: <200004201755.MAA06261@rgfsparc.cr.usgs.gov>
Date: Thu, 20 Apr 2000 12:55:20 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: u7mi22Y6dohiQH25sHqZSw==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>By the way, just out of interest, don't the tops of your knees get kind of
>bruised every time to you see the word "NAT", or have you learned to scoot
>back from your desk in time?

Looks to me like knees are getting bruised all around.

RGF

Robert G. Ferrell, CISSP
Information Systems Security Officer
National Business Center, US DoI
Robert_G_Ferrell@nbc.gov
------------------------------------------------------------
Nothing I have ever said should be construed as even vaguely
representing an official statement by the NBC or DoI.
------------------------------------------------------------



From owner-ietf-outbound  Thu Apr 20 14:10:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA17672
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 14:10:03 -0400 (EDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17595
	for <ietf@ietf.org>; Thu, 20 Apr 2000 14:07:23 -0400 (EDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id TAA73804 for <ietf@ietf.org>; Thu, 20 Apr 2000 19:06:44 +0100
Received: from hursley.ibm.com (gsine03.us.sine.ibm.com [9.14.6.43]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id TAA18052 for <ietf@ietf.org>; Thu, 20 Apr 2000 19:06:44 +0100 (BST)
Message-ID: <38FF473C.40DF385E@hursley.ibm.com>
Date: Thu, 20 Apr 2000 13:06:52 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Reply-To: listadm@ietf.org
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: ietf@ietf.org
Subject: To diffserv list members only
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Sorry to spam the IETF list with this but I don't know a better way.

An unknown number of people have either been mysteriously dropped from
the diffserv@ietf.org list, or had their mail delivery from this list
mysteriously suspended. If you haven't seen any mail at all from the diffserv
list for a few days, please access
http://www.ietf.org/mailman/listinfo/diffserv/ 
and enter the email address which you subscribed to diffserv
in the *last* box on that page to check your status.

And you might want change your password while you are there.

Support address: listadm@ietf.org . Please don't reply to this mail.

  Brian Carpenter
  diffserv co-chair



From owner-ietf-outbound  Thu Apr 20 15:20:40 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA19431
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 15:20:02 -0400 (EDT)
Received: from watsun.cc.columbia.edu (IDENT:cu51491@watsun.cc.columbia.edu [128.59.39.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19248
	for <ietf@ietf.org>; Thu, 20 Apr 2000 15:15:29 -0400 (EDT)
Received: (from jaltman@localhost)
	by watsun.cc.columbia.edu (8.8.5/8.8.5) id PAA24246;
	Thu, 20 Apr 2000 15:15:24 -0400 (EDT)
Date: Thu, 20 Apr 2000 15:15:24 EDT
From: Jeffrey Altman <jaltman@columbia.edu>
Reply-To: jaltman@columbia.edu
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: ietf@ietf.org, jnc@ginger.lcs.mit.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: Your message of Thu, 20 Apr 2000 13:32:29 -0400
Message-ID: <CMM.0.90.4.956258124.jaltman@watsun.cc.columbia.edu>
X-Loop: ietf@ietf.org

>     > From: Jeffrey Altman <jaltman@COLUMBIA.EDU>
> 
>     > All of the energy and money being spent on NATs could and should be
>     > spent to begin the migration to IPv6 instead.
> 
> Oh, goody, another round of wasted time and energy arguing about IPv6 and NAT
> boxes on the IETF list (triggered, as usual, by more pro-IPv6 propoganda from
> desperate IPv6 proponents).

Oh hardly.  I just don't the fact that ISP's are now forcing NATs on
customers unless customers can document a reason why they need more
than 1 IP address.  When NATs break so many existing protocols and
applications.  I am not a IPv6 proponent other than IPv6 provides the
extended address space that everyone needs without breaking the end to
end model of IP.



    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org




From owner-ietf-outbound  Thu Apr 20 15:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA19633
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 15:30:02 -0400 (EDT)
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19546
	for <ietf@ietf.org>; Thu, 20 Apr 2000 15:24:50 -0400 (EDT)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate2.mot.com (motgate2 2.1) with ESMTP id MAA11528 for <ietf@ietf.org>; Thu, 20 Apr 2000 12:24:49 -0700 (MST)]
Received: [from relay2.cig.mot.com (relay2.cig.mot.com [136.182.15.24]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id MAA16027 for <ietf@ietf.org>; Thu, 20 Apr 2000 12:24:48 -0700 (MST)]
Received: from Motorola.Com (dr05_239.il33.wes.mot.com [154.56.5.239]) by relay2.cig.mot.com (8.9.0/SCERG-RELAY-1.11b) with ESMTP id OAA26877 for <ietf@ietf.org>; Thu, 20 Apr 2000 14:17:59 -0500 (CDT)
Message-ID: <38FF553B.644687CC@Motorola.Com>
Date: Thu, 20 Apr 2000 14:06:35 -0500
From: Phil Neumiller <Phillip.Neumiller@Motorola.Com>
Organization: Personal Area Networking (PAN)
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: IP over Bluetooth, Cellular Handoff to WLAN
Content-Type: multipart/mixed;
 boundary="------------C1D94109D6AF48FD203DDCF1"
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.
--------------C1D94109D6AF48FD203DDCF1
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Folks,

Where(what is the mail list) is the discussion group for IP over Bluetooth?
I heard about the Pittsburgh BOF but I can't find a mail list.

Anybody interested in chatting about macro-cellular to WLAN/PAN handovers?

Thanks,

Phil
--------------C1D94109D6AF48FD203DDCF1
Content-Type: text/x-vcard; charset=us-ascii;
 name="Phillip.Neumiller.vcf"
Content-Description: Card for Phil Neumiller
Content-Disposition: attachment;
 filename="Phillip.Neumiller.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Neumiller;Phillip
tel;pager:1258338@skytel.com
tel;cell:iDen 847-9804238 / CDMA 847-370-3899
tel;home:847-516-2009
tel;work:847-632-4118 (will change)
x-mozilla-html:TRUE
org:Advanced Standards and Architecture;Personal Area Networking (PAN)
adr:;;;Schaumburg;IL;60195;USA
version:2.1
email;internet:Phillip.Neumiller@Motorola.com
title:Personal Networking Group (PNG)
fn:Phil Neumiller
end:vcard

--------------C1D94109D6AF48FD203DDCF1--



From owner-ietf-outbound  Thu Apr 20 15:40:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA19854
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 15:40:02 -0400 (EDT)
Received: from fwns2.raleigh.ibm.com (fwns2d.raleigh.ibm.com [204.146.167.236])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19825
	for <ietf@ietf.org>; Thu, 20 Apr 2000 15:39:33 -0400 (EDT)
Received: from rtpmail02.raleigh.ibm.com (rtpmail02.raleigh.ibm.com [9.37.172.48])
	by fwns2.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id PAA36768;
	Thu, 20 Apr 2000 15:38:50 -0400
Received: from ludwigia.raleigh.ibm.com (ludwigia.raleigh.ibm.com [9.37.60.3])
	by rtpmail02.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id PAA20978;
	Thu, 20 Apr 2000 15:38:50 -0400
Received: from ludwigia.raleigh.ibm.com (localhost [127.0.0.1]) by ludwigia.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id PAA14189; Thu, 20 Apr 2000 15:36:13 -0400
Message-Id: <200004201936.PAA14189@ludwigia.raleigh.ibm.com>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: ietf@ietf.org, jaltman@COLUMBIA.EDU
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-Reply-To: Message from "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu> 
   of "Thu, 20 Apr 2000 13:32:29 EDT." <200004201732.NAA22893@ginger.lcs.mit.edu> 
Date: Thu, 20 Apr 2000 15:36:13 -0400
From: Thomas Narten <narten@raleigh.ibm.com>
X-Loop: ietf@ietf.org

> Oh, goody, another round of wasted time and energy arguing about
> IPv6 and NAT boxes on the IETF list

So it seems. Too bad you couldn't just leave it at that without adding
another dose of gasoline to the mix.

Meanwhile, those of us who believe IPv6 is the best and most promising
way out of this mess will continue to work on actually making it
happen. Of course, if someone has a better idea, I'd surely love to
read the draft.

Thomas



From owner-ietf-outbound  Thu Apr 20 16:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA20239
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 16:00:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20198
	for <ietf@ietf.org>; Thu, 20 Apr 2000 15:58:38 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id PAA23389;
	Thu, 20 Apr 2000 15:58:39 -0400
Date: Thu, 20 Apr 2000 15:58:39 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200004201958.PAA23389@ginger.lcs.mit.edu>
To: ietf@ietf.org, jaltman@columbia.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

    > From: Jeffrey Altman <jaltman@columbia.edu>

    > I am not a IPv6 proponent other than

Well, I'm not exactly a big fan of NAT boxes either. Disgusting kludges.

However, I've generally found that it's not really very useful to go around
saying "it's not really raining, it's not really raining" while I'm walking
in a thunderstorm.....
                              
NAT's are with us, like them or not, and the sooner we accept it, and try to
start working to fix things up to work with them, the better...

(E.g. fixing IPSEC to work through them, to use one example mentioned here -
although some people would no doubt point to things like SSL, which already
work through NAT boxes, and ask why we need IPSEC anyway - but I'm *not* going
to get into that! :-)


    > the extended address space that everyone needs without breaking the end
    > to end model of IP.

Well, I think we can regain the "end-end model", even with NAT boxes, if we
accept that those 32-bit things are irrevocably destined to become just
forwarding tags with only local scope.

There's a need, and a place, for things with only local scope - e.g. the
network layer header in front of the internet header, the hop count in the
internet header, etc, etc. The IPv4 address will have to be added to that list
- and for things which need an end-end name, we'll have to migrate to using
something else.

This still leaves us with the architectural problem of having mapping state
in the border boxes (another impingement on the fatesharing principle - i.e.
that all state relevant to an end-end connection be kept only at the ends),
but that can be looked at. It's not like there's *no* state in the network,
without which the connection won't work - routing table entries may seem like
they're handed down on stone tablets, but they are critical state too.

Then there's how it's installed (wiretapping DNS - eccch, another disgusting
kludge); definitely need to do something better there.

But it will have to be an incremental approach back to goodness, I fear...

	Noel



From owner-ietf-outbound  Thu Apr 20 16:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA20483
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 16:10:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20452
	for <ietf@ietf.org>; Thu, 20 Apr 2000 16:09:33 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA10511;
        Thu, 20 Apr 2000 16:08:20 -0400 (EDT)
Message-Id: <200004202008.QAA10511@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Matt Holdrege <holdrege@lucent.com>
cc: jaltman@columbia.edu, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Thu, 20 Apr 2000 09:55:55 PDT."
             <4.3.1.2.20000420095132.00bff510@porky> 
Date: Thu, 20 Apr 2000 16:08:20 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Also please do not steer this thread towards a NAT bashing-fest. We need to 
> complete this document and we need constructive input to this draft.

unfortunately, the major premise of the draft is flawed.  there 
are far too many problems to NAT, affecting far too many applications, 
to make a usefully complete list of the applications that are affected.  
and the list is constantly growing larger.

finally, the notion that one can fix NAT's problems with ALGs is
not only incorrect, it's impractical for NATs to support even
the applications for which ALGs are feasible.

Keith



From owner-ietf-outbound  Thu Apr 20 17:11:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA21437
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 17:10:02 -0400 (EDT)
Received: from fepC.post.tele.dk (fepC.post.tele.dk [195.41.46.147])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21315
	for <ietf@ietf.org>; Thu, 20 Apr 2000 17:02:03 -0400 (EDT)
Received: from Anders ([194.239.165.151]) by fepC.post.tele.dk
          (InterMail vM.4.01.02.00 201-229-116) with SMTP
          id <20000420210204.BZFD7404.fepC.post.tele.dk@Anders>
          for <ietf@ietf.org>; Thu, 20 Apr 2000 23:02:04 +0200
Message-ID: <008f01bfab0b$a7532fe0$1000000a@DIC>
From: "Anders Feder" <lists.anders@feder.dk>
To: <ietf@ietf.org>
Subject: Universal Network Language
Date: Thu, 20 Apr 2000 23:01:49 +0200
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.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hi,

The translation system being developed for the United Nations, the Universal
Network Language (UNL), looks quite promising. Does the IETF have any plans
regarding this system?

UNL homepage: http://www.unl.ias.unu.edu/

- Anders Feder



From owner-ietf-outbound  Thu Apr 20 17:41:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA21797
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 17:40:03 -0400 (EDT)
Received: from redmailwall.attws.com (redmailwall.attws.com [199.108.253.115])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21774
	for <ietf@ietf.org>; Thu, 20 Apr 2000 17:39:13 -0400 (EDT)
Received: from viruswall.entp.attws.com (viruswall.entp.attws.com [155.176.34.36])
	by redmailwall.attws.com (8.9.3/8.9.3) with ESMTP id OAA07499;
	Thu, 20 Apr 2000 14:35:27 -0700 (PDT)
Received: from nwestmail.nwest.attws.com by viruswall.entp.attws.com (8.8.8/AT&T Wireless Services, Inc. V8 version 2)
	id OAA10953; Thu, 20 Apr 2000 14:31:56 -0700 (PDT)
Received: from kali.nwest.mccaw.com (kali.nwest.attws.com [141.204.186.81])
	by nwestmail.nwest.attws.com (8.8.8+Sun/8.8.8) with ESMTP id OAA02054;
	Thu, 20 Apr 2000 14:31:57 -0700 (PDT)
Received: (from daryl@localhost)
	by kali.nwest.mccaw.com (8.9.1/8.9.1) id OAA11041;
	Thu, 20 Apr 2000 14:32:08 -0700
Date: Thu, 20 Apr 2000 14:32:08 -0700
From: Daryl Bunce <daryl.bunce@attws.com>
Message-Id: <200004202132.OAA11041@kali.nwest.mccaw.com>
To: ietf@ietf.org
Subject: RE: IP over Bluetooth, Cellular Handoff to WLAN
Cc: Phillip.Neumiller@Motorola.Com
X-Loop: ietf@ietf.org


> Anybody interested in chatting about macro-cellular to WLAN/PAN handovers?

I've been thinking of this quite a bit since probably jan.

I'm really interested in the potential of dynamic routing
over bluetooth, possibly without the handover...
(Needless to say, AT&T Wireless, my current employer, is
not taking sides).  Your bluetooth (BT) computer to my
BT palm pilot to that car's BT cdplayer to the next
vehicle's BT ...

 - R/db		( daryl.bunce@attws.com, 425/580-7275 )
     Architecture/Emerging Technologies Group
     The Moon is Waning Gibbous (96% of Full)



From owner-ietf-outbound  Thu Apr 20 19:21:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA22724
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 19:20:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22693
	for <ietf@ietf.org>; Thu, 20 Apr 2000 19:18:42 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id TAA11053;
        Thu, 20 Apr 2000 19:17:21 -0400 (EDT)
Message-Id: <200004202317.TAA11053@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: ietf@ietf.org, jaltman@columbia.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Thu, 20 Apr 2000 15:58:39 EDT."
             <200004201958.PAA23389@ginger.lcs.mit.edu> 
Date: Thu, 20 Apr 2000 19:17:21 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

>     > From: Jeffrey Altman <jaltman@columbia.edu>
> 
>     > I am not a IPv6 proponent other than
> 
> Well, I'm not exactly a big fan of NAT boxes either. Disgusting kludges.
> 
> However, I've generally found that it's not really very useful to go around
> saying "it's not really raining, it's not really raining" while I'm walking
> in a thunderstorm.....

nobody is saying that it isn't raining.
(though personally I'd say NATs are more like baseball-sized hail than rain)

people are saying (to continue the analogy) that if people are getting wet 
and cold and ill because they're standing out in the rain, maybe they 
should go somewhere else instead of continuing to stand there and saying 
"man was meant to be rained on".

> NAT's are with us, like them or not, and the sooner we accept it, and try to
> start working to fix things up to work with them, the better...

some of us are trying to fix the NATs.  but ultimately the only way to 
"fix" NATs is to coerce them into being routers that deal with 
larger end-to-end addresses.

>     > the extended address space that everyone needs without breaking the end
>     > to end model of IP.
> 
> Well, I think we can regain the "end-end model", even with NAT boxes, if we
> accept that those 32-bit things are irrevocably destined to become just
> forwarding tags with only local scope.

we might regain the "end to end model" from doing this but we would 
still prevent a lot of applications from working well.  if the only
applications we ever wanted to care about were email and the web this 
might be good enough.  but from where I sit it looks like Internet usage
is becoming more and more diverse. so a model that assumes that everything
is connection-oriented and can therefore afford connection setup overhead, 
or that all networked apps are client-server or provider-consumer, or that 
all apps need a central point of control, doesn't look very attractive to me.

an Internet that doesn't support distributed apps efficiently is at
least as crippled as one that doesn't support multicast. 

> There's a need, and a place, for things with only local scope - e.g. the
> network layer header in front of the internet header, the hop count in the
> internet header, etc, etc. The IPv4 address will have to be added to that list
> - and for things which need an end-end name, we'll have to migrate to using
> something else.

from the point of view of a developer of distributed apps, that's a 
pretty naive statement.  and I have yet to see someone who recommends 
that approach demonstrate how to recover the functionality that you lose 
by doing so.    instead, the argument tends to be of the form
"your use of IP addresses as endpoint IDs is already screwed by NATs, so 
we might as well usurp them for use as local forwarding tags".

and except for the dubious benefit of NAT compatibility, I haven't been
able to figure out why it's so important to have yet another form of 
local forwarding tag in addition to link-layer addresses, MPLS tags, 
PPP header compression, IP-in-IP tunneling, and probably one or two
other ways that we have for forwarding IP packets within a local scope.

> But it will have to be an incremental approach back to goodness, I fear...

if you mean an approach that can be deployed incrementally, I agree.
but strict hill-climbing strategies tend not to produce very good solutions,
and the top of the NAT hill is a long way from goodness.

Keith



From owner-ietf-outbound  Thu Apr 20 19:31:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA22884
	for ietf-outbound.10@ietf.org; Thu, 20 Apr 2000 19:30:03 -0400 (EDT)
Received: from e4.ny.us.ibm.com (e4.ny.us.ibm.com [32.97.182.104])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22813
	for <ietf@ietf.org>; Thu, 20 Apr 2000 19:26:00 -0400 (EDT)
From: pravinb@us.ibm.com
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22])
	by e4.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id TAA410860;
	Thu, 20 Apr 2000 19:24:27 -0400
Received: from D51MTA07.pok.ibm.com (d51mta07.pok.ibm.com [9.117.200.35])
	by northrelay02.pok.ibm.com (8.8.8m3/NCO v2.07) with SMTP id TAA258114;
	Thu, 20 Apr 2000 19:25:58 -0400
Received: by D51MTA07.pok.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id 852568C7.0080B2C3 ; Thu, 20 Apr 2000 19:25:43 -0400
X-Lotus-FromDomain: IBMUS
To: Phil Neumiller <Phillip.Neumiller@Motorola.Com>
cc: ietf@ietf.org, Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Thomas Narten <narten@raleigh.ibm.com>
Message-ID: <852568C7.0080B122.00@D51MTA07.pok.ibm.com>
Date: Thu, 20 Apr 2000 19:27:16 -0400
Subject: FWD: IP over Bluetooth, Cellular Handoff to WLAN
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org


Phil,

A proposal for IP over Bluetooth BOF is under preparation. We are
in the process of soliciting approvals from the IETF area directors and
the Bluetooth SIG.

I'll post an announcement to the IETF mailing list as soon as all
approvals are in place.

-*- Pravin -*-
===========================================
Pravin Bhagwat
http://www.research.ibm.com/people/p/pravin

> Folks,
>
> Where(what is the mail list) is the discussion group for IP over
Bluetooth?
> I heard about the Pittsburgh BOF but I can't find a mail list.
>
> Anybody interested in chatting about macro-cellular to WLAN/PAN
handovers?
>
> Thanks,
>
> Phil




From owner-ietf-outbound  Fri Apr 21 02:40:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA09462
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 02:40:02 -0400 (EDT)
Received: from web1405.mail.yahoo.com (web1405.mail.yahoo.com [128.11.23.169])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA09412
	for <ietf@ietf.org>; Fri, 21 Apr 2000 02:32:00 -0400 (EDT)
Received: (qmail 19911 invoked by uid 60001); 21 Apr 2000 06:31:59 -0000
Message-ID: <20000421063159.19910.qmail@web1405.mail.yahoo.com>
Received: from [209.239.198.221] by web1405.mail.yahoo.com; Thu, 20 Apr 2000 23:31:59 PDT
Date: Thu, 20 Apr 2000 23:31:59 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
To: Keith Moore <moore@cs.utk.edu>, Matt Holdrege <holdrege@lucent.com>
Cc: jaltman@COLUMBIA.EDU, ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org


--- Keith Moore <moore@cs.utk.edu> wrote:
> > Also please do not steer this thread towards a NAT bashing-fest. We need to
> 
> > complete this document and we need constructive input to this draft.
> 
> unfortunately, the major premise of the draft is flawed.  there 
> are far too many problems to NAT, affecting far too many applications, 
> to make a usefully complete list of the applications that are affected.  
> and the list is constantly growing larger.
> 
> finally, the notion that one can fix NAT's problems with ALGs is
> not only incorrect, it's impractical for NATs to support even
> the applications for which ALGs are feasible.
> 
> Keith
> 
> 
Keith - If you have issues with the premise of the draft or the NAT WG - 
you should take this up with the ADs. This is not the forum to do that.
Our mailboxes are just getting cluttered with way too much of the crusade
stuff. That is not what the draft or the WG is about.

You are welcome to send in input that can be valuable to the draft. Thanks.

regards,
suresh 


=====


__________________________________________________
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com



From owner-ietf-outbound  Fri Apr 21 03:30:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA09800
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 03:30:02 -0400 (EDT)
Received: from web1405.mail.yahoo.com (web1405.mail.yahoo.com [128.11.23.169])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA09756
	for <ietf@ietf.org>; Fri, 21 Apr 2000 03:27:35 -0400 (EDT)
Received: (qmail 25686 invoked by uid 60001); 21 Apr 2000 07:27:35 -0000
Message-ID: <20000421072735.25685.qmail@web1405.mail.yahoo.com>
Received: from [209.239.198.221] by web1405.mail.yahoo.com; Fri, 21 Apr 2000 00:27:35 PDT
Date: Fri, 21 Apr 2000 00:27:35 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org



--- Vernon Schryver <vjs@calcite.rhyolite.com> wrote:
> > From: Matt Holdrege <holdrege@lucent.com>
> 
> > ...
> > Just so there is no more confusion, in no way is the IETF endorsing the use
> 
> > or development of NAT. You've completely missed the point of the draft. 
> > It's purpose is to clearly point out the problems that NAT causes to a 
> > given set of protocols.
> >
> > Also please do not steer this thread towards a NAT bashing-fest. We need to
> 
> > complete this document and we need constructive input to this draft. Thanks
> 
> > again for your original input.
> 
> 
> If the document is not intended to be read as advocating NAT, it also
> needs substantial non-technical changes.  It currently comes across as
> a list of fairly minor, generally easily fixed problems or problems that
> don't matter.  I don't mean to say that is the intended point of the
> document, but is how I read it.  Since I'm among those who feel that the
> situation with NAT is not quite as bad things would have been if we had
> waited for IPv6, you might expect my prejudices to make me read it the
> other way.
> 

If you an issue with specific portions of the draft, please let us know.
Minor edits could be sent to the authors privately. Thanks.

> Instead of appearing to be a complete list of problem and their complete
> and easy solutions, the document needs to have more words in each section
> saying that the sublist of problems is probably incomplete.  The
> shortcomings of solutions to the problems should be belabored instead of
> glossed over.  Seeing that the problems are significant must not require
> any technical sophistication in the reader.

Agreed. The document was not intended to be an exhaustive list of
protocols/applications that fail with NAT. The abstract actually
captures that sentiment. Anyways, if you have specific input on things
being glossed over without sufficient coverage, do let us know, with 
any proposed textual editions. We will certainly follow through on that.


>                                             For example, most people who
> should read this document will see nothing but some opaque acronyms
> whose problems surely don't matter in Section 5.  Why should anyone care
> that IPCEC doesn't work with NAT?
> 

Well, readers should know that IPsec that protects the addresses in IP 
header cannot work with NAT enroute. Dont you think?

> 
> Vernon Schryver    vjs@rhyolite.com
> 

cheers,
suresh 

=====


__________________________________________________
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com



From owner-ietf-outbound  Fri Apr 21 05:20:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA10645
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 05:20:02 -0400 (EDT)
Received: from web1405.mail.yahoo.com (web1405.mail.yahoo.com [128.11.23.169])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA10608
	for <ietf@ietf.org>; Fri, 21 Apr 2000 05:17:04 -0400 (EDT)
Received: (qmail 3511 invoked by uid 60001); 21 Apr 2000 09:17:04 -0000
Message-ID: <20000421091704.3510.qmail@web1405.mail.yahoo.com>
Received: from [209.239.198.221] by web1405.mail.yahoo.com; Fri, 21 Apr 2000 02:17:04 PDT
Date: Fri, 21 Apr 2000 02:17:04 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: jaltman@COLUMBIA.EDU, ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org


--- Jeffrey Altman <jaltman@COLUMBIA.EDU> wrote:
> This draft is very incomplete and in my opinion not ready for prime
> time.  The working group has in the past requested lists of protocols
> and applications which do not work with NATs.  I have replied
> discussing those items for which I am most familiar:

Hmm.. I do not recall seeing your e-mail on this matter before.
I dont know how we could have lost it. Anyways, sorry about that.

<... stuff deleted> 
>
> 
> Telnet:
> 
> Transmits IP addresses from the client to the server for the purposes
> of setting the DISPLAY variable.  When set the DISPLAY variable is 
> used for subsequent connections from X clients on the host to an
> X server on the workstation.
> 

Agreed, if you use IP address of the X-server, instead of DNS name
(in the case of Basic-NAT en-route). In the case of NAPT enroute,
it is a non-issue, as you would have used just the IP address of 
the NAPT device, right?
 
We covered this in section 3.1, but not in the context of telnet
(X-Windows client). Good point.
 
> When AUTH is used with Kerberos 4 and Kerberos 5 there are issues
> related to the IP addresses which are embedded into the Kerberos 
> tickets which specify the valid machines from which the tickets are 
> valid.
> 

Are you saying that IP address of the senders is always embedded in 
the kerberos-4 tickets?

Section 6 attempts to state that any application that has private IP 
address in the payload and its payload secured (and NAT is not party 
to the security key) cannot traverse NAT device. We can certainly include
this application there.

Section 8.1 of RFC 2663 also talks about NAT limitations with regards
to applications with IP address content(especially, encrypted/authenticated)


> When START_TLS is used there may be client certificate verification
> problems caused by the NAT depending on the information provided in
> the certificate.
> 

Agreed. Same comment as before.

> FTP:
> 
> As stated FTP, uses multiple sessions.  But what it fails to state
> is that if any form of PROT is used to secure the command channel
> then it is impossible to implement an ALG to perform IP Address swaps.
> 

Agreed. Will add text to clarify this.

> When AUTH is used with Kerberos 4, Kerberos 5, and TLS the same
> problems that occur with Telnet occur with FTP.
> 

I guess, you are talking about sending IP address data encrypted 
from a telnet station. Please elaborate, if I am missing something.


> RSH/RLOGIN:
> 
> RSH uses multiple sessions to support separate streams for stdout and 
> stderr.  The stderr socket is a connection from the server to the
> client.  And unlike FTP, there is no equivalent to PASV mode.
> 
Are you saying that there is a problem when a private host does
rsh into an external server? If so, can stderr be directed to the
client-host by name, as opposed to IP-address?

I donot know much about the inner-working of "rsh" to state whether it 
can work with a NAPT device between client and server.

> RLOGIN does not use multiple sessions.

What is the problem here?

> 
> But the Kerberos protoected versions of RSH and RLOGIN will not work 
> in a NAT environment due to the ticket problems and the use of
> multiple sessions.
> 
What is the issue with multiple sessions? Are you refering to one of the 
sessions being redirected to the originator by address?

> Kerberos 4:
> 
> Kerberos 4 tickets are encrypted.  Therefore, an ALG cannot be
> written.  The K4 ticket contains a single IP address describing the
> interface used by the client to retrieve the ticket from the TGT from
> the perspective of the KDC.  If the KDC and all services are on the 
> far side of the NAT, the end user will not notice any problems.  But
> the ticket will be valid from any IP address inside the NAT (on the 
> private network.) 

How so? Are you assuming that AUTH is not used?

>                   Without a NAT, an attacker needs to be able to 
> spoof the source IP addresses of a connection that is being made in
> order to use a stolen ticket on a different host.    With a NAT, all 
> the attacker needs to do from the near side of the NAT is to simply 
> gain possession of a ticket.  
> 

An attacker can be resourceful in many ways. An attacker does not need a 
NAT to spoof an IP address. Private users of a NAT domain are assumed 
to be within a trusting domain.

> Kerberos 5:
> 
> Kerberos 5 tickets are encrypted.  Therefore, an ALG cannot be
> written.  The K5 ticket contains a list of IP addresses from which
> the ticket is to be considered valid.  The list is generated by the
> client machine, not the KDC.  If the services being accessed with
> Kerberos authentication are on the public side of the NAT, then 
> the Kerberos authentication will fail because the IP address used
> by the NAT is not in the list of acceptable addresses.
> 

OK.

> There are two workarounds in Kerberos 5 both of which reduce the 
> security of the tickets.  The first is to have the clients specify 
> the public IP address of the NAT in the ticket's IP list.  But this
> leads to the same security problem detailed for K4.  Plus, how is
> the client supposed to find out what the public IP Address of the NAT
> is from the private side?
> 

Yes. Sounds like a problem. RSIP may have a win here.

> The second method is to remove all IP addresses from the K5 tickets
> but this now makes theft of the ticket even worse since the tickets 
> can be used from anywhere.  Not just from within the private network.
> 

Agreed. How do you expect the intruders  will steal the tickets, without
being recipients of the ticket? Unless, you are assuming that the private
network is not trusted and that there are intruders within the private 
network.


> X Windows:
> 
> There are two problems in the X world.  First, the X clients which are
> in the public space need to make connections to the X Server which is
> in the private space.  The IP address to which the connections are to
> be made is specified by the DISPLAY environment variable which is 
> set by the client in some way.    The NAT would have to have an ALG
> to replace the IP address and configure a port in the valid display
> range (ports 6000 and higher) to act as a gateway.  
>

Yes. I belive, we addressed this already under Telnet/DISPLAY.
 
> But if the NAT listens for incoming connections then it may well 
> increase the security risk by providing access to the X server that
> would not otherwise be available. 

I dont understand how this increase the security risk.
Allowing access to X-servers is simply a matter of configuration. This 
is not different from a firewall that configures the X-servers for external
access, for example.

>                                   Since the NATs tamper with the
> IP addresses it will also not be possible for X Authorization methods
> other than MIT-MAGIC-COOKIE-1 to be used.  MIT-MAGIC-COOKIE-1 is the
> least secure of all the documented X Authorization methods.
>

You may be right. I am not familiar with the X Authorization methods.
 
> -------
> 
> This small sampling of the types of information which are not provided
> in this document is most likely just the tip of the iceberg.  I
> recommend that this document not be published in its current form due
> to the overwhelming impression that is given to the reader that there
> are no significant problems with NATs.  Plus the document clearly
> mentions areas where further research is required where the necessary
> research is not difficult to perform.
> 

I agree, the document in its current form is not ready for publication
as an RFC. It needs work. Thanks for your input. We will certainly 
incorporate the comments in the next rev of the draft.

> 
> 
>     Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
>                  The Kermit Project * Columbia University
>               612 West 115th St #716 * New York, NY * 10025
>   http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org
> 
> 
> 
regards,
suresh

__________________________________________________
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com



From owner-ietf-outbound  Fri Apr 21 05:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA10762
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 05:30:02 -0400 (EDT)
Received: from kediri.webindonesia.com (kediri.webindonesia.com [207.106.122.14])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA10728
	for <ietf@ietf.org>; Fri, 21 Apr 2000 05:25:23 -0400 (EDT)
Received: (qmail 648 invoked by uid 1003); 21 Apr 2000 09:25:24 -0000
Date: Fri, 21 Apr 2000 05:25:24 -0400
From: "Rahmat M. Samik-Ibrahim" <ibrahim@kediri.webindonesia.com>
To: Milis IETF <ietf@ietf.org>
Subject: The RFC-Editor and IANA  (part II)
Message-ID: <20000421052524.A614@kediri.webindonesia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95us
X-Loop: ietf@ietf.org

Quoted from another thread:

  However, we believe that there is a fairly general understanding 
  among IAB, ICANN, and US DoC that the IAB could, indeed, transfer 
  the portions of the IANA efforts that relate to IETF work elsewhere 
  if that were necessary or desirable.

I like this bold statement very much, and I believe that this is the 
way that the IAB should go! And, I assume that it was not a humorous
intentional. It is still not clear, however, why both IANA and the 
RFC-Editor have never explicitly acknowledged that they were chartered 
by the IAB.

If the funding of the RFC Editor function is $1,295,517 and it 
produces 1300 RFCs, the production cost of one RFC will be about $1000. 
This is equivalent to 10 third world man month. No complain, since
this is funded by Uncle Sam's tax payers or its derivative.

(Unfortunately, parts of ICANN and regional *NIC registries funds 
will come from the third world).

References:
* http://ittf.vlsm.org/ietf/164.txt
* http://ittf.vlsm.org/ietf/00/1.txt
* http://gtm.vlsm.org/in-i-iana1.html

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- You have to let me go, I just wanna tell you! - 5IVE INVINCIBLE -



From owner-ietf-outbound  Fri Apr 21 08:40:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA14108
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 08:40:02 -0400 (EDT)
Received: from watsun.cc.columbia.edu (IDENT:cu51491@watsun.cc.columbia.edu [128.59.39.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13905
	for <ietf@ietf.org>; Fri, 21 Apr 2000 08:31:26 -0400 (EDT)
Received: (from jaltman@localhost)
	by watsun.cc.columbia.edu (8.8.5/8.8.5) id IAA27421;
	Fri, 21 Apr 2000 08:31:25 -0400 (EDT)
Date: Fri, 21 Apr 2000 8:31:24 EDT
From: Jeffrey Altman <jaltman@columbia.edu>
Reply-To: jaltman@columbia.edu
To: Pyda Srisuresh <srisuresh@yahoo.com>
Cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: Your message of Fri, 21 Apr 2000 02:17:04 -0700 (PDT)
Message-ID: <CMM.0.90.4.956320284.jaltman@watsun.cc.columbia.edu>
X-Loop: ietf@ietf.org

I have so many issues with this reply that I am only going to focus on
one.

> Agreed. How do you expect the intruders  will steal the tickets, without
> being recipients of the ticket? Unless, you are assuming that the private
> network is not trusted and that there are intruders within the private 
> network.

There is no such thing as a trusted network.  One of the first things
you learn about security (having nothing to do with computer security)
is that most attacks occur from inside the organization.  There is no
such thing as a trusted network.

I have pointed you in directions you need to follow.  Stating that the
a problem in one context is described in the described in another
context is not useful in this document.  It is exactly because of this
approach that the document comes across sounding as if the problems
described are trivial and inconsequential.



    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org




From owner-ietf-outbound  Fri Apr 21 09:40:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA16230
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 09:40:02 -0400 (EDT)
Received: from fep2.excitehome.net (fep2.excitehome.net [24.0.26.113])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15964
	for <ietf@ietf.org>; Fri, 21 Apr 2000 09:30:40 -0400 (EDT)
Received: from c8-a.snvl1.sfba.home.com ([24.0.25.112])
          by fep2.excitehome.net (InterMail vM.4.01.02.27 201-229-119-110)
          with ESMTP
          id <20000421133034.GEUJ579.fep2.excitehome.net@c8-a.snvl1.sfba.home.com>
          for <ietf@ietf.org>; Fri, 21 Apr 2000 06:30:34 -0700
Message-Id: <4.2.0.58.20000421092319.0095f100@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Fri, 21 Apr 2000 09:31:43 +0100
To: ietf <ietf@ietf.org>
From: RJ Atkinson <rja@inet.org>
Subject: SNMPv3 deployment & Wind River Systems
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Hi,

	Lack of SNMPv3 availability in networking products is a serious
operational problem in the Internet today, IMHO.

	A large number of networking vendors are telling @Home that the
vendor has difficulty in offering SNMPv3 because WindRiver won't take the
Epilogue SNMP Agent software (Epilogue is now owned by WindRiver
so that code would be the obvious choice) and port it across to VxWorks
(and for that matter, PSOS).   VxWorks and PSOS are only available with
a SNMPv1/v2c agent even today, with no prospect for SNMPv3 anytime soon.

	While theoretically anyone could port the code, in practice a lot
of the affected companies aren't big enough to have that amount of extra staff
lying around.  By the way, this also means there is a market for
a pre-ported (to VxWorks/PSOS) version of any other SNMP code, if someone
is feeling like a capitalist.

	If anyone here has the ear of anyone in management at WindRiver Systems,
it would be a public service to push them to get an SNMPv3 agent available to
their VxWorks customers ASAP.  The downstream customer demand exists.

	Sorry for the interruption and thanks for listening.

Ran
rja@inet.org




From owner-ietf-outbound  Fri Apr 21 13:51:55 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA22257
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 13:50:02 -0400 (EDT)
Received: from fw-ra06.raytheon.com (fw-ra06.RAYTHEON.COM [192.27.4.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22144
	for <ietf@ietf.org>; Fri, 21 Apr 2000 13:41:11 -0400 (EDT)
Received: from isra02.rsc.raytheon.com (isra02.rsc.raytheon.com [147.19.2.15])
	by fw-ra06.raytheon.com (8.9.1/8.9.1) with ESMTP id KAA06002;
	Fri, 21 Apr 2000 10:41:02 -0700 (PDT)
Received: from electra.rsc.raytheon.com (mail@electra.RSC.RAYTHEON.COM [147.19.52.42])
	by isra02.rsc.raytheon.com (8.9.1/8.9.1) with ESMTP id KAA08689;
	Fri, 21 Apr 2000 10:41:09 -0700 (PDT)
Received: from (ZFUAA373715) [147.19.54.44] 
	by electra.rsc.raytheon.com with smtp (Exim 2.05 #1 (Debian))
	id 12ihQT-00057r-00; Fri, 21 Apr 2000 10:41:09 -0700
Received: by localhost with Microsoft MAPI; Fri, 21 Apr 2000 10:41:07 -0700
Message-ID: <01BFAB7E.19D8C990.rascheri@electra.rsc.raytheon.com>
From: "Richard C. Ascheri" <rascheri@electra.rsc.raytheon.com>
Reply-To: "rascheri@electra.rsc.raytheon.com"
	 <rascheri@electra.rsc.raytheon.com>
To: "'Michael B. Bellopede'" <Michael.CTR.Bellopede@tc.faa.gov>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Digital Radio Configuration Question
Date: Fri, 21 Apr 2000 10:41:07 -0700
Organization: Raytheon
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Encoding: 121 TEXT
X-Loop: ietf@ietf.org


I'm trying to announce to the host connected to the Ethernet interface. 
 Yes the digital radio does have other interfaces, but I believe that only 
one type of interface (ethernet or PPP) will be active at any one time, 
i.e. we won't have the PPP interface working at the same time as the 
Ethernet.  At least that is not the plan so far.

To bring you up to date:  I started down the path of using the Limited 
Broadcast address and an ICMP Echo Request message to get the Digital Radio 
to announce it's IP address.

I wrote a simple program that sends an ICMP Echo Request message to the 
limited broadcast address of 255.255.255.255.  This appeared to work when 
testing it with many of the hosts on our network, i.e. numerous hosts 
responded with their own IP address...  However, the digital radio does NOT 
respond because the VxWorks operating system apparently doesn't support 
answering the limited broadcast address...(The documentation suggests that 
you have to set the broadcast address for the interface, and 
255.255.255.255 is illegal).  So that method looks like a dead end.  That 
was going to be the easiest and the cleanest.

The next method I plan to try is to use a Multicast address to exchange 
maybe an ICMP Echo Request message (or some other message) with one 
another.  First idea is to identify a Multicast address to use to do this. 
 I want to try and use one of the predefined multicast addresses.  Any 
suggestions from anyone as to which one might be appropriate for this kind 
of thing?

If the above methods fail then my final attempt will be to implement a 
minimum Service Location Protocol V2 Implementation in the digital radio, 
and have it announce some kind of configuration service.  The host could 
then look for this configuration service and get the information it needs 
from the SLP messages.  The thing I like about this method is that it is a 
standard RFC, and I can later expand on the other services that I might 
want the digital radio to announce.

Any other suggestions would be greatly appreciated.

Thanks in advance,
Rick.


-----Original Message-----
From:	Michael B. Bellopede [SMTP:Michael.CTR.Bellopede@tc.faa.gov]
Sent:	Friday, April 21, 2000 7:20 AM
To:	Richard C. Ascheri
Subject:	RE: Digital Radio Configuration Question

If you have more than one physical interface, each with its own IP, than
this device definitely is considered a router.  Are you trying to announce
the IP of the ethernet interface to the connected ethernet host (via
ethernet interface), or announce to a host communicating with the radio
interface?

-Michael B. Bellopede
 Michael.CTR.Bellopede@tc.faa.gov
 "There is no spoon."

-----Original Message-----
From: Richard C. Ascheri [mailto:rascheri@electra.rsc.raytheon.com]
Sent: Monday, April 17, 2000 1:32 PM
To: 'ietf@ietf.org'
Subject: Digital Radio Configuration Question



Hello,

I'm a Systems Engineer at Raytheon Company.  I have been working on the
development of a digital IP based radio for some time now.  The radio has
an Ethernet interface, PPP interface, and an ADDSI X.25 interface.

My question relates to the configuration of the radio.  To configure the
radio we have an implementation of SNMPv2.  This implementation allows the
radio to be configured over the Ethernet or PPP interfaces using the SNMPv2
protocol.

My question relates to configuring the radio without knowing it's IP
address.  I understand that SNMP requires the IP address of the device you
want to configure.

I am interested in a standard method of announcing the IP address of the
Ethernet interface.  This would allow a configuration tool to look for the
announcements and then send SNMP configuration messages to modify the
radios configuration.  For this scenario you can assume that the radio will
be attached to a single host over an Ethernet interface.  There will be no
other hosts or radios on the network.  Assume that the IP address of the
radio is NOT known.  It could be set to anything, even an address outside
of the range of the hosts subnet.

I have looked at a number of RFC's but have found these two that may work:

RFC 1256 - ICMP Router Discovery.  This rfc does announce the IP address,
however, for this scenario I'm not interested in saying that this radio is
the next hop gateway.  Given that the radio has numerous interfaces and an
TCP/IP stack you might consider this a router.  However, I don't really
feel that this RFC directly relates to solving the configuration problem.
 The host is not really looking for it's next hop gateway.  It's looking
for devices that can be configured through SNMP.

RFC 2608 - Service Location Protocol v2.  This rfc does imply that I could
create a "Configuration-Service" and announce its availability using the
SNMP protocol.  This actually sounds like the right kind of solution to my
problem.

But now I'm wondering whether or not there is something else that I haven't
found.  Maybe something in the works, as a draft, or a working group that
is responsible for looking at these kinds of problems.

Any and all comments would be gratefully appreciated.

Thanks in advance.
Rick.

Richard C. Ascheri                                      Raytheon Company
Principle Systems Engineer                              1801 Hughes Drive
Network Technology Group                                Fullerton, CA.
92836
C3I Systems                                     http://www.raytheon.com
rascheri@electra.rsc.raytheon.com




From owner-ietf-outbound  Fri Apr 21 14:01:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA22560
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 14:00:02 -0400 (EDT)
Received: from small-gods.mit.edu (SMALL-GODS.MIT.EDU [18.177.0.248])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22427
	for <ietf@ietf.org>; Fri, 21 Apr 2000 13:55:30 -0400 (EDT)
Received: (from ghudson@localhost) by small-gods.mit.edu (8.9.3)
	id NAA10101; Fri, 21 Apr 2000 13:55:18 -0400 (EDT)
Message-Id: <200004211755.NAA10101@small-gods.mit.edu>
To: Pyda Srisuresh <srisuresh@YAHOO.COM>
cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-Reply-To: Your message of "Fri, 21 Apr 2000 02:17:04 PDT."
             <20000421091704.3510.qmail@web1405.mail.yahoo.com> 
Date: Fri, 21 Apr 2000 13:55:18 -0400
From: Greg Hudson <ghudson@MIT.EDU>
X-Loop: ietf@ietf.org

I'd like to make some clarifications about Kerberos and NAT.

>> When AUTH is used with Kerberos 4 and Kerberos 5 there are issues
>> related to the IP addresses which are embedded into the Kerberos
>> tickets which specify the valid machines from which the tickets are
>> valid.

> Are you saying that IP address of the senders is always embedded in
> the kerberos-4 tickets?

In Kerberos 4, when the KDC receives a ticket request, it includes the
source IP address in the returned ticket.  This works fine if the KDC
is across a NAT gateway, as long as all of the Kerberos services are
also across a NAT gateway.

In Kerberos 5, the client specifies a list of IP addresses which the
ticket should be valid for, or it can ask for a ticket valid for all
IP addresses.  By asking for an all-IP-addresses ticket or a ticket
containing the NAT gateway address, you can get krb5 to work with a
NAT gateway, although it isn't very transparent (it requires the
clients to behave differently than they otherwise would).  The MIT
krb5 1.0 implementation didn't have any configurability for what IP
addresses the client asked for (it always asked for the set of its
interface addresses) and did not interact well with NAT.  The MIT krb5
1.1 implementation allows you to put "noaddresses" somewhere in
krb5.conf to request all-IP-addresses-valid tickets.

Not all Kerberos 4 or 5 services actually check source IP addresses.
(I don't have a list of common Kerberos services which do or do not
check source IP addresses, unfortunately.  AFS is a good example of a
Kerberos 4 service which does not.)  Services which don't check are
obviously not picky about NAT gateways.

There are, of course, a substantial number of people who believe that
Kerberos source IP address checking is not worth the trouble, since it
is not a central part of the Kerberos security model.  (Basically, it
means if someone steals Kerberos tickets, they can't use them from a
different IP address unless they can forge the source IP address or
use services which don't check.)



From owner-ietf-outbound  Fri Apr 21 14:31:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA23082
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 14:30:02 -0400 (EDT)
Received: from pobox.isi.com (pobox.isi.com [192.73.222.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22954
	for <ietf@ietf.org>; Fri, 21 Apr 2000 14:22:47 -0400 (EDT)
Received: from rswanson (csdial2 [192.103.52.193])
	by pobox.isi.com (Pro-8.9.3/Pro-8.9.3/Pobox 991110 TroyC) with SMTP id LAA10681;
	Fri, 21 Apr 2000 11:25:35 -0700 (PDT)
Reply-To: <robb.swanson@windriver.com>
From: "Robb Swanson" <robb.swanson@windriver.com>
To: "RJ Atkinson" <rja@inet.org>, "ietf" <ietf@ietf.org>
Subject: RE: SNMPv3 deployment & Wind River Systems
Date: Fri, 21 Apr 2000 14:29:53 -0400
Message-ID: <NDBBIAJFIKDKNDNJOINFEEBCDMAA.robb.swanson@windriver.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <4.2.0.58.20000421092319.0095f100@avarice.inner.net>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

The facts, as stated, are simply not true.

SNMPv3 is ported and supported for both VxWorks and pSOS+.  Prior to the
merger of Wind River and Integrated Systems (which owned Epilogue),
there was no SNMPv3 solution for VxWorks.  But it is available today.
SNMPv3 has been available for pSOS+ for as long as Epilogue had an
SNMPv3 solution (about 18 months now).

Robb Swanson                   voice : 781-643-5222
Field Engineering Specialist     fax : 781-643-5225
Wind River                       www : http://www.windriver.com


> -----Original Message-----
> From: RJ Atkinson [mailto:rja@inet.org]
> Sent: Friday, April 21, 2000 4:32 AM
> To: ietf
> Subject: SNMPv3 deployment & Wind River Systems
>
>
> Hi,
>
> 	Lack of SNMPv3 availability in networking products is a serious
> operational problem in the Internet today, IMHO.
>
> 	A large number of networking vendors are telling @Home that the
> vendor has difficulty in offering SNMPv3 because WindRiver
> won't take the
> Epilogue SNMP Agent software (Epilogue is now owned by WindRiver
> so that code would be the obvious choice) and port it across
> to VxWorks
> (and for that matter, PSOS).   VxWorks and PSOS are only
> available with
> a SNMPv1/v2c agent even today, with no prospect for SNMPv3
> anytime soon.
>
> 	While theoretically anyone could port the code, in
> practice a lot
> of the affected companies aren't big enough to have that
> amount of extra staff
> lying around.  By the way, this also means there is a market for
> a pre-ported (to VxWorks/PSOS) version of any other SNMP
> code, if someone
> is feeling like a capitalist.
>
> 	If anyone here has the ear of anyone in management at
> WindRiver Systems,
> it would be a public service to push them to get an SNMPv3
> agent available to
> their VxWorks customers ASAP.  The downstream customer demand exists.
>
> 	Sorry for the interruption and thanks for listening.
>
> Ran
> rja@inet.org
>
>
>



From owner-ietf-outbound  Fri Apr 21 14:51:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA23579
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 14:50:02 -0400 (EDT)
Received: from stovokor.epilogue.com (stovokor.epilogue.com [128.224.1.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23555
	for <ietf@ietf.org>; Fri, 21 Apr 2000 14:49:42 -0400 (EDT)
Received: from sar@localhost by stovokor.epilogue.com id <7863-195>; Fri, 21 Apr 2000 14:49:24 -0400
Sender: sar@epilogue.com
From: "Shawn A. Routhier" <sar@epilogue.com>
To: rja@inet.org
CC: ietf@ietf.org
In-reply-to: <4.2.0.58.20000421092319.0095f100@avarice.inner.net> (message
	from RJ Atkinson on Fri, 21 Apr 2000 10:10:46 -0400)
Subject: Re: SNMPv3 deployment & Wind River Systems
Message-Id: <20000421184938Z7863-195+7662@stovokor.epilogue.com>
Date: 	Fri, 21 Apr 2000 14:49:24 -0400
X-Loop: ietf@ietf.org


This note is simply to update the record.  As the whole discussion
is dealing with a single vendor followups should probably be taken
off-line.

Anyway, the port of Envoy and SNMPv3 to VxWorks is in the hands of the
manufacturing and shipping department and should be shipped to customers
shortly (next week or so).  Envoy with SNMPv3 was released on pSOS
somewhat over a year ago.

regards,
Shawn A. Routhier
Epilogue, Integrated Systems (pSOS), WindRiver (VxWorks)

   Hi,

	   Lack of SNMPv3 availability in networking products is a serious
   operational problem in the Internet today, IMHO.

	   A large number of networking vendors are telling @Home that the
   vendor has difficulty in offering SNMPv3 because WindRiver won't take the
   Epilogue SNMP Agent software (Epilogue is now owned by WindRiver
   so that code would be the obvious choice) and port it across to VxWorks
   (and for that matter, PSOS).   VxWorks and PSOS are only available with
   a SNMPv1/v2c agent even today, with no prospect for SNMPv3 anytime soon.

	   While theoretically anyone could port the code, in practice a lot
   of the affected companies aren't big enough to have that amount of extra staff
   lying around.  By the way, this also means there is a market for
   a pre-ported (to VxWorks/PSOS) version of any other SNMP code, if someone
   is feeling like a capitalist.

	   If anyone here has the ear of anyone in management at WindRiver Systems,
   it would be a public service to push them to get an SNMPv3 agent available to
   their VxWorks customers ASAP.  The downstream customer demand exists.

	   Sorry for the interruption and thanks for listening.

   Ran
   rja@inet.org




From owner-ietf-outbound  Fri Apr 21 16:01:59 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA24668
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 16:00:02 -0400 (EDT)
Received: from fw-ra06.raytheon.com (fw-ra06.RAYTHEON.COM [192.27.4.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24488
	for <ietf@ietf.org>; Fri, 21 Apr 2000 15:50:30 -0400 (EDT)
Received: from isra02.rsc.raytheon.com (isra02.rsc.raytheon.com [147.19.2.15])
	by fw-ra06.raytheon.com (8.9.1/8.9.1) with ESMTP id MAA23829;
	Fri, 21 Apr 2000 12:50:22 -0700 (PDT)
Received: from electra.rsc.raytheon.com (mail@electra.RSC.RAYTHEON.COM [147.19.52.42])
	by isra02.rsc.raytheon.com (8.9.1/8.9.1) with ESMTP id MAA15201;
	Fri, 21 Apr 2000 12:50:30 -0700 (PDT)
Received: from (ZFUAA373715) [147.19.54.44] 
	by electra.rsc.raytheon.com with smtp (Exim 2.05 #1 (Debian))
	id 12ijRd-0005DG-00; Fri, 21 Apr 2000 12:50:29 -0700
Received: by localhost with Microsoft MAPI; Fri, 21 Apr 2000 12:50:27 -0700
Message-ID: <01BFAB90.2B4C3C40.rascheri@electra.rsc.raytheon.com>
From: "Richard C. Ascheri" <rascheri@electra.rsc.raytheon.com>
Reply-To: "rascheri@electra.rsc.raytheon.com"
	 <rascheri@electra.rsc.raytheon.com>
To: "'John Stracke'" <francis@ecal.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Digital Radio Configuration Question
Date: Fri, 21 Apr 2000 12:50:27 -0700
Organization: Raytheon
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Encoding: 50 TEXT
X-Loop: ietf@ietf.org

John,

I called it the "Limited Broadcast Address" because that is what Richard 
Stevens calls it in his book, "TCP/IP Illustrated Volume 1", which I had 
thought was considered the BIBLE amongst networking professionals.

Secondly, I am aware that no router in the world forwards this address.  It 
says so in the book, and it would be rediculous to do so in the first 
place.

My problem relates to obtaining the IP address of a digital radio which is 
connected to the same physical network as the host, but which you do not 
know it's IP address.  You have no other means of finding out its IP 
address, i.e. no look inside the box.  It does support SNMP, however you 
need an IP address to read its configuration.  Hence, the thought about 
using the limited broadcast address and an ICMP Echo Request message.

As for VxWorks being cautious, no I think it is more of an oversight on 
their part.  I'll have to ask them why....

Thanks,
Rick.


-----Original Message-----
From:	John Stracke [SMTP:francis@ecal.com]
Sent:	Friday, April 21, 2000 11:36 AM
To:	rascheri@electra.rsc.raytheon.com
Subject:	Re: Digital Radio Configuration Question

"Richard C. Ascheri" wrote:

> I wrote a simple program that sends an ICMP Echo Request message to the
> limited broadcast address of 255.255.255.255.

That's not the limited broadcast address; that's the universal broadcast
address, the one that would send a packet to every host in the Internet.  I
say "would" because it's such an obviously bad idea that essentially every
router in the world comes out of the box refusing to forward it.  Most host
software will respond to it, though; VxWorks is probably being cautious.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Do not suspect that I am not human.          |
|francis@ecal.com|                                             |
\==============================================================/





From owner-ietf-outbound  Fri Apr 21 17:51:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA26141
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 17:50:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26064
	for <ietf@ietf.org>; Fri, 21 Apr 2000 17:40:31 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA03931;
        Fri, 21 Apr 2000 17:38:54 -0400 (EDT)
Message-Id: <200004212138.RAA03931@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Greg Hudson <ghudson@mit.edu>
cc: Pyda Srisuresh <srisuresh@yahoo.com>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Fri, 21 Apr 2000 13:55:18 EDT."
             <200004211755.NAA10101@small-gods.mit.edu> 
Date: Fri, 21 Apr 2000 17:38:54 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> In Kerberos 4, when the KDC receives a ticket request, it includes the
> source IP address in the returned ticket.  This works fine if the KDC
> is across a NAT gateway, as long as all of the Kerberos services are
> also across a NAT gateway.

doesn't this require the NAT to use the same inside<->outside address
binding for the connection between the client and the KDC as for
the connection between the client and the application server?
e.g. it seems like the NAT could easily change address bindings 
during the lifetime of a ticket.

Keith



From owner-ietf-outbound  Fri Apr 21 18:21:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA26410
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 18:20:02 -0400 (EDT)
Received: from orchard.arlington.ma.us (orchard.hamachi.org [4.255.0.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26386
	for <ietf@ietf.org>; Fri, 21 Apr 2000 18:17:39 -0400 (EDT)
Received: from orchard.arlington.ma.us (localhost [[UNIX: localhost]])
	by orchard.arlington.ma.us (8.8.8/1.34) with ESMTP id WAA07167;
	Fri, 21 Apr 2000 22:15:22 GMT
Message-Id: <200004212215.WAA07167@orchard.arlington.ma.us>
To: Keith Moore <moore@cs.utk.edu>
cc: Greg Hudson <ghudson@MIT.EDU>, Pyda Srisuresh <srisuresh@YAHOO.COM>,
        ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-Reply-To: Message from Keith Moore <moore@cs.utk.edu> 
   of "Fri, 21 Apr 2000 17:38:54 EDT." <200004212138.RAA03931@astro.cs.utk.edu> 
Date: Fri, 21 Apr 2000 18:15:22 -0400
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
X-Loop: ietf@ietf.org

> doesn't this require the NAT to use the same inside<->outside address
> binding for the connection between the client and the KDC as for
> the connection between the client and the application server?
> e.g. it seems like the NAT could easily change address bindings 
> during the lifetime of a ticket.

Correct.  I think Greg was thinking only of NATs which share a single
global address among multiple clients on a private network...

				- Bill



From owner-ietf-outbound  Fri Apr 21 18:31:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA26519
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 18:30:02 -0400 (EDT)
Received: from small-gods.mit.edu (SMALL-GODS.MIT.EDU [18.177.0.248])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26471
	for <ietf@ietf.org>; Fri, 21 Apr 2000 18:25:25 -0400 (EDT)
Received: (from ghudson@localhost) by small-gods.mit.edu (8.9.3)
	id SAA11987; Fri, 21 Apr 2000 18:25:24 -0400 (EDT)
Message-Id: <200004212225.SAA11987@small-gods.mit.edu>
To: Keith Moore <moore@cs.utk.edu>
cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-Reply-To: Your message of "Fri, 21 Apr 2000 17:38:54 EDT."
             <200004212138.RAA03931@astro.cs.utk.edu> 
Date: Fri, 21 Apr 2000 18:25:24 -0400
From: Greg Hudson <ghudson@MIT.EDU>
X-Loop: ietf@ietf.org

> doesn't this require the NAT to use the same inside<->outside
> address binding for the connection between the client and the KDC as
> for the connection between the client and the application server?
> e.g. it seems like the NAT could easily change address bindings
> during the lifetime of a ticket.

True.  However, the same problem applies without NAT if the client
changes address bindings, so I wouldn't say this is really a
NAT-related problem.



From owner-ietf-outbound  Fri Apr 21 18:51:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA26729
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 18:50:02 -0400 (EDT)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26676
	for <ietf@ietf.org>; Fri, 21 Apr 2000 18:41:33 -0400 (EDT)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id PAA26627;
	Fri, 21 Apr 2000 15:38:51 -0700 (PDT)
Received: from p7020-img-nt.cisco.com (sj-dial-1-22.cisco.com [171.68.179.23]) by rhino (SMI-8.6/CISCO.WS.1.1) with ESMTP id PAA03436; Fri, 21 Apr 2000 15:46:06 -0700
Message-Id: <4.3.1.2.20000421235346.0319bcd0@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 21 Apr 2000 23:54:18 +0800
To: "Anders Feder" <lists.anders@feder.dk>
From: Fred Baker <fred@cisco.com>
Subject: Re: Universal Network Language
Cc: <ietf@ietf.org>
In-Reply-To: <008f01bfab0b$a7532fe0$1000000a@DIC>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 11:01 PM 4/20/00 +0200, Anders Feder wrote:
>The translation system being developed for the United Nations, the Universal
>Network Language (UNL), looks quite promising. Does the IETF have any plans
>regarding this system?

not specifically. Care to make an argument that we should?



From owner-ietf-outbound  Fri Apr 21 19:01:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA26841
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 19:00:01 -0400 (EDT)
Received: from watsun.cc.columbia.edu (IDENT:cu51491@watsun.cc.columbia.edu [128.59.39.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26760
	for <ietf@ietf.org>; Fri, 21 Apr 2000 18:51:32 -0400 (EDT)
Received: (from jaltman@localhost)
	by watsun.cc.columbia.edu (8.8.5/8.8.5) id SAA29280;
	Fri, 21 Apr 2000 18:51:29 -0400 (EDT)
Date: Fri, 21 Apr 2000 18:51:28 EDT
From: Jeffrey Altman <jaltman@columbia.edu>
Reply-To: jaltman@columbia.edu
To: Greg Hudson <ghudson@MIT.EDU>
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: Your message of Fri, 21 Apr 2000 18:25:24 -0400
Message-ID: <CMM.0.90.4.956357488.jaltman@watsun.cc.columbia.edu>
X-Loop: ietf@ietf.org

> > doesn't this require the NAT to use the same inside<->outside
> > address binding for the connection between the client and the KDC as
> > for the connection between the client and the application server?
> > e.g. it seems like the NAT could easily change address bindings
> > during the lifetime of a ticket.
> 
> True.  However, the same problem applies without NAT if the client
> changes address bindings, so I wouldn't say this is really a
> NAT-related problem.
> 

Under what conditions transparent to the user does a client change
address bindings?



    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org




From owner-ietf-outbound  Fri Apr 21 19:11:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA26992
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 19:10:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26781
	for <ietf@ietf.org>; Fri, 21 Apr 2000 18:51:53 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id SAA04230;
        Fri, 21 Apr 2000 18:50:34 -0400 (EDT)
Message-Id: <200004212250.SAA04230@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Greg Hudson <ghudson@MIT.EDU>
cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Fri, 21 Apr 2000 18:25:24 EDT."
             <200004212225.SAA11987@small-gods.mit.edu> 
Date: Fri, 21 Apr 2000 18:50:33 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> > doesn't this require the NAT to use the same inside<->outside
> > address binding for the connection between the client and the KDC as
> > for the connection between the client and the application server?
> > e.g. it seems like the NAT could easily change address bindings
> > during the lifetime of a ticket.
> 
> True.  However, the same problem applies without NAT if the client
> changes address bindings, 

granted, but how often do clients change address bindings in practice?

> so I wouldn't say this is really a NAT-related problem.

of course it's a NAT-related problem, in the sense that if you
have a NAT box and want to use Kerberos you are highly likely
to observe the problem.

for almost every kind of harm that NATs do to applications you can 
find some other means of causing the same problem.  but just because 
the problem can be caused by other things doesn't mean it's not 
related to NATs. 

Keith



From owner-ietf-outbound  Fri Apr 21 20:31:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA27609
	for ietf-outbound.10@ietf.org; Fri, 21 Apr 2000 20:30:02 -0400 (EDT)
Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA27555
	for <ietf@ietf.org>; Fri, 21 Apr 2000 20:27:44 -0400 (EDT)
Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP
	id AA13916; Fri, 21 Apr 00 20:29:38 EDT
Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45])
	by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id UAA27712;
	Fri, 21 Apr 2000 20:27:40 -0400 (EDT)
Received: from miles-davis (MUCKLEY-TWO-SEVENTY-TWO.MIT.EDU [18.172.6.16])
	by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id UAA08744;
	Fri, 21 Apr 2000 20:27:40 -0400 (EDT)
Message-Id: <4.2.0.58.20000421202317.01dbb0a0@po12.mit.edu>
X-Sender: pbh@po12.mit.edu (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Fri, 21 Apr 2000 20:27:35 -0400
To: Keith Moore <moore@cs.utk.edu>, Greg Hudson <ghudson@MIT.EDU>
From: "Paul B. Hill" <pbh@MIT.EDU>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
Cc: Pyda Srisuresh <srisuresh@YAHOO.COM>, ietf@ietf.org
In-Reply-To: <200004212138.RAA03931@astro.cs.utk.edu>
References: <Your message of "Fri, 21 Apr 2000 13:55:18 EDT." <200004211755.NAA10101@small-gods.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 05:38 PM 4/21/2000 -0400, Keith Moore wrote:

>doesn't this require the NAT to use the same inside<->outside address
>binding for the connection between the client and the KDC as for
>the connection between the client and the application server?
>e.g. it seems like the NAT could easily change address bindings
>during the lifetime of a ticket.

Yup, so far I have always been able to work around this by opening up an 
SSL IMAP connection to remote server to stablize the address while I need 
to do other work. Oh the fun games we encounter when mixing security and 
NATs :)

Paul



From owner-ietf-outbound  Sat Apr 22 05:51:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA14326
	for ietf-outbound.10@ietf.org; Sat, 22 Apr 2000 05:50:03 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14303
	for <ietf@ietf.org>; Sat, 22 Apr 2000 05:48:37 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id FAA01188;
	Sat, 22 Apr 2000 05:48:36 -0400
Date: Sat, 22 Apr 2000 05:48:36 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200004220948.FAA01188@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: jnc@ginger.lcs.mit.edu, moore@cs.utk.edu
X-Loop: ietf@ietf.org

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

    > there are far too many problems to NAT, affecting far too many
    > applications ... and the list is constantly growing larger.

Perhaps if there was a document that explained how to design an application
so that it worked through a NAT box, the list might not be growing so quickly?

Although I wouldn't want to be the person to write such a document, since
they're going to have to wade through hordes of flak from people who seem to
convinced that if they just flame enough about how worthless NAT boxes are,
and how they ought to be banned/exterminated, NAT boxes will go away. ("Back,
tides!")


We could also contemplate the possibility of producing fixes for old things
that NAT boxes break, but on the record so far, I'm not very sanguine.

(The enquiring mind wonders why this isn't happening - but doesn't have to
look too far. In addition to the usual IETF problem of too many problems and
too few people, there's the other camel in the tent, to whit - whose ox will
be gored if we make NAT boxes work better? And who will be the big losers if
we don't make NAT work better - why, the users, of course. But who cares
about them?)

For a classic example, look at the recommendations of the IAB Workshop last
year about IPSEC (and I'll asssume for the moment that IPSec is important to
securing the Internet, and stay away from the debates about IPSEC versus SSL,
etc):

   It is urgent that we implement and deploy IPsec using some other
   identifier than 32-bit IP addresses ... The current IPsec specifications
   support the use of several different Identity types (e.g. Domain Name,
   User@Domain Name). ... We strongly urge the IETF to completely
   deprecate the use of the binary 32-bit IP addresses within IPsec
   ... in particular any IP address dependencies should be eliminated from
   ISAKMP and IKE. Ubiquitous deployment of the Secure DNS Extensions ([8])
   should be strongly encouraged to facilitate widespread deployment of IPsec
   (including IKE) without address-based Identity types.

So, has any of this happened? AFAIK, no; I may be wrong, but I don't recall
seeing anything about either deprecating use of address-based identities, or a
fix to IKE/etc to remove all address dependencies.  Sure, everyone's busy, but
has anyone in the IAB/IESG/etc been tasked with making this happen?

The really ironic thing about this particular case is that people who want to
deploy IPv6 would probably benefit from this particular fix, too. Right now,
as far as I can tell (sorry, it's been a while since I looked at this, and the
details made my eyes glaze over), a number of the different IPv4<->IPv6
interoperability tools don't work with IPSec, both because of the use of
address-based identities, and address dependencies in IKE. Removing these
dependencies might allow IPSec to work in IPv4<->IPv6 interactions.

But has anything happened here? Nope. Can't do anything to make NAT boxes
work better, can we?


Even more radically, we could start requiring that new stuff works through
NAT boxes. What a concept!

While to an objective observer that might seem like a fairly reasonable step,
given how widely NAT boxes are deployed, G-d forbid we do anything so
rational. I mean, who cares if we screw over the users, that's their own
fault for not realizing how tasteless NAT is.

Damn the users, full steam ahead!

	Noel



From owner-ietf-outbound  Sat Apr 22 08:21:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA15254
	for ietf-outbound.10@ietf.org; Sat, 22 Apr 2000 08:20:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15201
	for <ietf@ietf.org>; Sat, 22 Apr 2000 08:14:36 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200004221206.VAA03371@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id VAA03371; Sat, 22 Apr 2000 21:06:05 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <200004220948.FAA01188@ginger.lcs.mit.edu> from "J. Noel Chiappa"
 at "Apr 22, 2000 05:48:36 am"
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Date: Sat, 22 Apr 2000 21:06:04 +0859 ()
CC: ietf@ietf.org, moore@cs.utk.edu
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Noel;

>     > From: Keith Moore <moore@cs.utk.edu>
> 
>     > there are far too many problems to NAT, affecting far too many
>     > applications ... and the list is constantly growing larger.
> 
> Perhaps if there was a document that explained how to design an application
> so that it worked through a NAT box, the list might not be growing so quickly?
> 
> Although I wouldn't want to be the person to write such a document, since
> they're going to have to wade through hordes of flak from people who seem to
> convinced that if they just flame enough about how worthless NAT boxes are,
> and how they ought to be banned/exterminated, NAT boxes will go away. ("Back,
> tides!")

You might have thought that NAT had made the Internet a collection of
private IP networks, which were acceptable.

However, the real problem of NAT is not of NAT itself but of NAT based
applicatins which are so network layer independent that they work over
non-IP networks.

NAT and NAT friendly application/transport protocols makes the Internet
a collection of private non-IP networks.

NAT is killing not only the Internet but also the IP protocol and a
standardization body for it.

For example, NAT friendly application/transport protocols for IP
telephony are H.323 and SIP.

Because SIP is so complex (even worse than H.323) and has no difficulty
to accomodate non-IP environment, SIP has lost the battle against H.323.

For telephony, the real battle should be fought between Internet
telephony and IP telephony over NAT with H.323 (Internet telephony
without NAT and IP telephony with NAT are opposite concepts).

The next thing to see is, what will happen between WAP and HTTP?

							Masataka Ohta



From owner-ietf-outbound  Sat Apr 22 11:22:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA16333
	for ietf-outbound.10@ietf.org; Sat, 22 Apr 2000 11:20:03 -0400 (EDT)
Received: from web1406.mail.yahoo.com (web1406.mail.yahoo.com [128.11.23.170])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA16262
	for <ietf@ietf.org>; Sat, 22 Apr 2000 11:05:18 -0400 (EDT)
Received: (qmail 10228 invoked by uid 60001); 22 Apr 2000 15:05:17 -0000
Message-ID: <20000422150517.10227.qmail@web1406.mail.yahoo.com>
Received: from [209.239.202.152] by web1406.mail.yahoo.com; Sat, 22 Apr 2000 08:05:17 PDT
Date: Sat, 22 Apr 2000 08:05:17 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: jaltman@COLUMBIA.EDU, Pyda Srisuresh <srisuresh@yahoo.com>
Cc: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org


--- Jeffrey Altman <jaltman@COLUMBIA.EDU> wrote:
> I have so many issues with this reply that I am only going to focus on
> one.
> 
> > Agreed. How do you expect the intruders  will steal the tickets, without
> > being recipients of the ticket? Unless, you are assuming that the private
> > network is not trusted and that there are intruders within the private 
> > network.
> 
> There is no such thing as a trusted network.  One of the first things
> you learn about security (having nothing to do with computer security)
> is that most attacks occur from inside the organization.  There is no
> such thing as a trusted network.
> 

I hear what you say. Thanks.

> I have pointed you in directions you need to follow.  Stating that the
> a problem in one context is described in the described in another
> context is not useful in this document.  It is exactly because of this
> approach that the document comes across sounding as if the problems
> described are trivial and inconsequential.
> 
> 

Dont get me wrong. I was not suggesting that it suffices to point out
one end of the problem (ex: X-Windows Server redirection). I was merely
stating that the document covered one end, but failed to cover the other
end of the problem (i.e., Setting the DISPLAY variable from a Telnet 
session, using an IP address).
  
> 
>     Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
>                  The Kermit Project * Columbia University
>               612 West 115th St #716 * New York, NY * 10025
>   http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org
> 
> 

cheers,
suresh

=====


__________________________________________________
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com



From owner-ietf-outbound  Sat Apr 22 11:32:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA16414
	for ietf-outbound.10@ietf.org; Sat, 22 Apr 2000 11:30:04 -0400 (EDT)
Received: from tsx-prime.MIT.EDU (TSX-PRIME.MIT.EDU [18.86.0.76])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA16277
	for <ietf@ietf.org>; Sat, 22 Apr 2000 11:10:33 -0400 (EDT)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id LAA28261; Sat, 22 Apr 2000 11:10:31 -0400
Date: Sat, 22 Apr 2000 11:10:31 -0400
Message-Id: <200004221510.LAA28261@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
CC: ietf@ietf.org, jnc@ginger.lcs.mit.edu, moore@cs.utk.edu
In-reply-to: J. Noel Chiappa's message of Sat, 22 Apr 2000 05:48:36 -0400,
	<200004220948.FAA01188@ginger.lcs.mit.edu>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   Date: Sat, 22 Apr 2000 05:48:36 -0400
   From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>

       > there are far too many problems to NAT, affecting far too many
       > applications ... and the list is constantly growing larger.

   Perhaps if there was a document that explained how to design an application
   so that it worked through a NAT box, the list might not be growing so
   quickly? 

   Although I wouldn't want to be the person to write such a document, since
   they're going to have to wade through hordes of flak from people who seem to
   convinced that if they just flame enough about how worthless NAT boxes are,
   and how they ought to be banned/exterminated, NAT boxes will go
   away. ("Back, tides!")

The list can also be useful in terms of really documenting for the first
time, in one places, all of the ways that application writer's hands are
tied if they want to be survive running through a NAT.  

If all you want to do is a single TCP connection, it's not so bad.  But
the moment you want to do any kind of back-connection, or to be able to
associate multiple connections in either direction, life gets hard.
What's the answer?  Tell the application programmer, "Well, don't do
that!"?  Tell them to do IP-IP tunnelling?  Tell them to invent their
own streaming layer on top of TCP, ala ssh?

And if you want to design a new UDP protocol, what can you depend upon
for a NAT box to do?  Will it pass unrecognized UDP protocols at all?
How will it handle port translations?  Will it keep state?  

   For a classic example, look at the recommendations of the IAB Workshop last
   year about IPSEC (and I'll asssume for the moment that IPSec is important to
   securing the Internet, and stay away from the debates about IPSEC
   versus SSL, etc):

      It is urgent that we implement and deploy IPsec using some other
      identifier than 32-bit IP addresses ... The current IPsec specifications
      support the use of several different Identity types (e.g. Domain Name,
      User@Domain Name). ... We strongly urge the IETF to completely
      deprecate the use of the binary 32-bit IP addresses within IPsec
      ... in particular any IP address dependencies should be eliminated from
      ISAKMP and IKE. Ubiquitous deployment of the Secure DNS Extensions ([8])
      should be strongly encouraged to facilitate widespread deployment
      of IPsec (including IKE) without address-based Identity types.

Well, where's Secure DNS deplyoment?  :-)

More seriously, Secure DNS by itself isn't enough.  We also need to
mandate that NAT boxes provide certain types of infrastructure in terms
of dynamic updating of DNS servers, *and* a split-DNS configuration that
gives correct inside/outside responses.  Part of the problem with
relying on DNS names instead is that this assumes that DNS/NAT games are
(a) set up consistently, or (b) set up at all.  Some ISP's or Company
setups may do NAT's, but not provide any kind of consistent DNS
addresses, either forwards or backwards resolution.  Also, from an
implementation point of view, there isn't even a good way for you to
obtain a globally usable FQDN on most OS's.

The real issue is that NAT's are still considered a hack.  And hacks
don't necessarily have the full set of support infrastructure behind
them so they can be used reliably.  So while it's granted that there
hasn't been anyone on the IPSEC wg with interest in this area, it's also
fair to say that even if they were interested, they'd immediately run
across another problem of it's not clear what kind of support
infrastructure you can rely upon.  (And if the support infrastructure
doesn't exist in the real world, spending man-years writing a spec that
presumes the existince of such a support infrastructure is just as
Cannutish as saying "Back, Tides!")

Maybe what is needed is a new IRTF working group --- the Anti-End2End
group.  It's charter will be "the end to end principle is dead", and
they can try to figure out everything that will be needed to turn the IP
address into a 32-bit local routing entity.  After all, this is a
fundamental architectural principal that we will be overturning, and it
will probably have impacts all over the stack.  And after they come up
with the plan of everything that will have to change, people can look at
it, and say, "Oh, ugh, maybe that wasn't such a hot idea after all", or
"Gee, I guess while it's horrible, it's easier than trying to get IPV6
deployed."

Right now, NAT and other attacks on the end-to-end model are being done
as a series of hill-climbing optimizations, with no real attempt to see
if they can solve the entire problem or not.  (After all, they're just
hacks, right?  And everyone knows there's nothing more to the Internet
than http and e-mail anyway....)

IMHO the problem is that we're stuck halfway.  Either NAT's are a
fundamental part of the architecture, and we have to try to figure out
*everything* that has to change in order to accomodate them as
first-class objects, or they are hacks and kludges which should go away,
and we should be working towards that goal.  Right now, we're just
completely schizophrenic on the issue, and that's not helpful.

The question is, how to decide the issue.  Super-soakers at 24 paces,
perhaps?  :-)

						- Ted

P.S.  An interesting observation with NAT is that it's really the
newcomers to the internet, both in terms of protocols and users, that
suffer the most.  Old users are grandfathered because they can get have
the class B's addresses in the swamp, and don't need to use NAT.  Old
protocols (with the exception of those that do encryption), can depend
on the NAT boxes doing some truely awful stuff (like rewriting FTP's
command channel, and all of the TCP checksum games that have to take
place) to make their protocols work.  It's really the newer users,
especially those that are using cable modems and ADSL users, and the
people who want to write newer protocols, that end up getting contrained
by NAT.

Speaking personally, I knew about these issues, so when I got my home
DSL connection, I insisted on getting a /27 from my provider, and
fortunately I (or more precisely my company) was willing to pay the
money to get a real address block, so I didn't have to deal with NAT.  I
decided I didn't want to have to waste time with trying to make NAT
work, and it was simply cheaper to get real addresses.  I had more
important things to do.

Other folks who are saavy enough can usually find contacts at places
with free address space, and so they're playing tunneling games so they
can get chunks of un-NAT-ed address space, even if their local provider
refuses to give it to them.  A number of these people are IETF'ers.  :-)

So not only do we have the usual IETF problem of too many problems and
too few people with clue, it's probably less effort for those who *can*
fix the problem (and I include either IPV6 or fixing NAT in this
category) to evade the problem completely, one way or another --- at
least at a personal level.



From owner-ietf-outbound  Sat Apr 22 12:02:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA16653
	for ietf-outbound.10@ietf.org; Sat, 22 Apr 2000 12:00:03 -0400 (EDT)
Received: from web1406.mail.yahoo.com (web1406.mail.yahoo.com [128.11.23.170])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA16598
	for <ietf@ietf.org>; Sat, 22 Apr 2000 11:50:37 -0400 (EDT)
Received: (qmail 14826 invoked by uid 60001); 22 Apr 2000 15:50:37 -0000
Message-ID: <20000422155037.14825.qmail@web1406.mail.yahoo.com>
Received: from [209.239.202.152] by web1406.mail.yahoo.com; Sat, 22 Apr 2000 08:50:37 PDT
Date: Sat, 22 Apr 2000 08:50:37 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org


--- "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu> wrote:
>     > From: Keith Moore <moore@cs.utk.edu>
> 
>     > there are far too many problems to NAT, affecting far too many
>     > applications ... and the list is constantly growing larger.
> 
> Perhaps if there was a document that explained how to design an application
> so that it worked through a NAT box, the list might not be growing so
> quickly?
> 

There actually is a draft titled "NAT Friendly Application Design Guidelines"
< draft-ietf-nat-app-guide-02.txt> attempting to do just that. I do believe,
this can be very valuable to future application developers that need to 
deploy their apps in networks with NAT devices.

Thanks for bringing this up. If someone has valuable input on this, please
send the same to the draft author. Thanks. 

<... Text deleted>

regards,
suresh

__________________________________________________
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com



From owner-ietf-outbound  Sat Apr 22 12:11:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA16829
	for ietf-outbound.10@ietf.org; Sat, 22 Apr 2000 12:10:03 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16619
	for <ietf@ietf.org>; Sat, 22 Apr 2000 11:55:04 -0400 (EDT)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id LAA03556;
	Sat, 22 Apr 2000 11:55:02 -0400 (EDT)
Sender: hgs@cs.columbia.edu
Message-ID: <3901CB56.61EC7B8A@cs.columbia.edu>
Date: Sat, 22 Apr 2000 11:55:02 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Pyda Srisuresh <srisuresh@yahoo.com>
CC: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
References: <20000422150517.10227.qmail@web1406.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

It might be useful to point out more clearly the common characteristics
of protocols that are broken by NATs. These include, in particular,
protocols that use one connection to establish another data flow. Such
protocols include ftp, SIP and RTSP (the latter is not mentioned yet in
the draft, but NATs also interfere with its operation). Note that unless
we forego such control protocol designs altogether, NATs in principle
break these unless every host has an external DNS mapping. (Thus, in
reference to a recent message to just design NAT-friendly protocols,
this means in practice that such "out-of-band" designs could not be
supported by this NATy version of the Internet. In effect, this leads to
the abomination of carrying real-time data in HTTP connections.)

Other protocol designs are those that are symmetric rather than
client-server based. This affects all Internet telephony or event-based
protocols (IM and generalizations) unless they maintain an outbound
connection with a server acting as their representative to the globally
routed Internet. The latter obviously does not address the media stream
addressing problems.

-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



From owner-ietf-outbound  Sat Apr 22 13:31:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA17346
	for ietf-outbound.10@ietf.org; Sat, 22 Apr 2000 13:30:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17305
	for <ietf@ietf.org>; Sat, 22 Apr 2000 13:25:14 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id NAA02164;
	Sat, 22 Apr 2000 13:25:12 -0400
Date: Sat, 22 Apr 2000 13:25:12 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200004221725.NAA02164@ginger.lcs.mit.edu>
To: ietf@ietf.org, moore@cs.utk.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

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

    >> I'm not exactly a big fan of NAT boxes either. Disgusting kludges.

    >> However, I've generally found that it's not really very useful to go
    >> around saying "it's not really raining, it's not really raining" while
    >> I'm walking in a thunderstorm.....
 
    > nobody is saying that it isn't raining.

Look, I have on my disk a file from June, 1992 (yes, that's not a typo -
*1992*) called "Problems with NAT".

However, as a close personal friend of the patron saint of Lost Causes (see
all the scars on my forehead? :-), let me tell you that I have (painfully :-)
learned to recognize a lost cause when I see one, and trying to put the NAT
geni back in the bottle definitely counts.

It's raining NAT's. Deal with it.


    >> I think we can regain the "end-end model", even with NAT boxes, if we
    >> accept that those 32-bit things are irrevocably destined to become just
    >> forwarding tags with only local scope.
 
    > we might regain the "end to end model" from doing this but we would
    > still prevent a lot of applications from working well. ... so a model
    > that assumes that everything is connection-oriented and can therefore
    > afford connection setup overhead ... doesn't look very attractive to me.
 
I'm not trying to deny there are real problems with the NAT world (and you've
pointed out at least very serious one - I wasn't sure of what you meant by
the others).

In fact, I 'embrace' NAT only in order to build things that enable us to
throw away NAT - ASAP!

And it won't be easy - but there is *no* forward path for growing the
Internet which is easy. Whatever we do, it's going to be painful.

But I don't think a forklift upgrade is workable in today's Internet. We have
to find an path consisting of many incremental steps. E.g. we have to build a
new end-end namespace, and modify applications one by one to use it. (That
still won't fix some of the problems you allude to, but's it's a necessary
preliminary step.) Then, with that as a fixed reference, we can more easily
deploy new location 'names'.


    > and I have yet to see someone who recommends that approach demonstrate
    > how to recover the functionality that you lose by doing so.

Well, the goal is to throw away NATs eventually (like 10 years down the road,
at the pace the gigantic beast called the Internet moves now). But we can't
get there unless we embrace NAT's in the short term.

    > except for the dubious benefit of NAT compatibility, I haven't been
    > able to figure out why it's so important to have yet another form of
    > local forwarding tag

Simple; I don't think anyone working with NAT's has any interest in another
form of local forwarding tag! People don't give a rat's anterior about
another local forwarding tag. They treat them that way because they have to,
not because they need/want a local forwarding tag.


    >> But it will have to be an incremental approach back to goodness, I
    >> fear...
 
    > if you mean an approach that can be deployed incrementally, I agree.

Good, something we concur on - although I suspect my "incremental" is perhaps
a lot more incremental than you realize.

    > the top of the NAT hill is a long way from goodness.

Absolutely. Which is why it's important to throw NAT's away as soon as we
can.

	Noel



From owner-ietf-outbound  Sat Apr 22 17:21:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA19028
	for ietf-outbound.10@ietf.org; Sat, 22 Apr 2000 17:20:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18926
	for <ietf@ietf.org>; Sat, 22 Apr 2000 17:10:31 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA00745;
        Sat, 22 Apr 2000 17:10:04 -0400 (EDT)
Message-Id: <200004222110.RAA00745@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: ietf@ietf.org, moore@cs.utk.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Sat, 22 Apr 2000 13:25:12 EDT."
             <200004221725.NAA02164@ginger.lcs.mit.edu> 
Date: Sat, 22 Apr 2000 17:10:03 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Look, I have on my disk a file from June, 1992 (yes, that's not a typo -
> *1992*) called "Problems with NAT".
> 
> However, as a close personal friend of the patron saint of Lost Causes (see
> all the scars on my forehead? :-), let me tell you that I have (painfully :-)
> learned to recognize a lost cause when I see one, and trying to put the NAT
> geni back in the bottle definitely counts.
> 
> It's raining NAT's. Deal with it.

understood.  it's just that part of my strategy for dealing with the 
NAT problem is to try to counteract the "NATs are wonderful and don't
really cause any signifcant problems that can't be fixed with ALGs" 
propaganda that's being generated from some corners.  NATs are a big
problem for the Internet and we can't really solve it until folks realize 
that there's a problem. 

and just because I'm arguing against the above kinds of statements doesn't 
mean that I think we can convince folks to just discard their NATs.  I do 
however think that folks may be willing to upgrade and/or replace their 
NATs once something better exists that allows them to run applications that
they can't run with current NATs.  and I don't know of any way to 
improve things that doesn't require replacing/upgrading NATs in some sense.

another part of my strategy is to counteract the "we need to move away 
from using addresses as endpoint IDs" argument, which I might restate
as "we don't really need endpoint IDs which allow network addresses
to be algorithmically derived from them". because in my experience 
endpoint IDs that are not resolvable into network addresses aren't 
very useful, and endpoint IDs that require a distributed database lookup 
to translate them into network addresses are slow, inefficient, expensive, 
and error prone.

I do understand that there are scaling difficulties at the routing layer 
associated with having network addresses be derivable from endpoint IDs,
(e.g. having them be both stable and globally scoped) even though I 
don't think I could accurately describe those problems.  


>     >> I think we can regain the "end-end model", even with NAT boxes, if we
>     >> accept that those 32-bit things are irrevocably destined to become just
>     >> forwarding tags with only local scope.
>  
>     > we might regain the "end to end model" from doing this but we would
>     > still prevent a lot of applications from working well. ... so a model
>     > that assumes that everything is connection-oriented and can therefore
>     > afford connection setup overhead ... doesn't look very attractive to me.
>  
> I'm not trying to deny there are real problems with the NAT world (and you've
> pointed out at least very serious one - I wasn't sure of what you meant by
> the others).
> 
> In fact, I 'embrace' NAT only in order to build things that enable us to
> throw away NAT - ASAP!
> 
> And it won't be easy - but there is *no* forward path for growing the
> Internet which is easy. Whatever we do, it's going to be painful.

agreed.
 
> But I don't think a forklift upgrade is workable in today's Internet. We have
> to find an path consisting of many incremental steps. 

I guess I think that forklift upgrades might be possible, but those 
have to be incremental as well - and the folks who pay for the upgrades 
have to see some benefit from doing so.

> E.g. we have to build a
> new end-end namespace, and modify applications one by one to use it. (That
> still won't fix some of the problems you allude to, but's it's a necessary
> preliminary step.) Then, with that as a fixed reference, we can more easily
> deploy new location 'names'.

I agree that applications will need to adapt to a new end to end namespace,
because a 32 bit space isn't enough for the long term even if the bits 
had no significance at all for network topoligy.   (you still would need
to have hierarchical delegation of the namespace and the associated 
inefficiences, just so that assignment would scale)

>     > and I have yet to see someone who recommends that approach demonstrate
>     > how to recover the functionality that you lose by doing so.
> 
> Well, the goal is to throw away NATs eventually (like 10 years down the road,
> at the pace the gigantic beast called the Internet moves now). But we can't
> get there unless we embrace NAT's in the short term.

this is not clear to me.  I understand that folks are going to use NATs
when NATs meet their immediate needs and when getting non NATted addresses
is too painful.  but there is an increasing demand for devices and 
applications that do not work well with NAT.
 
>     > except for the dubious benefit of NAT compatibility, I haven't been
>     > able to figure out why it's so important to have yet another form of
>     > local forwarding tag
> 
> Simple; I don't think anyone working with NAT's has any interest in another
> form of local forwarding tag! People don't give a rat's anterior about
> another local forwarding tag. They treat them that way because they have to,
> not because they need/want a local forwarding tag.

okay, so you're not arguing that the architecture inherently needs more local
forwarding tags, but simply that this is the environment that NATs give us,
and if we can find a solution that works within that environment, we're 
better off.  I guess I don't see a way to actually solve applications' 
problems that doesn't either require some changes to the NAT (whether by a 
forklift or a rom upgrade), or requires that the NATted IP network be
treated as a link layer and that the "real" traffic be tunneled over it.  
(which is equivalent in difficulty to a forklift upgrade and more complex)
and if we're going to need to change the NATs anyway I'd just as soon
change them in such a way that we're back to having endpoint IDs
from which network addresses can be algorithmically derived.

> 
>     >> But it will have to be an incremental approach back to goodness, I
>     >> fear...
>  
>     > if you mean an approach that can be deployed incrementally, I agree.
> 
> Good, something we concur on - although I suspect my "incremental" is perhaps
> a lot more incremental than you realize.
> 
>     > the top of the NAT hill is a long way from goodness.
> 
> Absolutely. Which is why it's important to throw NAT's away as soon as we
> can.

sure.  see we do agree on some things!

Keith



From owner-ietf-outbound  Sat Apr 22 17:51:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA19474
	for ietf-outbound.10@ietf.org; Sat, 22 Apr 2000 17:50:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19444
	for <ietf@ietf.org>; Sat, 22 Apr 2000 17:48:43 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA00997;
        Sat, 22 Apr 2000 17:48:15 -0400 (EDT)
Message-Id: <200004222148.RAA00997@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
cc: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, ietf@ietf.org,
        moore@cs.utk.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Sat, 22 Apr 2000 11:10:31 EDT."
             <200004221510.LAA28261@tsx-prime.MIT.EDU> 
Date: Sat, 22 Apr 2000 17:48:15 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

>    Date: Sat, 22 Apr 2000 05:48:36 -0400
>    From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
> 
>        > there are far too many problems to NAT, affecting far too many
>        > applications ... and the list is constantly growing larger.
> 
>    Perhaps if there was a document that explained how to design an application
>    so that it worked through a NAT box, the list might not be growing so
>    quickly? 

here's a stab at one:

if you want your application to work with NATs:
(in light of both NATs and other typical conditions)

	- either make it two-party only (e.g. strict client/server). 
	  or have a central party that contacts all of the other
	  parties and looks up those addresses using their DNS names.
	  you cannot expect to set up arbitrary communications paths. 
	- don't make any assumption at all about the meanings of,
	  stability of, or uniqueness of, the IP address of the 
          communicating parties 
	- use TCP only, with short-lived connections 
	  (say, no more than a few minutes, or no more than the TTL
	   of the A record returned from the DNS lookup)
	- instruct your customers that all servers (i.e. all parties that 
          accept connections rather than initiate them) which need to
	  communicate with clients on the other side of a NAT, must be
	  located in public address space.
	- use DNS names, rather than IP addresses, to identify your endpoints
	  for the purpse of reaching them across the net 
	- all DNS names used in this way need to be evaluated from the same
	  point.
	- if you need to log events, assign each party a unique name for 
	  logging purposes.  don't rely on either the IP address or the
	  DNS name.
	- authenticate using TLS and client certs rather than IPsec.
	- bind your servers to well-known ports rather than 
	  having them dynamically assigned 
	- do a DNS lookup of your destination immediately before
	  setting up each TCP connection.
	- don't rely on an DNS inverse address (PTR) lookup to give you the 
	  name of a process/service for the purpose of reaching it later
	- don't rely on a process's idea of its own DNS name for the purpose
	  of reaching it later - many hosts don't know their own names.
	- if your application needs to access multiple services on the 
	  same host (e.g. NFS mount and NFS access), multiplex all 
	  of those service requests on the same port.   don't assume
	  that port A on host address X and port B on host address X 
	  actually reach the same host.  
        - similarly, don't do protocol feature negotiation using port 
          numbers, and don't do protocol version negotiation using port 
          numbers.  design your protocol so that it can negotiate
          version and/or features in-band.  this includes use of tls/ssl
	  if this is optional.

if you find that you cannot make your application work under these conditions:

	- attempt to detect the presence of NATs so that you can display
	  a reasonable error message.  e.g.

	  you have a NAT installed between A and B and this application
	  fundamentally cannot work over a NAT.

	  or

	  you have a NAT installed between A and B.  this application 
	  cannot work over a NAT without the explicit support in the
	  NAT for this application.  contact your NAT vendor to determine
	  whether your NAT can be modified to support this application.
	
> The list can also be useful in terms of really documenting for the first
> time, in one places, all of the ways that application writer's hands are
> tied if they want to be survive running through a NAT.  

http://www.cs.utk.edu/~moore/what-nats-break.html
is an approximation of the latter kind of list.

> More seriously, Secure DNS by itself isn't enough.  We also need to
> mandate that NAT boxes provide certain types of infrastructure in terms
> of dynamic updating of DNS servers, *and* a split-DNS configuration that
> gives correct inside/outside responses.  

this might help in some ways, but it's not at all clear that it would
be a good idea overall.  Just because some NATs mung DNS records in
an attempt to fit in better doesn't mean that going further down this
path is architecturally sound.

> The real issue is that NAT's are still considered a hack.  And hacks
> don't necessarily have the full set of support infrastructure behind
> them so they can be used reliably.  

some things are inherently hacks.  it isn't clear that you can make
network address translation work reliably even if you add more stuff 
to those boxes. 

> Maybe what is needed is a new IRTF working group --- the Anti-End2End
> group.  It's charter will be "the end to end principle is dead", and
> they can try to figure out everything that will be needed to turn the IP
> address into a 32-bit local routing entity.  

seems like the NAT group is already a close approximation to that.
and somehow I doubt that such a group would attract enough people who
really understand the needs of applications, and the tradeoffs,
to produce a decent solution.

if we're going to compare various ways of attacking the NAT problem,
we first need to get some shared understanding of what kinds of service
the brave new network would need to provide.  otherwise, we have no
basis with which to compare the various solutions.

> IMHO the problem is that we're stuck halfway.  Either NAT's are a
> fundamental part of the architecture, and we have to try to figure out
> *everything* that has to change in order to accomodate them as
> first-class objects, or they are hacks and kludges which should go away,
> and we should be working towards that goal.  Right now, we're just
> completely schizophrenic on the issue, and that's not helpful.

yes.

Keith



From owner-ietf-outbound  Sat Apr 22 22:11:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA22443
	for ietf-outbound.10@ietf.org; Sat, 22 Apr 2000 22:10:03 -0400 (EDT)
Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22403
	for <ietf@ietf.org>; Sat, 22 Apr 2000 22:08:49 -0400 (EDT)
Received: from laptop.ix.netcom.com ([209.138.5.30])
	by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id WAA05098;
	Sat, 22 Apr 2000 22:08:36 -0400 (EDT)
Message-Id: <4.3.2.20000422201841.00c435d0@127.0.0.1>
X-Sender: rshockey/popd.ix.netcom.com@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Sat, 22 Apr 2000 21:08:35 -0500
To: Keith Moore <moore@cs.utk.edu>, "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
From: Richard Shockey <rshockey@ix.netcom.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
Cc: ietf@ietf.org, moore@cs.utk.edu
In-Reply-To: <200004222110.RAA00745@astro.cs.utk.edu>
References: <Your message of "Sat, 22 Apr 2000 13:25:12 EDT." <200004221725.NAA02164@ginger.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org


>
>and just because I'm arguing against the above kinds of statements doesn't
>mean that I think we can convince folks to just discard their NATs.  I do
>however think that folks may be willing to upgrade and/or replace their
>NATs once something better exists that allows them to run applications that
>they can't run with current NATs.  and I don't know of any way to
>improve things that doesn't require replacing/upgrading NATs in some sense.

Keith .I have been following this thread for some time and I am in total 
agreement with your position and the position of the IAB on this issue.

However we seem to be missing a rational strategy for dealing with the 
Layer 8 [economic] issue here which is the greed of the general ISP 
community in matters involving the issuance of  IP numbers, especially in 
the emerging home based SOHO broadband industry, cable or DSL.

Beyond the ongoing problem of installation nightmares, which are well 
documented in every print publication I see. We are hearing daily stories 
of  49.95 a month for DSL service with 1 IP address but if you want 5 its 
79.95 for "business class service". The ISP assumes that if you want more 
than 1 IP address you are running a server, forget that it could be a 
service like IPP, but some e-commerce site or whatever.

Our distinguished colleague Vint Cerf highlights these issues, once 
again,  in the latest issue of Upside May 2000 page 204 ( no its not online 
yet ).

Though I know this list is often populated with folks with a libertarian 
bent, may I remind some that there is one other form of global numbering 
that is allocated on a reasonable, fair and equitable basis to all comers. 
Telephone Numbers. This process is political but it works ( unless you live 
in Northern California ).

The problem is not NAT's. The problem is why people have to use 
NAT's...they can't get the numbers they need or want, in large measure, due 
to the greed of ISP's.

The problem, as I see it is really a Layer 9 issue [politicial] which is we 
have no national policy in the US, or any where else on the planet, for the 
issuance of IP addresses on request to those consumers or businesses who 
need them on a fair and equitable basis consistent with the requirements of 
the routing tables.

And yes I have a credit card ready, willing and able to purchase service 
for an ISP willing to give be a nice block of IP V6 numbers ( 50 will do ) 
at a reasonable price and the support necessary to implement them.

Dr. Cerf ..you have a customer.




 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey
Shockey Consulting LLC
8045 Big Bend Blvd. Suite 110
St. Louis, MO 63119
Voice 314.918.9020
eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
INTERNET Mail & IFAX : rshockey@ix.netcom.com
GSTN Fax 314.918.9015
MediaGate iPost VoiceMail and Fax 800.260.4464
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<



From owner-ietf-outbound  Sat Apr 22 22:31:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA22689
	for ietf-outbound.10@ietf.org; Sat, 22 Apr 2000 22:30:04 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22598
	for <ietf@ietf.org>; Sat, 22 Apr 2000 22:24:00 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id WAA02287;
        Sat, 22 Apr 2000 22:23:30 -0400 (EDT)
Message-Id: <200004230223.WAA02287@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Richard Shockey <rshockey@ix.netcom.com>
cc: Keith Moore <moore@cs.utk.edu>, "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>,
        ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Sat, 22 Apr 2000 21:08:35 CDT."
             <4.3.2.20000422201841.00c435d0@127.0.0.1> 
Date: Sat, 22 Apr 2000 22:23:30 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

Richard,

I'm not entirely pleased with the current policies for address assignment,
nor with the pricing policies of certain ISPs for access for more than
one IP address.  However, I'm convinced that even with improvements to 
these policies, IPv4 address exhaustion would still be a major problem
(it could easily be a far worse problem) and would still be a significant 
motivation for NAT deployment.

Keith



From owner-ietf-outbound  Sun Apr 23 00:01:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA24570
	for ietf-outbound.10@ietf.org; Sun, 23 Apr 2000 00:00:06 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET (nod.Reston.mci.net [166.45.6.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24510
	for <ietf@ietf.org>; Sat, 22 Apr 2000 23:53:13 -0400 (EDT)
Received: from cerf.mci.net ([24.163.108.28])
 by shoe.reston.mci.net (PMDF V5.2-32 #40475)
 with ESMTPA id <01JOJZKHNOEQ8ZEHW3@shoe.reston.mci.net> for ietf@ietf.org;
 Sat, 22 Apr 2000 23:53:13 EST
Date: Sat, 22 Apr 2000 23:50:05 -0400
From: "vinton g. cerf" <vcerf@MCI.NET>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-reply-to: <4.3.2.20000422201841.00c435d0@127.0.0.1>
X-Sender: vcerf@shoe.reston.mci.net
To: Richard Shockey <rshockey@ix.netcom.com>, Keith Moore <moore@cs.utk.edu>,
        "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: ietf@ietf.org, moore@cs.utk.edu
Message-id: <4.3.1.2.20000422234827.01305f30@shoe.reston.mci.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <200004222110.RAA00745@astro.cs.utk.edu>
Content-Transfer-Encoding: 7BIT
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7BIT

big smile - vBNS+ is running IPv6 on a commercial basis. I'd be more than interested in
your opinion of a sensible (acceptable) policy on the minimum size of IPv6 space one might expect
to allocate to customers. 

Vint

At 09:08 PM 4/22/2000 -0500, Richard Shockey wrote:
>And yes I have a credit card ready, willing and able to purchase service for an ISP willing to give be a nice block of IP V6 numbers ( 50 will do ) at a reasonable price and the support necessary to implement them.
>
>Dr. Cerf ..you have a customer.

=================================================================
I moved to a new MCI WorldCom facility on Nov 11, 1999

MCI WorldCom
22001 Loudoun County Parkway
Building F2, Room 4115, ATTN: Vint Cerf
Ashburn, VA 20147
Telephone (703) 886-1690
FAX (703) 886-0047


"INTERNET IS FOR EVERYONE!" 
See you at INET2000, Yokohama, Japan July 18-21, 2000
http://www.isoc.org/inet2000




From owner-ietf-outbound  Sun Apr 23 03:23:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA01884
	for ietf-outbound.10@ietf.org; Sun, 23 Apr 2000 03:20:02 -0400 (EDT)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01525
	for <ietf@ietf.org>; Sun, 23 Apr 2000 03:16:34 -0400 (EDT)
Received: by kuji.off.connect.com.au (Postfix, from userid 170)
	id 9BEFE10B25; Sun, 23 Apr 2000 16:45:59 +0930 (CST)
Received: from connect.com.au (localhost [127.0.0.1])
	by kuji.off.connect.com.au (Postfix) with ESMTP
	id 408736F6A; Sun, 23 Apr 2000 16:45:59 +0930 (CST)
To: Richard Shockey <rshockey@ix.netcom.com>
Cc: Keith Moore <moore@cs.utk.edu>, "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>,
        ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-reply-to: Your message of "Sat, 22 Apr 2000 21:08:35 EST."
             <4.3.2.20000422201841.00c435d0@127.0.0.1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <28718.956474152.1@connect.com.au>
Date: Sun, 23 Apr 2000 16:45:53 +0930
From: Mark Prior <mrp@connect.com.au>
Message-Id: <20000423071559.9BEFE10B25@kuji.off.connect.com.au>
X-Loop: ietf@ietf.org

     The problem is not NAT's. The problem is why people have to use
     NAT's...they can't get the numbers they need or want, in large measure, due
     to the greed of ISP's.

That is a huge generalisation. The ISP I work for offers customers as
many IP numbers as they can justify and at no additional cost to them.
Irrespective of the availability of public address space a large number
of customers choose to do NAT for their own reasons.

Mark.



From owner-ietf-outbound  Sun Apr 23 03:31:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA03082
	for ietf-outbound.10@ietf.org; Sun, 23 Apr 2000 03:30:02 -0400 (EDT)
Received: from monitor.internaut.com (mg-206253200-16.ricochet.net [206.253.200.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02087
	for <ietf@ietf.org>; Sun, 23 Apr 2000 03:21:45 -0400 (EDT)
Received: from vaiobean (vaiobean.ntdev.microsoft.com [204.57.137.66] (may be forged))
	by monitor.internaut.com (8.9.2/8.8.8) with SMTP id AAA69651;
	Sun, 23 Apr 2000 00:06:56 -0700 (PDT)
Reply-To: <aboba@internaut.com>
From: "Bernard Aboba" <aboba@internaut.com>
To: "'Richard Shockey'" <rshockey@ix.netcom.com>,
        "'Keith Moore'" <moore@cs.utk.edu>,
        "'J. Noel Chiappa'" <jnc@ginger.lcs.mit.edu>
Cc: <ietf@ietf.org>, <moore@cs.utk.edu>
Subject: RE: draft-ietf-nat-protocol-complications-02.txt 
Date: Sun, 23 Apr 2000 00:21:02 -0700
Message-ID: <000101bfacf4$7b57e9e0$428939cc@ntdev.microsoft.com>
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 CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <4.3.2.20000422201841.00c435d0@127.0.0.1>
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>they can't get the numbers they need or want, in large measure, due
>to the greed of ISPs.

Rather than demonizing ISPs, it's more worthwhile to take
some time to stand in their shoes. Back in the mid '90s,
we faced these same issues in provisioning of small office/home
offices. It was generally much easier (and less expensive from
an administrative point of view) to roll out dialup infrastructure
on a mass scale allocating a single (dynamic address) than it
was to allocate and keep track of address space, with attendant
routing issues.

Early on, the hope was that RADIUS functionality like
Framed-Route and Framed-Routing could enable inexpensive
mass-provisioning of SOHOs connected via inexpensive
RIP-enabled analog and ISDN routers. This functionality
did make it easier to set up statically routed SOHOs.
However, it didn't scale very well as POPs grew to
encompass many access devices, and customers changed
their points of attachment, thus making it increasingly
difficult to administer from a routing point of view.

Support data also told us that those statically routed
customers were many times more likely to require
extensive support. All of this combined to make the
real costs of providing the "routed" service many
times that of giving customers a NAT and a dynamically
assigned address.

Since then, we've made remarkably little progress on
the auto-provisioning problem.

>And yes I have a credit card ready, willing and able to purchase service
>for an ISP willing to give be a nice block of IP V6 numbers ( 50 will do )
>at a reasonable price and the support necessary to implement them.
      ^^^^^^^^^^               ^^^^^^^

The words "reasonable" and "support" do not fit together well, since a
service that requires lots of support isn't likely to be reasonably
priced. What we probably should be shooting for is a service that can
be sold at a reasonable price, but that requires no support at all.




From owner-ietf-outbound  Sun Apr 23 07:31:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA06959
	for ietf-outbound.10@ietf.org; Sun, 23 Apr 2000 07:30:02 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA06887
	for <ietf@ietf.org>; Sun, 23 Apr 2000 07:24:37 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.05202-0@bells.cs.ucl.ac.uk>; Sun, 23 Apr 2000 12:21:02 +0100
To: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
cc: Pyda Srisuresh <srisuresh@yahoo.com>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-reply-to: Your message of "Sat, 22 Apr 2000 11:55:02 EDT." <3901CB56.61EC7B8A@cs.columbia.edu>
Date: Sun, 23 Apr 2000 12:20:56 +0100
Message-ID: <1375.956488856@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org



henning,

good stuff...
people would do well to read this - 

also, all attempts to fix NATs so as to ameliorate these problems
have _exactly_ the same deployment complexity as IPv6 - there's a
quote somewhere from yakov rehkter to this effect (can't find it
exactly, but he was coming the ther way saying why dont we use NATs
instead of v6 - same difference)


by the way, at least one router vendor has now lost a large contract
to a competitor becuase it couldn't provide v6 routing (forwardig,
yes, routing, no).... so perhaps we'll see the situation change quite
fast now:-)

In message <3901CB56.61EC7B8A@cs.columbia.edu>, Henning Schulzrinne typed:

 >>It might be useful to point out more clearly the common characteristics
 >>of protocols that are broken by NATs. These include, in particular,
 >>protocols that use one connection to establish another data flow. Such
 >>protocols include ftp, SIP and RTSP (the latter is not mentioned yet in
 >>the draft, but NATs also interfere with its operation). Note that unless
 >>we forego such control protocol designs altogether, NATs in principle
 >>break these unless every host has an external DNS mapping. (Thus, in
 >>reference to a recent message to just design NAT-friendly protocols,
 >>this means in practice that such "out-of-band" designs could not be
 >>supported by this NATy version of the Internet. In effect, this leads to
 >>the abomination of carrying real-time data in HTTP connections.)
 >>
 >>Other protocol designs are those that are symmetric rather than
 >>client-server based. This affects all Internet telephony or event-based
 >>protocols (IM and generalizations) unless they maintain an outbound
 >>connection with a server acting as their representative to the globally
 >>routed Internet. The latter obviously does not address the media stream
 >>addressing problems.
 >>
 >>-- 
 >>Henning Schulzrinne   http://www.cs.columbia.edu/~hgs
 >>

 cheers

   jon



From owner-ietf-outbound  Sun Apr 23 10:31:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA07978
	for ietf-outbound.10@ietf.org; Sun, 23 Apr 2000 10:30:02 -0400 (EDT)
Received: from smtp-out2.bellatlantic.net (smtp-out2.bellatlantic.net [199.45.39.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07942
	for <ietf@ietf.org>; Sun, 23 Apr 2000 10:22:42 -0400 (EDT)
Received: from cs.columbia.edu (adsl-151-198-20-48.bellatlantic.net [151.198.20.48])
	by smtp-out2.bellatlantic.net (8.9.1/8.9.1) with ESMTP id KAA21860
	for <ietf@ietf.org>; Sun, 23 Apr 2000 10:22:35 -0400 (EDT)
Message-ID: <39030794.28EFD3BC@cs.columbia.edu>
Date: Sun, 23 Apr 2000 10:24:20 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD BA45DSL  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Patent protection from NATs
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

To combine the two long-running threads: The solution to the NAT problem
is obvious - we need a submarine patent where somebody claims rights to
NATs and then charges so much for licensing that it makes technically
more sound solutions, say, IPv6, economically attractive. Indeed, I
think we should get together a group of people to patent all the
architecturally bad ideas (call it the "RSI group"), as they'll appear
sooner or later. That will give us 20 years of respite...



From owner-ietf-outbound  Sun Apr 23 11:31:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA08377
	for ietf-outbound.10@ietf.org; Sun, 23 Apr 2000 11:30:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08349
	for <ietf@ietf.org>; Sun, 23 Apr 2000 11:25:37 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id JAA20748
	for ietf@ietf.org  env-from <vjs>;
	Sun, 23 Apr 2000 09:25:37 -0600 (MDT)
Date: Sun, 23 Apr 2000 09:25:37 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004231525.JAA20748@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Patent protection from NATs
X-Loop: ietf@ietf.org

> From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>

> To combine the two long-running threads: The solution to the NAT problem
> is obvious - we need a submarine patent where somebody claims rights to
> NATs and then charges so much for licensing that it makes technically
> more sound solutions, say, IPv6, economically attractive. Indeed, I
> think we should get together a group of people to patent all the
> architecturally bad ideas (call it the "RSI group"), as they'll appear
> sooner or later. That will give us 20 years of respite...

Beware of what you wish for.
It's far more likely that there is a so not widely unknown patent
on IPv6, such as the idea of using more than 32 bits in an address.
If you can get a patent much more obvious ideas, such as
http://patent.womplex.ibm.com/details?&pn=US05446889__ or
http://www.patents.ibm.com/details?&pn=US06025810__&s_all=1#23 then
the far more obscure and (possibly?) more practical idea of a bigger
transport layer address is surely patentable.

For example, remember the Soderblum Patent that caused so much
grief for FDDI.  (see http://www.patents.ibm.com/details?&pn10=US04293948 )


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Sun Apr 23 12:21:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA08779
	for ietf-outbound.10@ietf.org; Sun, 23 Apr 2000 12:20:02 -0400 (EDT)
Received: from unknown (ip72.atlanta14.ga.pub-ip.psi.net [38.30.162.72])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA08732
	for <ietf@ietf.org>; Sun, 23 Apr 2000 12:17:02 -0400 (EDT)
From: <benchmark@conok.com>
To: <ietf@ietf.org>
Date: Mon, 24 Apr 2000 03:18:38
Message-Id: <37.849337.510255@>
Subject: laser printer toner advertisement
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit






BENCHMARK SUPPLY
5334 LAKE VIEW CLUB
ATLANTA GA 30338

***LASER PRINTER TONER CARTRIDGES***
***FAX AND COPIER TONER***
 
WE ACCEPT GOVERNMENT, SCHOOL & UNIVERSITY PURCHASE ORDERS
JUST LEAVE YOUR PO # WITH CORRECT BILLING & SHIPPING ADDRESS

   CHECK OUT OUR NEW CARTRIDGE PRICES :
 

APPLE 
 
  LASER WRITER  PRO 600 OR 16/600         $69
  LASER WRITER SELECT 300,310.360         $69
  LASER WRITER 300, 320                   $54 
  LASER WRITER LS,NT,2NTX,2F,2G & 2SC     $54 
  LASER WRITER 12/640                     $79 

HEWLETT PACKARD 

  LASERJET SERIES 2,3 & 3D (95A)          $49 
  LASERJET SERIES  2P AND 3P (75A)        $54 
  LASERJET SERIES 3SI AND 4SI (91A)       $75 
  LASERJET SERIES 4L AND 4P               $49 
  LASERJET SERIES 4, 4M, 5, 5M, 4+ (98A)  $59 
  LASERJET SERIES 4000 HIGH YIELD  (27X)  $99 
  LASERJET SERIES 4V                      $95 
  LASERJET SERIES 5SI , 8000              $95 
  LASERJET SERIES 5L AND 6L               $49 
  LASERJET SERIES 5P, 5MP, 6P, 6MP        $59 
  LASERJET SERIES 5000 (29A)             $135
  LASERJET SERIES 1100 (92A)              $49 
  LASERJET SERIES 2100 (96A)              $84
  LASERJET SERIES 8100 (82X)		 $145


HP LASERFAX 

  LASERFAX 500, 700, FX1,                 $59 
  LASERFAX 5000, 7000, FX2,               $59 
  LASERFAX  FX3                           $69 
  LASERFAX  FX4                           $79 
 

LEXMARK 

  OPTRA  4019, 4029  HIGH YIELD          $135 
  OPTRA R, 4039, 4049 HIGH YIELD         $135 
  OPTRA S 4059 HIGH YIELD                $135 
  OPTRA E                                 $59 
  OPTRA  N                               $115 
 

EPSON 

  EPL-7000, 8000                         $105 
  EPL-1000, 1500                         $105 
 

CANON 

  LBP-430                                 $49 
  LBP-460, 465                            $59 
  LBP-8 II                                $54 
  LBP-LX                                  $54 
  LBP-MX                                  $95 
  LBP-AX                                  $49 
  LBP-EX                                  $59 
  LBP-SX                                  $49 
  LBP-BX                                  $95 
  LBP-PX                                  $49 
  LBP-WX                                  $95 
  LBP-VX                                  $59 
  CANON FAX L700 THRU L790 FX1            $59 
  CANONFAX L5000 L70000  FX2              $59 
 

CANON COPIERS 

  PC 20, 25 ETC....                       $89 
  PC 3, 6RE, 7, 11  (A30)                 $69 
  PC 320 THRU 780  (E40)                  $89 
 

NEC 

  SERIES 2 LASER MODEL 90,95             $105


PLEASE NOTE:

1) ALL OUR CARTRIDGES ARE GENUINE OEM CARTRIDGES.
2) WE DO NOT SEND OUT CATALOGS OR PRICE LISTS 
3) WE DO NOT FAX QUOTES OR PRICE LISTS.  
4) WE DO NOT SELL TO RESELLERS OR BUY FROM DISTRIBUTERS
5) WE DO NOT CARRY: BROTHER-MINOLTA-KYOSERA-PANASONIC PRODUCTS
6) WE DO NOT CARRY: XEROX-FUJITSU-OKIDATA OR SHARP PRODUCTS
7) WE DO NOT CARRY ANY COLOR PRINTER SUPPLIES    
8) WE DO NOT CARRY DESKJET/INKJET OR BUBBLEJET SUPPLIES
9) WE DO NOT BUY FROM OR SELL TO RECYCLERS OR REMANUFACTURERS



               

****OUR  ORDER LINE IS 770-399-0953 ****

****OUR CUSTOMER SERVICE  LINE IS 800-586-0540****
****OUR E-MAIL REMOVAL AND COMPLAINT LINE IS 888-494-8597****

****PLACE YOUR ORDER AS FOLLOWS**** :

BY PHONE   770-399-0953 

BY FAX:    770-698-9700 
BY MAIL:   BENCHMARK PRINT SUPPLY
           7540 BRIDGEGATE COURT
,          ATLANTA GA 30350

MAKE SURE YOU INCLUDE THE FOLLOWING INFORMATION IN YOUR ORDER: 

             1)  YOUR PHONE NUMBER 
             2)  COMPANY NAME 
             3)  SHIPPING ADDRESS 
             4)  YOUR NAME 
             5)  ITEMS NEEDED WITH QUANTITIES 
             6)  METHOD OF PAYMENT. (COD OR CREDIT CARD) 
             7)  CREDIT CARD NUMBER WITH EXPIRATION DATE 

 
1) WE SHIP UPS GROUND. ADD $4.5 FOR SHIPPING AND HANDLING.
2) COD CHECK ORDERS ADD $3.5 TO YOUR SHIPPING COST.
2) WE ACCEPT ALL MAJOR CREDIT CARD OR "COD" ORDERS.
3) OUR STANDARD MERCHANDISE REFUND POLICY IS NET 30 DAYS
4) OUR STANDARD MERCHANDISE REPLCAMENT POLICY IS NET 90 DAYS. 


NOTE NUMBER (1): 

PLEASE DO NOT CALL OUR ORDER LINE TO REMOVE YOUR E-MAIL 
ADDRESS OR COMPLAIN. OUR ORDER LINE IS NOT SETUP TO FORWARD 
YOUR E-MAIL ADDRESS REMOVAL REQUESTS OR PROCESS YOUR 
COMPLAINTS..IT WOULD BE A WASTED PHONE CALL.YOUR ADDRESS 
WOULD NOT BE REMOVED AND YOUR COMPLAINTS WOULD NOT BE 
HANDLED.PLEASE CALL OUR TOLL FREE E-MAIL REMOVAL AND 
COMPLAINT LINE TO DO THAT.

NOTE NUMBER (2):

OUR E-MAIL RETURN ADDRESS IS NOT SETUP TO ANSWER ANY 
QUESTIONS YOU MIGHT HAVE REGARDING OUR PRODUCTS. OUR E-MAIL 
RETURN ADDRESS IS ALSO NOT SETUP TO TAKE ANY ORDERS AT 
THIS TIME. PLEASE CALL THE ORDER LINE TO PLACE YOUR ORDER
 OR HAVE ANY QUESTIONS ANSWERED. OTHERWISE PLEASE CALL OUR 
CUSTOMER SERCICE LINE.







 
 
 
 
 
 
 
 
 



From owner-ietf-outbound  Sun Apr 23 13:51:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09414
	for ietf-outbound.10@ietf.org; Sun, 23 Apr 2000 13:50:02 -0400 (EDT)
Received: from keith.fenris.net (keith.fenris.net [158.222.0.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09391
	for <ietf@ietf.org>; Sun, 23 Apr 2000 13:49:56 -0400 (EDT)
Received: from murray.lloyd.com (keith.fenris.net [158.222.0.2])
	by keith.fenris.net (8.9.3/8.9.3) with ESMTP id KAA25798
	for <ietf@ietf.org>; Sun, 23 Apr 2000 10:51:22 -0700 (PDT)
Message-Id: <4.3.1.0.20000423095850.00b2f8d0@127.0.0.1>
X-Sender: brian@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sun, 23 Apr 2000 10:12:48 -0700
To: ietf@ietf.org
From: Brian Lloyd <brian@lloyd.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-Reply-To: <200004222110.RAA00745@astro.cs.utk.edu>
References: <Your message of "Sat, 22 Apr 2000 13:25:12 EDT." <200004221725.NAA02164@ginger.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 02:10 PM 4/22/00, Keith Moore wrote:
> > Look, I have on my disk a file from June, 1992 (yes, that's not a typo -
> > *1992*) called "Problems with NAT".

This is probably a naive viewpoint but I have always viewed NAT as a hack 
that would allow us to continue to use 32bit addresses until we could 
deploy a larger address.  When this discussion was going on back in 1992 
(yes, I remember the arguments) NAT was proposed as an interim solution, 
not a final solution.  So, whatever happened to IPv6?  128 bit addresses 
would certainly allow us to continue using IP addresses as endpoint 
identifiers thus eliminating the need for NAT.  It seems that this is a 
more reasonable solution than trying to make NAT work under all circumstances.

I hate to say it but if Microsoft deployed IPv6 in its OS products, this 
discussion would probably be moot because the endpoint users would upgrade 
most of the endpoints for us thus just requiring the backbone to run IPv4 
and IPv6 routing in parallel for a time.

Never mind.  I am sure I am just being naive.


Brian Lloyd                                    Lucent Technologies
brian@lloyd.com                                3461 Robin Lane, Suite 1
http://www.livingston.com                      Cameron Park, CA  95682
+1.530.676.6513 - voice                        +1.530.676.3442 - fax



From owner-ietf-outbound  Sun Apr 23 21:41:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA12156
	for ietf-outbound.10@ietf.org; Sun, 23 Apr 2000 21:40:03 -0400 (EDT)
Received: from saint.heaven.net (saint.heaven.net [198.69.28.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12133
	for <ietf@ietf.org>; Sun, 23 Apr 2000 21:39:23 -0400 (EDT)
Received: (from stpeters@localhost)
	by saint.heaven.net (8.9.3/8.9.3) id VAA07171;
	Sun, 23 Apr 2000 21:39:15 -0400
From: "Dick St.Peters" <stpeters@NetHeaven.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14595.42435.211757.289533@saint.heaven.net>
Date: Sun, 23 Apr 2000 21:39:15 -0400 (EDT)
To: <ietf@ietf.org>
Subject: RE: draft-ietf-nat-protocol-complications-02.txt 
In-Reply-To: <000101bfacf4$7b57e9e0$428939cc@ntdev.microsoft.com>
References: <4.3.2.20000422201841.00c435d0@127.0.0.1>
	<000101bfacf4$7b57e9e0$428939cc@ntdev.microsoft.com>
X-Mailer: VM 6.72 under Emacs 19.34.1
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Bernard Aboba writes:
> Rather than demonizing ISPs, it's more worthwhile to take
> some time to stand in their shoes. Back in the mid '90s,
> we faced these same issues in provisioning of small office/home
> offices. It was generally much easier (and less expensive from
> an administrative point of view) to roll out dialup infrastructure
> on a mass scale allocating a single (dynamic address) than it
> was to allocate and keep track of address space, with attendant
> routing issues.

While I fully agree that demonizing ISPs is not useful, routing issues
for user subnets ceased being a problem quite some time ago - since
OSPF became generally available in NAS boxes.

I have four service areas in which my dialup users have a choice of
access numbers that are answered in different POPs.  Users with a
routed subnet can disconnect from one number and immediately reconnect
via a number answered in a different town, and OSPF will route their
network to them.  TCP sessions remain intact, seeing only a pause.

Routing issues are not the reason for NAT deployment.  On my network
NAT exists because users prefer it.  We give any user, even analog
dialup users, a /29 free for the asking.  They are hard to give away.
Every user running NAT has chosen to do so rather than accept a free
subnet.

Currently, 0.8% of our dialup (including ISDN) users have taken us up
on our free subnet offer.  (I think I told someone 0.08% in private
mail a day or two ago - sorry about that.)  We even have a T1 client
that chose to take one IP address and run NAT.  Most users are not
networking geeks.  They like NAT because NAT boxes make what they want
to do so easy.

Note that giving away /29s to dialup users puts us in a tenuous
position with respect to the address use guidelines for ISPs in
RFC2050 - a BCP, under which assigning even a single /32 to a dialup
user is "strongly discouraged".  It also says "ISPs should have
documented justification available for each assignment."

Basically an ISP can A) violate RFC2050 by giving subnets without
documented justification, B) document willingness to pay extra for a
subnet as evidence of justification, or C) pry into users' business
asking what they want a subnet for.

We used to give free /27s to any user who asked.  However, when ARIN
put ISP address use under a microscope and RFC2050 gave the
guidelines, we did some checking of use and found that no dialup user
assigned a subnet had more than 4 addresses in use, so we reduced the
free subnet size (except for grandfathered users).

--
Dick St.Peters, stpeters@NetHeaven.com 
Gatekeeper, NetHeaven, Saratoga Springs, NY
Saratoga/Albany/Amsterdam/BoltonLanding/Cobleskill/Greenwich/
GlensFalls/LakePlacid/NorthCreek/Plattsburgh/...
    Oldest Internet service based in the Adirondack-Albany region



From owner-ietf-outbound  Sun Apr 23 22:31:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA13425
	for ietf-outbound.10@ietf.org; Sun, 23 Apr 2000 22:30:03 -0400 (EDT)
Received: from golfersmail.org (golfersmail.org [208.243.164.74])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13396
	for <ietf@ietf.org>; Sun, 23 Apr 2000 22:26:46 -0400 (EDT)
Received: from hamza [203.135.8.158] by golfersmail.org
  (SMTPD32-6.00) id A0D13330294; Sun, 23 Apr 2000 22:26:25 -0400
Reply-To: <ozair@GOLFERSMAIL.ORG>
From: "Ozair" <ozair@GOLFERSMAIL.ORG>
To: <ietf@ietf.org>
Subject: Hello
Date: Mon, 24 Apr 2000 07:28:30 +0500
Message-ID: <LOBBICHDENPAIHMCGGEOIEABDBAA.ozair@golfersmail.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <39030794.28EFD3BC@cs.columbia.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hello everyone,

My name is Mohammad Ozair Rasheed. I joined this list a few days back in
hope of understanding various protocol issues present in this forum. Here is
a brief look at me.

I am from Pakistan and work for a software house at the city of Lahore
(www.cres-tech.com) as the Senior Systems Analyst. Currently I am working as
the Project Coordinator for implementing the Database and Data Warehouse
Portion of the National Data Warehouse Project. I am also a volunteer member
for PMI and am working in a team for developing the Project Management
Principles for PMI.

Well, that is a brief information about me. It would be very helpful if any
one of you could provide me with background information about this list and
the topics that have been under discussion. I would very much like to add
value to the discussions.

Regards,
M. Ozair Rasheed
Pakistan.



From owner-ietf-outbound  Sun Apr 23 23:51:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA15394
	for ietf-outbound.10@ietf.org; Sun, 23 Apr 2000 23:50:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15289
	for <ietf@ietf.org>; Sun, 23 Apr 2000 23:44:44 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id XAA02772;
        Sun, 23 Apr 2000 23:44:12 -0400 (EDT)
Message-Id: <200004240344.XAA02772@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Dick St.Peters" <stpeters@NetHeaven.com>
cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Sun, 23 Apr 2000 21:39:15 EDT."
             <14595.42435.211757.289533@saint.heaven.net> 
Date: Sun, 23 Apr 2000 23:44:12 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Most users are not
> networking geeks.  They like NAT because NAT boxes make what they want
> to do so easy.

presumably they don't realize that the NATs are making it hard 
to do other things that they might want to do.

I wonder...how many of these folks really want network address 
translation, versus those who just want the other things that
NAT boxes often do?   (DHCP, firewall, hub, router, all with 
really easy setup)

maybe we need to make it as easy to connect a small net to the 
Internet, as it is to connect a host. 

Keith



From owner-ietf-outbound  Mon Apr 24 00:01:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA15483
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 00:00:05 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15442
	for <ietf@ietf.org>; Sun, 23 Apr 2000 23:55:29 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 12jZy3-000MFw-00; Sun, 23 Apr 2000 20:55:27 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
References: <14595.42435.211757.289533@saint.heaven.net>
	<200004240344.XAA02772@astro.cs.utk.edu>
Message-Id: <E12jZy3-000MFw-00@rip.psg.com>
Date: Sun, 23 Apr 2000 20:55:27 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>> Most users are not networking geeks.  They like NAT because NAT boxes
>> make what they want to do so easy.
>
> presumably they don't realize that the NATs are making it hard 
> to do other things that they might want to do.
> 
> I wonder...how many of these folks really want network address 
> translation, versus those who just want the other things that
> NAT boxes often do?   (DHCP, firewall, hub, router, all with 
> really easy setup)
> 
> maybe we need to make it as easy to connect a small net to the 
> Internet, as it is to connect a host. 
> 
> Keith

bingo!

[ as easy for all parties, the user and the upstream ]



From owner-ietf-outbound  Mon Apr 24 00:21:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA15659
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 00:20:03 -0400 (EDT)
Received: from saint.heaven.net (saint.heaven.net [198.69.28.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15632
	for <ietf@ietf.org>; Mon, 24 Apr 2000 00:16:35 -0400 (EDT)
Received: (from stpeters@localhost)
	by saint.heaven.net (8.9.3/8.9.3) id AAA09329;
	Mon, 24 Apr 2000 00:16:24 -0400
From: "Dick St.Peters" <stpeters@NetHeaven.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14595.51864.365595.505493@saint.heaven.net>
Date: Mon, 24 Apr 2000 00:16:24 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-Reply-To: <200004240344.XAA02772@astro.cs.utk.edu>
References: <14595.42435.211757.289533@saint.heaven.net>
	<200004240344.XAA02772@astro.cs.utk.edu>
X-Mailer: VM 6.72 under Emacs 19.34.1
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> > Most users are not
> > networking geeks.  They like NAT because NAT boxes make what they want
> > to do so easy.
> 
> presumably they don't realize that the NATs are making it hard 
> to do other things that they might want to do.
> 
> I wonder...how many of these folks really want network address 
> translation, versus those who just want the other things that
> NAT boxes often do?   (DHCP, firewall, hub, router, all with 
> really easy setup)

Bingo.  Most don't even know what NAT is.  They buy a box that does
what they want with easy setup and sometimes never mentions NAT.
(What they want doesn't include DHCP; they mostly don't know what that
is either.)

--
Dick St.Peters, stpeters@NetHeaven.com 



From owner-ietf-outbound  Mon Apr 24 00:31:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA15776
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 00:30:04 -0400 (EDT)
Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15710
	for <IETF@IETF.org>; Mon, 24 Apr 2000 00:23:35 -0400 (EDT)
Received: from SERVER (adsl-63-199-7-253.dsl.snfc21.pacbell.net)
 by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with SMTP id <0FTI00L5I6THGT@mta5.snfc21.pbi.net> for IETF@IETF.org; Sun,
 23 Apr 2000 21:22:30 -0700 (PDT)
Date: Sun, 23 Apr 2000 21:20:41 -0700
From: Peter Johansson <PJohansson@ACM.ORG>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-reply-to: <200004240344.XAA02772@astro.cs.utk.edu>
X-Sender: Celeborn@PacBell.net
To: IETF@ietf.org
Message-id: <3.0.5.32.20000423212041.009399b0@PacBell.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Content-type: text/plain; charset="us-ascii"
References: <"Your message of Sun, 23 Apr 2000 21:39:15 EDT."
 <14595.42435.211757.289533@saint.heaven.net>
X-Loop: ietf@ietf.org

At 11:44 PM 4/23/00 -0400, Keith Moore wrote:

>I wonder...how many of these folks really want network address 
>translation, versus those who just want the other things that
>NAT boxes often do?   (DHCP, firewall, hub, router, all with 
>really easy setup)

I'm not a valid statistical sampling, just a point of anecdotal evidence in
support of your musings, Keith.

Less than four months ago I switched from dial-up access to ADSL. My ISP
was being less than forthcoming about the security risks inherent in a
24/7, so I had to do some research on my own. I settled on a DSL
modem/router with NAT capabilities in the belief that it would meet my
(modest) security needs. "Modest" because I have, as yet, no plans to
provide Internet services, only consume them.

Even today I know little about the nuts and bolts of NAT's operations. I've
started following this and other threads (notably zero configuration)
because I'm vitally interested in the "home network"---and come at it from
a Serial Bus (IEEE 1394) perspective.

So, YES, I think many could care less about NAT per se and only care about
the things that come with it.

Regards,

Peter Johansson

Congruent Software, Inc.
98 Colorado Avenue
Berkeley, CA  94707

(510) 527-3926
(510) 527-3856 FAX

PJohansson@ACM.org



From owner-ietf-outbound  Mon Apr 24 01:01:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA16067
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 01:00:02 -0400 (EDT)
Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16023
	for <ietf@ietf.org>; Mon, 24 Apr 2000 00:57:10 -0400 (EDT)
Received: from laptop.ix.netcom.com ([209.138.158.55])
	by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id AAA05097;
	Mon, 24 Apr 2000 00:57:04 -0400 (EDT)
Message-Id: <4.3.2.20000423224201.00bbfd30@127.0.0.1>
X-Sender: rshockey/popd.ix.netcom.com@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Sun, 23 Apr 2000 23:06:31 -0500
To: "vinton g. cerf" <vcerf@mci.net>, Keith Moore <moore@cs.utk.edu>
From: Richard Shockey <rshockey@ix.netcom.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
In-Reply-To: <4.3.1.2.20000422234827.01305f30@shoe.reston.mci.net>
References: <4.3.2.20000422201841.00c435d0@127.0.0.1>
 <200004222110.RAA00745@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 11:50 PM 4/22/2000 -0400, vinton g. cerf wrote:
>big smile - vBNS+ is running IPv6 on a commercial basis. I'd be more than 
>interested in
>your opinion of a sensible (acceptable) policy on the minimum size of IPv6 
>space one might expect
>to allocate to customers.
>
>Vint



Well that is a very interesting thought exercise depending on the market 
that is being addressed and what is the market growth in networked devices 
in the future.

If we were looking at a typicial household and you wanted to plan for the 
future I would have to assume 1 address for every single thing plugged in 
to any thing, phone, electrical appliances, water, maybe even sewage. Yes 
an IP address on your toilet. Now before we all giggle ourselves silly at 
that thought it might be reasonable to assume that at some point in the 
future sewage/water companies would want to monitor use in order to charge 
appropriately. Its been a desire of utility companies for some time to 
remotely retrieve usage data from households for the purposes of billing.

With "always on" IP and IP on anything this is closer to reality than we 
might think. In order to permit a reasonable allocation of addresses with 
room for growth the idea of 25 IP address per household and 10 person 
actually seems conservative.

Businesses are different but some of the needs are the same.  The typical 
business customer has multiple devices at their command, many of which are 
currently IP addressable or certainly should be, phone, cell phone, 
printer, copier, fax, scanners, PDA's, cameras. 15 addressees per employee?

Ive never seen any studies on what is current enterprise consumption of IP 
addresses is per employee or what differences there might be between 
consumption in the automobile industry vs the aircraft industry vs a 
consumer products company vs a typicial teleco.

Whatever it is now it would be reasonable to assume that address 
consumption per employee within 10 years will be 4x what it is now.



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey
Shockey Consulting LLC
8045 Big Bend Blvd. Suite 110
St. Louis, MO 63119
Voice 314.918.9020
eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
INTERNET Mail & IFAX : rshockey@ix.netcom.com
GSTN Fax 314.918.9015
MediaGate iPost VoiceMail and Fax 800.260.4464
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<



From owner-ietf-outbound  Mon Apr 24 01:21:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA17860
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 01:20:03 -0400 (EDT)
Received: from mail4.microsoft.com (mail4.microsoft.com [131.107.3.122])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA17040
	for <ietf@ietf.org>; Mon, 24 Apr 2000 01:12:32 -0400 (EDT)
Received: from 157.54.9.103 by mail4.microsoft.com (InterScan E-Mail VirusWall NT); Sun, 23 Apr 2000 22:10:56 -0700 (Pacific Daylight Time)
Received: by INET-IMC-04 with Internet Mail Service (5.5.2651.58)
	id <J3RM696Y>; Sun, 23 Apr 2000 22:08:16 -0700
Message-ID: <D5922CA42F8CD31189D800805F19A16C04B7B167@RED-MSG-48>
From: Ian King <iking@microsoft.com>
To: "'Keith Moore'" <moore@cs.utk.edu>,
        "Dick St.Peters"
	 <stpeters@NetHeaven.com>
Cc: ietf@ietf.org
Subject: RE: draft-ietf-nat-protocol-complications-02.txt 
Date: Sun, 23 Apr 2000 22:08:14 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

Maybe we need to help make it easy to GET assignments of blocks of addresses
for individuals/small businesses/etc.  Part of the problem is the obvious:
IPv4 addresses are running short.  Part is the "K-Mart" level of product
understanding I've experienced with many vendors of Internet connectivity.
When I asked a cable IP vendor about getting a static address assignment,
the (sales) person said, "Oh, there's no static, it's the Internet."  <sigh>
That's a priceless quote, but frankly dial-up vendors weren't any better.  

The first is an engineering problem, and we're working on that one (IPv6),
right?  :-)  The second is a market problem, and I don't think it's going to
go away until either telcos realize that they need to make a commitment to
being in the IP business (and train their staff), or we have meaningful
alternatives to the telcos for individual connectivity.  

From the individual user's perspective, NAT does seem a lot easier.  You
hook computer A to the ISP, computers B and C to computer A, and everyone
can surf -- cool.  I AM a networking geek, and NAT was a lot easier (and
cheaper) than the alternatives.  I suspect it will remain so for at least a
while -- Ian 

> -----Original Message-----
> From: Keith Moore [mailto:moore@cs.utk.edu]
> Sent: Sunday, April 23, 2000 8:44 PM
> To: Dick St.Peters
> Cc: ietf@ietf.org
> Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
> 
> 
> > Most users are not
> > networking geeks.  They like NAT because NAT boxes make 
> what they want
> > to do so easy.
> 
> presumably they don't realize that the NATs are making it hard 
> to do other things that they might want to do.
> 
> I wonder...how many of these folks really want network address 
> translation, versus those who just want the other things that
> NAT boxes often do?   (DHCP, firewall, hub, router, all with 
> really easy setup)
> 
> maybe we need to make it as easy to connect a small net to the 
> Internet, as it is to connect a host. 
> 
> Keith
> 



From owner-ietf-outbound  Mon Apr 24 06:11:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA29425
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 06:10:02 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29398
	for <ietf@ietf.org>; Mon, 24 Apr 2000 06:04:43 -0400 (EDT)
Received: from contactdish (ASt-Lambert-101-2-165.abo.wanadoo.fr [193.251.59.165]) by atkielski.com (8.8.8) id MAA94568; Mon, 24 Apr 2000 12:04:38 +0200 (CEST)
Message-ID: <002001bfadd4$80253fa0$0a00000a@wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <D5922CA42F8CD31189D800805F19A16C04B7B167@RED-MSG-48>
Subject: IPv6: Past mistakes repeated?
Date: Mon, 24 Apr 2000 12:04:36 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

What I find interesting throughout discussions that mention IPv6 as a solution for a shortage of addresses in IPv4 is that people
see the problems with IPv4, but they don't realize that IPv6 will run into the same difficulties.  _Any_ addressing scheme that uses
addresses of fixed length will run out of addresses after a finite period of time, and that period may be orders of magnitude
shorter than anyone might at first believe.

Consider IPv4.  Thirty-two bits allows more than four billion individual machines to be addressed.  In theory, then, we should have
enough IPv4 addresses for everyone until four billion machines are actually online simultaneously.  Despite this, however, we seem
to be running short of addresses already, even though only a fraction of them are actually used.  The reason for this is that the
address space is of finite size, and that we attempt to allocate that finite space in advance of actual use.

It should be clear that IPv6 will have the same problem.  The space will be allocated in advance.  Over time, it will become obvious
that the original allocation scheme is ill-adapted to changing requirements (because we simply cannot foresee those requirements).
Much, _much_ sooner than anyone expects, IPv6 will start to run short of addresses, for the same reason that IPv4 is running short.
It seems impossible now, but I suppose that running out of space in IPv4 seemed impossible at one time, too.

The allocation pattern is easy to foresee.  Initially, enormous subsets of the address space will be allocated carelessly and
generously, because "there are so many addresses that we'll never run out" and because nobody will want to expend the effort to
achieve finer granularity in the face of such apparent plenty.  This mistake will be repeated for each subset of the address space
allocated, by each organization charged with allocating the space.  As a result, in a surprisingly short time, the address space
will be exhausted.  This _always_ happens with fixed address spaces.  It seems to be human nature, but information theory has a hand
in it, too.

If you need further evidence, look at virtual memory address spaces.  Even if a computer's architecture allows for a trillion bits
of addressing space, it invariably becomes fragmented and exhausted in an amazingly short time.  The "nearly infinite space" allowed
by huge virtual addresses turns out to be very finite and very limiting indeed.

The only real solution to this is an open-ended addressing scheme--one to which digits can be added as required.  And it just so
happens that a near-perfect example of such a scheme is right in front of us all, in the form of the telephone system.  Telephone
numbers have never had a fixed number of digits.  The number has always been variable, and has simply expanded as needs have changed
and increased.  At one time, a four-digit number was enough to reach anyone.  Then seven-digit numbers became necessary.  Then an
area code became necessary.  And finally, a country code became necessary.  Perhaps a planet code will be necessary at some point in
the future.  But the key feature of the telephone system is that nobody ever decided upon a fixed number of digits in the beginning,
and so there is no insurmountable obstacle to adding digits forever, if necessary.  Imagine what things would be like if someone had
decided in 1900 that seven digits would be enough for the whole world, and then equipment around the world were designed only to
handle seven digits, with no room for expansion.  What would happen when it came time to install the 10,000,000th telephone, or when
careless allocation exhausted the seven-digit space?

Anyway, some keys to a successful addressing scheme, in my opinion, are as follows (but the first is the only mandatory feature, I
think):

1. The number of digits used for addressing is not limited by the addressing protocol.
2. Every machine in the network need only know in detail about other points in the network that have the same high-order digits in
their addresses.
3. There is a distinction for every machine between "local" addresses (those that implicitly have the same high-order digits as the
address of the machine in question) and "remote" addresses (those that have different high-order digits).

With such an address scheme, a single international body can allocate one digit to each region of the world (the size of the regions
is irrelevant).  Beneath that, other, more local bodies, one per initial digit, can allocate more digits below that.  There is no
need for anyone to allocate the entire address space in advance, so there is no need to worry about problems with the initial
allocation that will have to be fixed later.  And since the actual number of digits in a machine address is unlimited, different
parts of the world, different companies, different organizations, etc., can expand addresses as needed.  At any given time, the
maximum number of digits would be fixed at some very high number (128 decimal digits, perhaps), but if this ever became too
limiting, it would be sufficient to simply up that number--no reallocation or modification of the address space would be necessary.

Imagine computers in the United States under such a scheme.  All IPtNG addresses (IPtNG=IP: the Next Generation--I have to call it
something, right?) for the U.S. would start with one.  Since there are lots of computers in the U.S., you'd see addresses like:

14872883747534 for a machine in San Jose
1487048377212  for a machine in Sacramento
1412278987831  for a machine in Los Angeles
1248819473     for a machine in Wyoming
134875810869   for a machine in Boston

... and so on.  Notice that the lengths vary based on the number of machines in a given region--if you need more address space, you
just add more digits.  Wyoming has relatively few machines, so addresses there are short.  San Jose has a zillion machines, so
addresses there are long.

Now picture the small country of Vulgaria, and its address space:

486174         for a machine in Vulgaria Minor (where most of the population lives)
48631          for a machine in Vulgaria Major

Vulgaria is a tiny country with only a few hundred machines.  The 4 designates the region of the world in which Vulgaria is found.
The 86 is allocated to all of Vulgaria.  The remaining digits are allocated within Vulgaria itself.

If you haven't already noticed, this pattern is essentially the one already in use for telephones.  It works extremely well.

Some might say that this ties the IP address to a geographical region.  Well, yes, it does.  So what?  If you want to use IP for
security (as in identifying individuals), you're making a mistake to begin with.  The address of a machine just locates it for
routing purposes; it does not authenticate its identity.  If you want identity information for machines, you give them a separate
"identity address" that follows them anywhere in the world, even if their IPtNG address changes.  And if you want identity
information for people (which is often the real goal), you give _them_ an "identity address" that follows them anywhere in the
world.

Here again, with respect to security, the telephone network sets the pattern: if you move, your telephone number changes, but your
identity does not.  Nobody calls a telephone number and simply assumes the identity of the person who answers; normally an
authentication process is carried out ("Can I speak to Jane?"), because everyone knows that a telephone number just gets you to a
specific telephone, but not to a specific person.  Nobody lets you charge purchases to a specific credit card just because you are
calling from a specific telephone--you still have to identify yourself.

Anyway, I suppose it's too late to change anything in IPv6, but I'm convinced that IPv6 will just show the same problems as IPv4,
and it will be more like 20-40 years down the road, and not the billions of years that some people seem to assume.  I think that
history shows that the leading mistake of all engineers is to underestimate future capacity needs, and I see that happening with
IPv6, just as it did with IPv4 (and with Y2K, and with the IBM PC address space, and so on, and so on).  I just thought I'd add my
$0.02.  Maybe I've overlooked something in IPv6, but I fear that I have not.

I'd be interested in hearing what others think of this potential problem.  (Or at least correct me if I've overlooked something in
IPv6 that will prevent the problems listed above from occurring.)

  -- Anthony



From owner-ietf-outbound  Mon Apr 24 07:30:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA00278
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 07:30:03 -0400 (EDT)
Received: from dragonfly.ncdragonfly.com (dragonfly.ncdragonfly.com [209.137.27.201])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00158
	for <ietf@ietf.org>; Mon, 24 Apr 2000 07:21:54 -0400 (EDT)
Received: from dahsceptre (216.5.191.94 [216.5.191.94]) by dragonfly.ncdragonfly.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3)
	id G91S87A9; Mon, 24 Apr 2000 07:28:36 -0400
Reply-To: <dahigginbotham@ncdragonfly.com>
From: "David A Higginbotham" <dahigginbotham@ncdragonfly.com>
To: "'Anthony Atkielski'" <anthony@atkielski.com>, <ietf@ietf.org>
Subject: RE: IPv6: Past mistakes repeated?
Date: Mon, 24 Apr 2000 07:22:06 -0400
Message-ID: <BB2831D3689AD211B14C00104B14623B1E7569@HAZEN04>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <BB2831D3689AD211B14C00104B14623B23B411@HAZEN04>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I agree! Why create a finite anything when an infinite possibility exists?
On another note, I have heard the argument that a unique identifier already
exists in the form of a MAC address why not make further use of it?

David H

-----Original Message-----
From: Anthony Atkielski [mailto:anthony@atkielski.com]
Sent: Monday, April 24, 2000 6:05 AM
To: ietf@ietf.org
Subject: IPv6: Past mistakes repeated?


What I find interesting throughout discussions that mention IPv6 as a
solution for a shortage of addresses in IPv4 is that people
see the problems with IPv4, but they don't realize that IPv6 will run into
the same difficulties.  _Any_ addressing scheme that uses
addresses of fixed length will run out of addresses after a finite period of
time, and that period may be orders of magnitude
shorter than anyone might at first believe.

Consider IPv4.  Thirty-two bits allows more than four billion individual
machines to be addressed.  In theory, then, we should have
enough IPv4 addresses for everyone until four billion machines are actually
online simultaneously.  Despite this, however, we seem
to be running short of addresses already, even though only a fraction of
them are actually used.  The reason for this is that the
address space is of finite size, and that we attempt to allocate that finite
space in advance of actual use.

It should be clear that IPv6 will have the same problem.  The space will be
allocated in advance.  Over time, it will become obvious
that the original allocation scheme is ill-adapted to changing requirements
(because we simply cannot foresee those requirements).
Much, _much_ sooner than anyone expects, IPv6 will start to run short of
addresses, for the same reason that IPv4 is running short.
It seems impossible now, but I suppose that running out of space in IPv4
seemed impossible at one time, too.

The allocation pattern is easy to foresee.  Initially, enormous subsets of
the address space will be allocated carelessly and
generously, because "there are so many addresses that we'll never run out"
and because nobody will want to expend the effort to
achieve finer granularity in the face of such apparent plenty.  This mistake
will be repeated for each subset of the address space
allocated, by each organization charged with allocating the space.  As a
result, in a surprisingly short time, the address space
will be exhausted.  This _always_ happens with fixed address spaces.  It
seems to be human nature, but information theory has a hand
in it, too.

If you need further evidence, look at virtual memory address spaces.  Even
if a computer's architecture allows for a trillion bits
of addressing space, it invariably becomes fragmented and exhausted in an
amazingly short time.  The "nearly infinite space" allowed
by huge virtual addresses turns out to be very finite and very limiting
indeed.

The only real solution to this is an open-ended addressing scheme--one to
which digits can be added as required.  And it just so
happens that a near-perfect example of such a scheme is right in front of us
all, in the form of the telephone system.  Telephone
numbers have never had a fixed number of digits.  The number has always been
variable, and has simply expanded as needs have changed
and increased.  At one time, a four-digit number was enough to reach anyone.
Then seven-digit numbers became necessary.  Then an
area code became necessary.  And finally, a country code became necessary.
Perhaps a planet code will be necessary at some point in
the future.  But the key feature of the telephone system is that nobody ever
decided upon a fixed number of digits in the beginning,
and so there is no insurmountable obstacle to adding digits forever, if
necessary.  Imagine what things would be like if someone had
decided in 1900 that seven digits would be enough for the whole world, and
then equipment around the world were designed only to
handle seven digits, with no room for expansion.  What would happen when it
came time to install the 10,000,000th telephone, or when
careless allocation exhausted the seven-digit space?

Anyway, some keys to a successful addressing scheme, in my opinion, are as
follows (but the first is the only mandatory feature, I
think):

1. The number of digits used for addressing is not limited by the addressing
protocol.
2. Every machine in the network need only know in detail about other points
in the network that have the same high-order digits in
their addresses.
3. There is a distinction for every machine between "local" addresses (those
that implicitly have the same high-order digits as the
address of the machine in question) and "remote" addresses (those that have
different high-order digits).

With such an address scheme, a single international body can allocate one
digit to each region of the world (the size of the regions
is irrelevant).  Beneath that, other, more local bodies, one per initial
digit, can allocate more digits below that.  There is no
need for anyone to allocate the entire address space in advance, so there is
no need to worry about problems with the initial
allocation that will have to be fixed later.  And since the actual number of
digits in a machine address is unlimited, different
parts of the world, different companies, different organizations, etc., can
expand addresses as needed.  At any given time, the
maximum number of digits would be fixed at some very high number (128
decimal digits, perhaps), but if this ever became too
limiting, it would be sufficient to simply up that number--no reallocation
or modification of the address space would be necessary.

Imagine computers in the United States under such a scheme.  All IPtNG
addresses (IPtNG=IP: the Next Generation--I have to call it
something, right?) for the U.S. would start with one.  Since there are lots
of computers in the U.S., you'd see addresses like:

14872883747534 for a machine in San Jose
1487048377212  for a machine in Sacramento
1412278987831  for a machine in Los Angeles
1248819473     for a machine in Wyoming
134875810869   for a machine in Boston

... and so on.  Notice that the lengths vary based on the number of machines
in a given region--if you need more address space, you
just add more digits.  Wyoming has relatively few machines, so addresses
there are short.  San Jose has a zillion machines, so
addresses there are long.

Now picture the small country of Vulgaria, and its address space:

486174         for a machine in Vulgaria Minor (where most of the population
lives)
48631          for a machine in Vulgaria Major

Vulgaria is a tiny country with only a few hundred machines.  The 4
designates the region of the world in which Vulgaria is found.
The 86 is allocated to all of Vulgaria.  The remaining digits are allocated
within Vulgaria itself.

If you haven't already noticed, this pattern is essentially the one already
in use for telephones.  It works extremely well.

Some might say that this ties the IP address to a geographical region.
Well, yes, it does.  So what?  If you want to use IP for
security (as in identifying individuals), you're making a mistake to begin
with.  The address of a machine just locates it for
routing purposes; it does not authenticate its identity.  If you want
identity information for machines, you give them a separate
"identity address" that follows them anywhere in the world, even if their
IPtNG address changes.  And if you want identity
information for people (which is often the real goal), you give _them_ an
"identity address" that follows them anywhere in the
world.

Here again, with respect to security, the telephone network sets the
pattern: if you move, your telephone number changes, but your
identity does not.  Nobody calls a telephone number and simply assumes the
identity of the person who answers; normally an
authentication process is carried out ("Can I speak to Jane?"), because
everyone knows that a telephone number just gets you to a
specific telephone, but not to a specific person.  Nobody lets you charge
purchases to a specific credit card just because you are
calling from a specific telephone--you still have to identify yourself.

Anyway, I suppose it's too late to change anything in IPv6, but I'm
convinced that IPv6 will just show the same problems as IPv4,
and it will be more like 20-40 years down the road, and not the billions of
years that some people seem to assume.  I think that
history shows that the leading mistake of all engineers is to underestimate
future capacity needs, and I see that happening with
IPv6, just as it did with IPv4 (and with Y2K, and with the IBM PC address
space, and so on, and so on).  I just thought I'd add my
$0.02.  Maybe I've overlooked something in IPv6, but I fear that I have not.

I'd be interested in hearing what others think of this potential problem.
(Or at least correct me if I've overlooked something in
IPv6 that will prevent the problems listed above from occurring.)

  -- Anthony



From owner-ietf-outbound  Mon Apr 24 09:22:52 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA02916
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 09:21:37 -0400 (EDT)
Received: from fsnt.future.futusoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02687
	for <ietf@ietf.org>; Mon, 24 Apr 2000 09:13:29 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futusoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000437607@fsnt.future.futusoft.com>;
 Mon, 24 Apr 2000 18:53:15 +0530
Received: from manishs (manishs.future.futsoft.com [10.0.12.32]) by kailash.future.futsoft.com (8.7.1/8.7.1) with SMTP id SAA07799; Mon, 24 Apr 2000 18:32:51 +0530
Received: by localhost with Microsoft MAPI; Mon, 24 Apr 2000 18:39:30 +0530
Message-Id: <01BFAE1C.6D0AB9C0.manishs@future.futsoft.com>
From: "Manish R. Shah." <manishs@future.futsoft.com>
Reply-To: "manishs@future.futsoft.com" <manishs@future.futsoft.com>
To: "'Anthony Atkielski'" <anthony@atkielski.com>,
        "'ietf@ietf.org'"
	 <ietf@ietf.org>
Subject: RE: IPv6: Past mistakes repeated?
Date: Mon, 24 Apr 2000 18:39:29 +0530
Organization: future software
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


IPv6 is designed to be compatible with IPv4?

If what you suggest should be implemented, then probably
the entire software of all the switches and hubs need to be
upgraded (if not entirely scrapped) . 

As also everytime the source and destination addresses are
upgraded, all the systems and the related software needs to 
be upgraded. Personally my telephone number has changed
3 times within the last couple of years. So in this case, it is not
possible to change the code of the intermediate routers every time.
But yeah, the numbers can be made configurable.

Although I agree that the concept being advocated is indeed 
revolutionary, and also might be beneficial to some extent. 
But the million dollar question is that whether the protocol and 
switch vendors would like to scrap the years and amount 
of investment that they have already made in the existing system.

Furthur study of your proposal needs to be done !!! and can be a 
hot topic of discussion. 

Cheers !!!

Manish.

--------------------------------------------------------------
** Nothing is Impossible, Even Impossible says I'm possible !!! **
--------------------------------------------------------------

Manish R. Shah.
Senior Software Engineer,
Future Software Pvt Ltd.
480-481, Anna Salai, Nandanam
Chennai 600035.
Phone: +91-(44)-433-0550 Xten 294.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++

-----Original Message-----
From:	Anthony Atkielski [SMTP:anthony@atkielski.com]
Sent:	Monday, April 24, 2000 3:35 PM
To:	ietf@ietf.org
Subject:	IPv6: Past mistakes repeated?

 << File: ATT00001.txt; charset = Windows-1252 >> 

What I find interesting throughout discussions that mention IPv6 as a solution for a shortage of addresses in IPv4 is that people
see the problems with IPv4, but they don't realize that IPv6 will run into the same difficulties.  _Any_ addressing scheme that uses
addresses of fixed length will run out of addresses after a finite period of time, and that period may be orders of magnitude
shorter than anyone might at first believe.

Consider IPv4.  Thirty-two bits allows more than four billion individual machines to be addressed.  In theory, then, we should have
enough IPv4 addresses for everyone until four billion machines are actually online simultaneously.  Despite this, however, we seem
to be running short of addresses already, even though only a fraction of them are actually used.  The reason for this is that the
address space is of finite size, and that we attempt to allocate that finite space in advance of actual use.

It should be clear that IPv6 will have the same problem.  The space will be allocated in advance.  Over time, it will become obvious
that the original allocation scheme is ill-adapted to changing requirements (because we simply cannot foresee those requirements).
Much, _much_ sooner than anyone expects, IPv6 will start to run short of addresses, for the same reason that IPv4 is running short.
It seems impossible now, but I suppose that running out of space in IPv4 seemed impossible at one time, too.

The allocation pattern is easy to foresee.  Initially, enormous subsets of the address space will be allocated carelessly and
generously, because "there are so many addresses that we'll never run out" and because nobody will want to expend the effort to
achieve finer granularity in the face of such apparent plenty.  This mistake will be repeated for each subset of the address space
allocated, by each organization charged with allocating the space.  As a result, in a surprisingly short time, the address space
will be exhausted.  This _always_ happens with fixed address spaces.  It seems to be human nature, but information theory has a hand
in it, too.

If you need further evidence, look at virtual memory address spaces.  Even if a computer's architecture allows for a trillion bits
of addressing space, it invariably becomes fragmented and exhausted in an amazingly short time.  The "nearly infinite space" allowed
by huge virtual addresses turns out to be very finite and very limiting indeed.

The only real solution to this is an open-ended addressing scheme--one to which digits can be added as required.  And it just so
happens that a near-perfect example of such a scheme is right in front of us all, in the form of the telephone system.  Telephone
numbers have never had a fixed number of digits.  The number has always been variable, and has simply expanded as needs have changed
and increased.  At one time, a four-digit number was enough to reach anyone.  Then seven-digit numbers became necessary.  Then an
area code became necessary.  And finally, a country code became necessary.  Perhaps a planet code will be necessary at some point in
the future.  But the key feature of the telephone system is that nobody ever decided upon a fixed number of digits in the beginning,
and so there is no insurmountable obstacle to adding digits forever, if necessary.  Imagine what things would be like if someone had
decided in 1900 that seven digits would be enough for the whole world, and then equipment around the world were designed only to
handle seven digits, with no room for expansion.  What would happen when it came time to install the 10,000,000th telephone, or when
careless allocation exhausted the seven-digit space?

Anyway, some keys to a successful addressing scheme, in my opinion, are as follows (but the first is the only mandatory feature, I
think):

1. The number of digits used for addressing is not limited by the addressing protocol.
2. Every machine in the network need only know in detail about other points in the network that have the same high-order digits in
their addresses.
3. There is a distinction for every machine between "local" addresses (those that implicitly have the same high-order digits as the
address of the machine in question) and "remote" addresses (those that have different high-order digits).

With such an address scheme, a single international body can allocate one digit to each region of the world (the size of the regions
is irrelevant).  Beneath that, other, more local bodies, one per initial digit, can allocate more digits below that.  There is no
need for anyone to allocate the entire address space in advance, so there is no need to worry about problems with the initial
allocation that will have to be fixed later.  And since the actual number of digits in a machine address is unlimited, different
parts of the world, different companies, different organizations, etc., can expand addresses as needed.  At any given time, the
maximum number of digits would be fixed at some very high number (128 decimal digits, perhaps), but if this ever became too
limiting, it would be sufficient to simply up that number--no reallocation or modification of the address space would be necessary.

Imagine computers in the United States under such a scheme.  All IPtNG addresses (IPtNG=IP: the Next Generation--I have to call it
something, right?) for the U.S. would start with one.  Since there are lots of computers in the U.S., you'd see addresses like:

14872883747534 for a machine in San Jose
1487048377212  for a machine in Sacramento
1412278987831  for a machine in Los Angeles
1248819473     for a machine in Wyoming
134875810869   for a machine in Boston

... and so on.  Notice that the lengths vary based on the number of machines in a given region--if you need more address space, you
just add more digits.  Wyoming has relatively few machines, so addresses there are short.  San Jose has a zillion machines, so
addresses there are long.

Now picture the small country of Vulgaria, and its address space:

486174         for a machine in Vulgaria Minor (where most of the population lives)
48631          for a machine in Vulgaria Major

Vulgaria is a tiny country with only a few hundred machines.  The 4 designates the region of the world in which Vulgaria is found.
The 86 is allocated to all of Vulgaria.  The remaining digits are allocated within Vulgaria itself.

If you haven't already noticed, this pattern is essentially the one already in use for telephones.  It works extremely well.

Some might say that this ties the IP address to a geographical region.  Well, yes, it does.  So what?  If you want to use IP for
security (as in identifying individuals), you're making a mistake to begin with.  The address of a machine just locates it for
routing purposes; it does not authenticate its identity.  If you want identity information for machines, you give them a separate
"identity address" that follows them anywhere in the world, even if their IPtNG address changes.  And if you want identity
information for people (which is often the real goal), you give _them_ an "identity address" that follows them anywhere in the
world.

Here again, with respect to security, the telephone network sets the pattern: if you move, your telephone number changes, but your
identity does not.  Nobody calls a telephone number and simply assumes the identity of the person who answers; normally an
authentication process is carried out ("Can I speak to Jane?"), because everyone knows that a telephone number just gets you to a
specific telephone, but not to a specific person.  Nobody lets you charge purchases to a specific credit card just because you are
calling from a specific telephone--you still have to identify yourself.

Anyway, I suppose it's too late to change anything in IPv6, but I'm convinced that IPv6 will just show the same problems as IPv4,
and it will be more like 20-40 years down the road, and not the billions of years that some people seem to assume.  I think that
history shows that the leading mistake of all engineers is to underestimate future capacity needs, and I see that happening with
IPv6, just as it did with IPv4 (and with Y2K, and with the IBM PC address space, and so on, and so on).  I just thought I'd add my
$0.02.  Maybe I've overlooked something in IPv6, but I fear that I have not.

I'd be interested in hearing what others think of this potential problem.  (Or at least correct me if I've overlooked something in
IPv6 that will prevent the problems listed above from occurring.)

  -- Anthony



From owner-ietf-outbound  Mon Apr 24 09:31:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA03146
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 09:30:04 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02821
	for <ietf@ietf.org>; Mon, 24 Apr 2000 09:19:37 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA00538;
        Mon, 24 Apr 2000 09:19:01 -0400 (EDT)
Message-Id: <200004241319.JAA00538@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Ian King <iking@microsoft.com>
cc: "'Keith Moore'" <moore@cs.utk.edu>,
        "Dick St.Peters" <stpeters@NetHeaven.com>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Sun, 23 Apr 2000 22:08:14 PDT."
             <D5922CA42F8CD31189D800805F19A16C04B7B167@RED-MSG-48> 
Date: Mon, 24 Apr 2000 09:19:01 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Maybe we need to help make it easy to GET assignments of blocks of addresses
> for individuals/small businesses/etc.  Part of the problem is the obvious:
> IPv4 addresses are running short.  Part is the "K-Mart" level of product
> understanding I've experienced with many vendors of Internet connectivity.

right.  but for folks with a K-Mart level of understanding you need a 
K-Mart interface.  buy your "internet interface box" at the K-Mart,
take it home, plug it in to your phone line or whatever, and get
instant internet for all of the computers in your home.  
(almost just like NATs today except that you get static IP addresses).

> The first is an engineering problem, and we're working on that one (IPv6),
> right?  :-)  The second is a market problem, and I don't think it's going to
> go away until either telcos realize that they need to make a commitment to
> being in the IP business (and train their staff), or we have meaningful
> alternatives to the telcos for individual connectivity.  

I don't think it's just a marketing problem.  User interfaces are also 
an engineering issue.  Seems like there's a gap between the things we
produce in IETF and what is needed to actually make things work well
for K-Mart-level customers.  If the specifications defined by IETF
and implemented by ISPs aren't sufficient to allow plug-and-ping,
it's hardly surprising when NAT vendors fill in the gaps - and given
that the network didn't provide the level of service that was needed, 
it's hardly surprising that the gaps are filled in a technically dubious 
manner.

Keith



From owner-ietf-outbound  Mon Apr 24 09:41:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA03524
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 09:40:04 -0400 (EDT)
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02828
	for <ietf@ietf.org>; Mon, 24 Apr 2000 09:19:41 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-green.research.att.com (Postfix) with ESMTP
	id 1213E1E010; Mon, 24 Apr 2000 09:19:41 -0400 (EDT)
Received: from smb.research.att.com (sigaba.research.att.com [135.207.23.169])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id JAA07709;
	Mon, 24 Apr 2000 09:19:40 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 7281335DC2; Mon, 24 Apr 2000 09:19:39 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: dahigginbotham@ncdragonfly.com
Cc: "'Anthony Atkielski'" <anthony@atkielski.com>, ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 24 Apr 2000 09:19:39 -0400
Sender: smb@research.att.com
Message-Id: <20000424131939.7281335DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <BB2831D3689AD211B14C00104B14623B1E7569@HAZEN04>, "David A Higginbot
ham" writes:
>I agree! Why create a finite anything when an infinite possibility exists?
>On another note, I have heard the argument that a unique identifier already
>exists in the form of a MAC address why not make further use of it?

Would it surprise anyone to hear that all of that was considered and 
discussed, ad nauseum, in the IPng directorate?  That's right -- we weren't 
stupid or ignorant of technological history.  There were proponents for 
several different schemes, including fixed-length addresses of 64 and later 
128 bits, addresses where the two high-order bits denoted the multiple of 64 
to be used (that was my preference), or CLNP, where addresses could be quite 
variable in length (I forget the maximum).

But the first thing to remember is that there are tradeoffs.  Yes, infinitely 
long addresses are nice, but they're much harder to store in programs (you can 
no longer use a simple fixed-size structure for any tuple that includes an 
address) and (more importantly) route, since the router has to use the entire 
address in making its decision.  Furthermore, if it's a variable-length 
address, the router has to know where the end is, in order to look at the next 
field.  (Even if the destination address comes first, routers have to look at 
the source address because of ACLs -- though you don't want address-based 
security (and you shouldn't want it), you still need anti-spoofing filters.)  
I should add, btw, that there's a considerable advantage to having addresses 
be a multiple of the bus width in size, since that simplifies fetching the 
next field.)

As I said, I (and others) preferred a limited form of variable-length addresses. 
Given the various tradeoffs, we "lost".  One reason is something that was 
pointed out by a number of people:  code that isn't exercised generally doesn't
work well.  If we didn't have really long addresses in use from the beginning, 
some major implementations wouldn't support them properly.

Some minor points.  Using a MAC address was considered and rejected.  
First, not all machines have them.  Second, some machines have more than one 
-- which should be used?  Third, although MACs are supposed to be globally 
unique, accidents happen and there have been collisions.  Fourth, they're two 
short -- 48 bits then, moving towards 64 bits today.  Fifth, there's the issue 
of privacy.  Sixth -- and this rules out pure geographic addressing schemes -- 
IP addresses are tied to the routing system.  We don't know any other way to 
route large numbers of networks other than by using the high-order bits of the 
address.  If you want addresses allocated geographically, your routing has to 
be geographic.  (There have been designs for that, I should add, such as the 
Metropolitan Area Exchanges.  But for those to work, assorted ISPs would have 
to co-operate on a large scale, something that I don't think will happen.)  
Phone numbers are allocated geographically, but that only works because 
historically, most areas only had one monopoly phone company.  That has 
changed today, in many parts of the world, leading to complexities such as (in 
the U.S.) local number portability -- but telephone networks do one lookup per 
call, not one per packet.

		--Steve Bellovin




From owner-ietf-outbound  Mon Apr 24 10:41:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA05061
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 10:40:04 -0400 (EDT)
Received: from sean.ebone.net (IDENT:root@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04929
	for <ietf@ietf.org>; Mon, 24 Apr 2000 10:32:42 -0400 (EDT)
Received: (from smd@localhost)
	by sean.ebone.net (8.9.3/8.9.3) id QAA04024;
	Mon, 24 Apr 2000 16:32:38 +0200 (CEST)
Date: Mon, 24 Apr 2000 16:32:38 +0200 (CEST)
From: Sean Doran <smd@ebone.net>
Message-Id: <200004241432.QAA04024@sean.ebone.net>
To: iking@microsoft.com, moore@cs.utk.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org, stpeters@NetHeaven.com
X-Loop: ietf@ietf.org


[Keith Moore on a "KMart box"]
| take it home, plug it in to your phone line or whatever, and get
| instant internet for all of the computers in your home.  
| (almost just like NATs today except that you get static IP addresses).

No, not "or whatever" but "AND whatever".

Otherwise this is a nice but insufficient device, 
since there is an implicit presupposition that only
 one provider will be used by any given owner/lessor 
of this K-Mart box.

If one makes a broad policy decision that it should be possible
and simple for all very small users to be serviced simultaneously
by multiple providers, then you must be very careful about the
static IP address constraint.

Personally, I think _at least_ individual households should be
multihomed -- adjust your K-Mart box so that it can support multiple
interfaces.  Perhaps you might end up with a plug for your DSL or
POTS connection, a plug for your cable connection, and a plug for
your wireless or electricity-grid connection.

Traditional multihoming has some significant features:
	-- all the hosts in the multihomed entity have a fixed
	   set of addresses relative to one another
	   (i.e., hosts don't care about the "remote" topology)
	-- traffic is balanced in both directions in some fashion 
           across the set of multiple providers' connections
	-- if there is a partition in the network which
	   breaks connectivity through one provider, the
	   connectivity will automatically back-up through
	   the remaining provider(s) who are unaffected
	   by the partition

Unfortunately, IPv6's current addressing architecture makes it very
difficult to do this sort of traditional multihoming if one is not
a TLA.  This is a significant step backward from the current IPv4
situation, where one can persuade various operators to accept
more-specific prefixes (coloured with appropriate community
attributes) in order to optimize return traffic from particular
parts of the Internet.

Therefore, in order to support IPv6 house-network multihoming, so
as to preserve at least these three features of traditional
multihoming, either the current IPv6 addressing architecture's
restrictions on who can be a TLA must be abandoned (so each house
becomes a TLA), or NATs must be used to rewrite house-network
addresses into various PA address ranges supplied by the multiple
providers.

If it is reasonable to want to support multihoming individual
SMEs, households, or even "smd"s, IPv6's overall addressing and
routing architecture seems much ill-suited to the task WITHOUT
the presence of NAT.   

IPv6's larger address space is merely a necessary piece of an 
Internet which will not run out of numbers.   

NATs and NAT-like translators appear to be more and more a
fundamental tool in the IPv6 arsenal, and it unfortunate that
people position IPv6 as an alternative to NAT.

	Sean.



From owner-ietf-outbound  Mon Apr 24 11:51:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA06618
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 11:50:02 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA06552
	for <ietf@ietf.org>; Mon, 24 Apr 2000 11:47:33 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.14504-0@bells.cs.ucl.ac.uk>; Mon, 24 Apr 2000 16:43:37 +0100
To: Anthony Atkielski <anthony@atkielski.com>
cc: ietf <ietf@ietf.org>
Subject: Re: IPv6: Past mistakes repeated?
In-reply-to: Your message of "Mon, 24 Apr 2000 12:04:36 +0200." <002001bfadd4$80253fa0$0a00000a@wanadoo.fr>
Date: Mon, 24 Apr 2000 16:43:31 +0100
Message-ID: <2917.956591011@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


its ironic you should send this today, when 12 million people in
london, england, had to learn to dial 8 digits instead of 7 because of
lack of foresight from the telephone regualtor when re-numbering less
than a decade ago - it is reported that 2--30% of calls today are
misdialled...

repeat after me:
variable length addresses dont stop you having to renumber

of courser, the DNS hides all this from many applications, in exactly
the same way that NATs dont.

j.



From owner-ietf-outbound  Mon Apr 24 12:01:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA07000
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 12:00:03 -0400 (EDT)
Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06631
	for <IETF@IETF.org>; Mon, 24 Apr 2000 11:50:22 -0400 (EDT)
Received: from SERVER (adsl-63-199-7-253.dsl.snfc21.pacbell.net)
 by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with SMTP id <0FTJ00KDZ2G6SK@mta5.snfc21.pbi.net> for IETF@IETF.org; Mon,
 24 Apr 2000 08:45:42 -0700 (PDT)
Date: Mon, 24 Apr 2000 08:42:01 -0700
From: Peter Johansson <PJohansson@ACM.ORG>
Subject: RE: IPv6: Past mistakes repeated?
In-reply-to: <BB2831D3689AD211B14C00104B14623B1E7569@HAZEN04>
X-Sender: Celeborn@PacBell.net
To: IETF@ietf.org
Message-id: <3.0.5.32.20000424084201.00903d10@PacBell.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Content-type: text/plain; charset="us-ascii"
References: <BB2831D3689AD211B14C00104B14623B23B411@HAZEN04>
X-Loop: ietf@ietf.org

At 07:22 AM 4/24/00 -0400, David A Higginbotham wrote:

>On another note, I have heard the argument that a unique identifier already
>exists in the form of a MAC address why not make further use of it?

Well, because it's too Ethernet-centric, for one thing! Other transport
media (suitable to transport IP) do not necessarily base their link-levevl
addressing on static schemes whose addresses are assigned at time of
manufacture.

Regards,

Peter Johansson

Congruent Software, Inc.
98 Colorado Avenue
Berkeley, CA  94707

(510) 527-3926
(510) 527-3856 FAX

PJohansson@ACM.org



From owner-ietf-outbound  Mon Apr 24 12:21:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA07857
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 12:20:02 -0400 (EDT)
Received: from mail1.microsoft.com (mail1.microsoft.com [131.107.3.125])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA07579
	for <ietf@ietf.org>; Mon, 24 Apr 2000 12:12:21 -0400 (EDT)
Received: from 157.54.9.101 by mail1.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 24 Apr 2000 09:11:34 -0700 (Pacific Daylight Time)
Received: by INET-IMC-01 with Internet Mail Service (5.5.2651.58)
	id <JPA8H1XB>; Mon, 24 Apr 2000 09:11:33 -0700
Message-ID: <D5922CA42F8CD31189D800805F19A16C04B7B16B@RED-MSG-48>
From: Ian King <iking@microsoft.com>
To: "'Anthony Atkielski'" <anthony@atkielski.com>, ietf@ietf.org
Subject: RE: IPv6: Past mistakes repeated?
Date: Mon, 24 Apr 2000 09:11:23 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

"Near-perfect example"?  I beg to differ.  I used to work for a Local
Exchange Carrier.  

The telephone number situation in the United States has been one of
continual crisis for years, because of rapid growth in use (in part because
of Internet access!).  The area served by a given "area code" would be split
into smaller areas with multiple area codes; these days, those areas aren't
necessarily even contiguous.  Moving from seven-digit to (effectively)
ten-digit numbers was difficult, if not impossible, for some older
equipment; sometimes a kludge could be developed to allow the old equipment
to be used for a few more months or years, but often as not new equipment
was required, at considerable cost.  It was difficult for end users, too: in
addition to the confusion everyone suffered during the transition (I still
get scads of wrong numbers on my cellphone, because people forget the area
code is needed), businesses had to spend great sums of money to revise their
public appearance (advertising, letterhead, etc.).  

And, often as not, we'd do it all over again a few months later.  

My point is that ANY numbering scheme is difficult to change, once it's in
place.  Someone else on this thread made a good point, however, that the
administration of that scheme can make worlds of difference - this person's
point was about "giveaway" assignment of large portions of the address
space, "because there's so much" -- hm, sounds like the exhaustion of
Earth's natural resources, too.  :-)  I'd suggest that address assignment
policy should keep process lightweight, so that it is realistic for
businesses to regularly ask for assignments in more granular chunks; rather
than grabbing a class A-size space "just in case", big users would be
willing to request another 256 when the new branch office opens, then
another 64 for the summer interns... and so individuals can easily get
multiple addresses through an ISP.  

In fact, it should be as easy as getting a telephone number.  -- Ian 

> -----Original Message-----
> From: Anthony Atkielski [mailto:anthony@atkielski.com]
> Sent: Monday, April 24, 2000 3:05 AM
> To: ietf@ietf.org
> Subject: IPv6: Past mistakes repeated?
> 
> 
[snip]
> The only real solution to this is an open-ended addressing 
> scheme--one to which digits can be added as required.  And it just so
> happens that a near-perfect example of such a scheme is right 
> in front of us all, in the form of the telephone system.  Telephone
> numbers have never had a fixed number of digits.  The number 
> has always been variable, and has simply expanded as needs 
> have changed
> and increased.  At one time, a four-digit number was enough 
> to reach anyone.  Then seven-digit numbers became necessary.  Then an
> area code became necessary.  And finally, a country code 
> became necessary.  Perhaps a planet code will be necessary at 
> some point in
> the future.  But the key feature of the telephone system is 
> that nobody ever decided upon a fixed number of digits in the 
> beginning,
> and so there is no insurmountable obstacle to adding digits 
> forever, if necessary.  Imagine what things would be like if 
> someone had
> decided in 1900 that seven digits would be enough for the 
> whole world, and then equipment around the world were designed only to
> handle seven digits, with no room for expansion.  What would 
> happen when it came time to install the 10,000,000th 
> telephone, or when
> careless allocation exhausted the seven-digit space?
> 
[snip]



From owner-ietf-outbound  Mon Apr 24 12:31:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA08237
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 12:30:06 -0400 (EDT)
Received: from web1406.mail.yahoo.com (web1406.mail.yahoo.com [128.11.23.170])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA07911
	for <ietf@ietf.org>; Mon, 24 Apr 2000 12:21:10 -0400 (EDT)
Received: (qmail 21971 invoked by uid 60001); 24 Apr 2000 16:21:10 -0000
Message-ID: <20000424162110.21970.qmail@web1406.mail.yahoo.com>
Received: from [209.239.207.103] by web1406.mail.yahoo.com; Mon, 24 Apr 2000 09:21:10 PDT
Date: Mon, 24 Apr 2000 09:21:10 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Cc: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org


--- Henning Schulzrinne <schulzrinne@cs.columbia.edu> wrote:
> It might be useful to point out more clearly the common characteristics
> of protocols that are broken by NATs. These include, in particular,
> protocols that use one connection to establish another data flow. Such
> protocols include ftp, SIP and RTSP (the latter is not mentioned yet in
> the draft, but NATs also interfere with its operation). Note that unless
> we forego such control protocol designs altogether, NATs in principle
> break these unless every host has an external DNS mapping. 

We had originally considered having a section in the draft listing 
common characteristics of all the applications that fail. Then we 
decided against it, as such a section already exists in RFC 2663 and 
"Traditional-NAT" draft. Instead, we chose to focus on gathering 
the various protocols/applications that fail, why they fail and if
there are any work-arounds. Input on the IETF list, past few days, 
has been great. The draft should look much better when the input is
all folded in. 

For example, the problem you point out with applications with 
inter-dependent control and data sessions can be found listed 
as NAT limitation in section 8.2 of RFC 2663.

>                                                            (Thus, in
> reference to a recent message to just design NAT-friendly protocols,
> this means in practice that such "out-of-band" designs could not be
> supported by this NATy version of the Internet. In effect, this leads to
> the abomination of carrying real-time data in HTTP connections.)
> 
Agreed. The intent of NAT-friendly guidelines was merely to point 
the gotchas that can be fixed - not to dissuade development of 
protocols that cannot be NAT-friendly.


> Other protocol designs are those that are symmetric rather than
> client-server based. This affects all Internet telephony or event-based
> protocols (IM and generalizations) unless they maintain an outbound
> connection with a server acting as their representative to the globally
> routed Internet. The latter obviously does not address the media stream
> addressing problems.
> 
I assume, you mean Peer-to-peer protocols/applications require 
bi-directional flows at a minimum. Clearly, it is a problem doing
this across traditional NAT (i.e., Basic-NAT or NAPT) because
Traditional-NAT fundamentally is unidirectional and supports 
out-bound flows only. Bidirectional-NAT might work with these
apps (with all the caveats that go with address translation). 

> -- 
> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs
> 

regards,
suresh

__________________________________________________
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com



From owner-ietf-outbound  Mon Apr 24 12:51:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA08664
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 12:50:03 -0400 (EDT)
Received: from postoffice.cisco.com (postoffice.cisco.com [171.69.198.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08535
	for <ietf@ietf.org>; Mon, 24 Apr 2000 12:42:44 -0400 (EDT)
Received: from [10.19.130.188] (deering-dsl3.cisco.com [10.19.130.188]) by postoffice.cisco.com (8.8.7-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id JAA24145; Mon, 24 Apr 2000 09:41:18 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@postoffice
Message-Id: <v04220804b52a1d69f905@[10.19.130.188]>
In-Reply-To: <200004241432.QAA04024@sean.ebone.net>
References: <200004241432.QAA04024@sean.ebone.net>
Date: Mon, 24 Apr 2000 09:42:06 -0700
To: Sean Doran <smd@ebone.net>
From: Steve Deering <deering@cisco.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: iking@microsoft.com, moore@cs.utk.edu, ietf@ietf.org,
        stpeters@NetHeaven.com
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 4:32 PM +0200 4/24/00, Sean Doran wrote:
>Unfortunately, IPv6's current addressing architecture makes it very
>difficult to do this sort of traditional multihoming if one is not
>a TLA.  This is a significant step backward from the current IPv4
>situation, where one can persuade various operators to accept
>more-specific prefixes (coloured with appropriate community
>attributes) in order to optimize return traffic from particular
>parts of the Internet.

Sean,

That is widely claimed but incorrect.  Nothing in the IPv6 addressing
architecture prevents a user from negotiating with multiple operators
to accept any prefix assigned to that user.  IPv6 retains the same
capability as IPv4 in that respect.

>Therefore, in order to support IPv6 house-network multihoming, so
>as to preserve at least these three features of traditional
>multihoming, either the current IPv6 addressing architecture's
>restrictions on who can be a TLA must be abandoned (so each house
>becomes a TLA),...

The consequences of those restrictions are not what you imagined, but
even so, making each house a TLA does not strike me as a scalable
multihoming solution for very large numbers of houses, given the current
state of the routing art.

>...or NATs must be used to rewrite house-network addresses into various
>PA address ranges supplied by the multiple providers.

That's not the only possible alternative, and it is an alternative that
creates a bunch of other unsolved problems (see earlier messages in this
thread).

>IPv6's larger address space is merely a necessary piece of an 
>Internet which will not run out of numbers.  

Wow, we actually agree on something!  (Though I could quibble over the
"merely".)

Steve



From owner-ietf-outbound  Mon Apr 24 13:01:50 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA08933
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 13:00:03 -0400 (EDT)
Received: from garlic.amaranth.net (garlic.amaranth.net [216.235.243.195])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08619
	for <ietf@ietf.org>; Mon, 24 Apr 2000 12:48:50 -0400 (EDT)
Received: from senie.com (garlic.amaranth.net [216.235.243.195])
	(authenticated)
	by garlic.amaranth.net (8.10.0/8.10.0) with ESMTP id e3OGmRN29118;
	Mon, 24 Apr 2000 12:48:27 -0400
Message-ID: <39047ADB.84B3F256@senie.com>
Date: Mon, 24 Apr 2000 12:48:27 -0400
From: Daniel Senie <dts@senie.com>
Organization: Amaranth Networks Inc.
X-Mailer: Mozilla 4.72 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ian King <iking@microsoft.com>
CC: "'Anthony Atkielski'" <anthony@atkielski.com>, ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
References: <D5922CA42F8CD31189D800805F19A16C04B7B16B@RED-MSG-48>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Ian King wrote:
> 
> "Near-perfect example"?  I beg to differ.  I used to work for a Local
> Exchange Carrier.
> 
> The telephone number situation in the United States has been one of
> continual crisis for years, because of rapid growth in use (in part because
> of Internet access!).  The area served by a given "area code" would be split
> into smaller areas with multiple area codes; these days, those areas aren't
> necessarily even contiguous.  Moving from seven-digit to (effectively)
> ten-digit numbers was difficult, if not impossible, for some older
> equipment; sometimes a kludge could be developed to allow the old equipment
> to be used for a few more months or years, but often as not new equipment
> was required, at considerable cost.  It was difficult for end users, too: in
> addition to the confusion everyone suffered during the transition (I still
> get scads of wrong numbers on my cellphone, because people forget the area
> code is needed), businesses had to spend great sums of money to revise their
> public appearance (advertising, letterhead, etc.).
> 
> And, often as not, we'd do it all over again a few months later.

We've now got number portability. I've got a choice of local exchange
carriers. I can get service from Bell Atlantic or from MediaOne. I can
keep the same phone number when I move from one to the other.

From the reports I read, this was implemented by mapping phone numbers
to some other tag (which the user doesn't see) which is used to get the
calls to the proper carrier and ultimately to the proper user.

Sounds a whole lot like using DNS to map names to IP addresses. Of
course we expose users to IP addresses WAY too often, and overuse them
in applications as well, for this analogy to be really workable for the
Internet.

Users shouldn't care or know about the network's internal addressing.
Some of the application issues with NATs spring directly from this issue
(e.g. user of X-terminal setting display based on IP address instead of
DNS name).

-- 
-----------------------------------------------------------------
Daniel Senie                                        dts@senie.com
Amaranth Networks Inc.                    http://www.amaranth.com



From owner-ietf-outbound  Mon Apr 24 13:31:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09570
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 13:30:02 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09268
	for <ietf@ietf.org>; Mon, 24 Apr 2000 13:20:23 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id NAA07529
	for <ietf@ietf.org>; Mon, 24 Apr 2000 13:19:27 -0400
Sender: francis@localhost.localdomain
Message-ID: <3904821D.779F3A5@ecal.com>
Date: Mon, 24 Apr 2000 13:19:26 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
References: <4.3.2.20000422201841.00c435d0@127.0.0.1>
	 <200004222110.RAA00745@astro.cs.utk.edu> <4.3.2.20000423224201.00bbfd30@127.0.0.1>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Richard Shockey wrote:

> If we were looking at a typicial household and you wanted to plan for the
> future I would have to assume 1 address for every single thing plugged in
> to any thing, phone, electrical appliances, water, maybe even sewage. Yes
> an IP address on your toilet.

[...]

> Businesses are different but some of the needs are the same.  The typical
> business customer has multiple devices at their command, many of which are
> currently IP addressable or certainly should be, phone, cell phone,
> printer, copier, fax, scanners, PDA's, cameras. 15 addressees per employee?

Maybe more--business needs would probably be almost a superset of home needs
(only major appliances I can think of that are in my home but not my office
are the washer and dryer).  If the sewage utilities find it useful to monitor
toilets, they'll want to include businesses--they'll probably start with
businesses, in fact, which will be more amenable to price incentives.

--
/=================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.   |
|Chief Scientist |================================================|
|eCal Corp.      |"How can one conceive of a one party system in a|
|francis@ecal.com|country that has over 200 varieties of cheese?" |
|                |--Charles de Gaulle                             |
\=================================================================/





From owner-ietf-outbound  Mon Apr 24 13:41:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09902
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 13:40:03 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09269
	for <ietf@ietf.org>; Mon, 24 Apr 2000 13:20:23 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id NAA07535
	for <ietf@ietf.org>; Mon, 24 Apr 2000 13:20:18 -0400
Sender: francis@localhost.localdomain
Message-ID: <39048252.257ED5ED@ecal.com>
Date: Mon, 24 Apr 2000 13:20:18 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Patent protection from NATs
References: <39030794.28EFD3BC@cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Henning Schulzrinne wrote:

> Indeed, I
> think we should get together a group of people to patent all the
> architecturally bad ideas (call it the "RSI group"), as they'll appear
> sooner or later. That will give us 20 years of respite...

...provided somebody pays the legal fees to enforce the patents.

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |The cheapest, fastest, most reliable components|
|francis@ecal.com|of a computer system are those that aren't     |
|                |there.--Gordon Bell                            |
\================================================================/





From owner-ietf-outbound  Mon Apr 24 13:51:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA10103
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 13:50:03 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09310
	for <ietf@ietf.org>; Mon, 24 Apr 2000 13:22:31 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id NAA07547
	for <ietf@ietf.org>; Mon, 24 Apr 2000 13:21:34 -0400
Sender: francis@localhost.localdomain
Message-ID: <3904829E.6292EA65@ecal.com>
Date: Mon, 24 Apr 2000 13:21:34 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
References: <D5922CA42F8CD31189D800805F19A16C04B7B16B@RED-MSG-48>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Ian King wrote:

> I'd suggest that address assignment
> policy should keep process lightweight, so that it is realistic for
> businesses to regularly ask for assignments in more granular chunks; rather
> than grabbing a class A-size space "just in case", big users would be
> willing to request another 256 when the new branch office opens

Wasn't one of the design goals of IPv6 to make renumbering easier, so that
people could move from small assignments to large ones?

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |The cheapest, fastest, most reliable components|
|francis@ecal.com|of a computer system are those that aren't     |
|                |there.--Gordon Bell                            |
\================================================================/





From owner-ietf-outbound  Mon Apr 24 14:01:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10487
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 14:00:03 -0400 (EDT)
Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09867
	for <ietf@ietf.org>; Mon, 24 Apr 2000 13:38:55 -0400 (EDT)
Received: from laptop.ix.netcom.com ([209.138.155.55])
	by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id NAA13337;
	Mon, 24 Apr 2000 13:38:44 -0400 (EDT)
Message-Id: <4.3.2.20000424122949.00b80140@127.0.0.1>
X-Sender: rshockey/popd.ix.netcom.com@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Mon, 24 Apr 2000 12:39:09 -0500
To: Daniel Senie <dts@senie.com>, Ian King <iking@microsoft.com>
From: Richard Shockey <rshockey@ix.netcom.com>
Subject: Re: IPv6: Past mistakes repeated?
Cc: "'Anthony Atkielski'" <anthony@atkielski.com>, ietf@ietf.org
In-Reply-To: <39047ADB.84B3F256@senie.com>
References: <D5922CA42F8CD31189D800805F19A16C04B7B16B@RED-MSG-48>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org


>
> > The telephone number situation in the United States has been one of
> > continual crisis for years, because of rapid growth in use (in part because
> > of Internet access!).  The area served by a given "area code" would be 
> split
> > into smaller areas with multiple area codes; these days, those areas aren't
> > necessarily even contiguous.  Moving from seven-digit to (effectively)
> > ten-digit numbers was difficult, if not impossible, for some older
> > equipment; sometimes a kludge could be developed to allow the old equipment
> > to be used for a few more months or years, but often as not new equipment
> > was required, at considerable cost.  It was difficult for end users, 
> too: in
> > addition to the confusion everyone suffered during the transition (I still
> > get scads of wrong numbers on my cellphone, because people forget the area
> > code is needed), businesses had to spend great sums of money to revise 
> their
> > public appearance (advertising, letterhead, etc.).
> >
> > And, often as not, we'd do it all over again a few months later.
>
>We've now got number portability. I've got a choice of local exchange
>carriers. I can get service from Bell Atlantic or from MediaOne. I can
>keep the same phone number when I move from one to the other.

FYI And by 2002 you will be able to port your number from your land line 
phone service to your cell phone as well...that is  called "service 
portability".



> From the reports I read, this was implemented by mapping phone numbers
>to some other tag (which the user doesn't see) which is used to get the
>calls to the proper carrier and ultimately to the proper user.

Yep ...essentially phone numbers are nothing more than names to the IN.

FYI  there is a ID on how the Number Portability system works and there 
have been recent FCC rulings on Number Conservation and Pooling which 
direct teleco's not to hoard phone numbers or else they will be taken away.

It is a system that has worked remarkably well and is rapidly being adopted 
my many other countries as well.




>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-foster-e164-gstn-np-00.txt



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey
Shockey Consulting LLC
8045 Big Bend Blvd. Suite 110
St. Louis, MO 63119
Voice 314.918.9020
eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
INTERNET Mail & IFAX : rshockey@ix.netcom.com
GSTN Fax 314.918.9015
MediaGate iPost VoiceMail and Fax 800.260.4464
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<



From owner-ietf-outbound  Mon Apr 24 14:11:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10838
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 14:10:02 -0400 (EDT)
Received: from saint.heaven.net (saint.heaven.net [198.69.28.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09878
	for <ietf@ietf.org>; Mon, 24 Apr 2000 13:39:50 -0400 (EDT)
Received: (from stpeters@localhost)
	by saint.heaven.net (8.9.3/8.9.3) id NAA00759;
	Mon, 24 Apr 2000 13:39:39 -0400
From: "Dick St.Peters" <stpeters@NetHeaven.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14596.34523.398151.914260@saint.heaven.net>
Date: Mon, 24 Apr 2000 13:39:39 -0400 (EDT)
To: ietf@ietf.org
Subject: RE: IPv6: Past mistakes repeated?
In-Reply-To: <3.0.5.32.20000424084201.00903d10@PacBell.net>
References: <BB2831D3689AD211B14C00104B14623B23B411@HAZEN04>
	<3.0.5.32.20000424084201.00903d10@PacBell.net>
X-Mailer: VM 6.72 under Emacs 19.34.1
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> On another note, I have heard the argument that a unique identifier already
> exists in the form of a MAC address why not make further use of it?

I can remember early TCP/IP implementations that used class A
addressing only, with the host portion of the Enet MAC address as the
host portion of the IP address - "because ARP is too hard" or
something like that.  I think the first Suns did this.

--
Dick St.Peters, stpeters@NetHeaven.com 
Gatekeeper, NetHeaven, Saratoga Springs, NY
Saratoga/Albany/Amsterdam/BoltonLanding/Cobleskill/Greenwich/
GlensFalls/LakePlacid/NorthCreek/Plattsburgh/...
    Oldest Internet service based in the Adirondack-Albany region



From owner-ietf-outbound  Mon Apr 24 14:21:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA11269
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 14:20:05 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09947
	for <ietf@ietf.org>; Mon, 24 Apr 2000 13:41:23 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA01442;
        Mon, 24 Apr 2000 13:40:48 -0400 (EDT)
Message-Id: <200004241740.NAA01442@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Sean Doran <smd@ebone.net>
cc: iking@microsoft.com, moore@cs.utk.edu, ietf@ietf.org,
        stpeters@NetHeaven.com
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Mon, 24 Apr 2000 16:32:38 +0200."
             <200004241432.QAA04024@sean.ebone.net> 
Date: Mon, 24 Apr 2000 13:40:48 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> [Keith Moore on a "KMart box"]
> | take it home, plug it in to your phone line or whatever, and get
> | instant internet for all of the computers in your home.  
> | (almost just like NATs today except that you get static IP addresses).
> 
> No, not "or whatever" but "AND whatever".
> 
> Otherwise this is a nice but insufficient device, 
> since there is an implicit presupposition that only
> one provider will be used by any given owner/lessor 
> of this K-Mart box.

sorry if I oversimplified things.  it's clear to me that you have
to allow for user selection of providers, but I was trying to 
make a simple illustration of how this might work, not write 
the requirements document.
 
> If one makes a broad policy decision that it should be possible
> and simple for all very small users to be serviced simultaneously
> by multiple providers, then you must be very careful about the
> static IP address constraint.

I'm all for user selection of providers, but 'serviced simultaneously
by multiple providers' seems like a stretch.  as I'm sure you are aware,
traditional multihoming has scaling implications for the routing 
infrastructure - it's far from clear that it's feasible for every
household to be traditionally multihomed.

my view is that folks who want traditional multihoming 
(i.e. they who want their own entries in core routers' tables)
will sooner or later have to pay major ISPs for those entries.  
I have heard that you can pay individual ISPs for this now.  
so maybe what we need is a clearinghouse organization or two 
that provides one-stop shopping - take your money and ensure
that your routing table entry is maintained in each of several
major ISPs routers.  once we have that kind of cost recovery model,
folks who really need traditional multihoming (and can afford it)
will be able to get it - it won't matter how big your subnet mask is.

> Traditional multihoming has some significant features:
> 	-- all the hosts in the multihomed entity have a fixed
> 	   set of addresses relative to one another
> 	   (i.e., hosts don't care about the "remote" topology)
> 	-- traffic is balanced in both directions in some fashion 
>            across the set of multiple providers' connections
> 	-- if there is a partition in the network which
> 	   breaks connectivity through one provider, the
> 	   connectivity will automatically back-up through
> 	   the remaining provider(s) who are unaffected
> 	   by the partition

traditional multihoming is very useful under the right circumstances,
though you need a lot more than just multiple connections advertised
to the net to make it work well.

> Unfortunately, IPv6's current addressing architecture makes it very
> difficult to do this sort of traditional multihoming if one is not
> a TLA.  This is a significant step backward from the current IPv4
> situation, where one can persuade various operators to accept
> more-specific prefixes (coloured with appropriate community
> attributes) in order to optimize return traffic from particular
> parts of the Internet.

I agree that traditional multihoming should not be limited to TLA-sized
portions of the net, and I expect that in practice, even in IPv6, 
it will not be so limited.  having fixed partition sizes in IP addresses
is a bad idea - we learned that long ago with fixed class sizes. And
IPv6-style multihoming through DNS has some fairly significant limitations - 
not that it's not useful for some cases, but for many applications it's 
not going to substitute for traditional multihoming.  

> Therefore, in order to support IPv6 house-network multihoming, so
> as to preserve at least these three features of traditional
> multihoming, either the current IPv6 addressing architecture's
> restrictions on who can be a TLA must be abandoned (so each house
> becomes a TLA), or NATs must be used to rewrite house-network
> addresses into various PA address ranges supplied by the multiple
> providers.

it's not at all clear to me why households need traditional multihoming,
nor how to make it feasible for households to have it.  so I would regard
this as overdesign of the home 'internet interface box'

and given the degree of harm that NATs have done to IPv4, I hope they
never rear their ugly heads in IPv6.

> If it is reasonable to want to support multihoming individual
> SMEs, households, or even "smd"s, IPv6's overall addressing and
> routing architecture seems much ill-suited to the task WITHOUT
> the presence of NAT.   

what's the point of traditional multihoming anyway if you have to
have NATs?  you might as well do IPv6-style multihoming - assign a 
separate address prefix to every incoming connection and let the
hosts sort it out.  you don't need NATs to do this.

> IPv6's larger address space is merely a necessary piece of an 
> Internet which will not run out of numbers.   
> 
> NATs and NAT-like translators appear to be more and more a
> fundamental tool in the IPv6 arsenal, and it unfortunate that
> people position IPv6 as an alternative to NAT.

NATs can be a transition tool for connecting between IPv4 and IPv6, 
but NATs should never get in the way of a native IPv6 connection.

Keith



From owner-ietf-outbound  Mon Apr 24 14:31:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA11542
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 14:30:04 -0400 (EDT)
Received: from squid10.clearaccess.net (IDENT:root@[204.214.6.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10064
	for <ietf@ietf.org>; Mon, 24 Apr 2000 13:47:51 -0400 (EDT)
Received: from tech20 ([204.214.6.254])
	by squid10.clearaccess.net (8.9.3/8.9.3) with SMTP id MAA17703
	for <ietf@ietf.org>; Mon, 24 Apr 2000 12:50:20 -0400
From: "Scot Mc Pherson" <smcpherson@clearaccess.net>
To: <ietf@ietf.org>
Subject: RE: Universal Network Language
Date: Mon, 24 Apr 2000 13:47:33 -0400
Message-ID: <006401bfae15$2c2dab80$4cc8a8c0@clearaccess.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
In-reply-to: <4.3.1.2.20000421235346.0319bcd0@flipper.cisco.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Pardon my ignorance, but isn't this the function of IP?

-Scot Mc Pherson, N2UPA
-Sr. Network Analyst
-ClearAccess Communications
-Ph: 941.744.5757 ext. 210
-Fax: 941.744.0629
-mailto:smcpherson@clearaccess.net
-http://www.clearaccess.net

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Friday, April 21, 2000 11:54 AM
To: Anders Feder
Cc: ietf@ietf.org
Subject: Re: Universal Network Language


At 11:01 PM 4/20/00 +0200, Anders Feder wrote:
>The translation system being developed for the United Nations, the
Universal
>Network Language (UNL), looks quite promising. Does the IETF have any plans
>regarding this system?

not specifically. Care to make an argument that we should?



From owner-ietf-outbound  Mon Apr 24 15:07:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA12171
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 15:00:03 -0400 (EDT)
Received: from leonid.genesyslab.com (pbinat33.genesyslab.com [209.233.177.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12113
	for <ietf@ietf.org>; Mon, 24 Apr 2000 14:57:25 -0400 (EDT)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id LAA19564;
	Mon, 24 Apr 2000 11:55:05 -0700
Date: Mon, 24 Apr 2000 11:55:05 -0700
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200004241855.LAA19564@leonid.genesyslab.com>
To: dahigginbotham@ncdragonfly.com, smb@research.att.com
Subject: Re: IPv6: Past mistakes repeated?
Cc: anthony@atkielski.com, ietf@ietf.org
X-Loop: ietf@ietf.org

>From: "Steven M. Bellovin" <smb@research.att.com>
>
>In message <BB2831D3689AD211B14C00104B14623B1E7569@HAZEN04>, "David A Higginbot
>ham" writes:
>>I agree! Why create a finite anything when an infinite possibility exists?
>>On another note, I have heard the argument that a unique identifier already
>>exists in the form of a MAC address why not make further use of it?
>
>Would it surprise anyone to hear that all of that was considered and
>discussed, ad nauseum, in the IPng directorate?  That's right -- we weren't
>stupid or ignorant of technological history.  There were proponents for
>several different schemes, including fixed-length addresses of 64 and later
>128 bits, addresses where the two high-order bits denoted the multiple of 64
>to be used (that was my preference), or CLNP, where addresses could be quite
>variable in length (I forget the maximum).
>
>But the first thing to remember is that there are tradeoffs.  Yes, infinitely
>long addresses are nice, but they're much harder to store in programs (you can
>no longer use a simple fixed-size structure for any tuple that includes an
>address) and (more importantly) route, since the router has to use the entire
>address in making its decision.  Furthermore, if it's a variable-length
>address, the router has to know where the end is, in order to look at the next
>field.  (Even if the destination address comes first, routers have to look at
>the source address because of ACLs -- though you don't want address-based
>security (and you shouldn't want it), you still need anti-spoofing filters.)
>I should add, btw, that there's a considerable advantage to having addresses
>be a multiple of the bus width in size, since that simplifies fetching the
>next field.)
>
   Routers may use the different addresses for routing. Outbound router
may assign "route address" to keep intermediate route tables small.

   It is not the same as NAT because original and real destination address
never replaced.

		       - Leonid Yegoshin.



From owner-ietf-outbound  Mon Apr 24 15:11:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA12501
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 15:10:03 -0400 (EDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12173
	for <ietf@ietf.org>; Mon, 24 Apr 2000 15:00:07 -0400 (EDT)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id LAA14699;
	Mon, 24 Apr 2000 11:59:41 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id SAA05983;
	Mon, 24 Apr 2000 18:59:41 GMT
Date: Mon, 24 Apr 2000 18:59:41 GMT
Message-Id: <200004241859.SAA05983@gra.isi.edu>
To: ietf@ietf.org, stpeters@NetHeaven.com
Subject: RE: IPv6: Past mistakes repeated?
X-Sun-Charset: US-ASCII
X-Loop: ietf@ietf.org

  *> 
  *> I can remember early TCP/IP implementations that used class A
  *> addressing only, with the host portion of the Enet MAC address as the
  *> host portion of the IP address - "because ARP is too hard" or
  *> something like that.  I think the first Suns did this.
  *> 
  *> --

Dick,

Right idea, wrong link layer. The low-order 24 bits of an IP address
was originally a 24-bit ARPANET (/Milnet/DDN) host address.

Bob Braden



From owner-ietf-outbound  Mon Apr 24 15:21:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA12669
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 15:20:03 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12420
	for <ietf@ietf.org>; Mon, 24 Apr 2000 15:07:29 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id PAA07914
	for <ietf@ietf.org>; Mon, 24 Apr 2000 15:06:21 -0400
Sender: francis@localhost.localdomain
Message-ID: <39049B2D.5E22F76@ecal.com>
Date: Mon, 24 Apr 2000 15:06:21 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
References: <200004241740.NAA01442@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Keith Moore wrote:

> it's not at all clear to me why households need traditional multihoming,
> nor how to make it feasible for households to have it.  so I would regard
> this as overdesign of the home 'internet interface box'

Now that I've got a decent DSL provider, I've found that the least reliable
component of my Net access is the power line: my DSL just works, but the power
company has been flaking out 2-3 times a week for the past month or so.  (I
have my computers on UPSes, but your average K-Mart Box user wouldn't.)
Multihoming wouldn't solve that.

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |Using strong crypto on the Internet is like    |
|francis@ecal.com|using an armored car to transport money from   |
|                |someone living in a tent to someone living in a|
|                |cardboard box.                                 |
\================================================================/





From owner-ietf-outbound  Mon Apr 24 15:31:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA13000
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 15:30:03 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12472
	for <ietf@ietf.org>; Mon, 24 Apr 2000 15:09:35 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id PAA07922
	for <ietf@ietf.org>; Mon, 24 Apr 2000 15:08:40 -0400
Sender: francis@localhost.localdomain
Message-ID: <39049BB8.B15D649B@ecal.com>
Date: Mon, 24 Apr 2000 15:08:40 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Universal Network Language
References: <006401bfae15$2c2dab80$4cc8a8c0@clearaccess.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Scot Mc Pherson wrote:

> Pardon my ignorance, but isn't this the function of IP?

No, it turns out that what they mean by UNL is an artificial human language, a
common intermediary that any human text can be translated into; they postulate
translation servers that know how to translate between UNL and specific human
languages.  Much higher in the stack than IP.  :-)

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |"There will be no more there. We will all be |
|francis@ecal.com|here."--networkMCI ad                        |
\==============================================================/





From owner-ietf-outbound  Mon Apr 24 15:51:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA13403
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 15:50:03 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12713
	for <ietf@ietf.org>; Mon, 24 Apr 2000 15:21:35 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id PAA07009;
	Mon, 24 Apr 2000 15:21:29 -0400
Date: Mon, 24 Apr 2000 15:21:29 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200004241921.PAA07009@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: RE: IPv6: Past mistakes repeated?
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

A couple of routing points, not related to NAT:

    > From: Ian King <iking@microsoft.com>

    > so that it is realistic for businesses to regularly ask for assignments
    > in more granular chunks; rather than grabbing a class A-size space
    > "just in case", big users would be willing to request another 256 when
    > the new branch office opens, then another 64 for the summer interns...

Sorry, this doesn't work - at least with IPvN (N=4,6) addresses as currently
constituted. The routing system (i.e. the software that computes paths
through the network) uses those addresses as the namespace it works on, and
to make the routing scale properly (a.k.a. "keep the network running"), those
addresses have to be aggregable.

In other words, you need to be able to have a single routing table entry that
covers a chunk of the network (such as a company's in-house network) - and
that routing table entry can't include other things as well. If a company,
etc, had addresses assigned in dribs and drabs, the way you suggest, that
company's addresses would no longer have that property.

Other namespaces, which don't have to include location information, just
identification (e.g. IEEE 48-bit numbers) work just fine with this kind of
allocation policy - but not any namespace used by path selection in a large
network.


    > From: Steve Deering <deering@cisco.com>

    > making each house a TLA does not strike me as a scalable multihoming
    > solution for very large numbers of houses, given the current state of
    > the routing art.

The restriction has little to do with the current state of the routing art
(which is not to say that better path-selection architectures than the one
the Internet is currently using do not exist :-).

Even with the best routing system, it still couldn't support tracking large
numbers of houses as individual destinations (i.e. having individual routing
tables extries across the global scope) - even if the routers had large
enough route table memories to hold the 100's of millions of routes which
could result.

	Noel



From owner-ietf-outbound  Mon Apr 24 16:01:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA13600
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 16:00:03 -0400 (EDT)
Received: from sean.ebone.net (IDENT:root@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13219
	for <ietf@ietf.org>; Mon, 24 Apr 2000 15:35:55 -0400 (EDT)
Received: (from smd@localhost)
	by sean.ebone.net (8.9.3/8.9.3) id VAA04803;
	Mon, 24 Apr 2000 21:35:51 +0200 (CEST)
Date: Mon, 24 Apr 2000 21:35:51 +0200 (CEST)
From: Sean Doran <smd@ebone.net>
Message-Id: <200004241935.VAA04803@sean.ebone.net>
To: moore@cs.utk.edu, smd@ebone.net
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org


| it's not at all clear to me why households need traditional multihoming,
| nor how to make it feasible for households to have it.  so I would regard
| this as overdesign of the home 'internet interface box'

Three observations:

	1. 

	In the past, when and if large arrogant backbone providers like
	me used to say that a push against multihoming was a good way
	to avoid stressing the current routing system by avoiding
	address deaggregation and globally-visible reachable changes
	that could result, we would get flayed alive.

	The lesson: always assume that, no matter how technically odd
	one thinks it may be, everyone will want to multihome if it is
	feasible to do so.

	2.

	Multihomed entities like to submit bandwidth increase orders
	to one or the other provider over time, depending on a
	number of factors.   Likewise, singlehomed entities appear
	to want to multihome, and at some point rather than upgrade
	the single connection to the Internet, will order a second
	connection from a different provider, and attempt to do
	traditional multihoming.

	3.

	In many areas nearly every household PRESENTLY has several
	possible fixed, wireless and switched facilities over which
	Internet access can be offered.

I would say that rather than being overdesigned, that it is slightly
underdesigned, because it does not address the possibility of multitenanted
households, with (for example) his&hers routing policies.  (For example,
he uses a cable provider for access, she has a DSL paid for her by her job
so she can do her engineering activities from home).

| and given the degree of harm that NATs have done to IPv4, I hope they
| never rear their ugly heads in IPv6.

Noel's right, your knees must really hurt!

| what's the point of traditional multihoming anyway if you have to
| have NATs?  you might as well do IPv6-style multihoming - assign a 
| separate address prefix to every incoming connection and let the
| hosts sort it out.  you don't need NATs to do this.

The NAT function here is subsumed into the host.

Pushing NATs into hosts is an attractive idea, but it does
require alot more knowledge of the network in the hosts, and
one can gain no economies of scale that a standalone NAT shared
by many hosts can achieve.  Also, if the hosts themselves are 
singly homed to a particular LIS (e.g. an ethernet with hosts and a
router with interfaces to several providers), they will have a
devil of a time incorporating a NAT function.

| NATs can be a transition tool for connecting between IPv4 and IPv6, 
| but NATs should never get in the way of a native IPv6 connection.

They will, though.

	Sean.



From owner-ietf-outbound  Mon Apr 24 16:11:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA13787
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 16:10:03 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13226
	for <ietf@ietf.org>; Mon, 24 Apr 2000 15:36:03 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3OJZlB28952;
	Mon, 24 Apr 2000 15:35:47 -0400
Message-Id: <200004241935.e3OJZlB28952@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: John Stracke <francis@ecal.com>
cc: ietf@ietf.org
Subject: Re: Universal Network Language 
In-reply-to: Your message of "Mon, 24 Apr 2000 15:08:40 EDT."
             <39049BB8.B15D649B@ecal.com> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <006401bfae15$2c2dab80$4cc8a8c0@clearaccess.net>
            <39049BB8.B15D649B@ecal.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 24 Apr 2000 15:35:43 -0400
X-Loop: ietf@ietf.org

On Mon, 24 Apr 2000 15:08:40 EDT, John Stracke <francis@ecal.com>  said:
> No, it turns out that what they mean by UNL is an artificial human language, a
> common intermediary that any human text can be translated into; they postulate
> translation servers that know how to translate between UNL and specific human
> languages.  Much higher in the stack than IP.  :-)

Remember that the Babelfish, by allowing perfect communication, was the cause
of more and bloodier wars than anything else ever recorded... ;)

Douglas Adams was right...

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Mon Apr 24 16:21:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA13993
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 16:20:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13238
	for <ietf@ietf.org>; Mon, 24 Apr 2000 15:36:47 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA01885;
        Mon, 24 Apr 2000 15:36:06 -0400 (EDT)
Message-Id: <200004241936.PAA01885@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Anthony Atkielski" <anthony@atkielski.com>
cc: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-reply-to: Your message of "Mon, 24 Apr 2000 12:04:36 +0200."
             <002001bfadd4$80253fa0$0a00000a@wanadoo.fr> 
Date: Mon, 24 Apr 2000 15:36:06 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> What I find interesting throughout discussions that mention IPv6 as a
> solution for a shortage of addresses in IPv4 is that people see the
> problems with IPv4, but they don't realize that IPv6 will run into the
> same difficulties.  _Any_ addressing scheme that uses addresses of
> fixed length will run out of addresses after a finite period of time,

I suppose that's true - as long as addresses are consumed at a rate
faster than they are recycled.  But the fact that we will run out of
addresses eventually might not be terribly significant - the Sun will
also run out of hydrogen eventually, but in the meantime we still find
it useful.

> and that period may be orders of magnitude shorter than anyone might
> at first believe.

it is certainly true that without careful management IPv6 address
space could be consumed fairly quickly.  but to me it looks like that
with even moderate care IPv6 space can last for several tens of years.

> Consider IPv4.  Thirty-two bits allows more than four billion
> individual machines to be addressed.  

not really.  IP has always assumed that address space would be
delegated in power-of-two sized "chunks" - at first those chunks only
came in 3 sizes (2**8, 2**16, or 2**24 addresses), and later on it
became possible to delegate any power-of-two sized chunk.  but even
assuming ideally sized allocations, each of those chunks would on
average be only 50% utilized. 

so every level of delegation effectively uses 1 of those 32 bits, and
on average most parts of the net are probably delegated 4-5 levels
deep.  (IANA/regional registry/ISP/customer/internal). so we end up
effectively not with 2**32 addresses but with something like 2**27 or
2**28.  (approximately 134 million or 268 million)

(see also RFC 1715 for a different analysis, which when applied to
IPv4, yields similar results for the optimistic case)

allocating space in advance might indeed take away another few bits.
but given the current growth rate of the internet it is necessary.
the internet is growing so fast that a policy of always allocating
only the smallest possible chunk for a net would not only be
cumbersome, it would result in poor aggregation in routing tables and
quite possibly in worse overall utilization of address space.

but if it someday gets easier to renumber a subnet we might then find
it easier to garbage collect, and recycle, fragmented portions of
address space.  and if the growth rate slowed down (which for various
reasons is possible) then we could do advance allocation more
conservatively.

> It should be clear that IPv6 will have the same problem.  The space
> will be allocated in advance.  Over time, it will become obvious that
> the original allocation scheme is ill-adapted to changing requirements
> (because we simply cannot foresee those requirements).  Much, _much_
> sooner than anyone expects, IPv6 will start to run short of addresses,
> for the same reason that IPv4 is running short.  It seems impossible
> now, but I suppose that running out of space in IPv4 seemed impossible
> at one time, too.

IPv6 allocation will have some of the same properties of IPv4
allocation.  We're still using power-of-two sized blocks, we'll still
waste at least one bit of address space per level of delegation.  It
will probably be somewhat easier to renumber networks and recycle
address - how much easier remains to be seen.

OTOH, I don't see why IPv6 will necessarily have significantly more
levels of assignment delegation.  Even if it needs a few more levels,
6 or 7 bits out of 128 total is a lot worse than 4 or 5 bits out of 32.

> The allocation pattern is easy to foresee.  Initially, enormous
> subsets of the address space will be allocated carelessly and
> generously, because "there are so many addresses that we'll never run
> out" 

I don't know where you get that idea.  Quite the contrary, the
regional registries seem to share your concern that we will use up
IPv6 space too quickly and *all* of the comments I've heard about the
initial assignment policies were that they were too conservative.
IPv6 space does need to be carefully managed, but it can be doled out
somewhat more generously than IPv4 space.

> and because nobody will want to expend the effort to achieve
> finer granularity in the face of such apparent plenty.  

First of all, having too fine a granularity in allocation prevents you
from aggregating routes.  Second, with power-of-two sized allocations
there's a limit to how much granularity you can get - even if you
always allocate optimal sized blocks.

> This mistake will be repeated for each subset of the address space
> allocated, by each organization charged with allocating the space.

It's not clear that it's a mistake.  it's a tradeoff between having
aggregatable addresses and distributed assignment on one hand and
conserving address space on the other.  and the people doing address
assignment these days are quite accustomed to thinking in these terms.

> If you need further evidence, look at virtual memory address spaces.
> Even if a computer's architecture allows for a trillion bits of
> addressing space, it invariably becomes fragmented and exhausted in an
> amazingly short time.  

this is only amazing to those who haven't heard of Moore's law.
(presumably the same set of people who thought DES would never be broken)

on the other hand, it's not clear how valid this analogy is for
predicting the growth of the Internet - just because Moore's law (if
it keeps on working) might predict that in a decade we could
eventually have thousands of network-accessible computing devices for
everyone on the planet, doesn't mean that those people would be able
to deal with thousands of such devices.  and there do appear to be
limits to the number of human beings that the planet can support.  and
if by that time the robot population exceeds the human population then
I'm happy to let the robots solve the problem of upgrading to a new
version of IP.

and as for other planets, all kinds of assumptions about the current
Internet fail when you try to make it work at interplanetary
transmission latencies.  so if we do manage to significantly populate
other planets or if we find extraterrestrial species that we want to
network with, we'll have to build a new architecture.  and people are
already working on that.

> The only real solution to this is an open-ended addressing scheme--one
> to which digits can be added as required.  

variable length addresses do have some nice properties.  there are
also some drawbacks.

fwiw, phone numbers do in fact have a fixed maximum length which is
wired into devices all over the planet - not just in the phone system
but in numerous computer databases, etc..  it is not much easier to
increase the overall length of phone numbers than it is to make IP
addresses longer.  and once you set a fixed maximum length then it's
just a matter of representation - do you have a variable-length
address field or do you have a fixed-length field with zero padding?
fixed-length fields are a lot easier for routers to deal with.  (and
for similar reasons a lot of software uses fixed-length fields for
phone numbers)

128-bit IPv6 addresses are roughly equivalent to 40 digits, which IIRC
is a lot longer than the maximum size of a phone number under E.164.
(sorry, I don't have a copy handy to check)

and the means by which IPv6 addresses are being allocated is actually
not so different from the means in which phone numbers are allocated -
the major exception being that IPv6 prefixes are assigned to major
ISPs rather than to geographic regions.  (the latter difference might
affect routing but probably does not affect allocation efficiency).

so I think the bottom line answer to your message is that your concers
are valid (if perhaps a bit exaggerated) and an allocation mechanism
similar to what you suggest is already in place.

Keith



From owner-ietf-outbound  Mon Apr 24 16:30:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA14190
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 16:30:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13346
	for <ietf@ietf.org>; Mon, 24 Apr 2000 15:43:45 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA01931;
        Mon, 24 Apr 2000 15:43:04 -0400 (EDT)
Message-Id: <200004241943.PAA01931@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Daniel Senie <dts@senie.com>
cc: Ian King <iking@microsoft.com>,
        "'Anthony Atkielski'" <anthony@atkielski.com>, ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-reply-to: Your message of "Mon, 24 Apr 2000 12:48:27 EDT."
             <39047ADB.84B3F256@senie.com> 
Date: Mon, 24 Apr 2000 15:43:04 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Users shouldn't care or know about the network's internal addressing.
> Some of the application issues with NATs spring directly from this issue
> (e.g. user of X-terminal setting display based on IP address instead of
> DNS name).

it's not the same issue.  the point of using IP addresses in DISPLAY 
variables is not to make them visible to the user - it's because 
using the IP address is (in a non-NATted network) far more reliable 
than depending on the DNS lookup to work.  the fact that doing this
makes the address more visible to the user is just a side effect;
most users don't care diddly about it one way or the other as long
as it works.

Keith



From owner-ietf-outbound  Mon Apr 24 16:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA14478
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 16:40:02 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13536
	for <ietf@ietf.org>; Mon, 24 Apr 2000 15:57:17 -0400 (EDT)
Received: from contactdish (ASt-Lambert-101-2-165.abo.wanadoo.fr [193.251.59.165]) by atkielski.com (8.8.8) id VAA21928; Mon, 24 Apr 2000 21:57:10 +0200 (CEST)
Message-ID: <00c401bfae27$477809f0$0a00000a@wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
Subject: Fw: IPv6: Past mistakes repeated?
Date: Mon, 24 Apr 2000 21:57:10 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> If what you suggest should be implemented, then
> probably the entire software of all the switches
> and hubs need to be upgraded (if not entirely scrapped) .

That's what has to be done, anyway.  I'm not sure that I see what you are
saying.

> As also everytime the source and destination addresses are
> upgraded, all the systems and the related software needs to
> be upgraded.

If you design it correctly in the first place, this isn't necessary.

Think of a railroad network as an analogy.  The current design for IP
addressing allows a fixed number of tracks, and you have to allocate them
all in advance.  If the future evolution of the network is such that your
allocation turns out to be less than optimal, you have to redo entire
sections of the network to reallocate tracks.

Now compare this with an open-ended addressing scheme.  All you have to do
in this case is allocate the first track.  As additional tracks are needed,
you build new ones, branching off from the first track.  If some branches
evolve more than others, no problem--they can just add additional branches
of their own.  No branch impinges on any other branch.  You might have only
two branches leading away from your original track.  One of them might lead
to a total of fifty stations (endpoints), but the other might lead to ten
trillion stations.  It doesn't matter, and you don't have to care, since
when you route trains on your section of the network, all you'll look at is
the first digit of the destination, which will tell you which of your two
branches the train must follow.
And you might be on a branch yourself, for that matter.  The network can be
restructured upstream or downstream of your little section of track, and it
remains transparent to you, as long as the digit designations for you and
the two branches you serve remain the same.

> Personally my telephone number has changed
> 3 times within the last couple of years.

Probably because the telephone numbering scheme was not truly open-ended.
In the U.S., for example, attempts to fix the number of digits in telephone
numbers have caused great problems, with things like area codes being
exhausted, exchanges being exhausted, and so on.  A truly open-ended scheme
wouldn't have this problem--you'd just add more digits in the areas that
needed more numbers.  This open-ended scheme is actually in place for
international calling.  (Equipment usually has fixed-length buffers for
telephone numbers, but all you have to do is boost the size of the buffers
if you ever come across numbers that won't fit.)

> But the million dollar question is that whether the
> protocol and switch vendors would like to scrap the
> years and amount of investment that they have already
> made in the existing system.

Looks like they're pretty much doing that with IPv6 now!  And with a
fixed-length addres, they'll be doing it again in 15 years, only it will
cost a thousand times more than it did on this pass.

  -- Anthony




From owner-ietf-outbound  Mon Apr 24 16:50:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA14658
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 16:50:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13543
	for <ietf@ietf.org>; Mon, 24 Apr 2000 15:57:47 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA02002;
        Mon, 24 Apr 2000 15:57:16 -0400 (EDT)
Message-Id: <200004241957.PAA02002@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Sean Doran <smd@ebone.net>
cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Mon, 24 Apr 2000 21:35:51 +0200."
             <200004241935.VAA04803@sean.ebone.net> 
Date: Mon, 24 Apr 2000 15:57:16 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> | it's not at all clear to me why households need traditional multihoming,
> | nor how to make it feasible for households to have it.  so I would regard
> | this as overdesign of the home 'internet interface box'
> 
> Three observations:
> 
> 	1. 
> 
> 	In the past, when and if large arrogant backbone providers like
> 	me used to say that a push against multihoming was a good way
> 	to avoid stressing the current routing system by avoiding
> 	address deaggregation and globally-visible reachable changes
> 	that could result, we would get flayed alive.

that's because (it appeared) you were trying to do this by fiat rather 
than simply passing along the costs associated with doing so.
(I can see it now: if you multihome, you pay a charge for every time
one of your links changes state...)

> 	The lesson: always assume that, no matter how technically odd
> 	one thinks it may be, everyone will want to multihome if it is
> 	feasible to do so.

sure, if they can do it for free.  but multihoming has costs.
somebody has to pay for it.  given that most folks probably don't
need it, it makes sense to let those who need it pay the extra cost.

> 	2.
> 
> 	Multihomed entities like to submit bandwidth increase orders
> 	to one or the other provider over time, depending on a
> 	number of factors.   Likewise, singlehomed entities appear
> 	to want to multihome, and at some point rather than upgrade
> 	the single connection to the Internet, will order a second
> 	connection from a different provider, and attempt to do
> 	traditional multihoming.

yep.  I don't see the problem as long as they're willing to pay the
ISPs for the routing.

> 	3.
> 
> 	In many areas nearly every household PRESENTLY has several
> 	possible fixed, wireless and switched facilities over which
> 	Internet access can be offered.

sure.  but how likely is it that most folks will want to pay for more
than one connection (when one will do), much less having them multihomed?

why would they need that?  most ISPs aren't *that* unreliable.

> I would say that rather than being overdesigned, that it is slightly
> underdesigned, because it does not address the possibility of multitenanted
> households, with (for example) his&hers routing policies.  (For example,
> he uses a cable provider for access, she has a DSL paid for her by her job
> so she can do her engineering activities from home).

folks will work out these things just like they work out ways of paying
for trips that are part business and part personal.  I'm not convinced 
that multihoming is even a distantly likely solution to such a scenario.
  
> | and given the degree of harm that NATs have done to IPv4, I hope they
> | never rear their ugly heads in IPv6.
> 
> Noel's right, your knees must really hurt!

not as much as my applications do.

> | what's the point of traditional multihoming anyway if you have to
> | have NATs?  you might as well do IPv6-style multihoming - assign a 
> | separate address prefix to every incoming connection and let the
> | hosts sort it out.  you don't need NATs to do this.
> 
> The NAT function here is subsumed into the host.

no, it's not as bad as a NAT because hosts and applications
can be aware of the multiple addresses if they need to be.
(and those that don't need to be aware don't have to deal with it)

> Pushing NATs into hosts is an attractive idea, but it does
> require alot more knowledge of the network in the hosts, and
> one can gain no economies of scale that a standalone NAT shared
> by many hosts can achieve.  

I don't see the economies of scale; all I see is the inability of
such a network to efficiently support certain kinds of applications.

> | NATs can be a transition tool for connecting between IPv4 and IPv6, 
> | but NATs should never get in the way of a native IPv6 connection.
> 
> They will, though.

I'm sure somebody will do it here or there.  But by the time IPv6
gets widely deployed the problems with NATs will be widely understood,
and people will know better than to put them in their network unless
it's being set up for a very specific purpose for which NATs don't
cause a problem.

Keith



From owner-ietf-outbound  Mon Apr 24 17:00:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA14864
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 17:00:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13948
	for <ietf@ietf.org>; Mon, 24 Apr 2000 16:18:14 -0400 (EDT)
Received: from contactdish (ASt-Lambert-101-2-165.abo.wanadoo.fr [193.251.59.165]) by atkielski.com (8.8.8) id WAA25104; Mon, 24 Apr 2000 22:18:12 +0200 (CEST)
Message-ID: <00cb01bfae2a$381baae0$0a00000a@wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <20000424131939.7281335DC2@smb.research.att.com>
Subject: Re: IPv6: Past mistakes repeated? 
Date: Mon, 24 Apr 2000 22:18:09 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> But the first thing to remember is that there are
> tradeoffs.  Yes, infinitely long addresses are nice,
> but they're much harder to store in programs (you
> can no longer use a simple fixed-size structure for
> any tuple that includes an address) ...

Sure you can.  You just allocated the fixed space generously, _and_ you
include code that traps any address with more bytes than you can handle.  If
that ever happens, you rebuild your table with a larger fixed space.  You
might include code to catch addresses that approach the limit so that you
have time to rebuild the table at your leisure, rather than when the routing
actually fails, of course.

> ... and (more importantly) route, since the router
> has to use the entire address in making its decision.

Why does it need the entire address?

You only need the entire address if addresses are assigned arbitrarily from
the address space, such that no subset of the complete address is in itself
sufficient to complete any portion of the routing.  That is indeed a problem
today, with address allocation that does not necessarily strictly following
routing requirements.  But that was imposed by the very fact of trying to
allocate a fixed space in advance.  In a variable-length address space, you
don't have to anticipate any kind of advance allocation--you can just add
digits to addresses where they are required, and routers only need to look
at enough of an address to figure out where it should go next.  In a
variable-length scheme, you can be sure that any address that begins with
19283 always goes down the route you have for 19283, no matter what the
remaining digits are.  (Naturally, you could route with finer granularity at
some nodes, if you wanted to, but you wouldn't necessarily be obligated to
do that.)

> Furthermore, if it's a variable-length address, the
> router has to know where the end is, in order to look
> at the next field.

Just put that up front.  For example, prefix the address with a length byte.
If the byte is zero, the address is four bytes long (compatible with IPv4).
If it is one, the address is five bytes long.  And so on, up to 254+4= 258
bytes long.  If the byte is 255, however (unlikely, but this scheme would
provide for _any_ address length), then the _next_ byte specifies additional
bytes to be added to 254 (i.e., lengths of 254 through 508 bytes).  This
second byte follows the same pattern, and so on.  You'll never run out of
addresses this way, ever.

It's not really hard.  You just have to write the code up front to handle
it.  And if you don't want to allow for infinite capacity (you have to stop
somewhere, in any practical implementation), you just make darn sure that
you have code that will trap any address longer than you can handle.  If
anything ever hits the trap, you change some parameters and recompile, and
you're back online.

> Even if the destination address comes first, routers have
> to look at the source address because of ACLs -- though
> you don't want address-based security (and you shouldn't
> want it), you still need anti-spoofing filters.

Hmm... I don't know.  If you restrict the address field to routing only, do
you still need anti-spoofing?  A given address can lead to only one
endpoint, unless I'm missing something here.

> One reason is something that was pointed out by a number
> of people:  code that isn't exercised generally doesn't
> work well.  If we didn't have really long addresses in
> use from the beginning, some major implementations wouldn't
> support them properly.

It's a lot easier to fix a bug than to rewrite the protocol from scratch
when it runs out of capacity.

> There have been designs for [geographic addressing], I
> should add, such as the Metropolitan Area Exchanges.
> But for those to work, assorted ISPs would have
> to co-operate on a large scale, something that I
> don't think will happen.

Why would they have to cooperate in a variable-length scheme?  They would
only allocate addresses on their branch.  They could route within their
branch without knowing or caring about other branches (as long as they know
the high-order digits identifying their own branches, which someone else
would assign to them).  And if they ever saw addresses with high-order
digits that didn't match their own assigned digits, they'd know that the
address meant "elsewhere."  Of course, finer granularity would be possible,
but not required.

That's how telephones work.  If you call someone in Mongolia from the U.S.,
the U.S. exchanges don't have to know or care about the trailing digits in
the number; they only have to look at enough of the number to know to route
the call towards Mongolia.  Can you imagine what the telephone system would
be like if every country had to know every detail about the numbering system
of every other country?

> Phone numbers are allocated geographically, but that
> only works because historically, most areas only had
> one monopoly phone company.

That's not a requirement.  Just assign additional companies an additional
branch.   At most, the new companies would add one digit to the address.

> ... but telephone networks do one lookup per call, not
> one per packet.

I should think you'd be able to optimize this, especially since, with a
variable-length scheme, you only need to look as far as necessary to pick a
route.  If you have a route for 12847, you know that 12847xxxxxx is always
going to take that route.  Depending on how many outbound routes you have,
this could be very fast indeed.

  -- Anthony



From owner-ietf-outbound  Mon Apr 24 17:10:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15108
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 17:10:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14046
	for <ietf@ietf.org>; Mon, 24 Apr 2000 16:22:01 -0400 (EDT)
Received: from contactdish (ASt-Lambert-101-2-165.abo.wanadoo.fr [193.251.59.165]) by atkielski.com (8.8.8) id WAA25479; Mon, 24 Apr 2000 22:22:00 +0200 (CEST)
Message-ID: <00d201bfae2a$bf691e60$0a00000a@wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <2917.956591011@cs.ucl.ac.uk>
Subject: Re: IPv6: Past mistakes repeated?
Date: Mon, 24 Apr 2000 22:21:59 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> its ironic you should send this today, when 12
> million people in london, england, had to learn
> to dial 8 digits instead of 7 because of lack
> of foresight from the telephone regualtor when
> re-numbering less than a decade ago ...

France has increased the number of digits in telephone numbers several times
over the past 20 years, and it has always been without a hitch.  Each time
the telco has prepared for a barrage of misdials, just in case, but they
have never materialized.  Currently, numbers are ten digits long, everywhere
in the country, although the first digit is actually a selector for your
chosen local telco provider (0 = France Telecom, the historical operator).

  -- Anthony



From owner-ietf-outbound  Mon Apr 24 17:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15342
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 17:20:03 -0400 (EDT)
Received: from apollo.dmnews.com (mail.dmnews.com [204.141.161.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14089
	for <ietf@ietf.org>; Mon, 24 Apr 2000 16:22:47 -0400 (EDT)
Received: by mail.dmnews.com with Internet Mail Service (5.5.2448.0)
	id <HNLHMGXK>; Mon, 24 Apr 2000 16:28:59 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE03D885@mail.dmnews.com>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'John Stracke'" <francis@ecal.com>
Cc: ietf@ietf.org
Subject: RE: Universal Network Language
Date: Mon, 24 Apr 2000 16:28:59 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="windows-1252"
X-Loop: ietf@ietf.org

I totally agree with you - at least there should be a choice either user or
content induced - to translate or not to translate. Also one must think of
the possibility of how much the translation service or program will become
another point of failure - or even a security issue.

Lillian Komlossy                     
Site Manager                         
http://www.dmnews.com           
http://www.imarketingnews.com  
(212) 925-7300 ext. 232 


-----Original Message-----
From: John Stracke [mailto:francis@ecal.com]
Sent: Monday, April 24, 2000 4:18 PM
To: Lillian Komlossy
Subject: Re: Universal Network Language


Lillian Komlossy wrote:

> It would make sense if it sat in front of the applications such as the
> browsers and did the translation - or the applications interfaced with it
-
> but either way it will be another monkie to slow down the entire process.
I
> don't know if it is worth the effort.

I suspect it will be if, and only if, the actual translation works.  If it
does, then someone will come up with a way to make it more efficient.  At
the
moment, it looks like they're putting the translation services onto servers
because they think that's the only way to get them deployed; and probably
they're right.

I'm skeptical about the translation, though; machine translation has a long
way
to go, and forcing it to run through a synthetic language will probably
hinder
more than it hurts.  (Think about what happens when you want to translate
from,
say, English to German, and the concept you're translating can be expressed
concisely in both languages, but not in UNL.)

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |That is correct. I'm out of fuel. My landing |
|francis@ecal.com|gear is jammed. And there's an unhappy bald  |
|                |eagle loose in the cockpit.                  |
\==============================================================/




From owner-ietf-outbound  Mon Apr 24 17:30:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15511
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 17:30:04 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14152
	for <ietf@ietf.org>; Mon, 24 Apr 2000 16:28:41 -0400 (EDT)
Received: from contactdish (ASt-Lambert-101-2-165.abo.wanadoo.fr [193.251.59.165]) by atkielski.com (8.8.8) id VAA20607; Mon, 24 Apr 2000 21:45:43 +0200 (CEST)
Message-ID: <00b601bfae25$ae270900$0a00000a@wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <BB2831D3689AD211B14C00104B14623B1E7569@HAZEN04>
Subject: Re: IPv6: Past mistakes repeated?
Date: Mon, 24 Apr 2000 21:45:43 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> I agree! Why create a finite anything when an infinite
> possibility exists?

Exactly.  If you designed an open-ended protocol, you're far less likely to
ever have to rewrite it.

> On another note, I have heard the argument that
> a unique identifier already exists in the form of
> a MAC address why not make further use of it?

Not every machine on the Internet has an Ethernet card with a MAC address,
otherwise it might not be such a bad idea.  I think using the MAC address is
an excellent idea for software protection schemes (it's a lot more elegant
than a hardware key such as a dongle), but nobody seems interested in that.
In any case, this latter application is outside the scope of Internet
discussions.

  -- Anthony



From owner-ietf-outbound  Mon Apr 24 17:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15732
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 17:40:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14213
	for <ietf@ietf.org>; Mon, 24 Apr 2000 16:30:30 -0400 (EDT)
Received: from contactdish (ASt-Lambert-101-2-165.abo.wanadoo.fr [193.251.59.165]) by atkielski.com (8.8.8) id WAA26410; Mon, 24 Apr 2000 22:30:28 +0200 (CEST)
Message-ID: <00db01bfae2b$eec52ef0$0a00000a@wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <D5922CA42F8CD31189D800805F19A16C04B7B16B@RED-MSG-48>
Subject: Re: IPv6: Past mistakes repeated?
Date: Mon, 24 Apr 2000 22:30:19 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> The telephone number situation in the United States
> has been one of continual crisis for years, because
> of rapid growth in use (in part because of Internet
> access!).  The area served by a given "area code" would
> be split into smaller areas with multiple area codes;
> these days, those areas aren't necessarily even contiguous.

That is mostly because the telco(s) tried to impose a fixed address length
on a scheme that really should have remained variable.  Telephone numbers
overseas are truly variable.  When you dial 011+3, the remaining digits can
be anywhere from one to a thousand.  The local end just stores them all
until you say you are done (by pausing or hitting the # key), and then it
routes it as far as it can, and passes the rest onto some other node.

> I'd suggest that address assignment policy should
> keep process lightweight, so that it is realistic for
> businesses to regularly ask for assignments in more
> granular chunks ...

But if you use a truly variable scheme, you don't have to assign anything at
all.

Say Company X wants some addresses, and it is in an area where all addresses
start with 9482.  You just add some digits, tell them what they are, and
they can add as many addresses as they want behind those digits.  All you
have to care about is that 94825xxxxx gets routed to Company X.  The rest of
the address allocation is their business.  They might have just two digits
on the end, or they might have forty.

With fixed-length addresses, you're in trouble as soon as you make an
assignment.  You might assign 94820000 through 94829999 to Company X.  The
problem is that, if Company X needs only 200 addresses, you've wasted 9800
addresses, and you can't give them to anyone else.  Conversely, if Company X
ever needs more than 10000 addresses, you have to completely reallocate
everything, or fragment their address range.  Either way, you lose.

> ... big users would be willing to request another 256
> when the new branch office opens, then another 64 for
> the summer interns...

All well and good, except that it fragments the address space, making it
impossible to route on just a portion of the address--you have to start
looking at the entire address, all the time.

  -- Anthony



From owner-ietf-outbound  Mon Apr 24 17:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15859
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 17:50:02 -0400 (EDT)
Received: from tsx-prime.MIT.EDU (TSX-PRIME.MIT.EDU [18.86.0.76])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA14300
	for <ietf@ietf.org>; Mon, 24 Apr 2000 16:31:30 -0400 (EDT)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id QAA28413; Mon, 24 Apr 2000 16:31:11 -0400
Date: Mon, 24 Apr 2000 16:31:11 -0400
Message-Id: <200004242031.QAA28413@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: John Stracke <francis@ecal.com>
CC: ietf@ietf.org
In-reply-to: John Stracke's message of Mon, 24 Apr 2000 15:06:21 -0400,
	<39049B2D.5E22F76@ecal.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   Date: Mon, 24 Apr 2000 15:06:21 -0400
   From: John Stracke <francis@ecal.com>

   > it's not at all clear to me why households need traditional multihoming,
   > nor how to make it feasible for households to have it.  so I would regard
   > this as overdesign of the home 'internet interface box'

   Now that I've got a decent DSL provider, I've found that the least
   reliable component of my Net access is the power line: my DSL just
   works, but the power company has been flaking out 2-3 times a week
   for the past month or so.  (I have my computers on UPSes, but your
   average K-Mart Box user wouldn't.)  Multihoming wouldn't solve that.

It depends on your ISP.  In the worst case some consumer grade DSL lines
are pretty bad --- 2-3 hour outages in the middle of the day (after all
no one uses the Internet during the day --- they're at work! :-),
sometimes every 3-4 days.  (I don't use this provider any more; clearly
they're using all of their money to take out full-page and half-page ads
in the Boston Globe's, and they're not spending it on upgrading their
network operations.  :-)

To make matters worse, there's a huge price differential between
"consumer grade" ISP's and "business grade" ISP's.  This kind of
situation is just ripe for arbitradge.  :-)

I can imagine some poor (but demanding) network geeks deciding that
they'll solve this problem by purchasing multiple cheap consumer grade
ISP's (say a cable modem and a ADSL line), and then set up tunnels to
some place where they can get address space.  If you can assume that
only one of your consomer grade pipes will crap out at a time, they can
switch the tunnel endpoint to the other grade of service, and keep
working with the same IP addresses, even though one of their lines has
stopped working.  (This is also useful because the cheap consumer grade
ISP's generally won't give you a large address block, even without the
dual redundancy --- and two cheap consumer grade network services is
probably far cheaper than a single business grade ISP monthly fee.)

Right now, getting address space via tunnelling usually requires knowing
someone with connections at some institution with a fast connection to
the internet and a large amount of available address space.  But I
suspect there may be a huge business opportunity here, especially if the
the some price differential between various grades of service continues.

						- Ted



From owner-ietf-outbound  Mon Apr 24 18:00:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA16004
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 18:00:03 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14966
	for <ietf@ietf.org>; Mon, 24 Apr 2000 17:01:19 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id RAA08837
	for <ietf@ietf.org>; Mon, 24 Apr 2000 17:00:24 -0400
Sender: francis@localhost.localdomain
Message-ID: <3904B5E8.1C3991D6@ecal.com>
Date: Mon, 24 Apr 2000 17:00:24 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
References: <200004241936.PAA01885@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Keith Moore wrote:

> if by that time the robot population exceeds the human population then
> I'm happy to let the robots solve the problem of upgrading to a new
> version of IP.

Ah--the Iron Man's Burden.  :-)

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |Beware of wizards, for you are crunchy and good|
|francis@ecal.com|with ketchup.                                  |
\================================================================/





From owner-ietf-outbound  Mon Apr 24 18:10:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA16242
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 18:10:03 -0400 (EDT)
Received: from saint.heaven.net (saint.heaven.net [198.69.28.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15383
	for <ietf@ietf.org>; Mon, 24 Apr 2000 17:20:58 -0400 (EDT)
Received: (from stpeters@localhost)
	by saint.heaven.net (8.9.3/8.9.3) id RAA04039;
	Mon, 24 Apr 2000 17:20:49 -0400
From: "Dick St.Peters" <stpeters@NetHeaven.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14596.47793.75293.482566@saint.heaven.net>
Date: Mon, 24 Apr 2000 17:20:49 -0400 (EDT)
To: ietf@ietf.org
Subject: RE: IPv6: Past mistakes repeated?
In-Reply-To: <200004241921.PAA07009@ginger.lcs.mit.edu>
References: <200004241921.PAA07009@ginger.lcs.mit.edu>
X-Mailer: VM 6.72 under Emacs 19.34.1
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>     > making each house a TLA does not strike me as a scalable multihoming
>     > solution for very large numbers of houses, given the current state of
>     > the routing art.
> 
> The restriction has little to do with the current state of the routing art
> (which is not to say that better path-selection architectures than the one
> the Internet is currently using do not exist :-).
> 
> Even with the best routing system, it still couldn't support tracking large
> numbers of houses as individual destinations (i.e. having individual routing
> tables extries across the global scope) - even if the routers had large
> enough route table memories to hold the 100's of millions of routes which
> could result.

I should probably just go back to lurking, but ... my take on every
house being multihomed was to imagine full local meshing - each house
peering with its neighbors redundantly.  If, say, my power-line port
was down, that information needn't be known by anything outside my own
neighborhood.  When the local power distribution center couldn't get a
power-grid packet to me directly, they'd give it to my neighbor and
let his smart house determine whether to send it to mine by wireless
or cable or whatever else has come along.  The rest of the world could
just engage in some kind of "get it closer" routing.

Don't ask me about mobile users.  I'm going back to lurking ...

--
Dick St.Peters, stpeters@NetHeaven.com 
Gatekeeper, NetHeaven, Saratoga Springs, NY
Saratoga/Albany/Amsterdam/BoltonLanding/Cobleskill/Greenwich/
GlensFalls/LakePlacid/NorthCreek/Plattsburgh/...
    Oldest Internet service based in the Adirondack-Albany region



From owner-ietf-outbound  Mon Apr 24 18:20:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA16399
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 18:20:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15453
	for <ietf@ietf.org>; Mon, 24 Apr 2000 17:26:03 -0400 (EDT)
Received: from contactdish (ASt-Lambert-101-2-165.abo.wanadoo.fr [193.251.59.165]) by atkielski.com (8.8.8) id XAA32977; Mon, 24 Apr 2000 23:26:02 +0200 (CEST)
Message-ID: <010a01bfae33$b1518ca0$0a00000a@wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <200004241936.PAA01885@astro.cs.utk.edu>
Subject: Re: IPv6: Past mistakes repeated? 
Date: Mon, 24 Apr 2000 23:26:01 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

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


> I suppose that's true - as long as addresses are consumed
> at a rate faster than they are recycled.  But the fact that
> we will run out of addresses eventually might not be terribly
> significant - the Sun will also run out of hydrogen
> eventually, but in the meantime we still find it useful.

Ah ... famous last words.  I feel confident that similar words were said
when the original 32-bit address scheme was developed:

"Four billion addresses ... that's more than one computer for every person
on Earth!"

"Only a few companies are every going to have more than a few computers ...
just give a Class A to anyone who asks."

And so now we are running out.

But the real thing here is, even with the wisest allocations imaginable, we
would still run out much, much faster than the total number of addresses in
the address space might lead one to believe.  And that is because we have to
_predict_ how addresses will be used, and we cannot easily change the
consequences of those predictions.  So there are always significant blocks
of unused addresses, even as we run out of addresses in other ways.

> it is certainly true that without careful management
> IPv6 address space could be consumed fairly quickly.
> but to me it looks like that with even moderate care IPv6
> space can last for several tens of years.

Ten years, I'd say.  And then redefining a new addressing scheme will cost a
thousand times more than it will today, at least.  Even washing machines
will have to get new programming!

> not really.  IP has always assumed that address space
> would be delegated in power-of-two sized "chunks" ...

Aye, there's the rub.  It has always been necessary to _assume_ and
_delegate_ address space, because the address space is finite in size.  It
has always been necessary to predict the future, in other words, in a domain
where the future is very uncertain indeed.

> ... at first those chunks only came in 3 sizes (2**8,
> 2**16, or 2**24 addresses), and later on it became possible
> to delegate any power-of-two sized chunk.

But by then, a lot of the biggest chunks were already in use.

> ... but even assuming ideally sized allocations, each
> of those chunks would on average be only 50% utilized.

Right.  So the only solution is to get rid of the need to allocate in
advance in the first place.

Think of variable addressing and the needs of the tiny country of Vulgaria.
Vulgaria needs address space.  Okay, so you say, well, Vulgaria is in, say,
Eastern Europe, and all addresses in Eastern Europe begin with 473.  All the
addresses from 4731 to 4738 are taken.  So you add address 4739, which now
means "everyone else in Eastern Europe," and you assign 47391 to Vulgaria.
That's all you have to do.  If Vulgaria wants to further subdivide, it can;
it can assign 473911 to Northern Vulgaria, and 473912 to the rugged
Vulgarian Alps region.  It doesn't matter to anyone except Vulgaria.

Given this, North America doesn't have to change anything at all.  Before,
anything that started with 473 went to Eastern Europe, and that's still the
case.  Some European routers have to smarten up a bit, because now they have
to be aware that 4739 goes to another routing point that handles "all other"
Eastern European countries.  And this new routing point (heck, maybe
Vulgaria will host it, eh?) must know that 47391 goes to Vulgaria, but
nothing more.  Only routers in Vulgaria itself need to care where 473911
goes as compared to 473912.  And only routers in the rugged Vulgarian Alps
need to know that 4739124 goes to Smallville, and 4739126 goes to
Metropolis, both cities nestled there in the Alps.  And since the addressing
scheme is open ended, even if Vulgaria one day has ten trillion computers on
the Net, nothing outside Vulgaria needs to change.

> allocating space in advance might indeed take away
> another few bits. but given the current growth rate
> of the internet it is necessary.

Only with a fixed address space.

> the internet is growing so fast that a policy of
> always allocating only the smallest possible chunk
> for a net would not only be cumbersome, it would result
> in poor aggregation in routing tables and quite
> possibly in worse overall utilization of address space.

Exactly ... but that's the magic of the variable address scheme.  You only
have to allocate disparate chunks in a fixed address scheme because the size
of each chunk is limited by the length of an address field.  But if the
address field is variable, you can make any chunk as big as you want.  If
you have addresses of 4739124xx initially (Metropolis only had a few
machines at first), and you run out of addresses after 473912498, you just
make 473912499 point to "more addresses for Metropolis," and start
allocating, say 4739124990001 through 4739124999998 (you always leave at
least one slot empty so that it can point to "more addresses").

> I don't know where you get that idea.

That's how it happened for IPv4.

> Quite the contrary, the regional registries seem to
> share your concern that we will use up IPv6 space too
> quickly and *all* of the comments I've heard about the
> initial assignment policies were that they were too
> conservative.

No matter how conservative they are, the finite length of the address field
will eventually cause problems, and much sooner than anyone thinks.

> IPv6 space does need to be carefully managed, but it
> can be doled out somewhat more generously than IPv4 space.

And in 2030:

"Of course, nobody in 2000 realized that we'd eventually need 1048576
listener addresses for each of our cellphones and wristwatches, even if that
is obvious now.  As a result, we've nearly exhausted the IPv6 space, and we
are looking at a new scheme.  We think that a new fixed address space of 192
bits will surely be all anyone will ever need before the sun turns cold, and
we'll never have this problem again."

> First of all, having too fine a granularity in allocation
> prevents you from aggregating routes.

Only with a fixed address length.

Look at it this way:  Think of fixed-length addresses as rays streaming out
from the center of a circle.  You allocate rays so that they are adjacent to
facilitate routing.  However, no matter what you do, the time will come when
you just cannot allocate the number of adjacent rays that you require for
some purpose, and at that point, your routing system breaks, or you deny
someone an allocation.

Now think of variable-length addresses as rays also--but in this case, you
have the option of splitting any ray to create more rays.  Now you can
allocate adjacent rays as required, and if you run out of rays, you split a
few to make more, and they are still adjacent.  You can split them as many
times as you want.

Or you can look at it as numbers.  Fixed-length addresses are integers.
Variable-length addresses are real numbers.  You can only have so many
integers between 1 and 100, but you can have an infinite number of real
numbers between those two limits--you just keep adding decimal places.

> It's not clear that it's a mistake.  it's a tradeoff
> between having aggregatable addresses and distributed
> assignment on one hand and conserving address space
> on the other.

It's a mistake in that it is imposed by a finite address space.  Eliminate
the finite address space, and this is no longer an issue.  You don't have to
care about aggregating addresses--you just create more, if you need them.

Surely you've seen this in technical manuals: If you need to put something
between section 1 and section 2, you just add a section 1.5.  That's
variable addressing.  But if you limit yourself to fixed addressing, your
only choice is to move every section in the manual so that you can put in a
different section 2 (making the old section 2 section 3, and the old section
3 section 4, and so on).

> this is only amazing to those who haven't heard of
> Moore's law.

Moore's law isn't the cause of the problem.  The problem isn't created by
advances in hardware or software or network capacity; it is created by the
inevitable impossibility of knowing the future with certainty.  You cannot
know what a network will look like in the infinite future, so there is no
way to optimally allocate addresses in a fixed address space without
eventually being required to do everything over again.

> fwiw, phone numbers do in fact have a fixed maximum
> length which is wired into devices all over the planet ...

Yes, but it's way easier to make a field larger than it is to build and
implement a new protocol.  And if you design for variable length, you can
trap anything that exceeds your buffer space and fix it when the time comes
(or before the time comes, if you check ahead).  If you don't design for
variable length, you just rewrite everything.

> ... it is not much easier to increase the overall
> length of phone numbers than it is to make IP
> addresses longer.

But in a variable-length system, you can make both ends variable.  You can
thus add length at either end without affecting more than a tiny part of the
network (the part that has to know about the portions of the address that
you've extended).  Routers that look only at the parts that haven't changed
(in the middle) don't require any modifications.

  -- Anthony



From owner-ietf-outbound  Mon Apr 24 18:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA16538
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 18:30:03 -0400 (EDT)
Received: from leo.eg.bucknell.edu (dns.dhcp.org [134.82.56.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15961
	for <ietf@ietf.org>; Mon, 24 Apr 2000 17:55:26 -0400 (EDT)
Received: from droms-mac (pm3mi3-1.uplink.net [209.173.86.98])
	by leo.eg.bucknell.edu (8.8.8+Sun/8.8.8) with ESMTP id RAA18057;
	Mon, 24 Apr 2000 17:55:22 -0400 (EDT)
Message-Id: <4.2.2.20000424175302.00a46db0@mail.bucknell.edu>
X-Sender: droms@mail.bucknell.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Mon, 24 Apr 2000 17:55:06 -0400
To: "Anthony Atkielski" <anthony@atkielski.com>, <ietf@ietf.org>
From: Ralph Droms <droms@bucknell.edu>
Subject: Re: IPv6: Past mistakes repeated?
In-Reply-To: <00b601bfae25$ae270900$0a00000a@wanadoo.fr>
References: <BB2831D3689AD211B14C00104B14623B1E7569@HAZEN04>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 09:45 PM 4/24/00 +0200, Anthony Atkielski wrote:
> > I agree! Why create a finite anything when an infinite
> > possibility exists?
>
>Exactly.  If you designed an open-ended protocol, you're far less likely to
>ever have to rewrite it.

You just have to redeploy new implementations when you add new 
features.  "Open-ended" isn't helping us in extending DHCP.  That's not to 
say a practical, extensible, open-ended protocol can't be written...

- Ralph




From owner-ietf-outbound  Mon Apr 24 18:40:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA16759
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 18:40:02 -0400 (EDT)
Received: from watsun.cc.columbia.edu (IDENT:cu51491@watsun.cc.columbia.edu [128.59.39.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16034
	for <ietf@ietf.org>; Mon, 24 Apr 2000 18:00:30 -0400 (EDT)
Received: (from jaltman@localhost)
	by watsun.cc.columbia.edu (8.8.5/8.8.5) id SAA29857;
	Mon, 24 Apr 2000 18:00:11 -0400 (EDT)
Date: Mon, 24 Apr 2000 18:00:11 EDT
From: Jeffrey Altman <jaltman@columbia.edu>
Reply-To: jaltman@columbia.edu
To: Keith Moore <moore@cs.utk.edu>
Cc: Daniel Senie <dts@senie.com>, Ian King <iking@microsoft.com>,
        "'Anthony Atkielski'" <anthony@atkielski.com>, ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
In-Reply-To: Your message of Mon, 24 Apr 2000 15:43:04 -0400
Message-ID: <CMM.0.90.4.956613611.jaltman@watsun.cc.columbia.edu>
X-Loop: ietf@ietf.org

> > Users shouldn't care or know about the network's internal addressing.
> > Some of the application issues with NATs spring directly from this issue
> > (e.g. user of X-terminal setting display based on IP address instead of
> > DNS name).
> 
> it's not the same issue.  the point of using IP addresses in DISPLAY 
> variables is not to make them visible to the user - it's because 
> using the IP address is (in a non-NATted network) far more reliable 
> than depending on the DNS lookup to work.  the fact that doing this
> makes the address more visible to the user is just a side effect;
> most users don't care diddly about it one way or the other as long
> as it works.
> 
> Keith
> 

The default DISPLAY variable for an X Server on the local machine is

  unix:0

This means contact the 0th display attached to the 0th X Server on the
local machine.  When you make a connection to a remote machine you
cannot count on the return from gethostname() is going to have any
relationship to the name in the DNS.  Not to mention that on a
multi-homed machine you need to be able to choose the IP address that
is actually accessible to the remote.  So what you do is look at the
IP address on the local end of the socket that is being used to
connect to the remote system and insert that IP address into the
exported DISPLAY variable.  This has of course worked for 20 years and
fails when a NAT is in the middle.



    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org




From owner-ietf-outbound  Mon Apr 24 18:50:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA16903
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 18:50:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16202
	for <ietf@ietf.org>; Mon, 24 Apr 2000 18:09:03 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id SAA02550;
        Mon, 24 Apr 2000 18:08:34 -0400 (EDT)
Message-Id: <200004242208.SAA02550@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Keith Moore <moore@cs.utk.edu>
cc: "Anthony Atkielski" <anthony@atkielski.com>, ietf@ietf.org
Subject: correction Re: IPv6: Past mistakes repeated? 
In-reply-to: Your message of "Mon, 24 Apr 2000 15:36:06 EDT."
             <200004241936.PAA01885@astro.cs.utk.edu> 
Date: Mon, 24 Apr 2000 18:08:34 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

in an earlier message, I wrote:

> OTOH, I don't see why IPv6 will necessarily have significantly more
> levels of assignment delegation.  Even if it needs a few more levels,
> 6 or 7 bits out of 128 total is a lot worse than 4 or 5 bits out of 32.

the last sentence contains a thinko.  it should read:

6 or 7 bits out of 128 total is a lot better than 4 or 5 bits out of 32.

(I originally wrote the comparison in the other order, but when I swapped
sides, forgot to change the direction of the comparison.)

Keith



From owner-ietf-outbound  Mon Apr 24 19:00:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA17039
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 19:00:03 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16214
	for <ietf@ietf.org>; Mon, 24 Apr 2000 18:09:30 -0400 (EDT)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12jr2Y-0007g7-00; Mon, 24 Apr 2000 23:09:14 +0100
Date: Mon, 24 Apr 2000 23:09:11 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Anthony Atkielski <anthony@atkielski.com>
cc: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
In-Reply-To: <00db01bfae2b$eec52ef0$0a00000a@wanadoo.fr>
Message-ID: <Pine.GSO.4.21.0004242308220.20719-100000@petra.ee.surrey.ac.uk>
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-Loop: ietf@ietf.org

> The telephone number situation in the United States
> has been one of continual crisis for years

funny, I've always had the impression that the '555' area code was
infinite.

L.

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



From owner-ietf-outbound  Mon Apr 24 19:10:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA17256
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 19:10:03 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16642
	for <ietf@ietf.org>; Mon, 24 Apr 2000 18:34:32 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200004242232.HAA13164@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id HAA13164; Tue, 25 Apr 2000 07:32:34 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <200004241432.QAA04024@sean.ebone.net> from Sean Doran at "Apr 24,
 2000 04:32:38 pm"
To: Sean Doran <smd@ebone.net>
Date: Tue, 25 Apr 2000 07:32:33 +0859 ()
CC: iking@microsoft.com, moore@cs.utk.edu, ietf@ietf.org,
        stpeters@NetHeaven.com
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Sean;

> [Keith Moore on a "KMart box"]
> | take it home, plug it in to your phone line or whatever, and get
> | instant internet for all of the computers in your home.  
> | (almost just like NATs today except that you get static IP addresses).
> 
> No, not "or whatever" but "AND whatever".

Do you mean "plug THEM in to your phone line and whatever"?

> Otherwise this is a nice but insufficient device, 

Otherwise the device is unnecessarily complex (which means it is
more expensive and less reliable) and, worse, is the single point
of failure.

							Masataka Ohta



From owner-ietf-outbound  Mon Apr 24 19:20:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA17390
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 19:20:04 -0400 (EDT)
Received: from sean.ebone.net (IDENT:root@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16710
	for <ietf@ietf.org>; Mon, 24 Apr 2000 18:36:59 -0400 (EDT)
Received: (from smd@localhost)
	by sean.ebone.net (8.9.3/8.9.3) id AAA05263;
	Tue, 25 Apr 2000 00:36:59 +0200 (CEST)
Date: Tue, 25 Apr 2000 00:36:59 +0200 (CEST)
From: Sean Doran <smd@ebone.net>
Message-Id: <200004242236.AAA05263@sean.ebone.net>
To: ietf@ietf.org, stpeters@NetHeaven.com
Subject: RE: IPv6: Past mistakes repeated?
X-Loop: ietf@ietf.org

Dick St.Peters writes:

| I should probably just go back to lurking

No, these are fundamentally hard problems, and nobody has real answers.
What is interesting is that people haven't asked real questions either,
and yet have decided that the correct approach is IPv6.

| but ... my take on every
| house being multihomed was to imagine full local meshing - each house
| peering with its neighbors redundantly.

Well, this presupposes some infrastructure built especially for
that purpose, or some surprising business-to-consumer cordiality.
I can't imagine for example the cable people offering free (if
local) connectivity to everyone for this purpose -- there is the
issue of owning&operating copper/fibre/brouter gear.  Likewise,
I can't imagine ANY operator who would allow unconditional access
to local infrastructure, including people who do not pay bills,
or who do destructive things.

| If, say, my power-line port
| was down, that information needn't be known by anything outside my own
| neighborhood.

Well, no - there is the issue of how traffic from elsewhere
in the world arrives to your neighbours' houses on your behalf.

That is, whatever arrangements were in place for the 
mapping 
your.place.ny.us -> 1.2.3.4/32 -> sprint -> netheaven -> DSL-line -> your router
would have to be adjusted to now prefer 
your.place.ny.us -> ... -> access -> your neighbour -> something -> your router

The "..." piece is what's interesting.

If the DNS were less "sticky" your.place.ny.us could map to a new address 
that already was going as far as your neighbour.

If the routing system were really robust to microscopic changes,
the DNS could stay the same and the difference would be that now
traffic would be attracted not to netheaven but to your neighbour.
This implies that the traffic is not attracted to netheaven and
possibly therefore also not sprint, but rather c&w and then "access",
which would now know that 1.2.3.4/32 goes to your neighbour rather
than to c&w.

| When the local power distribution center couldn't get a
| power-grid packet to me directly, they'd give it to my neighbor 

What if your neighbour is not being supplied by the power people,
because he doesn't like the price-performance and doesn't want
to pay the power people's bills?

What if your neighbour simply doesn't like you?

Why use your neighbour for backup when there is cable tv coax
running into your household also?

How can you deal with a failure at a power company transformer,
that cuts off both you AND your neighbour(s)?

| and
| let his smart house determine whether to send it to mine by wireless
| or cable or whatever else has come along.  The rest of the world could
| just engage in some kind of "get it closer" routing.

Right - the problem is that the physical geography and the network
topology can be disjoint.  Your neighbour may be physically next door,
and it may be that logically he is directly connected to you when
your copper through the wall is working.  But when that copper fails,
you have to go to netheaven, netheaven's next hop is sprint, sprint's
next hop is c&w, c&w's next hop is "access", and access finally delivers
over the cable plant to your neighbour.

I see no practical means of making sure that EVERY household
shares a single common logical supplier of traffic.

| Don't ask me about mobile users.  I'm going back to lurking ...

Don't give up - there is a learning opportunity for all of us.

	Sean.



From owner-ietf-outbound  Mon Apr 24 19:30:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA17554
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 19:30:03 -0400 (EDT)
Received: from sean.ebone.net (IDENT:root@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16970
	for <ietf@ietf.org>; Mon, 24 Apr 2000 18:56:54 -0400 (EDT)
Received: (from smd@localhost)
	by sean.ebone.net (8.9.3/8.9.3) id AAA05322;
	Tue, 25 Apr 2000 00:56:52 +0200 (CEST)
Date: Tue, 25 Apr 2000 00:56:52 +0200 (CEST)
From: Sean Doran <smd@ebone.net>
Message-Id: <200004242256.AAA05322@sean.ebone.net>
To: mohta@necom830.hpcl.titech.ac.jp, smd@ebone.net
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

Ohta-san:

| > No, not "or whatever" but "AND whatever".
|
| Do you mean "plug THEM in to your phone line and whatever"?

Yes, that is certainly one possibility.   I imagine the "inside"
interface would be some easy-to-wire LAN interface, enabling THEM
to communicate using whatever protocol/address seems appropriate inside.

I wonder how to decide the trade-off between the additional hardware
complexity of a multi-outside-port box and the additional software
involved in sharing state across several single-outside-port boxes.

	Sean.



From owner-ietf-outbound  Mon Apr 24 19:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA17775
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 19:40:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17752
	for <ietf@ietf.org>; Mon, 24 Apr 2000 19:39:33 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id TAA03004;
        Mon, 24 Apr 2000 19:39:01 -0400 (EDT)
Message-Id: <200004242339.TAA03004@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Dick St.Peters" <stpeters@NetHeaven.com>
cc: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-reply-to: Your message of "Mon, 24 Apr 2000 17:20:49 EDT."
             <14596.47793.75293.482566@saint.heaven.net> 
Date: Mon, 24 Apr 2000 19:39:01 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

personally, I can't imagine peering with my neighbors.
but maybe that's just me ... or my neighborhood.

Keith



From owner-ietf-outbound  Mon Apr 24 20:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA18026
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 20:00:04 -0400 (EDT)
Received: from garlic.amaranth.net (garlic.amaranth.net [216.235.243.195])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17998
	for <ietf@ietf.org>; Mon, 24 Apr 2000 19:58:36 -0400 (EDT)
Received: from senie.com (garlic.amaranth.net [216.235.243.195])
	(authenticated)
	by garlic.amaranth.net (8.10.0/8.10.0) with ESMTP id e3ONwNN01301;
	Mon, 24 Apr 2000 19:58:23 -0400
Message-ID: <3904DF9B.7F698C2A@senie.com>
Date: Mon, 24 Apr 2000 19:58:19 -0400
From: Daniel Senie <dts@senie.com>
Organization: Amaranth Networks Inc.
X-Mailer: Mozilla 4.72 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Sean Doran <smd@ebone.net>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
References: <200004242256.AAA05322@sean.ebone.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Sean Doran wrote:
> 
> Ohta-san:
> 
> | > No, not "or whatever" but "AND whatever".
> |
> | Do you mean "plug THEM in to your phone line and whatever"?
> 
> Yes, that is certainly one possibility.   I imagine the "inside"
> interface would be some easy-to-wire LAN interface, enabling THEM
> to communicate using whatever protocol/address seems appropriate inside.
> 
> I wonder how to decide the trade-off between the additional hardware
> complexity of a multi-outside-port box and the additional software
> involved in sharing state across several single-outside-port boxes.

Given the propensity of different hardware interfaces to spring up for
each new service, I'd argue having multiple boxes interacting, while
more complex, is more realistic.

Example: today I can get a DSL modem or router, and I can get a cable
modem. But the technologies of those interfaces seems to keep changing.
To build one device with multiple interfaces would require (due to the
changing technologies) a place to plug in interface modules. This raises
the cost of manufacture dramatically over building a box with a fixed
set of ports, so it's unrealistic to expect the market will favor it.

Sure, it's a harder problem. A good challenge for engineers to solve.

-- 
-----------------------------------------------------------------
Daniel Senie                                        dts@senie.com
Amaranth Networks Inc.                    http://www.amaranth.com



From owner-ietf-outbound  Mon Apr 24 20:30:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA18400
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 20:30:03 -0400 (EDT)
Received: from tower.partan.com (tower.partan.com [198.6.255.248])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18361
	for <ietf@ietf.org>; Mon, 24 Apr 2000 20:27:16 -0400 (EDT)
Received: (from asp@localhost)
	by tower.partan.com (8.9.3/8.9.3) id UAA04711;
	Mon, 24 Apr 2000 20:27:14 -0400 (EDT)
Date: Mon, 24 Apr 2000 20:27:13 -0400
From: Andrew Partan <asp@partan.com>
To: Sean Doran <smd@ebone.net>
Cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Message-ID: <20000424202713.A4635@partan.com>
References: <200004241432.QAA04024@sean.ebone.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <200004241432.QAA04024@sean.ebone.net>; from smd@ebone.net on Mon, Apr 24, 2000 at 04:32:38PM +0200
X-Loop: ietf@ietf.org

On Mon, Apr 24, 2000 at 04:32:38PM +0200, Sean Doran wrote:
> Therefore, in order to support IPv6 house-network multihoming, so
> as to preserve at least these three features of traditional
> multihoming, either the current IPv6 addressing architecture's
> restrictions on who can be a TLA must be abandoned (so each house
> becomes a TLA), or NATs must be used to rewrite house-network
> addresses into various PA address ranges supplied by the multiple
> providers.

Or seperate the end system identifer from the routing goop.  This
solves lots of problems (while introducing others).
	--asp@partan.com (Andrew Partan)



From owner-ietf-outbound  Mon Apr 24 20:41:01 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA18579
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 20:40:51 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18531
	for <ietf@ietf.org>; Mon, 24 Apr 2000 20:38:53 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id UAA03162;
        Mon, 24 Apr 2000 20:37:46 -0400 (EDT)
Message-Id: <200004250037.UAA03162@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Anthony Atkielski" <anthony@atkielski.com>
cc: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-reply-to: Your message of "Mon, 24 Apr 2000 23:26:01 +0200."
             <010a01bfae33$b1518ca0$0a00000a@wanadoo.fr> 
Date: Mon, 24 Apr 2000 20:37:46 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Ah ... famous last words.  I feel confident that similar words were said
> when the original 32-bit address scheme was developed:
> 
> "Four billion addresses ... that's more than one computer for every person
> on Earth!"
> 
> "Only a few companies are every going to have more than a few computers ...
> just give a Class A to anyone who asks."

I wasn't there, but I expect it would have sounded even more preposterous
for someone to have said: "I'm absolutely positive that this Internet thing 
will reach to nearly everyone on the planet in a couple of decades, and 
therefore we need to make sure it has many times more than 32 bits of 
address space"  even though that's what eventually happened.  

but just because it happened once doesn't mean that it will happen again.
we do well to learn from the past, but the past doesn't repeat itself
exactly.

it often seems to be the case that if you design for the long
term, what you get back isn't deployable in the near term because
you've made the problem too hard.  and if you design for the near 
term, what you get back will break in the long term.  but at least 
you get somewhere with the latter approach - the fact that we got 
a global Internet out of IPv4 demonstrated to people that the 
concept was viable.

today's design constraints aren't the same as tomorrow's.  with
today's Internet a lack of address space is a big problem.  with
IPv6 there's a considerable amount of breathing room for address 
space.  address space shortage is just one of many possible problems.
as long as the network keeps growing at exponential rates we are 
bound to run into some other major hurdle in a few years.  it might
be address space but the chances are good that before we hit that 
limitation again that we will run into some other fundamental barrier.  we 
can either try to anticipate every possible hurdle that the Internet 
might face or we can concentrate on fixing the obvious problems now 
and wait for the later problems to make themselves apparent before 
trying to fix them.  if we try to anticipate every major hurdle, 
we will never agree on how to solve all of those problems, and the 
Internet will bog down to the point that it's no longer useful.

> But the real thing here is, even with the wisest allocations imaginable, we
> would still run out much, much faster than the total number of addresses in
> the address space might lead one to believe.  And that is because we have to
> _predict_ how addresses will be used, and we cannot easily change the
> consequences of those predictions.  

no, that's just bogus.  on one hand you're saying that we cannot predict
how addresses will be used, and on the other hand you're saying that you 
can definitely predict that we'll run out of IPv6 addreses very soon.

> Ten years, I'd say.  

right now you're just pulling numbers out of thin air.  you have yet to 
give any basis whatsoever to make such a prediction credible.

> > not really.  IP has always assumed that address space
> > would be delegated in power-of-two sized "chunks" ...
> 
> Aye, there's the rub.  It has always been necessary to _assume_ and
> _delegate_ address space, because the address space is finite in size.  

wrong. you need to make design assumptions about delegation points, and
delegate portions of address space, even for variable length addresses
of arbitrary size.

> > ... at first those chunks only came in 3 sizes (2**8,
> > 2**16, or 2**24 addresses), and later on it became possible
> > to delegate any power-of-two sized chunk.
> 
> But by then, a lot of the biggest chunks were already in use.

true, several of the class A blocks were already in use by then.  
but initial allocations of IPv6 space are much more conservative .

> > ... but even assuming ideally sized allocations, each
> > of those chunks would on average be only 50% utilized.
> 
> Right.  So the only solution is to get rid of the need to allocate in
> advance in the first place.

no.  even with variable length addresses you want to exercise some 
discipline about how you allocate addresses.  otherwise you end up
some addresses being much longer than necessary, and this creates 
inefficiency and problems for routing.

> > allocating space in advance might indeed take away
> > another few bits. but given the current growth rate
> > of the internet it is necessary.
> 
> Only with a fixed address space.

nope.  even phone numbers are allocated by prefix blocks.

> > the internet is growing so fast that a policy of
> > always allocating only the smallest possible chunk
> > for a net would not only be cumbersome, it would result
> > in poor aggregation in routing tables and quite
> > possibly in worse overall utilization of address space.
> 
> Exactly ... but that's the magic of the variable address scheme.  You only
> have to allocate disparate chunks in a fixed address scheme because the size
> of each chunk is limited by the length of an address field.  

no, there are lots of other reasons for doing it.  you seem to be 
forgetting that routing hierarchy doesn't necessarily follow 
address hierarchy.  and that the point of a network protocol is
to get payload, rather than addresses, from one point to another.

> But if the address field is variable, you can make any chunk as big 
> as you want. 

actually, no you can't.  because addresses still have to fit within 
the minimum size of a datagram on the network and have room left
over for payload.

> > Quite the contrary, the regional registries seem to
> > share your concern that we will use up IPv6 space too
> > quickly and *all* of the comments I've heard about the
> > initial assignment policies were that they were too
> > conservative.
> 
> No matter how conservative they are, the finite length of the address field
> will eventually cause problems, and much sooner than anyone thinks.

eventually I can buy.  but your predictions about the specific 
timeframe have no substance. 
 
> > IPv6 space does need to be carefully managed, but it
> > can be doled out somewhat more generously than IPv4 space.
> 
> And in 2030:

In 2030 (if I'm still doing this stuff) I will be much more concerned
about the overflow of UNIX time in 2038.

> > First of all, having too fine a granularity in allocation
> > prevents you from aggregating routes.
> 
> Only with a fixed address length.

variable length addresses with no constriants on address growth
have their own set of routing problems.

> > this is only amazing to those who haven't heard of
> > Moore's law.
> 
> Moore's law isn't the cause of the problem.  The problem isn't created by
> advances in hardware or software or network capacity; it is created by the
> inevitable impossibility of knowing the future with certainty.  

but this same impossibility means that we do not know whether we should
put today's energy into making variable length addresses work efficiently
or into something else.  so we made a guess - a design compromise -
that we're better off with very long fixed-length addresses because 
fast routing hardware is an absolute requirement, and at least today
it seems much easier to design fast routing hardware (or software)
that looks at fixed offsets within a packet, than to design hardware or
software that looks at variable offsets.

now it might turn out that in a few decades this will cause an address
space shortage.  but that doesn't mean that we made a wrong decision 
because in today's world having fixed offsets for addresses within
a packet (and thus fast routing) is more important than having arbitraily
long addresses.  

the biggest problem with IPv6 is the difficulty in getting it deployed.  
and IPv6 has enough barriers to deployment already without variable 
length addresses making it harder to route than IPv4.

> > fwiw, phone numbers do in fact have a fixed maximum
> > length which is wired into devices all over the planet ...
> 
> Yes, but it's way easier to make a field larger than it is to build and
> implement a new protocol.  

it depends on how many places have that length limitation wired-in.
we might could have made the IPv4 address larger except that every 
application on the net assumed fixed-length addresses.

> > ... it is not much easier to increase the overall
> > length of phone numbers than it is to make IP
> > addresses longer.
> 
> But in a variable-length system, you can make both ends variable.  

no you can't, because you still need globally scoped addresses, and
you have the incremental upgrade problem.  if you change the 
root of the address space you have to do it for everything at once.

Keith



From owner-ietf-outbound  Mon Apr 24 20:50:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA18693
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 20:50:03 -0400 (EDT)
Received: from lint.cisco.com (lint.cisco.com [171.68.224.209])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18538
	for <ietf@ietf.org>; Mon, 24 Apr 2000 20:39:45 -0400 (EDT)
Received: from bigger-dawgs.cisco.com (pferguso-isdn.cisco.com [171.70.114.134]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id RAA26999; Mon, 24 Apr 2000 17:38:40 -0700 (PDT)
Message-Id: <4.3.1.2.20000424203812.00a8bc70@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Mon, 24 Apr 2000 20:38:28 -0400
To: Andrew Partan <asp@partan.com>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
In-Reply-To: <20000424202713.A4635@partan.com>
References: <200004241432.QAA04024@sean.ebone.net>
 <200004241432.QAA04024@sean.ebone.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 08:27 PM 04/24/2000 -0400, Andrew Partan wrote:

>Or seperate the end system identifer from the routing goop.  This
>solves lots of problems (while introducing others).

Deja Vu.

- paul



From owner-ietf-outbound  Mon Apr 24 21:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA18994
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 21:10:04 -0400 (EDT)
Received: from sean.ebone.net (IDENT:root@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18847
	for <ietf@ietf.org>; Mon, 24 Apr 2000 21:00:49 -0400 (EDT)
Received: (from smd@localhost)
	by sean.ebone.net (8.9.3/8.9.3) id DAA05776;
	Tue, 25 Apr 2000 03:00:41 +0200 (CEST)
Date: Tue, 25 Apr 2000 03:00:41 +0200 (CEST)
From: Sean Doran <smd@ebone.net>
Message-Id: <200004250100.DAA05776@sean.ebone.net>
To: asp@partan.com, smd@ebone.net
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

asp writes:

| Or seperate the end system identifer from the routing goop.  This
| solves lots of problems (while introducing others).

Right, so in the 8+8 model, some router performs a NAT function by
writing in the routing goop portion at an address abstraction boundary.

The host does not need to know the routing goop that will be used,
nor does it need to know the full routing goop associated with a
host from which it receives a packet.

However, I am wary of your terminology.  Rather than a system
identifier, you instead want a local locator -- something that
is unique within the local addressing scope and which allows
other hosts and routers in the scope to locate the correct receiving
interface.   The "routing goop" is a locator which is useful to
hosts outside the local addressing scope, and may vary from location
to location in the Internet.

In particular, if you follow the excellent posting by Anthony Atkieski
about variable-length addressing, you might find yourself agreeing
that in principle the "routing goop" may vary from place to place
not only by value, but also by length.

The NAT function is that which translates the "routing goop" 
from "undefined" to something useful outside the originating
local addressing scope.   It can also translate the "routing goop"
from one value to another.  That translation can also be an extension;
e.g. changing "4321" into "654321".

The "system identifier" is either a locator (which is how I guess
you mean to use it) or an actual system name, which would behave
more like a DNS entry.

The IRTF's NSRG is looking at what the system name/endpoint identifier
should be, how it should be carried, how it can be used to determine
what locators to use, and so forth.   It's a tricky problem in some ways.

If you overload these concepts and stuff the value into a packet,
(like 8+8), it could be a unique number (8 bytes long in this case).
In a given local routing scope we flat-route on those 8 byte addresses.
Outside that routing scope, you would not route on those 8 byte addresses
at all (you'd use the other 8 bytes of "routing goop").
 
If the "system identifier" 8 bytes are globally unique, than any
action where in IPv4 you operate on IP address as a way of identifying 
a host, you would only use those 8 bytes.   For example, the equivalent
of an IN-ADDR.ARPA lookup would use only those bytes, and none of the
routing goop bytes.

The NAT function then can be more restricted - it translates
only the "routing goop" part and not the "system identifier" part
of an 8+8 address.  The "system identifier" 8 bytes is used by
end hosts to determine that they are talking to the same entities,
even though the "routing goop" has been adjusted one or more times
in flight between the two hosts.

This can all be emulated in IPv4 iff we have a separate namespace
for "system identifier" carried in a conversation somehow.  

However, since it does make NAT much more straightforward, I do
not expect the bruised-knees brigade to admit or even recognize
the extra utility that such a namespace would bring to IPv6.  -:(

Fortunately, and to scare Steve Deering again, there are some
bright and sane people who think most of IPv6 isn't so bad, and
who are willing to play nicely in NSRG in hopes of improving it.
This bodes well.

	Sean.



From owner-ietf-outbound  Mon Apr 24 21:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA19358
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 21:30:03 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19233
	for <ietf@ietf.org>; Mon, 24 Apr 2000 21:21:38 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3P1LRB21088;
	Mon, 24 Apr 2000 21:21:27 -0400
Message-Id: <200004250121.e3P1LRB21088@black-ice.cc.vt.edu>
To: Anthony Atkielski <anthony@atkielski.com>
cc: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-reply-to: Your message of "Mon, 24 Apr 2000 21:45:43 +0200."
             <00b601bfae25$ae270900$0a00000a@wanadoo.fr> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <BB2831D3689AD211B14C00104B14623B1E7569@HAZEN04>
            <00b601bfae25$ae270900$0a00000a@wanadoo.fr>
Date: Mon, 24 Apr 2000 21:21:19 -0400
X-Loop: ietf@ietf.org

On Mon, 24 Apr 2000 21:45:43 +0200, Anthony Atkielski <anthony@atkielski.com>  said:
> Not every machine on the Internet has an Ethernet card with a MAC address,
> otherwise it might not be such a bad idea.  I think using the MAC address is
> an excellent idea for software protection schemes (it's a lot more elegant
> than a hardware key such as a dongle), but nobody seems interested in that.

Nobody is interested in it because it doesn't work.

The Ethernet spec requires that each card have a unique MAC address
that's burnt onto the card.  However, due to some truly wierd stuff
done by DecNet "way back when", cards were *also* required to support
loading a new MAC address on the fly.

So to pirate a softare package that locks based on the MAC address, all
you have to do is pirate it off any compatible machine on any subnet
other than your own.  You can even pirate it off your own subnet
if you don't care about ARP working. ;)

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Mon Apr 24 21:50:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA20441
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 21:50:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19507
	for <ietf@ietf.org>; Mon, 24 Apr 2000 21:39:51 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3P1dTB34670;
	Mon, 24 Apr 2000 21:39:29 -0400
Message-Id: <200004250139.e3P1dTB34670@black-ice.cc.vt.edu>
To: Anthony Atkielski <anthony@atkielski.com>
cc: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-reply-to: Your message of "Mon, 24 Apr 2000 22:18:09 +0200."
             <00cb01bfae2a$381baae0$0a00000a@wanadoo.fr> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <20000424131939.7281335DC2@smb.research.att.com>
            <00cb01bfae2a$381baae0$0a00000a@wanadoo.fr>
Date: Mon, 24 Apr 2000 21:39:28 -0400
X-Loop: ietf@ietf.org

On Mon, 24 Apr 2000 22:18:09 +0200, Anthony Atkielski <anthony@atkielski.com>  said:
> allocate a fixed space in advance.  In a variable-length address space, you
> don't have to anticipate any kind of advance allocation--you can just add
> digits to addresses where they are required, and routers only need to look
> at enough of an address to figure out where it should go next.  In a

Actually, we argued a *lot* about fixed/variable.  The reason 128
bit fixed won out was to a large extent due to the people from
various large high-performance router companies wanting a way to 
switch packets *quickly*.  At the time, a DS3 was considered REALLY
fast, and only a few places had FDDI campus backbones.

The problem is that the router guys wanted to fast-path the case of
"no IP option field, routing entry in cache" so that after seeing
only the first few bytes, they could know what interface to enqueue
the outbound packet on *before the entire packet had even come in*.
So for them, the idea of being able to take a known fixed-lenght field
that happened to line up nicely on the hardware memory cache lines,
stuffing it through an associative-lookup cache or other hardware
assist, and knowing in one or three cycles how to route it, was
VERY enticing.

Of course, an OC48 instead of a DS3 only makes it more crucial -
do the math, and figure out how many nanoseconds you have to make
a routing decision when reading off an OC48...

> > Furthermore, if it's a variable-length address, the
> > router has to know where the end is, in order to look
> > at the next field.
> 
> Just put that up front.  For example, prefix the address with a length byte.
> If the byte is zero, the address is four bytes long (compatible with IPv4).
 
> It's not really hard.  You just have to write the code up front to handle
> it.  And if you don't want to allow for infinite capacity (you have to stop

It's easy to do for an end-user workstation that's already bogged down
by the bloat inherent in <insert your least favorite OS vendor here>.

It's hard to do for something that's truly high-performance.


> 
> Hmm... I don't know.  If you restrict the address field to routing only, do
> you still need anti-spoofing?  A given address can lead to only one
> endpoint, unless I'm missing something here.

Well, at least around here, we also look at the *source* address on
all packets inbound to our routers to see if they make sense.  If it's
coming in from off-campus, it shouldn't have a prefix that belongs to
our AS.  If it's coming into our backbone from a building subnet, the
source better be in that subnet's range.  And so on.  RFC2267 talks
about it in more detail.

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Mon Apr 24 22:20:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA20808
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 22:20:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20777
	for <ietf@ietf.org>; Mon, 24 Apr 2000 22:16:01 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id UAA22653
	for ietf@ietf.org  env-from <vjs>;
	Mon, 24 Apr 2000 20:16:00 -0600 (MDT)
Date: Mon, 24 Apr 2000 20:16:00 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004250216.UAA22653@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
X-Loop: ietf@ietf.org

> > Not every machine on the Internet has an Ethernet card with a MAC address,
> > otherwise it might not be such a bad idea.  I think using the MAC address is
> > an excellent idea for software protection schemes (it's a lot more elegant
> > than a hardware key such as a dongle), but nobody seems interested in that.
>
> Nobody is interested in it because it doesn't work.
>
> The Ethernet spec requires that each card have a unique MAC address
> that's burnt onto the card.  However, due to some truly wierd stuff
> done by DecNet "way back when", cards were *also* required to support
> loading a new MAC address on the fly.
>
> So to pirate a softare package that locks based on the MAC address, all
> you have to do is pirate it off any compatible machine on any subnet
> other than your own.  You can even pirate it off your own subnet
> if you don't care about ARP working. ;)


Both of those positions seem odd.  The first because not all boxes have
unique MAC addresses, and not merely because of the "locally administrated"
nonsense or even because not all boxes have Ethernet interfaces, although
the second of those is a good reason.  Another good reason is that all of
the major and reputable Ethernet vendors I've heard of have accidentally
shipped significant numbers of Ethernet interfaces with duplicate MAC
addresses.  In theory it's trivial to assign unique MAC addresses, but in
practice it is very hard to do it right all of the time.

Note also that many outfits have been using MAC addresses and other
tactics other than dongles to do node locking for at least 15 years.
I've heard rumors that Windows 2000 will join that creaky old bandwagon,
I assume by using what Microsoft calls a GUID for the obvious.

The stuff about breaking software "node locking" is just as odd.
Never mind that all the systems I've worked on did the right thing
even while using a locally assigned MAC address when an application
asked for the permanent, offical address.  The statement about prirates
assumes that they'll will abide by the hope in the locked software
that when it askes the operating system and libraries for MAC address,
it gets any of the host's MAC addresses instead of some other 6 byte
string that is more convenient for the pirate.  In other words, why
would you bother the network machinery instead of, for example,
improving the dynamic library that contains the system call wrappers?

    ...

About local addresses, neighbors passing each other's traffic, unlikely
commercial cooperation, and so forth--does no one remember UUCP,
perhaps before the Mapping Project tried (and failed) to make hostnames
globally unique?

  ...

I'm flummoxed by the reawakening of the years IPng argument.  All of
the positions stated seem very familiar, both those that I think
are better ideas than IPv6 and those that I still think are crazy.
Does anyone really hope that anything decided, discussed or considered
now will have any positive effect?  What can you expect to do by
re-opening the can--no--train load of worms except delay IPv6 by
another 10 years to recapitulate the entire sorry history, including
highlights such as the decision of the IAB to throw away TCP/IP and
switch to the OSI protocol suite?  If you did restart history, how
would you hope to avoid yet another restart in about 2010?

Aren't the years of IPng flaming in the main IETF list captured
somewhere so that those of us who were not overjoyed by the first
edition can rest in peace?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Mon Apr 24 23:15:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA22369
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 23:15:00 -0400 (EDT)
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22209
	for <ietf@ietf.org>; Mon, 24 Apr 2000 23:02:20 -0400 (EDT)
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate2.mot.com (motgate2 2.1) with ESMTP id UAA27703 for <ietf@ietf.org>; Mon, 24 Apr 2000 20:02:20 -0700 (MST)]
Received: [from il33exm01.wes.mot.com (il33exm01.wes.mot.com [154.56.3.118]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id UAA23728 for <ietf@ietf.org>; Mon, 24 Apr 2000 20:02:20 -0700 (MST)]
Received: by il33exm01.wes.mot.com with Internet Mail Service (5.5.2650.21)
	id <28T0BRFL>; Mon, 24 Apr 2000 22:02:21 -0500
Message-ID: <7195C03599D9D311BE580008C75697EB105381@il33exm01.wes.mot.com>
From: Mathis Jim-AJM005 <Jim.Mathis@Motorola.com>
To: ietf@ietf.org
Subject: RE: IPv6: Past mistakes repeated? 
Date: Mon, 24 Apr 2000 22:02:12 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-Loop: ietf@ietf.org

A brief history lesson...

There was some concern about a 32-bit address space.  MIT-LCS
proposed 48 (or 64-bit) addresses but that was coupled with a
reduction of the TCP sequence number to 16 bits.  After some
discussion, we settled on 32-bits based on the computing 
resources available at the time.  At that time, there was no
separate IP header, only addressing fields in the TCP header.

Around that time, the ARPANET had recently scaled up from
8-bit host addresses to 24-bits.  Seemed unlikely that anyone 
would build more than 100 ARPANET-sized networks with its huge
IMPs and PDP-10 mainframe computers (and UCLA's 360).  48-bit 
Ethernet addressing wasn't around yet; otherwise we probably 
would have picked 64 bits just to not have to deal with ARP. 
This was before Moore's law; Intel had just released the 
8008 microprocessor.  There were less than 100,000 large 
commercial buildings (>500,000 sq. ft) in the world; seemed
that the number of class-c addresses were sufficient.  For
better or worse, the size of the address field went unchanged
from the original version of TCP (before IP was a separate 
header).

We were caught short by a technology paradigm shift coming
from semiconductor physics.  If computers rode the same 
technology advancement curve as cars, we wouldn't be having
an address space problem now.

We cannot predict the next big technology paradigm shift.
The real lesson to learn from IPv4 - IPv6 (which I think 
was described by Knuth in regards to conversion of computer 
instruction sets but I can't find the reference) is the 
cost of delaying conversion.  For the longer you delay
the inevitable, the more installed base you have to 
convert and the exponentially higher the resulting cost.  

The excellent engineering to keep v4 running was too good
and has slowed the inevitable movement to larger address
spaces.  While there are no guarantees that 128-bits won't
be exhausted sometime in the future, we do know a lot more 
about address space management and allocation than when Jon 
started handing out net numbers. The Internet has always 
been a balancing act between being ready for the future 
and getting something working today.  IPv6 will not change 
this, so we need to be prepared for change.  The next "big" 
problem facing the Internet that will require a broad-scale 
swap-out of software probably won't be address-space related. 

We need to move forward with IPv6 both by deploying it in 
the "core" and setting a time-frame after which non-IPv4 
compatible addresses will be assigned.  Unless there is a 
clear reason to move, no one wants to change software just 
to change.  Once IPv6 is in the major backhaul carriers, ISPs
can role out improved services based on IPv6 which will be 
the real reason end-users upgrade.  Seems like a real 
leadership vacuum here...

Jim

> -----Original Message-----
> From: Keith Moore [mailto:moore@cs.utk.edu]
> Sent: Monday, April 24, 2000 2:36 PM
> To: Anthony Atkielski
> Cc: ietf@ietf.org
> Subject: Re: IPv6: Past mistakes repeated? 
> 
> 
> > What I find interesting throughout discussions that mention 
> IPv6 as a
> > solution for a shortage of addresses in IPv4 is that people see the
> > problems with IPv4, but they don't realize that IPv6 will 
> run into the
> > same difficulties.  _Any_ addressing scheme that uses addresses of
> > fixed length will run out of addresses after a finite 
> period of time,
> 
> I suppose that's true - as long as addresses are consumed at a rate
> faster than they are recycled.  But the fact that we will run out of
> addresses eventually might not be terribly significant - the Sun will
> also run out of hydrogen eventually, but in the meantime we still find
> it useful.
> 
> > and that period may be orders of magnitude shorter than anyone might
> > at first believe.
> 
> it is certainly true that without careful management IPv6 address
> space could be consumed fairly quickly.  but to me it looks like that
> with even moderate care IPv6 space can last for several tens of years.
> 
> > Consider IPv4.  Thirty-two bits allows more than four billion
> > individual machines to be addressed.  
> 
> not really.  IP has always assumed that address space would be
> delegated in power-of-two sized "chunks" - at first those chunks only
> came in 3 sizes (2**8, 2**16, or 2**24 addresses), and later on it
> became possible to delegate any power-of-two sized chunk.  but even
> assuming ideally sized allocations, each of those chunks would on
> average be only 50% utilized. 
> 
> so every level of delegation effectively uses 1 of those 32 bits, and
> on average most parts of the net are probably delegated 4-5 levels
> deep.  (IANA/regional registry/ISP/customer/internal). so we end up
> effectively not with 2**32 addresses but with something like 2**27 or
> 2**28.  (approximately 134 million or 268 million)
> 
> (see also RFC 1715 for a different analysis, which when applied to
> IPv4, yields similar results for the optimistic case)
> 
> allocating space in advance might indeed take away another few bits.
> but given the current growth rate of the internet it is necessary.
> the internet is growing so fast that a policy of always allocating
> only the smallest possible chunk for a net would not only be
> cumbersome, it would result in poor aggregation in routing tables and
> quite possibly in worse overall utilization of address space.
> 
> but if it someday gets easier to renumber a subnet we might then find
> it easier to garbage collect, and recycle, fragmented portions of
> address space.  and if the growth rate slowed down (which for various
> reasons is possible) then we could do advance allocation more
> conservatively.
> 
> > It should be clear that IPv6 will have the same problem.  The space
> > will be allocated in advance.  Over time, it will become 
> obvious that
> > the original allocation scheme is ill-adapted to changing 
> requirements
> > (because we simply cannot foresee those requirements).  Much, _much_
> > sooner than anyone expects, IPv6 will start to run short of 
> addresses,
> > for the same reason that IPv4 is running short.  It seems impossible
> > now, but I suppose that running out of space in IPv4 seemed 
> impossible
> > at one time, too.
> 
> IPv6 allocation will have some of the same properties of IPv4
> allocation.  We're still using power-of-two sized blocks, we'll still
> waste at least one bit of address space per level of delegation.  It
> will probably be somewhat easier to renumber networks and recycle
> address - how much easier remains to be seen.
> 
> OTOH, I don't see why IPv6 will necessarily have significantly more
> levels of assignment delegation.  Even if it needs a few more levels,
> 6 or 7 bits out of 128 total is a lot worse than 4 or 5 bits 
> out of 32.
> 
> > The allocation pattern is easy to foresee.  Initially, enormous
> > subsets of the address space will be allocated carelessly and
> > generously, because "there are so many addresses that we'll 
> never run
> > out" 
> 
> I don't know where you get that idea.  Quite the contrary, the
> regional registries seem to share your concern that we will use up
> IPv6 space too quickly and *all* of the comments I've heard about the
> initial assignment policies were that they were too conservative.
> IPv6 space does need to be carefully managed, but it can be doled out
> somewhat more generously than IPv4 space.
> 
> > and because nobody will want to expend the effort to achieve
> > finer granularity in the face of such apparent plenty.  
> 
> First of all, having too fine a granularity in allocation prevents you
> from aggregating routes.  Second, with power-of-two sized allocations
> there's a limit to how much granularity you can get - even if you
> always allocate optimal sized blocks.
> 
> > This mistake will be repeated for each subset of the address space
> > allocated, by each organization charged with allocating the space.
> 
> It's not clear that it's a mistake.  it's a tradeoff between having
> aggregatable addresses and distributed assignment on one hand and
> conserving address space on the other.  and the people doing address
> assignment these days are quite accustomed to thinking in these terms.
> 
> > If you need further evidence, look at virtual memory address spaces.
> > Even if a computer's architecture allows for a trillion bits of
> > addressing space, it invariably becomes fragmented and 
> exhausted in an
> > amazingly short time.  
> 
> this is only amazing to those who haven't heard of Moore's law.
> (presumably the same set of people who thought DES would 
> never be broken)
> 
> on the other hand, it's not clear how valid this analogy is for
> predicting the growth of the Internet - just because Moore's law (if
> it keeps on working) might predict that in a decade we could
> eventually have thousands of network-accessible computing devices for
> everyone on the planet, doesn't mean that those people would be able
> to deal with thousands of such devices.  and there do appear to be
> limits to the number of human beings that the planet can support.  and
> if by that time the robot population exceeds the human population then
> I'm happy to let the robots solve the problem of upgrading to a new
> version of IP.
> 
> and as for other planets, all kinds of assumptions about the current
> Internet fail when you try to make it work at interplanetary
> transmission latencies.  so if we do manage to significantly populate
> other planets or if we find extraterrestrial species that we want to
> network with, we'll have to build a new architecture.  and people are
> already working on that.
> 
> > The only real solution to this is an open-ended addressing 
> scheme--one
> > to which digits can be added as required.  
> 
> variable length addresses do have some nice properties.  there are
> also some drawbacks.
> 
> fwiw, phone numbers do in fact have a fixed maximum length which is
> wired into devices all over the planet - not just in the phone system
> but in numerous computer databases, etc..  it is not much easier to
> increase the overall length of phone numbers than it is to make IP
> addresses longer.  and once you set a fixed maximum length then it's
> just a matter of representation - do you have a variable-length
> address field or do you have a fixed-length field with zero padding?
> fixed-length fields are a lot easier for routers to deal with.  (and
> for similar reasons a lot of software uses fixed-length fields for
> phone numbers)
> 
> 128-bit IPv6 addresses are roughly equivalent to 40 digits, which IIRC
> is a lot longer than the maximum size of a phone number under E.164.
> (sorry, I don't have a copy handy to check)
> 
> and the means by which IPv6 addresses are being allocated is actually
> not so different from the means in which phone numbers are allocated -
> the major exception being that IPv6 prefixes are assigned to major
> ISPs rather than to geographic regions.  (the latter difference might
> affect routing but probably does not affect allocation efficiency).
> 
> so I think the bottom line answer to your message is that your concers
> are valid (if perhaps a bit exaggerated) and an allocation mechanism
> similar to what you suggest is already in place.
> 
> Keith
> 



From owner-ietf-outbound  Mon Apr 24 23:20:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA22431
	for ietf-outbound.10@ietf.org; Mon, 24 Apr 2000 23:20:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22250
	for <ietf@ietf.org>; Mon, 24 Apr 2000 23:04:52 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id XAA03656;
        Mon, 24 Apr 2000 23:04:19 -0400 (EDT)
Message-Id: <200004250304.XAA03656@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Andrew Partan <asp@partan.com>
cc: Sean Doran <smd@EBONE.NET>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Mon, 24 Apr 2000 20:27:13 EDT."
             <20000424202713.A4635@partan.com> 
Date: Mon, 24 Apr 2000 23:04:19 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Or seperate the end system identifer from the routing goop.  This
> solves lots of problems (while introducing others).

even if you do this the end system identifier needs to be globally
scoped, and you need to be able to use the end system identifier 
from anywhere in the net, as a means to reach that end system.  

otherwise you're in about the same shape as with a NATted network.

Keith



From owner-ietf-outbound  Tue Apr 25 00:00:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA23324
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 00:00:07 -0400 (EDT)
Received: from leonid.genesyslab.com (leonid.genesyslab.com [204.94.142.156])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23227
	for <ietf@ietf.org>; Mon, 24 Apr 2000 23:50:47 -0400 (EDT)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id UAA20717;
	Mon, 24 Apr 2000 20:50:23 -0700
Date: Mon, 24 Apr 2000 20:50:23 -0700
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200004250350.UAA20717@leonid.genesyslab.com>
To: asp@partan.com, moore@cs.utk.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org, smd@EBONE.NET
X-Loop: ietf@ietf.org

>From: Keith Moore <moore@cs.utk.edu>
>
>> Or seperate the end system identifer from the routing goop.  This
>> solves lots of problems (while introducing others).
>
>even if you do this the end system identifier needs to be globally
>scoped, and you need to be able to use the end system identifier
>from anywhere in the net, as a means to reach that end system.
>
  DNS is a bright and successfull example of such deal.

  It could be better to use domain names as system IDs but today
there is too much software which assume IP as system ID
(network ID of system in real).

>otherwise you're in about the same shape as with a NATted network.

		       - Leonid Yegoshin.



From owner-ietf-outbound  Tue Apr 25 00:10:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA23526
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 00:10:04 -0400 (EDT)
Received: from mail2.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA23273
	for <ietf@ietf.org>; Mon, 24 Apr 2000 23:58:32 -0400 (EDT)
Received: from 157.54.9.104 by mail2.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 24 Apr 2000 20:57:17 -0700 (Pacific Daylight Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2651.58)
	id <J2VXHJQP>; Mon, 24 Apr 2000 20:57:17 -0700
Message-ID: <D5922CA42F8CD31189D800805F19A16C04B7B194@RED-MSG-48>
From: Ian King <iking@microsoft.com>
To: "'Keith Moore'" <moore@cs.utk.edu>,
        Anthony Atkielski
	 <anthony@atkielski.com>
Cc: ietf@ietf.org
Subject: RE: IPv6: Past mistakes repeated? 
Date: Mon, 24 Apr 2000 20:57:12 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

Yes, we made a guess -- a design compromise.  Folks, we're engineers, and we
come up with "good enough" answers.  Sure, we try to make sure that the
"good enough" answers are good enough for the majority of situations, for a
reasonable length of time.  But we're not prophets or philosophers or
prescient -- we're just engineers.  We made some "good enough" guesses with
IPv4 that, as Keith points out, got us to the situation of a global Internet
-- and our present dilemma is a byproduct of that solution's success.  I
would not be disappointed if our next "good enough" guess lasts us as long
as the last one.  After all, I'll want SOMEthing entertaining to do twenty
years from now.  :-)  

BTW -- I feel the same way about NAT: it's "good enough" for many
situations.  :-) Send me mail at home, it goes to one machine on my internal
172.16 LAN; check out my personal webpages, you're talking to another
machine (and a different OS) in that address space.  You don't see that, and
frankly I don't think about it very often.  It's close to a "it just works"
solution -- which is "good enough" for now.  

-- Ian 

> -----Original Message-----
> From: Keith Moore [mailto:moore@cs.utk.edu]
> Sent: Monday, April 24, 2000 5:38 PM
> To: Anthony Atkielski
> Cc: ietf@ietf.org
> Subject: Re: IPv6: Past mistakes repeated? 
> 
> 
[snip]
> 
> but this same impossibility means that we do not know whether 
> we should
> put today's energy into making variable length addresses work 
> efficiently
> or into something else.  so we made a guess - a design compromise -
> that we're better off with very long fixed-length addresses because 
> fast routing hardware is an absolute requirement, and at least today
> it seems much easier to design fast routing hardware (or software)
> that looks at fixed offsets within a packet, than to design 
> hardware or
> software that looks at variable offsets.
> 
[snip]



From owner-ietf-outbound  Tue Apr 25 03:10:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA06616
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 03:10:04 -0400 (EDT)
Received: from meter.eng.uci.edu (meter.eng.uci.edu [128.200.85.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06456
	for <ietf@ietf.org>; Tue, 25 Apr 2000 03:00:13 -0400 (EDT)
Received: from thomas.eng.uci.edu (thomas.eng.uci.edu [128.200.9.237]) by meter.eng.uci.edu (8.8.8/) with ESMTP id AAA04554; Tue, 25 Apr 2000 00:00:02 -0700 (PDT)
Received: from localhost (miyer@localhost) by thomas.eng.uci.edu (8.8.8/) with ESMTP id AAA18414; Tue, 25 Apr 2000 00:00:01 -0700 (PDT)
Date: Tue, 25 Apr 2000 00:00:00 -0700 (PDT)
From: Mahadevan Iyer  <miyer@eng.uci.edu>
To: Mathis Jim-AJM005 <Jim.Mathis@Motorola.com>
cc: ietf@ietf.org
Subject: RE: IPv6: Past mistakes repeated? 
In-Reply-To: <7195C03599D9D311BE580008C75697EB105381@il33exm01.wes.mot.com>
Message-ID: <Pine.SOL.4.05.10004242349100.18319-100000@thomas.eng.uci.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


I wonder which we will run out of first: IPv6 addresses or our
energy resources? Does the earth have sufficient energy resources to
support the level of human economic activity implied by the exhaustion of
the IPv6 address space? Guess i am looking too far into the future? :)

Maha.


On Mon, 24 Apr 2000, Mathis Jim-AJM005 wrote:

> A brief history lesson...
> 
> There was some concern about a 32-bit address space.  MIT-LCS
> proposed 48 (or 64-bit) addresses but that was coupled with a
> reduction of the TCP sequence number to 16 bits.  After some
> discussion, we settled on 32-bits based on the computing 
> resources available at the time.  At that time, there was no
> separate IP header, only addressing fields in the TCP header.
> 
> Around that time, the ARPANET had recently scaled up from
> 8-bit host addresses to 24-bits.  Seemed unlikely that anyone 
> would build more than 100 ARPANET-sized networks with its huge
> IMPs and PDP-10 mainframe computers (and UCLA's 360).  48-bit 
> Ethernet addressing wasn't around yet; otherwise we probably 
> would have picked 64 bits just to not have to deal with ARP. 
> This was before Moore's law; Intel had just released the 
> 8008 microprocessor.  There were less than 100,000 large 
> commercial buildings (>500,000 sq. ft) in the world; seemed
> that the number of class-c addresses were sufficient.  For
> better or worse, the size of the address field went unchanged
> from the original version of TCP (before IP was a separate 
> header).
> 
> We were caught short by a technology paradigm shift coming
> from semiconductor physics.  If computers rode the same 
> technology advancement curve as cars, we wouldn't be having
> an address space problem now.
> 
> We cannot predict the next big technology paradigm shift.
> The real lesson to learn from IPv4 - IPv6 (which I think 
> was described by Knuth in regards to conversion of computer 
> instruction sets but I can't find the reference) is the 
> cost of delaying conversion.  For the longer you delay
> the inevitable, the more installed base you have to 
> convert and the exponentially higher the resulting cost.  
> 


> Jim
> 
> > -----Original Message-----
> > From: Keith Moore [mailto:moore@cs.utk.edu]
> > Sent: Monday, April 24, 2000 2:36 PM
> > To: Anthony Atkielski
> > Cc: ietf@ietf.org
> > Subject: Re: IPv6: Past mistakes repeated? 
> > 
> > 
> > > What I find interesting throughout discussions that mention 
> > IPv6 as a
> > > solution for a shortage of addresses in IPv4 is that people see the
> > > problems with IPv4, but they don't realize that IPv6 will 
> > run into the
> > > same difficulties.  _Any_ addressing scheme that uses addresses of
> > > fixed length will run out of addresses after a finite 
> > period of time,
> > 
> > I suppose that's true - as long as addresses are consumed at a rate
> > faster than they are recycled.  But the fact that we will run out of
> > addresses eventually might not be terribly significant - the Sun will
> > also run out of hydrogen eventually, but in the meantime we still find
> > it useful.
> > 
> > > and that period may be orders of magnitude shorter than anyone might
> > > at first believe.
> > 
> > it is certainly true that without careful management IPv6 address
> > space could be consumed fairly quickly.  but to me it looks like that
> > with even moderate care IPv6 space can last for several tens of years.
> > 
> > > Consider IPv4.  Thirty-two bits allows more than four billion
> > > individual machines to be addressed.  
> > 



From owner-ietf-outbound  Tue Apr 25 07:00:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA08339
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 07:00:03 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET (nod.Reston.mci.net [166.45.6.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08251
	for <ietf@ietf.org>; Tue, 25 Apr 2000 06:55:21 -0400 (EDT)
Received: from cerf.mci.net ([24.28.207.119])
 by shoe.reston.mci.net (PMDF V5.2-32 #40475)
 with ESMTPA id <01JON6WN8XOW8Y51JU@shoe.reston.mci.net> for ietf@ietf.org;
 Tue, 25 Apr 2000 06:55:18 EST
Date: Tue, 25 Apr 2000 06:54:47 -0400
From: "vinton g. cerf" <vcerf@MCI.NET>
Subject: RE: IPv6: Past mistakes repeated?
In-reply-to: <7195C03599D9D311BE580008C75697EB105381@il33exm01.wes.mot.c om>
X-Sender: vcerf@shoe.reston.mci.net (Unverified)
To: ietf@ietf.org
Message-id: <4.3.1.2.20000425065204.0125d050@shoe.reston.mci.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-Transfer-Encoding: 7BIT
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7BIT

For those of you who don't know, and Jim is too modest
to tell you, he was a member of the Stanford team that
designed and implemented the first TCP protocol versions.
Later he went on to build the first versions for the
portable Digital LSI-11s used in the Packet Radio network.

Vint
=================================================================
I moved to a new MCI WorldCom facility on Nov 11, 1999

MCI WorldCom
22001 Loudoun County Parkway
Building F2, Room 4115, ATTN: Vint Cerf
Ashburn, VA 20147
Telephone (703) 886-1690
FAX (703) 886-0047


"INTERNET IS FOR EVERYONE!" 
See you at INET2000, Yokohama, Japan July 18-21, 2000
http://www.isoc.org/inet2000




From owner-ietf-outbound  Tue Apr 25 07:20:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA08785
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 07:20:03 -0400 (EDT)
Received: from msw.mimesweeper.com (msw.mimesweeper.com [194.168.90.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08736
	for <ietf@ietf.org>; Tue, 25 Apr 2000 07:18:43 -0400 (EDT)
Received: from bell.mimesweeper.com (unverified) by msw.mimesweeper.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc2a85a12634bca17c629@msw.mimesweeper.com>;
 Tue, 25 Apr 2000 12:18:22 +0100
Received: from GK-VAIO (gk-vaio.mimesweeper.com [194.168.90.137]) by bell.mimesweeper.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id 2C7NSD22; Tue, 25 Apr 2000 12:17:59 +0100
Message-Id: <4.2.2.20000425090404.00a3c3f0@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 25 Apr 2000 09:08:40 +0100
To: Richard Shockey <rshockey@ix.netcom.com>
From: Graham Klyne <GK@dial.pipex.com>
Subject: How many IP addresses?
Cc: ietf@ietf.org
In-Reply-To: <4.3.2.20000423224201.00bbfd30@127.0.0.1>
References: <4.3.1.2.20000422234827.01305f30@shoe.reston.mci.net>
 <4.3.2.20000422201841.00c435d0@127.0.0.1>
 <200004222110.RAA00745@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 11:06 PM 4/23/00 -0500, Richard Shockey wrote:
>With "always on" IP and IP on anything this is closer to reality than we 
>might think. In order to permit a reasonable allocation of addresses with 
>room for growth the idea of 25 IP address per household and 10 person 
>actually seems conservative.

Following this line of thought, I'd suggest taking the number of electrical 
outlets and multiplying by some suitable constant (say, 10, or 1000).

And what about all those little wireless-connected gadgets;  an IP address 
for each TV remote-control (where everyone has their own, of course, for 
personalized access and prioritizing control conflicts...)

#g

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound  Tue Apr 25 09:50:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA12483
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 09:50:04 -0400 (EDT)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12281
	for <ietf@ietf.org>; Tue, 25 Apr 2000 09:41:18 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id E4AE04CE32; Tue, 25 Apr 2000 09:41:16 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id JAA28254;
	Tue, 25 Apr 2000 09:41:16 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 0497635DC2; Tue, 25 Apr 2000 09:41:10 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Graham Klyne <GK@dial.pipex.com>
Cc: Richard Shockey <rshockey@ix.netcom.com>, ietf@ietf.org
Subject: Re: How many IP addresses? 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 25 Apr 2000 09:41:10 -0400
Sender: smb@research.att.com
Message-Id: <20000425134111.0497635DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <4.2.2.20000425090404.00a3c3f0@pop.dial.pipex.com>, Graham Klyne wri
tes:
>At 11:06 PM 4/23/00 -0500, Richard Shockey wrote:
>>With "always on" IP and IP on anything this is closer to reality than we 
>>might think. In order to permit a reasonable allocation of addresses with 
>>room for growth the idea of 25 IP address per household and 10 person 
>>actually seems conservative.
>
>Following this line of thought, I'd suggest taking the number of electrical 
>outlets and multiplying by some suitable constant (say, 10, or 1000).
>
>And what about all those little wireless-connected gadgets;  an IP address 
>for each TV remote-control (where everyone has their own, of course, for 
>personalized access and prioritizing control conflicts...)

I've been in rooms where people have walked through exactly calculation.  
Let's throw a few numbers around.

Assume that the average person in the world has 1000 outlets.  That's 
preposterously large for even Bill Gates' house, I suspect, and it doesn't 
even account for dividing by the number of people per house.  But let's stick 
with 1000.  Assume that there are 25*10^9 people in the world -- 4x the 
current population.  And allocate 10 IP addresses for each of those outlets.
That means that we need a minimum of 25*10^9 IP addresses, plus allowances for 
delegation on TLA boundaries, smaller provider chunks, homes, etc.

So -- when I divide 2^128 by 25*10^9, I get ~2^80.  That's right -- 80 bits 
worth of address space for allocation inefficiencies.  If, at each of three
levels, we really use just one address out of every 2^16, we *still* have
32 bits left over.

Conclusion:  if we don't do things differently, we have more than enough 
addresses for any conceivable size of the Internet.  (In fact, if we assume 
that there are 300*10^9 stars in the Milky Way, we're not very far from being 
able to handle interstellar networking, at least in terms of the number of 
hosts.  But we may have to redefine the TTL field to let packets last for 50K 
years or so...)

OK -- if 2^128 is that large, why did I (among others) conclude that we needed 
some headroom?  There's a lot of history showing that address space *always* 
runs out, and that the consumption often comes from changing your paradigm.  A 
routing/addressing scheme like 8+8 is an example of what I mean.  In another 
vein, I have a project going that requires 2^16 addresses per host, and maybe 
2^32.  There are undoubtedly other new ideas we can play with *if* we have 
enough address space.  But we have to engineer this in some fashion that 
permits efficient use of these addresses by hosts and (especially) routers.  
(An earlier poster wrote that you "just have to write the code".  That's the 
wrong idea -- big iron routers don't use "code" to do forwarding, they use 
silicon, and very fast silicon at that.  There are routers in production use 
today that are handling OC-192 -- 10 Gbps -- links.  You can't do that in 
software.)

		--Steve Bellovin




From owner-ietf-outbound  Tue Apr 25 10:10:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA12929
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 10:10:04 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12764
	for <ietf@ietf.org>; Tue, 25 Apr 2000 10:02:05 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA00576;
        Tue, 25 Apr 2000 09:57:45 -0400 (EDT)
Message-Id: <200004251357.JAA00576@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Leonid Yegoshin <egoshin@genesyslab.com>
cc: asp@partan.com, moore@cs.utk.edu, ietf@ietf.org, smd@EBONE.NET
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Mon, 24 Apr 2000 20:50:23 PDT."
             <200004250350.UAA20717@leonid.genesyslab.com> 
Date: Tue, 25 Apr 2000 09:57:45 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> >even if you do this the end system identifier needs to be globally
> >scoped, and you need to be able to use the end system identifier
> >from anywhere in the net, as a means to reach that end system.
> 
>   DNS is a bright and successfull example of such deal.

actually, DNS is slow, unreliable, and often out of sync with reality.

DNS reverse lookup tables (PTR) are not as well maintained as forward 
lookup tables (A) so they're even less reliable.

hosts often don't know their own DNS names, so they wouldn't know
their connection endpoint names either.

DNS names are often ambiguous - because a single DNS name corresponds
to multiple hosts (all implementing the same service) or because a
single host supports multiple DNS domains (a different name for each
service) or both.

the binding between a DNS name and an address is not the same thing
as the binding between an address and a connection endpoint.  the
two have different purposes and different lifetimes.

when people say "DNS can do the job" they may be saying different
things, e.g.
(a) they are thinking in terms of using existing DNS servers, 
(b) they are thinking in terms of using the DNS protocol, having 
translation occur at the boundaries between routing goop realms 
(similar to NAT's DNS ALG), or
(c) they are thinking in terms of a DNS-like system, but not DNS

with separate servers (whether they are existing DNS servers or not)
there is the problem of keeping the servers updated as to the 
current condition of the network.

with DNS at translation boundaraies there is the problem of 
"call setup overhead" (having queries propagate through 
multiple layers of translation until they reach their destination
network) also in this case DNS becomes a routing protocol of 
sorts, since the thing you advertise from one realm to another
becomes a DNS suffix rather than than an address prefix.
it's not at all clear that this scales.  

in either case having to do a DNS-like query before you can transmit
is slow compared to just sending a packet to an IP address.

Keith

p.s. if there's ever going to be a split between endpoint names and
routing goop, I'm convinced that endpoint names have to be usable 
by themselves (perhaps with some speed penalty), that the 
mapping between endpoint names and routing goop needs to be maintained
by the routing infrastructure rather than in some separate database, 
and that the lookup needs to be able to be done implicitly (as a side 
effect of sending packets without routing goop to their destination) 
rather than explicitly.  I think such a separation might be a good idea, 
because our current means of propagating reachability information
and computing routes does have limitations.  but I don't see any need 
to change the packet format seen by hosts (from IPv6), or any need to
change end hosts at all, in order to do this.



From owner-ietf-outbound  Tue Apr 25 10:30:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA13404
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 10:30:04 -0400 (EDT)
Received: from corpmail.galaxyscientific.com ([38.221.233.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13290
	for <ietf@ietf.org>; Tue, 25 Apr 2000 10:25:39 -0400 (EDT)
Received: from BELLOPEM (igate.tc.faa.gov [155.178.180.5]) by corpmail.galaxyscientific.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id 2KDCNDFY; Tue, 25 Apr 2000 10:24:00 -0400
From: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
To: "Steven M. Bellovin" <smb@research.att.com>
Cc: <ietf@ietf.org>
Subject: RE: How many IP addresses? 
Date: Tue, 25 Apr 2000 10:23:29 -0400
Message-ID: <PPECLLOGBEPHLOMKLNAMAENNCAAA.Michael.CTR.Bellopede@tc.faa.gov>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
In-Reply-To: <9925@tc.faa.gov>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit




>  But we have to engineer this in some fashion that
>permits efficient use of these addresses by hosts and (especially) routers.
>(An earlier poster wrote that you "just have to write the code".  That's
the
>wrong idea -- big iron routers don't use "code" to do forwarding, they use
>silicon, and very fast silicon at that.  There are routers in production
use
>today that are handling OC-192 -- 10 Gbps -- links.  You can't do that in
>software.)
>                --Steve Bellovin

Software, firmware, its a matter of semantics.  Do you think that silicon
magically performs routing and logical functions.  Hmmm...

-Michael B. Bellopede
 Michael.CTR.Bellopede@tc.faa.gov





From owner-ietf-outbound  Tue Apr 25 11:00:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA16147
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 11:00:04 -0400 (EDT)
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15536
	for <ietf@ietf.org>; Tue, 25 Apr 2000 10:56:47 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-green.research.att.com (Postfix) with ESMTP
	id 1F3401E008; Tue, 25 Apr 2000 10:56:46 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id KAA29966;
	Tue, 25 Apr 2000 10:56:45 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id A6EC135DC2; Tue, 25 Apr 2000 10:56:39 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
Cc: ietf@ietf.org
Subject: Re: How many IP addresses? 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 25 Apr 2000 10:56:39 -0400
Sender: smb@research.att.com
Message-Id: <20000425145639.A6EC135DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <PPECLLOGBEPHLOMKLNAMAENNCAAA.Michael.CTR.Bellopede@tc.faa.gov>, "Mi
chael B. Bellopede" writes:
>
>
>
>>  But we have to engineer this in some fashion that
>>permits efficient use of these addresses by hosts and (especially) routers.
>>(An earlier poster wrote that you "just have to write the code".  That's
>the
>>wrong idea -- big iron routers don't use "code" to do forwarding, they use
>>silicon, and very fast silicon at that.  There are routers in production
>use
>>today that are handling OC-192 -- 10 Gbps -- links.  You can't do that in
>>software.)
>>                --Steve Bellovin
>
>Software, firmware, its a matter of semantics.  Do you think that silicon
>magically performs routing and logical functions.  Hmmm...

Well, yes, magic might help the routing problem, if you have suitable pixie 
dust...  

More seriously, my point is that the techniques, optimizations, and costs are 
very different for software versus hardware.  If you're accustomed to thinking 
in software terms, you're not likely to make the proper design tradeoffs.

		--Steve Bellovin




From owner-ietf-outbound  Tue Apr 25 11:10:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA16506
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 11:10:02 -0400 (EDT)
Received: from fwns1.raleigh.ibm.com (fwns1d.raleigh.ibm.com [204.146.167.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16388
	for <ietf@ietf.org>; Tue, 25 Apr 2000 11:04:34 -0400 (EDT)
Received: from rtpmail03.raleigh.ibm.com (rtpmail03.raleigh.ibm.com [9.37.172.47])
	by fwns1.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id LAA26724;
	Tue, 25 Apr 2000 11:04:03 -0400
Received: from ludwigia.raleigh.ibm.com (ludwigia.raleigh.ibm.com [9.37.60.3])
	by rtpmail03.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id LAA36412;
	Tue, 25 Apr 2000 11:04:03 -0400
Received: from hygro.raleigh.ibm.com (IDENT:root@lig32-226-34-220.us.lig-dial.ibm.com [32.226.34.220]) by ludwigia.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id LAA23966; Tue, 25 Apr 2000 11:00:19 -0400
Received: from hygro.adsl.duke.edu (IDENT:narten@localhost.localdomain [127.0.0.1])
	by hygro.adsl.duke.edu (8.9.3/8.9.3) with ESMTP id KAA00869;
	Tue, 25 Apr 2000 10:57:30 -0400
Message-Id: <200004251457.KAA00869@hygro.adsl.duke.edu>
To: John Stracke <francis@ecal.com>
cc: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-Reply-To: Message from John Stracke <francis@ecal.com> 
   of "Mon, 24 Apr 2000 13:21:34 EDT." <3904829E.6292EA65@ecal.com> 
Date: Tue, 25 Apr 2000 10:57:30 -0400
From: Thomas Narten <narten@hygro.adsl.duke.edu>
X-Loop: ietf@ietf.org

John Stracke <francis@ecal.com> writes:

> Wasn't one of the design goals of IPv6 to make renumbering easier,
> so that people could move from small assignments to large ones?

Yes.  IPv6's primary tool in this regard is that it supports multiple
addresses simultaneously. To renumber, you add a new address to each
of your devices (corresponding to the addresses appropriate for the
new ISP) and start using it. For a transition period, both addresses
work equally well. When everything is switched over to the new
address, you simply stop using the old address. There are mechanisms
in IPv6 that make this approach straightforward (i.e., specifying when
to start using the new addresses, how long to overlap using both the
old and new ones, and when to finally retire the old addresses). No
flag day, no need to even reboot machines.

Thomas



From owner-ietf-outbound  Tue Apr 25 11:20:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA16776
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 11:20:03 -0400 (EDT)
Received: from fwns2.raleigh.ibm.com (fwns2d.raleigh.ibm.com [204.146.167.236])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16394
	for <ietf@ietf.org>; Tue, 25 Apr 2000 11:04:39 -0400 (EDT)
Received: from rtpmail03.raleigh.ibm.com (rtpmail03.raleigh.ibm.com [9.37.172.47])
	by fwns2.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id LAA24790;
	Tue, 25 Apr 2000 11:04:04 -0400
Received: from ludwigia.raleigh.ibm.com (ludwigia.raleigh.ibm.com [9.37.60.3])
	by rtpmail03.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id LAA26692;
	Tue, 25 Apr 2000 11:04:07 -0400
Received: from hygro.raleigh.ibm.com (IDENT:root@lig32-226-34-220.us.lig-dial.ibm.com [32.226.34.220]) by ludwigia.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id LAA23970; Tue, 25 Apr 2000 11:00:23 -0400
Received: from hygro.adsl.duke.edu (IDENT:narten@localhost.localdomain [127.0.0.1])
	by hygro.adsl.duke.edu (8.9.3/8.9.3) with ESMTP id KAA00848;
	Tue, 25 Apr 2000 10:48:55 -0400
Message-Id: <200004251448.KAA00848@hygro.adsl.duke.edu>
To: Sean Doran <smd@ebone.net>
cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-Reply-To: Message from Sean Doran <smd@ebone.net> 
   of "Mon, 24 Apr 2000 16:32:38 +0200." <200004241432.QAA04024@sean.ebone.net> 
Date: Tue, 25 Apr 2000 10:48:55 -0400
From: Thomas Narten <narten@hygro.adsl.duke.edu>
X-Loop: ietf@ietf.org

Sean Doran <smd@ebone.net> writes:

> Unfortunately, IPv6's current addressing architecture makes it very
> difficult to do this sort of traditional multihoming if one is not
> a TLA.

This is not true. IPv6's TLA scheme has as its primary goal placing an
upper bound on the number of routing prefixes that are needed in the
core. I.e., a backbone provider is only required to maintain routes
for each individual TLA in order to have reachability to ALL
destinations. Contrast that with today's IPv4 where the number of
prefixes that need to be maintained in the DFZ in order to have global
reachability is more-or-less unbounded, so some prefixes are not
reachable from everywhere.

That doesn't mean that all or even any of these routes will be
optimal. An individual provider, may, maintain longer prefixes for
selected destinations in order to provide better contectivity, say, to
those willing to pay. Thus, traditional multihoming is still quite
possible, assuming the various ISPs that need to handle the routes
agree to do so. But the goal is to make such routes exceptions that
are value-add rather than are a fundamental requirement in order to
insure global reachability for all.

Thomas



From owner-ietf-outbound  Tue Apr 25 11:30:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA17043
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 11:30:04 -0400 (EDT)
Received: from fwns1.raleigh.ibm.com (fwns1d.raleigh.ibm.com [204.146.167.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16400
	for <ietf@ietf.org>; Tue, 25 Apr 2000 11:04:45 -0400 (EDT)
Received: from rtpmail03.raleigh.ibm.com (rtpmail03.raleigh.ibm.com [9.37.172.47])
	by fwns1.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id LAA26740;
	Tue, 25 Apr 2000 11:04:13 -0400
Received: from ludwigia.raleigh.ibm.com (ludwigia.raleigh.ibm.com [9.37.60.3])
	by rtpmail03.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id LAA35164;
	Tue, 25 Apr 2000 11:04:13 -0400
Received: from hygro.raleigh.ibm.com (IDENT:root@lig32-226-34-220.us.lig-dial.ibm.com [32.226.34.220]) by ludwigia.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id LAA23974; Tue, 25 Apr 2000 11:00:27 -0400
Received: from hygro.adsl.duke.edu (IDENT:narten@localhost.localdomain [127.0.0.1])
	by hygro.adsl.duke.edu (8.9.3/8.9.3) with ESMTP id KAA00832;
	Tue, 25 Apr 2000 10:41:08 -0400
Message-Id: <200004251441.KAA00832@hygro.adsl.duke.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-Reply-To: Message from "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu> 
   of "Sat, 22 Apr 2000 05:48:36 EDT." <200004220948.FAA01188@ginger.lcs.mit.edu> 
Date: Tue, 25 Apr 2000 10:41:08 -0400
From: Thomas Narten <narten@hygro.adsl.duke.edu>
X-Loop: ietf@ietf.org

"J. Noel Chiappa" <jnc@ginger.lcs.mit.edu> writes:

> For a classic example, look at the recommendations of the IAB Workshop last
> year about IPSEC (and I'll asssume for the moment that IPSec is important to
> securing the Internet, and stay away from the debates about IPSEC versus SSL,
> etc):

>    It is urgent that we implement and deploy IPsec using some other
>    identifier than 32-bit IP addresses ... The current IPsec specifications
>    support the use of several different Identity types (e.g. Domain Name,
>    User@Domain Name). ... We strongly urge the IETF to completely
>    deprecate the use of the binary 32-bit IP addresses within IPsec
>    ... in particular any IP address dependencies should be eliminated from
>    ISAKMP and IKE. Ubiquitous deployment of the Secure DNS Extensions ([8])
>    should be strongly encouraged to facilitate widespread deployment of IPsec
>    (including IKE) without address-based Identity types.

> So, has any of this happened?

If I had a dollar for every time someone suggested just fixing
IPsec...

"Fixing" IPsec really also means fixing TCP/UDP, since they have
checksums that cover the IP addresses in use. Sure, if IPsec is in use
its MACs are stronger than the TCP/IP checksum, but one still has to
fix TCP/UDP to be IPsec aware so that they don't step on each other's
toes and do the wrong thing.

Bernard Aboba's recent posting to ipsra provides some excellent
details on some of the issues.

From: "Bernard Aboba" <aboba@internaut.com>
To: <ietf-ipsra@vpnc.org>
Date: Sat, 15 Apr 2000 15:56:35 -0700
Subject: NAT and IPSEC issues
Reply-To: <aboba@internaut.com>
Importance: Normal

While we're on the subject of NAT and IPSRA issues, it might
make sense to articulate what the issues are exactly. 
Here's my understanding:

a) IPSEC AH will not go through the NAT, because the AH header
   incorporates the IP source and destination fields in the 
   authentication hash. 

b) IPSEC ESP does not incorporate the IP source and destination
   fields in its authentication hash. However, there is an
   implicit dependency on source and dest. addresses within
   TCP and UDP checksums which cover the "pseudo-header." 
   Therefore ISPEC ESP will only go through the NAT if 
   TCP/UDP protocols are not involved (as in IPSEC tunnel
   mode or IPSEC/GRE), UDP/TCP checksums are turned off, or
   if UDP/TCP checksums are ignored by the receiving party. 

c) IKE will only go through the NAT if the parties do not
   check or use IP addresses in IKE MM identifiers (several 
   current implementations don't do this) AND if in addition 
   they don't check or use IP addresses in IKE QM identifiers 
   (most implementations DO use addresses and check them). 

d) Because of IKE rekeying behavior, it is necessary for 
   implementations to float their IKE source port in order
   to enable NATs to de-multiplex incoming rekeys which may
   not use the same cookies as the earlier traffic. 

e) In order to enable an IPSEC implementation to send traffic
   down the correct IPSEC SA, it is necessary for those SAs
   to be differentiated in some way. In practice this implies
   negotiation of non-overlapping filters.

Some conclusions resulting from the above:

1) Because many IPSEC tunnel mode implementations negotiate
   filters of "ANY to ANY" it is possible for their IKE traffic 
   to pass through NATs. However, the issue of overlapping filters
   means that there can only be a single IPSEC tunnel up from
   behind the NAT box to the security gateway. If there were two
   tunnels up, each with the same filters, the security gateway
   could be confused and send traffic down the wrong one. 

2) While it might be helpful to use something other than IP
   addresses as identifiers in IKE MM, in practice the real
   issue is the identifiers used in IKE QM. While FQDNs or
   userIDs could be used to signify "me" and "you" if it is
   necessary to use subnets in the filters it is not clear 
   how this could be addressed. 

3) While IPSEC tunnel mode with "ANY to ANY" filters 
   can pass through a NAT, IPSEC/L2TP cannot, due to the 
   specific filters that need to be negotiated. 

4) To get IPSEC transport mode to work (with ESP) it would
   be necessary to either turn off UDP/TCP checksumming or
   have receivers not do checksum checks on packets protected
   by ISPEC SAs. At first glance, it wouldn't appear that
   ignoring checksum checks would do much damage since 
   the cryptographic hashes are stronger than checksums
   anyway. 
   



From owner-ietf-outbound  Tue Apr 25 11:40:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA17472
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 11:40:05 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16746
	for <ietf@ietf.org>; Tue, 25 Apr 2000 11:18:32 -0400 (EDT)
Received: from zed.isi.edu (zed.isi.edu [128.9.160.57])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id IAA23436;
	Tue, 25 Apr 2000 08:18:24 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.8.7/8.8.6) id IAA08321;
	Tue, 25 Apr 2000 08:18:21 -0700 (PDT)
Message-Id: <200004251518.IAA08321@zed.isi.edu>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: moore@cs.utk.edu (Keith Moore)
Date: Tue, 25 Apr 2000 08:18:20 -0700 (PDT)
Cc: egoshin@genesyslab.com (Leonid Yegoshin), asp@partan.com, moore@cs.utk.edu,
        ietf@ietf.org, smd@EBONE.NET
In-Reply-To: <200004251357.JAA00576@astro.cs.utk.edu> from "Keith Moore" at Apr 25, 2000 09:57:45 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

% > >even if you do this the end system identifier needs to be globally
% > >scoped, and you need to be able to use the end system identifier
% > >from anywhere in the net, as a means to reach that end system.
% > 
% >   DNS is a bright and successfull example of such deal.
% 
% actually, DNS is slow, unreliable, and often out of sync with reality.
% 
% DNS reverse lookup tables (PTR) are not as well maintained as forward 
% lookup tables (A) so they're even less reliable.

	This is an assertion that I've heard over the years
	and I've come to beleive (based on regular audits of
	the in-addr space) that this is an Internet equivalent
	of an urban legend.  I'd really like to see your backing 
	data on this.

	The 2q2000 data for the in-addr tree shows 77402 unique
	servers answering for 693,337 zones.  
	19515 servers blocked/refused data. Of the 57887 that 
	answered, these are the numbers for improper configuration:

	BAD_SERVER:	4278
	FORMERR:	8
	NXDOMAIN:	28

	So, of the 57,887 visable servers, 4314 are improperly configured 
	in the visable in-addr.arpa. tree.  Thats 7.45% of the
	servers being "not well maintained".  I know of no similar data
	collected on the forward tree as a whole. I'm currently checking
	the data in a few TLDs to see if spot data may indicate a trend.

	Now as to the accuracy of the data in the zones, that depends
	on the owner of the data beleiving the data correct and that
	will be very hard to check.

--bill



From owner-ietf-outbound  Tue Apr 25 11:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA17754
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 11:50:07 -0400 (EDT)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16927
	for <ietf@ietf.org>; Tue, 25 Apr 2000 11:25:15 -0400 (EDT)
Received: from [171.78.6.241] (dhcp006-241.bbn.com [171.78.6.241])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id LAA10303;
	Tue, 25 Apr 2000 11:01:51 -0400 (EDT)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: day@po1.bbn.com
Message-Id: <v04011700b52b622f05c8@[171.78.140.250]>
In-Reply-To: <20000425134111.0497635DC2@smb.research.att.com>
Date: Tue, 25 Apr 2000 11:01:53 -0400
To: "Steven M. Bellovin" <smb@RESEARCH.ATT.COM>,
        Graham Klyne <GK@dial.pipex.com>
From: John Day <day@bbn.com>
Subject: Re: How many IP addresses?
Cc: Richard Shockey <rshockey@ix.netcom.com>, ietf@ietf.org
X-Loop: ietf@ietf.org

At 9:41 -0400 4/25/00, Steven M. Bellovin wrote:
>In message <4.2.2.20000425090404.00a3c3f0@pop.dial.pipex.com>, Graham
>Klyne wri
>tes:
>>At 11:06 PM 4/23/00 -0500, Richard Shockey wrote:
>>>With "always on" IP and IP on anything this is closer to reality than we
>>>might think. In order to permit a reasonable allocation of addresses with
>>>room for growth the idea of 25 IP address per household and 10 person
>>>actually seems conservative.
>>
>>Following this line of thought, I'd suggest taking the number of electrical
>>outlets and multiplying by some suitable constant (say, 10, or 1000).
>>
>>And what about all those little wireless-connected gadgets;  an IP address
>>for each TV remote-control (where everyone has their own, of course, for
>>personalized access and prioritizing control conflicts...)
>
>I've been in rooms where people have walked through exactly calculation.
>Let's throw a few numbers around.
>
>Assume that the average person in the world has 1000 outlets.  That's
>preposterously large for even Bill Gates' house, I suspect, and it doesn't
>even account for dividing by the number of people per house.  But let's stick
>with 1000.  Assume that there are 25*10^9 people in the world -- 4x the
>current population.  And allocate 10 IP addresses for each of those outlets.
>That means that we need a minimum of 25*10^9 IP addresses, plus allowances
>for
>delegation on TLA boundaries, smaller provider chunks, homes, etc.
>
>So -- when I divide 2^128 by 25*10^9, I get ~2^80.  That's right -- 80 bits
>worth of address space for allocation inefficiencies.  If, at each of three
>levels, we really use just one address out of every 2^16, we *still* have
>32 bits left over.

Doesn't this leave out a few pieces of data?  Given the current IPv6
address format, which includes a globally unique 64 bit interface ID and 64
bits of globally unique routing goop.  My calculation is that you only have
2^64 addresses to work with which leaves roughly 12 bits, maybe 14 to work
with.

But still, should be more than enough, don't you think?



From owner-ietf-outbound  Tue Apr 25 12:00:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA18055
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 12:00:07 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17715
	for <ietf@ietf.org>; Tue, 25 Apr 2000 11:48:53 -0400 (EDT)
Received: from zed.isi.edu (zed.isi.edu [128.9.160.57])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id IAA27864;
	Tue, 25 Apr 2000 08:48:50 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.8.7/8.8.6) id IAA08741;
	Tue, 25 Apr 2000 08:48:47 -0700 (PDT)
Message-Id: <200004251548.IAA08741@zed.isi.edu>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: narten@hygro.adsl.duke.edu (Thomas Narten)
Date: Tue, 25 Apr 2000 08:48:47 -0700 (PDT)
Cc: smd@ebone.net (Sean Doran), ietf@ietf.org
In-Reply-To: <200004251448.KAA00848@hygro.adsl.duke.edu> from "Thomas Narten" at Apr 25, 2000 10:48:55 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

% 
% Sean Doran <smd@ebone.net> writes:
% 
% > Unfortunately, IPv6's current addressing architecture makes it very
% > difficult to do this sort of traditional multihoming if one is not
% > a TLA.
% 
% This is not true. IPv6's TLA scheme has as its primary goal placing an
% upper bound on the number of routing prefixes that are needed in the
% core. I.e., a backbone provider is only required to maintain routes
% for each individual TLA in order to have reachability to ALL
% destinations. Contrast that with today's IPv4 where the number of
% prefixes that need to be maintained in the DFZ in order to have global
% reachability is more-or-less unbounded, so some prefixes are not
% reachable from everywhere.
% 
% Thomas

and this is different from only carrying the 253 usable /8 prefixes in
IPv4 how? 

--bill



From owner-ietf-outbound  Tue Apr 25 12:10:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA18456
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 12:10:05 -0400 (EDT)
Received: from mail.perspex.com (IDENT:tlilley@mail.perspex.com [12.5.16.108])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17836
	for <ietf@ietf.org>; Tue, 25 Apr 2000 11:52:25 -0400 (EDT)
Received: from localhost (tlilley@localhost) by mail.perspex.com (8.8.7/8.7.3) with SMTP id PAA29514; Tue, 25 Apr 2000 15:49:44 GMT
Date: Tue, 25 Apr 2000 15:49:44 +0000 (/etc/localtime)
From: Tripp Lilley <tlilley@perspex.com>
To: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
cc: "Steven M. Bellovin" <smb@research.att.com>, ietf@ietf.org
Subject: RE: How many IP addresses? 
In-Reply-To: <PPECLLOGBEPHLOMKLNAMAENNCAAA.Michael.CTR.Bellopede@tc.faa.gov>
Message-ID: <Pine.LNX.3.96.1000425154705.24095O-100000@mail.perspex.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Tue, 25 Apr 2000, Michael B. Bellopede wrote:

> >wrong idea -- big iron routers don't use "code" to do forwarding, they use
> >silicon, and very fast silicon at that.  There are routers in production
> >                --Steve Bellovin
> 
> Software, firmware, its a matter of semantics.  Do you think that silicon
> magically performs routing and logical functions.  Hmmm...

Uh, "hardware" != "EEPROM + CPU" here. "hardware" == "custom routing
ASICs". In the "no options, entry in cache" scenario Steve mentions, the
processor "don't enter into it", as it all goes through the raw silicon.

Think gates. Not bill gates, logic gates.

-- 
   Tripp Lilley  *  tripp@perspex.com  *  http://stargate.sg505.net/~tlilley/
------------------------------------------------------------------------------
  "I get a lot of letters like, 'Dear John, I've got a dead alien. What
   should I do with it?'  One word: barbecue!"

   - John Lovitz, A Yellow Pages commercial



From owner-ietf-outbound  Tue Apr 25 12:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA18729
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 12:20:03 -0400 (EDT)
Received: from shell.nominum.com (shell.nominum.com [204.152.187.59])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18706
	for <ietf@ietf.org>; Tue, 25 Apr 2000 12:19:53 -0400 (EDT)
Received: from nominum.com (shell.nominum.com [204.152.187.59])
	by shell.nominum.com (Postfix) with ESMTP
	id A29F931905; Tue, 25 Apr 2000 09:19:18 -0700 (PDT)
Message-ID: <3905C584.68DD615D@nominum.com>
Date: Tue, 25 Apr 2000 09:19:16 -0700
From: "David R. Conrad" <David.Conrad@nominum.com>
Organization: Nominum, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: Thomas Narten <narten@hygro.adsl.duke.edu>
Cc: Sean Doran <smd@EBONE.NET>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
References: <200004251448.KAA00848@hygro.adsl.duke.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Thomas,

> This is not true. IPv6's TLA scheme has as its primary goal placing an
> upper bound on the number of routing prefixes that are needed in the
> core.
...
> Contrast that with today's IPv4 where the number of
> prefixes that need to be maintained in the DFZ in order to have global
> reachability is more-or-less unbounded, so some prefixes are not
> reachable from everywhere.

As you know, this is not IPv6 magic.  The underlying routing technology
between v4 and v6, namely CIDR, is identical.  The only difference is that _by
convention_, the number of routing prefixes in v6 is limited.  If we were to
create an IPv4 Internet' without the historical baggage of the existing IPv4
Internet, the same conventions could be applied.

> Thus, traditional multihoming is still quite
> possible, assuming the various ISPs that need to handle the routes
> agree to do so. 

I find it a bit strange that people seem to think the logic / incentives /
disincentives that drive multihoming in the v4 Internet will not apply in the
v6 Internet.

Rgds,
-drc



From owner-ietf-outbound  Tue Apr 25 12:30:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA18982
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 12:30:06 -0400 (EDT)
Received: from ns2.microwavenetworks.com (ns2.microwavenetworks.com [209.44.144.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18919
	for <ietf@ietf.org>; Tue, 25 Apr 2000 12:26:58 -0400 (EDT)
Received: from mercury.mns (exchmail [172.16.11.6])
	by ns2.microwavenetworks.com (8.9.3/8.9.3) with ESMTP id LAA03837;
	Tue, 25 Apr 2000 11:23:57 -0500
Received: by MERCURY with Internet Mail Service (5.0.1460.8)
	id <CDGQ8MKC>; Tue, 25 Apr 2000 11:21:44 -0500
Message-ID: <CC96542306D7D2119E0B080009EB58FE9582BA@MERCURY>
From: Timothy Behne <TimothyB@microwavenetworks.com>
To: "'John Day'" <day@bbn.com>, "Steven M. Bellovin" <smb@RESEARCH.ATT.COM>,
        Graham Klyne <GK@DIAL.PIPEX.COM>
Cc: Richard Shockey <rshockey@IX.NETCOM.COM>, ietf@ietf.org
Subject: RE: How many IP addresses?
Date: Tue, 25 Apr 2000 11:21:42 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1460.8)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Also, I dont see how you got 25*10^9 * 1000 * 10 = 25*10^9.  Should be
25*10^13.  This requires log(25*10^13)/log(2), or 48 bits, to use every
address.  So the original answer (80 bits left over) was correct, and using
25*10^9 in the calculation must have been a typo.  I just had to satisfy
myself :)

Anyway, even if we REALLY only have 64 bits, we still have 16 left over, and
given the assumptions we made about the number of addresses each person will
require, it still seems to be more than enough.

-----Original Message-----
From: John Day [mailto:day@bbn.com]
Sent: Tuesday, April 25, 2000 10:02 AM
To: Steven M. Bellovin; Graham Klyne
Cc: Richard Shockey; ietf@ietf.org
Subject: Re: How many IP addresses?


At 9:41 -0400 4/25/00, Steven M. Bellovin wrote:
>In message <4.2.2.20000425090404.00a3c3f0@pop.dial.pipex.com>, Graham
>Klyne wri
>tes:
>>At 11:06 PM 4/23/00 -0500, Richard Shockey wrote:
>>>With "always on" IP and IP on anything this is closer to reality than we
>>>might think. In order to permit a reasonable allocation of addresses with
>>>room for growth the idea of 25 IP address per household and 10 person
>>>actually seems conservative.
>>
>>Following this line of thought, I'd suggest taking the number of
electrical
>>outlets and multiplying by some suitable constant (say, 10, or 1000).
>>
>>And what about all those little wireless-connected gadgets;  an IP address
>>for each TV remote-control (where everyone has their own, of course, for
>>personalized access and prioritizing control conflicts...)
>
>I've been in rooms where people have walked through exactly calculation.
>Let's throw a few numbers around.
>
>Assume that the average person in the world has 1000 outlets.  That's
>preposterously large for even Bill Gates' house, I suspect, and it doesn't
>even account for dividing by the number of people per house.  But let's
stick
>with 1000.  Assume that there are 25*10^9 people in the world -- 4x the
>current population.  And allocate 10 IP addresses for each of those
outlets.
>That means that we need a minimum of 25*10^9 IP addresses, plus allowances
>for
>delegation on TLA boundaries, smaller provider chunks, homes, etc.
>
>So -- when I divide 2^128 by 25*10^9, I get ~2^80.  That's right -- 80 bits
>worth of address space for allocation inefficiencies.  If, at each of three
>levels, we really use just one address out of every 2^16, we *still* have
>32 bits left over.

Doesn't this leave out a few pieces of data?  Given the current IPv6
address format, which includes a globally unique 64 bit interface ID and 64
bits of globally unique routing goop.  My calculation is that you only have
2^64 addresses to work with which leaves roughly 12 bits, maybe 14 to work
with.

But still, should be more than enough, don't you think?



From owner-ietf-outbound  Tue Apr 25 12:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA19248
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 12:40:04 -0400 (EDT)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19148
	for <ietf@ietf.org>; Tue, 25 Apr 2000 12:35:54 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id D961B4CE0F; Tue, 25 Apr 2000 12:35:51 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id MAA01995;
	Tue, 25 Apr 2000 12:35:51 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 9F3ED35DC2; Tue, 25 Apr 2000 12:35:45 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Timothy Behne <TimothyB@microwavenetworks.com>
Cc: "'John Day'" <day@bbn.com>, Graham Klyne <GK@dial.pipex.com>,
        Richard Shockey <rshockey@ix.netcom.com>, ietf@ietf.org
Subject: Re: How many IP addresses? 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 25 Apr 2000 12:35:45 -0400
Sender: smb@research.att.com
Message-Id: <20000425163545.9F3ED35DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <CC96542306D7D2119E0B080009EB58FE9582BA@MERCURY>, Timothy Behne writ
es:
>Also, I dont see how you got 25*10^9 * 1000 * 10 = 25*10^9.  Should be
>25*10^13.  This requires log(25*10^13)/log(2), or 48 bits, to use every
>address.  So the original answer (80 bits left over) was correct, and using
>25*10^9 in the calculation must have been a typo.  I just had to satisfy
>myself :)

Yes, that was in fact a typo, and my calculations used 10^13.
>
>Anyway, even if we REALLY only have 64 bits, we still have 16 left over, and
>given the assumptions we made about the number of addresses each person will
>require, it still seems to be more than enough.

As I indicated, the real issue is innovative ways to use the address space.

		--Steve Bellovin




From owner-ietf-outbound  Tue Apr 25 12:50:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA19477
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 12:50:03 -0400 (EDT)
Received: from postoffice.cisco.com (postoffice.cisco.com [171.69.198.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19297
	for <ietf@ietf.org>; Tue, 25 Apr 2000 12:41:31 -0400 (EDT)
Received: from [10.19.130.188] (deering-dsl3.cisco.com [10.19.130.188]) by postoffice.cisco.com (8.8.7-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id JAA05205; Tue, 25 Apr 2000 09:36:35 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@postoffice
Message-Id: <v04220801b52b78f8ac20@[10.19.130.188]>
In-Reply-To: <200004251548.IAA08741@zed.isi.edu>
References: <200004251548.IAA08741@zed.isi.edu>
Date: Tue, 25 Apr 2000 09:37:24 -0700
To: Bill Manning <bmanning@ISI.EDU>
From: Steve Deering <deering@cisco.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: narten@hygro.adsl.duke.edu (Thomas Narten), smd@ebone.net (Sean Doran),
        ietf@ietf.org
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 8:48 AM -0700 4/25/00, Bill Manning wrote:
>and this is different from only carrying the 253 usable /8 prefixes in
>IPv4 how? 

The set of customers who have addresses under a given IPv4 /8 prefix greater
than 127 do not all aggregate into a single topological subregion (e.g., a
single ISP), and therefore more granular routes must be widely disseminated
to make those customers reachable.  That's the difference.

Steve



From owner-ietf-outbound  Tue Apr 25 13:00:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA19699
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 13:00:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19332
	for <ietf@ietf.org>; Tue, 25 Apr 2000 12:42:12 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3PGg2B26284;
	Tue, 25 Apr 2000 12:42:02 -0400
Message-Id: <200004251642.e3PGg2B26284@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Bill Manning <bmanning@ISI.EDU>
cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Tue, 25 Apr 2000 08:18:20 PDT."
             <200004251518.IAA08321@zed.isi.edu> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200004251518.IAA08321@zed.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 25 Apr 2000 12:41:50 -0400
X-Loop: ietf@ietf.org

On Tue, 25 Apr 2000 08:18:20 PDT, Bill Manning said:
> 	The 2q2000 data for the in-addr tree shows 77402 unique
> 	servers answering for 693,337 zones.  
> 	19515 servers blocked/refused data. Of the 57887 that 
> 	answered, these are the numbers for improper configuration:
> 
> 	BAD_SERVER:	4278
> 	FORMERR:	8
> 	NXDOMAIN:	28
> 
> 	So, of the 57,887 visable servers, 4314 are improperly configured 
> 	in the visable in-addr.arpa. tree.  Thats 7.45% of the
> 	servers being "not well maintained".  I know of no similar data

Does "not well maintained" include the following:

1) DNS server for the zone is originally configured correctly, and the
first 20-30 hosts are entered with a proper A record and a PTR that matches.

2) Clueful guy leaves, new DNS "goo-roo" takes over, and adds the next 300
machines with just an A record, and no PTR matching.  The checks you make
would show this as "well maintained", even though 90% of the hosts are broken
with respect to PTR entries.

Given that 7% of the sites can't get past step (1), I'm willing to bet that
a lot MORE of the sites are accumulating cruft under step (2).

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Tue Apr 25 13:10:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA19915
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 13:10:03 -0400 (EDT)
Received: from watsun.cc.columbia.edu (IDENT:cu51491@watsun.cc.columbia.edu [128.59.39.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19381
	for <ietf@ietf.org>; Tue, 25 Apr 2000 12:44:52 -0400 (EDT)
Received: (from jaltman@localhost)
	by watsun.cc.columbia.edu (8.8.5/8.8.5) id MAA26299;
	Tue, 25 Apr 2000 12:44:28 -0400 (EDT)
Date: Tue, 25 Apr 2000 12:44:27 EDT
From: Jeffrey Altman <jaltman@columbia.edu>
Reply-To: jaltman@columbia.edu
To: Bill Manning <bmanning@ISI.EDU>
Cc: moore@cs.utk.edu (Keith Moore), egoshin@genesyslab.com (Leonid Yegoshin),
        asp@partan.com, moore@cs.utk.edu, ietf@ietf.org, smd@EBONE.NET
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: Your message of Tue, 25 Apr 2000 08:18:20 -0700 (PDT)
Message-ID: <CMM.0.90.4.956681067.jaltman@watsun.cc.columbia.edu>
X-Loop: ietf@ietf.org

> % > >even if you do this the end system identifier needs to be globally
> % > >scoped, and you need to be able to use the end system identifier
> % > >from anywhere in the net, as a means to reach that end system.
> % > 
> % >   DNS is a bright and successfull example of such deal.
> % 
> % actually, DNS is slow, unreliable, and often out of sync with reality.
> % 
> % DNS reverse lookup tables (PTR) are not as well maintained as forward 
> % lookup tables (A) so they're even less reliable.
> 
> 	This is an assertion that I've heard over the years
> 	and I've come to beleive (based on regular audits of
> 	the in-addr space) that this is an Internet equivalent
> 	of an urban legend.  I'd really like to see your backing 
> 	data on this.

This is hardly an urban legend.  Columbia University requires the
use of tcpwrappers in Paranoid mode which requires that the forward
and reverse lookups for an IP address in DNS match.  The Kermit
Project is based at Columbia University and uses its systems for
our FTP and HTTP access.  A week does not go by when we do not
get complaints about people being unable to access our FTP server
due to a failure of the forward and reverse to match.

Just from the first 8 hours of logs today:

  proxauth3-bb2.globalintranet.net != 212.234.59.254
  hide193.nhs.uk != 195.107.47.193
  marta-c-gw.caravan.ru != 212.24.53.234
  su9127.eclipse.co.uk != 212.104.136.138
  
Granted this is hardly a scientific study.  But we see this from
approximately a dozen new addresses every day.



    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org




From owner-ietf-outbound  Tue Apr 25 13:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA20142
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 13:20:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19614
	for <ietf@ietf.org>; Tue, 25 Apr 2000 12:55:43 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id MAA02714;
	Tue, 25 Apr 2000 12:55:32 -0400
Date: Tue, 25 Apr 2000 12:55:32 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200004251655.MAA02714@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

    > From: Brian Lloyd <brian@lloyd.com>

I was thinking about your message, and something from my exchanges with Keith
Moore suddenly popped into my head with great clarity. I think it's the
answer to your question immediately below - and it has some very grave
consequences.

Although it's something which has basically been said before, I find this new
formulation makes the problem - and its implications - especially clear (and
so I hope everyone will take the time to read it - it's not long).


    > whatever happened to IPv6? 128 bit addresses would certainly allow us
    > to continue using IP addresses as endpoint identifiers thus eliminating
    > the need for NAT. It seems that this is a more reasonable solution than
    > trying to make NAT work under all circumstances.

The basic key *architectural* problem with NAT (as opposed to all the
mechanical problems like encrypted checksums, etc, some of which can be
solved with variant mechanisms like RSIP), as made clear by Keith's comments,
is that when you have a small number of external addresses being shared by a
larger number of hosts behind some sort of "address-sharing" device, there's
no permanent association between an address and a host. It's *that* that
causes many of the worst problems - problems for which there *is* no good
work-around (because the problem is fundamental in nature).

Now, if you have a site which has more hosts than it can get external IPv4
addresses for, then as long as there are considerable numbers of IPv4 hosts a
site needs to interoperate with, *deploying IPv6 internally to the site does
the site basically no good at all*. Why?

Because for interactions with those external IPv4 hosts (who will be the vast
majority of the hosts one wants to talk to, in the initial stages of
deployment), *you have exactly the same architectural problem*. No matter
what IPv6<->IPv4 interoperability mechanism you use, you still have that same
*fundamental* problem - no permanent association between a host and an
address (in this case, the IPv4 address that it *has* to use to communicate
with an IPv4-only host).


When one looks at the overall business/economic case for deploying IPv6, in
the light of this, the results are fairly devastating - and explain perfectly
what we've been seeing for the last couple of years (rapid increase in the
number of NAT boxes, and basically no traction for IPv6).

A site considering deploying IPv6 is in one of two cases: it already has
enough IPv4 addresses, or it doesn't. In the foremer case, what's the upside
to deploying IPv6? Autoconfiguration, etc aren't enough to outweigh all the
costs of switching (to software which is less available, less tested, less
tuned, etc).

In the latter case, it's equally as bad: they are going to have to struggle
with the problems inherent in IPv4-address-sharing technology whether they go
with IPv6 or not, and again, the remaining advantages of IPv6 (autoconfig,
etc) are outweighed by the costs.


I'm still sorting through the implications from this, trying to put them all
with equal clarity, but one thing that does seem clear is that this kind of
upgrade model is economically unworkable in the current large-scale Internet.
Exactly what will work is something that needs to be pondered for a while.

One possible lesson is that we need think about how any new stuff is going to
make peoples lives significantly easier overall as soon as they start to
deploy it, because without that, probably very little is going to get done.

	Noel



From owner-ietf-outbound  Tue Apr 25 13:30:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA20326
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 13:30:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19645
	for <ietf@ietf.org>; Tue, 25 Apr 2000 12:56:53 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id JAA07033;
	Tue, 25 Apr 2000 09:56:20 -0700 (PDT)
Message-ID: <3905CE2D.67397FD2@isi.edu>
Date: Tue, 25 Apr 2000 09:56:13 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Daniel Senie <dts@senie.com>
CC: Ian King <iking@microsoft.com>,
        "'Anthony Atkielski'" <anthony@atkielski.com>, ietf@ietf.org,
        touch@ISI.EDU
Subject: Re: IPv6: Past mistakes repeated?
References: <D5922CA42F8CD31189D800805F19A16C04B7B16B@RED-MSG-48> <39047ADB.84B3F256@senie.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Daniel Senie wrote:
> 
> Ian King wrote:
> >
> >From the reports I read, this was implemented by mapping phone numbers
> to some other tag (which the user doesn't see) which is used to get the
> calls to the proper carrier and ultimately to the proper user.
> 
> Sounds a whole lot like using DNS to map names to IP addresses. Of
> course we expose users to IP addresses WAY too often, and overuse them
> in applications as well, for this analogy to be really workable for the
> Internet.

It might also sound like another level of indirection would be useful.

DNS -> IP is sometimes difficult to manage because both can change. It
would be useful to have an ID that had nothing to do with either,
allowing renumbering and renaming without losing that pointer.

E.g. DNS <-> ID <-> IP

Joe



From owner-ietf-outbound  Tue Apr 25 13:40:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA20543
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 13:40:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19995
	for <ietf@ietf.org>; Tue, 25 Apr 2000 13:11:02 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA08830;
	Tue, 25 Apr 2000 10:10:57 -0700 (PDT)
Message-ID: <3905D19B.14E3BE5@isi.edu>
Date: Tue, 25 Apr 2000 10:10:51 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Anthony Atkielski <anthony@atkielski.com>
CC: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
References: <200004241936.PAA01885@astro.cs.utk.edu> <010a01bfae33$b1518ca0$0a00000a@wanadoo.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Anthony Atkielski wrote:
> 
> Exactly ... but that's the magic of the variable address scheme.  You only
> have to allocate disparate chunks in a fixed address scheme because the size
> of each chunk is limited by the length of an address field.  But if the
> address field is variable, you can make any chunk as big as you want.  If
> you have addresses of 4739124xx initially (Metropolis only had a few
> machines at first), and you run out of addresses after 473912498, you just
> make 473912499 point to "more addresses for Metropolis," and start
> allocating, say 4739124990001 through 4739124999998 (you always leave at
> least one slot empty so that it can point to "more addresses").

Seems like that's very inefficient. You're building a tree. You make the
tree deeper in places where you have more nodes.

Even with forward-looking allocations, the tree is going to lopside
toward a linear organization, and need to be rebalanced.

(e.g., renumbered).

> No matter how conservative they are, the finite length of the address field
> will eventually cause problems, and much sooner than anyone thinks.

And variable length addrs. will cause problems eventually too, but it'll
be harder to explain why.

Joe



From owner-ietf-outbound  Tue Apr 25 13:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA20714
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 13:50:03 -0400 (EDT)
Received: from teapot27.domain5.bigpond.com (teapot27.domain5.bigpond.com [139.134.5.174])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA20061
	for <ietf@ietf.org>; Tue, 25 Apr 2000 13:15:42 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by teapot27.domain5.bigpond.com (NTMail 3.02.13) with ESMTP id ba853243 for <ietf@ietf.org>; Wed, 26 Apr 2000 02:26:54 +1000
Received: from DC-56-16.bpb.bigpond.com ([203.40.56.16]) by mail5.bigpond.com (Claudes-Ultra-Violet-MailRouter V2.7e 9/9768171); 26 Apr 2000 02:26:53
From: "$ Mafiouso" <Mafiouso@most-wanted.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 26 Apr 2000 02:16:46 +1000
Subject: You Gota See!
Reply-To: Mafiouso@most-wanted.com
Organization: Mafiouso Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
X-Priority: 1
Message-Id: <16265456883117@domain5.bigpond.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

$ Hey!

$ Check Out This:

http://mafiouso3.tripod.com

$ The Best In Everything Mp3s, Pictures, Movies What Ever Your After You Will 
Find It Here, 

$ Want a HOT Christina Aguilera Background For Your PC
$ Just Goto The Link Below And Right Click, Then `SET AS WALLPAPER.

http://mafiouso3.tripod.com/Christina.jpg

:)  Remember It's Da A Hit!

$ Contact Mafiouso At:

$ ICQ   53709750
$ Email mafiouso@most-wanted.com



From owner-ietf-outbound  Tue Apr 25 14:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA21022
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 14:00:03 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20227
	for <ietf@ietf.org>; Tue, 25 Apr 2000 13:22:48 -0400 (EDT)
Received: from zed.isi.edu (zed.isi.edu [128.9.160.57])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA10606;
	Tue, 25 Apr 2000 10:22:45 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.8.7/8.8.6) id KAA10059;
	Tue, 25 Apr 2000 10:22:42 -0700 (PDT)
Message-Id: <200004251722.KAA10059@zed.isi.edu>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: deering@cisco.com (Steve Deering)
Date: Tue, 25 Apr 2000 10:22:42 -0700 (PDT)
Cc: ietf@ietf.org
In-Reply-To: <v04220801b52b78f8ac20@[10.19.130.188]> from "Steve Deering" at Apr 25, 2000 09:37:24 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

% 
% At 8:48 AM -0700 4/25/00, Bill Manning wrote:
% >and this is different from only carrying the 253 usable /8 prefixes in
% >IPv4 how? 
% 
% The set of customers who have addresses under a given IPv4 /8 prefix greater
% than 127 do not all aggregate into a single topological subregion (e.g., a
% single ISP), and therefore more granular routes must be widely disseminated
% to make those customers reachable.  That's the difference.
% 
% Steve

Given the nature of trans-oceanic b/w vs. local b/w arguments I've heard
over the years, I'd say that these delegations are esentially constrained
to topological subregions and that for the most part, having the largest
incumbent ISPs in each region announce the respective /8 would roughly 
meet the IPv6, heirarchical aggregation argument.


133.0.0.0/8 - Japan
193/8           RIPE NCC - Europe                       May 93
194/8           RIPE NCC - Europe                       May 93
195/8           RIPE NCC - Europe                       May 93
199/8           ARIN - North America                    May 93
200/8           ARIN - Central and South America        May 93
201/8           Reserved - Central and South America    May 93
202/8           APNIC - Pacific Rim                     May 93
203/8           APNIC - Pacific Rim                     May 93
204/8           ARIN - North America                    Mar 94
205/8           ARIN - North America                    Mar 94
206/8           ARIN - North America                    Apr 95
207/8           ARIN - North America                    Nov 95
208/8           ARIN - North America                    Apr 96
209/8           ARIN - North America                    Jun 96
210/8           APNIC - Pacific Rim                     Jun 96
211/8           APNIC - Pacific Rim                     Jun 96
212/8           RIPE NCC - Europe                       Oct 97
213/8           RIPE NCC - Europe                       Mar 99
214/8           US-DOD                                  Mar 98
215/8           US-DOD                                  Mar 98
216/8           ARIN - North America                    Apr 98

-- 
--bill



From owner-ietf-outbound  Tue Apr 25 14:10:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA21297
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 14:10:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20647
	for <ietf@ietf.org>; Tue, 25 Apr 2000 13:45:27 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA13534;
	Tue, 25 Apr 2000 10:45:23 -0700 (PDT)
Message-ID: <3905D9AC.354119A0@isi.edu>
Date: Tue, 25 Apr 2000 10:45:16 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Anthony Atkielski <anthony@atkielski.com>
CC: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
References: <BB2831D3689AD211B14C00104B14623B1E7569@HAZEN04> <00b601bfae25$ae270900$0a00000a@wanadoo.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Anthony Atkielski wrote:
> 
> > I agree! Why create a finite anything when an infinite
> > possibility exists?
> 
> Exactly.  If you designed an open-ended protocol, you're far less likely to
> ever have to rewrite it.

PS - that's what we have version numbers for.

Open-ended can sometimes mean "you never know when you're exercising
(exorcising) new code" too.

Joe



From owner-ietf-outbound  Tue Apr 25 14:20:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA21491
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 14:20:02 -0400 (EDT)
Received: from leonid.genesyslab.com (pbinat33.genesyslab.com [209.233.177.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20844
	for <ietf@ietf.org>; Tue, 25 Apr 2000 13:54:29 -0400 (EDT)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id KAA21157;
	Tue, 25 Apr 2000 10:52:27 -0700
Date: Tue, 25 Apr 2000 10:52:27 -0700
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200004251752.KAA21157@leonid.genesyslab.com>
To: moore@cs.utk.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

>From: Keith Moore <moore@cs.utk.edu>
>
>> >even if you do this the end system identifier needs to be globally
>> >scoped, and you need to be able to use the end system identifier
>> >from anywhere in the net, as a means to reach that end system.
>>
>>   DNS is a bright and successfull example of such deal.
>
>actually, DNS is slow, unreliable, and often out of sync with reality.
>
>DNS reverse lookup tables (PTR) are not as well maintained as forward
>lookup tables (A) so they're even less reliable.
>
  (Bill Manning has another mind here - read it, please)

>hosts often don't know their own DNS names, so they wouldn't know
>their connection endpoint names either.
>
>DNS names are often ambiguous - because a single DNS name corresponds
>to multiple hosts (all implementing the same service) or because a
>single host supports multiple DNS domains (a different name for each
>service) or both.
>
   Yes, it is a reason why we can't use today domain names as system ID.
But it means that we should shift consideration to appropriate level -
- IP addresses. The second level of indirection arises but it is not
bad as long as we do not decrease a setup speed.

>the binding between a DNS name and an address is not the same thing
>as the binding between an address and a connection endpoint.  the
>two have different purposes and different lifetimes.
>
  I agree here.

>when people say "DNS can do the job" they may be saying different
>things, e.g.
>(a) they are thinking in terms of using existing DNS servers,
>(b) they are thinking in terms of using the DNS protocol, having
>translation occur at the boundaries between routing goop realms
>(similar to NAT's DNS ALG), or
>(c) they are thinking in terms of a DNS-like system, but not DNS
>
   I speak about (c). Routing addresses may be handled by providers
but not end-user. It should be

   (1) more accurate
   (2) more fast
   (3) independent in terms "rule of game" (may be chanded later
       without rewriting all)

>with separate servers (whether they are existing DNS servers or not)
>there is the problem of keeping the servers updated as to the
>current condition of the network.
>
>with DNS at translation boundaraies there is the problem of
>"call setup overhead" (having queries propagate through
>multiple layers of translation until they reach their destination
>network) also in this case DNS becomes a routing protocol of
>sorts, since the thing you advertise from one realm to another
>becomes a DNS suffix rather than than an address prefix.
>it's not at all clear that this scales.
>
  Keith, it depends from design. I can propose
 (1) caching,
 (2) implicit router resolution on each DNS A? query (each TCP setup
     precedes DNS A? query or using cached values) - "router DNS" may track
     each DNS query/response and append routing prefix to response.
     In this case there isn't any time lag... at least up to TTL expiration.
 (3) Separate network datagram service addresses from connection-oriented.
     We have two real network datagram services now - DNS and may be NTP
     (Voice RTP traffic or like UDP is in real a connection-oriented srvs)

But I don't afraid "call setup overhead" (see previous) because I afraid
only call setup speed decrease and support issues. As long as call setup
speed is not changed and support simple I like it.

>in either case having to do a DNS-like query before you can transmit
>is slow compared to just sending a packet to an IP address.
>
   We can implement technics which do both in the same time.
We do not need to replicate DNS again. We should admit that DNS is
network service in conrast with end-customer srvs and handle it different.
It means that different service rules and may be different set of addresses
may be used for this. The same is in BGP - there is a practice to hide
inter-router addresses of provider backbone, for exam to increase security
and give additional flexibility of backbone configuration.

>Keith
>
>p.s. if there's ever going to be a split between endpoint names and
>routing goop, I'm convinced that endpoint names have to be usable
>by themselves

  Yes.

>              (perhaps with some speed penalty), that the
>mapping between endpoint names and routing goop needs to be maintained
>by the routing infrastructure rather than in some separate database,

  Yes ! Yes !

>and that the lookup needs to be able to be done implicitly (as a side
>effect of sending packets without routing goop to their destination)
>rather than explicitly.  I think such a separation might be a good idea,
>because our current means of propagating reachability information
>and computing routes does have limitations.  but I don't see any need
>to change the packet format seen by hosts (from IPv6), or any need to
>change end hosts at all, in order to do this.

   Keith, sorry, didn't read this p.s. before I wrote answer on main
mail body. You absolutely understand me, thank you.

			       - Leonid Yegoshin, LY22



From owner-ietf-outbound  Tue Apr 25 14:30:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA21675
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 14:30:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20905
	for <ietf@ietf.org>; Tue, 25 Apr 2000 13:56:55 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA01588;
        Tue, 25 Apr 2000 13:56:18 -0400 (EDT)
Message-Id: <200004251756.NAA01588@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Bill Manning <bmanning@ISI.EDU>
cc: moore@cs.utk.edu (Keith Moore), egoshin@genesyslab.com (Leonid Yegoshin),
        asp@partan.com, ietf@ietf.org, smd@EBONE.NET
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Tue, 25 Apr 2000 08:18:20 PDT."
             <200004251518.IAA08321@zed.isi.edu> 
Date: Tue, 25 Apr 2000 13:56:18 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

        So, of the 57,887 visable servers, 4314 are improperly configured 
        in the visable in-addr.arpa. tree.  Thats 7.45% of the
        servers being "not well maintained". 

a 92.55% reliability rate is not exactly impressive, at least not in
a favorable sense.

it might be tolerable if a failure of the PTR lookup doesn't cause
the application to fail. but after all, people are saying that DNS
is good enough to serve as a means to map endpoint identifiers
to realm-local addresses or routing goop.  if applications were 
written to depend on DNS reverse lookups in order to get endpoint
identifiers of their peers, they would only work as reliably as DNS,
which isn't very good.

thanks for backing up my assertion with hard data.

Keith



From owner-ietf-outbound  Tue Apr 25 14:40:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA21947
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 14:40:04 -0400 (EDT)
Received: from postoffice.cisco.com (postoffice.cisco.com [171.69.198.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20970
	for <ietf@ietf.org>; Tue, 25 Apr 2000 13:59:15 -0400 (EDT)
Received: from [10.19.130.188] (deering-dsl3.cisco.com [10.19.130.188]) by postoffice.cisco.com (8.8.7-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA19408; Tue, 25 Apr 2000 10:58:10 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@postoffice
Message-Id: <v04220806b52b86ceecfd@[10.19.130.188]>
In-Reply-To: <200004251722.KAA10059@zed.isi.edu>
References: <200004251722.KAA10059@zed.isi.edu>
Date: Tue, 25 Apr 2000 10:58:59 -0700
To: Bill Manning <bmanning@ISI.EDU>
From: Steve Deering <deering@cisco.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 10:22 AM -0700 4/25/00, Bill Manning wrote:
>Given the nature of trans-oceanic b/w vs. local b/w arguments I've heard
>over the years, I'd say that these delegations are esentially constrained
>to topological subregions and that for the most part, having the largest
>incumbent ISPs in each region announce the respective /8 would roughly 
>meet the IPv6, heirarchical aggregation argument.

A few counter-points:

	- As you know, I am a fan of geographic addressing (to provide a
	  real, scalable, user-friendly  solution to most of the multihoming
	  and renumbering problems), but as you also know, proposals to do
	  any sort of geographic routing have usually been met with
	  hostility and derision from the ISP community and others, because
	  of the topological constraints and interchange requirements it
	  would impose on the ISPs.  I welcome you to try, but don't get
	  your hopes up.

	- Are there not a large number of Class B addresses (and Class C
	  addresses, but maybe those have all been filtered out by now)
	  that were assigned before the registries were established, and
	  thus not aggregatable under the registry allocation prefixes?

	- Why are we talking about this?  Yes, you could adopt the same
	  or a similar address allocation/aggregation policy in IPv4 as
	  has been specified for IPv6, if you were starting all over again
	  with IPv4.  But so what?

Steve



From owner-ietf-outbound  Tue Apr 25 14:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA22272
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 14:50:04 -0400 (EDT)
Received: from shell.nominum.com (shell.nominum.com [204.152.187.59])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21124
	for <ietf@ietf.org>; Tue, 25 Apr 2000 14:01:29 -0400 (EDT)
Received: from nominum.com (shell.nominum.com [204.152.187.59])
	by shell.nominum.com (Postfix) with ESMTP
	id DA12531908; Tue, 25 Apr 2000 11:00:52 -0700 (PDT)
Message-ID: <3905DD53.ACE85C3B@nominum.com>
Date: Tue, 25 Apr 2000 11:00:51 -0700
From: "David R. Conrad" <David.Conrad@nominum.com>
Organization: Nominum, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: Steve Deering <deering@cisco.com>
Cc: Bill Manning <bmanning@ISI.EDU>,
        Thomas Narten <narten@hygro.adsl.duke.edu>, Sean Doran <smd@EBONE.NET>,
        ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
References: <200004251548.IAA08741@zed.isi.edu> <v04220801b52b78f8ac20@[10.19.130.188]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> At 8:48 AM -0700 4/25/00, Bill Manning wrote:
> >and this is different from only carrying the 253 usable /8 prefixes in
> >IPv4 how?
> 
> The set of customers who have addresses under a given IPv4 /8 prefix greater
> than 127 do not all aggregate into a single topological subregion (e.g., a
> single ISP), and therefore more granular routes must be widely disseminated
> to make those customers reachable.  That's the difference.

No.  This is a historical feature that IPv6 alleviates by being able to start
over with a clean slate.  You could (at least theoretically) emulate this in
v4.

The difference is that v6 gives you the option of significantly more TLAs than
v4 can ever have.  Of course, this isn't really a feature.

Rgds,
-drc



From owner-ietf-outbound  Tue Apr 25 15:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA22595
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 15:00:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21132
	for <ietf@ietf.org>; Tue, 25 Apr 2000 14:01:37 -0400 (EDT)
Received: from zed.isi.edu (zed.isi.edu [128.9.160.57])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA15970;
	Tue, 25 Apr 2000 11:01:28 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.8.7/8.8.6) id LAA10598;
	Tue, 25 Apr 2000 11:01:25 -0700 (PDT)
Message-Id: <200004251801.LAA10598@zed.isi.edu>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: moore@cs.utk.edu (Keith Moore)
Date: Tue, 25 Apr 2000 11:01:24 -0700 (PDT)
Cc: bmanning@ISI.EDU (Bill Manning), moore@cs.utk.edu (Keith Moore),
        egoshin@genesyslab.com (Leonid Yegoshin), asp@partan.com,
        ietf@ietf.org, smd@EBONE.NET
In-Reply-To: <200004251756.NAA01588@astro.cs.utk.edu> from "Keith Moore" at Apr 25, 2000 01:56:18 PM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

% 
%         So, of the 57,887 visable servers, 4314 are improperly configured 
%         in the visable in-addr.arpa. tree.  Thats 7.45% of the
%         servers being "not well maintained". 
% 
% a 92.55% reliability rate is not exactly impressive, at least not in
% a favorable sense.
% 
% it might be tolerable if a failure of the PTR lookup doesn't cause
% the application to fail. but after all, people are saying that DNS
% is good enough to serve as a means to map endpoint identifiers
% to realm-local addresses or routing goop.  if applications were 
% written to depend on DNS reverse lookups in order to get endpoint
% identifiers of their peers, they would only work as reliably as DNS,
% which isn't very good.
% 
% thanks for backing up my assertion with hard data.
% 
% Keith

	I've not backed your assertion. I've provided some data
	on the relative stability of the in-addr space. You've provided
	zero data on the efficacy of the forward delegations.
	
	Can you, with a straight face, claim the servers for the
	forward zones have a better reliability rate than the 92.55%
	that I have seen in the inverse tree?  If so, where is the
	data to back your assertion?  Or would the community like
	me to do for the forward tree what I have been doing for the
	inverse tree?

--bill



From owner-ietf-outbound  Tue Apr 25 15:15:04 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23298
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 15:14:47 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21233
	for <ietf@ietf.org>; Tue, 25 Apr 2000 14:07:08 -0400 (EDT)
Received: from contactdish (ASt-Lambert-101-2-165.abo.wanadoo.fr [193.251.59.165]) by atkielski.com (8.8.8) id UAA35339; Tue, 25 Apr 2000 20:07:05 +0200 (CEST)
Message-ID: <019201bfaee1$11a7fdc0$0a00000a@wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <200004250037.UAA03162@astro.cs.utk.edu>
Subject: Re: IPv6: Past mistakes repeated? 
Date: Tue, 25 Apr 2000 20:07:05 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

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

> I wasn't there, but I expect it would have sounded
> even more preposterous for someone to have said:
> "I'm absolutely positive that this Internet thing
> will reach to nearly everyone on the planet in a
> couple of decades, and therefore we need to make
> sure it has many times more than 32 bits of address
> space"  even though that's what eventually happened.

Well, I suppose it would depend on who was listening at the time.

> but just because it happened once doesn't mean that
> it will happen again.  we do well to learn from the
> past, but the past doesn't repeat itself exactly.

It often repeats itself approximately, though.  And I predict that, since
computer engineers have been underestimating capacity requirements for the
past fifty years, they'll do it yet again this time, and then this
conversation will be repeated a few decades from now.

> it often seems to be the case that if you design for
> the long term, what you get back isn't deployable
> in the near term because you've made the problem
> too hard.

I dunno.  I don't think that adding two more digits in the 1960s to year
fields would have really made any problems too hard.  It was more a question
of people wanting to do things the easy way.  And you can't say that it was
a technological barrier, because they were still making Y2K-related mistakes
into the 1980s and beyond.

Also, making things hard is probably the second-most-common mistake of
computer engineers.  First they don't plan for the required capacity, and
then they get so lost in ever-expanding features that they never actually
deploy anything close to what they put in the specs.  This is more a problem
for software engineers than hardware enginers, though; hardware engineers
are constrained by the harsh realities of actually having to build things
that work, whereas software engineers can throw together buggy
approximations and limp along with those indefinitely.

It seems that, in the early days of [insert any major computer development
here], engineers just try to get something to work--anything.  Simplest is
best.  They make the capacity mistake, but they don't make the
software-bloat mistake.  However, ten years later, when they come up with
the "new and improved" version of whatever major development is in question,
not only do they _still_ underestimate capacity (even with past mistakes in
this area staring them in the face), but they slide into the abyss of
featuritis and software bloat, spending their time writing and reviewing and
honing ever-more-complex specifications that nobody will be able to actually
code, debut, and implement before the observable universe reaches thermal
equilibrium.  Sometimes the result is a "temporary" implementation that
actually does the job (even though it still has the capacity problem) and
eventually becomes the permaennt standard, with the original specs being
relegated to dusty archives somewhere.

> ... the fact that we got a global Internet out of IPv4
> demonstrated to people that the concept was viable.

Absolutely.  We just underestimated capacity requirements, as usual.

> with IPv6 there's a considerable amount of breathing
> room for address space.

Why settle for a "considerable amount" (which time will show to be less
considerable than first believed) when a "nearly infinite amount" can be
designed into the project?

> address space shortage is just one of many possible problems.

True, but it is much better understood than many of the others.  It's a
classic capacity problem.  And, as in most cases of capacity problems, it's
more a nuisance than something fun to work on, so it doesn't get as much
attention as it probably deserves, compared to the rest.

> as long as the network keeps growing at exponential
> rates we are bound to run into some other major hurdle
> in a few years.

It won't continue to grow at exponential rates, but it will grow in a way
that doesn't match the addressing scheme, and the modes of its future growth
will probably be different from anything we can expect or foresee today.  So
the only option is to just allow for the unforeseeable, instead of trying to
predict and implement for it.

> we can either try to anticipate every possible hurdle
> that the Internet might face or we can concentrate on
> fixing the obvious problems now and wait for the later
> problems to make themselves apparent before trying
> to fix them.

Address space is a pretty obvious problem.  But as I've indicated, it's not
a very exciting one.

> on one hand you're saying that we cannot predict
> how addresses will be used ...

Yes.

> ... and on the other hand you're saying that you
> can definitely predict that we'll run out of IPv6
> addreses very soon.

No, I cannot predict that.  But consider this:  If a fixed-length address
field is used, and we exceed the capacity of the field, we have a serious
problem.  If a variable-length address field is used, we do not exceed the
capacity of the field, ever.  And if we never exceed the capacity of the
fixed-address field, well, we'll never exceed the capacity of the variable
field either, will we?  So a variable field is a win-win scenario--you don't
have to hope that you can predict the future--whereas the fixed-length field
is a win-lose scenario, in which you have to just hope that your predictions
are right.

> right now you're just pulling numbers out of thin air.

Yup.

> you have yet to give any basis whatsoever to make such
> a prediction credible.

It doesn't have to be credible, it just has to be possible.  The increment
of work required for a variable address space is not so very great, if it is
carefully thought through, and the potential benefits are enormous.  In
contrast, the increment of work required to fix exhaustion of a fixed
address space is staggering, and no amount of thinking things through will
prevent it, if and when the address space is exhausted.

> wrong. you need to make design assumptions about
> delegation points, and delegate portions of address
> space, even for variable length addresses of
> arbitrary size.

Any examples of this?  None come to my mind.  With a variable-length
address, you don't have to care how the entire space is allocated; you just
allocate the part that you are responsible for.  You do not need to predict
all future use with a variable-length address, whereas you _must_ predict
all future use with a fixed-length address.

> true, several of the class A blocks were already
> in use by then.  but initial allocations of IPv6
> space are much more conservative .

With a finite address space, they can never be conservative enough, unless
you discard the inherent routability of the addressing scheme (by assigning
consecutive addresses one at a time on individual demand, for example).
This is because you cannot predict future evolution of the allocation
criteria for the address space, and you cannot expand the space.

> no.  even with variable length addresses you want
> to exercise some discipline about how you allocate
> addresses.

Why?

> otherwise you end up some addresses being much
> longer than necessary, and this creates
> inefficiency and problems for routing.

In what cases would a variable-length address be longer than necessary?  I
can easily think of allocation schemes that would break the routability of a
fixed-length addressing scheme, but I don't see this problem with
variable-length addresses.

> nope.  even phone numbers are allocated by prefix blocks.

Not on a worldwide basis.  The U.S. treats its address space as fixed (which
is one reason why it is now in trouble), but this isn't really true for the
world overall.  If a call is routed to Vulgaria from the U.S., nobody in the
U.S. has to care how Vulgaria allocates its telephone numbers.

> you seem to be forgetting that routing hierarchy
> doesn't necessarily follow address hierarchy.

It can't, with fixed addresses.  At some point you have to allocate
non-contiguous addresses for the same routing destination, and then your
routing breaks.

With a variable-length address, this is not a problem.

> actually, no you can't.  because addresses still have
> to fit within the minimum size of a datagram on the network
> and have room left over for payload.

Don't use fixed datagrams sizes.  Or, if you must, implement within limits,
but leave indicators for exceptions to the limits, so that you don't have to
redo it all from scratch when you eventually exceed the limits.

> eventually I can buy.  but your predictions about the specific
> timeframe have no substance.

Time will tell.

> In 2030 (if I'm still doing this stuff) I will be much
> more concerned about the overflow of UNIX time in 2038.

Seems that UNIX wasn't engineered with the necessary capacity, either.

> variable length addresses with no constriants on
> address growth have their own set of routing problems.

Such as?

> but this same impossibility means that we do not
> know whether we should put today's energy into making
> variable length addresses work efficiently or into
> something else.

We should put today's energy into designing systems that make no irrevocable
assumptions about tomorrow.

> ... at least today it seems much easier to design fast
> routing hardware (or software) that looks at fixed offsets
> within a packet, than to design hardware or software that
> looks at variable offsets.

It's always easier.  However, you need to design something into the protocol
that tells the hardware when it is dealing with information outside the
envelope for which it was designed.  Then you can trap the exception and fix
things.  If you simply assume that there will never be any exceptions, you
get dramatic and dangerous failures when they finally come along.

> the biggest problem with IPv6 is the difficulty in
> getting it deployed.  and IPv6 has enough barriers to
> deployment already without variable length addresses
> making it harder to route than IPv4.

Maybe it is overambitious.

The easiest way to get it deployed, though, would be to have Microsoft ship
it as part of Windows.  In a year or two, everyone would be using it.  And
as long as this doesn't happen, it will never get deployed (at least not
anywhere near the desktop or home user).

> it depends on how many places have that length
> limitation wired-in.

You build them so that the wiring is easy to change and is not duplicated
any more times than absolutely necessary.

> no you can't, because you still need globally scoped
> addresses, and you have the incremental upgrade problem.

That doesn't seem to have stopped the world's telephone networks from
connecting to each other, and they had exactly this problem.

> if you change the root of the address space you have
> to do it for everything at once.

Only if everything already assumes that the root it sees is the only root
that exists, which is not a good way to design things.  In a telephone
system, the "root" can be my central office, or my area code, or my country
code, depending on how far I'm calling.

  -- Anthony



From owner-ietf-outbound  Tue Apr 25 15:20:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23422
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 15:20:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21418
	for <ietf@ietf.org>; Tue, 25 Apr 2000 14:16:30 -0400 (EDT)
Received: from contactdish (ASt-Lambert-101-2-165.abo.wanadoo.fr [193.251.59.165]) by atkielski.com (8.8.8) id UAA36510; Tue, 25 Apr 2000 20:16:27 +0200 (CEST)
Message-ID: <019d01bfaee2$61232b80$0a00000a@wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <20000424131939.7281335DC2@smb.research.att.com>           <00cb01bfae2a$381baae0$0a00000a@wanadoo.fr> <200004250139.e3P1dTB34670@black-ice.cc.vt.edu>
Subject: Re: IPv6: Past mistakes repeated? 
Date: Tue, 25 Apr 2000 20:16:28 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

From: <Valdis.Kletnieks@vt.edu>

> The problem is that the router guys wanted to fast-path
> the case of "no IP option field, routing entry in cache"
> so that after seeing only the first few bytes, they could
> know what interface to enqueue the outbound packet on
> *before the entire packet had even come in*.

But this would be even faster with a variable-length address than with a
fixed-length address.  You just read address bits until you find a match,
and ignore the rest.

> It's easy to do for an end-user workstation that's
> already bogged down by the bloat inherent in <insert
> your least favorite OS vendor here>.
>
> It's hard to do for something that's truly high-performance.

Something that is high-performance usually costs a lot more than an end-user
workstation, too, especially with the 90% gross margin that the vendor adds
to the hardware price.  It's reasonable to expect to get what you pay for.

  -- Anthony



From owner-ietf-outbound  Tue Apr 25 15:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23603
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 15:30:04 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21438
	for <ietf@ietf.org>; Tue, 25 Apr 2000 14:17:02 -0400 (EDT)
Received: from zed.isi.edu (zed.isi.edu [128.9.160.57])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA18042;
	Tue, 25 Apr 2000 11:17:00 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.8.7/8.8.6) id LAA10794;
	Tue, 25 Apr 2000 11:16:57 -0700 (PDT)
Message-Id: <200004251816.LAA10794@zed.isi.edu>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: deering@cisco.com (Steve Deering)
Date: Tue, 25 Apr 2000 11:16:56 -0700 (PDT)
Cc: bmanning@ISI.EDU (Bill Manning), ietf@ietf.org
In-Reply-To: <v04220806b52b86ceecfd@[10.19.130.188]> from "Steve Deering" at Apr 25, 2000 10:58:59 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

% 
% At 10:22 AM -0700 4/25/00, Bill Manning wrote:
% >Given the nature of trans-oceanic b/w vs. local b/w arguments I've heard
% >over the years, I'd say that these delegations are esentially constrained
% >to topological subregions and that for the most part, having the largest
% >incumbent ISPs in each region announce the respective /8 would roughly 
% >meet the IPv6, heirarchical aggregation argument.
% 
% A few counter-points:
% 
% 	- As you know, I am a fan of geographic addressing (to provide a
% 	  real, scalable, user-friendly  solution to most of the multihoming
% 	  and renumbering problems), but as you also know, proposals to do
% 	  any sort of geographic routing have usually been met with
% 	  hostility and derision from the ISP community and others, because
% 	  of the topological constraints and interchange requirements it
% 	  would impose on the ISPs.  I welcome you to try, but don't get
% 	  your hopes up.

	And why do you think that the ISP community and others will not
	meet the IPv6 routing proposal with anything less than the
	"hostility and derision" that came from the previous attempts
	to impose "topological constraints and interchange requirements"
	on them?

% 	- Are there not a large number of Class B addresses (and Class C
% 	  addresses, but maybe those have all been filtered out by now)
% 	  that were assigned before the registries were established, and
% 	  thus not aggregatable under the registry allocation prefixes?

	Yup, a bunch.

% 	- Why are we talking about this?  Yes, you could adopt the same
% 	  or a similar address allocation/aggregation policy in IPv4 as
% 	  has been specified for IPv6, if you were starting all over again
% 	  with IPv4.  But so what?

	Well, for two reasons:  a) IPv4 address delegation policy, since
	about 1996 has been done at a gross level, on continental bounds
	(e.g. the RIR model) so there is a rough alignment with the proposed
	IPv6 plan, at least as far as "modern" delegations are concerned.
	This is something that could be exploited for testing to see if the
	IPv6 delegation/aggregation plan is actually going to fly.
	b) We have IPv4 addresses as legacy environments that -RIGHT NOW-
	are showing problems with computing/maintaining state in a dynamic
	world. If we can "prove" the solution in the IPv4 world, then that
	would remove much of the "hostility & derision" when moving on to
	IPv6.  

	Two thoughts from here... :)

% 
% Steve
% 
% 


-- 
--bill



From owner-ietf-outbound  Tue Apr 25 15:40:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23938
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 15:40:04 -0400 (EDT)
Received: from leonid.genesyslab.com (pbinat33.genesyslab.com [209.233.177.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21520
	for <ietf@ietf.org>; Tue, 25 Apr 2000 14:21:16 -0400 (EDT)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id LAA21228
	for ietf@ietf.org; Tue, 25 Apr 2000 11:13:39 -0700
Date: Tue, 25 Apr 2000 11:13:39 -0700
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200004251813.LAA21228@leonid.genesyslab.com>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
X-Loop: ietf@ietf.org

It is a problem of lack well designed user-interface in DNS packet.
DNS from the beginning presents a tool more than a product.
Most of my friends who handles DNS create some PERL scripts or so.
Or try to use something from public domain but it is not adequate sometime.

  Also a miscommunication between IP provider and customer pays a big
toll: one my friend can't get a right NS address records
long time because it "illegally" cached at some providers point
and nobody knows where.

		       - Leonid Yegoshin.

-------------------------------------------------------------------
>From: Valdis.Kletnieks@vt.edu
>
>On Tue, 25 Apr 2000 08:18:20 PDT, Bill Manning said:
>>       The 2q2000 data for the in-addr tree shows 77402 unique
>>       servers answering for 693,337 zones.
>>       19515 servers blocked/refused data. Of the 57887 that
>>       answered, these are the numbers for improper configuration:
>>
>>       BAD_SERVER:     4278
>>       FORMERR:        8
>>       NXDOMAIN:       28
>>
>>       So, of the 57,887 visable servers, 4314 are improperly configured
>>       in the visable in-addr.arpa. tree.  Thats 7.45% of the
>>       servers being "not well maintained".  I know of no similar data
>
>Does "not well maintained" include the following:
>
>1) DNS server for the zone is originally configured correctly, and the
>first 20-30 hosts are entered with a proper A record and a PTR that matches.
>
>2) Clueful guy leaves, new DNS "goo-roo" takes over, and adds the next 300
>machines with just an A record, and no PTR matching.  The checks you make
>would show this as "well maintained", even though 90% of the hosts are broken
>with respect to PTR entries.
>
>Given that 7% of the sites can't get past step (1), I'm willing to bet that
>a lot MORE of the sites are accumulating cruft under step (2).
>

>From: Jeffrey Altman <jaltman@columbia.edu>
>> % DNS reverse lookup tables (PTR) are not as well maintained as forward
>> % lookup tables (A) so they're even less reliable.
>>
>>       This is an assertion that I've heard over the years
>>       and I've come to beleive (based on regular audits of
>>       the in-addr space) that this is an Internet equivalent
>>       of an urban legend.  I'd really like to see your backing
>>       data on this.
>
>This is hardly an urban legend.  Columbia University requires the
>use of tcpwrappers in Paranoid mode which requires that the forward
>and reverse lookups for an IP address in DNS match.  The Kermit
>Project is based at Columbia University and uses its systems for
>our FTP and HTTP access.  A week does not go by when we do not
>get complaints about people being unable to access our FTP server
>due to a failure of the forward and reverse to match.
>
>Just from the first 8 hours of logs today:
>
>  proxauth3-bb2.globalintranet.net != 212.234.59.254
>  hide193.nhs.uk != 195.107.47.193
>  marta-c-gw.caravan.ru != 212.24.53.234
>  su9127.eclipse.co.uk != 212.104.136.138
>
>Granted this is hardly a scientific study.  But we see this from
>approximately a dozen new addresses every day.



From owner-ietf-outbound  Tue Apr 25 15:50:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA24211
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 15:50:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21591
	for <ietf@ietf.org>; Tue, 25 Apr 2000 14:25:00 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA01702;
        Tue, 25 Apr 2000 14:24:26 -0400 (EDT)
Message-Id: <200004251824.OAA01702@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Bill Manning <bmanning@ISI.EDU>
cc: moore@cs.utk.edu (Keith Moore), egoshin@genesyslab.com (Leonid Yegoshin),
        asp@partan.com, ietf@ietf.org, smd@EBONE.NET
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Tue, 25 Apr 2000 11:01:24 PDT."
             <200004251801.LAA10598@zed.isi.edu> 
Date: Tue, 25 Apr 2000 14:24:26 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

>         I've not backed your assertion. I've provided some data
>         on the relative stability of the in-addr space. You've provided
>         zero data on the efficacy of the forward delegations.
>         
>         Can you, with a straight face, claim the servers for the
>         forward zones have a better reliability rate than the 92.55%
>         that I have seen in the inverse tree?  

actually, no.  I don't have hard data to back the assertion that the
reverse tree is less reliable than the forward tree... nor do I really
need to do that to make the point that DNS PTR lookup isn't reliable 
enough to allow DNS to be used to lookup connection endpoint identifiers.

Keith



From owner-ietf-outbound  Tue Apr 25 16:00:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA24451
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 16:00:04 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21886
	for <ietf@ietf.org>; Tue, 25 Apr 2000 14:37:47 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA01895;
        Tue, 25 Apr 2000 14:34:05 -0400 (EDT)
Message-Id: <200004251834.OAA01895@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: John Day <day@bbn.com>
cc: "Steven M. Bellovin" <smb@research.att.com>,
        Graham Klyne <GK@dial.pipex.com>,
        Richard Shockey <rshockey@ix.netcom.com>, ietf@ietf.org
Subject: Re: How many IP addresses? 
In-reply-to: Your message of "Tue, 25 Apr 2000 11:01:53 EDT."
             <v04011700b52b622f05c8@[171.78.140.250]> 
Date: Tue, 25 Apr 2000 14:34:05 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Doesn't this leave out a few pieces of data?  Given the current IPv6
> address format, which includes a globally unique 64 bit interface ID and 64
> bits of globally unique routing goop.  My calculation is that you only have
> 2^64 addresses to work with which leaves roughly 12 bits, maybe 14 to work
> with.

right.  but for privacy reasons you really don't want to transmit the 
64 bit interface ID around anyway.  so at some point you reclaim
those bits for use in routing.

Keith



From owner-ietf-outbound  Tue Apr 25 16:10:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA24763
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 16:10:04 -0400 (EDT)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22107
	for <ietf@ietf.org>; Tue, 25 Apr 2000 14:46:29 -0400 (EDT)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id LAA10898;
	Tue, 25 Apr 2000 11:39:35 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 25 Apr 2000 18:46:21 UT
Received: from porky (porky.ascend.com [192.207.23.83])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id LAA23442;
	Tue, 25 Apr 2000 11:46:21 -0700 (PDT)
Received: from ascend.com by ascend.com
Message-Id: <4.3.1.2.20000425114035.00bf24b0@porky>
X-Sender: mhold@porky
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 25 Apr 2000 11:47:54 -0700
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
From: Matt Holdrege <holdrege@lucent.com>
Subject: NAT->IPv6
Cc: ietf@ietf.org
In-Reply-To: <200004251655.MAA02714@ginger.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 12:55 PM 4/25/00 -0400, J. Noel Chiappa wrote:
>The basic key *architectural* problem with NAT (as opposed to all the
>mechanical problems like encrypted checksums, etc, some of which can be
>solved with variant mechanisms like RSIP), as made clear by Keith's comments,
>is that when you have a small number of external addresses being shared by a
>larger number of hosts behind some sort of "address-sharing" device, there's
>no permanent association between an address and a host. It's *that* that
>causes many of the worst problems - problems for which there *is* no good
>work-around (because the problem is fundamental in nature).
>
>Now, if you have a site which has more hosts than it can get external IPv4
>addresses for, then as long as there are considerable numbers of IPv4 hosts a
>site needs to interoperate with, *deploying IPv6 internally to the site does
>the site basically no good at all*.

I think we've been through all this already and we explored it deeply at 
the IAB Network Layer Workshop. One of the conclusions is that an IPv6 
network NAT'ed to the IPv4 Internet isn't any better than what we have 
today with
IPv4-NAT-IPv4, yet it will allow the given network to move to IPv6 in hopes 
of someday connecting to other IPv6 networks without using NAT.

So if you are NAT'd to the public Internet today, you shouldn't have a 
problem with converting internally to IPv6. At least from an architectural 
sense. :)



From owner-ietf-outbound  Tue Apr 25 16:20:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA25004
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 16:20:03 -0400 (EDT)
Received: from postoffice.cisco.com (postoffice.cisco.com [171.69.198.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22328
	for <ietf@ietf.org>; Tue, 25 Apr 2000 14:53:03 -0400 (EDT)
Received: from [10.19.130.188] (deering-dsl3.cisco.com [10.19.130.188]) by postoffice.cisco.com (8.8.7-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id LAA29154; Tue, 25 Apr 2000 11:51:54 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@postoffice
Message-Id: <v04220809b52b95dc772a@[10.19.130.188]>
In-Reply-To: <200004251816.LAA10794@zed.isi.edu>
References: <200004251816.LAA10794@zed.isi.edu>
Date: Tue, 25 Apr 2000 11:52:42 -0700
To: Bill Manning <bmanning@ISI.EDU>
From: Steve Deering <deering@cisco.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 11:16 AM -0700 4/25/00, Bill Manning wrote:
>	And why do you think that the ISP community and others will not
>	meet the IPv6 routing proposal with anything less than the
>	"hostility and derision" that came from the previous attempts
>	to impose "topological constraints and interchange requirements"
>	on them?

I was talking about the requirements of geographic addressing and routing.
The IPv6 addressing and routing plan does not impose those requirements.
Rather, the IPv6 addressing and routing plan is just the CIDR plan that
is being used today by that community for IPv4, with some policy proposals
to attempt to limit the number of prefixes that must be globally advertised,
something that many in that community have said over and over again is of
vital importance.

(Of course, some will respond with hostility and derision to any plan,
even if it's exactly what they would argue for, if it comes in IPv6
clothing.)

>
>% 	- Are there not a large number of Class B addresses (and Class C
>% 	  addresses, but maybe those have all been filtered out by now)
>% 	  that were assigned before the registries were established, and
>% 	  thus not aggregatable under the registry allocation prefixes?
>
>	Yup, a bunch.

OK, so because of that, just changing the IPv4 Internet today to advertise
only /8s globally would not be functionally equivalent to just advertising
IPv6 TLAs, which was your original question.

>% 	- Why are we talking about this?  Yes, you could adopt the same
>% 	  or a similar address allocation/aggregation policy in IPv4 as
>% 	  has been specified for IPv6, if you were starting all over again
>% 	  with IPv4.  But so what?
>
>	Well, for two reasons:  a) IPv4 address delegation policy, since
>	about 1996 has been done at a gross level, on continental bounds
>	(e.g. the RIR model) so there is a rough alignment with the proposed
>	IPv6 plan, at least as far as "modern" delegations are concerned.
>	This is something that could be exploited for testing to see if the
>	IPv6 delegation/aggregation plan is actually going to fly.

Huh?  We have been "testing" that for some years in the IPv4 world, and
we have adopted it for IPv6.  What further testing do you have in mind,
and in what salient way do you think the IPv6 delegation/aggregation plan
is different?

>	b) We have IPv4 addresses as legacy environments that -RIGHT NOW-
>	are showing problems with computing/maintaining state in a dynamic
>	world. If we can "prove" the solution in the IPv4 world, then that
>	would remove much of the "hostility & derision" when moving on to
>	IPv6.

Huh?  You want to stop routing to IPv4 prefixes that don't aggregate under
/8s in order to "prove" that we shouldn't allocate such prefixes in IPv6???

Steve



From owner-ietf-outbound  Tue Apr 25 16:30:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA25190
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 16:30:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22897
	for <ietf@ietf.org>; Tue, 25 Apr 2000 15:05:18 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id PAA03220;
	Tue, 25 Apr 2000 15:05:11 -0400
Date: Tue, 25 Apr 2000 15:05:11 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200004251905.PAA03220@ginger.lcs.mit.edu>
To: holdrege@lucent.com, ietf@ietf.org
Subject: Re:  NAT->IPv6
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

    > From: Matt Holdrege <holdrege@lucent.com>

    >> The basic key *architectural* problem with NAT ... is that when you
    >> have a small number of external addresses being shared by a larger
    >> number of hosts behind some sort of "address-sharing" device, there's
    >> no permanent association between an address and a host. It's *that*
    >> that causes many of the worst problems - problems for which there *is*
    >> no good work-around (because the problem is fundamental in nature).
    >> ... if you have a site which has more hosts than it can get external
    >> IPv4 addresses for .. *deploying IPv6 internally to the site does the
    >> site basically no good at all*.

    > we've been through all this already ... at the IAB Network Layer
    > Workshop. One of the conclusions is that an IPv6 network NAT'ed to
    > the IPv4 Internet isn't any better than what we have today with
    > IPv4-NAT-IPv4

Well, my statement is broader than that. It says that *any* IPv6<->IPv4
interoperability mechanism is going to have the same fundamental problems as
IPv4<->IPv4 NAT. I think that's a pretty powerful statement, one that puts a
hard ceiling on what one can hope to accomplish (in any moderate timeframe)
with *any* alternative to IPv4<->IPv4 NAT (including IPv4 RSIP).


    > So if you are NAT'd to the public Internet today, you shouldn't have
    > a problem with converting internally to IPv6. At least from an
    > architectural sense. :)

Sure, you're going to have basically the same service externally, if you are
using IPv6 internally, as you are if you are using IPv4 internally.

So, you're the CIO for Foondoggle Corp, and you're trying to figure out
whether to spend any of your Q3 funds on IPv6 conversion. Let's see, benefits
are not very many (autoconfig may be the best one), and the cost is
substantial. OK, let's put it off till the next quarter. Go back to step 1.

	Noel



From owner-ietf-outbound  Tue Apr 25 16:40:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA25472
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 16:40:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22911
	for <ietf@ietf.org>; Tue, 25 Apr 2000 15:05:59 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA02185;
        Tue, 25 Apr 2000 15:05:27 -0400 (EDT)
Message-Id: <200004251905.PAA02185@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Tue, 25 Apr 2000 12:55:32 EDT."
             <200004251655.MAA02714@ginger.lcs.mit.edu> 
Date: Tue, 25 Apr 2000 15:05:27 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Now, if you have a site which has more hosts than it can get external IPv4
> addresses for, then as long as there are considerable numbers of IPv4 hosts a
> site needs to interoperate with, *deploying IPv6 internally to the site does
> the site basically no good at all*. Why?

this sounds like a slight exaggeration, but I do think that the main 
incentive to deploy v6 will come from the need to communicate with global 
addresses to points *outside* of folks' internal networks.

it doesn't follow that deploying IPv6 internally to a site does no good
at all - it will of course do some good if the site has applications
on internal hosts that need to communicate with external hosts using 
global addresses.  and of course having v6 deployed internally would 
allow the site to run those same applications interally without any 
configuration changes.

but if you're trying to make the point that there's little purpose in
having your own IPv6 island - I think that's basically right.
 
Keith



From owner-ietf-outbound  Tue Apr 25 16:50:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA25687
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 16:50:03 -0400 (EDT)
Received: from shell.nominum.com (shell.nominum.com [204.152.187.59])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23440
	for <ietf@ietf.org>; Tue, 25 Apr 2000 15:20:21 -0400 (EDT)
Received: from nominum.com (shell.nominum.com [204.152.187.59])
	by shell.nominum.com (Postfix) with ESMTP
	id 3B7E531906; Tue, 25 Apr 2000 12:19:50 -0700 (PDT)
Message-ID: <3905EFD5.47AA5BFB@nominum.com>
Date: Tue, 25 Apr 2000 12:19:49 -0700
From: "David R. Conrad" <David.Conrad@nominum.com>
Organization: Nominum, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
Cc: Bill Manning <bmanning@ISI.EDU>, Leonid Yegoshin <egoshin@genesyslab.com>,
        asp@partan.com, ietf@ietf.org, smd@EBONE.NET
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
References: <200004251756.NAA01588@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Keith,

> a 92.55% reliability rate is not exactly impressive, at least not in
> a favorable sense.
> 
> it might be tolerable if a failure of the PTR lookup doesn't cause
> the application to fail. 

If people's livelihood depends on something, they're more likely to insure it
actually works.  Very little depends on PTR records doing anything (with a
relatively few exceptions of sites that configure it otherwise).  The fact
that Bill's getting a 92.55% reliability figure for something that the vast
majority of people use to get something other than IP addresses in logfiles is
actually surprisingly good.

> if applications were
> written to depend on DNS reverse lookups in order to get endpoint
> identifiers of their peers, they would only work as reliably as DNS,
> which isn't very good.

If it "isn't very good", try using the Internet without it for a bit.

In your view, what is it in the DNS protocol(s) that results in a lack of
reliability?

Rgds,
-drc



From owner-ietf-outbound  Tue Apr 25 17:00:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA25889
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 17:00:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23579
	for <ietf@ietf.org>; Tue, 25 Apr 2000 15:29:12 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3PJShB30070;
	Tue, 25 Apr 2000 15:28:43 -0400
Message-Id: <200004251928.e3PJShB30070@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Anthony Atkielski <anthony@atkielski.com>
cc: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-reply-to: Your message of "Tue, 25 Apr 2000 20:07:05 +0200."
             <019201bfaee1$11a7fdc0$0a00000a@wanadoo.fr> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200004250037.UAA03162@astro.cs.utk.edu>
            <019201bfaee1$11a7fdc0$0a00000a@wanadoo.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 25 Apr 2000 15:28:35 -0400
X-Loop: ietf@ietf.org

On Tue, 25 Apr 2000 20:07:05 +0200, Anthony Atkielski <anthony@atkielski.com>  said:
> I dunno.  I don't think that adding two more digits in the 1960s to year
> fields would have really made any problems too hard.  It was more a question

You never had to fit 2 more bytes onto a punch card, did you?

I'm not being facetious here - you had 80 columns and that was IT.

Some databases were laid out with (for instance) exactly 3 6144-byte
records per physical track on the disk.  Adding 2 more digits would have
dropped it to 2 per track, with a lot of wasted space - and forcing not
only the consumption of 50% more disk, but also re-doing any indexing (see
below for a related story).

> of people wanting to do things the easy way.  And you can't say that it was
> a technological barrier, because they were still making Y2K-related mistakes
> into the 1980s and beyond.

When I got to VT in 1989, chargeback accounts on the IBM mainframe
were of the form 'nxxxy'. n was a 0-9 type code, and xxx was a 3-digit
hex number and y was a single digit 0-7.  Turns out that the xxx and y
were the track humber and record number when the database lived on an
IBM3330 disk drive.  The database had since been moved to 3350, and
then to 3380/3390.  However, it proved to be just too much of a
challenge to track down ALL the places those numbers were used and fix
them.  Not only does the database itself need to be redone, but you
get to re-do all the userids to give them the new numbers, find ALL
the JCL that has chargeback accounting information, fix all the files
on secretary's PCs that have a professor-to-account lists.. the list
goes on and on....

And we're a relatively small shop - our machine room is only 10K sqare feet..

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Tue Apr 25 17:10:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA26109
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 17:10:03 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23697
	for <ietf@ietf.org>; Tue, 25 Apr 2000 15:31:10 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA02332;
        Tue, 25 Apr 2000 15:30:29 -0400 (EDT)
Message-Id: <200004251930.PAA02332@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "David R. Conrad" <David.Conrad@nominum.com>
cc: Keith Moore <moore@cs.utk.edu>, Bill Manning <bmanning@ISI.EDU>,
        Leonid Yegoshin <egoshin@genesyslab.com>, asp@partan.com,
        ietf@ietf.org, smd@EBONE.NET
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Tue, 25 Apr 2000 12:19:49 PDT."
             <3905EFD5.47AA5BFB@nominum.com> 
Date: Tue, 25 Apr 2000 15:30:29 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> If people's livelihood depends on something, they're more likely to insure 
> it actually works.  

that's a good point.  but it's one thing to make sure that DNS mappings
for "major" services are correct, and quite another to make sure that 
the DNS mappings are correct in both directions for every single host.

even the DNS names for major services may not be well maintained.  
at one time I did a survey of the reasons for mail bounces
for one of my larger mailing lists.  about half of the mail bounces
seemed to be due to configuration errors.  about half of those
seemed to be due to DNS configuration errors - e.g. MX records pointing
to the wrong host, zone replicas not being kept in sync, zone
replicas which were different but with the same serial number.

> In your view, what is it in the DNS protocol(s) that results in a lack of
> reliability?

the reliability problems are mostly not the protocol...though the protocol 
does have limitations if you want to use it (as some have proposed) to 
support host or process mobility.  and in the face of even moderate 
packet losses DNS queries can take a very long time. 

mainly it's the fact that DNS is maintained as a separate entity.
if you really want it to be in sync with reality, you need some
mechanisms to ensure that updates happen automagically, and/or that
configuration errors are automatically and quickly detected and
the information about the error gets to the person who can fix it.

Keith



From owner-ietf-outbound  Tue Apr 25 17:20:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA26318
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 17:20:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24006
	for <ietf@ietf.org>; Tue, 25 Apr 2000 15:42:33 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id PAA03466;
	Tue, 25 Apr 2000 15:42:31 -0400
Date: Tue, 25 Apr 2000 15:42:31 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200004251942.PAA03466@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: jnc@ginger.lcs.mit.edu, moore@cs.utk.edu
X-Loop: ietf@ietf.org

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

IPv6's claimed big advantage - a bigger address space - turns out not to be an
advantage at all - at least in any stage much short of completely deployment.

IPv6 deployment is going to have to be driven by IPv6's *other* features, and
when you take bigger addresses out of the cost/benefit ration, I'm even more
dubious that the features that are left (autoconfiguration, etc) outweigh all
the costs and risks of IPv6 conversion.

It seems that you can postulate whatever level of IPv6 deployment you like (a
long stretch in itself, but just for the sake of argument, let's make it) -
5%, 10%, whatever - and there's still no mechanism to drive further
deployment.

Here's why:

    >> if you have a site which has more hosts than it can get external IPv4
    >> addresses for, then as long as there are considerable numbers of IPv4
    >> hosts a site needs to interoperate with, *deploying IPv6 internally to
    >> the site does the site basically no good at all*.

    > I do think that the main incentive to deploy v6 will come from the need
    > to communicate with global addresses to points *outside* of folks'
    > internal networks.

Huh?

If those outside sites are running IPv4, deployment of IPv6 does the people
who deployed it basically no good at all over IPv4 NAT - because the
fundamental problem (of not having enough external addresses) is the same,
regardless of whether the internal protocol is IPv4 or IPv6.

Thus, the problems caused by that limitation (many of which you so well
articulated in a previous message, such as the need to go through a
rendezvous to set up translation state) will also be the same, regardless of
whether the internal protocol is IPv4 or IPv6.


    > deploying IPv6 internally .. will of course do some good if the site
    > has applications on internal hosts that need to communicate with
    > external hosts using global addresses. if you're .. point [is] that
    > there's little purpose in having your own IPv6 island

Deployment won't do any good if the people it's trying to communicate with
externally are running IPv4 - and I *don't* include only the cases where
there's a local island of IPv6. Here's the logic:

As long as a substantial portion of the Internet is running IPv4 only, any
site is going to have to have some mechanism to communicate with the IPv4
portion of the Internet. It may not be quite as good as native IPv6-IPv6 -
*but it has to be OK, or the company is toast*. As an important corollary,
there may be an incremental improvement in functionality with a pure
IPv6<->IPv6 mode, but that increment is inevitably going to be minimal.

And my new point is that whether the site is running IPv4 or IPv6 internally,
it won't make any big difference to how well that IPv4 interoperation
mechanism operates, since the fundamental problem is the same.

So, if i) a company has an acceptable mechanism to interoperate, ii) they
won't see any big improvement from IPv6<->IPv6 operation, and iii) there's no
advantage in the IPv4 ineroperation mechanism to be gained by deployment of
IPv6 internally - then where's the incentive to deploy?

	Noel



From owner-ietf-outbound  Tue Apr 25 17:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA26517
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 17:30:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24255
	for <ietf@ietf.org>; Tue, 25 Apr 2000 15:52:24 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3PJq6B34624;
	Tue, 25 Apr 2000 15:52:06 -0400
Message-Id: <200004251952.e3PJq6B34624@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Anthony Atkielski <anthony@atkielski.com>
cc: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-reply-to: Your message of "Tue, 25 Apr 2000 20:16:28 +0200."
             <019d01bfaee2$61232b80$0a00000a@wanadoo.fr> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <20000424131939.7281335DC2@smb.research.att.com> <00cb01bfae2a$381baae0$0a00000a@wanadoo.fr> <200004250139.e3P1dTB34670@black-ice.cc.vt.edu>
            <019d01bfaee2$61232b80$0a00000a@wanadoo.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 25 Apr 2000 15:52:05 -0400
X-Loop: ietf@ietf.org

On Tue, 25 Apr 2000 20:16:28 +0200, Anthony Atkielski <anthony@atkielski.com>  said:
> But this would be even faster with a variable-length address than with a
> fixed-length address.  You just read address bits until you find a match,
> and ignore the rest.

Umm.. No.

"until you find a match" works totally differently in the silicon world
than for programming.

Today's homework assignment:  Using 7400-series logic chips, design and
implement an 8-bit adder (you may ignore the carry out of the high bit).
For bonus credit - implement an arbitrary-length adder, the number of bits
being specified in-band (do NOT use the signalling bits as input to the adder).

When you understand the difference, enlightenment will soon follow.

(And yes, I thought variable-length was a Cool Idea too, until one of the
Cisco crew made the case for router convenience...)

Somebody with a better memory than I can point at the big-internet archives,
where this was all thrashed out the FIRST time...


-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Tue Apr 25 17:40:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA26868
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 17:40:03 -0400 (EDT)
Received: from baboon.aciri.org (baboon.aciri.org [192.150.187.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24829
	for <ietf@ietf.org>; Tue, 25 Apr 2000 16:11:39 -0400 (EDT)
Received: (from pfrancis@localhost)
	by baboon.aciri.org (8.9.3/8.9.3) id NAA40378;
	Tue, 25 Apr 2000 13:11:36 -0700 (PDT)
	(envelope-from pfrancis)
Date: Tue, 25 Apr 2000 13:11:36 -0700 (PDT)
From: Paul Francis <pfrancis@aciri.org>
Message-Id: <200004252011.NAA40378@baboon.aciri.org>
To: narten@hygro.adsl.duke.edu, smd@EBONE.NET
Subject: multihoming (was Re: draft-ietf-nat-protocol-complications-02.txt)
Cc: ietf@ietf.org
In-Reply-To: <200004251448.KAA00848@hygro.adsl.duke.edu>
X-Loop: ietf@ietf.org

>  
>  Sean Doran <smd@ebone.net> writes:
>  
>  > Unfortunately, IPv6's current addressing architecture makes it very
>  > difficult to do this sort of traditional multihoming if one is not
>  > a TLA.
>  
>  This is not true. IPv6's TLA scheme has as its primary goal placing an
>  upper bound on the number of routing prefixes that are needed in the
>  
>  That doesn't mean that all or even any of these routes will be
>  optimal. An individual provider, may, maintain longer prefixes for
>  selected destinations in order to provide better contectivity, say, to
>  those willing to pay. Thus, traditional multihoming is still quite
>  possible, assuming the various ISPs that need to handle the routes
>  agree to do so. But the goal is to make such routes exceptions that
>  are value-add rather than are a fundamental requirement in order to
>  insure global reachability for all.
>  

Sean said that traditional multihoming would be "very difficult".

You replied that "This is not true" (which I take to mean
that multihoming is not very difficult), and then go on to describe
something that sounds very difficult to me (maintain longer prefixes,
make multihomed customers pay for it, get the ISPs to agree to
handle such longer prefixes).  You say that "multihoming is still
quite posible", but nobody said that it was impossible, just
difficult.  For me, your statement certainly reinforces the idea
that multihoming in IPv6 is indeed very difficult.

I read your statement as follows:

    IPv6 does not solve the multihoming problem.  Instead, it tries
    to minimize the damage by:
    
    1. discouraging the use of multihoming, primarily may making
    multihomed customers pay more for it.
    2. forcing paths to multihomed sites to be less efficient (at
    least for all but one of the ISP connection points) and or,
    3. limiting the regions of the internet for which multihoming
    is effective for a given customer.

Is this an accurate representation?

PF



From owner-ietf-outbound  Tue Apr 25 17:50:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA27047
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 17:50:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25053
	for <ietf@ietf.org>; Tue, 25 Apr 2000 16:22:09 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA02502;
        Tue, 25 Apr 2000 16:18:47 -0400 (EDT)
Message-Id: <200004252018.QAA02502@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: ietf@ietf.org, moore@cs.utk.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Tue, 25 Apr 2000 15:42:31 EDT."
             <200004251942.PAA03466@ginger.lcs.mit.edu> 
Date: Tue, 25 Apr 2000 16:18:47 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> IPv6's claimed big advantage - a bigger address space - turns out not to be an
> advantage at all - at least in any stage much short of completely deployment.

that's an exaggeration.  if you have an app that needs IPv6, you don't 
need complete deployment of IPv6 throughout the whole network to use
that app.  you just need for the hosts that want to support that app 
to have IPv6 (on many hosts the IPv6 stack can be installed at the 
same time as the app itself), and you need a way to route IPv6 packets 
between those hosts.  

and as long as a site has one external public IPv4 address, 6to4 and 
6over4 go a long way toward providing the ability for all of the 
internal hosts at that site to run IPv6 if their local stack supports it.

of course, if the backbone supports v6 natively, that's a nice optimization.

>     >> if you have a site which has more hosts than it can get external IPv4
>     >> addresses for, then as long as there are considerable numbers of IPv4
>     >> hosts a site needs to interoperate with, *deploying IPv6 internally to
>     >> the site does the site basically no good at all*.
> 
>     > I do think that the main incentive to deploy v6 will come from the need
>     > to communicate with global addresses to points *outside* of folks'
>     > internal networks.
> 
> Huh?
> 
> If those outside sites are running IPv4, deployment of IPv6 does the people
> who deployed it basically no good at all over IPv4 NAT - because the
> fundamental problem (of not having enough external addresses) is the same,
> regardless of whether the internal protocol is IPv4 or IPv6.

I don't see what you're getting at.  the outside sites may be running v4 
with a limited number of external addresses - not enough addresses for 
each host.  but if they are running v6 they will have plenty of external 
addresses.
 
> Thus, the problems caused by that limitation (many of which you so well
> articulated in a previous message, such as the need to go through a
> rendezvous to set up translation state) will also be the same, regardless of
> whether the internal protocol is IPv4 or IPv6.

with 6to4 the mapping is algorithmic so there's no need to go through
a rendezvous, or do a network query, to set up translation state.

>     > deploying IPv6 internally .. will of course do some good if the site
>     > has applications on internal hosts that need to communicate with
>     > external hosts using global addresses. if you're .. point [is] that
>     > there's little purpose in having your own IPv6 island
> 
> Deployment won't do any good if the people it's trying to communicate with
> externally are running IPv4 

if the remote sites are *only* running IPv4, having v6 locally won't help
much.  but the fact that they're running v4 makes it easy for them to
bootstrap to v6 by using 6to4.

but it's generally true that if you're talking between a v6-only and 
v4-only host you have to accept the limitations of NAT.

> So, if i) a company has an acceptable mechanism to interoperate, ii) they
> won't see any big improvement from IPv6<->IPv6 operation, and iii) there's no
> advantage in the IPv4 ineroperation mechanism to be gained by deployment of
> IPv6 internally - then where's the incentive to deploy?

as I see it the incentives to deploy v6 include the following:

a) ability to run applications that won't work over IPv4 in practice
   due to a shortage of addresses and the resulting inability to
   use addresses as connection endpoint identifiers; ability to
   write distributed apps that scale better than hub-and-spoke apps.
   (distributed games, conferencing systems, instant messaging,
    high performance distributed computations)

b) ability to deploy new networks which can directly address large
   numbers of devices, where this would be infeasible using IPv4
   (might include traditional Internet in emerging areas of the globe,
   IP-enabled cellphones and mobile devices, and new networks intended 
   to support instrumentation/telemetery - e.g. monitoring of power meters)

c) ability to individually and remotely address every device in a 
   network which is currently accessible only via a NAT or not at all -
   i.e. change a NAT-based client-only LAN into a LAN which can 
   potentially support client and/or server operation from every host.
   doing this gives you the ability to support new applications
   or support existing applications more efficiently
   (internet phone, fax to the desktop, instant messaging, etc.);
   it also allows you to do new things with your network
   (e.g. for home networks; be able to program or diagnose your vcr 
   remotely) 

d) ability to communicate with the new networks in (c) and (d)
   from the rest of the Internet.

e) ability to deploy new applications without installing a new ALG
   in the NAT....6to4 becomes the universal ALG.

if the Internet were going to stay just like it is today -
email and web - there would be no need to deploy v6.  but the
Internet won't stay like it is today.  there are too many
useful things that can be done with the Internet (and
lots of money to be made in the process) if it had the ability to 
directly address every host.  so people are going to provide that
ability, and the most obvious way to do it is to use IPv6.

Keith



From owner-ietf-outbound  Tue Apr 25 18:00:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA27253
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 18:00:03 -0400 (EDT)
Received: from keith.fenris.net (keith.fenris.net [158.222.0.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25065
	for <ietf@ietf.org>; Tue, 25 Apr 2000 16:23:40 -0400 (EDT)
Received: from localhost (brian@localhost)
	by keith.fenris.net (8.9.3/8.9.3) with ESMTP id NAA05875;
	Tue, 25 Apr 2000 13:23:43 -0700 (PDT)
Date: Tue, 25 Apr 2000 13:23:43 -0700 (PDT)
From: Brian Lloyd <brian@lloyd.com>
X-Sender: brian@keith.fenris.net
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <200004251655.MAA02714@ginger.lcs.mit.edu>
Message-ID: <Pine.GSO.4.21.0004251231030.5266-100000@keith.fenris.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Tue, 25 Apr 2000, J. Noel Chiappa wrote:

>     > From: Brian Lloyd <brian@lloyd.com>
> 
> I was thinking about your message, and something from my exchanges
> with Keith Moore suddenly popped into my head with great clarity. I
> think it's the answer to your question immediately below - and it has
> some very grave consequences.
>
> ...
> 
>     > whatever happened to IPv6? 128 bit addresses would certainly allow us
>     > to continue using IP addresses as endpoint identifiers thus eliminating
>     > the need for NAT. It seems that this is a more reasonable solution than
>     > trying to make NAT work under all circumstances.
> 
> The basic key *architectural* problem with NAT (as opposed to all the
> mechanical problems like encrypted checksums, etc, some of which can
> be solved with variant mechanisms like RSIP), as made clear by Keith's
> comments, is that when you have a small number of external addresses
> being shared by a larger number of hosts behind some sort of
> "address-sharing" device, there's no permanent association between an
> address and a host. It's *that* that causes many of the worst problems
> - problems for which there *is* no good work-around (because the
> problem is fundamental in nature).

Right.  NAT, or any other technology that breaks the static relationship
between identifiers and the hosts they identify, is basically flawed.  
You can never again count on the address/identifier as a means to identify
a given host.  I saw that one coming back in '92 and managed to scrounge a
class-B for my little grassroots ISP so that I wouldn't have to deal with
that problem nor would my customers.  I am sooooo glad I did that.  It is
still paying dividends to me today.

> Now, if you have a site which has more hosts than it can get external
> IPv4 addresses for, then as long as there are considerable numbers of
> IPv4 hosts a site needs to interoperate with, *deploying IPv6
> internally to the site does the site basically no good at all*. Why?

That seems obvious to me.  IPv6 over IPv4 is NAT all over again.  Once
again you are trying to cram 100 kg of routing drek into a 5 kg bag.

> Because for interactions with those external IPv4 hosts (who will be
> the vast majority of the hosts one wants to talk to, in the initial
> stages of deployment), *you have exactly the same architectural
> problem*. No matter what IPv6<->IPv4 interoperability mechanism you
> use, you still have that same *fundamental* problem - no permanent
> association between a host and an address (in this case, the IPv4
> address that it *has* to use to communicate with an IPv4-only host).

Right.  But it is safe to go the other way ... oops, no it's not.  I still
have only 32 bits locally to identify all those remote hosts.  Sure I can
give every local host a virtual IPv6 address by making the 'v4 address the
low order 32 bits of the 'v6 address but that doesn't help my local host
find a remote host across the 'v6 network.

But it does seem that we could begin deploying 'v6 in the backbone
piecemeal while leaving the high order 96 bits zero'd out.  Sun, Linux,
MacOS, and Win-whatever add IPv6 to their stacks as part of their ongoing
upgrade and you have the means for a relatively peaceful transition.

> When one looks at the overall business/economic case for deploying
> IPv6, in the light of this, the results are fairly devastating - and
> explain perfectly what we've been seeing for the last couple of years
> (rapid increase in the number of NAT boxes, and basically no traction
> for IPv6).

There are hard decisions to be made.  You can begin do it now for $$$ or
you can do it later for $$$$$$.  What is the future cost and what is the
future value of money?  It seems to me that the business folk can
understand that equation.

> A site considering deploying IPv6 is in one of two cases: it already
> has enough IPv4 addresses, or it doesn't. In the foremer case, what's
> the upside to deploying IPv6? Autoconfiguration, etc aren't enough to
> outweigh all the costs of switching (to software which is less
> available, less tested, less tuned, etc).

It may be cheaper to deploy IPv6 now because I don't have as many hosts
now as I will have to convert in the future.

> In the latter case, it's equally as bad: they are going to have to
> struggle with the problems inherent in IPv4-address-sharing technology
> whether they go with IPv6 or not, and again, the remaining advantages
> of IPv6 (autoconfig, etc) are outweighed by the costs.
> 
> I'm still sorting through the implications from this, trying to put
> them all with equal clarity, but one thing that does seem clear is
> that this kind of upgrade model is economically unworkable in the
> current large-scale Internet. Exactly what will work is something that
> needs to be pondered for a while.

What works is a function of the motivation of the people involved.  What I
am about to say will undoubtedly violate the libertarian and anarchistic
bent of most of the people I have known who are involved with the IETF
(myself included).  That said, sometimes government intervention can be
useful.  If 'v6 is legally mandated, it will get done.  This approach has
driven the development of more efficient and cleaner automobiles.  This
has driven a cleaner environment.  Moving from IPv4 to IPv6 has all the
flavor of an EPA clean-up effort.  It is expensive, nasty work that
doesn't buy you anything in the short run but it may keep your progeny
from dying in a generation.

> One possible lesson is that we need think about how any new stuff is
> going to make peoples lives significantly easier overall as soon as
> they start to deploy it, because without that, probably very little is
> going to get done.

Sometimes you just have to do something whether it is easy or not.  As I
said, the endpoint problem will solve itself in time if IPv6 is an itegral
part of Solaris, Linux, MacOS, and Win-whatever.  People eventually
upgrade their hardware and their operating software.  They already pay to
do that whether or not IPv6 is in there, hence my comment about M$
possibly making this easier. (Gawd, I can't believe that I, a rabid
M$-phobe, am saying this.)  Likewise, if Cisco makes IPv6 an integral part
of IOS, the other router mfgrs will follow suit because they want to be
competitive.  The key point is that the money for upgrading is already
there, we just have to "hide the hat" and see to it that IPv6 is part of
that upgrade.  Once that happens all the pieces are in place to do the
transition.  The only question is how to handle coexistance of IPv4 and
IPv6.  The transition plan is really, really important.

I don't know about you but I just can't see applying band-aids forever.  
We can apply the efforts of the many bright people of this group to
solving the problem or we can fragment and continue to work on band-aids
until band-aids no longer work and the cost of transition is astronomical.

But I remember that old saying, "There is never time or money to do it
right, but there is always time and money to do it over."  I think I will
go out and ride the horses for a bit and then go flying.  That brings me
comfort and pleasure where watching people perpetuate stupidity does not.  
Whether or not this gets done right now or later, it will eventually get
done, and my email will manage to get through somehow.

Brian Lloyd
brian@lloyd.com
+1.530.676.6513



From owner-ietf-outbound  Tue Apr 25 18:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA27464
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 18:10:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25325
	for <ietf@ietf.org>; Tue, 25 Apr 2000 16:32:05 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id QAA03684;
	Tue, 25 Apr 2000 16:32:04 -0400
Date: Tue, 25 Apr 2000 16:32:04 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200004252032.QAA03684@ginger.lcs.mit.edu>
To: ietf@ietf.org, moore@cs.utk.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

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

    > I don't see what you're getting at. the outside sites may be running v4
    > with a limited number of external addresses ... if they are running v6
    > they will have plenty of external addresses.

Not external *IPv4* addresses, they won't - which is what kind of addresses
they need to communicate with other IPv4 sites.

    > if the remote sites are *only* running IPv4, having v6 locally won't
    > help much. ... it's generally true that if you're talking between a
    > v6-only and v4-only host you have to accept the limitations of NAT.

That's the point I've been trying to make.

	Noel



From owner-ietf-outbound  Tue Apr 25 18:20:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA27598
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 18:20:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25495
	for <ietf@ietf.org>; Tue, 25 Apr 2000 16:40:21 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA02696;
        Tue, 25 Apr 2000 16:39:50 -0400 (EDT)
Message-Id: <200004252039.QAA02696@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Anthony Atkielski" <anthony@atkielski.com>
cc: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-reply-to: Your message of "Tue, 25 Apr 2000 20:07:05 +0200."
             <019201bfaee1$11a7fdc0$0a00000a@wanadoo.fr> 
Date: Tue, 25 Apr 2000 16:39:49 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> I dunno.  I don't think that adding two more digits in the 1960s to year
> fields would have really made any problems too hard.  

you've obviously never tried to write business applications for a 
machine with only a few Kbytes of memory.  memory was expensive
in the 1960s, and limited in size.  so was secondary storage.
people optimized every byte, and for good reasons.

> And you can't say that it was a technological barrier, because 
> they were still making Y2K-related mistakes into the 1980s and beyond.

up and into the early 1980s the technological barrier was real.
after that, some of the problems were habit or oversight and some 
of them were due to the need to backward compatibility.  there's
also a more subtle problem that it's difficult to maintain old software
and every time you fix an old bug you stand a good chance of introducing
a new one.  so software tends not to get updated as long as it's mostly 
working.  it's hardly surprising that people didn't bother to fix 
some of the y2k problems until they were forced to do so.

> Why settle for a "considerable amount" (which time will show to be less
> considerable than first believed) when a "nearly infinite amount" can be
> designed into the project?

this has been explained already.  "nearly infinite" imposes technological 
limitations which make it unimplementable at wire speeds, and thus,
undeployable.

and I've already addressed most of the other questions you ask, so I'm
not going to respond to them again.

Keith



From owner-ietf-outbound  Tue Apr 25 18:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA27717
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 18:30:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25570
	for <ietf@ietf.org>; Tue, 25 Apr 2000 16:42:42 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA02716;
        Tue, 25 Apr 2000 16:42:11 -0400 (EDT)
Message-Id: <200004252042.QAA02716@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: ietf@ietf.org, moore@cs.utk.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Tue, 25 Apr 2000 16:32:04 EDT."
             <200004252032.QAA03684@ginger.lcs.mit.edu> 
Date: Tue, 25 Apr 2000 16:42:11 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

>     > I don't see what you're getting at. the outside sites may be running v4
>     > with a limited number of external addresses ... if they are running v6
>     > they will have plenty of external addresses.
> 
> Not external *IPv4* addresses, they won't - which is what kind of addresses
> they need to communicate with other IPv4 sites.

IPv4 vs. IPv6 isn't an either/or - it's quite reasonable for a site
to run IPv4 (with NAT if necessary) alongside IPv6.  I expect that
most sites already on the net will do exactly this - use IPv4 with 
NAT for traditional applications that NAT supports and use IPv6 for 
the other ones.

Keith



From owner-ietf-outbound  Tue Apr 25 18:40:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA28009
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 18:40:03 -0400 (EDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25773
	for <ietf@ietf.org>; Tue, 25 Apr 2000 16:53:33 -0400 (EDT)
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 NAA01488;
	Tue, 25 Apr 2000 13:52:51 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.9.3/8.9.3-VIRSCAN) id MAA15176;
	Tue, 25 Apr 2000 12:57:27 -0700
X-Virus-Scanned:  Tue, 25 Apr 2000 12:57:27 -0700 Nokia Silicon Valley Email Exploit Scanner
Received: from <charliep@iprg.nokia.com> (charliep.iprg.nokia.com [205.226.2.89]) by darkstar.iprg.nokia.com  SMTP/WTS (12.69)
 xmaa14832; Tue, 25 Apr 00 12:57:17 -0700
Sender: charliep@iprg.nokia.com
Message-ID: <39060599.B6BE7006@iprg.nokia.com>
Date: Tue, 25 Apr 2000 13:52:41 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Matt Holdrege <holdrege@lucent.com>
CC: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, ietf@ietf.org
Subject: Re: NAT->IPv6
References: <4.3.1.2.20000425114035.00bf24b0@porky>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


Hello Matt,

I probably shouldn't tread into these waters, but...

>> Now, if you have a site which has more hosts than it can get external IPv4
>> addresses for, then as long as there are considerable numbers of IPv4 hosts a
>> site needs to interoperate with, *deploying IPv6 internally to the site does
>> the site basically no good at all*.
> 
> I think we've been through all this already and we explored it deeply at
> the IAB Network Layer Workshop. One of the conclusions is that an IPv6
> network NAT'ed to the IPv4 Internet isn't any better than what we have
> today with
> IPv4-NAT-IPv4, yet it will allow the given network to move to IPv6 in hopes
> of someday connecting to other IPv6 networks without using NAT.

The last sentence isn't internally self-consistent.  NATting from IPv6
to IPv4 creates the potential that you mention, and that is a benefit.
SO, it _is_ better.

If we get to a model where large new domains use IPv6 addressing
with NAT to global IPv4 address space, that would be quite useful.
Before too long, services will appear on the IPv6 network that
can't get the IPv4 global addresses they need.  IPv6 clients will
work at least as well as privately-addressed IPv4 clients, so that
there is no downside to going IPv6.  As this happens more and more,
the IPv6 domains will begin to dominate and interconnect efficiently.

Since the Internet continues to grow rapidly, today's dominant
deployment may well be tomorrow's sad legacy.  Or not, depending
on who knows what?

> So if you are NAT'd to the public Internet today, you shouldn't have a
> problem with converting internally to IPv6. At least from an architectural
> sense. :)

Indeed.  And, to re-use an old bit of wisdom: "You're either part of
the problem, or part of the solution".

Regards,
Charlie P.



From owner-ietf-outbound  Tue Apr 25 18:50:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA28224
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 18:50:02 -0400 (EDT)
Received: from baboon.aciri.org (baboon.aciri.org [192.150.187.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25780
	for <ietf@ietf.org>; Tue, 25 Apr 2000 16:53:43 -0400 (EDT)
Received: (from pfrancis@localhost)
	by baboon.aciri.org (8.9.3/8.9.3) id NAA40544;
	Tue, 25 Apr 2000 13:53:40 -0700 (PDT)
	(envelope-from pfrancis)
Date: Tue, 25 Apr 2000 13:53:40 -0700 (PDT)
From: Paul Francis <pfrancis@aciri.org>
Message-Id: <200004252053.NAA40544@baboon.aciri.org>
To: francis@ecal.com, narten@hygro.adsl.duke.edu
Subject: runumbering (was:  Re: IPv6: Past mistakes repeated?)
Cc: ietf@ietf.org
In-Reply-To: <200004251457.KAA00869@hygro.adsl.duke.edu>
X-Loop: ietf@ietf.org

>  
>  > Wasn't one of the design goals of IPv6 to make renumbering easier,
>  > so that people could move from small assignments to large ones?
>  
>  Yes.  IPv6's primary tool in this regard is that it supports multiple
>  addresses simultaneously. To renumber, you add a new address to each
>  ..... snip snip .....
>  address, you simply stop using the old address. There are mechanisms
>  in IPv6 that make this approach straightforward (i.e., specifying when
>  

I have a hard time believing that your average IP net manager
wouldn't prefer to run an IPv6-IPv6 NAT box (lets call this
NATv6) at her ISP boundary rather than do site-wide renumbering.
My reasoning goes as follows:

First, while I am willing to grant you the term "straightforward"
to describe site-wide renumbering (it is, for instance, easier
than running a dynamic routing protocol), I would not grant the
term "trivial", and I would say there is some risk and effort
(to minimize the risk) involved. 

For instance, draft-ietf-ipnlwg-router-renum-10.txt says:
"Because of the power of the Router Renumbering mechanism, each RR
message includes a sequence number to guard against replays, and is
required to be authenticated and integrity-checked." Sounds risky
to me.

To minimize the risk, the IP net manager would go through siginifant
effort, first thoroughly testing everything to see that it works as
it is supposed to, then planning the renumbering, then doing the first
phase (adding the new prefix to routers before updating any hosts),
then doing a lot of testing of that, then bit by bit updating hosts,
testing each time, then somehow making sure that every host (or at
least every important host) has been properly updated and the new prefix
is fully in use, and then finally removing the old prefix (and you can
bet her heart will skip a beat when the window reading "Are you sure
you want to delete this prefix" comes up.

This is all doable, but isn't something a net manager is going to
take on lightly.


Now consider the NATv6 alternative.  The average net admin is already
comfortable with NAT at the ISP boundary (hell, some even like it).
She will already be running NAT, if for no other reason than to deal
with IPv4-IPv6 transition.  NATv6 is much less onerous than NATv4,
because the address mapping is one to one (and in fact is probably
a simple prefix rewriting, not a large table lookup), not many to
one like with IPv4.  What's more, NATv6 will give you some rudimentary
form of multihoming (can advertise different prefixes at different
ISPs)!

It seems to me that the decision to just use NATv6 rather than
do a site-wide runumber will be a very easy decision to make.

PF



From owner-ietf-outbound  Tue Apr 25 19:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28405
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 19:00:02 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25854
	for <ietf@ietf.org>; Tue, 25 Apr 2000 16:59:05 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id QAA12826
	for <ietf@ietf.org>; Tue, 25 Apr 2000 16:58:32 -0400
Sender: francis@localhost.localdomain
Message-ID: <390606F8.2F315D4A@ecal.com>
Date: Tue, 25 Apr 2000 16:58:32 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
References: <20000424131939.7281335DC2@smb.research.att.com>           <00cb01bfae2a$381baae0$0a00000a@wanadoo.fr> <200004250139.e3P1dTB34670@black-ice.cc.vt.edu> <019d01bfaee2$61232b80$0a00000a@wanadoo.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Anthony Atkielski wrote:

> From: <Valdis.Kletnieks@vt.edu>
>
> > so that after seeing only the first few bytes, they could
> > know what interface to enqueue the outbound packet on
> > *before the entire packet had even come in*.
>
> But this would be even faster with a variable-length address than with a
> fixed-length address.  You just read address bits until you find a match,
> and ignore the rest.

That's *slow*.

Remember, fast routers are built out of logic gates, not software.  Dynamic
tree structures are hard to build out of gates (no recursion).

> > It's hard to do for something that's truly high-performance.
>
> Something that is high-performance usually costs a lot more than an end-user
> workstation, too, especially with the 90% gross margin that the vendor adds
> to the hardware price.  It's reasonable to expect to get what you pay for.

Well, yes.  Backbone providers pay lots and lots of money to get routers that
actually work.  If all they got was gated running on a workstation, the
backbones wouldn't be performing anywhere near current levels.  (Proof: that's
what the old T3 NSFNet routers were, RS/6000s with special hardware to talk to
the T3.  Supposedly, they couldn't even keep up with T3s, let alone modern
OC-mumbles.)

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |"Collect call from reality, will you accept  |
|francis@ecal.com|the--" *click*                               |
\==============================================================/





From owner-ietf-outbound  Tue Apr 25 19:10:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28658
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 19:10:02 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25860
	for <ietf@ietf.org>; Tue, 25 Apr 2000 16:59:27 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id QAA12822;
	Tue, 25 Apr 2000 16:58:25 -0400
Sender: francis@localhost.localdomain
Message-ID: <390606F0.27B34B98@ecal.com>
Date: Tue, 25 Apr 2000 16:58:25 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Anthony Atkielski <anthony@atkielski.com>
CC: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
References: <200004250037.UAA03162@astro.cs.utk.edu> <019201bfaee1$11a7fdc0$0a00000a@wanadoo.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Anthony Atkielski wrote:

> From: "Keith Moore" <moore@cs.utk.edu>
>
> > it often seems to be the case that if you design for
> > the long term, what you get back isn't deployable
> > in the near term because you've made the problem
> > too hard.
>
> I dunno.  I don't think that adding two more digits in the 1960s to year
> fields would have really made any problems too hard.

Hard, no; expensive, yes.  Consider a DMV system for a state with, oh, 10
million people; each person has a record with at least 3 dates (birth, license
expiration, and one registration date for each car).  Using 4-digit years would
have required over 60MB more storage space.  I don't know 1960s storage prices,
but I know that 60MB would have cost enough to be worth saving.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Anyone who has a conditioned response        |
|francis@ecal.com|immediately thinks of Pavlov.                |
\==============================================================/





From owner-ietf-outbound  Tue Apr 25 19:20:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28868
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 19:20:02 -0400 (EDT)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26159
	for <ietf@ietf.org>; Tue, 25 Apr 2000 17:10:45 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.1/8.10.1) with ESMTP id e3PL9rB33196;
	Tue, 25 Apr 2000 17:09:53 -0400
Message-Id: <200004252109.e3PL9rB33196@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "David R. Conrad" <David.Conrad@nominum.com>
cc: Keith Moore <moore@CS.UTK.EDU>, Bill Manning <bmanning@ISI.EDU>,
        Leonid Yegoshin <egoshin@genesyslab.com>, asp@partan.com,
        ietf@ietf.org, smd@EBONE.NET
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Tue, 25 Apr 2000 12:19:49 PDT."
             <3905EFD5.47AA5BFB@nominum.com> 
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200004251756.NAA01588@astro.cs.utk.edu>
            <3905EFD5.47AA5BFB@nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 25 Apr 2000 17:09:47 -0400
X-Loop: ietf@ietf.org

On Tue, 25 Apr 2000 12:19:49 PDT, "David R. Conrad" said:
> If it "isn't very good", try using the Internet without it for a bit.
> 
> In your view, what is it in the DNS protocol(s) that results in a lack of
> reliability?

Actually, in my experience, the protocol isn't the biggest problem.  To
paraphrase an old joke - "95% of all automobile accidents are caused by
a mechanical failure - a loose nut behind the wheel".

It's like open mail relays - the majority of sites *wont* fix the
problem until the cost of fixing it is less than the pain of not
fixing it.  We had a number of hosts at our site listed in ORBS and
similar databases for MONTHS that cleaned up their act quickly once
they couldn't post to Listserv..


-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Tue Apr 25 19:30:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA29143
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 19:30:02 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26548
	for <ietf@ietf.org>; Tue, 25 Apr 2000 17:30:34 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id RAA12919
	for <ietf@ietf.org>; Tue, 25 Apr 2000 17:30:05 -0400
Sender: francis@localhost.localdomain
Message-ID: <39060E5C.510AE4B5@ecal.com>
Date: Tue, 25 Apr 2000 17:30:05 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: NAT->IPv6
References: <200004251905.PAA03220@ginger.lcs.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

"J. Noel Chiappa" wrote:

> So, you're the CIO for Foondoggle Corp, and you're trying to figure out
> whether to spend any of your Q3 funds on IPv6 conversion. Let's see, benefits
> are not very many (autoconfig may be the best one), and the cost is
> substantial.

Sure.  Then you buy out Moondoggle Corp, which used some of the same private IP
numbers you did, and you're faced with having to renumber everything.  While
you're at it, you decide to convert both networks to v6 so it'll be easier next
time.

(Yes, I know you could put a NAT between the two former companies; but it'll
*hurt*.)

--
/===============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own. |
|Chief Scientist |==============================================|
|eCal Corp.      |I am Homer of Borg. Prepare to be assi... Mmm,|
|francis@ecal.com|doughnuts!                                    |
\===============================================================/





From owner-ietf-outbound  Tue Apr 25 19:40:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA29348
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 19:40:02 -0400 (EDT)
Received: from alive.znep.com (root@alive.znep.com [207.167.15.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26655
	for <ietf@ietf.org>; Tue, 25 Apr 2000 17:32:51 -0400 (EDT)
Received: from localhost (marcs@localhost)
	by alive.znep.com (8.9.3/8.9.1) with ESMTP id PAA14555;
	Tue, 25 Apr 2000 15:32:48 -0600 (MDT)
	(envelope-from marcs@znep.com)
Date: Tue, 25 Apr 2000 15:32:47 -0600 (MDT)
From: Marc Slemko <marcs@znep.com>
To: "David R. Conrad" <David.Conrad@nominum.com>
cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <3905EFD5.47AA5BFB@nominum.com>
Message-ID: <Pine.BSF.4.20.0004251513170.511-100000@alive.znep.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Tue, 25 Apr 2000, David R. Conrad wrote:

> Keith,
> 
> > a 92.55% reliability rate is not exactly impressive, at least not in
> > a favorable sense.
> > 
> > it might be tolerable if a failure of the PTR lookup doesn't cause
> > the application to fail. 
> 
> If people's livelihood depends on something, they're more likely to insure it
> actually works.  Very little depends on PTR records doing anything (with a
> relatively few exceptions of sites that configure it otherwise).  The fact
> that Bill's getting a 92.55% reliability figure for something that the vast
> majority of people use to get something other than IP addresses in logfiles is
> actually surprisingly good.

Except that figure is just for the delegation of the reverse to somewhere
that answers and knows something.

If you look at it on a host by host basis, you will find a lot more hosts
with incorrect or no reverse DNS.

I think that the separation between reverse and forward DNS is a big
problem in keeping things in synch.  Sure, this is a UI issue in some
ways.  But I can assure you that if, by default, people just had to edit a
single file and it would automatically do both forward and reverse
mappings, reverse DNS would be a lot more reliable.  Sure, there are cases
when you need to manually setup what you really want anyway.  It is even
worse when forward and reverse DNS are controlled by different groups.

But, as you say, if it has to work period then it will work.  If only 5%
of the things require it, however, those 5% will always be getting
broken.  

In some ways, I think DNS is too reliable, strictly on the protocol level.  
I would be interested to see numbers from a sample of randomly selected
domains regarding what percentage of their listed nameservers were working
properly, and by that I mean returning a SOA for the zone or something
equally mundane.

I can start off with a good example netscape.com: 75%.  1 of their listed
nameservers hasn't been responding (well, to DNS requests; handles HTTP
requests just fine...) for months.  I am completely unable to get such a
major domain to fix their broken DNS setup, despite the fact that it
causes me (not to mention the other couple of people who ever resolve
netscape.com like, say, anyone who ever starts up Navigator, regardless of
what their home page is set to) significantly noticible delays at times...

Also of interest would be looking at the difference in nameservers between
what a zone itself lists for the zone and what the parent lists for it.

That is always the problem when designing a protocol, of course.  If you
make it robust, you end up with a net loss when things are "working
normally" compared to if it were less robust and foced people to fix their
brokenness.  But that is getting off topic, whatever the topic really
is...



From owner-ietf-outbound  Tue Apr 25 19:50:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA29537
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 19:50:02 -0400 (EDT)
Received: from mailhost.IntNet.net (mailhost.IntNet.net [198.252.32.150])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27072
	for <ietf@ietf.org>; Tue, 25 Apr 2000 17:50:47 -0400 (EDT)
Received: from jtoigo by mailhost.IntNet.net (8.8.5/INTNET/SMI-SVR4)
	id RAA08573; Tue, 25 Apr 2000 17:53:25 -0400 (EDT)
X-Auth: cs-clw-5-228.intnet.net [207.90.1.228]
Message-ID: <04ab01bfaf00$934819e0$dd9cfea9@jtoigo>
From: "Jon William Toigo" <jtoigo@IntNet.net>
To: <ietf@ietf.org>
Subject: SCSI over IP
Date: Tue, 25 Apr 2000 17:52:37 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_04A8_01BFAEDF.0B3AB4C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_04A8_01BFAEDF.0B3AB4C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I learned of a forthcoming RFC covering SCSI over IP from IBM and Cisco =
a couple of weeks ago.  Has anyone heard about this?  Has the RFC been =
submitted yet?   Are there any web sites with more information?

Jon William Toigo
Independent Consultant and Author
jtoigo@intnet.net

------=_NextPart_000_04A8_01BFAEDF.0B3AB4C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I learned of a forthcoming RFC covering =
SCSI over=20
IP from IBM and Cisco a couple of weeks ago.&nbsp; Has anyone heard =
about=20
this?&nbsp; Has the RFC been submitted yet?&nbsp;&nbsp; Are there any =
web sites=20
with more information?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Jon William Toigo</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Independent Consultant and =
Author</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"mailto:jtoigo@intnet.net">jtoigo@intnet.net</A></FONT></DIV></BOD=
Y></HTML>

------=_NextPart_000_04A8_01BFAEDF.0B3AB4C0--



From owner-ietf-outbound  Tue Apr 25 20:00:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA29718
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 20:00:03 -0400 (EDT)
Received: from postoffice.cisco.com (postoffice.cisco.com [171.69.198.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27440
	for <ietf@ietf.org>; Tue, 25 Apr 2000 18:08:29 -0400 (EDT)
Received: from [10.19.130.188] (deering-dsl3.cisco.com [10.19.130.188]) by postoffice.cisco.com (8.8.7-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id PAA00381; Tue, 25 Apr 2000 15:07:24 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@postoffice
Message-Id: <v0422080ab52bb51acf9e@[10.19.130.188]>
In-Reply-To: <019201bfaee1$11a7fdc0$0a00000a@wanadoo.fr>
References: <200004250037.UAA03162@astro.cs.utk.edu>
 <019201bfaee1$11a7fdc0$0a00000a@wanadoo.fr>
Date: Tue, 25 Apr 2000 15:08:13 -0700
To: "Anthony Atkielski" <anthony@atkielski.com>
From: Steve Deering <deering@cisco.com>
Subject: Re: IPv6: Past mistakes repeated?
Cc: <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Anthony,

One interesting example:  OSI NSAP addresses are variable length, with a
theoretical limit of 255 bytes I believe (perhaps there's an escape
mechanism to grow them longer?).  There was an "implementors'
agreement" to limit the maximum length in actual use to 20 bytes "for now",
to make implementations practical.  Two things happened:

	(1) Almost all of the addressing plans designed for NSAPAs
	    produced addresses that were *exactly* 20 bytes long, in
	    some cases inserting padding in the middle of the address
	    to fill it out to 20 bytes!  I suspect that was done to
	    make the address allocation job easier, e.g., making
	    sure delegation boundaries fell on byte boundaries.

	(2) Many of the implementations ended up with the 20-byte limit
	    wired into them, such that the use of addresses longer than
	    20 bytes would have required updating most of the installed
	    base (the changes being of a similar nature to those required
	    to modify an IPv4 application or protocol to support IPv6).

This (admittedly anecdotal) example led me to surmise that:

	- any variable-length address scheme will have a maximum size
	  imposed upon it, for pragmatic implementation reasons.

	- any variable-length address scheme will quickly degenerate
	  into a fixed-length scheme of maximum size, for human nature
	  reasons (the humans being the people doing the address
	  allocation).

At which point, you are back to the problem you were trying to avoid.

I think the only reason this hasn't happened in the phone system is due
to resistance by humans to reading, writing, and entering very long
strings of digits.  Unfortunately, computers aren't as fussy.

Perhaps you could think of IPv6 addresses as variable-length addresses
within a fixed-size container, in which the variable-length part is in
the middle and not at the right hand end?  :-)

Anyway, as pointed out by others, the IPv6 work anticipates that there
may be a need to "rebalance" the address assignments (i.e., renumber) in
the future, if/when our predictions of where the growth will be turn out
to be wrong, which ought to be less painful than making the changes to
deployed implementations that your scheme would require whenever a
significant number of addresses started to exceed the length that caused
traps into the exception-handling code.  And we avoid the risk of having
many very long addresses (in this case, longer than 16 bytes) being used,
which is important for a connectionless protocol like IP, in which the
addresses are overhead in every packet.

Steve



From owner-ietf-outbound  Tue Apr 25 20:10:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA29938
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 20:10:02 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28094
	for <ietf@ietf.org>; Tue, 25 Apr 2000 18:44:04 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id SAA13085;
	Tue, 25 Apr 2000 18:41:56 -0400
Sender: francis@localhost.localdomain
Message-ID: <39061F34.8F75103@ecal.com>
Date: Tue, 25 Apr 2000 18:41:56 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Francis <pfrancis@aciri.org>
CC: narten@hygro.adsl.duke.edu, smd@EBONE.NET, ietf@ietf.org
Subject: Re: multihoming (was Re: draft-ietf-nat-protocol-complications-02.txt)
References: <200004252011.NAA40378@baboon.aciri.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Paul Francis wrote:

> Sean said that traditional multihoming would be "very difficult".
>
> You replied that "This is not true" (which I take to mean
> that multihoming is not very difficult), and then go on to describe
> something that sounds very difficult to me (maintain longer prefixes,
> make multihomed customers pay for it, get the ISPs to agree to
> handle such longer prefixes).

But these are the same problems that you have with multihoming in IPv4.  So
the assertion is that IPv6 doesn't make it any worse, and tries to make it
less necessary.

--
/===============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own. |
|Chief Scientist |==============================================|
|eCal Corp.      |"Fate just isn't what it used to be." --Hobbes|
|francis@ecal.com|                                              |
\===============================================================/





From owner-ietf-outbound  Tue Apr 25 20:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA00190
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 20:20:02 -0400 (EDT)
Received: from tower.partan.com (tower.partan.com [198.6.255.248])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28353
	for <ietf@ietf.org>; Tue, 25 Apr 2000 18:57:41 -0400 (EDT)
Received: (from asp@localhost)
	by tower.partan.com (8.9.3/8.9.3) id SAA07168;
	Tue, 25 Apr 2000 18:57:38 -0400 (EDT)
From: Andrew Partan <asp@partan.com>
Message-Id: <200004252257.SAA07168@tower.partan.com>
Subject: Re: IPv6: Past mistakes repeated?
To: moore@cs.utk.edu (Keith Moore)
Date: Tue, 25 Apr 2000 18:57:38 -0400 (EDT)
Cc: ietf@ietf.org
In-Reply-To: <200004250037.UAA03162@astro.cs.utk.edu> from "Keith Moore" at Apr 24, 0 08:37:46 pm
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
X-Loop: ietf@ietf.org

> address space shortage is just one of many possible problems.
> as long as the network keeps growing at exponential rates we are 
> bound to run into some other major hurdle in a few years.  it might
> be address space but the chances are good that before we hit that 
> limitation again that we will run into some other fundamental barrier.

The problem some of us have been worring about is the routing table.

The routing table can either fill up or be overwhelmed by the rate
of change of routing entries.  There is a tradeoff between these
two - no changes means that you can have a large static table; lots
of changes and you will need a smaller table to have stability.

Unfortunately its hard to predict when you will tip over...
	--asp@partan.com (Andrew Partan)



From owner-ietf-outbound  Tue Apr 25 20:30:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA00435
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 20:30:03 -0400 (EDT)
Received: from postoffice.cisco.com (postoffice.cisco.com [171.69.198.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28373
	for <ietf@ietf.org>; Tue, 25 Apr 2000 18:58:29 -0400 (EDT)
Received: from [10.19.130.188] (deering-dsl3.cisco.com [10.19.130.188]) by postoffice.cisco.com (8.8.7-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id PAA07798; Tue, 25 Apr 2000 15:53:57 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@postoffice
Message-Id: <v0422080bb52bc7db38a0@[10.19.130.188]>
In-Reply-To: <200004252011.NAA40378@baboon.aciri.org>
References: <200004252011.NAA40378@baboon.aciri.org>
Date: Tue, 25 Apr 2000 15:54:46 -0700
To: Paul Francis <pfrancis@aciri.org>
From: Steve Deering <deering@cisco.com>
Subject: Re: multihoming (was Re:
 draft-ietf-nat-protocol-complications-02.txt)
Cc: narten@hygro.adsl.duke.edu, smd@EBONE.NET, ietf@ietf.org
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 1:11 PM -0700 4/25/00, Paul Francis wrote:
>For me, your statement certainly reinforces the idea that multihoming in
>IPv6 is indeed very difficult.

More accurately: multihoming in IP (any version) is indeed very difficult.
The problems are a fundamental consequence of having to do hierarchical
addressing and routing.  IPv6 is no worse than IPv4 in this regard, and
there are some features of IPv6 that might actually make make it better
(e.g., host support for multiple addresses on a single interface).

>I read your statement as follows:
>
>    IPv6 does not solve the multihoming problem.  Instead, it tries
>    to minimize the damage by:
>    
>    1. discouraging the use of multihoming, primarily may making
>    multihomed customers pay more for it.
>    2. forcing paths to multihomed sites to be less efficient (at
>    least for all but one of the ISP connection points) and or,
>    3. limiting the regions of the internet for which multihoming
>    is effective for a given customer.
>
>Is this an accurate representation?

Not at all.  Try this:

    IPv4 has one, problematical solution to the site multihoming problem:
    advertise the site's prefix globally (or, at least, beyond more than
    a single ISP's domain).  This has obvious scaling problems as a
    solution to multihoming a very large number of sites (e.g., millions
    of households, as in Sean's example).

    People have accused IPv6 of lacking that one (non-scalable) solution
    to multihoming, based on a misunderstanding of the IPv6 address
    architecture.  That accusation is false, and nothing in IPv6 prevents
    the use of the same, lousy multihoming solution we have today for IPv4.

    IPv6 includes support for *additional* potential solutions to multihoming
    in which, rather than a site having a single prefix advertised globally,
    the site has multiple, aggregatable prefixes, and something more
    intelligent is done in the site's border routers and/or the the end
    hosts.  This is work-in-progress, and is likely to produce solutions
    with a different (but, we hope, acceptable in many contexts) set of
    shortcomings.

Steve



From owner-ietf-outbound  Tue Apr 25 20:40:59 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA00690
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 20:40:55 -0400 (EDT)
Received: from mail.nanospace.com (qmailr@mail.nanospace.com [209.213.199.10])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA28740
	for <ietf@ietf.org>; Tue, 25 Apr 2000 19:12:39 -0400 (EDT)
Received: (qmail 20470 invoked from network); 25 Apr 2000 23:12:36 -0000
Received: from thegrind.yipes.com (HELO zzsf220) (209.213.212.254)
  by mail.nanospace.com with SMTP; 25 Apr 2000 23:12:36 -0000
Reply-To: <jdunn@yipes.com>
From: "Jim Stephenson-Dunn" <jdunn@yipes.com>
To: "'Mathis Jim-AJM005'" <Jim.Mathis@Motorola.com>
Cc: <ietf@ietf.org>
Subject: RE: IPv6: Past mistakes repeated? 
Date: Tue, 25 Apr 2000 16:12:30 -0700
Message-ID: <01C88F753E97D311A7180090278D1D40689B50@TEAMSF>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <01C88F753E97D311A7180090278D1D406E0792@TEAMSF>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Jim, I totally agree with you. We need to move and start deploying this now
rather that later. Starting with the carriers, then the ISP's and the trend
will flow down until eventually (in 10-15 years) everyone and everything
will be IPv6.

I have been tasked with looking into the feasability of upgrading our core
network to v6. I work for a company in San Francisco. We link LAN's and
MAN's But we will be looking to interconnect all of our cities in the US
together and IMHO I think IPv6 is the ONLY long term solution to achieve
this, what is the point of building a network and then having to renumber it
a couple of years down the line, it is better to use v6 numbering now and
continue that way.

It may be painful but no where near as painful as having to renumber
everything in 5/10/15 years time. There WILL be issues, undoubtably, but
usually anything worth while has these problems and issues, that is what
makes it worth while, striving for.

We need to embrace this and move forward as one community, with everyone
singing from the same hymn sheet as it were. If (we)the engineers won't
deploy v6 ourselves, then how can we expect anyone else to. There is alot of
fear,uncertainty and doubt in the world about what we are trying to do here
(I seem to experience it in one form or another every day {;-( ), and surely
we should be taking the lead here (isn't that in the charter somewhere ?) If
the Engineers lead, the masses will follow.

I think it is now a well established fact that eventually we will deplete v6
address space, but as Ian says, in twenty years time we can take what we
have learnt with the deployment of v6 and apply it to the new version of IP.
Who know's, maybe it will be 256 or even 512 bits long, and if that isn't an
argument for a global DHCP server, I don't know what is.(and you think we
have problems now ;->)

Jim

Jim Dunn

Senior Network Engineer
San Francisco NOC



-----Original Message-----
From: Mathis Jim-AJM005 [mailto:Jim.Mathis@Motorola.com]
Sent: Monday, April 24, 2000 8:02 PM
To: ietf@ietf.org
Subject: RE: IPv6: Past mistakes repeated?


A brief history lesson...

There was some concern about a 32-bit address space.  MIT-LCS
proposed 48 (or 64-bit) addresses but that was coupled with a
reduction of the TCP sequence number to 16 bits.  After some
discussion, we settled on 32-bits based on the computing
resources available at the time.  At that time, there was no
separate IP header, only addressing fields in the TCP header.

Around that time, the ARPANET had recently scaled up from
8-bit host addresses to 24-bits.  Seemed unlikely that anyone
would build more than 100 ARPANET-sized networks with its huge
IMPs and PDP-10 mainframe computers (and UCLA's 360).  48-bit
Ethernet addressing wasn't around yet; otherwise we probably
would have picked 64 bits just to not have to deal with ARP.
This was before Moore's law; Intel had just released the
8008 microprocessor.  There were less than 100,000 large
commercial buildings (>500,000 sq. ft) in the world; seemed
that the number of class-c addresses were sufficient.  For
better or worse, the size of the address field went unchanged
from the original version of TCP (before IP was a separate
header).

We were caught short by a technology paradigm shift coming
from semiconductor physics.  If computers rode the same
technology advancement curve as cars, we wouldn't be having
an address space problem now.

We cannot predict the next big technology paradigm shift.
The real lesson to learn from IPv4 - IPv6 (which I think
was described by Knuth in regards to conversion of computer
instruction sets but I can't find the reference) is the
cost of delaying conversion.  For the longer you delay
the inevitable, the more installed base you have to
convert and the exponentially higher the resulting cost.

The excellent engineering to keep v4 running was too good
and has slowed the inevitable movement to larger address
spaces.  While there are no guarantees that 128-bits won't
be exhausted sometime in the future, we do know a lot more
about address space management and allocation than when Jon
started handing out net numbers. The Internet has always
been a balancing act between being ready for the future
and getting something working today.  IPv6 will not change
this, so we need to be prepared for change.  The next "big"
problem facing the Internet that will require a broad-scale
swap-out of software probably won't be address-space related.

We need to move forward with IPv6 both by deploying it in
the "core" and setting a time-frame after which non-IPv4
compatible addresses will be assigned.  Unless there is a
clear reason to move, no one wants to change software just
to change.  Once IPv6 is in the major backhaul carriers, ISPs
can role out improved services based on IPv6 which will be
the real reason end-users upgrade.  Seems like a real
leadership vacuum here...

Jim

> -----Original Message-----
> From: Keith Moore [mailto:moore@cs.utk.edu]
> Sent: Monday, April 24, 2000 2:36 PM
> To: Anthony Atkielski
> Cc: ietf@ietf.org
> Subject: Re: IPv6: Past mistakes repeated?
>
>
> > What I find interesting throughout discussions that mention
> IPv6 as a
> > solution for a shortage of addresses in IPv4 is that people see the
> > problems with IPv4, but they don't realize that IPv6 will
> run into the
> > same difficulties.  _Any_ addressing scheme that uses addresses of
> > fixed length will run out of addresses after a finite
> period of time,
>
> I suppose that's true - as long as addresses are consumed at a rate
> faster than they are recycled.  But the fact that we will run out of
> addresses eventually might not be terribly significant - the Sun will
> also run out of hydrogen eventually, but in the meantime we still find
> it useful.
>
> > and that period may be orders of magnitude shorter than anyone might
> > at first believe.
>
> it is certainly true that without careful management IPv6 address
> space could be consumed fairly quickly.  but to me it looks like that
> with even moderate care IPv6 space can last for several tens of years.
>
> > Consider IPv4.  Thirty-two bits allows more than four billion
> > individual machines to be addressed.
>
> not really.  IP has always assumed that address space would be
> delegated in power-of-two sized "chunks" - at first those chunks only
> came in 3 sizes (2**8, 2**16, or 2**24 addresses), and later on it
> became possible to delegate any power-of-two sized chunk.  but even
> assuming ideally sized allocations, each of those chunks would on
> average be only 50% utilized.
>
> so every level of delegation effectively uses 1 of those 32 bits, and
> on average most parts of the net are probably delegated 4-5 levels
> deep.  (IANA/regional registry/ISP/customer/internal). so we end up
> effectively not with 2**32 addresses but with something like 2**27 or
> 2**28.  (approximately 134 million or 268 million)
>
> (see also RFC 1715 for a different analysis, which when applied to
> IPv4, yields similar results for the optimistic case)
>
> allocating space in advance might indeed take away another few bits.
> but given the current growth rate of the internet it is necessary.
> the internet is growing so fast that a policy of always allocating
> only the smallest possible chunk for a net would not only be
> cumbersome, it would result in poor aggregation in routing tables and
> quite possibly in worse overall utilization of address space.
>
> but if it someday gets easier to renumber a subnet we might then find
> it easier to garbage collect, and recycle, fragmented portions of
> address space.  and if the growth rate slowed down (which for various
> reasons is possible) then we could do advance allocation more
> conservatively.
>
> > It should be clear that IPv6 will have the same problem.  The space
> > will be allocated in advance.  Over time, it will become
> obvious that
> > the original allocation scheme is ill-adapted to changing
> requirements
> > (because we simply cannot foresee those requirements).  Much, _much_
> > sooner than anyone expects, IPv6 will start to run short of
> addresses,
> > for the same reason that IPv4 is running short.  It seems impossible
> > now, but I suppose that running out of space in IPv4 seemed
> impossible
> > at one time, too.
>
> IPv6 allocation will have some of the same properties of IPv4
> allocation.  We're still using power-of-two sized blocks, we'll still
> waste at least one bit of address space per level of delegation.  It
> will probably be somewhat easier to renumber networks and recycle
> address - how much easier remains to be seen.
>
> OTOH, I don't see why IPv6 will necessarily have significantly more
> levels of assignment delegation.  Even if it needs a few more levels,
> 6 or 7 bits out of 128 total is a lot worse than 4 or 5 bits
> out of 32.
>
> > The allocation pattern is easy to foresee.  Initially, enormous
> > subsets of the address space will be allocated carelessly and
> > generously, because "there are so many addresses that we'll
> never run
> > out"
>
> I don't know where you get that idea.  Quite the contrary, the
> regional registries seem to share your concern that we will use up
> IPv6 space too quickly and *all* of the comments I've heard about the
> initial assignment policies were that they were too conservative.
> IPv6 space does need to be carefully managed, but it can be doled out
> somewhat more generously than IPv4 space.
>
> > and because nobody will want to expend the effort to achieve
> > finer granularity in the face of such apparent plenty.
>
> First of all, having too fine a granularity in allocation prevents you
> from aggregating routes.  Second, with power-of-two sized allocations
> there's a limit to how much granularity you can get - even if you
> always allocate optimal sized blocks.
>
> > This mistake will be repeated for each subset of the address space
> > allocated, by each organization charged with allocating the space.
>
> It's not clear that it's a mistake.  it's a tradeoff between having
> aggregatable addresses and distributed assignment on one hand and
> conserving address space on the other.  and the people doing address
> assignment these days are quite accustomed to thinking in these terms.
>
> > If you need further evidence, look at virtual memory address spaces.
> > Even if a computer's architecture allows for a trillion bits of
> > addressing space, it invariably becomes fragmented and
> exhausted in an
> > amazingly short time.
>
> this is only amazing to those who haven't heard of Moore's law.
> (presumably the same set of people who thought DES would
> never be broken)
>
> on the other hand, it's not clear how valid this analogy is for
> predicting the growth of the Internet - just because Moore's law (if
> it keeps on working) might predict that in a decade we could
> eventually have thousands of network-accessible computing devices for
> everyone on the planet, doesn't mean that those people would be able
> to deal with thousands of such devices.  and there do appear to be
> limits to the number of human beings that the planet can support.  and
> if by that time the robot population exceeds the human population then
> I'm happy to let the robots solve the problem of upgrading to a new
> version of IP.
>
> and as for other planets, all kinds of assumptions about the current
> Internet fail when you try to make it work at interplanetary
> transmission latencies.  so if we do manage to significantly populate
> other planets or if we find extraterrestrial species that we want to
> network with, we'll have to build a new architecture.  and people are
> already working on that.
>
> > The only real solution to this is an open-ended addressing
> scheme--one
> > to which digits can be added as required.
>
> variable length addresses do have some nice properties.  there are
> also some drawbacks.
>
> fwiw, phone numbers do in fact have a fixed maximum length which is
> wired into devices all over the planet - not just in the phone system
> but in numerous computer databases, etc..  it is not much easier to
> increase the overall length of phone numbers than it is to make IP
> addresses longer.  and once you set a fixed maximum length then it's
> just a matter of representation - do you have a variable-length
> address field or do you have a fixed-length field with zero padding?
> fixed-length fields are a lot easier for routers to deal with.  (and
> for similar reasons a lot of software uses fixed-length fields for
> phone numbers)
>
> 128-bit IPv6 addresses are roughly equivalent to 40 digits, which IIRC
> is a lot longer than the maximum size of a phone number under E.164.
> (sorry, I don't have a copy handy to check)
>
> and the means by which IPv6 addresses are being allocated is actually
> not so different from the means in which phone numbers are allocated -
> the major exception being that IPv6 prefixes are assigned to major
> ISPs rather than to geographic regions.  (the latter difference might
> affect routing but probably does not affect allocation efficiency).
>
> so I think the bottom line answer to your message is that your concers
> are valid (if perhaps a bit exaggerated) and an allocation mechanism
> similar to what you suggest is already in place.
>
> Keith
>




From owner-ietf-outbound  Tue Apr 25 20:50:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA00874
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 20:50:03 -0400 (EDT)
Received: from postoffice.cisco.com (postoffice.cisco.com [171.69.198.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28893
	for <ietf@ietf.org>; Tue, 25 Apr 2000 19:21:43 -0400 (EDT)
Received: from [10.19.130.188] (deering-dsl3.cisco.com [10.19.130.188]) by postoffice.cisco.com (8.8.7-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id QAA12226; Tue, 25 Apr 2000 16:21:02 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@postoffice
Message-Id: <v0422080cb52bd6f7c619@[10.19.130.188]>
In-Reply-To: <200004252053.NAA40544@baboon.aciri.org>
References: <200004252053.NAA40544@baboon.aciri.org>
Date: Tue, 25 Apr 2000 16:21:50 -0700
To: Paul Francis <pfrancis@aciri.org>
From: Steve Deering <deering@cisco.com>
Subject: Re: runumbering (was:  Re: IPv6: Past mistakes repeated?)
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 1:53 PM -0700 4/25/00, Paul Francis wrote:
>It seems to me that the decision to just use NATv6 rather than
>do a site-wide runumber will be a very easy decision to make.

If that were the only issue, sure.  But there are tradeoffs: is the ease
of renumbering (which should be a relatively rare event) offered by a NAT
box worth all the ongoing costs incurred in using NAT in the first place
(more complicated, fragile network, more difficult problem diagnosis,
degraded performance, weakened security, opportunity costs of not being
able to run certain kinds of applications, and so on)?

Steve



From owner-ietf-outbound  Tue Apr 25 21:00:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA01137
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 21:00:03 -0400 (EDT)
Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29239
	for <ietf@ietf.org>; Tue, 25 Apr 2000 19:32:30 -0400 (EDT)
Received: from dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155])
	by piglet.dstc.edu.au (8.9.3/8.9.3) with ESMTP id JAA09009;
	Wed, 26 Apr 2000 09:31:40 +1000 (EST)
X-Mailer: exmh version 2.1.0 09/18/1999
To: "David R. Conrad" <David.Conrad@nominum.com>
cc: Keith Moore <moore@cs.utk.edu>, Bill Manning <bmanning@ISI.EDU>,
        Leonid Yegoshin <egoshin@genesyslab.com>, asp@partan.com,
        ietf@ietf.org, smd@EBONE.NET
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-Reply-To: Message from "David R. Conrad" <David.Conrad@nominum.com> 
   of "Tue, 25 Apr 2000 12:19:49 MST." <3905EFD5.47AA5BFB@nominum.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 26 Apr 2000 09:31:39 +1000
Message-ID: <5631.956705499@dstc.edu.au>
From: George Michaelson <ggm@dstc.edu.au>
X-Loop: ietf@ietf.org


I think there are interesting things happening in DNS. I wrote a not very
good paper for AUUG a few years back noting an error rate in DNS above 10%
for the mirror site I do stats on.

Reviewing the figures for yesterday I get 9.75% unresolvable which is pretty
close to Bill Mannings figure.

But then I checked over the last 116 days since the start of the year. I find
that for a deployed site, logging IP and DNS name into CLF format (so I can
use analog) for ftp ,rsync and www I get:

	avg=15.288431, lo=4.213000, hi=33.265000

I think Bill is saying what really exists in DNS. I'm saying what a box
deployed in the field can expect to see. Its pretty damn variable and its
a lot worse than the DNS records would themselves suggest. Remember that
DNS is timebound with timeouts in client code, uses UDP and is subject to
the same kind of loss issues as the general datapath.

(this is on a client base of around 3000 hosts, weighted for Australia/NZ)

cheers
	-George
--
George Michaelson         |  DSTC Pty Ltd
Email: ggm@dstc.edu.au    |  University of Qld 4072
Phone: +61 7 3365 4310    |  Australia
  Fax: +61 7 3365 4311    |  http://www.dstc.edu.au




From owner-ietf-outbound  Tue Apr 25 21:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA01401
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 21:10:03 -0400 (EDT)
Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29898
	for <ietf@ietf.org>; Tue, 25 Apr 2000 20:08:29 -0400 (EDT)
Received: from dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155])
	by piglet.dstc.edu.au (8.9.3/8.9.3) with ESMTP id KAA13686;
	Wed, 26 Apr 2000 10:08:08 +1000 (EST)
X-Mailer: exmh version 2.1.0 09/18/1999
To: Steve Deering <deering@cisco.com>
cc: "Anthony Atkielski" <anthony@ATKIELSKI.COM>, ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-Reply-To: Message from Steve Deering <deering@cisco.com> 
   of "Tue, 25 Apr 2000 15:08:13 MST." <v0422080ab52bb51acf9e@[10.19.130.188]> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 26 Apr 2000 10:08:08 +1000
Message-ID: <5870.956707688@dstc.edu.au>
From: George Michaelson <ggm@dstc.edu.au>
X-Loop: ietf@ietf.org


  I think the only reason this hasn't happened in the phone system is due
  to resistance by humans to reading, writing, and entering very long
  strings of digits.  Unfortunately, computers aren't as fussy.

My experience is that as people become more (internationally) mobile their
use of IDD +xx aaaa bbbb form number spec becomes more common.

Likewise with major slices of the UK and Australia recently renumbered, people
were forced to ditch their paper investment in old numbers and dropped into
line in a semi-standard form of representation which has to be full-number
aligned, because the new digits are in front of the old semi-optional prefixes.

In other words, the old '7 digits is all people can handle' rule is melting
in the face of a larger pool of people who have to use longer digit strings.

cheers
	-George
--
George Michaelson         |  DSTC Pty Ltd
Email: ggm@dstc.edu.au    |  University of Qld 4072
Phone: +61 7 3365 4310    |  Australia
  Fax: +61 7 3365 4311    |  http://www.dstc.edu.au




From owner-ietf-outbound  Tue Apr 25 21:20:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA01622
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 21:20:03 -0400 (EDT)
Received: from cerberus.oware.net (IDENT:qmailr@gateway.doradosoftware.com [206.215.28.201] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA29991
	for <ietf@ietf.org>; Tue, 25 Apr 2000 20:12:28 -0400 (EDT)
Received: (qmail 21794 invoked from network); 26 Apr 2000 00:16:46 -0000
Received: from dhcp192-168-1-213.oware.net (HELO scooby) (192.168.1.213)
  by gateway.doradosoftware.com with SMTP; 26 Apr 2000 00:16:46 -0000
Message-ID: <008301bfaf0b$d14f4f00$abb6fea9@oware.net>
Reply-To: "Jasen Strutt" <jasen@pcpotato.com>
From: "Jasen Strutt" <jasen@pcpotato.com>
To: "Jon William Toigo" <jtoigo@IntNet.net>, <ietf@ietf.org>
References: <04ab01bfaf00$934819e0$dd9cfea9@jtoigo>
Subject: Re: SCSI over IP
Date: Tue, 25 Apr 2000 17:13:07 -0600
Organization: Some, but not much
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0080_01BFAED9.867AE340"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0080_01BFAED9.867AE340
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

SCSIoIP=20
Who'd a thunk it....

I believe there are a few hash renditions of it at a higher level of =
networking through distributed computing / storage and processing but =
lack the white papers to send you on it. I'd be interested if anyone =
else has specifics on it.

Comments?=20
 =20
  ----- Original Message -----=20
  From: Jon William Toigo=20
  To: ietf@ietf.org=20
  Sent: Tuesday, April 25, 2000 3:52 PM
  Subject: SCSI over IP


  I learned of a forthcoming RFC covering SCSI over IP from IBM and =
Cisco a couple of weeks ago.  Has anyone heard about this?  Has the RFC =
been submitted yet?   Are there any web sites with more information?

  Jon William Toigo
  Independent Consultant and Author
  jtoigo@intnet.net

------=_NextPart_000_0080_01BFAED9.867AE340
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>SCSIoIP </FONT></DIV>
<DIV><FONT size=3D2>Who'd a thunk it....</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>I believe there are a few hash renditions of it at a =
higher=20
level of networking through distributed computing / storage and =
processing but=20
lack the white papers to send you on it. I'd be interested if anyone =
else has=20
specifics on it.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Comments?&nbsp;</FONT></DIV>
<DIV><FONT size=3D2>&nbsp;&nbsp;</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A href=3D"mailto:jtoigo@IntNet.net" title=3Djtoigo@IntNet.net>Jon =
William=20
  Toigo</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:ietf@ietf.org"=20
  title=3Dietf@ietf.org>ietf@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, April 25, 2000 =
3:52=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> SCSI over IP</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>I learned of a forthcoming RFC =
covering SCSI over=20
  IP from IBM and Cisco a couple of weeks ago.&nbsp; Has anyone heard =
about=20
  this?&nbsp; Has the RFC been submitted yet?&nbsp;&nbsp; Are there any =
web=20
  sites with more information?</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Jon William Toigo</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Independent Consultant and =
Author</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><A=20
  =
href=3D"mailto:jtoigo@intnet.net">jtoigo@intnet.net</A></FONT></DIV></BLO=
CKQUOTE></BODY></HTML>

------=_NextPart_000_0080_01BFAED9.867AE340--



From owner-ietf-outbound  Tue Apr 25 21:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA01864
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 21:30:04 -0400 (EDT)
Received: from mail2.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA00095
	for <ietf@ietf.org>; Tue, 25 Apr 2000 20:15:38 -0400 (EDT)
Received: from 157.54.9.104 by mail2.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 25 Apr 2000 17:14:03 -0700 (Pacific Daylight Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2651.58)
	id <J2VXL51T>; Tue, 25 Apr 2000 17:14:02 -0700
Message-ID: <BB61526CDE70D2119D0F00805FBECA2F16967274@RED-MSG-55>
From: Christian Huitema <huitema@microsoft.com>
To: "'Paul Francis'" <pfrancis@aciri.org>, francis@ecal.com,
        narten@hygro.adsl.duke.edu
Cc: ietf@ietf.org
Subject: RE: runumbering (was:  Re: IPv6: Past mistakes repeated?)
Date: Tue, 25 Apr 2000 17:13:57 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

> Now consider the NATv6 alternative.  The average net admin is already
> comfortable with NAT at the ISP boundary (hell, some even like it).
> She will already be running NAT, if for no other reason than to deal
> with IPv4-IPv6 transition.  NATv6 is much less onerous than NATv4,
> because the address mapping is one to one (and in fact is probably
> a simple prefix rewriting, not a large table lookup), not many to
> one like with IPv4.  What's more, NATv6 will give you some rudimentary
> form of multihoming (can advertise different prefixes at different
> ISPs)!

I think your description is somewhat biased, Paul. Suppose that you execute
the strategy you describe, and that the address 10.3.2.1, that was mapped to
129.87.64.32, gets transparently remapped to 130.123.45.67. It seems to me
that you are going to loose all existing TCP connections, just like with any
other form of renumbering. Suppose then that the external prefix of your
site, 129.87.64.0/25, was used in the firewall access control lists of your
business partners. Well, unless these partners somehow reprogram their
firewall, the packets sourced from 130.123.45.67 are not going to get
through. What? Numeric addresses in ACL is bad? Come on -- if none were
used, if we only used DNS names, then renumbering would not be the problem
that it is known to be! Besides, do you believe that using a NAT rather than
plain renumbering would make your external DNS records to upgrade any
sooner?

Suppose now that you want to use NAT for multihoming. Suppose then that I
really care that my TCP connection survives when I loose contact with ISP-A,
the one that provided me with the prefix 129.87.64.0/25. Can I just go on
routing the packets through ISP-B, that provides me with the address
130.123.45.0/25? Well, you can source them, but not receiving them, unless
you convince ISP-B to announce your other /25 prefix in its BGP tables --
just like the old fashion no-NAT multihoming. And then, how exactly do you
tell your customers that, among the two IP addresses of your web site, they
should really use 130.123.45.3, not 129.87.64.5?

Turn it any way you want, TCP sessions can only survive renumbering through
end to end mechanisms, in effect some form of TCP-NG, and effective
multihoming requires either a single address prefix supported by multiple
ISPs, or end to end smartness to pick the best of N addresses (hey, we could
use *your* work for that!) As Steve pointed out, trying to convince your ISP
to announce random non topological prefixes will get you laughed out of
court. There is, in fact, no alternative to end-to-end smartness -- the
smarter your end systems, the more likely they are to use the network
correctly. Now, if your systems are smart and now how to choose one of many
available addresses, then we have a solution with v6 multi-homing -- the
support of multiple prefixes per site, multiple addresses per interface. 



From owner-ietf-outbound  Tue Apr 25 21:40:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA02088
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 21:40:02 -0400 (EDT)
Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00977
	for <ietf@ietf.org>; Tue, 25 Apr 2000 20:54:35 -0400 (EDT)
Received: from yogi.ece.cmu.edu (IDENT:root@YOGI.ECE.CMU.EDU [128.2.252.128])
	by ece.cmu.edu (8.9.2/8.8.8) with ESMTP id UAA13760;
	Tue, 25 Apr 2000 20:54:31 -0400 (EDT)
Received: from yogi.ece.cmu.edu (bassoon@localhost [127.0.0.1])
	by yogi.ece.cmu.edu (8.8.7/8.8.7) with ESMTP id UAA24941;
	Tue, 25 Apr 2000 20:54:30 -0400
Message-Id: <200004260054.UAA24941@yogi.ece.cmu.edu>
To: "Jon William Toigo" <jtoigo@IntNet.net>
cc: ietf@ietf.org
Subject: Re: SCSI over IP 
In-reply-to: Your message of "Tue, 25 Apr 2000 17:52:37 EDT."
             <04ab01bfaf00$934819e0$dd9cfea9@jtoigo> 
Date: Tue, 25 Apr 2000 20:54:30 -0400
From: Dave Nagle <bassoon@yogi.ece.cmu.edu>
X-Loop: ietf@ietf.org

Jon,

 >> I learned of a forthcoming RFC covering SCSI over IP from IBM and Cisco =
 >> a couple of weeks ago.  Has anyone heard about this?  Has the RFC been =
 >> submitted yet?   Are there any web sites with more information?


  Information on the proposed RFC info on SCSI over IP is 

    http://www.ece.cmu.edu/~ips


dave............

David Nagle
Director, Parallel Data Lab
School of Computer Science
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-3898 (office)
412-268-3890 (fax)
http://www.ece.cmu.edu/~bassoon


Original Message
----------------
 >> This is a multi-part message in MIME format.
 >> 
 >> ------=_NextPart_000_04A8_01BFAEDF.0B3AB4C0
 >> Content-Type: text/plain;
 >> 	charset="iso-8859-1"
 >> Content-Transfer-Encoding: quoted-printable
 >> 
 >> I learned of a forthcoming RFC covering SCSI over IP from IBM and Cisco =
 >> a couple of weeks ago.  Has anyone heard about this?  Has the RFC been =
 >> submitted yet?   Are there any web sites with more information?
 >> 
 >> Jon William Toigo
 >> Independent Consultant and Author
 >> jtoigo@intnet.net
 >> 
 >> ------=_NextPart_000_04A8_01BFAEDF.0B3AB4C0
 >> Content-Type: text/html;
 >> 	charset="iso-8859-1"
 >> Content-Transfer-Encoding: quoted-printable
 >> 
 >> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 >> <HTML><HEAD>
 >> <META content=3D"text/html; charset=3Diso-8859-1" =
 >> http-equiv=3DContent-Type>
 >> <META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
 >> <STYLE></STYLE>
 >> </HEAD>
 >> <BODY bgColor=3D#ffffff>
 >> <DIV><FONT face=3DArial size=3D2>I learned of a forthcoming RFC covering =
 >> SCSI over=20
 >> IP from IBM and Cisco a couple of weeks ago.&nbsp; Has anyone heard =
 >> about=20
 >> this?&nbsp; Has the RFC been submitted yet?&nbsp;&nbsp; Are there any =
 >> web sites=20
 >> with more information?</FONT></DIV>
 >> <DIV>&nbsp;</DIV>
 >> <DIV><FONT face=3DArial size=3D2>Jon William Toigo</FONT></DIV>
 >> <DIV><FONT face=3DArial size=3D2>Independent Consultant and =
 >> Author</FONT></DIV>
 >> <DIV><FONT face=3DArial size=3D2><A=20
 >> href=3D"mailto:jtoigo@intnet.net">jtoigo@intnet.net</A></FONT></DIV></BOD=
 >> Y></HTML>
 >> 
 >> ------=_NextPart_000_04A8_01BFAEDF.0B3AB4C0--



From owner-ietf-outbound  Tue Apr 25 21:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA03187
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 21:50:02 -0400 (EDT)
Received: from npax.cavebear.com (npax.cavebear.com [192.203.17.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02142
	for <ietf@ietf.org>; Tue, 25 Apr 2000 21:42:18 -0400 (EDT)
Received: from localhost (karl@localhost)
	by npax.cavebear.com (8.9.3/8.9.3) with ESMTP id SAA05666
	for <ietf@ietf.org>; Tue, 25 Apr 2000 18:41:47 -0700
Date: Tue, 25 Apr 2000 18:41:46 -0700 (PDT)
From: Karl Auerbach <karl@CaveBear.com>
Reply-To: Karl Auerbach <karl@CaveBear.com>
To: IETF <ietf@ietf.org>
Subject: RE: runumbering (was:  Re: IPv6: Past mistakes repeated?)
In-Reply-To: <BB61526CDE70D2119D0F00805FBECA2F16967274@RED-MSG-55>
Message-ID: <Pine.LNX.4.21.0004251835590.5631-100000@npax.cavebear.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


> Turn it any way you want, TCP sessions can only survive renumbering through
> end to end mechanisms...

Which raises the interesting (to me anyway) question: Is there value in
considering a new protocol, layered on top of TCP, but beneath new
applications, that provides an "association" the life of which transcends
the TCP transports upon which it is constructed?

I believe that if we had such a protocol that it would be a useful tool to
solve many of the juggling acts that transpire under the heading of
"mobile networking" as well as providing a way to continue (or
"resume") connectivity after IP address changes.

(I will, of course, be suitably embarrassed if someone points out that
work is already going on to do this.)

		--karl--




From owner-ietf-outbound  Tue Apr 25 22:50:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA05109
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 22:50:02 -0400 (EDT)
Received: from mail.perspex.com (IDENT:tlilley@mail.perspex.com [12.5.16.108])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05066
	for <ietf@ietf.org>; Tue, 25 Apr 2000 22:47:01 -0400 (EDT)
Received: from localhost (tlilley@localhost) by mail.perspex.com (8.8.7/8.7.3) with SMTP id CAA00312; Wed, 26 Apr 2000 02:49:32 GMT
Date: Wed, 26 Apr 2000 02:49:32 +0000 (/etc/localtime)
From: Tripp Lilley <tlilley@perspex.com>
To: Karl Auerbach <karl@CaveBear.com>
cc: IETF <ietf@ietf.org>
Subject: RE: runumbering (was:  Re: IPv6: Past mistakes repeated?)
In-Reply-To: <Pine.LNX.4.21.0004251835590.5631-100000@npax.cavebear.com>
Message-ID: <Pine.LNX.3.96.1000426023756.32487M-100000@mail.perspex.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Tue, 25 Apr 2000, Karl Auerbach wrote:

> Which raises the interesting (to me anyway) question: Is there value in
> considering a new protocol, layered on top of TCP, but beneath new
> applications, that provides an "association" the life of which transcends
> the TCP transports upon which it is constructed?
> 
> I believe that if we had such a protocol that it would be a useful tool to
> solve many of the juggling acts that transpire under the heading of
> "mobile networking" as well as providing a way to continue (or
> "resume") connectivity after IP address changes.

Like you, I'll shuffle away in embarassment if this is already going on,
but it seems to me a heck of a good idea. I really don't like the idea of
tunnelling all the way back home to my measly DSL line when I'm sitting at
Interop behind a pair of DS3's, just so I can keep my sessions persistent
:)

I once accidently put my Sparc to sleep before I left for the evening, and
came back in the morning, realizing my mistake. I unslept it, and my ssh
session back home was still kicking. I was pleasantly surprised.

I shouldn't have been.

That is, that's the way it should work... I should be able to put my
laptop to sleep, hop on the plane, land in San Francisco, pull it back
out, unsleep it, and pick up where I left off, _without_ tunneling all the
way back home (ie: MobileIP). That's about as bad as going through MAE
East just to get to the ISP down the street...

And, yes, I'd gladly implement apps that were "association-aware", if such
a mechanism existed (and, Karl, if it doesn't exist, and you start hacking
it out, I'll write "running code" for ya :) ).

-- 
   Tripp Lilley  *  tripp@perspex.com  *  http://stargate.sg505.net/~tlilley/
------------------------------------------------------------------------------
  "I get a lot of letters like, 'Dear John, I've got a dead alien. What
   should I do with it?'  One word: barbecue!"

   - John Lovitz, A Yellow Pages commercial



From owner-ietf-outbound  Tue Apr 25 23:10:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA05441
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 23:10:02 -0400 (EDT)
Received: from leonid.genesyslab.com (pbinat33.genesyslab.com [209.233.177.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05343
	for <ietf@ietf.org>; Tue, 25 Apr 2000 23:02:12 -0400 (EDT)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id TAA21976
	for ietf@ietf.org; Tue, 25 Apr 2000 19:55:02 -0700
Date: Tue, 25 Apr 2000 19:55:02 -0700
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200004260255.TAA21976@leonid.genesyslab.com>
To: ietf@ietf.org
Subject: Re: NAT->IPv6
X-Loop: ietf@ietf.org

>From: "Charles E. Perkins" <charliep@iprg.nokia.com>
>
>If we get to a model where large new domains use IPv6 addressing
>with NAT to global IPv4 address space, that would be quite useful.
>Before too long, services will appear on the IPv6 network that
>can't get the IPv4 global addresses they need.

   I asked my friends who manages corporate network - "how long" ?
He answered - "why ? I have 3 big outside servers and 1000 desktops.
I need only 5 not NATted Internet addresses and 128 NATted...
And NAT is very power security firewall for me  - I don't need to 
keep eye on desktops!"

		       - Leonid Yegoshin, LY22



From owner-ietf-outbound  Tue Apr 25 23:20:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA05635
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 23:20:02 -0400 (EDT)
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05545
	for <ietf@ietf.org>; Tue, 25 Apr 2000 23:16:39 -0400 (EDT)
Received: (from bmanning@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id UAA03931;
	Tue, 25 Apr 2000 20:16:11 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200004260316.UAA03931@zephyr.isi.edu>
Subject: Re: runumbering (was:  Re: IPv6: Past mistakes repeated?)
To: karl@CaveBear.com
Date: Tue, 25 Apr 2000 20:16:10 -0700 (PDT)
Cc: ietf@ietf.org (IETF)
In-Reply-To: <Pine.LNX.4.21.0004251835590.5631-100000@npax.cavebear.com> from "Karl Auerbach" at Apr 25, 2000 06:41:46 PM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

% > Turn it any way you want, TCP sessions can only survive renumbering through
% > end to end mechanisms...
% 
% Which raises the interesting (to me anyway) question: Is there value in
% considering a new protocol, layered on top of TCP, but beneath new
% applications, that provides an "association" the life of which transcends
% the TCP transports upon which it is constructed?
% 
% I believe that if we had such a protocol that it would be a useful tool to
% solve many of the juggling acts that transpire under the heading of
% "mobile networking" as well as providing a way to continue (or
% "resume") connectivity after IP address changes.
% 
% (I will, of course, be suitably embarrassed if someone points out that
% work is already going on to do this.)
% 
% 		--karl--


 The most visable one was implemented at UCLA in 1996. Built using 
 a per-session 32bit sequence. My idea was to use the DNS lable instead
 of a fixed 32bit number. A bit harder... :)



--bill



From owner-ietf-outbound  Tue Apr 25 23:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA05805
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 23:30:03 -0400 (EDT)
Received: from leonid.genesyslab.com (pbinat33.genesyslab.com [209.233.177.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05691
	for <ietf@ietf.org>; Tue, 25 Apr 2000 23:22:15 -0400 (EDT)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id UAA22050
	for ietf@ietf.org; Tue, 25 Apr 2000 20:20:39 -0700
Date: Tue, 25 Apr 2000 20:20:39 -0700
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200004260320.UAA22050@leonid.genesyslab.com>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
X-Loop: ietf@ietf.org

>From: Keith Moore <moore@cs.utk.edu>
>
>> If people's livelihood depends on something, they're more likely to insure
>> it actually works.
>
>that's a good point.  but it's one thing to make sure that DNS mappings
>for "major" services are correct, and quite another to make sure that
>the DNS mappings are correct in both directions for every single host.
>
>even the DNS names for major services may not be well maintained.
>at one time I did a survey of the reasons for mail bounces
>for one of my larger mailing lists.  about half of the mail bounces
>seemed to be due to configuration errors.  about half of those
>seemed to be due to DNS configuration errors - e.g. MX records pointing
>to the wrong host, zone replicas not being kept in sync, zone
>replicas which were different but with the same serial number.
>
>> In your view, what is it in the DNS protocol(s) that results in a lack of
>> reliability?
>
>the reliability problems are mostly not the protocol...though the protocol
>does have limitations if you want to use it (as some have proposed) to
>support host or process mobility.  and in the face of even moderate
>packet losses DNS queries can take a very long time.
>
>mainly it's the fact that DNS is maintained as a separate entity.
>if you really want it to be in sync with reality, you need some
>mechanisms to ensure that updates happen automagically, and/or that
>configuration errors are automatically and quickly detected and
>the information about the error gets to the person who can fix it.

  Problems with DNS maintainance arise from fact that DNS should be
maintained manual. If we return back to routing addresses resolution
it can be deployed on maintainless basis because all needed information
already concentrated in routers. There is not any human-like names here
and allocation of route addresses may be done automatic (on tree base
strategy from some root point in network).

		       - Leonid Yegoshin, LY22



From owner-ietf-outbound  Tue Apr 25 23:40:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA06442
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 23:40:04 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06095
	for <ietf@ietf.org>; Tue, 25 Apr 2000 23:31:18 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id XAA04005;
        Tue, 25 Apr 2000 23:29:13 -0400 (EDT)
Message-Id: <200004260329.XAA04005@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Paul Francis <pfrancis@ACIRI.ORG>
cc: francis@ecal.com, narten@hygro.adsl.duke.edu, ietf@ietf.org
Subject: Re: runumbering (was: Re: IPv6: Past mistakes repeated?) 
In-reply-to: Your message of "Tue, 25 Apr 2000 13:53:40 PDT."
             <200004252053.NAA40544@baboon.aciri.org> 
Date: Tue, 25 Apr 2000 23:29:13 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> I have a hard time believing that your average IP net manager
> wouldn't prefer to run an IPv6-IPv6 NAT box (lets call this
> NATv6) at her ISP boundary rather than do site-wide renumbering.

some of the applications that will motivate the deployment of
IPv6 will be those that do not work with NAT.  (if they do work
with NAT, it's probably easier to just use IPv4.)

so it's quite likely that whereas imposing a NAT box on IPv4 users
wouldn't break many apps using IPv4, imposing a NAT box on IPv6 users
will break many of the apps using IPv6.

also, people using NATs are starting to become aware of the problems
that they cause - particularly those trying to build VPNs between
multiple NATted networks.  so by the time there's enough v6 
deployment for people to have to renumber, enough people will have 
been burned by NATs that won't want to repeat that experience.

Keith



From owner-ietf-outbound  Tue Apr 25 23:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA06714
	for ietf-outbound.10@ietf.org; Tue, 25 Apr 2000 23:50:02 -0400 (EDT)
Received: from postoffice.cisco.com (postoffice.cisco.com [171.69.198.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06581
	for <ietf@ietf.org>; Tue, 25 Apr 2000 23:44:49 -0400 (EDT)
Received: from [10.19.130.188] (deering-dsl3.cisco.com [10.19.130.188]) by postoffice.cisco.com (8.8.7-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id UAA14707; Tue, 25 Apr 2000 20:44:17 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@postoffice
Message-Id: <v04220814b52c114f7dfe@[10.19.130.188]>
In-Reply-To: <3905DD53.ACE85C3B@nominum.com>
References: <200004251548.IAA08741@zed.isi.edu>
 <v04220801b52b78f8ac20@[10.19.130.188]> <3905DD53.ACE85C3B@nominum.com>
Date: Tue, 25 Apr 2000 20:45:07 -0700
To: "David R. Conrad" <David.Conrad@nominum.com>
From: Steve Deering <deering@cisco.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 11:00 AM -0700 4/25/00, David R. Conrad wrote:
> > At 8:48 AM -0700 4/25/00, Bill Manning wrote:
> > >and this is different from only carrying the 253 usable /8 prefixes in
> > >IPv4 how?
> > 
> > The set of customers who have addresses under a given IPv4 /8 prefix greater
> > than 127 do not all aggregate into a single topological subregion (e.g., a
> > single ISP), and therefore more granular routes must be widely disseminated
> > to make those customers reachable.  That's the difference.
>
>No.  This is a historical feature that IPv6 alleviates by being able to start
>over with a clean slate.  You could (at least theoretically) emulate this in
>v4.

Of course.  I interpreted Bill's question as how would this be different
than limiting IPv4 prefix advertisements to only /8s *today*, i.e., without
renumbering the IPv4 Internet, so I answered accordingly.  I didn't think
to interpret the question the way you did, because the answer is so obvious
it wouldn't have made sense to ask.

>The difference is that v6 gives you the option of significantly more TLAs than
>v4 can ever have.  Of course, this isn't really a feature.

Right.  IPv4 could in theory have 2^32 TLAs and IPv6 could in theory have
2^128 TLAs.  Are you saying that 2^32 TLAs would be OK?

Sheesh -- we get flamed for trying to impose a limit on the number of TLAs
and we get flamed for the possibility that the number TLAs might not be
limited...

Steve



From owner-ietf-outbound  Wed Apr 26 00:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA06890
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 00:00:06 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06781
	for <ietf@ietf.org>; Tue, 25 Apr 2000 23:52:40 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id XAA04143;
        Tue, 25 Apr 2000 23:51:17 -0400 (EDT)
Message-Id: <200004260351.XAA04143@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Karl Auerbach <karl@CaveBear.com>
cc: IETF <ietf@ietf.org>
Subject: Re: runumbering (was: Re: IPv6: Past mistakes repeated?) 
In-reply-to: Your message of "Tue, 25 Apr 2000 18:41:46 PDT."
             <Pine.LNX.4.21.0004251835590.5631-100000@npax.cavebear.com> 
X-SUBJECT-MSG-FROM: Karl Auerbach <karl@CaveBear.com> 
Date: Tue, 25 Apr 2000 23:51:17 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Which raises the interesting (to me anyway) question: Is there value in
> considering a new protocol, layered on top of TCP, but beneath new
> applications, that provides an "association" the life of which transcends
> the TCP transports upon which it is constructed?

been there, done that.  yes, it is valuable.  but it is expensive
in terms of the amount of protocol overhead and support that you 
need to make it work reliably in the face of various failures.
and it can be slow to recover from such failures.

for instance, you have to build your own data acks on top of TCP,
because if the other end of a connection changes IP addresses you
cannot assume that any data already acknowledged at the TCP level
was actually received by the application at the other end...and 
you therefore have to keep track of data that is unacknowleged by the 
other end in case you have to resynchronize.  

and you need above-TCP keepalives and redirects.

and you need a separate mechanism to keep track of the current
IP address and port number for each of your connection endpoints...
and which gets updated independently (in case your connection
with a peer drops before it has a chance to tell you where it's
moving to)  this separate mechanism has its own failure modes, 
and parts of that mechanism might also be mobile.

if you had to build mobility entirely at the above-tcp level
this might be a useful approach.  but there are better ways to 
implement mobile networking.

Keith



From owner-ietf-outbound  Wed Apr 26 00:20:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA07312
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 00:20:02 -0400 (EDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07194
	for <ietf@ietf.org>; Wed, 26 Apr 2000 00:14:58 -0400 (EDT)
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 VAA11290;
	Tue, 25 Apr 2000 21:13:53 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.9.3/8.9.3-VIRSCAN) id UAA10418;
	Tue, 25 Apr 2000 20:17:11 -0700
X-Virus-Scanned:  Tue, 25 Apr 2000 20:17:11 -0700 Nokia Silicon Valley Email Exploit Scanner
Received: from <charliep@iprg.nokia.com> (maxdialin8.iprg.nokia.com [205.226.20.238]) by darkstar.iprg.nokia.com  SMTP/WTS (12.69)
 xma010151; Tue, 25 Apr 00 20:17:04 -0700
Message-ID: <39066C19.6E91B23D@iprg.nokia.com>
Date: Tue, 25 Apr 2000 21:10:01 -0700
From: "C. Perkins/D. Reese" <charliep@iprg.nokia.com>
Reply-To: charliep@iprg.nokia.com
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Tripp Lilley <tlilley@PERSPEX.COM>
CC: IETF <ietf@ietf.org>
Subject: Re: runumbering (was:  Re: IPv6: Past mistakes repeated?)
References: <Pine.LNX.3.96.1000426023756.32487M-100000@mail.perspex.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


Hello again,

From the note below, it's obvious that there are some misconceptions
about Mobile IP that I'd like to correct.

Tripp Lilley wrote:

> That is, that's the way it should work... I should be able to put my
> laptop to sleep, hop on the plane, land in San Francisco, pull it back
> out, unsleep it, and pick up where I left off, _without_ tunneling all the
> way back home (ie: MobileIP). That's about as bad as going through MAE
> East just to get to the ISP down the street...

In the mobile-ip working group, we had many discussions in the years
before RFC 2002 about this problem.  We also had a solution, called
"route optimization".  The decision was taken to standardize the
"base protocol" and work on standardizing "route optimization"
later.  The reason was exactly because doing this sort of route
optimization needs kernel modifications.

I think that all the details have been worked out pretty well for
Mobile IP route optimization.  The specification has been implemented,
works, and may eventually get through last call if there is sufficient
interest.  The strategy to isolate route optimization from the base
Mobile IP protocol may be questioned with the benefit of hindsight,
but after all there are now millions of implementations of Mobile IP
deployed (according to mail sent to the mobile-ip mailing list).
We don't know if that number would be bigger or smaller if the
working group had included route optimization features with
the base protocol.

I think it would be preferable to put effort behind a known pretty-good
approach that takes modifications to the networking stack, instead
of starting over on a relatively unknown approach that also requires
modifications to the networking stack.  By known pretty-good, I mean
that it has a good story on security, has been studied for scalability,
and does the job.  Many other approaches could be taken with more
engineering effort, but I don't think any of the other possibilties are
anywhere near as close to being finished.  If there is something about
Mobile IP route optimization that should be improved, let's talk
about it; but let's also recognize that a lot of work has been done.

Regards,
Charlie P.




From owner-ietf-outbound  Wed Apr 26 00:30:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA07572
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 00:30:02 -0400 (EDT)
Received: from npax.cavebear.com (npax.cavebear.com [192.203.17.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07245
	for <ietf@ietf.org>; Wed, 26 Apr 2000 00:17:05 -0400 (EDT)
Received: from localhost (karl@localhost)
	by npax.cavebear.com (8.9.3/8.9.3) with ESMTP id VAA06247;
	Tue, 25 Apr 2000 21:16:24 -0700
Date: Tue, 25 Apr 2000 21:16:24 -0700 (PDT)
From: Karl Auerbach <karl@CaveBear.com>
Reply-To: Karl Auerbach <karl@CaveBear.com>
To: Keith Moore <moore@cs.utk.edu>
cc: IETF <ietf@ietf.org>
Subject: Re: runumbering (was: Re: IPv6: Past mistakes repeated?) 
In-Reply-To: <200004260351.XAA04143@astro.cs.utk.edu>
Message-ID: <Pine.LNX.4.21.0004252109080.6184-100000@npax.cavebear.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


> > Which raises the interesting (to me anyway) question: Is there value in
> > considering a new protocol, layered on top of TCP, but beneath new
> > applications, that provides an "association" the life of which transcends
> > the TCP transports upon which it is constructed?
> 
> been there, done that.  yes, it is valuable.  but it is expensive
> in terms of the amount of protocol overhead and support that you 
> need to make it work reliably in the face of various failures.
> and it can be slow to recover from such failures.
> 
> for instance, you have to build your own data acks on top of TCP,

There is a protocol design that did this, but we tend to shield our eyes
when we look that way - OSI Session layer.  It was a hideous thing indeed
to read on paper and way overburdened with options.  But when one got down
to the wire, the actual protocol traffic was small.  It didn't try to do
any kind of reliability or sequencing or even sensing that a transport had
died.  Rather it maintained a sequence of restart points - and it was only
at those points (which were triggered by the application saying "mark this
point") that there were things that could be called "acks".

So what I am suggesting is that it seems that there is evidence that one
can do an "association" protocol that is relatively lightweight in terms
of machinery, packets, packet headers, and end-node state if one leaves
the heavy lifting of reliability to the underlying TCP protocol.

I bet Marshall Rose has some good comments on this as he actually went and
did some of this.

(By-the-way, I'm not in any way suggesting OSI Session, I'm only trying to
learn from the past.)

		--karl--





From owner-ietf-outbound  Wed Apr 26 01:00:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA08034
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 01:00:02 -0400 (EDT)
Received: from leonid.genesyslab.com (pbinat33.genesyslab.com [209.233.177.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07997
	for <ietf@ietf.org>; Wed, 26 Apr 2000 00:58:38 -0400 (EDT)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id VAA22190
	for ietf@ietf.org; Tue, 25 Apr 2000 21:57:44 -0700
Date: Tue, 25 Apr 2000 21:57:44 -0700
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200004260457.VAA22190@leonid.genesyslab.com>
To: ietf@ietf.org
Subject: Re: NAT->IPv6
X-Loop: ietf@ietf.org

>From: John Stracke <francis@ecal.com>
>
>"J. Noel Chiappa" wrote:
>
>> So, you're the CIO for Foondoggle Corp, and you're trying to figure out
>> whether to spend any of your Q3 funds on IPv6 conversion. Let's see, benefits
>> are not very many (autoconfig may be the best one), and the cost is
>> substantial.
>
>Sure.  Then you buy out Moondoggle Corp, which used some of the same private IP
>numbers you did, and you're faced with having to renumber everything.  While
>you're at it, you decide to convert both networks to v6 so it'll be easier next
>time.
>
>(Yes, I know you could put a NAT between the two former companies; but it'll
>*hurt*.)

   Once in company where I worked somebody brought a virus and it crashed
a lot of Windows host. I don't remember details about it's fast propogation
but I remember how terrific IS staff wanted to put firewalls/NATs between
each floor ! They considered it as the only warranty and _asked_ money
for that.

		       - Leonid Yegoshin, LY22




From owner-ietf-outbound  Wed Apr 26 01:50:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA13483
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 01:50:03 -0400 (EDT)
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13062
	for <ietf@ietf.org>; Wed, 26 Apr 2000 01:41:13 -0400 (EDT)
Received: (from bmanning@localhost)
	by zephyr.isi.edu (8.8.7/8.8.6) id WAA09193;
	Tue, 25 Apr 2000 22:40:43 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200004260540.WAA09193@zephyr.isi.edu>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
To: Valdis.Kletnieks@vt.edu
Date: Tue, 25 Apr 2000 22:40:42 -0700 (PDT)
Cc: ietf@ietf.org, bmanning@ISI.EDU
In-Reply-To: <200004251642.e3PGg2B26284@black-ice.cc.vt.edu> from "Valdis.Kletnieks@vt.edu" at Apr 25, 2000 12:41:50 PM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

On Tue, 25 Apr 2000 08:18:20 PDT, Bill Manning said:
> 	The 2q2000 data for the in-addr tree shows 77402 unique
> 	servers answering for 693,337 zones.  
> 	19515 servers blocked/refused data. Of the 57887 that 
> 	answered, these are the numbers for improper configuration:
> 
> 	BAD_SERVER:	4278
> 	FORMERR:	8
> 	NXDOMAIN:	28
> 
> 	So, of the 57,887 visable servers, 4314 are improperly configured 
> 	in the visable in-addr.arpa. tree.  Thats 7.45% of the
> 	servers being "not well maintained".  I know of no similar data
>	(... for forward data ...)

	Rather than continue to whine about lack of data, this is 
	the .US forward zone data:

	9928 unique servers answering for 33299 zones. 2165 servers blocked
	or refused data. Of the 7763 that answered, these are the numbers
	for improper configuration:
	
	BAD_SERVER:	14
	FORMERR:	2
	NXDOMAIN:	29

	So, of the 7763 visable servers, 45 are improperly configured in the
	visable US. tree. Thats 4.53% of those servers being "not well
	maintained.

	Keith, These two data points seem to bear your assertion out.

	in-addr.arpa	7.45% - poorly managed
	us.		4.53% - poorly managed


--bill



From owner-ietf-outbound  Wed Apr 26 02:00:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA13581
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 02:00:03 -0400 (EDT)
Received: from lint.cisco.com (lint.cisco.com [171.68.224.209])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13450
	for <ietf@ietf.org>; Wed, 26 Apr 2000 01:47:52 -0400 (EDT)
Received: from elearhomepc (elear-dsl3.cisco.com [10.19.144.52]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id WAA02171; Tue, 25 Apr 2000 22:46:47 -0700 (PDT)
Message-ID: <001501bfaf43$127e4d00$3490130a@cisco.com>
From: "Eliot Lear" <lear@cisco.com>
To: "Leonid Yegoshin" <egoshin@genesyslab.com>
Cc: <ietf@ietf.org>
References: <200004260457.VAA22190@leonid.genesyslab.com>
Subject: Re: NAT->IPv6
Date: Tue, 25 Apr 2000 22:48:39 -0700
Organization: Cisco Systems
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

It is a complete fallacy that NAT provides any sort of security.  It does
no such thing.  Security is provide by a firewall, and (more importantly)
by strong security policies that are policed and enforced.

----- Original Message -----
From: Leonid Yegoshin <egoshin@genesyslab.com>
Newsgroups: cisco.external.ietf
Sent: Tuesday, April 25, 2000 10:11 PM
Subject: Re: NAT->IPv6


> >From: John Stracke <francis@ecal.com>
> >
> >"J. Noel Chiappa" wrote:
> >
> >> So, you're the CIO for Foondoggle Corp, and you're trying to figure
out
> >> whether to spend any of your Q3 funds on IPv6 conversion. Let's see,
benefits
> >> are not very many (autoconfig may be the best one), and the cost is
> >> substantial.
> >
> >Sure.  Then you buy out Moondoggle Corp, which used some of the same
private IP
> >numbers you did, and you're faced with having to renumber everything.
While
> >you're at it, you decide to convert both networks to v6 so it'll be
easier next
> >time.
> >
> >(Yes, I know you could put a NAT between the two former companies; but
it'll
> >*hurt*.)
>
>    Once in company where I worked somebody brought a virus and it crashed
> a lot of Windows host. I don't remember details about it's fast
propogation
> but I remember how terrific IS staff wanted to put firewalls/NATs between
> each floor ! They considered it as the only warranty and _asked_ money
> for that.
>
>        - Leonid Yegoshin, LY22
>



From owner-ietf-outbound  Wed Apr 26 03:20:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA20840
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 03:20:02 -0400 (EDT)
Received: from lint.cisco.com (lint.cisco.com [171.68.224.209])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20789
	for <ietf@ietf.org>; Wed, 26 Apr 2000 03:15:10 -0400 (EDT)
Received: from elearhomepc (elear-dsl3.cisco.com [10.19.144.52]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id AAA27988; Wed, 26 Apr 2000 00:14:06 -0700 (PDT)
Message-ID: <001a01bfaf4f$44cc9a80$3490130a@cisco.com>
From: "Eliot Lear" <lear@cisco.com>
To: "Bill Manning" <bmanning@ISI.EDU>
Cc: <ietf@ietf.org>, <vixie@vix.com>
References: <200004251642.e3PGg2B26284@black-ice.cc.vt.edu> <200004260540.WAA09193@zephyr.isi.edu>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Date: Wed, 26 Apr 2000 00:15:57 -0700
Organization: Cisco Systems
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

From: Bill Manning <bmanning@ISI.EDU>
> So, of the 7763 visable servers, 45 are improperly configured in the
> visable US. tree. Thats 4.53% of those servers being "not well
> maintained.
>
> Keith, These two data points seem to bear your assertion out.

It is always possible to do something poorly.  You can take the best
engineered product and misconfigure it, or otherwise not maintain it.
Sorta like not changing the oil.  On the other hand, how many times do you
see a name service failure for someone in the Keynote 40?  How often do you
get a failure for a site that uses a commercial service like Akamai?  If
you still get lots of failures when people are using the mechanism as
recommended, then the mechanism itself is poorly designed.  It also strikes
me that DNS is continuing to mature, and that things are getting better, as
more products come to the market, but this is more gut feel.

There are some open questions out there: does DNS provide sufficient
granularity?  Are its semantics rich enough for a mobile world?  People are
currently playing tricks with DNS that PVM had not envisioned, and Paul
Vixie loves to say something like, "DNS is not the droid you're looking
for" (forgive me, Paul, if I didn't get that quite right).

Just some thoughts...




From owner-ietf-outbound  Wed Apr 26 03:30:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA20984
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 03:30:01 -0400 (EDT)
Received: from hqfwa01.libertel.nl (hqfwa01.libertel.nl [194.229.118.20])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA20790
	for <ietf@ietf.org>; Wed, 26 Apr 2000 03:15:10 -0400 (EDT)
From: e.brouwers@libertel.nl
Received: by hqfwa01.libertel.nl; id AA23816; Wed, 26 Apr 2000 09:13:31 +0200
Received: from somewhere by smtpxd
Message-Id: <9EB2E2430BE9D311AD3A00508B116E0E4B45FF@SMTR-EXH3.LIBERTEL>
To: ietf@ietf.org
Subject: Frame relay over GRE/IP
Date: Wed, 26 Apr 2000 09:14:31 +0200
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Hello,

I've some questions about transporting frame relay over IP (I know, the
world is getting crazy):

1. Does anybody have any experience with encapsulation of frame relay by
means of GRE with IPv4 as delivery protocol (RFC1701, 1702, 2784)?

2. Why shouldn't I try to transport FR (FRF1.1) over IP? What are the cons?

3. Does anybody know, why the sequence number has been deprecated in RFC
2784?

4. Are there any vendors which implement GRE according to the latest RFC
2784?

Regards,

Eric




Eric Brouwers		
Libertel, Avenue Ceramique 300, 6221 KX  Maastricht, the Netherlands

phone	+31 43 355 7717
fax	+31 43 355 5566
mobile	+31 43 355 6717
e-mail	e.brouwers@libertel.nl



From owner-ietf-outbound  Wed Apr 26 04:22:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA21541
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 04:22:07 -0400 (EDT)
Received: from mail.ubn.nl (mail.ubn.nl [194.151.95.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21449
	for <ietf@ietf.org>; Wed, 26 Apr 2000 04:16:43 -0400 (EDT)
Received: from ubn005s.UBN-NL (ms-exchange [194.22.26.3])
	by mail.ubn.nl (8.8.6/8.8.6) with ESMTP id KAA28218;
	Wed, 26 Apr 2000 10:16:43 +0200 (MET DST)
Received: by ubnnlgvpbnt01.ubn-nl with Internet Mail Service (5.5.2448.0)
	id <23WLQLYZ>; Wed, 26 Apr 2000 10:16:52 +0200
Message-ID: <2E7A7F3C4F68D311910900805FA7168E81C003@ubn001v3.ubn-nl>
From: "Connelly, M " <m.connelly@kpn.com>
To: ietf@ietf.org,
        "'dahigginbotham@ncdragonfly.com'"
	 <dahigginbotham@ncdragonfly.com>
Subject: AW: IPv6: Past mistakes repeated?
Date: Wed, 26 Apr 2000 10:16:47 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

On the subject of infinite possibilities - given that there are an infinite
number of of possible mistakes and only one correct solution, it is
statistically impossible to do anything right.

IP4 was definitely a mistake. Whatever replaces it will invariably also be a
mistake.  Besides, if everything was done correctly this forum would be very
dull!

-Michael C

> ----------
> Van: 	David A Higginbotham[SMTP:dahigginbotham@ncdragonfly.com]
> Verzonden: 	maandag 24 april 2000 13:22
> Aan: 	'Anthony Atkielski'; ietf@ietf.org
> Onderwerp: 	RE: IPv6: Past mistakes repeated?
> 
> I agree! Why create a finite anything when an infinite possibility exists?
> On another note, I have heard the argument that a unique identifier
> already
> exists in the form of a MAC address why not make further use of it?
> 
> David H
> 
> -----Original Message-----
> From: Anthony Atkielski [mailto:anthony@atkielski.com]
> Sent: Monday, April 24, 2000 6:05 AM
> To: ietf@ietf.org
> Subject: IPv6: Past mistakes repeated?
> 
> 
> What I find interesting throughout discussions that mention IPv6 as a
> solution for a shortage of addresses in IPv4 is that people
> see the problems with IPv4, but they don't realize that IPv6 will run into
> the same difficulties.  _Any_ addressing scheme that uses
> addresses of fixed length will run out of addresses after a finite period
> of
> time, and that period may be orders of magnitude
> shorter than anyone might at first believe.
> 
> Consider IPv4.  Thirty-two bits allows more than four billion individual
> machines to be addressed.  In theory, then, we should have
> enough IPv4 addresses for everyone until four billion machines are
> actually
> online simultaneously.  Despite this, however, we seem
> to be running short of addresses already, even though only a fraction of
> them are actually used.  The reason for this is that the
> address space is of finite size, and that we attempt to allocate that
> finite
> space in advance of actual use.
> 
> It should be clear that IPv6 will have the same problem.  The space will
> be
> allocated in advance.  Over time, it will become obvious
> that the original allocation scheme is ill-adapted to changing
> requirements
> (because we simply cannot foresee those requirements).
> Much, _much_ sooner than anyone expects, IPv6 will start to run short of
> addresses, for the same reason that IPv4 is running short.
> It seems impossible now, but I suppose that running out of space in IPv4
> seemed impossible at one time, too.
> 
> The allocation pattern is easy to foresee.  Initially, enormous subsets of
> the address space will be allocated carelessly and
> generously, because "there are so many addresses that we'll never run out"
> and because nobody will want to expend the effort to
> achieve finer granularity in the face of such apparent plenty.  This
> mistake
> will be repeated for each subset of the address space
> allocated, by each organization charged with allocating the space.  As a
> result, in a surprisingly short time, the address space
> will be exhausted.  This _always_ happens with fixed address spaces.  It
> seems to be human nature, but information theory has a hand
> in it, too.
> 
> If you need further evidence, look at virtual memory address spaces.  Even
> if a computer's architecture allows for a trillion bits
> of addressing space, it invariably becomes fragmented and exhausted in an
> amazingly short time.  The "nearly infinite space" allowed
> by huge virtual addresses turns out to be very finite and very limiting
> indeed.
> 
> The only real solution to this is an open-ended addressing scheme--one to
> which digits can be added as required.  And it just so
> happens that a near-perfect example of such a scheme is right in front of
> us
> all, in the form of the telephone system.  Telephone
> numbers have never had a fixed number of digits.  The number has always
> been
> variable, and has simply expanded as needs have changed
> and increased.  At one time, a four-digit number was enough to reach
> anyone.
> Then seven-digit numbers became necessary.  Then an
> area code became necessary.  And finally, a country code became necessary.
> Perhaps a planet code will be necessary at some point in
> the future.  But the key feature of the telephone system is that nobody
> ever
> decided upon a fixed number of digits in the beginning,
> and so there is no insurmountable obstacle to adding digits forever, if
> necessary.  Imagine what things would be like if someone had
> decided in 1900 that seven digits would be enough for the whole world, and
> then equipment around the world were designed only to
> handle seven digits, with no room for expansion.  What would happen when
> it
> came time to install the 10,000,000th telephone, or when
> careless allocation exhausted the seven-digit space?
> 
> Anyway, some keys to a successful addressing scheme, in my opinion, are as
> follows (but the first is the only mandatory feature, I
> think):
> 
> 1. The number of digits used for addressing is not limited by the
> addressing
> protocol.
> 2. Every machine in the network need only know in detail about other
> points
> in the network that have the same high-order digits in
> their addresses.
> 3. There is a distinction for every machine between "local" addresses
> (those
> that implicitly have the same high-order digits as the
> address of the machine in question) and "remote" addresses (those that
> have
> different high-order digits).
> 
> With such an address scheme, a single international body can allocate one
> digit to each region of the world (the size of the regions
> is irrelevant).  Beneath that, other, more local bodies, one per initial
> digit, can allocate more digits below that.  There is no
> need for anyone to allocate the entire address space in advance, so there
> is
> no need to worry about problems with the initial
> allocation that will have to be fixed later.  And since the actual number
> of
> digits in a machine address is unlimited, different
> parts of the world, different companies, different organizations, etc.,
> can
> expand addresses as needed.  At any given time, the
> maximum number of digits would be fixed at some very high number (128
> decimal digits, perhaps), but if this ever became too
> limiting, it would be sufficient to simply up that number--no reallocation
> or modification of the address space would be necessary.
> 
> Imagine computers in the United States under such a scheme.  All IPtNG
> addresses (IPtNG=IP: the Next Generation--I have to call it
> something, right?) for the U.S. would start with one.  Since there are
> lots
> of computers in the U.S., you'd see addresses like:
> 
> 14872883747534 for a machine in San Jose
> 1487048377212  for a machine in Sacramento
> 1412278987831  for a machine in Los Angeles
> 1248819473     for a machine in Wyoming
> 134875810869   for a machine in Boston
> 
> ... and so on.  Notice that the lengths vary based on the number of
> machines
> in a given region--if you need more address space, you
> just add more digits.  Wyoming has relatively few machines, so addresses
> there are short.  San Jose has a zillion machines, so
> addresses there are long.
> 
> Now picture the small country of Vulgaria, and its address space:
> 
> 486174         for a machine in Vulgaria Minor (where most of the
> population
> lives)
> 48631          for a machine in Vulgaria Major
> 
> Vulgaria is a tiny country with only a few hundred machines.  The 4
> designates the region of the world in which Vulgaria is found.
> The 86 is allocated to all of Vulgaria.  The remaining digits are
> allocated
> within Vulgaria itself.
> 
> If you haven't already noticed, this pattern is essentially the one
> already
> in use for telephones.  It works extremely well.
> 
> Some might say that this ties the IP address to a geographical region.
> Well, yes, it does.  So what?  If you want to use IP for
> security (as in identifying individuals), you're making a mistake to begin
> with.  The address of a machine just locates it for
> routing purposes; it does not authenticate its identity.  If you want
> identity information for machines, you give them a separate
> "identity address" that follows them anywhere in the world, even if their
> IPtNG address changes.  And if you want identity
> information for people (which is often the real goal), you give _them_ an
> "identity address" that follows them anywhere in the
> world.
> 
> Here again, with respect to security, the telephone network sets the
> pattern: if you move, your telephone number changes, but your
> identity does not.  Nobody calls a telephone number and simply assumes the
> identity of the person who answers; normally an
> authentication process is carried out ("Can I speak to Jane?"), because
> everyone knows that a telephone number just gets you to a
> specific telephone, but not to a specific person.  Nobody lets you charge
> purchases to a specific credit card just because you are
> calling from a specific telephone--you still have to identify yourself.
> 
> Anyway, I suppose it's too late to change anything in IPv6, but I'm
> convinced that IPv6 will just show the same problems as IPv4,
> and it will be more like 20-40 years down the road, and not the billions
> of
> years that some people seem to assume.  I think that
> history shows that the leading mistake of all engineers is to
> underestimate
> future capacity needs, and I see that happening with
> IPv6, just as it did with IPv4 (and with Y2K, and with the IBM PC address
> space, and so on, and so on).  I just thought I'd add my
> $0.02.  Maybe I've overlooked something in IPv6, but I fear that I have
> not.
> 
> I'd be interested in hearing what others think of this potential problem.
> (Or at least correct me if I've overlooked something in
> IPv6 that will prevent the problems listed above from occurring.)
> 
>   -- Anthony
> 



From owner-ietf-outbound  Wed Apr 26 08:01:55 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA24247
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 08:00:02 -0400 (EDT)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24032
	for <ietf@ietf.org>; Wed, 26 Apr 2000 07:51:27 -0400 (EDT)
From: Dave_Lee@3com.com
Received: from new-york.3com.com (new-york.3com.com [129.213.157.12])
	by seattle.3com.com (8.8.8/8.8.8) with ESMTP id EAA20101;
	Wed, 26 Apr 2000 04:51:07 -0700 (PDT)
Received: from hqoutbound.ops.3com.com (hqoutbound.OPS.3Com.COM [139.87.48.104])
	by new-york.3com.com (8.8.8/8.8.8) with SMTP id EAA23525;
	Wed, 26 Apr 2000 04:51:06 -0700 (PDT)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999))  id 882568CD.00410433 ; Wed, 26 Apr 2000 04:50:09 -0700
X-Lotus-FromDomain: 3COM
To: jasen@pcpotato.com, jtoigo@intnet.net, ietf@ietf.org
cc: Barbara Denny <denny@3com.com>, ips@ece.cmu.edu
Message-ID: <882568CD.0041034D.00@hqoutbound.ops.3com.com>
Date: Wed, 26 Apr 2000 04:50:38 -0700
Subject: Re: SCSI over IP (fwd)
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org



For more information on the SCSI over IP (IP storage) proposed working group,
please see http://www.ece.cmu.edu/~ips.  The IBM/Cisco draft and other material
is there.



Date: Tue, 25 Apr 2000 17:13:07 -0600
From: Jasen Strutt <jasen@pcpotato.com>
To: Jon William Toigo <jtoigo@intnet.net>, ietf@ietf.org
Subject: Re: SCSI over IP

SCSIoIP
Who'd a thunk it....

I believe there are a few hash renditions of it at a higher level of networking
through distributed computing / storage and processing but lack the white papers
to send you on it. I'd be interested if anyone else has specifics on it.

Comments?

  ----- Original Message -----
  From: Jon William Toigo
  To: ietf@ietf.org
  Sent: Tuesday, April 25, 2000 3:52 PM
  Subject: SCSI over IP


  I learned of a forthcoming RFC covering SCSI over IP from IBM and Cisco a
couple of weeks ago.  Has anyone heard about this?  Has the RFC been submitted
yet?   Are there any web sites with more information?

  Jon William Toigo
  Independent Consultant and Author
  jtoigo@intnet.net






From owner-ietf-outbound  Wed Apr 26 09:11:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA25728
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 09:10:02 -0400 (EDT)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25592
	for <ietf@ietf.org>; Wed, 26 Apr 2000 09:05:07 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 79C524CE0F; Wed, 26 Apr 2000 09:05:04 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id JAA18294;
	Wed, 26 Apr 2000 09:05:03 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id A8C0035DC2; Wed, 26 Apr 2000 09:04:58 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: "Eliot Lear" <lear@cisco.com>
Cc: "Leonid Yegoshin" <egoshin@genesyslab.com>, ietf@ietf.org
Subject: Re: NAT->IPv6 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 26 Apr 2000 09:04:58 -0400
Sender: smb@research.att.com
Message-Id: <20000426130458.A8C0035DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <001501bfaf43$127e4d00$3490130a@cisco.com>, "Eliot Lear" writes:
>It is a complete fallacy that NAT provides any sort of security.  It does
>no such thing.  Security is provide by a firewall, and (more importantly)
>by strong security policies that are policed and enforced.

Eliot is absolutely right.  A NAT box *might* be part of a firewall, but by 
itself it isn't one.  It's no more secure, and often less so, than an 
application-level firewall.

The myth that NATs per se provide strong security is one of the greatest 
barriers to their elimination.

		--Steve Bellovin




From owner-ietf-outbound  Wed Apr 26 09:21:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA25919
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 09:20:04 -0400 (EDT)
Received: from sean.ebone.net (IDENT:root@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25873
	for <ietf@ietf.org>; Wed, 26 Apr 2000 09:17:41 -0400 (EDT)
Received: (from smd@localhost)
	by sean.ebone.net (8.9.3/8.9.3) id PAA06850;
	Wed, 26 Apr 2000 15:16:17 +0200 (CEST)
Date: Wed, 26 Apr 2000 15:16:17 +0200 (CEST)
From: Sean Doran <smd@ebone.net>
Message-Id: <200004261316.PAA06850@sean.ebone.net>
To: David.Conrad@nominum.com, deering@cisco.com
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org


Steve Deering writes:

| Sheesh -- we get flamed for trying to impose a limit on the number of TLAs
| and we get flamed for the possibility that the number TLAs might not be
| limited...

The salient point here is that the current inter-domain routing
architecture is not robust to growth in the number of entities
which are multihomed.   This is a failing of both IPv4 and IPv6.

There is no known dynamic IDR system which will do a substantially
better job with CIDR-style addressing, which both IPv4 and IPv6 
are "cursed" with.

However, there are known dynamic IDR systems which are robust to increasing
amounts of multihoming, however these generally require an addressing 
architecture that is fundamentally different from CIDR, and/or 
a scheme in which the host-router and router-router packet formats
differ significantly.

	Sean.



From owner-ietf-outbound  Wed Apr 26 09:31:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA26138
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 09:30:03 -0400 (EDT)
Received: from corpmail.galaxyscientific.com ([38.221.233.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25955
	for <ietf@ietf.org>; Wed, 26 Apr 2000 09:21:10 -0400 (EDT)
Received: from BELLOPEM (igate.tc.faa.gov [155.178.180.5]) by corpmail.galaxyscientific.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id 2KDCN17R; Wed, 26 Apr 2000 09:19:28 -0400
From: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
To: "Connelly; M " <m.connelly@kpn.com>, <ietf@ietf.org>,
        <dahigginbotham@ncdragonfly.com>
Subject: RE: IPv6: Past mistakes repeated?
Date: Wed, 26 Apr 2000 09:19:02 -0400
Message-ID: <PPECLLOGBEPHLOMKLNAMKEOKCAAA.Michael.CTR.Bellopede@tc.faa.gov>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <10076@tc.faa.gov>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I fear your logic is flawed.  If there are an infinite number of
possibilities, than not only are there infinite possible mistakes, but an
infinite number of good solutions.  Also, just because a solution is good,
does not mean it will or should last forever.

-Michael B. Bellopede
 Michael.CTR.Bellopede@tc.faa.gov
 "There is no spoon."

>-----Original Message-----
>From: Connelly; M [mailto:m.connelly@kpn.com]
>Sent: Wednesday, April 26, 2000 10:17 AM
>To: ietf@ietf.org; 'dahigginbotham@ncdragonfly.com'
>Subject: AW: IPv6: Past mistakes repeated?
>
>
>On the subject of infinite possibilities - given that there are an infinite
>number of of possible mistakes and only one correct solution, it is
>statistically impossible to do anything right.
>
>IP4 was definitely a mistake. Whatever replaces it will invariably also be
a
>mistake.  Besides, if everything was done correctly this forum would be
very
>dull!
>
>-Michael C
>
>> ----------
>> Van:  David A Higginbotham[SMTP:dahigginbotham@ncdragonfly.com]
>> Verzonden:    maandag 24 april 2000 13:22
>> Aan:  'Anthony Atkielski'; ietf@ietf.org
>> Onderwerp:    RE: IPv6: Past mistakes repeated?
>>
>> I agree! Why create a finite anything when an infinite possibility
exists?
>> On another note, I have heard the argument that a unique identifier
>> already
>> exists in the form of a MAC address why not make further use of it?
>>
>> David H
>>
>> -----Original Message-----
>> From: Anthony Atkielski [mailto:anthony@atkielski.com]
>> Sent: Monday, April 24, 2000 6:05 AM
>> To: ietf@ietf.org
.> Subject: IPv6: Past mistakes repeated?
>>
>>



From owner-ietf-outbound  Wed Apr 26 09:41:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA26391
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 09:40:03 -0400 (EDT)
Received: from fwns1.raleigh.ibm.com (fwns1d.raleigh.ibm.com [204.146.167.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26315
	for <ietf@ietf.org>; Wed, 26 Apr 2000 09:35:44 -0400 (EDT)
Received: from rtpmail01.raleigh.ibm.com (rtpmail01.raleigh.ibm.com [9.37.172.24])
	by fwns1.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id JAA22254;
	Wed, 26 Apr 2000 09:35:09 -0400
Received: from ludwigia.raleigh.ibm.com (ludwigia.raleigh.ibm.com [9.37.60.3])
	by rtpmail01.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id JAA33114;
	Wed, 26 Apr 2000 09:35:09 -0400
Received: from hygro.raleigh.ibm.com (IDENT:root@lig32-226-34-42.us.lig-dial.ibm.com [32.226.34.42]) by ludwigia.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id JAA26409; Wed, 26 Apr 2000 09:31:13 -0400
Received: from hygro.raleigh.ibm.com (IDENT:narten@localhost.localdomain [127.0.0.1])
	by hygro.raleigh.ibm.com (8.9.3/8.9.3) with ESMTP id JAA01189;
	Wed, 26 Apr 2000 09:32:45 -0400
Message-Id: <200004261332.JAA01189@hygro.raleigh.ibm.com>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: ietf@ietf.org, moore@cs.utk.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-Reply-To: Message from "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu> 
   of "Tue, 25 Apr 2000 15:42:31 EDT." <200004251942.PAA03466@ginger.lcs.mit.edu> 
Date: Wed, 26 Apr 2000 09:32:45 -0400
From: Thomas Narten <narten@raleigh.ibm.com>
X-Loop: ietf@ietf.org

> IPv6's claimed big advantage - a bigger address space - turns out
> not to be an advantage at all - at least in any stage much short of
> completely deployment.

Not surprisingly, I disagree.

> Here's why:

>     >> if you have a site which has more hosts than it can get external IPv4
>     >> addresses for, then as long as there are considerable numbers of IPv4
>     >> hosts a site needs to interoperate with, *deploying IPv6 internally to
>     >> the site does the site basically no good at all*.

Actually, in the above scenario, NAT is already a requirement for IPv4
communication with the outside world. So, if you switch to IPv6
internally, use IPv6-IPv4 NATPT (i.e., combination of NAT and IPv6 to
IPv4 translation) you have pretty much the same
functionality/limitation as with IPv4 NAT.

Now, consider someone in the process of deploying massive numbers of
devices (100's of millions) together with the infrastructure to
support them (e.g., wireless). With IPv4, they face not only the
necessity of using NAT to get to outside destinations, but also the
use of NAT _internally_ because there isn't enough private address
space to properly number the internal part of the infrastructure.

In this scenario, IPv6 internally at least gives them end-to-end ness
internally (plus scalability, more robustness, etc., etc.), something
the can't get with IPv4. And it gives them the same set of
issues/headaches when talking to the outside world that they would
have if just using IPv4.

I don't know about you, but it scares me to read the various forecasts
about how wireless will transform the landscape over the next few
years. E.g., more wireless phones with internet connectivity than
PCs. The numbers are just staggering and the associated demand for
addresses will be astonishing. We ain't seen nothing yet.

Thomas



From owner-ietf-outbound  Wed Apr 26 09:51:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA26613
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 09:50:03 -0400 (EDT)
Received: from fwns2.raleigh.ibm.com (fwns2d.raleigh.ibm.com [204.146.167.236])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26322
	for <ietf@ietf.org>; Wed, 26 Apr 2000 09:35:47 -0400 (EDT)
Received: from rtpmail03.raleigh.ibm.com (rtpmail03.raleigh.ibm.com [9.37.172.47])
	by fwns2.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id JAA24206;
	Wed, 26 Apr 2000 09:35:13 -0400
Received: from ludwigia.raleigh.ibm.com (ludwigia.raleigh.ibm.com [9.37.60.3])
	by rtpmail03.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id JAA34668;
	Wed, 26 Apr 2000 09:35:13 -0400
Received: from hygro.raleigh.ibm.com (IDENT:root@lig32-226-34-42.us.lig-dial.ibm.com [32.226.34.42]) by ludwigia.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id JAA26413; Wed, 26 Apr 2000 09:31:18 -0400
Received: from hygro.raleigh.ibm.com (IDENT:narten@localhost.localdomain [127.0.0.1])
	by hygro.raleigh.ibm.com (8.9.3/8.9.3) with ESMTP id JAA01151;
	Wed, 26 Apr 2000 09:11:46 -0400
Message-Id: <200004261311.JAA01151@hygro.raleigh.ibm.com>
To: Paul Francis <pfrancis@aciri.org>
cc: francis@ecal.com, ietf@ietf.org
Subject: Re: runumbering (was: Re: IPv6: Past mistakes repeated?) 
In-Reply-To: Message from Paul Francis <pfrancis@aciri.org> 
   of "Tue, 25 Apr 2000 13:53:40 PDT." <200004252053.NAA40544@baboon.aciri.org> 
Date: Wed, 26 Apr 2000 09:11:46 -0400
From: Thomas Narten <narten@raleigh.ibm.com>
X-Loop: ietf@ietf.org

> It seems to me that the decision to just use NATv6 rather than
> do a site-wide runumber will be a very easy decision to make.

Actually, if your assumption is that NATv6 is better than IPv6 with
renumbering, then IPv4 and NATv4 was good enough to start with and
there was need to move to IPv6 in the first place. However, many
people fear that NATs just won't cut it as a long-term solution, with
a number of different reasons why this is so (impact on security and
applications, operational and administrative costs, etc.). But if
NATv4 doesn't cut it, I don't see how NATv6 between IPv6 sites cuts it
either.

Thomas



From owner-ietf-outbound  Wed Apr 26 10:01:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA26810
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 10:00:06 -0400 (EDT)
Received: from fwns1.raleigh.ibm.com (fwns1d.raleigh.ibm.com [204.146.167.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26332
	for <ietf@ietf.org>; Wed, 26 Apr 2000 09:35:55 -0400 (EDT)
Received: from rtpmail02.raleigh.ibm.com (rtpmail02.raleigh.ibm.com [9.37.172.48])
	by fwns1.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id JAA21250;
	Wed, 26 Apr 2000 09:35:22 -0400
Received: from ludwigia.raleigh.ibm.com (ludwigia.raleigh.ibm.com [9.37.60.3])
	by rtpmail02.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id JAB33994;
	Wed, 26 Apr 2000 09:35:22 -0400
Received: from hygro.raleigh.ibm.com (IDENT:root@lig32-226-34-42.us.lig-dial.ibm.com [32.226.34.42]) by ludwigia.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id JAA26417; Wed, 26 Apr 2000 09:31:22 -0400
Received: from hygro.raleigh.ibm.com (IDENT:narten@localhost.localdomain [127.0.0.1])
	by hygro.raleigh.ibm.com (8.9.3/8.9.3) with ESMTP id JAA01125;
	Wed, 26 Apr 2000 09:00:01 -0400
Message-Id: <200004261300.JAA01125@hygro.raleigh.ibm.com>
To: Paul Francis <pfrancis@aciri.org>
cc: smd@EBONE.NET, ietf@ietf.org
Subject: Re: multihoming (was Re: draft-ietf-nat-protocol-complications-02.txt) 
In-Reply-To: Message from Paul Francis <pfrancis@aciri.org> 
   of "Tue, 25 Apr 2000 13:11:36 PDT." <200004252011.NAA40378@baboon.aciri.org> 
Date: Wed, 26 Apr 2000 09:00:00 -0400
From: Thomas Narten <narten@raleigh.ibm.com>
X-Loop: ietf@ietf.org

> Sean said that traditional multihoming would be "very difficult".

Actually, Sean's statement was that  "IPv6's current addressing
architecture" makes multihoming very difficult, and that is the point
that is untrue.

> You replied that "This is not true" (which I take to mean
> that multihoming is not very difficult), and then go on to describe
> something that sounds very difficult to me (maintain longer prefixes,
> make multihomed customers pay for it, get the ISPs to agree to
> handle such longer prefixes).

This is exactly what we have in IPv4 today, except that multihomed
customers aren't really paying. And maybe they won't pay in IPv6
either. The market can sort that out. The point of the IPv6 addressing
architecture is to make that sort of multihoming a _possibility_ and
an _optimization_ rather than a _requirement_. In contrast, today's
IPv4 has lots of long prefixes in the DFZ with no clear way of placing
an upper bound on the number of prefixes that must be maintained in
the DFZ to provide reachability to all sites. In IPv6, the small
number (8K's worth) of TLAs should do the trick. That still leaves
room for many more "value-add" routes when one considers that today's
IPv4 already can/must handle 75K worth of prefixes in the DFZ. The
difference is in IPv4 it is a requirement to maintain all 75K+ routes
in order to just get reachability.

> You say that "multihoming is still quite posible", but nobody said
> that it was impossible, just difficult.  For me, your statement
> certainly reinforces the idea that multihoming in IPv6 is indeed
> very difficult.

As others have pointed out, IPv6 is also developing a multiple
addresses per end-node approach to multihoming. This approach appears
to be more scalable that the current IPv4 solution. Indeed, people
seem to point to multihoming as one of the biggest threats to
continued scaling of the IPv4 routing infrastructure. So one of IPv6's
multihoming approaches is no worse than IPv4, while another appears to
be significantly better. So once again (in contrast to assertions made
by some), IPv6 *does* have some features that should make IPv6 routing
scale better than it does in IPv4.

> I read your statement as follows:

>     IPv6 does not solve the multihoming problem.  Instead, it tries
>     to minimize the damage by:
>     
>     1. discouraging the use of multihoming, primarily may making
>     multihomed customers pay more for it.
>     2. forcing paths to multihomed sites to be less efficient (at
>     least for all but one of the ISP connection points) and or,
>     3. limiting the regions of the internet for which multihoming
>     is effective for a given customer.

> Is this an accurate representation?

Absolutely not, as I hope has now been made clear.

Thomas



From owner-ietf-outbound  Wed Apr 26 10:30:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA27255
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 10:30:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27139
	for <ietf@ietf.org>; Wed, 26 Apr 2000 10:20:41 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id KAA00869;
        Wed, 26 Apr 2000 10:20:01 -0400 (EDT)
Message-Id: <200004261420.KAA00869@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Karl Auerbach <karl@CaveBear.com>
cc: Keith Moore <moore@cs.utk.edu>, IETF <ietf@ietf.org>
Subject: Re: runumbering (was: Re: IPv6: Past mistakes repeated?) 
In-reply-to: Your message of "Tue, 25 Apr 2000 21:16:24 PDT."
             <Pine.LNX.4.21.0004252109080.6184-100000@npax.cavebear.com> 
X-SUBJECT-MSG-FROM: Karl Auerbach <karl@CaveBear.com> 
Date: Wed, 26 Apr 2000 10:20:01 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> So what I am suggesting is that it seems that there is evidence that one
> can do an "association" protocol that is relatively lightweight in terms
> of machinery, packets, packet headers, and end-node state if one leaves
> the heavy lifting of reliability to the underlying TCP protocol.

the on-the-wire protocol overhead is not that great.  the computational
overhead to the host and application, and the resulting loss in maximum
bandwidth, are fairly expensive.

basically it's a lot more efficient to do some variant of mobile IP.

Keith



From owner-ietf-outbound  Wed Apr 26 10:50:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA27595
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 10:50:02 -0400 (EDT)
Received: from sean.ebone.net (IDENT:root@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27493
	for <ietf@ietf.org>; Wed, 26 Apr 2000 10:44:02 -0400 (EDT)
Received: (from smd@localhost)
	by sean.ebone.net (8.9.3/8.9.3) id QAA07449;
	Wed, 26 Apr 2000 16:44:00 +0200 (CEST)
Date: Wed, 26 Apr 2000 16:44:00 +0200 (CEST)
From: Sean Doran <smd@ebone.net>
Message-Id: <200004261444.QAA07449@sean.ebone.net>
To: jnc@ginger.lcs.mit.edu, narten@raleigh.ibm.com
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

Thomas Narten writes:

| I don't know about you, but it scares me to read the various forecasts
| about how wireless will transform the landscape over the next few
| years.

It scares me how much people buy into hype.

I seem to recall reading forecasts about many bright shiny trendy
things would change transform the landscape over the next few years,
if only you invest in it.

What you are asking for is investment in IPv6 based on your
fear and uncertainty about an explosion in the number of end-systems
that will need to communicate with the Internet as a whole,
rather than within an individual addressing domain (or set thereof),
with gateways if and as necessary between these addressing domains.

| E.g., more wireless phones with internet connectivity than
| PCs. The numbers are just staggering and the associated demand for
| addresses will be astonishing. We ain't seen nothing yet.

Wireless phones?  Dead technology.  My prediction: zero phones,
but rather alot of pocket-sized computers which run a variety of
local and network applications, with voice simply being one of those.

IETF-conference-like wireless LANs instead of cellular base-stations,
DHCP, connections which can survive renumbering when moving from place
to place (or which are short/stateless enough not to care), something
IMPP-like for registering at a rendezvous point to accept incoming
connections, and whatever evolves out of these technologies will simply
kill GSM, UMTS and the like, all without forcing a dubious fundamental
change upon the rest of the Internet.

IPv6ification is one such dubious fundamental change, driven in
part by people who have succumbed to the fear that the hypesters
behind many of the claims of these soon-to-be-dead bellhead systems
really would like everyone to believe in.   It inflates their
share prices, and deflates critical analysis of various approaches
to Internet scalability on ALL metrics (not just size of header fields).

	Sean.



From owner-ietf-outbound  Wed Apr 26 11:00:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA27839
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 11:00:03 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA27559
	for <ietf@ietf.org>; Wed, 26 Apr 2000 10:49:03 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.20751-0@bells.cs.ucl.ac.uk>; Wed, 26 Apr 2000 15:48:44 +0100
To: Thomas Narten <narten@raleigh.ibm.com>
cc: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, ietf@ietf.org,
        moore@cs.utk.edu, J.Crowcroft@CS.UCL.AC.UK
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-reply-to: Your message of "Wed, 26 Apr 2000 09:32:45 EDT." <200004261332.JAA01189@hygro.raleigh.ibm.com>
Date: Wed, 26 Apr 2000 15:43:54 +0100
Message-ID: <6274.956760234@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <200004261332.JAA01189@hygro.raleigh.ibm.com>, Thomas Narten typed:

 >>> IPv6's claimed big advantage - a bigger address space - turns out
 >>> not to be an advantage at all - at least in any stage much short of
 >>> completely deployment.

 >>Not surprisingly, I disagree.


right, noels wrong.

the amount of address translation
state you have to keep (and syncronise between failover NATs etc)
 per active session decreases as
the percentage of hosts that are native IPv6 increases, 
(and obviously also
decreases as the absolute number of hosts increases but new hosts
are all v6) - in your scenario (a likely wireless 3G deployment one,
this could happen pretty fast

the amount of disconnect the v4 legacy machines will see because the
state maintenance will fail (as any large system does partially, ALL THE TIME),
will increase, and possibly quite fast...routing state is already in a
bad enough state....without adding address translation state to it...

NATs are not only bad e2e karma, they are bad tech, just like x.25 and atm.

 >>> Here's why:
 >>
 >>>     >> if you have a site which has more hosts than it can get external IPv4
 >>>     >> addresses for, then as long as there are considerable numbers of IPv4
 >>>     >> hosts a site needs to interoperate with, *deploying IPv6 internally to
 >>>     >> the site does the site basically no good at all*.
 >>
 >>Actually, in the above scenario, NAT is already a requirement for IPv4
 >>communication with the outside world. So, if you switch to IPv6
 >>internally, use IPv6-IPv4 NATPT (i.e., combination of NAT and IPv6 to
 >>IPv4 translation) you have pretty much the same
 >>functionality/limitation as with IPv4 NAT.
 >>
 >>Now, consider someone in the process of deploying massive numbers of
 >>devices (100's of millions) together with the infrastructure to
 >>support them (e.g., wireless). With IPv4, they face not only the
 >>necessity of using NAT to get to outside destinations, but also the
 >>use of NAT _internally_ because there isn't enough private address
 >>space to properly number the internal part of the infrastructure.
 >>
 >>In this scenario, IPv6 internally at least gives them end-to-end ness
 >>internally (plus scalability, more robustness, etc., etc.), something
 >>the can't get with IPv4. And it gives them the same set of
 >>issues/headaches when talking to the outside world that they would
 >>have if just using IPv4.
 >>
 >>I don't know about you, but it scares me to read the various forecasts
 >>about how wireless will transform the landscape over the next few
 >>years. E.g., more wireless phones with internet connectivity than
 >>PCs. The numbers are just staggering and the associated demand for
 >>addresses will be astonishing. We ain't seen nothing yet.
 >>
 >>Thomas
 >>

 cheers

   jon



From owner-ietf-outbound  Wed Apr 26 11:40:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA28686
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 11:40:03 -0400 (EDT)
Received: from mailhost.IntNet.net (mailhost.IntNet.net [198.252.32.150])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28559
	for <ietf@ietf.org>; Wed, 26 Apr 2000 11:33:10 -0400 (EDT)
Received: from jtoigo by mailhost.IntNet.net (8.8.5/INTNET/SMI-SVR4)
	id LAA05036; Wed, 26 Apr 2000 11:34:15 -0400 (EDT)
X-Auth: cs-clw-5-214.intnet.net [207.90.1.214]
Message-ID: <066001bfaf94$c0153860$dd9cfea9@jtoigo>
From: "Jon William Toigo" <jtoigo@IntNet.net>
To: <Dave_Lee@3com.com>
Cc: <ietf@ietf.org>
References: <882568CD.0041034D.00@hqoutbound.ops.3com.com>
Subject: Re: SCSI over IP (fwd)
Date: Wed, 26 Apr 2000 11:33:18 -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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Thanks for the referral, Dave.  Now that I have the SCSI over IP RFC text, I
am wondering how soon, if ever, we will likely see a standard and/or product
based on the specification?

To your knowledge, is SCSI over IP being pursued in earnest by IP networking
equipment companies at present?

JWT



From owner-ietf-outbound  Wed Apr 26 11:50:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA28846
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 11:50:02 -0400 (EDT)
Received: from npax.cavebear.com (npax.cavebear.com [192.203.17.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28570
	for <ietf@ietf.org>; Wed, 26 Apr 2000 11:33:32 -0400 (EDT)
Received: from localhost (karl@localhost)
	by npax.cavebear.com (8.9.3/8.9.3) with ESMTP id IAA08343
	for <ietf@ietf.org>; Wed, 26 Apr 2000 08:33:00 -0700
Date: Wed, 26 Apr 2000 08:33:00 -0700 (PDT)
From: Karl Auerbach <karl@CaveBear.com>
Reply-To: Karl Auerbach <karl@CaveBear.com>
To: IETF <ietf@ietf.org>
Subject: Re: runumbering (was: Re: IPv6: Past mistakes repeated?) 
In-Reply-To: <200004261420.KAA00869@astro.cs.utk.edu>
Message-ID: <Pine.LNX.4.21.0004260823460.8285-100000@npax.cavebear.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


> > So what I am suggesting is that it seems that there is evidence that one
> > can do an "association" protocol that is relatively lightweight in terms
> > of machinery, packets, packet headers, and end-node state if one leaves
> > the heavy lifting of reliability to the underlying TCP protocol.
> 
> the on-the-wire protocol overhead is not that great.  the computational
> overhead to the host and application, and the resulting loss in maximum
> bandwidth, are fairly expensive.

I tend to disagree.  An association protocol only really does its work on
connect/reconnect - hopefully a rear event -- and when the application
says "let's establish a work-mark here".

And given that many of our applications are bursty/transactional vehicles
we're not talking about supercomputers transfering bulk files of
simulation data.

> basically it's a lot more efficient to do some variant of mobile IP.

Mobility is not the issue.  Rather, there is use, distinct from mobilty,
for an association that can persever longer than the underlying
transport(s), including changes of IP addresses.  Had we had such a tool
it would have perhaps obviated some of things the mobility folks had to
do.  But having an standardized association protocol is useful in its own
right, distinct from mobility.

In my eyes, an application that uses an association protocol to deal with
changes and faults in underlying connectivity is a lot more in accord with
end-to-end principles than if it relied on ad hoc transport/network
address juggling.

		--karl-




From owner-ietf-outbound  Wed Apr 26 12:10:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA29223
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 12:10:03 -0400 (EDT)
Received: from fwns2.raleigh.ibm.com (fwns2d.raleigh.ibm.com [204.146.167.236])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29145
	for <ietf@ietf.org>; Wed, 26 Apr 2000 12:06:26 -0400 (EDT)
Received: from rtpmail02.raleigh.ibm.com (rtpmail02.raleigh.ibm.com [9.37.172.48])
	by fwns2.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id MAA38676;
	Wed, 26 Apr 2000 12:05:51 -0400
Received: from ludwigia.raleigh.ibm.com (ludwigia.raleigh.ibm.com [9.37.60.3])
	by rtpmail02.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id MAA29832;
	Wed, 26 Apr 2000 12:05:52 -0400
Received: from localhost.localdomain (IDENT:root@lig32-226-104-199.us.lig-dial.ibm.com [32.226.104.199]) by ludwigia.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id MAA26625; Wed, 26 Apr 2000 12:01:55 -0400
Received: from localhost.localdomain (IDENT:narten@localhost.localdomain [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id MAA00804;
	Wed, 26 Apr 2000 12:05:45 -0400
Message-Id: <200004261605.MAA00804@localhost.localdomain>
To: Sean Doran <smd@ebone.net>
cc: jnc@ginger.lcs.mit.edu, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-Reply-To: Message from Sean Doran <smd@ebone.net> 
   of "Wed, 26 Apr 2000 16:44:00 +0200." <200004261444.QAA07449@sean.ebone.net> 
Date: Wed, 26 Apr 2000 12:05:45 -0400
From: Thomas Narten <narten@raleigh.ibm.com>
X-Loop: ietf@ietf.org

> | I don't know about you, but it scares me to read the various forecasts
> | about how wireless will transform the landscape over the next few
> | years.

> It scares me how much people buy into hype.

If only 10% of the hype is true, I'm still scared. Will it be celluar
phones? Maybe, maybe not. If not, there are still a bunch of other
wanna-be next-big technologies behind it. Don't underestimate the
potential for consumer-oriented per-person technologies to create real
astonishing demands.

Thomas



From owner-ietf-outbound  Wed Apr 26 12:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA29553
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 12:30:04 -0400 (EDT)
Received: from sean.ebone.net (IDENT:root@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29372
	for <ietf@ietf.org>; Wed, 26 Apr 2000 12:21:50 -0400 (EDT)
Received: (from smd@localhost)
	by sean.ebone.net (8.9.3/8.9.3) id SAA07757;
	Wed, 26 Apr 2000 18:21:47 +0200 (CEST)
Date: Wed, 26 Apr 2000 18:21:47 +0200 (CEST)
From: Sean Doran <smd@ebone.net>
Message-Id: <200004261621.SAA07757@sean.ebone.net>
To: narten@raleigh.ibm.com
Subject: Re: multihoming (was Re: draft-ietf-nat-protocol-complications-02.txt)
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

Thomas Narten writes:

| The point of the IPv6 addressing architecture is to make that
| sort of multihoming a _possibility_ and an _optimization_ rather
| than a _requirement_.

In a purely technical sense, redundancy of any sort is
an _optimization_ rather than a _requirement_.   There
is absolutely nothing in IPv4 that _requires_ any entity to
be multiply homed or multiply connected at all.

It seems out of touch with reality to rest on the argument that
multihoming by entities too small to qualify for a (scarce) TLA
needn't be considered from first principles because such a multihoming
is an _optimization_ and isn't really required.

| In contrast, today's
| IPv4 has lots of long prefixes in the DFZ with no clear way of placing
| an upper bound on the number of prefixes that must be maintained in
| the DFZ to provide reachability to all sites. In IPv6, the small
| number (8K's worth) of TLAs should do the trick.

This sounds like virtue without sacrifice - ecologically
correct routing at zero cost, except to "polluters" who
are in it only for themselves, out to _optimize_ their
perfectly sound single connectivity.

Great!  In this polluter-pays world, if you have a TLA assignment
and you change your topology so that your TLA prefix is announced
to my network from two directions instead of one, you are able to
influence my routing decision in how traffic I generate will return
to you.

If you do not have a TLA assignment and you change
your topology, I cannot see that, because I implement
the standardized /19 (oops, TLA) filter.  Unless you pay me.

Cool.  

Obviously, I cannot be too critical of this approach,
because it is precisely what I tried (and failed) to
do with the /19 (and earlier /18) filters in Sprintlink.

The horrendous failure of those filters was the inability
on my part to add economics to the mix, and to allow
organizations to offer some consideration in exchange for
a relaxing of the filtering policy.

This failure turns out not to be simply local -- there is no
reasonable scheme available to settle with one, two or three
filtering networks, let alone tens or hundreds or thousands.  So
when someone has a reason to want to pay for an _optimization_,
there is no practical means to do so, and therefore, technical
reasons for not imposing them as well as merely really bad P.R.  ones.

In the absence of a market, it is very hard to argue that
"the market" will sort things out.   Engineers shouldn't
resort to belief in the divine Invisible Hand when the
mechanisms and rules of a market do not exist yet.

There was also a backing-away from the original filtering policy.
The step back from /18 to /19 happened because the place where
economics was working best -- the RIPE registry -- was allocating
nothing smaller than /19s.   /19s were chosen because they
best fit the size of an initially-multihoming entity, and
/18s seemed to be much too big an allocation.   The initial
allocation of a /19 was based on a simple market principle:
if you were willing to pay $x to the registry, you get a /19.
Come back when you want more, we'll talk about it.

As the registries converged on the model of charging for
registering standard-or-shorter prefixes, the /19 filters
merely became a self-defensive measure to avoid hearing
accidentally-announced long prefixes.

The TLAs are much too big for most initially-multihoming
entities, and thus the TLAs themselves are essentially 
irrelevant and ultimately meaningless, in the same way
that the /18s were.    Today's TLAs are tomorrow's /8s,
as observed by Bill Manning.


| As others have pointed out, IPv6 is also developing a multiple
| addresses per end-node approach to multihoming.

This is pushing the NAT function of multihoming-using-NATs-and-PA-space
into the end hosts.  The problem is that each time a new TLA is
connected-to, a multihomed entity that does not qualify for a 
large enough allocation will have to convince all the devices
covered by the original address space to now adopt a 2nd, 3rd or
nth address.  In a sizable NLA, where the devices are not all
under the control of the NLA's administrators, this seems pretty
challenging.   (It's really cool for a sizable dialup provider!)

Worse, the NLA's administrators are STILL bereft of a way to 
influence the routing decision made by a distant TLA towards 
the multiply-addressed end hosts.   That is, if I want traffic
from AboveNet's TLA to come in via Sprintlink and traffic
from Exodus's TLA to come in via GTEI, how do I get the multiply-
addressed hosts that I do not control, and the various TLAs
and NLAs, to cooperate in that?  (For example, how could I get
a host owned by some customer's dialup customer to use an address
with Sprintlink's TLA when talking to www.above.net, and
to use an address with GTEI's TLA when talking to www.exodus.net?)

Section 5 of draft-ietf-ipngwg-default-addr-select-00.txt doesn't
have very much meat on this topic...

| >     IPv6 does not solve the multihoming problem.  Instead, it tries
| >     to minimize the damage by:
| >     
| >     1. discouraging the use of multihoming, primarily may making
| >     multihomed customers pay more for it.
| >     2. forcing paths to multihomed sites to be less efficient (at
| >     least for all but one of the ISP connection points) and or,
| >     3. limiting the regions of the internet for which multihoming
| >     is effective for a given customer.
|
| > Is this an accurate representation?
|
| Absolutely not, as I hope has now been made clear.

Actually, as I read your answer, the "not" must be a typo.

	Sean.



From owner-ietf-outbound  Wed Apr 26 12:50:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA29953
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 12:50:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29844
	for <ietf@ietf.org>; Wed, 26 Apr 2000 12:42:46 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id MAA15783;
	Wed, 26 Apr 2000 12:41:31 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: "'Thomas Narten'" <narten@raleigh.ibm.com>,
        "'J. Noel Chiappa'" <jnc@ginger.lcs.mit.edu>
Cc: <ietf@ietf.org>, <moore@cs.utk.edu>
Subject: RE: draft-ietf-nat-protocol-complications-02.txt 
Date: Wed, 26 Apr 2000 12:45:07 -0400
Message-ID: <001801bfaf9e$c8970fe0$d001010a@tst.ennovatenetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
In-Reply-To: <200004261332.JAA01189@hygro.raleigh.ibm.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


In his previous mail, Thomas Narten writes:

>

> 
> Now, consider someone in the process of deploying massive numbers of
> devices (100's of millions) together with the infrastructure to
> support them (e.g., wireless). With IPv4, they face not only the
> necessity of using NAT to get to outside destinations, but also the
> use of NAT _internally_ because there isn't enough private address
> space to properly number the internal part of the infrastructure.
>
> 
> I don't know about you, but it scares me to read the various forecasts
> about how wireless will transform the landscape over the next few
> years. E.g., more wireless phones with internet connectivity than
> PCs. The numbers are just staggering and the associated demand for
> addresses will be astonishing. We ain't seen nothing yet.
> 

The basic assumptions in your answer are:

1) wireless devices will need an IP address.
2) Wireless devices will need to run TCP over IP for doing file transfer,
web browsing etc.

These are neither necessary, nor desirable solutions for wireless data
or voice devices providing data. Most end user don't care whether their 
wireless email comes using an IP address or using a GSM ID or a Re-FLEX 
capcode. Wireless standards folks, if they want, can continue to keep NAT 
and IPv6 addresses away from end wireless devices.

Cheers,

--brijesh
Ennovate Networks Inc.,
 




From owner-ietf-outbound  Wed Apr 26 13:00:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA00222
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 13:00:02 -0400 (EDT)
Received: from sean.ebone.net (IDENT:root@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29858
	for <ietf@ietf.org>; Wed, 26 Apr 2000 12:44:58 -0400 (EDT)
Received: (from smd@localhost)
	by sean.ebone.net (8.9.3/8.9.3) id SAA07923;
	Wed, 26 Apr 2000 18:44:54 +0200 (CEST)
Date: Wed, 26 Apr 2000 18:44:54 +0200 (CEST)
From: Sean Doran <smd@ebone.net>
Message-Id: <200004261644.SAA07923@sean.ebone.net>
To: narten@raleigh.ibm.com, pfrancis@ACIRI.ORG
Subject: Re: runumbering (was: Re: IPv6: Past mistakes repeated?)
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

Thomas Narten writes:

| Actually, if your assumption is that NATv6 is better than IPv6 with
| renumbering, then IPv4 and NATv4 was good enough to start with and
| there was need to move to IPv6 in the first place.
           ^
	   no  (right?  maybe this is where the previous "not" came from -:) )

Did you see Noel's excellent observation that the problem with
NAT is architectural and not mechanical?   The architectural problem:
more things to address on one side of the NAT than there are addresses
on the other side of the NAT.

IPv6 does bring *ONE* thing significantly different from IPv4:
lots of address space.  So much, that we do not obviously need to
have situations where there is an addressability mismatch on any
side of a NAT.

NATv6 therefore does not suffer the architectural flaw that
causes him to have real problems with NAT, although it can
suffer many of the mechanical problems, particularly if IPv6
deliberately seeks to worsen the mechanical difficulties of NATv6.

This allows for the architectural features of NAT to be
less awkwared to exploit.

| But if NATv4 doesn't cut it, I don't see how NATv6 between IPv6
| sites cuts it either.

I hope this makes it clearer for you.

	Sean.



From owner-ietf-outbound  Wed Apr 26 13:10:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA00544
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 13:10:02 -0400 (EDT)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00448
	for <ietf@ietf.org>; Wed, 26 Apr 2000 13:06:12 -0400 (EDT)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id JAA22943;
	Wed, 26 Apr 2000 09:59:19 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 26 Apr 2000 17:06:06 UT
Received: from porky (porky.ascend.com [192.207.23.83])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id KAA28087;
	Wed, 26 Apr 2000 10:06:05 -0700 (PDT)
Received: from ascend.com by ascend.com
Message-Id: <4.3.1.2.20000426100233.00bdcbc0@porky>
X-Sender: mhold@porky
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 26 Apr 2000 10:07:29 -0700
To: Thomas Narten <narten@raleigh.ibm.com>
From: Matt Holdrege <holdrege@lucent.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
Cc: ietf@ietf.org
In-Reply-To: <200004261332.JAA01189@hygro.raleigh.ibm.com>
References: <Message from "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
 <200004251942.PAA03466@ginger.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org


>I don't know about you, but it scares me to read the various forecasts
>about how wireless will transform the landscape over the next few
>years. E.g., more wireless phones with internet connectivity than
>PCs. The numbers are just staggering and the associated demand for
>addresses will be astonishing. We ain't seen nothing yet.

It seems to be a given now that 3G phones will be IPv6 (at least outside 
the U.S.) when they roll out over the next few years. But we should make 
people clearly aware of what to expect when they NAT their way back to the 
IPv4 Internet or IPv4 intranets. That is one of the purposes of this draft. 
(oh yeah, this thread is supposed to be about contributing to the draft in 
the subject line)



From owner-ietf-outbound  Wed Apr 26 13:50:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA01138
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 13:50:03 -0400 (EDT)
Received: from lint.cisco.com (lint.cisco.com [171.68.224.209])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01021
	for <ietf@ietf.org>; Wed, 26 Apr 2000 13:41:10 -0400 (EDT)
Received: from elearhomepc (elear-dsl3.cisco.com [10.19.144.52]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id KAA03440; Wed, 26 Apr 2000 10:40:03 -0700 (PDT)
Message-ID: <003401bfafa6$b6b65da0$3490130a@cisco.com>
From: "Eliot Lear" <lear@cisco.com>
To: "Thomas Narten" <narten@raleigh.ibm.com>
Cc: <ietf@ietf.org>, "Sean Doran" <smd@ebone.net>
References: <jnc@ginger.lcs.mit.edu> <200004261332.JAA01189@hygro.raleigh.ibm.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Date: Wed, 26 Apr 2000 10:41:54 -0700
Organization: Cisco Systems
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Thomas,

I think you're actually both right.

Noel's comment was meant as a general case for even a very large
enterprise.  You provided a counterexample of some number of providers that
will need huge amounts of address space.  Much as I dislike NAT I believe
it's an unproven assertion that those providers won't find a way to molest
the architecture further to make it work.  Really all that is required is
some small percentage of public addresses, based on usage patterns.  Any
Bell Heads want to take a stab at that percentage?

My hope is, however, that a NAT deployment would be 6-4, so that they could
at least have the pipe dream that those NATs might some day become
unnecessary.

Also, many people have made claims of grand visions when it comes to usage
of address space, and these grand visions have been rebutted with "it
hasn't happened yet."  In some cases it hasn't happened because it couldn't
happen.  Fred tells the story of China.  I can tell the story of a cable
provider, back in 1993, who were planning a large scale Cable-IP
deployment.  They were ahead of their time, but not by that much.

Eliot




From owner-ietf-outbound  Wed Apr 26 14:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA01349
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 14:00:05 -0400 (EDT)
Received: from leonid.genesyslab.com (pbinat33.genesyslab.com [209.233.177.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01054
	for <ietf@ietf.org>; Wed, 26 Apr 2000 13:42:14 -0400 (EDT)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id KAA00562
	for ietf@ietf.org; Wed, 26 Apr 2000 10:31:24 -0700
Date: Wed, 26 Apr 2000 10:31:24 -0700
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200004261731.KAA00562@leonid.genesyslab.com>
To: ietf@ietf.org
Subject: Re: NAT->IPv6
X-Loop: ietf@ietf.org

>From: "Steven M. Bellovin" <smb@research.att.com>
>
>In message <001501bfaf43$127e4d00$3490130a@cisco.com>, "Eliot Lear" writes:
>>It is a complete fallacy that NAT provides any sort of security.  It does
>>no such thing.  Security is provide by a firewall, and (more importantly)
>>by strong security policies that are policed and enforced.
>
>Eliot is absolutely right.  A NAT box *might* be part of a firewall, but by
>itself it isn't one.  It's no more secure, and often less so, than an
>application-level firewall.
>
   You both right ... from strong point of view. But if intruder
can't hook target host simply because he does not know - how he can open
TCP to it then it is also part of security.

>The myth that NATs per se provide strong security is one of the greatest
>barriers to their elimination.

   It is not a myth. It is level of thinking. If you setup only firewall
and you are not very good network engineer you can't understand where could
be the next threat. Your TCP stack/firewall/etc may have a bug, some new
protocol may have a misdesign. But anybody clear understand that if your
internal hosts do not have a public address then all attacks may be
only static - wait until internal host open TCP to somewhere. And this
kind of attack may be at least investigated and compromised external host
may be found.

  I am not NAT defender but I recognize how IS dept thinks.
I prefer a mixed solution like uniq host system ID + some controllable
route address.

		       - Leonid Yegoshin, LY22



From owner-ietf-outbound  Wed Apr 26 14:20:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA01696
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 14:20:03 -0400 (EDT)
Received: from baboon.aciri.org (baboon.aciri.org [192.150.187.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01596
	for <ietf@ietf.org>; Wed, 26 Apr 2000 14:12:56 -0400 (EDT)
Received: (from pfrancis@localhost)
	by baboon.aciri.org (8.9.3/8.9.3) id LAA46227;
	Wed, 26 Apr 2000 11:12:50 -0700 (PDT)
	(envelope-from pfrancis)
Date: Wed, 26 Apr 2000 11:12:50 -0700 (PDT)
From: Paul Francis <pfrancis@aciri.org>
Message-Id: <200004261812.LAA46227@baboon.aciri.org>
To: narten@raleigh.ibm.com, pfrancis@aciri.org
Subject: Re: runumbering (was: Re: IPv6: Past mistakes repeated?)
Cc: francis@ecal.com, ietf@ietf.org
In-Reply-To: <200004261311.JAA01151@hygro.raleigh.ibm.com>
X-Loop: ietf@ietf.org


>  Actually, if your assumption is that NATv6 is better than IPv6 with
>  renumbering, then IPv4 and NATv4 was good enough to start with and

I'm not prepared to say that NATv6 is better than IPv6+renumber,
simply because what is better depends on what is important to
the user.  By some general architectural criteria IPv6+reunumber
is better, but I guess if pushed I would have to say that, for
a net manager with a limited budget, for whom internal connectivity
is far far more important than external connectivity, and with
some tricky mix of hosts and routers for instance, yes NATv6 is
"better".

I can easily imagine being a consultant and recommending to a
certain class of customers in certain situations that they use
NATv6.  (Boy I may regret this sentence...its going to be used
against me someday...  :-(

>  applications, operational and administrative costs, etc.). But if
>  NATv4 doesn't cut it, I don't see how NATv6 between IPv6 sites cuts it
>  either.
>               

NATv4 doesn't cut it, but net managers use it anyway.  NATv6 won't
cut it, but net managers may very well use it anyway.

I may be wrong...the motivations for using NATv6 will be weaker
than the motivations for using NATv4.  But at the same time, the
problems with using NATv6 will be less than the problems with
using NATv4.

On the motivation side, NATv6 won't have the lack-of-addresses
problem.  While this is the major motivation for NATv4, I don't
think it is the only motivation.  On the problems side, NATv6
won't have the problems of port mapping or of having to dynamically
map lots of internal addresses into a small number of external
addresses.

I guess my assertion, to the extent that I'm making one at all,
is that one should take into account these least paths of
resistance when designing new protocols.  This may mean not
designing the protocol you'd otherwise like to design if
practically speaking nobody is going to use it.  Unfortunately
I'm not able to translate this vague assertion into any
concrete suggestion for IPv6 per se...

PF



From owner-ietf-outbound  Wed Apr 26 14:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA01832
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 14:30:03 -0400 (EDT)
Received: from baboon.aciri.org (baboon.aciri.org [192.150.187.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01639
	for <ietf@ietf.org>; Wed, 26 Apr 2000 14:15:57 -0400 (EDT)
Received: (from pfrancis@localhost)
	by baboon.aciri.org (8.9.3/8.9.3) id LAA46253;
	Wed, 26 Apr 2000 11:15:51 -0700 (PDT)
	(envelope-from pfrancis)
Date: Wed, 26 Apr 2000 11:15:51 -0700 (PDT)
From: Paul Francis <pfrancis@aciri.org>
Message-Id: <200004261815.LAA46253@baboon.aciri.org>
To: deering@cisco.com, pfrancis@aciri.org
Subject: Re: multihoming (was Re: draft-ietf-nat-protocol-complications-02.txt)
Cc: ietf@ietf.org, narten@hygro.adsl.duke.edu, smd@EBONE.NET
In-Reply-To: <v0422080bb52bc7db38a0@[10.19.130.188]>
X-Loop: ietf@ietf.org


>  architecture.  That accusation is false, and nothing in IPv6 prevents
>  the use of the same, lousy multihoming solution we have today for IPv4.

Just for the record, I was *not* suggesting that IPv4 solves the
multihoming problem (I said nothing about it one way or the other).
I understand that internet-wide advertising of multiple prefixes
for multihomed sites does not scale, and so does not constitute a
solution.  (I would not use the word "solution" to describe IPv4's
defacto approach to multihoming.)

>  hosts.  This is work-in-progress, and is likely to produce solutions
>  with a different (but, we hope, acceptable in many contexts) set of
>  shortcomings.

Ok, so I think we may be in factual agreement if not in agreement
on emphasis or tone.  So, let me repeat my representation here and
ask you if the (hopefully acceptable) shortcomings would likely
have one or more of the following characteristics:                           

>    1. discouraging the use of multihoming, primarily may making
>    multihomed customers pay more for it.
>    2. forcing paths to multihomed sites to be less efficient (at
>    least for all but one of the ISP connection points) and or,
>    3. limiting the regions of the internet for which multihoming
>    is effective for a given customer.

Keep in mind that these three characteristics are gleaned (and then
negatively spun) directly from what Thomas wrote.  The negative spin
was a reaction to what I percieved as a misrepresentation of the
difficulties by Thomas.

Alternatively, maybe you could just point me to the work-in-progress
you refer to (even if it is in the form of IPv6 mailing list archives).
(I'm aware of the IDs on router renumbering, DNS suffix changing, and
the one about using mobility mechanisms for dealing with multihoming.)

PF



From owner-ietf-outbound  Wed Apr 26 14:40:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA02122
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 14:40:02 -0400 (EDT)
Received: from baboon.aciri.org (baboon.aciri.org [192.150.187.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01757
	for <ietf@ietf.org>; Wed, 26 Apr 2000 14:23:08 -0400 (EDT)
Received: (from pfrancis@localhost)
	by baboon.aciri.org (8.9.3/8.9.3) id LAA46281;
	Wed, 26 Apr 2000 11:23:02 -0700 (PDT)
	(envelope-from pfrancis)
Date: Wed, 26 Apr 2000 11:23:02 -0700 (PDT)
From: Paul Francis <pfrancis@aciri.org>
Message-Id: <200004261823.LAA46281@baboon.aciri.org>
To: francis@ecal.com, huitema@microsoft.com, narten@hygro.adsl.duke.edu,
        pfrancis@aciri.org
Subject: RE: runumbering (was:  Re: IPv6: Past mistakes repeated?)
Cc: ietf@ietf.org
In-Reply-To: <BB61526CDE70D2119D0F00805FBECA2F16967274@RED-MSG-55>
X-Loop: ietf@ietf.org

>  
>  I think your description is somewhat biased, Paul. Suppose that you execute

Sure...I was making a point, not publishing a full analysis.  But
my position did take into consideration everything you mention.

>  the strategy you describe, and that the address 10.3.2.1, that was mapped to
>  129.87.64.32, gets transparently remapped to 130.123.45.67. It seems to me
>  that you are going to loose all existing TCP connections, just like with any
>  other form of renumbering. Suppose then that the external prefix of your

I agree with everything you say here about the difficulties
of NAT as a renumbering-avoidance mechanism.  But I would
point out that these difficulties effect external connectivity
only, not internal connectivity.  (The same external difficulties
also exist even if you do full renumbering, so the fact that
they also exist in the NAT case does not necessarily change my
assertion that NAT will be the path of least resistance for
net managers.)

For most net managers, intra-company connectivity is way more
important than external connectivity.  Renumbering problems
effect intra-company connectivity, whereas NAT problems only
effect external connectivity. 

>  
>  Suppose now that you want to use NAT for multihoming. Suppose then that I
>  really care that my TCP connection survives when I loose contact with ISP-A,

I also agree with the statements you make about the problems
of multihoming with NAT.  You'll notice that I specifically
said "rudimentary form of multihoming".  I considered going
into what that meant when I wrote it, but didn't want to water
down my main point.   (Good communications sometimes necesitates
telling a biased and partial story.)

>  
>  court. There is, in fact, no alternative to end-to-end smartness -- the
>  smarter your end systems, the more likely they are to use the network
>  correctly. Now, if your systems are smart and now how to choose one of many
>  available addresses, then we have a solution with v6 multi-homing -- the
>  support of multiple prefixes per site, multiple addresses per interface. 
>  

I agree completely with what you say about needing to push
the multi-address complexity to the host.  As you kindly
pointed out (and I self-servingly expand on here), this is
an architecture I put forth about a decade ago in a sigcomm
paper (in Zurich, I don't remember the year).

But that architecture (hosts having multiple addresses
representing a site's multiple aggregation prefixes and
selecting among them) requires some method of identifying
hosts when they switch from one address to another
mid-connection.  I would assume that what people have in
mind for this are the mobility mechanisms?  (The alternative
is 8+8 or some variant, which I understand to be contentious
enough that it is a defacto non-starter.)

PF  



From owner-ietf-outbound  Wed Apr 26 14:50:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA02283
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 14:50:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01955
	for <ietf@ietf.org>; Wed, 26 Apr 2000 14:31:39 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id OAA05933;
	Wed, 26 Apr 2000 14:31:23 -0400
Date: Wed, 26 Apr 2000 14:31:23 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200004261831.OAA05933@ginger.lcs.mit.edu>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

    > right, noels wrong.

Noel is happy to wait, and see who's right. (I've been through this exact
same experience before, with CLNP, so I understand the life-cycle.) So far,
I've been waiting for quite a few years with IPv6, and so far I'm right.

Let's see, how many years have these standards been out, and how much
deployment has there been? Hmm, RFC-1883 was in December 1995. Can you point
me to *any* other IETF product that, 5 years after the Proposed Standard came
out, still hadn't been significantly deployed - and then went on to be a
success?

No?

I didn't think so.


    > NATs are not only bad e2e karma, they are bad tech

I'm not denying that - and I've said as much. All address-sharing devices are
problematic, and some (e.g. NAT boxes) are downright disgusting kludges.

However, history shows that bad tech doesn't magically replace itself, it has
to be replaced by an economically viable alternative. (For an example of this
principle in action, note that the vast majority of cars are still powered by
reciprocating internal-combustion engines... talk about poor basic concept!
But I digress....)

Judging from the real world out there, it appears that IPv6 isn't a viable
alternative.

	Noel



From owner-ietf-outbound  Wed Apr 26 15:00:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA02573
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 15:00:01 -0400 (EDT)
Received: from mail4.microsoft.com (mail4.microsoft.com [131.107.3.122])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA02257
	for <ietf@ietf.org>; Wed, 26 Apr 2000 14:48:34 -0400 (EDT)
Received: from 157.54.9.103 by mail4.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 26 Apr 2000 11:41:17 -0700 (Pacific Daylight Time)
Received: by INET-IMC-04 with Internet Mail Service (5.5.2651.58)
	id <JW3L60KC>; Wed, 26 Apr 2000 11:41:17 -0700
Message-ID: <BB61526CDE70D2119D0F00805FBECA2F16967281@RED-MSG-55>
From: Christian Huitema <huitema@microsoft.com>
To: "'Paul Francis'" <pfrancis@aciri.org>, francis@ecal.com,
        narten@hygro.adsl.duke.edu
Cc: ietf@ietf.org
Subject: RE: runumbering (was:  Re: IPv6: Past mistakes repeated?)
Date: Wed, 26 Apr 2000 11:41:11 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

> I agree completely with what you say about needing to push
> the multi-address complexity to the host.  As you kindly
> pointed out (and I self-servingly expand on here), this is
> an architecture I put forth about a decade ago in a sigcomm
> paper (in Zurich, I don't remember the year).

The paper "Efficient and robust policy routing using multiple hierarchical
addresses " was published at the 1991 SIGCOMM, in Zurich. ACM papers used to
be available on line, but it seems that the ACM now wants to enforce pay per
view.
(http://www.acm.org/pubs/citations/proceedings/comm/115992/p53-tsuchiya/)

There is related work on an "Extended Transmission Control Protocol"
available at http://www.chem.ucla.edu/~beichuan/etcp/

> But that architecture (hosts having multiple addresses
> representing a site's multiple aggregation prefixes and
> selecting among them) requires some method of identifying
> hosts when they switch from one address to another
> mid-connection.  I would assume that what people have in
> mind for this are the mobility mechanisms?  (The alternative
> is 8+8 or some variant, which I understand to be contentious
> enough that it is a defacto non-starter.)

The rubbing point is that identifying is not quite enough -- you need
"secure identifying" in order to avoid connection hijacking, probably
through some variation of IPSEC. Which brings us back to NATs not being
terribly helpful...



From owner-ietf-outbound  Wed Apr 26 15:10:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA02875
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 15:10:02 -0400 (EDT)
Received: from small-gods.mit.edu (SMALL-GODS.MIT.EDU [18.177.0.248])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02409
	for <ietf@ietf.org>; Wed, 26 Apr 2000 14:54:40 -0400 (EDT)
Received: (from ghudson@localhost) by small-gods.mit.edu (8.9.3)
	id OAA21051; Wed, 26 Apr 2000 14:54:21 -0400 (EDT)
Message-Id: <200004261854.OAA21051@small-gods.mit.edu>
To: Leonid Yegoshin <egoshin@genesyslab.com>
cc: ietf@ietf.org
Subject: Re: NAT->IPv6 
In-Reply-To: Your message of "Wed, 26 Apr 2000 10:31:24 PDT."
             <200004261731.KAA00562@leonid.genesyslab.com> 
Date: Wed, 26 Apr 2000 14:54:21 -0400
From: Greg Hudson <ghudson@MIT.EDU>
X-Loop: ietf@ietf.org

> But anybody clear understand that if your internal hosts do not have
> a public address then all attacks may be only static - wait until
> internal host open TCP to somewhere.

This is a naive understanding.  Source-routing would let me get
packets through to an internal address unless your NAT also acts as a
firewall.

(Granted, I think it turns out that pretty much all NATs do this kind
of firewalling in all cases.  But there's no reason why a firewall
allowing only outgoing connections should be any more error-prone than
a NAT gateway.)



From owner-ietf-outbound  Wed Apr 26 15:20:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA03091
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 15:20:03 -0400 (EDT)
Received: from baboon.aciri.org (baboon.aciri.org [192.150.187.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02416
	for <ietf@ietf.org>; Wed, 26 Apr 2000 14:54:50 -0400 (EDT)
Received: (from pfrancis@localhost)
	by baboon.aciri.org (8.9.3/8.9.3) id LAA46430;
	Wed, 26 Apr 2000 11:54:46 -0700 (PDT)
	(envelope-from pfrancis)
Date: Wed, 26 Apr 2000 11:54:46 -0700 (PDT)
From: Paul Francis <pfrancis@aciri.org>
Message-Id: <200004261854.LAA46430@baboon.aciri.org>
To: francis@ecal.com, huitema@microsoft.com, narten@hygro.adsl.duke.edu,
        pfrancis@aciri.org
Subject: RE: runumbering (was:  Re: IPv6: Past mistakes repeated?)
Cc: ietf@ietf.org
In-Reply-To: <BB61526CDE70D2119D0F00805FBECA2F16967281@RED-MSG-55>
X-Loop: ietf@ietf.org

>  > mid-connection.  I would assume that what people have in
>  > mind for this are the mobility mechanisms?  (The alternative
>  > is 8+8 or some variant, which I understand to be contentious
>  > enough that it is a defacto non-starter.)
>  
>  The rubbing point is that identifying is not quite enough -- you need
>  "secure identifying" in order to avoid connection hijacking, probably
>  through some variation of IPSEC. Which brings us back to NATs not being
>  terribly helpful...
>  

But if the mechanisms used are the mobility mechanisms, then the
security mechanisms for mobility will apply...

PF



From owner-ietf-outbound  Wed Apr 26 15:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA03455
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 15:40:03 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03432
	for <ietf@ietf.org>; Wed, 26 Apr 2000 15:39:22 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id NAA21937
	for ietf@ietf.org  env-from <vjs>;
	Wed, 26 Apr 2000 13:39:19 -0600 (MDT)
Date: Wed, 26 Apr 2000 13:39:19 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004261939.NAA21937@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: NAT->IPv6
X-Loop: ietf@ietf.org

> From: Greg Hudson <ghudson@MIT.EDU>

> > But anybody clear understand that if your internal hosts do not have
> > a public address then all attacks may be only static - wait until
> > internal host open TCP to somewhere.
>
> This is a naive understanding.  Source-routing would let me get
> packets through to an internal address unless your NAT also acts as a
> firewall.

Why isn't it also naive to assume that vulnerable applications on hosts
inside will honor IP source routes on the return path?

See for example, current BSD source for telnetd and rlogind.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Wed Apr 26 16:50:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA04374
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 16:50:02 -0400 (EDT)
Received: from mauve.innosoft.com (DSL107-055.brandx.net [209.55.107.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04344
	for <ietf@ietf.org>; Wed, 26 Apr 2000 16:48:41 -0400 (EDT)
From: ned.freed@innosoft.com
Received: from MAUVE.INNOSOFT.COM by MAUVE.INNOSOFT.COM (PMDF V6.1-1 #35243)
 id <01JOORXDFNG00004ZJ@MAUVE.INNOSOFT.COM> for ietf@ietf.org; Wed,
 26 Apr 2000 13:48:34 -0800 (PST)
Date: Wed, 26 Apr 2000 13:48:00 -0800 (PST)
Subject: RE: runumbering (was:  Re: IPv6: Past mistakes repeated?)
In-reply-to: "Your message dated Tue, 25 Apr 2000 18:41:46 -0700 (PDT)"
 <Pine.LNX.4.21.0004251835590.5631-100000@npax.cavebear.com>
To: Karl Auerbach <karl@CaveBear.com>
Cc: IETF <ietf@ietf.org>
Message-id: <01JOOZMEM1740004ZJ@MAUVE.INNOSOFT.COM>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
References: <BB61526CDE70D2119D0F00805FBECA2F16967274@RED-MSG-55>
X-Loop: ietf@ietf.org

> > Turn it any way you want, TCP sessions can only survive renumbering through
> > end to end mechanisms...

> Which raises the interesting (to me anyway) question: Is there value in
> considering a new protocol, layered on top of TCP, but beneath new
> applications, that provides an "association" the life of which transcends
> the TCP transports upon which it is constructed?

> I believe that if we had such a protocol that it would be a useful tool to
> solve many of the juggling acts that transpire under the heading of
> "mobile networking" as well as providing a way to continue (or
> "resume") connectivity after IP address changes.

> (I will, of course, be suitably embarrassed if someone points out that
> work is already going on to do this.)

  draft-xie-stewart-sigtran-ddp-00.txt

				ned



From owner-ietf-outbound  Wed Apr 26 17:10:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA04651
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 17:10:02 -0400 (EDT)
Received: from lint.cisco.com (lint.cisco.com [171.68.224.209])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04606
	for <ietf@ietf.org>; Wed, 26 Apr 2000 17:03:50 -0400 (EDT)
Received: from elearhomepc (elear-dsl3.cisco.com [10.19.144.52]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id OAA14078; Wed, 26 Apr 2000 14:02:43 -0700 (PDT)
Message-ID: <003e01bfafc3$06be94e0$3490130a@cisco.com>
From: "Eliot Lear" <lear@cisco.com>
To: "Vernon Schryver" <vjs@calcite.rhyolite.com>
Cc: <ietf@ietf.org>
References: <200004261939.NAA21937@calcite.rhyolite.com>
Subject: Re: NAT->IPv6
Date: Wed, 26 Apr 2000 14:04:34 -0700
Organization: Cisco Systems
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

It's also completely naive that source routing is your only threat.  One
can break into a NAT.  One can forge packets and address them
appropriately.  Firewalls prevent this, not NATs.




From owner-ietf-outbound  Wed Apr 26 17:20:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA04841
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 17:20:02 -0400 (EDT)
Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04699
	for <ietf@ietf.org>; Wed, 26 Apr 2000 17:11:49 -0400 (EDT)
Received: from us.networkcs.com (us.networkcs.com [137.66.11.15])
	by marcos.networkcs.com (8.9.3/8.9.3) with ESMTP id QAA73220
	for <ietf@ietf.org>; Wed, 26 Apr 2000 16:11:47 -0500 (CDT)
	(envelope-from salo@us.networkcs.com)
Received: (from salo@localhost)
	by us.networkcs.com (8.9.2/8.9.2) id QAA39839;
	Wed, 26 Apr 2000 16:11:46 -0500 (CDT)
	(envelope-from salo)
Date: Wed, 26 Apr 2000 16:11:46 -0500 (CDT)
From: Tim Salo <salo@networkcs.com>
Message-Id: <200004262111.QAA39839@us.networkcs.com>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <200004261831.OAA05933@ginger.lcs.mit.edu>
X-Loop: ietf@ietf.org

> Date: Wed, 26 Apr 2000 14:31:23 -0400
> From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
> To: ietf@ietf.org
> Subject: Re: draft-ietf-nat-protocol-complications-02.txt
> 
> Noel is happy to wait, and see who's right. (I've been through this exact
> same experience before, with CLNP, so I understand the life-cycle.) So far,
> I've been waiting for quite a few years with IPv6, and so far I'm right.
> 	[...]

Perhaps, we can start a pool to guess the date of the first IPv6-only
IETF meeting (laptop connections, wireless network, desktops all running
only IPv6).

Or, perhaps a true believer would like to propose that the network at
an upcoming IETF meeting support _only_ IPv6.  Perhaps the IPv6 working
group could staff a help desk.  I would make this proposal myself, but I
am concerned that I might be accused of trying to create a media spectacle
that would set back (?) IPv6 adoption by several years.

(If there is an IPv6-only  IETF meeting soon, I hope I can get one of
those IETF phone cards from Phil Gross -- I might want to go to me room
and get some work done.)

((Actually, I think an IPv6-only IETF meeting would be sort of neat.
I would at least try to get IPv6 working on my laptop.))

(((If we think an IPv6-only IETF meeting in impractical at this time, we
should consider not asking anyone else to migrate their network to IPv6
until it is mature enough to support an IETF meeting.)))

-tjs



From owner-ietf-outbound  Wed Apr 26 17:40:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA05257
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 17:40:01 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04977
	for <ietf@ietf.org>; Wed, 26 Apr 2000 17:25:05 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id PAA23682
	for ietf@ietf.org  env-from <vjs>;
	Wed, 26 Apr 2000 15:25:03 -0600 (MDT)
Date: Wed, 26 Apr 2000 15:25:03 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004262125.PAA23682@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: NAT->IPv6
X-Loop: ietf@ietf.org

> From: "Eliot Lear" <lear@cisco.com>

> It's also completely naive that source routing is your only threat.  One
> can break into a NAT.  One can forge packets and address them
> appropriately.  Firewalls prevent this, not NATs.

That statement is just as naive, unless you qualify the word "firewalls,"
and I'm not talking about accidents.  For example, what is a "router
firewall" except a lame NAT box?  It includes typical NAT filtering
rules and has NAT rewriting consisting of the identity map.  A NAT box
is like many routers sold as firewalls, except that it does better
filtering in its default configuration than a router firewall, and has
more than just the identity map for rewriting addresses and payloads.

You can't even say that pure application-layer or host-based firewalls
are always more secure than NAT boxes, because many host systems used for
such firewalls are happy to forward IP packets (although IP forwarding is
less likely to be on by default today).


I'm objecting to superstition cloaked as engineering, including 

   - "NAT boxes provide security",

   - "firewalls provide security but NAT boxes don't",

and my hot button,

   - "IP source routes are security threats."


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Wed Apr 26 17:50:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA05436
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 17:50:03 -0400 (EDT)
Received: from shell.nominum.com (shell.nominum.com [204.152.187.59])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05033
	for <ietf@ietf.org>; Wed, 26 Apr 2000 17:27:40 -0400 (EDT)
Received: from nominum.com (shell.nominum.com [204.152.187.59])
	by shell.nominum.com (Postfix) with ESMTP
	id 7732B3190A; Wed, 26 Apr 2000 14:23:21 -0700 (PDT)
Message-ID: <39075E48.5A93266F@nominum.com>
Date: Wed, 26 Apr 2000 14:23:20 -0700
From: "David R. Conrad" <David.Conrad@nominum.com>
Organization: Nominum, Inc.
X-Mailer: Mozilla 4.72 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
Cc: "David R. Conrad" <David.Conrad@nominum.com>,
        Bill Manning <bmanning@ISI.EDU>,
        Leonid Yegoshin <egoshin@genesyslab.com>, asp@partan.com,
        ietf@ietf.org, smd@EBONE.NET
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
References: <200004251930.PAA02332@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Keith,

> even the DNS names for major services may not be well maintained.
> at one time I did a survey of the reasons for mail bounces
> for one of my larger mailing lists. 

You appear to be saying that because historically people screwed up
configuring their DNS that it is impossible to rely on the DNS for critical
infrastructure.  This seems wrong to me.

If a properly configured DNS was a fundamental requirement of a working
network connection as is assumed by something like 8+8, I think it fairly
certain that any misconfigurations would be fixed as quickly as (say) a BGP
misconfiguration.

Rgds,
-drc



From owner-ietf-outbound  Wed Apr 26 18:00:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA05563
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 18:00:03 -0400 (EDT)
Received: from ce-nfs-1.cisco.com (ce-nfs-1.cisco.com [171.68.202.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05182
	for <ietf@ietf.org>; Wed, 26 Apr 2000 17:34:42 -0400 (EDT)
Received: from glock (dallas-nt-100.cisco.com [171.68.37.100])
	by ce-nfs-1.cisco.com (8.8.8+Sun/8.8.8) with SMTP id OAA03429;
	Wed, 26 Apr 2000 14:34:02 -0700 (PDT)
Message-ID: <022a01bfafc7$2433a3e0$642544ab@glock>
From: "Stephen Sprunk" <ssprunk@cisco.com>
To: <ned.freed@innosoft.com>, "Karl Auerbach" <karl@CAVEBEAR.COM>
Cc: "IETF" <ietf@ietf.org>
References: <BB61526CDE70D2119D0F00805FBECA2F16967274@RED-MSG-55> <01JOOZMEM1740004ZJ@MAUVE.INNOSOFT.COM>
Subject: Re: runumbering (was:  Re: IPv6: Past mistakes repeated?)
Date: Wed, 26 Apr 2000 16:33: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 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

draft-xie-stewart-sigtran-ddp-00 addresses redundancy and failover of
sessions within a server pool, where uncoordinated failover of sessions from
one endpoint to another is a requirement.  There is signifcant overheard and
indirection added to the session to achieve this.

We seem to be discussing a simpler requirement: coordinated movement of a
session from one ip:port pair on a single endpoint to a different ip:port
pair on the same endpoint.  Windows, buffer states, sequence numbers, etc.
could all remain the same.

I would think the latter requirement could be implemented as a simple TCP
"forward me" option.  For ESP/AH-protected sessions, no TCP-level
anti-hijacking protection seems necessary.  This could even be performed if
the original IP is suddenly not available and the other endpoint hasn't
given up on the connection yet; you send a "forward me" packet sourced from
the first IP, then listen for an ACK on the new IP.

I can think of no simple way (ie. without recreating IKE&AH inside TCP) to
do this for unprotected sessions; I'm not sure it's worth the effort to
solve either.

I'm sure there's something I'm missing here, or else this would have been
implemented 15 years ago...  Thoughts?

S

     |          |         Stephen Sprunk, K5SSS, CCIE #3723
    :|:        :|:        Network Consulting Engineer, NSA
   :|||:      :|||:       14875 Landmark Blvd #400; Dallas, TX
.:|||||||:..:|||||||:.    Email: ssprunk@cisco.com


----- Original Message -----
From: ned.freed@innosoft.com
To: Karl Auerbach
Cc: IETF
Sent: Wednesday, April 26, 2000 16:48
Subject: RE: runumbering (was: Re: IPv6: Past mistakes repeated?)


> > Turn it any way you want, TCP sessions can only survive renumbering
through
> > end to end mechanisms...

> Which raises the interesting (to me anyway) question: Is there value in
> considering a new protocol, layered on top of TCP, but beneath new
> applications, that provides an "association" the life of which transcends
> the TCP transports upon which it is constructed?

> I believe that if we had such a protocol that it would be a useful tool to
> solve many of the juggling acts that transpire under the heading of
> "mobile networking" as well as providing a way to continue (or
> "resume") connectivity after IP address changes.

> (I will, of course, be suitably embarrassed if someone points out that
> work is already going on to do this.)

  draft-xie-stewart-sigtran-ddp-00.txt

ned



From owner-ietf-outbound  Wed Apr 26 18:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA05825
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 18:10:02 -0400 (EDT)
Received: from shell.nominum.com (shell.nominum.com [204.152.187.59])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05309
	for <ietf@ietf.org>; Wed, 26 Apr 2000 17:43:02 -0400 (EDT)
Received: from nominum.com (shell.nominum.com [204.152.187.59])
	by shell.nominum.com (Postfix) with ESMTP
	id A89483190B; Wed, 26 Apr 2000 14:42:30 -0700 (PDT)
Message-ID: <390762C6.6320DD@nominum.com>
Date: Wed, 26 Apr 2000 14:42:30 -0700
From: "David R. Conrad" <David.Conrad@nominum.com>
Organization: Nominum, Inc.
X-Mailer: Mozilla 4.72 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: Steve Deering <deering@cisco.com>
Cc: "David R. Conrad" <David.Conrad@nominum.com>, ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
References: <200004251548.IAA08741@zed.isi.edu>
	 <v04220801b52b78f8ac20@[10.19.130.188]> <3905DD53.ACE85C3B@nominum.com> <v04220814b52c114f7dfe@[10.19.130.188]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Steve,

> I interpreted Bill's question as how would this be different
> than limiting IPv4 prefix advertisements to only /8s *today*, i.e., without
> renumbering the IPv4 Internet, so I answered accordingly.  I didn't think
> to interpret the question the way you did, because the answer is so obvious
> it wouldn't have made sense to ask.

Perhaps it is obvious to you, however it has been implied that one of the
advantages of v6 is that it has a limited number of TLAs which would be found
the the DFZ of the v6 Internet.  My point was that this is not an advantage of
v6 but rather an advantage of starting fresh and that the limitations on TLAs
is not an artifact of the v6 protocol, but rather an administrative limit
established by policy -- something quite malleable over time (perhaps more so
now given the creation of ICANN).

> IPv4 could in theory have 2^32 TLAs and IPv6 could in theory have
> 2^128 TLAs.  Are you saying that 2^32 TLAs would be OK?

No more than I would assume you'd say 2^128 TLAs would be OK.
 
Rgds,
-drc



From owner-ietf-outbound  Wed Apr 26 18:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA05926
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 18:20:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05322
	for <ietf@ietf.org>; Wed, 26 Apr 2000 17:44:19 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200004262133.GAA22662@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id GAA22662; Thu, 27 Apr 2000 06:33:06 +0900
Subject: Re: runumbering (was:  Re: IPv6: Past mistakes repeated?)
In-Reply-To: <BB61526CDE70D2119D0F00805FBECA2F16967281@RED-MSG-55> from Christian
 Huitema at "Apr 26, 2000 11:41:11 am"
To: Christian Huitema <huitema@microsoft.com>
Date: Thu, 27 Apr 2000 06:33:05 +0859 ()
CC: "'Paul Francis'" <pfrancis@aciri.org>, francis@ecal.com,
        narten@hygro.adsl.duke.eduu, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Christian;

> > But that architecture (hosts having multiple addresses
> > representing a site's multiple aggregation prefixes and
> > selecting among them) requires some method of identifying
> > hosts when they switch from one address to another
> > mid-connection.  I would assume that what people have in
> > mind for this are the mobility mechanisms?  (The alternative
> > is 8+8 or some variant, which I understand to be contentious
> > enough that it is a defacto non-starter.)

8+8 is not strictly necessary here unless you use locally scoped
addresses. As you can see, DNS reverse and, then, forward look
up is working fine for IPv4 hosts to know all the addresses of
other hosts with weak security.

Mobility, which does not work when home is unreachable, is no rubust
and, as is often the case with a psuedo multihoming proposal, does
not satisfy people needing multihoming. To make mobility rubust,
it is, instead, necessary to make mobile hosts multihomed.

> The rubbing point is that identifying is not quite enough -- you need
> "secure identifying" in order to avoid connection hijacking, probably
> through some variation of IPSEC. Which brings us back to NATs not being
> terribly helpful...

Wrong.

Use of complex and time consuming mechanisms such as IPSEC makes the
system insecure vulnerable to DoS attacks.

To avoid connection hijacking, cookies, such as TCP port and sequence
numbers, is enough, if they are long enough.

You may use optional IPSEC over it for extra security (it is more
secure primarily because IPSEC keys are long cookies), but you
don't need it.

							Masataka Ohta



From owner-ietf-outbound  Wed Apr 26 18:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA06052
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 18:30:03 -0400 (EDT)
Received: from leonid.genesyslab.com (leonid.genesyslab.com [204.94.142.156])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05709
	for <ietf@ietf.org>; Wed, 26 Apr 2000 18:04:08 -0400 (EDT)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id PAA00728;
	Wed, 26 Apr 2000 15:03:47 -0700
Date: Wed, 26 Apr 2000 15:03:47 -0700
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200004262203.PAA00728@leonid.genesyslab.com>
To: egoshin@genesyslab.com, ghudson@MIT.EDU
Subject: Re: NAT->IPv6
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

>From: Greg Hudson <ghudson@MIT.EDU>
>
>> But anybody clear understand that if your internal hosts do not have
>> a public address then all attacks may be only static - wait until
>> internal host open TCP to somewhere.
>
>This is a naive understanding.  Source-routing would let me get
>packets through to an internal address unless your NAT also acts as a
>firewall.
>
   Let's try. Today most of hosts have "IP-forwarding" switch off.
Because security reason.

>(Granted, I think it turns out that pretty much all NATs do this kind
>of firewalling in all cases.  But there's no reason why a firewall
>allowing only outgoing connections should be any more error-prone than
>a NAT gateway.)

   Greg, how you determine outgoing RTP connection like VoIP, for exam ?
UDP often has not clear "open" packet and difficult to control in classic
firewall. Fortunately VoIP may have H.323 or SIP negotiation first
but do you sure about another protocols ?

			       - Leonid Yegoshin, LY22



From owner-ietf-outbound  Wed Apr 26 20:00:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA06878
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 20:00:02 -0400 (EDT)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06837
	for <ietf@ietf.org>; Wed, 26 Apr 2000 19:56:03 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 2F4064CE0F; Wed, 26 Apr 2000 19:56:00 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id TAA29738;
	Wed, 26 Apr 2000 19:55:58 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 3D59735DC2; Wed, 26 Apr 2000 19:55:52 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: Christian Huitema <huitema@microsoft.com>,
        "'Paul Francis'" <pfrancis@aciri.org>, francis@ecal.com,
        narten@hygro.adsl.duke.eduu, ietf@ietf.org
Subject: Re: runumbering (was: Re: IPv6: Past mistakes repeated?) 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 26 Apr 2000 19:55:51 -0400
Sender: smb@research.att.com
Message-Id: <20000426235552.3D59735DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <200004262133.GAA22662@necom830.hpcl.titech.ac.jp>, Masataka Ohta wr
ites:

>
>To avoid connection hijacking, cookies, such as TCP port and sequence
>numbers, is enough, if they are long enough.

That's preposterous.  Long-enough numbers are good *if* and only if there are 
no eavesdroppers present.  We learned in 1993 that eavesdroppers are present 
on the Internet.  As for hijacking -- see 

@inproceedings{hijack,
        title = {A Simple Active Attack Against {TCP}},
        author = {Laurent Joncheray},
        year = 1995,
        booktitle = {Proceedings of the Fifth Usenix \Unix\ Security Symposium},
        address = {Salt Lake City, UT}
}

for a description of how to take over connections in today's world if you can 
see packets from it.  Again, we don't have to assume that our enemies are 
capable of it; we have empirical evidence.
>
>You may use optional IPSEC over it for extra security (it is more
>secure primarily because IPSEC keys are long cookies), but you
>don't need it.

Nonsense.  IPsec provides more security because the keys never travel over the 
wire in the clear.  Yes, key length is necessary to avoid guessing but it's 
very far from sufficient.


		--Steve Bellovin




From owner-ietf-outbound  Wed Apr 26 21:20:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA07640
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 21:20:02 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07584
	for <ietf@ietf.org>; Wed, 26 Apr 2000 21:14:04 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200004270106.KAA24221@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id KAA24221; Thu, 27 Apr 2000 10:06:08 +0900
Subject: Re: runumbering (was: Re: IPv6: Past mistakes repeated?)
In-Reply-To: <20000426235552.3D59735DC2@smb.research.att.com> from "Steven M.
 Bellovin" at "Apr 26, 2000 07:55:51 pm"
To: ietf@ietf.org
Date: Thu, 27 Apr 2000 10:06:06 +0859 ()
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Steve Bellovin;

> >To avoid connection hijacking, cookies, such as TCP port and sequence
> >numbers, is enough, if they are long enough.
> 
> That's preposterous.  Long-enough numbers are good *if* and only if there are 
> no eavesdroppers present.

"good *if* and only if"?

With cookies, a network is as secure as a telephone or fax network, which
is *GOOD* enough for credit card companies.

On the other hand, complex key handling mechanism introduces a
lot of chances for key eavesdropping.

> >You may use optional IPSEC over it for extra security (it is more
> >secure primarily because IPSEC keys are long cookies), but you
> >don't need it.
> 
> Nonsense.

Agreed, because TCP port and sequence numbers are long enough.

							Masataka Ohta



From owner-ietf-outbound  Wed Apr 26 21:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA07792
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 21:30:04 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07683
	for <ietf@ietf.org>; Wed, 26 Apr 2000 21:22:14 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id VAA02762;
        Wed, 26 Apr 2000 21:21:31 -0400 (EDT)
Message-Id: <200004270121.VAA02762@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "David R. Conrad" <David.Conrad@nominum.com>
cc: Keith Moore <moore@cs.utk.edu>, Bill Manning <bmanning@ISI.EDU>,
        Leonid Yegoshin <egoshin@genesyslab.com>, asp@partan.com,
        ietf@ietf.org, smd@EBONE.NET
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Wed, 26 Apr 2000 14:23:20 PDT."
             <39075E48.5A93266F@nominum.com> 
Date: Wed, 26 Apr 2000 21:21:31 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> > even the DNS names for major services may not be well maintained.
> > at one time I did a survey of the reasons for mail bounces
> > for one of my larger mailing lists. 
> 
> You appear to be saying that because historically people screwed up
> configuring their DNS that it is impossible to rely on the DNS for critical
> infrastructure.  This seems wrong to me.

I wouldn't say 'impossible'.  My point is that it is more difficult
to get this to work well than it might seem at first glance.

one reason I cited the DNS-related problems in email is that many 
people would consider email a critical service, and also one that
is employed on a daily basis by a large portion of one's network users.
so if people won't do what's necessary to make their email work, will 
they take the necessary steps to make other less critical services work?

> If a properly configured DNS was a fundamental requirement of a working
> network connection as is assumed by something like 8+8, I think it fairly
> certain that any misconfigurations would be fixed as quickly as (say) a BGP
> misconfiguration.

it depends ... on the size of the user population affected by a DNS
record (probably much smaller than the typical BGP misconfiguration,
and therefore less important) and also on where the errors are detected 
(email errors are usually detected by the sender of a message, since
that's who gets the bounced message.  but the party who has responsibility 
for fixing the error is usually not on the sender's end of things)

and note that even if you fix the reliability problems associated
with using DNS to do mapping from global endpoint IDs to local
routing information, you still have the performance problems to
deal with.

Keith



From owner-ietf-outbound  Wed Apr 26 21:40:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA08002
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 21:40:04 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07902
	for <ietf@ietf.org>; Wed, 26 Apr 2000 21:31:33 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id VAA02884;
        Wed, 26 Apr 2000 21:30:48 -0400 (EDT)
Message-Id: <200004270130.VAA02884@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Thomas Narten <narten@raleigh.ibm.com>
cc: Paul Francis <pfrancis@ACIRI.ORG>, smd@EBONE.NET, ietf@ietf.org
Subject: Re: multihoming (was Re: draft-ietf-nat-protocol-complications-02.txt) 
In-reply-to: Your message of "Wed, 26 Apr 2000 09:00:00 EDT."
             <200004261300.JAA01125@hygro.raleigh.ibm.com> 
Date: Wed, 26 Apr 2000 21:30:48 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> So one of IPv6's multihoming approaches is no worse than IPv4, 
> while another appears to be significantly better. 

...in terms of its impact on the routing system.  it's not clear
that having multiple addresses per host is significantly better
for applications in general.

my guess is that some applications will do well with multiple-address
style multihoming, while others will not.

but even if multiple-address style multihoming isn't a suitable 
replacement for all applications of single-address multihoming,
it's still nice to have as an option.

Keith



From owner-ietf-outbound  Wed Apr 26 22:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA09087
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 22:00:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09000
	for <ietf@ietf.org>; Wed, 26 Apr 2000 21:51:02 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id TAA27894
	for ietf@ietf.org  env-from <vjs>;
	Wed, 26 Apr 2000 19:50:59 -0600 (MDT)
Date: Wed, 26 Apr 2000 19:50:59 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004270150.TAA27894@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
X-Loop: ietf@ietf.org

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

> ...
> (email errors are usually detected by the sender of a message, since
> that's who gets the bounced message.  but the party who has responsibility 
> for fixing the error is usually not on the sender's end of things)
> ...

It may be irrelevant, and my personal sample size is trivially tiny. ...

In recent months very little email I've sent was bounced due to DNS errors
and only a little more has been delayed.  My logs say the delivery of much
more from others to me was delayed or failed because the sender's domain
did not resolve for hours or ever.  (familiar anti-spam hack, with my
guesses used to distinguish spam from legitimate mail suffering from bad
sender DNS)


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Wed Apr 26 22:10:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA09274
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 22:10:03 -0400 (EDT)
Received: from panther.cs.ucla.edu (Panther.CS.UCLA.EDU [131.179.128.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09024
	for <ietf@ietf.org>; Wed, 26 Apr 2000 21:53:28 -0400 (EDT)
Received: from localhost (terzis@localhost)
	by panther.cs.ucla.edu (8.9.1/UCLACS-5.0) with ESMTP id SAA27107;
	Wed, 26 Apr 2000 18:52:35 -0700 (PDT)
Date: Wed, 26 Apr 2000 18:52:35 -0700 (PDT)
From: Andreas Terzis <terzis@CS.UCLA.EDU>
To: Christian Huitema <huitema@microsoft.com>
cc: "'Paul Francis'" <pfrancis@aciri.org>, francis@ecal.com,
        narten@hygro.adsl.duke.edu, ietf@ietf.org
Subject: RE: runumbering (was:  Re: IPv6: Past mistakes repeated?)
In-Reply-To: <BB61526CDE70D2119D0F00805FBECA2F16967281@RED-MSG-55>
Message-ID: <Pine.SOL.4.10.10004261850290.26633-100000@panther.cs.ucla.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

Hi all,

I guess this is somewhat unrelated to the thread's maing topic but
the paper that Christian mentioned is available to everyone (as
well as all papers from SIGCOMM since 91) through SIGCOMM's web site.

The exact pointer for the paper mentioned below is

http://www.acm.org/pubs/articles/proceedings/comm/115992/p53-tsuchiya/p53-tsuchiya.pdf

regards,

-andreas

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Andreas A. Terzis,                  | UCLA Computer Science Department
http://irl.cs.ucla.edu/~terzis      | Internet Research Lab 

On Wed, 26 Apr 2000, Christian Huitema wrote:

> > I agree completely with what you say about needing to push
> > the multi-address complexity to the host.  As you kindly
> > pointed out (and I self-servingly expand on here), this is
> > an architecture I put forth about a decade ago in a sigcomm
> > paper (in Zurich, I don't remember the year).
> 
> The paper "Efficient and robust policy routing using multiple hierarchical
> addresses " was published at the 1991 SIGCOMM, in Zurich. ACM papers used to
> be available on line, but it seems that the ACM now wants to enforce pay per
> view.
> (http://www.acm.org/pubs/citations/proceedings/comm/115992/p53-tsuchiya/)
> 
> There is related work on an "Extended Transmission Control Protocol"
> available at http://www.chem.ucla.edu/~beichuan/etcp/
> 
> > But that architecture (hosts having multiple addresses
> > representing a site's multiple aggregation prefixes and
> > selecting among them) requires some method of identifying
> > hosts when they switch from one address to another
> > mid-connection.  I would assume that what people have in
> > mind for this are the mobility mechanisms?  (The alternative
> > is 8+8 or some variant, which I understand to be contentious
> > enough that it is a defacto non-starter.)
> 
> The rubbing point is that identifying is not quite enough -- you need
> "secure identifying" in order to avoid connection hijacking, probably
> through some variation of IPSEC. Which brings us back to NATs not being
> terribly helpful...
> 
> 



From owner-ietf-outbound  Wed Apr 26 22:20:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA09414
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 22:20:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09032
	for <ietf@ietf.org>; Wed, 26 Apr 2000 21:54:05 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id VAA02981;
        Wed, 26 Apr 2000 21:53:17 -0400 (EDT)
Message-Id: <200004270153.VAA02981@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Karl Auerbach <karl@CaveBear.com>
cc: IETF <ietf@ietf.org>
Subject: Re: runumbering (was: Re: IPv6: Past mistakes repeated?) 
In-reply-to: Your message of "Wed, 26 Apr 2000 08:33:00 PDT."
             <Pine.LNX.4.21.0004260823460.8285-100000@npax.cavebear.com> 
Date: Wed, 26 Apr 2000 21:53:17 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> > > So what I am suggesting is that it seems that there is evidence that one
> > > can do an "association" protocol that is relatively lightweight in terms
> > > of machinery, packets, packet headers, and end-node state if one leaves
> > > the heavy lifting of reliability to the underlying TCP protocol.
> > 
> > the on-the-wire protocol overhead is not that great.  the computational
> > overhead to the host and application, and the resulting loss in maximum
> > bandwidth, are fairly expensive.
> 
> I tend to disagree.  An association protocol only really does its work on
> connect/reconnect - hopefully a rear event -- and when the application
> says "let's establish a work-mark here".

no, that's not the bulk of the work.  the bulk of the work is just in
managing the extra copies of data (applications don't want to deal
with this explicitly, they want it handled by lower layers), in
detecting failures, distinguishing one kind of failure from another,
and in recovery.  for instance, to make the handoff efficient you
want to have the ability to say to your peer "please contact me on 
this new address" and have it do so.  but that message may be delayed
and meanwhile some new data might have been sent your way.  so the
host that is moving might also arrange to have data which was
sent to its old location forwarded to the new location for a time -
this saves the burden of getting the peer to retransmit everything.
but the "I'm moving" message might get dropped - this is actually 
likely because hosts don't usually know that they're moving and 
you have to assume that hosts that are mobile will be disconnected 
from time to time.  so you still need a fallback way to find your
peer's connections again - and this generally means some sort 
of resolution service for connection endpoints.   and the resolution
service probably also needs some redundancy.

now realize that it's quite possible for two peers to be moving
on the network at the same time, with their redirect messages
crossing each other and/or being dropped.  etc.  

there are a lot of states that have to be dealt with if you want
the system to be both reliable and efficient.
 
> And given that many of our applications are bursty/transactional vehicles
> we're not talking about supercomputers transfering bulk files of
> simulation data.

if you're talking about a general purpose facility then it probably 
does need to span a wide range of applications' needs.  perhaps not
supercomputers exchanging large matrices, but those are hardly the
only applications that care about performance and bandwidth.
even lowly web servers care about performance and bandwidth.

> > basically it's a lot more efficient to do some variant of mobile IP.
> 
> Mobility is not the issue.  Rather, there is use, distinct from mobilty,
> for an association that can persever longer than the underlying
> transport(s), including changes of IP addresses.  

if you build a level of indirection to handle this then it had better
handle mobility also.

and we don't need the kind of facility you're talking about just to
do renumbering.  nor would such a facility be sufficient, because
IP addresses are kept in other places besides just TCP connection state.

> In my eyes, an application that uses an association protocol to deal with
> changes and faults in underlying connectivity is a lot more in accord with
> end-to-end principles than if it relied on ad hoc transport/network
> address juggling.

either approach is end-to-end.  it's just that by putting this functionality
above the transport layer you end up duplicating the functionality that
was already implemented at lower layers, and you have to make the resulting
system fairly complex before you gain much for your trouble.

OTOH, by putting the mobility at the IP layer, you can let TCP take care of
the sequencing etc. and you don't have to implement it again in a higher
layer.

Keith



From owner-ietf-outbound  Wed Apr 26 22:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA09539
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 22:30:03 -0400 (EDT)
Received: from postoffice.cisco.com (postoffice.cisco.com [171.69.198.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09434
	for <ietf@ietf.org>; Wed, 26 Apr 2000 22:20:25 -0400 (EDT)
Received: from [171.71.38.64] (deering-office-pb.cisco.com [171.71.38.64]) by postoffice.cisco.com (8.8.7-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id TAA21388; Wed, 26 Apr 2000 19:16:35 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@postoffice
Message-Id: <v04220801b52d488e05ee@[171.71.38.64]>
In-Reply-To: <390762C6.6320DD@nominum.com>
References: <200004251548.IAA08741@zed.isi.edu>	
 <v04220801b52b78f8ac20@[10.19.130.188]> <3905DD53.ACE85C3B@nominum.com>
 <v04220814b52c114f7dfe@[10.19.130.188]> <390762C6.6320DD@nominum.com>
Date: Wed, 26 Apr 2000 19:16:01 -0700
To: "David R. Conrad" <David.Conrad@nominum.com>
From: Steve Deering <deering@cisco.com>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 2:42 PM -0700 4/26/00, David R. Conrad wrote:
>Perhaps it is obvious to you, however it has been implied that one of the
>advantages of v6 is that it has a limited number of TLAs which would be found
>the the DFZ of the v6 Internet.

The truth is subtly different than what what was implied or thought to be
implied, as I have tried to explain (with limited success, obviously), but
that's beside the point of your message:

>My point was that this is not an advantage of v6 but rather an advantage
>of starting fresh and that the limitations on TLAs is not an artifact of
>the v6 protocol, but rather an administrative limit established by policy

Yes, that's right.  If I understand correctly, you are upset by the
imprecise shorthand of saying "this is an advantage of IPv6 over IPv4"
and would prefer that we were careful always to say "this is an advantage
of the IPv6 addressing plan over the addressing plan of the existing IPv4
Internet, an advantage of starting fresh".  Fair enough.

Or are you asking us not to mention it at all, perhaps because there is
a plan to undertake a major renumbering of the IPv4 Internet so that
there will be a similarly small limit on the number of globally-advertised
IPv4 prefixes required to ensure reachability of all IPv4 customers?

>-- something quite malleable over time (perhaps more so
>now given the creation of ICANN).

In what way do you think the creation of ICANN might have made it easy or
easier to impose address changes on IPv4 customers?

> > IPv4 could in theory have 2^32 TLAs and IPv6 could in theory have
> > 2^128 TLAs.  Are you saying that 2^32 TLAs would be OK?
>
>No more than I would assume you'd say 2^128 TLAs would be OK.

So you agree there is a need to limit the number of TLAs to a number less
than that permitted by the address size, even for IPv4.  The longer address
of IPv6 does not introduce a new problem in this regard, contrary to what
you seemed to imply -- whatever method or policy you would use to limit
the number of TLAs in IPv4 could just as well be used in IPv6.  Or do you,
perhaps, think we really ought to be moving to a version of IP with 16-bit
addresses, to avoid the risk of creating too many TLAs?  :-)

Steve



From owner-ietf-outbound  Wed Apr 26 22:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA10609
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 22:40:04 -0400 (EDT)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10105
	for <ietf@ietf.org>; Wed, 26 Apr 2000 22:32:01 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 9A54D4CE49; Wed, 26 Apr 2000 22:31:59 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id WAA01703;
	Wed, 26 Apr 2000 22:31:58 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 89CBB35DC2; Wed, 26 Apr 2000 22:31:55 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 26 Apr 2000 22:31:54 -0400
Sender: smb@research.att.com
Message-Id: <20000427023155.89CBB35DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <200004270150.TAA27894@calcite.rhyolite.com>, Vernon Schryver writes

>It may be irrelevant, and my personal sample size is trivially tiny. ...
>
>In recent months very little email I've sent was bounced due to DNS errors
>and only a little more has been delayed.  My logs say the delivery of much
>more from others to me was delayed or failed because the sender's domain
>did not resolve for hours or ever.  (familiar anti-spam hack, with my
>guesses used to distinguish spam from legitimate mail suffering from bad
>sender DNS)
>

There is some data indicating that Keith is right, that there are problems in 
the DNS.  See, for example, http://www.research.att.com/~edith/Papers/infocom2000.ps

		--Steve Bellovin




From owner-ietf-outbound  Wed Apr 26 22:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA10771
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 22:50:02 -0400 (EDT)
Received: from mauve.innosoft.com (DSL107-055.brandx.net [209.55.107.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10120
	for <ietf@ietf.org>; Wed, 26 Apr 2000 22:32:04 -0400 (EDT)
From: ned.freed@innosoft.com
Received: from MAUVE.INNOSOFT.COM by MAUVE.INNOSOFT.COM (PMDF V6.1-1 #35243)
 id <01JOORXDFNG00004ZJ@MAUVE.INNOSOFT.COM> for ietf@ietf.org; Wed,
 26 Apr 2000 15:36:21 -0800 (PST)
Date: Wed, 26 Apr 2000 15:31:03 -0800 (PST)
Subject: Re: runumbering (was:  Re: IPv6: Past mistakes repeated?)
In-reply-to: "Your message dated Wed, 26 Apr 2000 16:33:54 -0500"
 <022a01bfafc7$2433a3e0$642544ab@glock>
To: Stephen Sprunk <ssprunk@cisco.com>
Cc: ned.freed@innosoft.com, Karl Auerbach <karl@CAVEBEAR.COM>,
        IETF <ietf@ietf.org>
Message-id: <01JOP3E0HF580004ZJ@MAUVE.INNOSOFT.COM>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
References: <BB61526CDE70D2119D0F00805FBECA2F16967274@RED-MSG-55>
 <01JOOZMEM1740004ZJ@MAUVE.INNOSOFT.COM>
X-Loop: ietf@ietf.org

> draft-xie-stewart-sigtran-ddp-00 addresses redundancy and failover of
> sessions within a server pool, where uncoordinated failover of sessions from
> one endpoint to another is a requirement.  There is signifcant overheard and
> indirection added to the session to achieve this.

> We seem to be discussing a simpler requirement: coordinated movement of a
> session from one ip:port pair on a single endpoint to a different ip:port
> pair on the same endpoint.  Windows, buffer states, sequence numbers, etc.
> could all remain the same.

The stated requirement was "an association that will outlast the TCP
connections it is based on". I saw (and see) nothing that limited this to
coordinated moves set up in advance.

You're right that it's a simpler problem, but the general problem is what's
on the table IMO.

And if ISO session layer is seen as comparable, we're *definitely* in the more
general problem space. (Although whether or not ISO session layer actually
solved such problems is another matter -- it sorta did on paper if you read the
specifications optimistically, but it never solved any of these problems in
practice. And I have the misfortunate of having had to deal with ISO session
layer stuff a *lot*.)

				Ned



From owner-ietf-outbound  Wed Apr 26 23:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA10881
	for ietf-outbound.10@ietf.org; Wed, 26 Apr 2000 23:00:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10845
	for <ietf@ietf.org>; Wed, 26 Apr 2000 22:56:09 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id UAA28894
	for ietf@ietf.org  env-from <vjs>;
	Wed, 26 Apr 2000 20:56:06 -0600 (MDT)
Date: Wed, 26 Apr 2000 20:56:06 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004270256.UAA28894@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
X-Loop: ietf@ietf.org

> From: "Steven M. Bellovin" <smb@research.att.com>

> ...
> There is some data indicating that Keith is right, that there are problems in 
> the DNS.  See, for example, http://www.research.att.com/~edith/Papers/infocom2000.ps

I don't think I understand the connection between that paper about
"Prefetching the Means for Dcoument Transfer: A New Approach for Reducing
Web Latency" and Keith's statement that DNS email errors are usually on
the receiver's side:

] (email errors are usually detected by the sender of a message, since
] that's who gets the bounced message.  but the party who has responsibility 
] for fixing the error is usually not on the sender's end of things)

My perhaps irrelevant, boring, or even wrong claim was that I'm seeing
more sender-side than receiver-side SMTP+DNS problems.

If the relevance of that paper is that people are have fun and
games with DNS to help HTTP, and that causes DNS errors that in
turn cause DNS problems seen by HTTP clients, then that's consistent
with my personal experience and my claim.  I see many crazy
DNS failures in my personal web surfing.  (crazy either because
obviously silly for a very big, presumably competently run  site
or because temporary, which says either roots are hosed or the same
very big, presumably competent site is crazy...have I mentioned
lately how frequently Akamai is not working for me?)


I bet that the types and frequencies of DNS errors varies with the
application, which strikes me as a significant change from how things used
to be.  For example, how many SMTP servers are behind DNS names that do
fancy load balancing?--yes, I think I can name a very few, but isn't the
vast majority of SMTP load balancing and so forth based on turning off
the listen socket (e.g. sendmail), MX records, and non-fancy round-robin
RR serving?  On the extreme, every venture capital fund seems to still be
shoveling money at anyone who wants to try anything you'd care to mention
(and lots more besides) to make HTTP go faster, and many of those schemes
seem to involve DNS creativity.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu Apr 27 02:00:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA17726
	for ietf-outbound.10@ietf.org; Thu, 27 Apr 2000 02:00:03 -0400 (EDT)
Received: from cbinmail.cisco.com (cbinmail.cisco.com [192.135.244.68])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17639
	for <ietf@ietf.org>; Thu, 27 Apr 2000 01:55:13 -0400 (EDT)
Received: from ashankar-pc ([192.135.245.153])
	by cbinmail.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id LAA18054;
	Thu, 27 Apr 2000 11:24:34 +0530 (IST)
Message-Id: <4.1.20000427111542.00a4e5b0@cbinmail>
X-Sender: ashankar@cbinmail
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 27 Apr 2000 11:21:24 +0530
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, ietf@ietf.org
From: Shankar Agarwal <ashankar@cisco.com>
Subject: RE: IPv6: Past mistakes repeated?
Cc: jnc@ginger.lcs.mit.edu
In-Reply-To: <200004241921.PAA07009@ginger.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 03:21 PM 4/24/00 -0400, J. Noel Chiappa wrote:
>A couple of routing points, not related to NAT:
>
>    > From: Ian King <iking@microsoft.com>
>
>    > so that it is realistic for businesses to regularly ask for assignments
>    > in more granular chunks; rather than grabbing a class A-size space
>    > "just in case", big users would be willing to request another 256 when
>    > the new branch office opens, then another 64 for the summer interns...
>
>Sorry, this doesn't work - at least with IPvN (N=4,6) addresses as currently
>constituted. The routing system (i.e. the software that computes paths
>through the network) uses those addresses as the namespace it works on, and
>to make the routing scale properly (a.k.a. "keep the network running"), those
>addresses have to be aggregable.
>
>In other words, you need to be able to have a single routing table entry that
>covers a chunk of the network (such as a company's in-house network) - and
>that routing table entry can't include other things as well. If a company,
>etc, had addresses assigned in dribs and drabs, the way you suggest, that
>company's addresses would no longer have that property.

This is because the way things are right now that we are thinking this way.
But we can change it.
We can make it like this.
1) Apply for the number of address that u need. i.e. small chunk.
2) If u need more address later on give back the original chunk and apply
for the large chunk. 

I know that the 2nd case will not make many people happy i.e. they will
have to expend little more effort but then with proper implementaion even
that will be null and i think the price is not much rather than wasting
address. And with this the current routing will work fine because u will
still have the network portion for the entire corporate same.

>
>Other namespaces, which don't have to include location information, just
>identification (e.g. IEEE 48-bit numbers) work just fine with this kind of
>allocation policy - but not any namespace used by path selection in a large
>network.
>
>
>    > From: Steve Deering <deering@cisco.com>
>
>    > making each house a TLA does not strike me as a scalable multihoming
>    > solution for very large numbers of houses, given the current state of
>    > the routing art.
>
>The restriction has little to do with the current state of the routing art
>(which is not to say that better path-selection architectures than the one
>the Internet is currently using do not exist :-).
>
>Even with the best routing system, it still couldn't support tracking large
>numbers of houses as individual destinations (i.e. having individual routing
>tables extries across the global scope) - even if the routers had large
>enough route table memories to hold the 100's of millions of routes which
>could result.
>
>	Noel
>
>



From owner-ietf-outbound  Thu Apr 27 03:20:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA24749
	for ietf-outbound.10@ietf.org; Thu, 27 Apr 2000 03:20:02 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA24676
	for <ietf@ietf.org>; Thu, 27 Apr 2000 03:10:55 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.03426-0@bells.cs.ucl.ac.uk>; Thu, 27 Apr 2000 08:10:28 +0100
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-reply-to: Your message of "Wed, 26 Apr 2000 14:31:23 EDT." <200004261831.OAA05933@ginger.lcs.mit.edu>
Date: Thu, 27 Apr 2000 08:10:31 +0100
Message-ID: <941.956819431@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <200004261831.OAA05933@ginger.lcs.mit.edu>, "J. Noel Chiappa" typed:

 >>    > right, noels wrong.
 
 >>Noel is happy to wait, and see who's right. (I've been through this exact
 >>same experience before, with CLNP, so I understand the life-cycle.) So far,
 >>I've been waiting for quite a few years with IPv6, and so far I'm right.

 >>Let's see, how many years have these standards been out, and how much
 >>deployment has there been? Hmm, RFC-1883 was in December 1995. Can you point
 >>me to *any* other IETF product that, 5 years after the Proposed Standard came
 >>out, still hadn't been significantly deployed - and then went on to be a
 >>success?

 >>No?

wrong - multicast.

 >>I didn't think so.
 
read again  - LOTS of things have seen almost no deployment since
being standar,d and lots of things haev seen deploymewnt (e.g. napster
hit around 15% of college traffic) without even a breath of an i-d
 
 >>    > NATs are not only bad e2e karma, they are bad tech

 >>I'm not denying that - and I've said as much. All address-sharing devices are
 >>problematic, and some (e.g. NAT boxes) are downright disgusting kludges.
 >>
 >>However, history shows that bad tech doesn't magically replace itself, it has
 >>to be replaced by an economically viable alternative. (For an example of this
 >>principle in action, note that the vast majority of cars are still powered by
 >>reciprocating internal-combustion engines... talk about poor basic concept!
 >>But I digress....)

i agree...

 >>Judging from the real world out there, it appears that IPv6 isn't a viable
 >>alternative.

i agree its not worth holding one's breath...

 cheers

   jon



From owner-ietf-outbound  Thu Apr 27 07:10:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA26416
	for ietf-outbound.10@ietf.org; Thu, 27 Apr 2000 07:10:02 -0400 (EDT)
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26351
	for <ietf@ietf.org>; Thu, 27 Apr 2000 07:04:12 -0400 (EDT)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate2.mot.com (motgate2 2.1) with ESMTP id EAA16588 for <ietf@ietf.org>; Thu, 27 Apr 2000 04:03:53 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id EAA15249 for <ietf@ietf.org>; Thu, 27 Apr 2000 04:03:32 -0700 (MST)]
Received: from email.mot.com (t_il06_t_port4.corp.mot.com [129.188.171.64]) by il27exb01.cig.mot.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id 21RPP8NN; Thu, 27 Apr 2000 06:03:14 -0500
Sender: stewrtrs@pobox.mot.com
Message-ID: <39082D00.56D3744D@email.mot.com>
Date: Thu, 27 Apr 2000 12:05:20 +0000
From: Randall Stewart <rstewar1@email.mot.com>
Organization: NAT
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Stephen Sprunk <ssprunk@cisco.com>
CC: ned.freed@innosoft.com, Karl Auerbach <karl@CAVEBEAR.COM>,
        IETF <ietf@ietf.org>
Subject: Re: runumbering (was:  Re: IPv6: Past mistakes repeated?)
References: <BB61526CDE70D2119D0F00805FBECA2F16967274@RED-MSG-55> <01JOOZMEM1740004ZJ@MAUVE.INNOSOFT.COM> <022a01bfafc7$2433a3e0$642544ab@glock>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Ok,

I will stop being a lurker and chime in since our draft was
mentioned :->

Stephen Sprunk wrote:
> 
> draft-xie-stewart-sigtran-ddp-00 addresses redundancy and failover of
> sessions within a server pool, where uncoordinated failover of sessions from
> one endpoint to another is a requirement.  There is signifcant overheard and
> indirection added to the session to achieve this.
> 
Yes, I think you sum up what DDP attempts to do but I strongly
disagree with your "signifcant overhead" argument. Qiaobing and I
have been playing with DDP now for quite a number of years. It has
some overhead on the wire (not much) since the overhead is mainly
upfront i.e. when you want to go hold a talk to someone you
may need to do a query to find out where it is and where all
its redundant pools are. This drops in to a cache in any sensible
implementation and then within some period will need to expire
or be updated. Even when the cache is updated it does NOT interfere
with the ongoing communication (its done in parrallel). So basically
the delay overhead to talk to a peer is possibly one round trip to
the local ENRP server (of course local is not necessarrily on the
machine you are on but it could be :-0). In some cases there may
be no delay. In particular, the ability to send to a address (pre-known)
and then do a parrallel query to the ENRP deamon. We did not
get this one in the draft but I am sure future updates will have
this ...

The point is I can't see what your "signifcant overhead" is. Yes
it will take a query to get some redundancy but after 5 years of
work I think we have the overhead as slim as we can... of course
perhaps the working group will show us a way to reduce it further
but we will see....

> We seem to be discussing a simpler requirement: coordinated movement of a
> session from one ip:port pair on a single endpoint to a different ip:port
> pair on the same endpoint.  Windows, buffer states, sequence numbers, etc.
> could all remain the same.

In its basic state this is what DDP does do.. i.e. if you don't have
multiple peers. But of course if the route fails between you and
your peer, the conversations over.. until the path is back up.

> 
> I would think the latter requirement could be implemented as a simple TCP
> "forward me" option.  For ESP/AH-protected sessions, no TCP-level
> anti-hijacking protection seems necessary.  This could even be performed if
> the original IP is suddenly not available and the other endpoint hasn't
> given up on the connection yet; you send a "forward me" packet sourced from
> the first IP, then listen for an ACK on the new IP.
> 
> I can think of no simple way (ie. without recreating IKE&AH inside TCP) to
> do this for unprotected sessions; I'm not sure it's worth the effort to
> solve either.
> 
> I'm sure there's something I'm missing here, or else this would have been
> implemented 15 years ago...  Thoughts?

Yes, having worked at solving this problem for 5 years you are missing
some of the subtle nature of where the different state is. You really
must have a seperate state around, unless the "new IP" is attached to
the same machine. In that case you end up with something that looks
like SCTP to provide the redundancy, i.e. use the "new IP" address.

R


> 
> S
> 
>      |          |         Stephen Sprunk, K5SSS, CCIE #3723
>     :|:        :|:        Network Consulting Engineer, NSA
>    :|||:      :|||:       14875 Landmark Blvd #400; Dallas, TX
> .:|||||||:..:|||||||:.    Email: ssprunk@cisco.com
> 
> ----- Original Message -----
> From: ned.freed@innosoft.com
> To: Karl Auerbach
> Cc: IETF
> Sent: Wednesday, April 26, 2000 16:48
> Subject: RE: runumbering (was: Re: IPv6: Past mistakes repeated?)
> 
> > > Turn it any way you want, TCP sessions can only survive renumbering
> through
> > > end to end mechanisms...
> 
> > Which raises the interesting (to me anyway) question: Is there value in
> > considering a new protocol, layered on top of TCP, but beneath new
> > applications, that provides an "association" the life of which transcends
> > the TCP transports upon which it is constructed?
> 
> > I believe that if we had such a protocol that it would be a useful tool to
> > solve many of the juggling acts that transpire under the heading of
> > "mobile networking" as well as providing a way to continue (or
> > "resume") connectivity after IP address changes.
> 
> > (I will, of course, be suitably embarrassed if someone points out that
> > work is already going on to do this.)
> 
>   draft-xie-stewart-sigtran-ddp-00.txt
> 
> ned

-- 
Randall R. Stewart
Member Technical Staff
Network Architecture and Technology (NAT)
847-632-7438 fax:847-632-6733



From owner-ietf-outbound  Thu Apr 27 09:51:05 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA28880
	for ietf-outbound.10@ietf.org; Thu, 27 Apr 2000 09:50:02 -0400 (EDT)
Received: from mail1.cai.com (mail1.cai.com [141.202.248.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28737
	for <ietf@ietf.org>; Thu, 27 Apr 2000 09:41:40 -0400 (EDT)
Received: by usilms50.cai.com with Internet Mail Service (5.5.2650.21)
	id <JWLZQ7SQ>; Thu, 27 Apr 2000 09:43:59 -0400
Message-ID: <27B34B6046FFD311BD880050046DFAD492BBB1@usilms01.cai.com>
From: "Evstiounin, Mikhail" <Mikhail.Evstiounin@ca.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>, ietf@ietf.org
Subject: RE: runumbering (was: Re: IPv6: Past mistakes repeated?)
Date: Thu, 27 Apr 2000 09:42:51 -0400
Return-Receipt-To: "Evstiounin, Mikhail" <Mikhail.Evstiounin@ca.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Loop: ietf@ietf.org

> From:	Masataka Ohta [SMTP:mohta@necom830.hpcl.titech.ac.jp]
> "good *if* and only if"?
> 
> With cookies, a network is as secure as a telephone or fax network, which
> is *GOOD* enough for credit card companies.

Not exactly. It's pretty easy to intercept any packet on the Internet,
that's not
the case for regular phones. Nevertheless, I've read some warnings from
credit companies about not using wireless phones because of security
concerns. Especially, if you live in a crowded area.
... 
> 							Masataka Ohta



From owner-ietf-outbound  Thu Apr 27 11:00:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA01618
	for ietf-outbound.10@ietf.org; Thu, 27 Apr 2000 11:00:02 -0400 (EDT)
Received: from doberman.cwusa.com (doberman-dmz.cwusa.com [146.135.88.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01519
	for <ietf@ietf.org>; Thu, 27 Apr 2000 10:53:08 -0400 (EDT)
Received: from us-cwi-iis-a02.cwusa.com ([146.135.85.100])
	by doberman.cwusa.com (8.9.1/8.9.1) with SMTP id KAA20196
	for <ietf@ietf.org>; Thu, 27 Apr 2000 10:52:25 -0400 (EDT)
Received: FROM us-cwi-exc-a10.cwusa.com BY us-cwi-iis-a02.cwusa.com ; Thu Apr 27 10:49:09 2000 -0400
Received: by us-cwi-exc-a10.cwi.cablew.com with Internet Mail Service (5.5.2650.21)
	id <JPDRWTQN>; Thu, 27 Apr 2000 10:52:06 -0400
Message-ID: <F685A00DB7B4D111B2400020AFFC2D580D702E8E@us-cwi-exc-a03.cwi.cablew.com>
From: "BookIII, Robert" <Robert.BookIII@cwusa.com>
To: "'Vernon Schryver'" <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: RE: draft-ietf-nat-protocol-complications-02.txt
Date: Thu, 27 Apr 2000 10:52:06 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

This may be a divergence from the topic, so I'll apologize in advance, but
Vernon's point about bounced emails struck a cord with me. I made the
mistake of leaving a couple of options on my MS Outlook which causes a
receipt to be sent back to me when an email is delivered and when it's read.
At this point, the flurry has calmed down from my first email to the list,
save for a couple of auto-responses from NTMail in the name of
951rkly@sbs.oxon.sch.uk <mailto:951rkly@sbs.oxon.sch.uk> . I've been getting
repetitive delivery and read acknowledgements, which seemed to have abated
but have started up again. Does anyone know how I could go about addressing
this? Thanks for your time and consideration.

		-----Original Message-----
		From:	Vernon Schryver [mailto:vjs@calcite.rhyolite.com]
		Sent:	Wednesday, April 26, 2000 10:56 PM
		To:	ietf@ietf.org
		Subject:	Re:
draft-ietf-nat-protocol-complications-02.txt

		> From: "Steven M. Bellovin" <smb@research.att.com>

		> ...
		> There is some data indicating that Keith is right, that
there are problems in 
		> the DNS.  See, for example,
http://www.research.att.com/~edith/Papers/infocom2000.ps

		I don't think I understand the connection between that paper
about
		"Prefetching the Means for Dcoument Transfer: A New Approach
for Reducing
		Web Latency" and Keith's statement that DNS email errors are
usually on
		the receiver's side:

		] (email errors are usually detected by the sender of a
message, since
		] that's who gets the bounced message.  but the party who
has responsibility 
		] for fixing the error is usually not on the sender's end of
things)

		My perhaps irrelevant, boring, or even wrong claim was that
I'm seeing
		more sender-side than receiver-side SMTP+DNS problems.

		If the relevance of that paper is that people are have fun
and
		games with DNS to help HTTP, and that causes DNS errors that
in
		turn cause DNS problems seen by HTTP clients, then that's
consistent
		with my personal experience and my claim.  I see many crazy
		DNS failures in my personal web surfing.  (crazy either
because
		obviously silly for a very big, presumably competently run
site
		or because temporary, which says either roots are hosed or
the same
		very big, presumably competent site is crazy...have I
mentioned
		lately how frequently Akamai is not working for me?)


		I bet that the types and frequencies of DNS errors varies
with the
		application, which strikes me as a significant change from
how things used
		to be.  For example, how many SMTP servers are behind DNS
names that do
		fancy load balancing?--yes, I think I can name a very few,
but isn't the
		vast majority of SMTP load balancing and so forth based on
turning off
		the listen socket (e.g. sendmail), MX records, and non-fancy
round-robin
		RR serving?  On the extreme, every venture capital fund
seems to still be
		shoveling money at anyone who wants to try anything you'd
care to mention
		(and lots more besides) to make HTTP go faster, and many of
those schemes
		seem to involve DNS creativity.


		Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu Apr 27 11:20:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA02084
	for ietf-outbound.10@ietf.org; Thu, 27 Apr 2000 11:20:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01952
	for <ietf@ietf.org>; Thu, 27 Apr 2000 11:12:54 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id JAA09824
	for ietf@ietf.org  env-from <vjs>;
	Thu, 27 Apr 2000 09:12:50 -0600 (MDT)
Date: Thu, 27 Apr 2000 09:12:50 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200004271512.JAA09824@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: draft-ietf-nat-protocol-complications-02.txt
X-Loop: ietf@ietf.org

> From: "BookIII, Robert" <Robert.BookIII@cwusa.com>

> ...
> save for a couple of auto-responses from NTMail in the name of
> ...

> but have started up again. Does anyone know how I could go about addressing
> this? Thanks for your time and consideration.

You can expect at least 3 and usually several more "vacation" notices,
delayed delivery warnings, and non-delivery bounces for each message you
send to the main IETF list over the course the week or 10 days after
sending.

By my recollections, even 10 years ago such garbage was unusual and
cause for complaints and apologies.  That nothing happens today, not even
the automatic removal of persistently broken addresses, is a commentary
on the changing nature of the IETF.  If you're an optimist, you might
infer only something about growth.

I've thought of suggesting that the IESG should maintain an address to
which such bounces could be sent to remove the offending address, but
then I've also throught of the reasonable (e.g. authentication) and silly
(e.g. censorship) controveries such a suggestion would trigger.


I've also thought of mentioning that I really don't need to see a dozen
announcements for the same junket of some other organization's boondoogle,
but then I've remembered we've gone through that many times.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu Apr 27 17:10:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA06873
	for ietf-outbound.10@ietf.org; Thu, 27 Apr 2000 17:10:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06730
	for <ietf@ietf.org>; Thu, 27 Apr 2000 17:00:21 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id RAA09763;
	Thu, 27 Apr 2000 17:00:14 -0400
Date: Thu, 27 Apr 2000 17:00:14 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200004272100.RAA09763@ginger.lcs.mit.edu>
To: ietf@ietf.org, moore@cs.utk.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

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

    >> You appear to be saying that because historically people screwed up
    >> configuring their DNS that it is impossible to rely on the DNS for
    >> critical infrastructure.

    > I wouldn't say 'impossible'. My point is that it is more difficult to
    > get this to work well than it might seem at first glance. ... and note
    > that even if you fix the reliability problems associated with using DNS
    > to do mapping from global endpoint IDs to local routing information,
    > you still have the performance problems to deal with.

Are you making the assumption that we can grow the network in size (let's not
even get into functionality) *without* adding extra architecture/mechanism?

In other words, is your problem with DNS as currently designed/implemented/
maintained - or is it more (as I seem to recall from previous messages from
you) with the general notion that more complex things are fundamentally bad
(since any extra mechanism is also a place for something to go wrong, or a
place to incur overhead)?

If so, I'd say that's false economy - to paraphrase Lincoln on leg length, a
network of a certain size and functionality neeeds a certain amount of
complexity, and if you fail to architect it in (i.e. cleanly), it will get
added around the edges in all sorts of ugly warts (i.e. the kind the Internet
stack is currently infested with).

	Noel



From owner-ietf-outbound  Fri Apr 28 02:50:40 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA25301
	for ietf-outbound.10@ietf.org; Fri, 28 Apr 2000 02:50:02 -0400 (EDT)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25278
	for <ietf@ietf.org>; Fri, 28 Apr 2000 02:49:37 -0400 (EDT)
From: Dave_Lee@3com.com
Received: from new-york.3com.com (new-york.3com.com [129.213.157.12])
	by seattle.3com.com (8.8.8/8.8.8) with ESMTP id XAA01645;
	Thu, 27 Apr 2000 23:49:28 -0700 (PDT)
Received: from hqoutbound.ops.3com.com (hqoutbound.OPS.3Com.COM [139.87.48.104])
	by new-york.3com.com (8.8.8/8.8.8) with SMTP id XAA01780;
	Thu, 27 Apr 2000 23:49:25 -0700 (PDT)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999))  id 882568CE.005E4F9B ; Thu, 27 Apr 2000 10:10:07 -0700
X-Lotus-FromDomain: 3COM
To: "Jon William Toigo" <jtoigo@IntNet.net>
cc: ietf@ietf.org, ips@ece.cmu.edu
Message-ID: <882568CE.005E4DE7.00@hqoutbound.ops.3com.com>
Date: Thu, 27 Apr 2000 10:10:48 -0700
Subject: Re: SCSI over IP (fwd)
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org



Jon -

Keep in mind that there is no standards track document - the document you have
is merely a proposal by one set of parties.  This effort is pre-WG (chairs,
charters, and final approvals are not complete to my knowledge).  There are a
number of parties that would like to see a proposed standard in the shortest
amount of time but it is a large area.  Thus, it's too early to speculate on
products (standards compatible products, at any rate) but I'd imagine that it'd
be *at least* towards 1Q 2001before we get to proposed standard.

Only one IP networking vendor (Cisco) that I'm aware of has made any public
direction statements in this area, though there is certainly interest among
others - more IP traffic is good for business, after all.  Obviously, the
storage networking industry is interested as well.

Dave




"Jon William Toigo" <jtoigo@IntNet.net> on 04/26/2000 08:33:18 AM

Sent by:  "Jon William Toigo" <jtoigo@IntNet.net>


To:   Dave Lee/HQ/3Com
cc:   ietf@ietf.org
Subject:  Re: SCSI over IP (fwd)




Thanks for the referral, Dave.  Now that I have the SCSI over IP RFC text, I
am wondering how soon, if ever, we will likely see a standard and/or product
based on the specification?

To your knowledge, is SCSI over IP being pursued in earnest by IP networking
equipment companies at present?

JWT







From owner-ietf-outbound  Fri Apr 28 10:01:04 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA01416
	for ietf-outbound.10@ietf.org; Fri, 28 Apr 2000 10:00:02 -0400 (EDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01276
	for <ietf@ietf.org>; Fri, 28 Apr 2000 09:54:37 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA00814;
        Fri, 28 Apr 2000 09:54:08 -0400 (EDT)
Message-Id: <200004281354.JAA00814@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
cc: ietf@ietf.org, moore@cs.utk.edu
Subject: Re: draft-ietf-nat-protocol-complications-02.txt 
In-reply-to: Your message of "Thu, 27 Apr 2000 17:00:14 EDT."
             <200004272100.RAA09763@ginger.lcs.mit.edu> 
Date: Fri, 28 Apr 2000 09:54:08 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> 
>     >> You appear to be saying that because historically people screwed up
>     >> configuring their DNS that it is impossible to rely on the DNS for
>     >> critical infrastructure.
> 
>     > I wouldn't say 'impossible'. My point is that it is more difficult to
>     > get this to work well than it might seem at first glance. ... and note
>     > that even if you fix the reliability problems associated with using DNS
>     > to do mapping from global endpoint IDs to local routing information,
>     > you still have the performance problems to deal with.
> 
> Are you making the assumption that we can grow the network in size (let's not
> even get into functionality) *without* adding extra architecture/mechanism?

no, it's fairly clear to me that we either constrain how people connect
their networks together, or we have to change the mechanism by which we 
propagate and/or compute routes (what kind of changes, or how to deploy
them, are not clear), if we want to make the network considerably larger. 

my general point is not that additional complexity is always bad - but if 
you're going to add a lot of complexity you should get a better system as a 
result.  and a system that doesn't meet the needs of applications is 
not clearly better. 

and the specific point is that folks who are thinking "just use DNS
or something like it" probably haven't looked at this in enough
detail, and/or they have a oversimplified view of applications' needs.

Keith



From owner-ietf-outbound  Sat Apr 29 17:43:01 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA22187
	for ietf-outbound.10@ietf.org; Sat, 29 Apr 2000 17:40:02 -0400 (EDT)
Received: from npax.cavebear.com (npax.cavebear.com [192.203.17.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22150
	for <ietf@ietf.org>; Sat, 29 Apr 2000 17:39:20 -0400 (EDT)
Received: from localhost (karl@localhost)
	by npax.cavebear.com (8.9.3/8.9.3) with ESMTP id OAA22638
	for <ietf@ietf.org>; Sat, 29 Apr 2000 14:38:51 -0700
Date: Sat, 29 Apr 2000 14:38:51 -0700 (PDT)
From: Karl Auerbach <karl@CaveBear.com>
Reply-To: Karl Auerbach <karl@CaveBear.com>
To: IETF <ietf@ietf.org>
Subject: Re: runumbering (was: Re: IPv6: Past mistakes repeated?) 
In-Reply-To: <200004270153.VAA02981@astro.cs.utk.edu>
Message-ID: <Pine.LNX.4.21.0004291418060.22505-100000@npax.cavebear.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


> > > the on-the-wire protocol overhead is not that great.  the computational
> > > overhead to the host and application, and the resulting loss in maximum
> > > bandwidth, are fairly expensive.
> > 
> > I tend to disagree.  An association protocol only really does its work on
> > connect/reconnect - hopefully a rear event -- and when the application
> > says "let's establish a work-mark here".
> 
> no, that's not the bulk of the work.  the bulk of the work is just in
> managing the extra copies of data (applications don't want to deal
> with this explicitly, they want it handled by lower layers), in
> detecting failures, distinguishing one kind of failure from another,
> and in recovery.

You are describing a super-transport, a TCP on TCP.

I don't want a super-transport.

All I'm trying to do is to create a means by which an aware application
can recognize transport (TCP) connection failures in a way that allows the
communicating parts of that aware application to resynchronize their
activity over a new TCP connection.  That's hardly the heavyweight engine
that you are positing, and there is no need for the protocol to retain
data or do anyting other than allow the communicating applications to
declare to one-another that they have reached a namable point in their
interaction.

Need Freed has pointed me to some interesting drafts that might do the
trick (or might be a good headstart)
  draft-xie-stewart-sigtran-ddp-00.txt

> OTOH, by putting the mobility at the IP layer, you can let TCP take care of
> the sequencing etc. and you don't have to implement it again in a higher
> layer.

Sure, IP address shell games do frequently work.  So does NAT.

By putting long-distance mobility at the IP layer we force the packet
path mechanisms to engage in a game of patting its head while rubbing its
tummy and reciting the alphabet backwards.

That's sometimes the right thing to do, other times it is not - the choice
is application dependent.

Sometimes it is easier to simply break a TCP connection and later create a
new TCP connection - and that's not just for mobility; it has many other
uses.

		--karl--





From owner-ietf-outbound  Sun Apr 30 02:02:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA03376
	for ietf-outbound.10@ietf.org; Sun, 30 Apr 2000 02:00:04 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03327
	for <ietf@ietf.org>; Sun, 30 Apr 2000 01:54:00 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200004300553.OAA06363@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id OAA06363; Sun, 30 Apr 2000 14:53:33 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <4.3.1.2.20000426100233.00bdcbc0@porky> from Matt Holdrege at "Apr
 26, 2000 10:07:29 am"
To: Matt Holdrege <holdrege@lucent.com>
Date: Sun, 30 Apr 2000 14:53:32 +0859 ()
CC: Thomas Narten <narten@raleigh.ibm.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Matt;

> >I don't know about you, but it scares me to read the various forecasts
> >about how wireless will transform the landscape over the next few
> >years. E.g., more wireless phones with internet connectivity than
> >PCs. The numbers are just staggering and the associated demand for
> >addresses will be astonishing. We ain't seen nothing yet.
> 
> It seems to be a given now that 3G phones will be IPv6 (at least outside 
> the U.S.) when they roll out over the next few years. But we should make 
> people clearly aware of what to expect when they NAT their way back to the 
> IPv4 Internet or IPv4 intranets. That is one of the purposes of this draft. 
> (oh yeah, this thread is supposed to be about contributing to the draft in 
> the subject line)

The reality is that mobile phones are using non-IP protocols.

If you use NAT, you have no reason to use IP.

In Japan, there are more than 5 million non-IP mobile WWW browsers
served by a single application gateway.

							Masataka Ohta



From owner-ietf-outbound  Sun Apr 30 02:51:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA10094
	for ietf-outbound.10@ietf.org; Sun, 30 Apr 2000 02:50:03 -0400 (EDT)
Received: from arcc.or.ke (root@[212.49.87.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10071
	for <ietf@ietf.org>; Sun, 30 Apr 2000 02:46:30 -0400 (EDT)
Received: from 199.2.222.254 ([199.2.222.123])
	by arcc.or.ke (8.9.3/8.9.3) with SMTP id KAA23541
	for <ietf@ietf.org>; Sun, 30 Apr 2000 10:06:32 +0300 (EAT)
Date: Sun, 30 Apr 2000 10:06:32 +0300 (EAT)
Message-Id: <200004300706.KAA23541@arcc.or.ke>
X-Sender: musandu@199.2.222.254
X-Mailer: Windows Eudora Pro Version 2.1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: Musandu <musandu@arcc.or.ke>
Subject: E - commerce limitations?
X-Loop: ietf@ietf.org


I have several questions related to internet commerce and existing internet
commerce systems:
(1)What is the maximum ( highest known ) amount ( in any widely traded
currency ) that can be paid off in a single transaction in existing internet
commerce systems?
(2)What is the greatest upper limit that can be settled by any known credit
/ debit card for a single transaction? and about how many people hold such
cards?
(3)I am looking for information criticising Integrion where can I find it ?

Yours sincerely,
Nyagudi Musandu



From owner-ietf-outbound  Sun Apr 30 06:51:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA01597
	for ietf-outbound.10@ietf.org; Sun, 30 Apr 2000 06:50:02 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET (nod.Reston.mci.net [166.45.6.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01561
	for <ietf@ietf.org>; Sun, 30 Apr 2000 06:43:13 -0400 (EDT)
Received: from cerf.mci.net ([24.163.108.28])
 by shoe.reston.mci.net (PMDF V5.2-32 #40475)
 with ESMTPA id <01JOU5XDI28891VVBQ@shoe.reston.mci.net> for ietf@ietf.org;
 Sun, 30 Apr 2000 06:43:13 EST
Date: Sun, 30 Apr 2000 06:20:48 -0400
From: "vinton g. cerf" <vcerf@MCI.NET>
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-reply-to: <200004300553.OAA06363@necom830.hpcl.titech.ac.jp>
X-Sender: vcerf@shoe.reston.mci.net
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>,
        Matt Holdrege <holdrege@lucent.com>
Cc: Thomas Narten <narten@raleigh.ibm.com>, ietf@ietf.org
Message-id: <4.3.1.2.20000430061634.0117de78@shoe.reston.mci.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <4.3.1.2.20000426100233.00bdcbc0@porky>
Content-Transfer-Encoding: 7BIT
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7BIT

that's right - they use iMODE on the DOCOMO mobiles. iMODE and
WAP seem to have that in common: a non-IP radio link protocol
and an application gateway. Of course, this limits the applications
to those that can be "translated" in the gateway, while an end to
end system (such as the Ricochet from Metricom) would allow 
essentially any application on an Internet server to interact
directly with the mobile device because the gateway would merely
be an IP level device, possibly with NAT functionality.
With a JAVA interpreter or other similar capability in the
mobile, one could imagine considerable competition for development
of new applications. As it stands, only the applications NTT
chooses to implement in the translating gateway are accessible.

Since HTTP is one of the "applications" served, there is still
a lot of room for competition, I suppose.

vint

At 02:53 PM 4/30/2000 +0859, Masataka Ohta wrote:

>In Japan, there are more than 5 million non-IP mobile WWW browsers
>served by a single application gateway.

=================================================================
I moved to a new MCI WorldCom facility on Nov 11, 1999

MCI WorldCom
22001 Loudoun County Parkway
Building F2, Room 4115, ATTN: Vint Cerf
Ashburn, VA 20147
Telephone (703) 886-1690
FAX (703) 886-0047


"INTERNET IS FOR EVERYONE!" 
See you at INET2000, Yokohama, Japan July 18-21, 2000
http://www.isoc.org/inet2000




From owner-ietf-outbound  Sun Apr 30 19:24:02 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA05031
	for ietf-outbound.10@ietf.org; Sun, 30 Apr 2000 19:20:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05005
	for <ietf@ietf.org>; Sun, 30 Apr 2000 19:15:02 -0400 (EDT)
Received: (from hta@localhost)
	by dokka.maxware.no (8.9.3/8.9.3) id BAA27980
	for ietf@ietf.org; Mon, 1 May 2000 01:15:02 +0200
Date: Mon, 1 May 2000 01:15:02 +0200
From: Harald Tveit Alvestrand <hta@dokka.maxware.no>
Message-Id: <200004302315.BAA27980@dokka.maxware.no>
To: ietf@ietf.org
Subject: FAQ: The IETF+Censored list
X-Loop: ietf@ietf.org


                        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@alvestrand.no".
   
   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 Harald Alvestrand, 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"
       
   To join the list, [1]send the word "subscribe" in the BODY of a
   message to ietf+censored-request@alvestrand.no (the URL here is an RFC
   2368 mailto URL that does the Right Thing).
   
   For fun, there is a special list for the rejected messages:
   ietf+censored-rejects@alvestrand.no - subscribe in the same fashion,
   by [2]mail to ietf+censored-rejects-request@alvestrand.no
   
   By public request, the current set of filters are listed at
   [3]http://www.alvestrand.no/cgi-bin/hta/ietf+censored-filters
   
   Some statistics on postings, which may be useful in getting a
   perspective on the effects of the filter, are at
   [4]posting-counts.html (started Oct 14, 1998).
   
   This page is http://www.alvestrand.no/ietf+censored.html, and is
   posted monthly in text form to ietf@ietf.org
     _________________________________________________________________
   
   Harald Tveit Alvestrand [5]< Harald@Alvestrand.no>

References

   1. mailto:ietf+censored-request@alvestrand.no?body=subscribe
   2. mailto:ietf+censored-rejects-request@alvestrand.no?body=subscribe
   3. http://www.alvestrand.no/cgi-bin/hta/ietf+censored-filters
   4. http://www.alvestrand.no/posting-counts.html
   5. mailto:harald@alvestrand.no



