From owner-ietf@ietf.org  Wed Oct  1 04:48:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03444
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 04:48:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4cS4-0000eu-0N
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 04:35:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4cRo-0000dA-Dz
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 04:35:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03123
	for <ietf@ietf.org>; Wed, 1 Oct 2003 04:34:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cRl-00040D-00
	for ietf@ietf.org; Wed, 01 Oct 2003 04:34:58 -0400
Received: from apollo.ext.eurgw.xerox.com ([13.16.138.21] helo=apollo.eurgw.xerox.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cRl-0003zZ-00
	for ietf@ietf.org; Wed, 01 Oct 2003 04:34:57 -0400
Received: from eurodns4.eur.xerox.com (eurodns4.eur.xerox.com [13.202.66.50])
	by apollo.eurgw.xerox.com (8.12.9-20030917/8.12.9) with ESMTP id h918YRkx010845
	for <ietf@ietf.org>; Wed, 1 Oct 2003 09:34:27 +0100 (BST)
Received: from eurdubmg04.eur.xerox.com (eurdubmg04.eur.xerox.com [13.202.66.61])
	by eurodns4.eur.xerox.com (8.12.9/8.12.8) with ESMTP id h918YRAl021699
	for <ietf@ietf.org>; Wed, 1 Oct 2003 09:34:27 +0100 (BST)
Received: from eurgbrbh02.emeacinops.xerox.com (unverified) by eurdubmg04.eur.xerox.com
 (Content Technologies SMTPRS 4.2.10) with ESMTP id <T65036856b30dca423d464@eurdubmg04.eur.xerox.com> for <ietf@ietf.org>;
 Wed, 1 Oct 2003 09:34:26 +0100
Received: from gbrwgcbh01.wgc.gbr.xerox.com ([13.200.2.175]) by eurgbrbh02.emeacinops.xerox.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2654.89)
	id SY6758H9; Wed, 1 Oct 2003 09:34:25 +0100
Received: by gbrwgcbh01.wgc.gbr.xerox.com with Internet Mail Service (5.5.2656.59)
	id <SYSC2R47>; Wed, 1 Oct 2003 09:38:33 +0100
Message-ID: <59697CCC6CE3D411B4CD00805FBB776704F7DDA9@gbrwgcms03.wgc.gbr.xerox.com>
From: "Brookes, Stuart P" <StuartP.Brookes@gbr.xerox.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: InterfaceTable question
Date: Wed, 1 Oct 2003 09:38:32 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C387F7.2DD53448"
Sender: owner-ietf@ietf.org
Precedence: bulk

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_01C387F7.2DD53448
Content-Type: text/plain

All,
 
I am new to SNMP and its workings, thus this may seem a very simple question
with an obvious answer to the majority of you.
 
But, how often, if ever, should the counters in the InterfaceTable be reset?
Are they counters that should never be re-set or should they be re-set when
a device is powered off and powered back on?  Or are they dependant on a
Network Management Tool and how often that is re-initialized?
 
Many Thanks
Stuart

------_=_NextPart_001_01C387F7.2DD53448
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1106" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=139093208-01102003><FONT face=Arial 
size=2>All,</FONT></SPAN></DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial size=2>I am new to SNMP and 
its workings, thus this may seem a very simple question with an obvious answer 
to the majority of you.</FONT></SPAN></DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial size=2>But, how often, if 
ever, should the counters in the InterfaceTable be reset?&nbsp; Are they 
counters that should never be re-set or should they be re-set when a device is 
powered off and powered back on?&nbsp; Or are they dependant on a Network 
Management Tool and how often that is re-initialized?</FONT></SPAN></DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial size=2>Many 
Thanks</FONT></SPAN></DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial 
size=2>Stuart</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C387F7.2DD53448--



From owner-ietf@ietf.org  Wed Oct  1 04:51:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03628
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 04:51:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4cdh-0001C0-0G
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 04:47:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4ccp-00019G-Jy
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 04:46:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03382
	for <ietf@ietf.org>; Wed, 1 Oct 2003 04:46:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ccn-00046U-00
	for ietf@ietf.org; Wed, 01 Oct 2003 04:46:21 -0400
Received: from apollo.ext.eurgw.xerox.com ([13.16.138.21] helo=apollo.eurgw.xerox.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ccm-00046C-00
	for ietf@ietf.org; Wed, 01 Oct 2003 04:46:20 -0400
Received: from eurodns2.eur.xerox.com (eurodns2.eur.xerox.com [13.202.66.10])
	by apollo.eurgw.xerox.com (8.12.9-20030917/8.12.9) with ESMTP id h918jpkx016495
	for <ietf@ietf.org>; Wed, 1 Oct 2003 09:45:51 +0100 (BST)
Received: from eurdubmg01.eur.xerox.com (eurdubmg01.eur.xerox.com [13.202.65.253])
	by eurodns2.eur.xerox.com (8.12.9/8.12.9) with ESMTP id h918jn9v007368
	for <ietf@ietf.org>; Wed, 1 Oct 2003 09:45:49 +0100 (BST)
Received: from eurgbrbh02.emeacinops.xerox.com (unverified) by eurdubmg01.eur.xerox.com
 (Content Technologies SMTPRS 4.2.10) with ESMTP id <T650372b93a0dca41fd51c@eurdubmg01.eur.xerox.com> for <ietf@ietf.org>;
 Wed, 1 Oct 2003 09:45:47 +0100
Received: from gbrwgcbh01.wgc.gbr.xerox.com ([13.200.2.175]) by eurgbrbh02.emeacinops.xerox.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2654.89)
	id SY6759PR; Wed, 1 Oct 2003 09:45:47 +0100
Received: by gbrwgcbh01.wgc.gbr.xerox.com with Internet Mail Service (5.5.2656.59)
	id <SYSC2RZ9>; Wed, 1 Oct 2003 09:49:54 +0100
Message-ID: <59697CCC6CE3D411B4CD00805FBB776704F7DDAC@gbrwgcms03.wgc.gbr.xerox.com>
From: "Brookes, Stuart P" <StuartP.Brookes@gbr.xerox.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: InterfaceTable question
Date: Wed, 1 Oct 2003 09:49:52 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C387F8.FA63F5C0"
Sender: owner-ietf@ietf.org
Precedence: bulk

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_01C387F8.FA63F5C0
Content-Type: text/plain

All,
 
I am new to SNMP and its workings, thus this may seem a very simple question
with an obvious answer to the majority of you.
 
But, how often, if ever, should the counters in the InterfaceTable be reset?
Are they counters that should never be re-set or should they be re-set when
a device is powered off and powered back on?  Or are they dependant on a
Network Management Tool and how often that is re-initialized?
 
Many Thanks
Stuart

------_=_NextPart_001_01C387F8.FA63F5C0
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1106" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=139093208-01102003><FONT face=Arial 
size=2>All,</FONT></SPAN></DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial size=2>I am new to SNMP and 
its workings, thus this may seem a very simple question with an obvious answer 
to the majority of you.</FONT></SPAN></DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial size=2>But, how often, if 
ever, should the counters in the InterfaceTable be reset?&nbsp; Are they 
counters that should never be re-set or should they be re-set when a device is 
powered off and powered back on?&nbsp; Or are they dependant on a Network 
Management Tool and how often that is re-initialized?</FONT></SPAN></DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial size=2>Many 
Thanks</FONT></SPAN></DIV>
<DIV><SPAN class=139093208-01102003><FONT face=Arial 
size=2>Stuart</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C387F8.FA63F5C0--



From owner-ietf@ietf.org  Wed Oct  1 05:05:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04272
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 05:05:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4cqJ-0002ga-2g
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 05:00:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4cps-0002cq-V7
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 04:59:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04068
	for <ietf@ietf.org>; Wed, 1 Oct 2003 04:59:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cpq-0004K1-00
	for ietf@ietf.org; Wed, 01 Oct 2003 04:59:50 -0400
Received: from tiere.net.avaya.com ([198.152.12.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cpq-0004Jy-00
	for ietf@ietf.org; Wed, 01 Oct 2003 04:59:50 -0400
Received: from tiere.net.avaya.com (localhost [127.0.0.1])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id h918xUoT002719
	for <ietf@ietf.org>; Wed, 1 Oct 2003 04:59:30 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id h918xSoT002698
	for <ietf@ietf.org>; Wed, 1 Oct 2003 04:59:28 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C387FA.5DFCEB93"
Subject: RE: InterfaceTable question
Date: Wed, 1 Oct 2003 11:59:48 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F042593F7@is0004avexu1.global.avaya.com>
Thread-Topic: InterfaceTable question
Thread-Index: AcOH+Pr9UUV30HIBQxKlPKKCe+oo3gAAPgzQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Brookes, Stuart P" <StuartP.Brookes@gbr.xerox.com>, <ietf@ietf.org>
Cc: <mibs@ops.ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C387FA.5DFCEB93
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Stuart,
=20
First, this question is more suitable to the MIBs list in the OPS area. =
Avoid copying all the IETF list for such issues in the future.=20
=20
Specifically, I suggest that you look at section 4.6.1.2 for =
recommendations on counters reset.=20
=20
Regards,
=20
Dan
=20

-----Original Message-----
From: Brookes, Stuart P [mailto:StuartP.Brookes@gbr.xerox.com]
Sent: 01 October, 2003 11:39 AM
To: 'ietf@ietf.org'
Subject: InterfaceTable question


All,
=20
I am new to SNMP and its workings, thus this may seem a very simple =
question with an obvious answer to the majority of you.
=20
But, how often, if ever, should the counters in the InterfaceTable be =
reset?  Are they counters that should never be re-set or should they be =
re-set when a device is powered off and powered back on?  Or are they =
dependant on a Network Management Tool and how often that is =
re-initialized?
=20
Many Thanks
Stuart


------_=_NextPart_001_01C387FA.5DFCEB93
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>Message</TITLE>

<META content=3D"MSHTML 5.50.4930.1700" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D318495608-01102003><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM>Stuart,</EM></STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D318495608-01102003><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM></EM></STRONG></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D318495608-01102003><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM>First, this question is more suitable to the MIBs =
list in the=20
OPS area. Avoid copying all the IETF list for such issues in the future. =

</EM></STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Specifically, I suggest that you look at section 4.6.1.2 for=20
recommendations on counters reset. </FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Regards,</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
<DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Brookes, Stuart P=20
  [mailto:StuartP.Brookes@gbr.xerox.com]<BR><B>Sent:</B> 01 October, =
2003 11:39=20
  AM<BR><B>To:</B> 'ietf@ietf.org'<BR><B>Subject:</B> InterfaceTable=20
  question<BR><BR></FONT></DIV>
  <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial=20
  size=3D2>All,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial size=3D2>I am =
new to SNMP=20
  and its workings, thus this may seem a very simple question with an =
obvious=20
  answer to the majority of you.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial size=3D2>But, =
how often, if=20
  ever, should the counters in the InterfaceTable be reset?&nbsp; Are =
they=20
  counters that should never be re-set or should they be re-set when a =
device is=20
  powered off and powered back on?&nbsp; Or are they dependant on a =
Network=20
  Management Tool and how often that is =
re-initialized?</FONT></SPAN></DIV>
  <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial size=3D2>Many =

  Thanks</FONT></SPAN></DIV>
  <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial=20
  size=3D2>Stuart</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C387FA.5DFCEB93--



From owner-ietf@ietf.org  Wed Oct  1 05:08:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04442
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 05:08:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4cv7-0002xy-4d
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 05:05:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4cun-0002t5-3b
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 05:04:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04234
	for <ietf@ietf.org>; Wed, 1 Oct 2003 05:04:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cuk-0004N3-00
	for ietf@ietf.org; Wed, 01 Oct 2003 05:04:54 -0400
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cuk-0004N0-00
	for ietf@ietf.org; Wed, 01 Oct 2003 05:04:54 -0400
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id h91938JK020071
	for <ietf@ietf.org>; Wed, 1 Oct 2003 04:03:08 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id h91935JK020054
	for <ietf@ietf.org>; Wed, 1 Oct 2003 04:03:06 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C387FB.129C1D89"
Subject: RE: InterfaceTable question
Date: Wed, 1 Oct 2003 12:04:51 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F042593F8@is0004avexu1.global.avaya.com>
Thread-Topic: InterfaceTable question
Thread-Index: AcOH+Pr9UUV30HIBQxKlPKKCe+oo3gAAPgzQAABBIVA=
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>,
        "Brookes, Stuart P" <StuartP.Brookes@gbr.xerox.com>, <ietf@ietf.org>
Cc: <mibs@ops.ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C387FB.129C1D89
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I forgot to mention the document - =
http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-=
02.txt.=20

-----Original Message-----
From: Romascanu, Dan (Dan)=20
Sent: 01 October, 2003 12:00 PM
To: Brookes, Stuart P; ietf@ietf.org
Cc: mibs@ops.ietf.org
Subject: RE: InterfaceTable question


Stuart,
=20
First, this question is more suitable to the MIBs list in the OPS area. =
Avoid copying all the IETF list for such issues in the future.=20
=20
Specifically, I suggest that you look at section 4.6.1.2 for =
recommendations on counters reset.=20
=20
Regards,
=20
Dan
=20

-----Original Message-----
From: Brookes, Stuart P [mailto:StuartP.Brookes@gbr.xerox.com]
Sent: 01 October, 2003 11:39 AM
To: 'ietf@ietf.org'
Subject: InterfaceTable question


All,
=20
I am new to SNMP and its workings, thus this may seem a very simple =
question with an obvious answer to the majority of you.
=20
But, how often, if ever, should the counters in the InterfaceTable be =
reset?  Are they counters that should never be re-set or should they be =
re-set when a device is powered off and powered back on?  Or are they =
dependant on a Network Management Tool and how often that is =
re-initialized?
=20
Many Thanks
Stuart


------_=_NextPart_001_01C387FB.129C1D89
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>Message</TITLE>

<META content=3D"MSHTML 5.50.4930.1700" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D407060409-01102003><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM>I forgot to mention the document - <A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-gui=
delines-02.txt">http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-re=
view-guidelines-02.txt</A>.=20
</EM></STRONG></FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Romascanu, Dan =
(Dan)=20
  <BR><B>Sent:</B> 01 October, 2003 12:00 PM<BR><B>To:</B> Brookes, =
Stuart P;=20
  ietf@ietf.org<BR><B>Cc:</B> mibs@ops.ietf.org<BR><B>Subject:</B> RE:=20
  InterfaceTable question<BR><BR></FONT></DIV>
  <DIV><SPAN class=3D318495608-01102003><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2><STRONG><EM>Stuart,</EM></STRONG></FONT></SPAN></DIV>
  <DIV><SPAN class=3D318495608-01102003><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2><STRONG><EM></EM></STRONG></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D318495608-01102003><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2><STRONG><EM>First, this question is more suitable to the MIBs =
list in=20
  the OPS area. Avoid copying all the IETF list for such issues in the =
future.=20
  </EM></STRONG></FONT></SPAN></DIV>
  <DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Specifically, I suggest that you look at section 4.6.1.2 for=20
  recommendations on counters reset. </FONT></EM></STRONG></SPAN></DIV>
  <DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Regards,</FONT></EM></STRONG></SPAN></DIV>
  <DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Dan</FONT></EM></STRONG></SPAN></DIV>
  <DIV><SPAN class=3D318495608-01102003><STRONG><EM><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></EM></STRONG></SPAN>&nbsp;</DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> Brookes, Stuart =
P=20
    [mailto:StuartP.Brookes@gbr.xerox.com]<BR><B>Sent:</B> 01 October, =
2003=20
    11:39 AM<BR><B>To:</B> 'ietf@ietf.org'<BR><B>Subject:</B> =
InterfaceTable=20
    question<BR><BR></FONT></DIV>
    <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial=20
    size=3D2>All,</FONT></SPAN></DIV>
    <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial size=3D2>I =
am new to SNMP=20
    and its workings, thus this may seem a very simple question with an =
obvious=20
    answer to the majority of you.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial =
size=3D2>But, how often,=20
    if ever, should the counters in the InterfaceTable be reset?&nbsp; =
Are they=20
    counters that should never be re-set or should they be re-set when a =
device=20
    is powered off and powered back on?&nbsp; Or are they dependant on a =
Network=20
    Management Tool and how often that is =
re-initialized?</FONT></SPAN></DIV>
    <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial =
size=3D2>Many=20
    Thanks</FONT></SPAN></DIV>
    <DIV><SPAN class=3D139093208-01102003><FONT face=3DArial=20
    =
size=3D2>Stuart</FONT></SPAN></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTM=
L>

------_=_NextPart_001_01C387FB.129C1D89--



From owner-ietf@ietf.org  Wed Oct  1 10:47:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15893
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 10:47:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4i8K-00073X-5y
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 10:39:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4i4d-0006rC-MN
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 10:35:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15497
	for <ietf@ietf.org>; Wed, 1 Oct 2003 10:35:20 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4i4c-0007i0-00
	for ietf@ietf.org; Wed, 01 Oct 2003 10:35:26 -0400
Received: from h80ad24ae.async.vt.edu ([128.173.36.174] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4i4b-0007hw-00
	for ietf@ietf.org; Wed, 01 Oct 2003 10:35:25 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h91ERCcG009814;
	Wed, 1 Oct 2003 10:27:12 -0400
Message-Id: <200310011427.h91ERCcG009814@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Cc: "Brookes, Stuart P" <StuartP.Brookes@gbr.xerox.com>, ietf@ietf.org,
        mibs@ops.ietf.org
Subject: cross-pollination (was Re: InterfaceTable question)
In-Reply-To: Your message of "Wed, 01 Oct 2003 12:04:51 +0300."
             <AAB4B3D3CF0F454F98272CBE187FDE2F042593F8@is0004avexu1.global.avaya.com> 
References: <AAB4B3D3CF0F454F98272CBE187FDE2F042593F8@is0004avexu1.global.avaya.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1485351717P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 01 Oct 2003 10:27:11 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Wed, 01 Oct 2003 12:04:51 +0300, "Romascanu, Dan (Dan)" said:

> http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-02.txt

> Specifically, I suggest that you look at section 4.6.1.2 for
> recommendations on counters reset.

Hopefully, that document isn't in violent disagreement from the answer the
original poster would get if they asked on the NANOG list.  Has OPS/MIB had
better luck in cross-pollinating with the NANOG crew than the IETF as a whole?
It's traditionally  been a weak spot of ours (although there's a few people who
are highly visible in both fora - you guys know who you are, and thanks.. ;)

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

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

iD8DBQE/euQ/cC3lWbTT17ARArRuAJ9xoW1IVcg1rIjslXg/5vOLZZfwJQCgzard
c8gugOPhwsVlJ47ZE9MVWmU=
=MS7t
-----END PGP SIGNATURE-----

--==_Exmh_1485351717P--



From owner-ietf@ietf.org  Wed Oct  1 12:23:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21888
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 12:23:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4jUW-0000DK-RQ
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 12:06:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4jSJ-00005M-Sq
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 12:03:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21007
	for <ietf@ietf.org>; Wed, 1 Oct 2003 12:03:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4jSI-0001RB-00
	for ietf@ietf.org; Wed, 01 Oct 2003 12:03:58 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4jSI-0001R8-00
	for ietf@ietf.org; Wed, 01 Oct 2003 12:03:58 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1A4jSE-00098f-00
	for ietf@ietf.org; Wed, 01 Oct 2003 11:03:54 -0500
Date: Wed, 01 Oct 2003 12:03:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Persistent applications-level identifiers, the DNS, and
 RFC 2428
Message-ID: <155922084.1065009834@scan.jck.com>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi.

I just had occasion to look again at RFC 2428, "FTP Extensions 
for IPv6 and NATs",  M. Allman, S. Ostermann, C. Metz. September 
1998, and to think about in the context of the recent 
flame-war^H^H^H^H^H^H^H^H^H discussions about use of IP 
addresses in applications.   2428 provides additional syntax and 
mechanisms for FTP to deal with IPv6, with some useful 
properties for NATs (useful if you believe in NATs).  It appears 
to provide only for addresses and does not appear to be 
extensible except to the addressing formats of new versions of 
IP.

It seems appropriate to ask whether 2428 should be opened and 
given at least the capability of passing DNS names and maybe 
some syntax that would permit clean extension to future 
identifiers.  In the unlikely event that there is insufficient 
interest or energy to do that work, should it be moved to 
historic or otherwise given a "not recommended" status as 
potentially harmful and inconsistent with the principle that 
applications (especially for IPv6) should be passing names and 
not IP addresses?

Please consider this a fairly narrow question.   I don't want to 
start either the "applications level identifiers" debate or the 
NAT wars again and they aren't necessary to answering the 
question.  On those topics, please, everyone, your points --pro, 
con, or otherwise-- have been made and anyone who is going to be 
convinced has been convinced.  More traffic on those subjects in 
the guise of responding to this question will just convince more 
people that it is impossible to carry out a technical discussion 
on the IETF list.

    john




From owner-ietf@ietf.org  Wed Oct  1 14:52:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28320
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 14:52:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4lra-0008BS-J6
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 14:38:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4lqq-00088k-Sl
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 14:37:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26896
	for <ietf@ietf.org>; Wed, 1 Oct 2003 14:37:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4lqp-0003DF-00
	for ietf@ietf.org; Wed, 01 Oct 2003 14:37:27 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4lqp-0003DC-00
	for ietf@ietf.org; Wed, 01 Oct 2003 14:37:27 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 086161413A; Wed,  1 Oct 2003 14:37:27 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 23794-03; Wed,  1 Oct 2003 14:37:26 -0400 (EDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 2525614106; Wed,  1 Oct 2003 14:37:26 -0400 (EDT)
Date: Wed, 1 Oct 2003 14:35:41 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <john-ietf@jck.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Persistent applications-level identifiers, the DNS, and RFC
 2428
Message-Id: <20031001143541.1d0a95a8.moore@cs.utk.edu>
In-Reply-To: <155922084.1065009834@scan.jck.com>
References: <155922084.1065009834@scan.jck.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

The extensions in 2428 are in wide use, and they work just fine.  I
don't see any reason to change them.  

Nor do I believe there is consensus that applications should always be
passing names in preference to IP addresses.  And until there is a
system for assigning stable names to hosts that are independent of
any administrative domain (since hosts often don't live in a single
administrative domain), and quickly and reliably mapping from those
names to IP addresses, the idea that applications should pass names in
preference to IP address is something that I would classify "fantasy" 
at best.  In particular, DNS is not sufficient to replace IP addresses
in this role.

see also 
http://www.cs.utk.edu/~moore/opinions/ipv6/dns-as-endpoint-id.html

Keith

> I just had occasion to look again at RFC 2428, "FTP Extensions 
> for IPv6 and NATs",  M. Allman, S. Ostermann, C. Metz. September 
> 1998, and to think about in the context of the recent 
> flame-war^H^H^H^H^H^H^H^H^H discussions about use of IP 
> addresses in applications.   2428 provides additional syntax and 
> mechanisms for FTP to deal with IPv6, with some useful 
> properties for NATs (useful if you believe in NATs).  It appears 
> to provide only for addresses and does not appear to be 
> extensible except to the addressing formats of new versions of 
> IP.
> 
> It seems appropriate to ask whether 2428 should be opened and 
> given at least the capability of passing DNS names and maybe 
> some syntax that would permit clean extension to future 
> identifiers.  In the unlikely event that there is insufficient 
> interest or energy to do that work, should it be moved to 
> historic or otherwise given a "not recommended" status as 
> potentially harmful and inconsistent with the principle that 
> applications (especially for IPv6) should be passing names and 
> not IP addresses?
> 
> Please consider this a fairly narrow question.   I don't want to 
> start either the "applications level identifiers" debate or the 
> NAT wars again and they aren't necessary to answering the 
> question.  On those topics, please, everyone, your points --pro, 
> con, or otherwise-- have been made and anyone who is going to be 
> convinced has been convinced.  More traffic on those subjects in 
> the guise of responding to this question will just convince more 
> people that it is impossible to carry out a technical discussion 
> on the IETF list.
> 



From owner-ietf@ietf.org  Wed Oct  1 16:05:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02100
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 16:05:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4n55-0000JP-Q2
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 15:56:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4n4i-0000GB-OV
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 15:55:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01829
	for <ietf@ietf.org>; Wed, 1 Oct 2003 15:55:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4n4h-0004QP-00
	for ietf@ietf.org; Wed, 01 Oct 2003 15:55:51 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4n4g-0004QM-00
	for ietf@ietf.org; Wed, 01 Oct 2003 15:55:51 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1A4n4d-000Axq-00; Wed, 01 Oct 2003 14:55:47 -0500
Date: Wed, 01 Oct 2003 15:55:47 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@cs.utk.edu>
cc: ietf@ietf.org
Subject: Re: Persistent applications-level identifiers, the DNS,
 and RFC 2428
Message-ID: <169834569.1065023747@scan.jck.com>
In-Reply-To: <20031001143541.1d0a95a8.moore@cs.utk.edu>
References: <155922084.1065009834@scan.jck.com>
 <20031001143541.1d0a95a8.moore@cs.utk.edu>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Wednesday, 01 October, 2003 14:35 -0400 Keith Moore 
<moore@cs.utk.edu> wrote:

> John,
>
> The extensions in 2428 are in wide use, and they work just
> fine.  I don't see any reason to change them.
>
> Nor do I believe there is consensus that applications should
> always be passing names in preference to IP addresses.  And
> until there is a system for assigning stable names to hosts
> that are independent of any administrative domain (since hosts
> often don't live in a single administrative domain), and
> quickly and reliably mapping from those names to IP addresses,
> the idea that applications should pass names in preference to
> IP address is something that I would classify "fantasy"  at
> best.  In particular, DNS is not sufficient to replace IP
> addresses in this role.
>
> see also
> http://www.cs.utk.edu/~moore/opinions/ipv6/dns-as-endpoint-id.
> html

Keith, you are starting down the path I was hoping to avoid, so 
maybe my specific concern and suggestion wasn't clear.  If is is 
working well as is, then I withdraw even the hint of deprecating 
the thing.    My main objection to 2428 is not that it _permits_ 
addresses, but that it provides no option other than addresses 
and nothing on which to hang a DNS name or other identifier if 
one has one.  That, it seems to me, is poor protocol design 
going forward, since it implies that the next new identifier 
requires yet another set of command keywords.

I suggest that it is useful, indeed important, to have a way to 
express and use DNS names --and, potentially, other 
identifiers-- as an alternative to addresses, if only because 
they isolate the near-user interface of the applications 
protocol from having to know which transport is to be used. 
Unlike a number of other situations in which I would agree with 
you, neither the "stable name" issue nor the independence of 
administrative domain one are significant here -- we routinely 
set up FTP command connections using DNS names, there are likely 
to be many circumstances in which it would be equally 
appropriate to set up the data connection that way, and FTP data 
connections don't persist (significantly) longer than the 
command connection.

We can debate --and work out-- the applicability statement that 
explains when one model or the other should be used.  But the 
protocol should, at least, support the alterative of passing a 
name.

regards,
     john

>> I just had occasion to look again at RFC 2428, "FTP
>> Extensions  for IPv6 and NATs",  M. Allman, S. Ostermann, C.
>> Metz. September  1998, and to think about in the context of
>> the recent  flame-war^H^H^H^H^H^H^H^H^H discussions about use
>> of IP  addresses in applications.   2428 provides additional
>> syntax and  mechanisms for FTP to deal with IPv6, with some
>> useful  properties for NATs (useful if you believe in NATs).
>> It appears  to provide only for addresses and does not appear
>> to be  extensible except to the addressing formats of new
>> versions of  IP.
>>
>> It seems appropriate to ask whether 2428 should be opened and
>> given at least the capability of passing DNS names and maybe
>> some syntax that would permit clean extension to future
>> identifiers.  In the unlikely event that there is
>> insufficient  interest or energy to do that work, should it
>> be moved to  historic or otherwise given a "not recommended"
>> status as  potentially harmful and inconsistent with the
>> principle that  applications (especially for IPv6) should be
>> passing names and  not IP addresses?
>>
>> Please consider this a fairly narrow question.   I don't want
>> to  start either the "applications level identifiers" debate
>> or the  NAT wars again and they aren't necessary to answering
>> the  question.  On those topics, please, everyone, your
>> points --pro,  con, or otherwise-- have been made and anyone
>> who is going to be  convinced has been convinced.  More
>> traffic on those subjects in  the guise of responding to this
>> question will just convince more  people that it is
>> impossible to carry out a technical discussion  on the IETF
>> list.
>>







From owner-ietf@ietf.org  Wed Oct  1 16:36:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03268
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 16:36:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4ncz-0002h3-Ax
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 16:31:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4ncM-0002dn-Bj
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 16:30:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03017
	for <ietf@ietf.org>; Wed, 1 Oct 2003 16:30:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ncK-0004pN-00
	for ietf@ietf.org; Wed, 01 Oct 2003 16:30:37 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ncK-0004pF-00
	for ietf@ietf.org; Wed, 01 Oct 2003 16:30:36 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 82E3014146; Wed,  1 Oct 2003 16:30:36 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 06641-12; Wed,  1 Oct 2003 16:30:35 -0400 (EDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 85724140CC; Wed,  1 Oct 2003 16:30:35 -0400 (EDT)
Date: Wed, 1 Oct 2003 16:28:50 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <john-ietf@jck.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Persistent applications-level identifiers, the DNS, and RFC
 2428
Message-Id: <20031001162850.704373ee.moore@cs.utk.edu>
In-Reply-To: <169834569.1065023747@scan.jck.com>
References: <155922084.1065009834@scan.jck.com>
	<20031001143541.1d0a95a8.moore@cs.utk.edu>
	<169834569.1065023747@scan.jck.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> Keith, you are starting down the path I was hoping to avoid, so 
> maybe my specific concern and suggestion wasn't clear.  If is is 
> working well as is, then I withdraw even the hint of deprecating 
> the thing.    My main objection to 2428 is not that it _permits_ 
> addresses, but that it provides no option other than addresses 
> and nothing on which to hang a DNS name or other identifier if 
> one has one.  That, it seems to me, is poor protocol design 
> going forward, since it implies that the next new identifier 
> requires yet another set of command keywords.

I disagree.  A host, at least one on the public Internet
(where IP addresses are globally unique as IP was designed to work) has
reliable knowledge of its current IP addresses.  It does not have
reliable knowledge of which DNS names are currently bound to its IP
addresses, nor of the intended purposes of those DNS names  (are the
names intended to be associated with a particular host or with a
particular service that is supplied by many hosts?).  

So expecting, or even allowing, an FTP client or server to say 
"contact me at this DNS name" seems to me to be providing additional 
ways for the FTP session to fail, while adding little (if any) value.
e.g. 

- the party providing the DNS name may be doing so erroneously,

- the DNS servers providing name-to-address translation might not
  be in service and reachable,

- DNS lookup might not be available to one party or another
  (e.g. one party is on a ad hoc network and wants to use LLMNR,
  while the other party is on a connected network and expects
  DNS to work)

- if there is an intermediary involved, use of the DNS name may 
  confuse the intermediary or one or the endpoints.  for instance, 
  it is often possible to use FTP between hosts in different
  addressing realms via use of an intermediary, while DNS names
  would fail in those situations.

I'll also note that RFC 2428 already provides a way (EPSV) to  establish
FTP transfers in the usual case where the file is being transferred
between client and server and no third party is involved, which doesn't
need *any* kind of name - neither IP address nor DNS name - as the
endpoint addresses are implicit.  This should be used in the vast
majority of cases.

More fundamentally, of course, I have issues with the citing of
"applications should use names rather than addresses" as a principle to
which there is widespread agreement, and which should drive protocol 
designs, or even as something which has been demonstrated to be
workable.   We don't need to revisit that discussion again right now, or
in this context, but neither should it be taken as a given.  (Nor does
this really have anything to do with NAT - the two are only tangentially
related.)

If we're only looking at the narrow question of FTP, I submit that EPSV
is good enough for the vast majority  of cases, EPRT with either v4 or
v6 addresses is good enough for 3-party transfers (assuming that you can
manage the security issues), and any marginal value that would be
provided by adding DNS capability is fairly dubious at best and
potentially harmful.



From owner-ietf@ietf.org  Wed Oct  1 17:59:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06484
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 17:59:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4oqQ-0007i1-TH
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 17:49:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4oqL-0007ea-Sw
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 17:49:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06092
	for <ietf@ietf.org>; Wed, 1 Oct 2003 17:49:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4oqK-0005xh-00
	for ietf@ietf.org; Wed, 01 Oct 2003 17:49:08 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4oqH-0005wx-00
	for ietf@ietf.org; Wed, 01 Oct 2003 17:49:05 -0400
Content-class: urn:content-classes:message
Subject: RE: Persistent applications-level identifiers, the DNS, and RFC 2428
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Oct 2003 14:48:29 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C5CF@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Persistent applications-level identifiers, the DNS, and RFC 2428
Thread-Index: AcOIOeg6499vGEqGQ/m3T2vZP56fbwAKirJA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "John C Klensin" <john-ietf@jck.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

John,

> John C Klensin wrote:
> It seems appropriate to ask whether 2428 should be opened
> and given at least the capability of passing DNS names
> and maybe some syntax that would permit clean extension
> to future identifiers.

It seems to me that this does not buy us much if it is limited to FTP.
Do you have in mind generalizing the mechanism of passing names instead
of addresses to other apps, and at which layer would the address-to-name
mapping occur?

If I understood you correctly:

The way it works today is:
- You pass a name to the app.
- The app looks up the name and maps an address to it.
- The app opens a TCP connection to the address.

Is what you are proposing:
- You pass a name to the app.
- The app opens a TCP connection to the name.
- The TCP layer manages the mapping.

-or-

- You pass a name to the app.
- The app opens a connects the session layer by name.
- The session layer maps an address to the name and opens a TCP
connection to the address.

-or-

Something else?

Michel.




From owner-ietf@ietf.org  Wed Oct  1 20:33:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12013
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 20:33:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4rHL-0006Er-Tr
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 20:25:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4rGf-0006Bp-GS
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 20:24:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11740
	for <ietf@ietf.org>; Wed, 1 Oct 2003 20:24:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4rGd-0007Ue-00
	for ietf@ietf.org; Wed, 01 Oct 2003 20:24:27 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4rGd-0007Ub-00
	for ietf@ietf.org; Wed, 01 Oct 2003 20:24:27 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1A4rGY-000DCv-00; Wed, 01 Oct 2003 19:24:22 -0500
Date: Wed, 01 Oct 2003 20:24:22 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michel Py <michel@arneill-py.sacramento.ca.us>, ietf@ietf.org
Subject: RE: Persistent applications-level identifiers, the DNS,
 and RFC 2428
Message-ID: <185949300.1065039862@scan.jck.com>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C5CF@server2003.arneill-py.sacramento.ca.us>
References:  <DD7FE473A8C3C245ADA2A2FE1709D90B06C5CF@server2003.ar
 neill-py.sacramento.ca.us>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Wednesday, 01 October, 2003 14:48 -0700 Michel Py 
<michel@arneill-py.sacramento.ca.us> wrote:

> John,
>
>> John C Klensin wrote:
>> It seems appropriate to ask whether 2428 should be opened
>> and given at least the capability of passing DNS names
>> and maybe some syntax that would permit clean extension
>> to future identifiers.
>
> It seems to me that this does not buy us much if it is limited
> to FTP. Do you have in mind generalizing the mechanism of
> passing names instead of addresses to other apps, and at which
> layer would the address-to-name mapping occur?

My ambitious in raising these questions are _very_ limited and, 
in particular, I don't see this as a back door to solving the 
non-DNS, topology-independent, persistent identifier problem. 
(It seems to me that needs to be solved through the front door, 
or not at all.).

Remember that FTP is a bit special -- it is the only major 
(widely deployed and used) application protocol we have that 
uses two TCP connections, one for a dialogue about what is to be 
done and one to actually move data.  That means it must have 
mechanisms for one or the other machine to tell the other one 
"set up a data channel to port X on machine Y"

We've also had a few IESG statements from time to time that have 
provide guidance/instructions to applications writers to get the 
explicit addresses out of the apps whenever possible.  As Keith 
notes, there is controversy as to whether that goal is 
realistic, at least given present our tools and identifier 
collection.

But, given those IESG statements, the character of  "set up a 
data channel to port X on machine Y", and some of the edge cases 
for which it has been used, it would seem at least superficially 
sensible to be able to specify Y as a DNS name or other 
identifier or, as was pointed out to me in a private note, to be 
able to specify the X and Y combination with a URI of some sort. 
I've got no particular interest in prohibiting the use of an IP 
address in Y (others can fight that war, I hope somewhere far 
away, if they want to), only some interest in exploring whether 
it is rational to have capability for a name as an additional 
option.  I do, architecturally and aesthetically, have an 
interest in not having to introduce a new pair of FTP command 
verbs each time someone figures out a different way to talk 
about (or identify) a host.  And that interest is why I got 
concerned when I noticed that 2428 had no provision for a name, 
or expansion of the syntax to accept a name, DNS or otherwise.

> If I understood you correctly:
>
> The way it works today is:
> - You pass a name to the app.
> - The app looks up the name and maps an address to it.
> - The app opens a TCP connection to the address.

yes.

> Is what you are proposing:
> - You pass a name to the app.
> - The app opens a TCP connection to the name.
> - The TCP layer manages the mapping.
>
> -or-
>
> - You pass a name to the app.
> - The app opens a connects the session layer by name.
> - The session layer maps an address to the name and opens a TCP
> connection to the address.

Both of those alternatives go down the "Stable, non-DNS, 
identifier" that Keith and others are concerned about.   For the 
purpose of this discussion/ question, I'm not -- I am purely 
worried about how to handle this unusual situation with FTP. 
Coming back to your first scenario, we have

- You pass a name to the app.
- The app looks up the name and maps an address to it.
- The app opens a TCP connection to the address, establishing 
the command channel
- Either the app or the host at the remote end of the connection 
obtains a name or address, somehow.  In the most common case, it 
will be its own target, so it makes sense for it to obtain its 
own address (or the address of the adapter from which the TCP 
connection was opened), but there are some other cases.
- It passes that address or name to the remote host, along with 
a port number.
- If it passes a name, the remote host looks up the name, maps 
an address to it, and opens a TCP connection to it, establishing 
the data channel.

   john





From owner-ietf@ietf.org  Wed Oct  1 21:14:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13078
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 21:14:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4ryt-0000mq-CV
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 21:10:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4ryq-0000jf-Q0
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 21:10:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12949
	for <ietf@ietf.org>; Wed, 1 Oct 2003 21:10:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ryp-00005d-00
	for ietf@ietf.org; Wed, 01 Oct 2003 21:10:07 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ryo-00005a-00
	for ietf@ietf.org; Wed, 01 Oct 2003 21:10:06 -0400
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200310020055.JAA03982@necom830.hpcl.titech.ac.jp>
Received: from mohta@localhost by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id JAA03982; Thu, 2 Oct 2003 09:55:06 +0900
Subject: Re: Persistent applications-level identifiers, the DNS, and RFC 2428
In-Reply-To: <155922084.1065009834@scan.jck.com> from John C Klensin at "Oct
 1, 2003 12:03:54 pm"
To: John C Klensin <john-ietf@jck.com>
Date: Thu, 2 Oct 2003 09:55:05 +0859 ()
CC: ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-ietf@ietf.org
Precedence: bulk

John;

> I just had occasion to look again at RFC 2428, "FTP Extensions 
> for IPv6 and NATs",

> Please consider this a fairly narrow question.

I'm afraid that your question is still too broad.

Are you asking the question for IPv6 or for NATs?

							Masataka Ohta



From owner-ietf@ietf.org  Wed Oct  1 21:14:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13113
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 21:14:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4s0p-0000vH-Kx
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 21:12:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4rza-0000mv-LS
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 21:10:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12953
	for <ietf@ietf.org>; Wed, 1 Oct 2003 21:10:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4rzY-00005m-00
	for ietf@ietf.org; Wed, 01 Oct 2003 21:10:52 -0400
Received: from 82-35-75-59.cable.ubr02.dals.blueyonder.co.uk ([82.35.75.59] helo=DarkLord.Sabahattin-Gucukoglu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4rzY-00005h-00
	for ietf@ietf.org; Wed, 01 Oct 2003 21:10:52 -0400
Received: from Spooler by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v3.32) ID MO00038A;
    2 Oct 03 02:09:46 +0100
Received: from spooler by sabahattin-gucukoglu.com (Mercury/32 v3.32); 2 Oct 03 02:09:44 +0100
Received: from aurora (192.168.1.3) by DarkLord.Sabahattin-Gucukoglu.com (Mercury/32 v3.32) with ESMTP ID MG000389;
   2 Oct 03 02:09:43 +0100
From: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
Organization: I need more of this!
To: ietf@ietf.org
Date: Thu, 02 Oct 2003 02:08:22 +0100
MIME-Version: 1.0
Subject: Trouble Interpreting RFC 2142
Message-ID: <3F7B8896.9192.1243B105@localhost>
X-PM-Encryptor: QDPGP, 4
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

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

Hi all,

I'm sure this has been raised before, and have done my fair share of 
searching - I think - on the matter.  Trouble is, I can't seem to 
interpret RFC 2142 properly and reach a firm conclusion.  I've seen 
variations on the interpretation of Suggestion Vs Compulsion for a while 
now, and no apparent clarification.  Perhaps the author's view would be 
particularly helpful.  The availability of the "Abuse" mailbox is the 
subject of exceptional debate.

Part of the abstract runs thus:

"Additional mailbox names and aliases are not prohibited, but 
organizations which support email exchanges with the Internet are 
encouraged to support AT LEAST each mailbox name for  
which the associated function exists within the organization."

Great.  So, while I'm not prevented from inventing fab new mailboxes for 
the same or even more services, business roles, etc., I'm at least 
tentatively asked to support the listed mailboxes for services I run, with 
the implicitly understood exception that all services for which mailboxes 
are mandated in their respective standards must be available regardless.  
Right?

Then, part of the Rationale says:

"However, if a given service is offerred, then the associated mailbox 
name(es) must be supported, resulting in delivery to a recipient 
appropriate for the referenced service or   
role."

Okay, I'm confused at this point.  I must support at least the addresses 
for services running at my domain, in contradiction to the mere 
encouragement we were getting earlier.  This statement alone is not a 
suggestion, as seems to be commonly believed (see policy at http://www.rfc-
ignorant.org/ 's Abuse list, for instance), and while no mention is made 
of a definition for "Must" or any further RFC in which the definition may 
be sought (and for which probable reason the word is therefore not in 
capital letters in the text of the RFC, as is often found in RFCs making 
such references), there seems to be a strong assumption that this 
resembles, quite understandably, a compulsion to support the minimal set 
of mailboxes, regardless (again, understood implicitly) of the definition 
of the protocol by its respective standard.

So, please, can someone help me figure this out?  To me, this is very, 
very shaky, and I wouldn't be willing to take sides without a better grasp 
on the situation and knowledge of the author's intentions in both pieces 
of the text.  Perhaps an updating RFC might help the situation, especially 
in light of today's mail usage and needs (for example, heavily of the 
aforementioned "Abuse" mailbox)?  Is some of my own understanding 
incorrect with regards to RFC precedence?

Cheers,
Sabahattin

- -- 

Thought for the day:
    Communist (n): one who has given up all hope
    of becoming a Capitalist.

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

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


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

iQA/AwUBP3t6hiNEOmEWtR2TEQJOmwCePqmbCCbPm14c2sqcwg4JgcWJBqkAoLAP
O+/Xc/L1otFdCpUjEdM4KVqj
=rwyS
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Wed Oct  1 21:46:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13951
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 21:46:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4sQx-00039k-HY
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 21:39:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4sQJ-00036Y-3e
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 21:38:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13823
	for <ietf@ietf.org>; Wed, 1 Oct 2003 21:38:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4sQH-0000QZ-00
	for ietf@ietf.org; Wed, 01 Oct 2003 21:38:29 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4sQG-0000QW-00
	for ietf@ietf.org; Wed, 01 Oct 2003 21:38:28 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1A4sQG-000Djm-00; Wed, 01 Oct 2003 20:38:28 -0500
Date: Wed, 01 Oct 2003 21:38:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
cc: ietf@ietf.org
Subject: Re: Persistent applications-level identifiers, the DNS,
 and RFC 2428
Message-ID: <190395764.1065044308@scan.jck.com>
In-Reply-To: <200310020055.JAA03982@necom830.hpcl.titech.ac.jp>
References:  <200310020055.JAA03982@necom830.hpcl.titech.ac.jp>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Thursday, 02 October, 2003 09:55 +0859 Masataka Ohta 
<mohta@necom830.hpcl.titech.ac.jp> wrote:

> John;
>
>> I just had occasion to look again at RFC 2428, "FTP
>> Extensions  for IPv6 and NATs",
>
>> Please consider this a fairly narrow question.
>
> I'm afraid that your question is still too broad.
>
> Are you asking the question for IPv6 or for NATs?

I am asking the question about FTP, about a piece of syntax in 
the protocol, and about the options that syntax permits.  If the 
addresses and address references that syntax nor permits are 
suitable for a particular situation, then one should use them. 
I am asking only about why we haven't structured that syntax so 
that use of a DNS name --or some other sort of name if/when it 
can be defined-- is possible if it turns out to be appropriate.

     john




From owner-ietf@ietf.org  Wed Oct  1 22:11:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14675
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 22:11:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4ssh-0004pU-M0
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 22:07:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4srf-0004mP-Vw
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 22:06:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14549
	for <ietf@ietf.org>; Wed, 1 Oct 2003 22:06:41 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4sre-0000iH-00
	for ietf@ietf.org; Wed, 01 Oct 2003 22:06:46 -0400
Received: from h80ad2560.async.vt.edu ([128.173.37.96] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4src-0000i9-00
	for ietf@ietf.org; Wed, 01 Oct 2003 22:06:45 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9226eqd006598;
	Wed, 1 Oct 2003 22:06:40 -0400
Message-Id: <200310020206.h9226eqd006598@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
Cc: ietf@ietf.org
Subject: Re: Trouble Interpreting RFC 2142 
In-Reply-To: Your message of "Thu, 02 Oct 2003 02:08:22 BST."
             <3F7B8896.9192.1243B105@localhost> 
References: <3F7B8896.9192.1243B105@localhost>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1482159518P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 01 Oct 2003 22:06:38 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1482159518P
Content-Type: text/plain; charset=us-ascii

On Thu, 02 Oct 2003 02:08:22 BST, Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>  said:

> Great.  So, while I'm not prevented from inventing fab new mailboxes for 
> the same or even more services, business roles, etc., I'm at least 
> tentatively asked to support the listed mailboxes for services I run, with 
> the implicitly understood exception that all services for which mailboxes 
> are mandated in their respective standards must be available regardless.  
> Right?

Right.  You need Postmaster, and then section 3 says that you should have
INFO, MARKETING, SALES, and SUPPORT if appropriate.  Somehow, I
don't see my domain not having a SALES mailbox as being a grave offense. ;)

> 
> Then, part of the Rationale says:
> 
> "However, if a given service is offerred, then the associated mailbox 
> name(es) must be supported, resulting in delivery to a recipient 
> appropriate for the referenced service or   
> role."
> 
> Okay, I'm confused at this point.  I must support at least the addresses 
> for services running at my domain, in contradiction to the mere 
> encouragement we were getting earlier.

You need the appropriate ones from section 3.  Then you need to have
ABUSE, NOC, and SECURITY from section 4.  Then for each service
in 5, you need the mailbox *if* you run that service.  You need
Postmaster.  If you do your own DNS, you need Hostmaster.
If you have a webserver, you need Webmaster, and so on.  If you
don't have an FTP server, you don't need an FTP mailbox.

I read it as saying "We suggest you have aliases from section 3 for
appropriate business units, and the service-oriented ones from section
5 are mandatory if you run that service".  So if you have a sales
division, a mailbox called 'sales' is suggested, but if you have a
webserver, you *have* to have a 'webmaster' mailbox.

--==_Exmh_-1482159518P
Content-Type: application/pgp-signature

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

iD8DBQE/e4gtcC3lWbTT17ARAureAKCs9K0KsagxePK6FCh6PF2WZElG/QCdEN8D
ZKuvxvTy+5WOp2R0Xm7g5bo=
=AAmI
-----END PGP SIGNATURE-----

--==_Exmh_-1482159518P--



From owner-ietf@ietf.org  Wed Oct  1 23:37:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17090
	for <ietf-web-archive@odin.ietf.org>; Wed, 1 Oct 2003 23:37:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4uAM-0001bl-7Y
	for ietf-list@asgard.ietf.org; Wed, 01 Oct 2003 23:30:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4u9c-0001Yl-J1
	for ietf@asgard.ietf.org; Wed, 01 Oct 2003 23:29:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16927
	for <ietf@ietf.org>; Wed, 1 Oct 2003 23:29:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4u9a-0001eJ-00
	for ietf@ietf.org; Wed, 01 Oct 2003 23:29:22 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4u9Z-0001eF-00
	for ietf@ietf.org; Wed, 01 Oct 2003 23:29:21 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id h923TBWH023243
	for ietf@ietf.org env-from <vjs>;
	Wed, 1 Oct 2003 21:29:11 -0600 (MDT)
Date: Wed, 1 Oct 2003 21:29:11 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200310020329.h923TBWH023243@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Trouble Interpreting RFC 2142
References: <200310020206.h9226eqd006598@turing-police.cc.vt.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Valdis.Kletnieks@vt.edu

> ...
> I read it as saying "We suggest you have aliases from section 3 for
> appropriate business units, and the service-oriented ones from section
> 5 are mandatory if you run that service".  So if you have a sales
> division, a mailbox called 'sales' is suggested, but if you have a
> webserver, you *have* to have a 'webmaster' mailbox.

I notice that you don't say you "MUST" have a webmaster mailbox,
which is good for more than one reason.  One is that "MUST" appears
only once in section 6 concern mailing lists.  Another is that today
webmaster@domain.com essentially never receives anything but spam.

Contrary to some who advocate rejecting mail from sites that don't do
what they call complying with RFC 2142, I read it as saying:

  If you're going to offer these services, then you probably want
  to receive comments about them.  If you do want to receive
  comments, then you'd better use these mailboxes, because that's
  where people will send their important notes about your services
  as well as offers about mortgage loans and other vital issues.

The purpose of every RFC is to improve interoperability.  The familiar
claims that not having an abuse mailbox justifies breaking SMTP
compatibility purely on grounds of Violation of Standards (Horrors!)
make sense only to people who don't read or care about those standards.
The First RFC Standard is "Be Conservative in what you send and generous
in what you accept," which implies that breaking compatibility on
legalistic grounds is always worse.

It makes sense to reject mail because of an observed a correlation
between spam and odd IP addresses, domains without about abuse
mailboxes, or anything else.  Security trumps interoperability.
If you press supporters of rfc-ignorant.org, they'll claim something
like that as justification.  However rfc-ignorant.org also lists
spamhaus.org.  Mr. Balling admits there has never been and never
will be spam from spamhaus.org and falls back on something incoherent
about a violation of RFC 2142.  Because of its name and because of
expressions of displeasure from spammers about the SBL, spamhaus.org
gets far too much junk at the standard mailboxes to do other than
have auto-responders that describe real contact methods.

You should do whatever you think is right while ignoring the sidewalk
superintendents, poseurs, would be famous spam fighters, kooks, trolls,
spammers, and other parasites.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Thu Oct  2 00:19:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18395
	for <ietf-web-archive@odin.ietf.org>; Thu, 2 Oct 2003 00:19:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4uqx-0004Nk-2O
	for ietf-list@asgard.ietf.org; Thu, 02 Oct 2003 00:14:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4uqE-0004Kd-HQ
	for ietf@asgard.ietf.org; Thu, 02 Oct 2003 00:13:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18238
	for <ietf@ietf.org>; Thu, 2 Oct 2003 00:13:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4uqC-000257-00
	for ietf@ietf.org; Thu, 02 Oct 2003 00:13:24 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4uqB-00024d-00
	for ietf@ietf.org; Thu, 02 Oct 2003 00:13:23 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h924IIf14075;
	Wed, 1 Oct 2003 21:18:18 -0700
Date: Wed, 1 Oct 2003 21:12:46 -0700
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v2.00.22)
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <192101725343.20031001211246@brandenburg.com>
To: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
CC: ietf@ietf.org
Subject: Re: Trouble Interpreting RFC 2142
In-Reply-To: <3F7B8896.9192.1243B105@localhost>
References: <3F7B8896.9192.1243B105@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sabahattin,

SG> Part of the abstract runs thus:
...
SG> encouraged to support AT LEAST each mailbox name for
...
SG> Then, part of the Rationale says:
SG> "However, if a given service is offerred, then the associated mailbox
SG> name(es) must be supported, resulting in delivery to a recipient 
SG> appropriate for the referenced service or   
SG> role."

SG> Okay, I'm confused at this point.  I must support at least the addresses 
SG> for services running at my domain, in contradiction to the mere 
SG> encouragement we were getting earlier.


Abstracts are not usually taken to be normative.  Certainly, this one is not
normative.

The Rationale and Scope section is intended to be a normative specification
for the generic aspects of the document.  That is, it says how the document
should be applied.

Like any standards document, the degree of actual force it carries is only as
strong as the community decides to impart to it.


d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Thu Oct  2 02:58:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05223
	for <ietf-web-archive@odin.ietf.org>; Thu, 2 Oct 2003 02:58:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A4xHt-00036N-6A
	for ietf-list@asgard.ietf.org; Thu, 02 Oct 2003 02:50:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A4xHq-00033F-1h
	for ietf@asgard.ietf.org; Thu, 02 Oct 2003 02:50:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05005
	for <ietf@ietf.org>; Thu, 2 Oct 2003 02:49:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xHn-0003k8-00
	for ietf@ietf.org; Thu, 02 Oct 2003 02:50:03 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xHm-0003k5-00
	for ietf@ietf.org; Thu, 02 Oct 2003 02:50:03 -0400
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200310020637.PAA05272@necom830.hpcl.titech.ac.jp>
Received: from mohta@localhost by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id PAA05272; Thu, 2 Oct 2003 15:37:03 +0900
Subject: Re: Persistent applications-level identifiers, the DNS, and RFC 2428
In-Reply-To: <190395764.1065044308@scan.jck.com> from John C Klensin at "Oct
 1, 2003 09:38:28 pm"
To: John C Klensin <john-ietf@jck.com>
Date: Thu, 2 Oct 2003 15:37:02 +0859 ()
CC: ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Sender: owner-ietf@ietf.org
Precedence: bulk

John;

> >> I just had occasion to look again at RFC 2428, "FTP
> >> Extensions  for IPv6 and NATs",
> >
> >> Please consider this a fairly narrow question.
> >
> > I'm afraid that your question is still too broad.
> >
> > Are you asking the question for IPv6 or for NATs?
> 
> I am asking the question about FTP, about a piece of syntax in 
> the protocol, and about the options that syntax permits.

For what purpose?

> I am asking only about why we haven't structured that syntax

Seemingly because there was no reason to have one.

If you think you now have a reason, you should state it.

If you don't, we can debate forever on infinite variations of
reasons and associated extensions.

For example, how about extending FTP to be able to treat 
realtime stream? It is a question about FTP, about a piece
of syntax (MODE/STRU commands) in the protocol, and about
the options that syntax permits.

							Masataka Ohta



From owner-ietf@ietf.org  Thu Oct  2 13:50:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16141
	for <ietf-web-archive@odin.ietf.org>; Thu, 2 Oct 2003 13:50:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A57J7-0004N1-RJ
	for ietf-list@asgard.ietf.org; Thu, 02 Oct 2003 13:32:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A57J1-0004Jp-Uo
	for ietf@asgard.ietf.org; Thu, 02 Oct 2003 13:31:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15022
	for <ietf@ietf.org>; Thu, 2 Oct 2003 13:31:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57J0-0003ro-00
	for ietf@ietf.org; Thu, 02 Oct 2003 13:31:58 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57Iz-0003rj-00
	for ietf@ietf.org; Thu, 02 Oct 2003 13:31:57 -0400
Content-class: urn:content-classes:message
Subject: RE: Persistent applications-level identifiers, the DNS, and RFC 2428
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Oct 2003 10:31:23 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C5D1@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Persistent applications-level identifiers, the DNS, and RFC 2428
Thread-Index: AcOIe4yol07qMU3pSG6xrZ6Q8gV/hwAjXsfA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "John C Klensin" <john-ietf@jck.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

John,

> John C Klensin wrote:
> My ambitious in raising these questions are _very_ limited
> and, in particular, I don't see this as a back door to
> solving the non-DNS, topology-independent, persistent
> identifier problem. (It seems to me that needs to be solved
> through the front door, or not at all.).

I'm with you here. So, we know we need something more universal, but in
the meantime we band-aid FTP to keep going. Because of its special
status and the fact that it is widespread, FTP might justify doing the
work for only one protocol. It is clear that to be worthy of the effort,
this should be deployed way before a persistent identifier solution is
rolled out though.
As long as I'm not the one doing the work I don't have a problem with it
:-D

However, I do have a concern: when later a generic identifier mechanism
is deployed, we will have two standards. Have you had any thoughts on
the possible collisions there?

Michel.




From owner-ietf@ietf.org  Thu Oct  2 14:10:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17463
	for <ietf-web-archive@odin.ietf.org>; Thu, 2 Oct 2003 14:10:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A57n8-0006c5-6e
	for ietf-list@asgard.ietf.org; Thu, 02 Oct 2003 14:03:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A57n4-0006Ym-4t
	for ietf@asgard.ietf.org; Thu, 02 Oct 2003 14:03:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17032
	for <ietf@ietf.org>; Thu, 2 Oct 2003 14:02:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57n3-0004Py-00
	for ietf@ietf.org; Thu, 02 Oct 2003 14:03:01 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57n2-0004Pv-00
	for ietf@ietf.org; Thu, 02 Oct 2003 14:03:00 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1A57n2-000Ly3-00; Thu, 02 Oct 2003 13:03:00 -0500
Date: Thu, 02 Oct 2003 14:02:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michel Py <michel@arneill-py.sacramento.ca.us>, ietf@ietf.org
Subject: RE: Persistent applications-level identifiers, the DNS,
 and RFC 2428
Message-ID: <249461346.1065103375@scan.jck.com>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C5D1@server2003.arneill-py.sacramento.ca.us>
References:  <DD7FE473A8C3C245ADA2A2FE1709D90B06C5D1@server2003.ar
 neill-py.sacramento.ca.us>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Thursday, 02 October, 2003 10:31 -0700 Michel Py 
<michel@arneill-py.sacramento.ca.us> wrote:

> John,
>
>> John C Klensin wrote:
>> My ambitious in raising these questions are _very_ limited
>> and, in particular, I don't see this as a back door to
>> solving the non-DNS, topology-independent, persistent
>> identifier problem. (It seems to me that needs to be solved
>> through the front door, or not at all.).
>
> I'm with you here. So, we know we need something more
> universal, but in the meantime we band-aid FTP to keep going.
> Because of its special status and the fact that it is
> widespread, FTP might justify doing the work for only one
> protocol. It is clear that to be worthy of the effort, this
> should be deployed way before a persistent identifier solution
> is rolled out though.
> As long as I'm not the one doing the work I don't have a
> problem with it :-D
>
> However, I do have a concern: when later a generic identifier
> mechanism is deployed, we will have two standards. Have you
> had any thoughts on the possible collisions there?

My goal is precisely to avoid ending up with either two 
standards or eight verbs.  Explanation of the latter:

      IPv4      IPv6 & self-referent  DNS    StableID
     address       address

RFC    959           2428           ???        ???
Verb  PORT,PASV    EPRT,EPSV     ?DPRT,DPSV? ?IPRT,IPSV?

That seems to me excessive, if we can avoid it.  So the 
suggestion is whether, given that 2428 is at Proposed, maybe it 
would be worth revising it, and the syntax for EPRT and EPSV, to 
_permit_ use of a DNS name now and to provide a clear extension 
path for a generic/stable identifier.

Too many DNS implementations are still having to support the "X" 
forms of the directory changing and modifying commands, and it 
has been a very long time.   All of them will need to support, 
esentially forever, PORT and PASV.  Ending up with eight verbs 
seems to me to be poor architecture, worse interface design, and 
a magnet for poor implementations.

--On Thursday, 02 October, 2003 13:39 -0400 Mark Allman 
<mallman@icir.org> wrote:

>...
> I think my hit to your narrow question is "no".  Sort of.
>
> It seems to me that the mechanisms defined in rfc2428 are
> working just fine.  Why go monkeying around with them?

I do not want to monkey around with those _mechanisms_.  I am 
objecting only to the syntax, which is extensible only by adding 
more verbs (see below).

>  It
> seems to me that the practical benefits of doing so would be
> quite small.  You may add a bit of flexibility in some cases,
> but you're also going to run up against a raft of new
> problems.  What are the practical benefits that we're going to
> get out of this exercise (i.e., how does this make FTP somehow
> better and not just "prettier" under the hood?).

In the, admittedly rare, situations in which the transfer is 
really third-party, and not even bound tightly to one of the 
other two, passing the domain name of the third host (one that 
is not at either end of the command connection) would seem more 
consistent with general architectural principles.  That seems to 
me to be especially true because, for those cases, the command 
connection host(s) are likely to get the pointer to that host in 
DNS name or URI form, not as an address.  In a world of NATs and 
split-horizon DNS setups (not that I like either), it seems far 
preferable to have the DNS name resolved from the host that is 
going to use the results to open a connection.   Again, this is 
a rare case but one that has occasionally been important with 
the IPv4 (and NCP) implementations of FTP.

> Now, if you had asked the question a little differently I
> might have answered differently.  If the question is:
>
>     Should we *add* a couple more verbs to FTP that are to be
> more     generic than the current verbs and allow for DNS
> names and other     "labels" we may come up with the in the
> future?  (With the     intent that the new verbs and the old
> verbs could co-exist.)
>
> Then I'd certainly be fine with that (assuming someone has the
> energy).  If these new commands end up taking over in the
> future then that's great and we can think about moving rfc2428
> to historic at that time.  But, I think the key here is that,
> IMO, we should *add*, not *replace*.

Aha.  Then we are having a difference of opinion about 
architecture and aesthetics, not function.  Putting in a new 
verb for the same function each time one wants to provide what 
is logically the same information in a different form impresses 
me as a bad idea.  You prefer it.  I don't know how to resolve 
that difference of aesthetic convictions other than with some 
"beauty is in the mind of the beholder" platitude... and that 
doesn't produce a resolution.

     john




From owner-ietf@ietf.org  Thu Oct  2 14:33:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18888
	for <ietf-web-archive@odin.ietf.org>; Thu, 2 Oct 2003 14:33:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A58CI-0000hW-El
	for ietf-list@asgard.ietf.org; Thu, 02 Oct 2003 14:29:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A58BC-0000aD-W1
	for ietf@asgard.ietf.org; Thu, 02 Oct 2003 14:27:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18568
	for <ietf@ietf.org>; Thu, 2 Oct 2003 14:27:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58BB-0004tv-00
	for ietf@ietf.org; Thu, 02 Oct 2003 14:27:57 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58BB-0004tc-00
	for ietf@ietf.org; Thu, 02 Oct 2003 14:27:57 -0400
Content-class: urn:content-classes:message
Subject: RE: Persistent applications-level identifiers, the DNS, and RFC 2428
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Oct 2003 11:27:26 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C5D2@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Persistent applications-level identifiers, the DNS, and RFC 2428
Thread-Index: AcOJD21ULZTUjkjESp26Xz7dg7ZNgAAAeKMQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "John C Klensin" <john-ietf@jck.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

John,

> John C Klensin wrote:
> My goal is precisely to avoid ending up with either two=20
> standards or eight verbs.  Explanation of the latter:
>
>      IPv4      IPv6 & self-referent   DNS      StableID
>     address        address
> RFC    959           2428             ???        ???
> Verb  PORT,PASV    EPRT,EPSV     ?DPRT,DPSV? ?IPRT,IPSV?
>
> That seems to me excessive, if we can avoid it.  So the
> suggestion is whether, given that 2428 is at Proposed,
> maybe it would be worth revising it, and the syntax for
> EPRT and EPSV, to _permit_ use of a DNS name now and to
> provide a clear extension path for a generic/stable
> identifier.

There is an issue with backwards compatibility here:
Let's say we have a source host that has an implementation that allows
EPRT and EPSV to use a name as well as an address. The destination host
is a legacy host (meaning, a host implementing only 2428 as it is today,
address only). How will the destination react when receiving an EPSV
with a name instead of an address?

More generically, how will a host react when receiving an EPSV with foo
when foo is unknown? I am curious about the mechanism you envision to
determine what kind of info is being passed.

Michel.




From owner-ietf@ietf.org  Thu Oct  2 14:59:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17464
	for <ietf-web-archive@odin.ietf.org>; Thu, 2 Oct 2003 14:10:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A57r0-0006wa-2T
	for ietf-list@asgard.ietf.org; Thu, 02 Oct 2003 14:07:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A57p1-0006ed-S3
	for ietf@asgard.ietf.org; Thu, 02 Oct 2003 14:05:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17164
	for <ietf@ietf.org>; Thu, 2 Oct 2003 14:04:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57p0-0004Sj-00
	for ietf@ietf.org; Thu, 02 Oct 2003 14:05:02 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57p0-0004Rp-00
	for ietf@ietf.org; Thu, 02 Oct 2003 14:05:02 -0400
Received: from cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 02 Oct 2003 11:10:11 -0700
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h92I4QXg022552;
	Thu, 2 Oct 2003 11:04:30 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AIR03533;
	Thu, 2 Oct 2003 11:04:25 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA03142; Thu, 2 Oct 2003 11:04:25 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16252.26793.98358.66738@thomasm-u1.cisco.com>
Date: Thu, 2 Oct 2003 11:04:25 -0700 (PDT)
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: Persistent applications-level identifiers, the DNS, and RFC 2428
In-Reply-To: <200310020637.PAA05272@necom830.hpcl.titech.ac.jp>
References: <190395764.1065044308@scan.jck.com>
	<200310020637.PAA05272@necom830.hpcl.titech.ac.jp>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Masataka Ohta writes:
 > John;
 > > I am asking the question about FTP, about a piece of syntax in 
 > > the protocol, and about the options that syntax permits.
 > 
 > For what purpose?
 > 
 > > I am asking only about why we haven't structured that syntax
 > 
 > Seemingly because there was no reason to have one.
 > 
 > If you think you now have a reason, you should state it.
 > 
 > If you don't, we can debate forever on infinite variations of
 > reasons and associated extensions.
 > 
 > For example, how about extending FTP to be able to treat 
 > realtime stream? It is a question about FTP, about a piece
 > of syntax (MODE/STRU commands) in the protocol, and about
 > the options that syntax permits.

I'm with Masataka here... I'm completely confused
as to what the problem is here. And in particular,
why another rendezvous protocol like, oh say, SIP
wouldn't suffer from the same set of problems --
which obviously already does have that realtime
stream rendezvous capability :)

		  Mike



From owner-ietf@ietf.org  Thu Oct  2 15:08:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20720
	for <ietf-web-archive@odin.ietf.org>; Thu, 2 Oct 2003 15:08:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A58dO-0002ru-GZ
	for ietf-list@asgard.ietf.org; Thu, 02 Oct 2003 14:57:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A58cx-0002nX-4G
	for ietf@asgard.ietf.org; Thu, 02 Oct 2003 14:56:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19777
	for <ietf@ietf.org>; Thu, 2 Oct 2003 14:56:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58cv-0005Gh-00
	for ietf@ietf.org; Thu, 02 Oct 2003 14:56:37 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58cv-0005Ge-00
	for ietf@ietf.org; Thu, 02 Oct 2003 14:56:37 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id A9C42141CB; Thu,  2 Oct 2003 14:56:37 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 27182-07; Thu,  2 Oct 2003 14:56:36 -0400 (EDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id B59BF1416A; Thu,  2 Oct 2003 14:56:36 -0400 (EDT)
Date: Thu, 2 Oct 2003 14:54:37 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <john-ietf@jck.com>
Cc: moore@cs.utk.edu, michel@arneill-py.sacramento.ca.us, ietf@ietf.org
Subject: Re: Persistent applications-level identifiers, the DNS, and RFC
 2428
Message-Id: <20031002145437.5b67681f.moore@cs.utk.edu>
In-Reply-To: <249461346.1065103375@scan.jck.com>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C5D1@server2003.ar
 neill-py.sacramento.ca.us>
	<249461346.1065103375@scan.jck.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> My goal is precisely to avoid ending up with either two 
> standards or eight verbs.  Explanation of the latter:
> 
>       IPv4      IPv6 & self-referent  DNS    StableID
>      address       address
> 
> RFC    959           2428           ???        ???
> Verb  PORT,PASV    EPRT,EPSV     ?DPRT,DPSV? ?IPRT,IPSV?
> 
> That seems to me excessive, if we can avoid it. 

If a case could actually be made for using DNS names in FTP
(and IMHO the case against is far heavier than the case in favor)
it would be a simple matter to define new "address types" for EPSV
and EPRT.  I don't see why new commands would be necessary.

> In the, admittedly rare, situations in which the transfer is 
> really third-party, and not even bound tightly to one of the 
> other two, passing the domain name of the third host (one that 
> is not at either end of the command connection) would seem more 
> consistent with general architectural principles. 

Which principles are those?  That it's better to use an ambiguous
reference to a host than a unambiguous one?  That it's better to add
extra complexity and failure modes to a system than to use a simple and
reliable mechanism?  That it's better to encourage fragmenting the DNS
to reflect disjoint addressing realms than it is to encourage a sane
address space?

> That seems to 
> me to be especially true because, for those cases, the command 
> connection host(s) are likely to get the pointer to that host in 
> DNS name or URI form, not as an address.  In a world of NATs and 
> split-horizon DNS setups (not that I like either), it seems far 
> preferable to have the DNS name resolved from the host that is 
> going to use the results to open a connection. 

It might seem that way, but experience indicates that DNS names are
_less_ reliable than IP addresses in referrals.  Because even with 
all of the harm done by RFC 1918 addersses, DNS is far more screwed up
in practice than IP.  Partly this is because DNS depends on even things
to be accessible, configured, and working properly in order to function
than IP does; and part of this is because there are more games played
with DNS than with IP.  And while use of RFC 1918 addresses at least
provides a clue that the address is not usable outside of the local
realm, there's no way to know whether a DNS name is globally usable or
not. 

And given the potential for a DNS name to produce different RRs at
different locations of the net (yes there are people doing this), it's
not clear at all that having the DNS name resolved from the host that is
going to use the address is the "right" meaning.   I would argue that
the lookup that is the closest to where the DNS name is _specified_ is
more likely to be the right one.   (Though I'd argue even more strongly
that producing different RRs at different locations is simply broken.)

At any rate, until someone defines a good way to make 3rd party FTP
transfers secure, any arguments about why DNS names are needed for 3rd
party transfers seem moot.


Keith



From owner-ietf@ietf.org  Thu Oct  2 23:19:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06474
	for <ietf-web-archive@odin.ietf.org>; Thu, 2 Oct 2003 23:19:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5GHX-0003Rl-3J
	for ietf-list@asgard.ietf.org; Thu, 02 Oct 2003 23:07:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5GGd-0003Pg-Fr
	for ietf@asgard.ietf.org; Thu, 02 Oct 2003 23:06:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06124
	for <ietf@ietf.org>; Thu, 2 Oct 2003 23:05:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5GGa-0002Gp-00
	for ietf@ietf.org; Thu, 02 Oct 2003 23:06:04 -0400
Received: from [202.108.44.204] (helo=163.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1A5GGZ-0002GH-00
	for ietf@ietf.org; Thu, 02 Oct 2003 23:06:04 -0400
Received: from wl302 (unknown [211.67.24.168])
	by 192.168.1.204 (Coremail) with SMTP id PhcBAGjnfD8XABio.1
	for <ietf@ietf.org>; Fri, 03 Oct 2003 11:05:14 +0800 (CST)
X-Originating-IP: [211.67.24.168]
Message-ID: <002f01c3895b$89e71d40$a81843d3@wl302>
From: "wang liang" <wangliang_f@163.com>
To: <ietf@ietf.org>
Subject:  How to bulid a new group?
Date: Fri, 3 Oct 2003 11:07:52 +0800
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 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



 If I find there is no a group for some important issues about Internet, and
It may be  necessary  to build a new one,what should I do?Who will deal with
this kind of suggestion?Where can I find the detailed  process of  asking
for a new work group?thanks.




From owner-ietf@ietf.org  Thu Oct  2 23:48:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07458
	for <ietf-web-archive@odin.ietf.org>; Thu, 2 Oct 2003 23:48:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5GrP-000539-HF
	for ietf-list@asgard.ietf.org; Thu, 02 Oct 2003 23:44:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5Gqh-00050h-BL
	for ietf@asgard.ietf.org; Thu, 02 Oct 2003 23:43:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07226
	for <ietf@ietf.org>; Thu, 2 Oct 2003 23:43:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Gqf-0002fw-00
	for ietf@ietf.org; Thu, 02 Oct 2003 23:43:21 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Gqe-0002ft-00
	for ietf@ietf.org; Thu, 02 Oct 2003 23:43:20 -0400
Received: from [63.202.92.152] (adsl-63-202-92-152.dsl.snfc21.pacbell.net [63.202.92.152])
	(authenticated bits=0)
	by above.proper.com (8.12.9/8.12.8) with ESMTP id h933hEKQ030429;
	Thu, 2 Oct 2003 20:43:14 -0700 (PDT)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0600203ebba2a0a7dba6@[63.202.92.152]>
In-Reply-To: <002f01c3895b$89e71d40$a81843d3@wl302>
References: <002f01c3895b$89e71d40$a81843d3@wl302>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Thu, 2 Oct 2003 20:43:19 -0700
To: "wang liang" <wangliang_f@163.com>, <ietf@ietf.org>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: How to bulid a new group?
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 11:07 AM +0800 10/3/03, wang liang wrote:
>  If I find there is no a group for some important issues about Internet, and
>It may be  necessary  to build a new one,what should I do?Who will deal with
>this kind of suggestion?Where can I find the detailed  process of  asking
>for a new work group?thanks.

See <http://www.ietf.org/tao.html> for probably everything you need 
to get started.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Fri Oct  3 00:32:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08690
	for <ietf-web-archive@odin.ietf.org>; Fri, 3 Oct 2003 00:32:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5HU2-0006pa-AB
	for ietf-list@asgard.ietf.org; Fri, 03 Oct 2003 00:24:02 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5HTd-0006nc-4c
	for ietf@asgard.ietf.org; Fri, 03 Oct 2003 00:23:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08308
	for <ietf@ietf.org>; Fri, 3 Oct 2003 00:23:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5HTb-000331-00
	for ietf@ietf.org; Fri, 03 Oct 2003 00:23:35 -0400
Received: from uni00du.unity.ncsu.edu ([152.1.13.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5HTa-00032y-00
	for ietf@ietf.org; Fri, 03 Oct 2003 00:23:34 -0400
Received: (from mwang3@localhost)
          by uni00du.unity.ncsu.edu (8.8.4/EC02Jan97)
	  id AAA16265; Fri, 3 Oct 2003 00:23:35 -0400 (EDT)
Date: Fri, 3 Oct 2003 00:23:34 -0400 (EDT)
From: Meng Wang <mwang3@unity.ncsu.edu>
To: ietf@ietf.org
Subject: About intrusion detection
Message-ID: <Pine.GSO.4.58.0310030022430.15687@uni00du.unity.ncsu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

  Anyone can provide useful info such as URLs on intrusion detection?
Is there any definition/description or summary on different kinds of
intrusions?

  Thanks.
meng




From owner-ietf@ietf.org  Fri Oct  3 01:49:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10562
	for <ietf-web-archive@odin.ietf.org>; Fri, 3 Oct 2003 01:49:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5IhW-0003pG-1m
	for ietf-list@asgard.ietf.org; Fri, 03 Oct 2003 01:42:02 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5Ign-0003n9-Tu
	for ietf@asgard.ietf.org; Fri, 03 Oct 2003 01:41:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10448
	for <ietf@ietf.org>; Fri, 3 Oct 2003 01:41:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Igl-0003kZ-00
	for ietf@ietf.org; Fri, 03 Oct 2003 01:41:15 -0400
Received: from web80604.mail.yahoo.com ([66.218.79.93])
	by ietf-mx with smtp (Exim 4.12)
	id 1A5Igl-0003kQ-00
	for ietf@ietf.org; Fri, 03 Oct 2003 01:41:15 -0400
Message-ID: <20031003054046.91544.qmail@web80604.mail.yahoo.com>
Received: from [62.56.220.4] by web80604.mail.yahoo.com via HTTP; Thu, 02 Oct 2003 22:40:46 PDT
Date: Thu, 2 Oct 2003 22:40:46 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: IETF Storage Solution
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1984144337-1065159646=:88518"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-1984144337-1065159646=:88518
Content-Type: text/plain; charset=us-ascii

Have the old hard disks read with use of laser and copied into new larger capacity hard disks.  Laser will read everything on the magnetic surface of the old hard disks including passwords, apps, OS, data and configurations.
 
CAUTION:  New hard disks must have the same hardware characteristics as the old ones to prevent OS malfunction ( special tailor-made hard disks ?? ).
 
How do you think governments read stolen laptops?? With laser ofcourse!
 
Long-term solution : Nano-technology - no good systems yet.
 
Nyagudi Musandu


---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
--0-1984144337-1065159646=:88518
Content-Type: text/html; charset=us-ascii

<DIV>Have the old hard disks read with use of laser and copied into new larger capacity hard disks.&nbsp; Laser will&nbsp;read everything on the magnetic surface of the old hard disks including passwords, apps, OS, data and configurations.</DIV>
<DIV>&nbsp;</DIV>
<DIV>CAUTION:&nbsp; New hard disks must have the same hardware characteristics as the old ones to prevent OS malfunction ( special tailor-made hard disks ?? ).</DIV>
<DIV>&nbsp;</DIV>
<DIV>How do you think governments read stolen laptops?? With laser ofcourse!</DIV>
<DIV>&nbsp;</DIV>
<DIV>Long-term solution : Nano-technology - no good systems yet.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi Musandu</DIV><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://shopping.yahoo.com/?__yltc=s%3A150000443%2Cd%3A22708228%2Cslk%3Atext%2Csec%3Amail">The New Yahoo! Shopping</a> - with improved product search
--0-1984144337-1065159646=:88518--



From owner-ietf@ietf.org  Fri Oct  3 09:22:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05758
	for <ietf-web-archive@odin.ietf.org>; Fri, 3 Oct 2003 09:22:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5Pm0-0007wU-IM
	for ietf-list@asgard.ietf.org; Fri, 03 Oct 2003 09:15:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A58D9-0000jb-LF
	for ietf@asgard.ietf.org; Thu, 02 Oct 2003 14:29:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18691
	for <ietf@ietf.org>; Thu, 2 Oct 2003 14:29:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58D8-0004wO-00
	for ietf@ietf.org; Thu, 02 Oct 2003 14:29:58 -0400
Received: from pop-2.dnv.wideopenwest.com ([64.233.207.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58D7-0004vY-00
	for ietf@ietf.org; Thu, 02 Oct 2003 14:29:58 -0400
Received: from guns.mallman.dyndns.org (d233-64-125-235.clv.wideopenwest.com [64.233.235.125])
	by pop-2.dnv.wideopenwest.com (8.11.6/8.11.6) with ESMTP id h92IWiM19572;
	Thu, 2 Oct 2003 13:32:44 -0500
Message-Id: <200310021832.h92IWiM19572@pop-2.dnv.wideopenwest.com>
To: John C Klensin <john-ietf@jck.com>
From: Mark Allman <mallman@icir.org>
Reply-To: mallman@icir.org
cc: Michel Py <michel@arneill-py.sacramento.ca.us>, ietf@ietf.org
Subject: Re: Persistent applications-level identifiers, the DNS, and RFC 2428 
In-Reply-To: <249461346.1065103375@scan.jck.com> 
Organization: ICSI Center for Internet Research (ICIR)
Song-of-the-Day: Jack and Diane
Date: Thu, 02 Oct 2003 14:24:28 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk


> Aha.  Then we are having a difference of opinion about
> architecture and aesthetics, not function.  Putting in a new verb
> for the same function each time one wants to provide what is
> logically the same information in a different form impresses me as
> a bad idea.  You prefer it.

No, I don't.  I share your desire to do something that is quite
generic and extendable and not end up with a ton of these commands.

My point was that EPRT/EPSV are working fine and rather than try to
kludge something on top of those why not just aim for a GPRT/GPSV
which would be very generic and general commands that could take any
sorts of identifiers of hosts that one might ever want to throw at
it.  That could be based on 2428, for sure.  That strikes me as a
clean approach.

(Oh ... and to resurrect another notion from the days of haggling
over the i-ds before 2428 ... I'd also think the transport protocol
stuff should be negotiated, as well.)

allman


--
Mark Allman -- ICIR -- http://www.icir.org/mallman/





From owner-ietf@ietf.org  Fri Oct  3 09:22:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05761
	for <ietf-web-archive@odin.ietf.org>; Fri, 3 Oct 2003 09:22:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5Pm0-0007wD-AA
	for ietf-list@asgard.ietf.org; Fri, 03 Oct 2003 09:15:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A57Rc-0004ml-Fv
	for ietf@asgard.ietf.org; Thu, 02 Oct 2003 13:40:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15544
	for <ietf@ietf.org>; Thu, 2 Oct 2003 13:40:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57Ra-00040X-00
	for ietf@ietf.org; Thu, 02 Oct 2003 13:40:50 -0400
Received: from pop-2.dnv.wideopenwest.com ([64.233.207.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57Ra-0003zl-00
	for ietf@ietf.org; Thu, 02 Oct 2003 13:40:50 -0400
Received: from guns.mallman.dyndns.org (d233-64-125-235.clv.wideopenwest.com [64.233.235.125])
	by pop-2.dnv.wideopenwest.com (8.11.6/8.11.6) with ESMTP id h92Hm1x11683;
	Thu, 2 Oct 2003 12:48:01 -0500
Message-Id: <200310021748.h92Hm1x11683@pop-2.dnv.wideopenwest.com>
To: John C Klensin <john-ietf@jck.com>
From: Mark Allman <mallman@icir.org>
Reply-To: mallman@icir.org
cc: ietf@ietf.org, "Shawn Ostermann" <sdo@picard.cs.ohiou.edu>
Subject: Re: Persistent applications-level identifiers, the DNS, and RFC 2428 
In-Reply-To: <155922084.1065009834@scan.jck.com> 
Organization: ICSI Center for Internet Research (ICIR)
Song-of-the-Day: Jack and Diane
Date: Thu, 02 Oct 2003 13:39:45 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk


John-

> It seems appropriate to ask whether 2428 should be opened and 
> given at least the capability of passing DNS names and maybe 
> some syntax that would permit clean extension to future 
> identifiers.

I think my hit to your narrow question is "no".  Sort of.

It seems to me that the mechanisms defined in rfc2428 are working
just fine.  Why go monkeying around with them?  It seems to me that
the practical benefits of doing so would be quite small.  You may
add a bit of flexibility in some cases, but you're also going to run
up against a raft of new problems.  What are the practical benefits
that we're going to get out of this exercise (i.e., how does this
make FTP somehow better and not just "prettier" under the hood?).

Now, if you had asked the question a little differently I might have
answered differently.  If the question is:

    Should we *add* a couple more verbs to FTP that are to be more
    generic than the current verbs and allow for DNS names and other
    "labels" we may come up with the in the future?  (With the
    intent that the new verbs and the old verbs could co-exist.)

Then I'd certainly be fine with that (assuming someone has the
energy).  If these new commands end up taking over in the future
then that's great and we can think about moving rfc2428 to historic
at that time.  But, I think the key here is that, IMO, we should
*add*, not *replace*.

allman


--
Mark Allman -- ICIR -- http://www.icir.org/mallman/





From owner-ietf@ietf.org  Fri Oct  3 09:29:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06162
	for <ietf-web-archive@odin.ietf.org>; Fri, 3 Oct 2003 09:29:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5PwV-0000ZT-I1
	for ietf-list@asgard.ietf.org; Fri, 03 Oct 2003 09:25:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5Pvp-0000RT-Vv
	for ietf@asgard.ietf.org; Fri, 03 Oct 2003 09:25:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05961
	for <ietf@ietf.org>; Fri, 3 Oct 2003 09:25:09 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Pvp-0000gH-00
	for ietf@ietf.org; Fri, 03 Oct 2003 09:25:17 -0400
Received: from h80ad2515.async.vt.edu ([128.173.37.21] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Pvn-0000g3-00
	for ietf@ietf.org; Fri, 03 Oct 2003 09:25:16 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h93DPCqd015622;
	Fri, 3 Oct 2003 09:25:12 -0400
Message-Id: <200310031325.h93DPCqd015622@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: NM Research <nm_research@yahoo.com>
Cc: ietf@ietf.org
Subject: Re: IETF Storage Solution 
In-Reply-To: Your message of "Thu, 02 Oct 2003 22:40:46 PDT."
             <20031003054046.91544.qmail@web80604.mail.yahoo.com> 
References: <20031003054046.91544.qmail@web80604.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1432453463P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 03 Oct 2003 09:25:11 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Thu, 02 Oct 2003 22:40:46 PDT, NM Research <nm_research@yahoo.com>  said:

> Have the old hard disks read with use of laser and copied into new larger capacity hard disks.

> CAUTION:  New hard disks must have the same hardware characteristics as the old ones to prevent OS malfunction ( special tailor-made hard disks ?? ).

This is totally nonsensical.  You can't have the "same hardware characteristics"
and "larger capacity" at the same time.

> How do you think governments read stolen laptops?? With laser ofcourse!

Actually, if you've stolen a laptop, it's usually easier to just take the disk and
plug it into another machine and read it with the normal mechanisms.

And if you're doing data recovery because you were silly enough to steal a laptop
that had a physically broken disk drive, the usual hardware is magnetic-based
rather than laser-based.

This is even less IETF-relevant than your previous postings.  Please read
the following two documents before posting to this list again:

http://www.ietf.org/tao.html (Also known as RFC3060)
http://www.ietf.org/internet-drafts/draft-mrose-ietf-posting-03.txt

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

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

iD8DBQE/fXi3cC3lWbTT17ARArN2AJwJb4q/hOMpOwt0SXBquZeCwYSaTQCfaW8c
1+WWO27/lmcI7eXXtylVDFI=
=KHrf
-----END PGP SIGNATURE-----

--==_Exmh_1432453463P--



From owner-ietf@ietf.org  Fri Oct  3 12:24:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14812
	for <ietf-web-archive@odin.ietf.org>; Fri, 3 Oct 2003 12:24:37 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5Sb0-0000t2-IT
	for ietf-list@asgard.ietf.org; Fri, 03 Oct 2003 12:15:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5SYX-0000lk-2P
	for ietf@asgard.ietf.org; Fri, 03 Oct 2003 12:13:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14094
	for <ietf@ietf.org>; Fri, 3 Oct 2003 12:13:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5SYW-0002ms-00
	for ietf@ietf.org; Fri, 03 Oct 2003 12:13:24 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5SYT-0002mK-00
	for ietf@ietf.org; Fri, 03 Oct 2003 12:13:22 -0400
Content-class: urn:content-classes:message
Subject: RE: Persistent applications-level identifiers, the DNS, and RFC 2428 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 3 Oct 2003 09:12:49 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C5D5@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Persistent applications-level identifiers, the DNS, and RFC 2428 
Thread-Index: AcOJsljJ4exeXB8yTN6MWsCeBCNEQgAEQ74g
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "John C Klensin" <john-ietf@jck.com>
Cc: <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Mark / John,

> Mark Allman wrote:
> Should we *add* a couple more verbs to FTP that are to be
> more generic than the current verbs and allow for DNS names
> and other "labels" we may come up with the in the future?
> (With the intent that the new verbs and the old verbs could
> co-exist.)
> Then I'd certainly be fine with that (assuming someone has
> the energy).  If these new commands end up taking over in
> the future then that's great and we can think about moving
> rfc2428 to historic at that time.  But, I think the key
> here is that, IMO, we should *add*, not *replace*.

This makes sense to me. For the same reason we are stuck supporting PORT
and PASV forever, I think that we are stuck supporting EPRT and EPSV
forever as well and that two new verbs that would include the
functionality of EPRT and EPSV with extended semantics that would allow
passing names and foo is the way to go.

> John C Klensin wrote:
> given that 2428 is at Proposed=20

I believe there is deployed EPRT/EPSV code based on 2428; IMHO you can't
assume that this code base will be upgraded to support names. It's too
late.

Michel.




From owner-ietf@ietf.org  Fri Oct  3 15:29:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22923
	for <ietf-web-archive@odin.ietf.org>; Fri, 3 Oct 2003 15:29:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5VQn-0006bi-68
	for ietf-list@asgard.ietf.org; Fri, 03 Oct 2003 15:17:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5Sbe-0000tO-4U
	for ietf@asgard.ietf.org; Fri, 03 Oct 2003 12:16:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14228
	for <ietf@ietf.org>; Fri, 3 Oct 2003 12:16:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Sbd-0002pg-00
	for ietf@ietf.org; Fri, 03 Oct 2003 12:16:37 -0400
Received: from smtp.sprintpcs.com ([63.167.114.16] helo=dedicated59-bos.wh.sprintip.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Sbc-0002pA-00
	for ietf@ietf.org; Fri, 03 Oct 2003 12:16:36 -0400
Received: from solidmatrix.com ([68.27.196.202])
 by dedicated59-bos.wh.sprintip.net
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTPA id <0HM600I65VUQ3K@dedicated59-bos.wh.sprintip.net> for
 ietf@ietf.org; Fri, 03 Oct 2003 16:16:07 +0000 (GMT)
Date: Fri, 03 Oct 2003 12:14:27 -0400
From: Yakov Shafranovich <research@solidmatrix.com>
Subject: Fwd: ICANN asks Verisign to shutdown SiteFinder in 48 hours
To: ietf@ietf.org
Message-id: <3F7DA063.6020409@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

Forwarded from the ASRG list:

-------- Original Message --------
Subject: 0. General - ICANN asks Verisign to shut down SiteFinder in 48
hours
Date: Fri, 03 Oct 2003 11:31:58 -0400
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
To: ASRG list <asrg@ietf.org>

ICANN has posted the following announcement to their website, asking
Verisign to stop the SiteFinder service within 48 hours:

http://www.icann.org/announcements/advisory-03oct03.htm








From owner-ietf@ietf.org  Fri Oct  3 16:10:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24579
	for <ietf-web-archive@odin.ietf.org>; Fri, 3 Oct 2003 16:10:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5W8e-0000MR-M2
	for ietf-list@asgard.ietf.org; Fri, 03 Oct 2003 16:02:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5W7G-0000JY-Fp
	for ietf@asgard.ietf.org; Fri, 03 Oct 2003 16:01:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24111
	for <ietf@ietf.org>; Fri, 3 Oct 2003 16:01:21 -0400 (EDT)
From: william@elan.net
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5W7F-0005c8-00
	for ietf@ietf.org; Fri, 03 Oct 2003 16:01:29 -0400
Received: from sokol.elan.net ([216.151.192.200])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5W79-0005c5-00
	for ietf@ietf.org; Fri, 03 Oct 2003 16:01:28 -0400
Received: from sokol.elan.net (localhost.localdomain [127.0.0.1])
	by sokol.elan.net (8.12.5/8.12.5) with ESMTP id h93HTXBo001915
	for <ietf@ietf.org>; Fri, 3 Oct 2003 10:29:33 -0700
Received: from localhost (william@localhost)
	by sokol.elan.net (8.12.5/8.12.5/Submit) with ESMTP id h93HTXdH001911
	for <ietf@ietf.org>; Fri, 3 Oct 2003 10:29:33 -0700
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Fri, 3 Oct 2003 10:29:33 -0700 (PDT)
To: ietf@ietf.org
Subject: Re: Fwd: ICANN asks Verisign to shutdown SiteFinder in 48 hours
In-Reply-To: <3F7DA063.6020409@solidmatrix.com>
Message-ID: <Pine.LNX.4.44.0310031019300.30751-100000@sokol.elan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

> ICANN has posted the following announcement to their website, asking
> Verisign to stop the SiteFinder service within 48 hours:
> 
> http://www.icann.org/announcements/advisory-03oct03.htm

Its finally over (for the now...):

http://www.washingtonpost.com/wp-dyn/articles/A40241-2003Oct3.html

VeriSign Freezes Search Service 
 
VeriSign Inc., the firm that operates a key piece of the Internet's 
address system, said it would temporarily shut down a new service that 
makes money off the typos of Web users after the Internet's oversight body 
threatened to take legal action against the company

Earlier today, Internet Corporation for Assigned Names and Numbers (ICANN) 
President Paul Twomey sent a letter to VeriSign demanding that the company 
take the service down or face legal consequences. Under its contracts with 
VeriSign ICANN can impose up to $100,000 in fines or strip the company of 
its authority to operate the registries that handle dot-com and dot-net 
Internet addresses.
 
"Without so much as a hearing, ICANN today formally asked us to shut down
the Site Finder service," said VeriSign spokesman Tom Galvin. "We will
accede to their request while we explore all of our options."
...
VeriSign also angered the close-knit group of engineers and scientists who 
are familiar with the technology underpinning the Internet. They say that 
Site Finder undermines the worldwide Domain Name System, causing e-mail 
systems, spam-blocking technology ano other applications to malfunction.

VeriSign said the claims are overblown.

"There is no data to indicate the core operation of the domain name system 
or the stability of the Internet has been adversely affected," VeriSign's 
Galvin said. "ICANN is using anecdotal and isolated issues in an attempt 
to assert a dubious right to regulate non-registry services."

Before agreeing to take down Site Finder, VeriSign had promised to work 
with the Internet community to iron out any glitches triggered by Site 
Finder.

Site Finder has triggered the first real showdown between VeriSign -- the 
world's largest Internet addressing company -- and ICANN, the group 
created by the U.S. government to bring order and competition to the 
growing online world.

"War is breaking out between the regulators and the people they regulate. 
This is a real power struggle [over] who controls the rules on the 
Internet going forward," said said Paxfire's Lewyn.




From owner-ietf@ietf.org  Fri Oct  3 17:33:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00155
	for <ietf-web-archive@odin.ietf.org>; Fri, 3 Oct 2003 17:33:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5XIG-0003Lq-Ob
	for ietf-list@asgard.ietf.org; Fri, 03 Oct 2003 17:16:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5XIC-0003K6-Dn
	for ietf@asgard.ietf.org; Fri, 03 Oct 2003 17:16:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29569
	for <ietf@ietf.org>; Fri, 3 Oct 2003 17:16:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5XIA-0007D4-00
	for ietf@ietf.org; Fri, 03 Oct 2003 17:16:50 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5XIA-0007Ci-00
	for ietf@ietf.org; Fri, 03 Oct 2003 17:16:50 -0400
Received: from vista.av8.net (vista.av8.net [130.105.36.10])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA17161;
	Fri, 3 Oct 2003 17:12:04 -0400
Date: Fri, 3 Oct 2003 17:12:02 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: Yakov Shafranovich <research@solidmatrix.com>
cc: ietf@ietf.org
Subject: Re: Fwd: ICANN asks Verisign to shutdown SiteFinder in 48 hours
In-Reply-To: <3F7DA063.6020409@solidmatrix.com>
Message-ID: <Pine.LNX.4.44.0310031700250.10796-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

I see that Verisign is complying while they "review their options".

Well, hopefully they are having their lawyers go over their contracts to
see if ICANN can claim it is in breach of any contract.  It would seem
that they can't, having not complained about other registries, and having
not substantiated any adverse effects to the internet.  It will take some
time to go through each claim and offer a substantial proof that it is
wrong.  It will be interesting to see what the lawyers say.

It was really to bad that they gave the "angry scientists and engineers"
as much credit as they did. This angry group is basically the same bunch
of Verisign bashers that have been whining about Verisign or Network
Solutions for many years, when there are other registries that are much
more deserving of criticism.  Calling them scientists and engineers gives
too much credit because real scientists and engineers deal in facts. I
would use another term.

I for one hope that SiteFinder will come back, and I wish Verisign good
luck.

		--Dean

On Fri, 3 Oct 2003, Yakov Shafranovich wrote:

> Forwarded from the ASRG list:
>
> -------- Original Message --------
> Subject: 0. General - ICANN asks Verisign to shut down SiteFinder in 48
> hours
> Date: Fri, 03 Oct 2003 11:31:58 -0400
> From: Yakov Shafranovich <research@solidmatrix.com>
> Organization: SolidMatrix Technologies, Inc.
> To: ASRG list <asrg@ietf.org>
>
> ICANN has posted the following announcement to their website, asking
> Verisign to stop the SiteFinder service within 48 hours:
>
> http://www.icann.org/announcements/advisory-03oct03.htm
>
>
>
>
>
>
>




From owner-ietf@ietf.org  Fri Oct  3 19:49:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04457
	for <ietf-web-archive@odin.ietf.org>; Fri, 3 Oct 2003 19:49:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5ZXc-0008Ox-6u
	for ietf-list@asgard.ietf.org; Fri, 03 Oct 2003 19:40:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5ZXM-0008M8-5b
	for ietf@asgard.ietf.org; Fri, 03 Oct 2003 19:40:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04241
	for <ietf@ietf.org>; Fri, 3 Oct 2003 19:40:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5ZXK-0000iP-00
	for ietf@ietf.org; Fri, 03 Oct 2003 19:40:38 -0400
Received: from smtpzilla5.xs4all.nl ([194.109.127.141])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5ZXJ-0000iM-00
	for ietf@ietf.org; Fri, 03 Oct 2003 19:40:38 -0400
Received: from thelady (a213-84-140-41.adsl.xs4all.nl [213.84.140.41])
	by smtpzilla5.xs4all.nl (8.12.9/8.12.9) with ESMTP id h93NebL1033846
	for <ietf@ietf.org>; Sat, 4 Oct 2003 01:40:37 +0200 (CEST)
From: "A. Kremer" <inanbe@xs4all.nl>
To: <ietf@ietf.org>
Subject: Out of Office Reply & junkmail
Date: Sat, 4 Oct 2003 01:40:47 +0200
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAKl/PcBvLSEmzIII0yovh2cKAAAAQAAAA+41UdubEgUq9NzZyndQdSwEAAAAA@xs4all.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ladies and gentlemen,

Is there any relationship between turning on an Out of Office Reply and
receiving a lot of junk/spammail?

There is a reason why I ask you this..

When I went for a 2 weeks holiday, I turned on my Out of Office Reply.
After those 2 weeks, when I got back at the office, I had received
250(!) spammails. I guess it is unnecessary to mention the contents
here. ;)

A few weeks later I got ill and stayed home, so I was not able to turn
on my Out of Office Reply.
After my return at the office, I only had received 2 spammails.

Then I had another holiday and I turned my Out of Office Reply on.
And guess what happened!
169 spammails when I returned at the office. After being absent for 7
working days.

At that moment the thought crossed my mind that there MUST be any
relationship between turning Out of Office Reply on, and receiving
junk/spammail.

So, am I right or am I wrong about this Out of Office issue?

If there is already an answer to this question, please let me know where
I can find it.

Very kind regards,

A. Kremer




From owner-ietf@ietf.org  Fri Oct  3 21:08:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06083
	for <ietf-web-archive@odin.ietf.org>; Fri, 3 Oct 2003 21:08:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5an1-0003ya-QO
	for ietf-list@asgard.ietf.org; Fri, 03 Oct 2003 21:00:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5am8-0003vh-EU
	for ietf@asgard.ietf.org; Fri, 03 Oct 2003 21:00:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05883
	for <ietf@ietf.org>; Fri, 3 Oct 2003 20:59:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5am6-0001Jv-00
	for ietf@ietf.org; Fri, 03 Oct 2003 20:59:58 -0400
Received: from srv-mailgatesjc2.webex.com ([64.68.123.248] helo=webex.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5am6-0001Jm-00
	for ietf@ietf.org; Fri, 03 Oct 2003 20:59:58 -0400
Received: from ([192.168.253.55])
	by srv-mailgatesjc2.webex.com with ESMTP ;
	Fri, 03 Oct 2003 17:58:55 -0700 (PDT)
Received: by BASTION.webex.com with Internet Mail Service (5.5.2653.19)
	id <SZ7ADCMJ>; Fri, 3 Oct 2003 17:58:33 -0700
Message-ID: <CA8D7A11C649284AA163D951DA565330032B3B6F@srv-mailsjc2>
From: Joerg Reichelt <Joerg.Reichelt@webex.com>
To: "Ietf (E-mail)" <ietf@ietf.org>
Subject: Re: I-D ACTION:draft-aeble-ooo-replies-00.txt
Date: Fri, 3 Oct 2003 18:00:31 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

I have a few comments regarding this draft.

While I agree with a lot of the statements regarding mailing
lists and bulk mail, I disagree with the following:

  "4. Suggested Practices

     Wherever possible, OoO replies SHOULD NOT be used. If they have to be
     used, their use should be tightly controlled:

     1.  OoO replies SHOULD only be used internal to any organization.
         Any mailbox available for contact with external parties SHOULD be
         a role-based mailbox to which several employees have access.

         Outgoing replies SHOULD have a From: header from that role
         mailbox, not from the person replying. This serves the purposes
         of

         *  being always available to the external party

         *  keeping sensitive information in-house.

         Role-based mailboxes SHALL NOT generate OoO replies ever."

This is fine for organizations where anyone within a certain group can 
handle a particular external request. This does, however, not work in 
most circumstances that I have seen. The reason being that often one
person is handling a particular project or customer, and there is too 
much context necessary to satisfactorily transfer the handling of that
contact on a very temporary basis, which makes it uneconomical.

This recommendation is too restrictive and doesn't consider such cases
that in my experience are very common. It might be a good idea to explore
typical cases where OoO notifications are being used, and give tailored
recommendations for these cases individually, since I believe there is
no one-size-fits-all.

     "2.  OoO replies MUST NOT include job information of the addressee."

Again, in the cases described above, you would want to respond in an
official capacity, in which case many companies require to include a
specific company signature containing all sorts of business information,
including the job title and contact information.

It is perfectly OK to include such information when responding to 
customer requests or emails from project partners. It is, however, 
not desirable in most cases for bulk mail and automated senders,
which are addressed separately in this recommendations.

     "4.  OoO systems MUST remember which originators were already notified
         and MUST NOT resend another OoO reply during a configurable
         timeframe. This timeframe SHOULD vary between one week and one
         month."

This should be applicable for any unique combination of <From: address,
To: address, OoO incident> (and possibly some other values).

I am specifically referring to the possibility that someone might be OoO
on Monday, and then again from Wednesday to Friday. If the incident was
defined as Monday plus Wednesday to Friday, and the sender was notified
of this whole set, then only one notification is sufficient. If the OoO
period 'Wednesday to Friday' was not known when the OoO notification was
set up for Monday, and thus this information was not conveyed in the
notifications sent out for that Monday incident, then a separate 
notification should be sent for the second incident, regardless of the 
fact that the sender already got a notification within a week (or month).

/jr



From owner-ietf@ietf.org  Fri Oct  3 21:21:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06459
	for <ietf-web-archive@odin.ietf.org>; Fri, 3 Oct 2003 21:21:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5b3T-0005AF-7Z
	for ietf-list@asgard.ietf.org; Fri, 03 Oct 2003 21:17:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5b2k-00057F-GH
	for ietf@asgard.ietf.org; Fri, 03 Oct 2003 21:17:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06340
	for <ietf@ietf.org>; Fri, 3 Oct 2003 21:17:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5b2i-0001UU-00
	for ietf@ietf.org; Fri, 03 Oct 2003 21:17:08 -0400
Received: from [203.135.39.217] (helo=thisdomain)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5b2e-0001UB-00
	for ietf@ietf.org; Fri, 03 Oct 2003 21:17:07 -0400
Received: from giki.giki.edu.pk by giki.edu.pk ; Sat, 04 Oct 2003 06:14:30 +0500
X-Originating-IP: 192.168.1.5
X-Auth-User: u2000070@giki.edu.pk
Received: from gandalf.resnet.giki.edu.pk (station210.pc-lab.giki.edu.pk [192.168.155.210])
	by giki.giki.edu.pk  with ESMTP id FAA23235
	for <ietf@ietf.org>; Sat, 4 Oct 2003 05:57:53 +0500
Received: from pakis (pakis.hostel6.resnet.giki.edu.pk [192.168.61.93])
	by gandalf.resnet.giki.edu.pk  with SMTP id h94153w25174
	for <ietf@ietf.org>; Sat, 4 Oct 2003 06:05:08 +0500
Message-ID: <020c01c38a15$7da7a170$5d3da8c0@hostel6.resnet.giki.edu.pk>
From: "M.Shoaib Khan" <u2000070@giki.edu.pk>
To: <ietf@ietf.org>
Subject: Fw: ZOOM... ZOOm... ZOom... Zoom... zoom....
Date: Sat, 4 Oct 2003 06:18:54 +0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



 how about having one draft for this  ;)







































**************************************************************
Scanned by  MailScan Anti-Virus and Content Security Software.
Visit http://www.mwti.net for more info on eScan and MailScan.
**************************************************************






From owner-ietf@ietf.org  Fri Oct  3 22:13:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07713
	for <ietf-web-archive@odin.ietf.org>; Fri, 3 Oct 2003 22:13:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5bnv-0007lc-4s
	for ietf-list@asgard.ietf.org; Fri, 03 Oct 2003 22:05:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5bnN-0007ih-LT
	for ietf@asgard.ietf.org; Fri, 03 Oct 2003 22:05:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07607
	for <ietf@ietf.org>; Fri, 3 Oct 2003 22:05:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5bnL-0001xS-00
	for ietf@ietf.org; Fri, 03 Oct 2003 22:05:19 -0400
Received: from mail9.speakeasy.net ([216.254.0.209] helo=mail.speakeasy.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5bnL-0001xP-00
	for ietf@ietf.org; Fri, 03 Oct 2003 22:05:19 -0400
Received: (qmail 26027 invoked from network); 4 Oct 2003 02:05:17 -0000
Received: from unknown (HELO speakeasy.net) ([66.92.168.196])
          (envelope-sender <dja2003@hotpop.com>)
          by mail9.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <inanbe@xs4all.nl>; 4 Oct 2003 02:05:17 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: "A. Kremer" <inanbe@xs4all.nl>, <ietf@ietf.org>
Subject: Re: Out of Office Reply & junkmail
Date: Fri, 3 Oct 2003 22:10:38 -0400
User-Agent: KMail/1.5
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAKl/PcBvLSEmzIII0yovh2cKAAAAQAAAA+41UdubEgUq9NzZyndQdSwEAAAAA@xs4all.nl>
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAKl/PcBvLSEmzIII0yovh2cKAAAAQAAAA+41UdubEgUq9NzZyndQdSwEAAAAA@xs4all.nl>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310032210.38258.dja2003@hotpop.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

"A. Kremer" <inanbe@xs4all.nl> wrote:

 > Is there any relationship between turning on an Out of Office Reply
 > and receiving a lot of junk/spammail?

Perhaps your replies verified your address to some spammers, who then 
quickly dumped more spam on you and sold your address?

-- 
Dave Aronson
"Work" web site:   http://destined.to/program
"Play" web site: http://listen.to/davearonson




From owner-ietf@ietf.org  Sat Oct  4 18:43:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17601
	for <ietf-web-archive@odin.ietf.org>; Sat, 4 Oct 2003 18:43:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5unX-0001lD-9I
	for ietf-list@asgard.ietf.org; Sat, 04 Oct 2003 18:22:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5unA-0001il-Jy
	for ietf@asgard.ietf.org; Sat, 04 Oct 2003 18:22:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17283
	for <ietf@ietf.org>; Sat, 4 Oct 2003 18:22:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5un8-0003fR-00
	for ietf@ietf.org; Sat, 04 Oct 2003 18:22:22 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5un8-0003fE-00
	for ietf@ietf.org; Sat, 04 Oct 2003 18:22:22 -0400
Received: from vista.av8.net (vista.av8.net [130.105.36.10])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id SAA28579;
	Sat, 4 Oct 2003 18:18:14 -0400
Date: Sat, 4 Oct 2003 18:18:13 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: "A. Kremer" <inanbe@xs4all.nl>
cc: ietf@ietf.org
Subject: Re: Out of Office Reply & junkmail
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAKl/PcBvLSEmzIII0yovh2cKAAAAQAAAA+41UdubEgUq9NzZyndQdSwEAAAAA@xs4all.nl>
Message-ID: <Pine.LNX.4.44.0310041802260.12154-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

The people who send much of such abuse are frequently those who are most
annoyed by out of office replies.

Real commercial spammers aren't "verifying your address". They already
have it. There is no market for verified email addresses. Only a specific
kind of non-commercial (ab)user wants a verified addresses. They are
typically mail administrators who do so by habit, because they don't like
bounces.  Spammers (if they actually used proxies and forged From:
addresses) don't get bounces.

For example, when Spews.org recently thought it was being criticized, it
signed up the person doing the criticism to 'about a thousand junk mail
lists' and began DDOS'ing their web site. (story posted on Politech)

What remains to be calculated is how many virus stables it takes to
account for all of the non-commercial spam.

If you really want to fight spam, you would get law enforcement prosecute
and jail more virus operators. This is already a felony in the US, and a
crime in many countries.  You don't need anything else.  Nor will anything
else solve the spam problem.

But I'm still waiting for California ISPs to start posting billions in
profits now that spam has been banned there. Billions have been removed
from their expenses, so where are the profits from that? I digress... Have
a good weekend.

		--Dean

On Sat, 4 Oct 2003, A. Kremer wrote:

> Ladies and gentlemen,
>
> Is there any relationship between turning on an Out of Office Reply and
> receiving a lot of junk/spammail?
>
> There is a reason why I ask you this..
>
> When I went for a 2 weeks holiday, I turned on my Out of Office Reply.
> After those 2 weeks, when I got back at the office, I had received
> 250(!) spammails. I guess it is unnecessary to mention the contents
> here. ;)
>
> A few weeks later I got ill and stayed home, so I was not able to turn
> on my Out of Office Reply.
> After my return at the office, I only had received 2 spammails.
>
> Then I had another holiday and I turned my Out of Office Reply on.
> And guess what happened!
> 169 spammails when I returned at the office. After being absent for 7
> working days.
>
> At that moment the thought crossed my mind that there MUST be any
> relationship between turning Out of Office Reply on, and receiving
> junk/spammail.
>
> So, am I right or am I wrong about this Out of Office issue?
>
> If there is already an answer to this question, please let me know where
> I can find it.
>
> Very kind regards,
>
> A. Kremer
>
>
>




From owner-ietf@ietf.org  Sat Oct  4 22:01:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21243
	for <ietf-web-archive@odin.ietf.org>; Sat, 4 Oct 2003 22:01:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5y2o-00028i-8h
	for ietf-list@asgard.ietf.org; Sat, 04 Oct 2003 21:50:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5y2h-000261-Kp
	for ietf@asgard.ietf.org; Sat, 04 Oct 2003 21:50:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21068
	for <ietf@ietf.org>; Sat, 4 Oct 2003 21:50:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5y2f-00058o-00
	for ietf@ietf.org; Sat, 04 Oct 2003 21:50:37 -0400
Received: from tx1.citynet.net ([66.118.64.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5y2f-00058l-00
	for ietf@ietf.org; Sat, 04 Oct 2003 21:50:37 -0400
Received: from a (dhcp-69-43-8-180.park.dialup.citynet.net [69.43.8.180])
	by tx1.citynet.net (8.12.10/8.12.6=Outbound) with SMTP id h951lO7t001333;
	Sat, 4 Oct 2003 21:47:25 -0400
Message-ID: <000601c38ae2$d8a2dd60$b4082b45@a>
From: "Bill Cunningham" <billc1@citynet.net>
To: "Dean Anderson" <dean@av8.com>
Cc: <ietf@ietf.org>
References: <Pine.LNX.4.44.0310041802260.12154-100000@vista.av8.net>
Subject: Re: Out of Office Reply & junkmail
Date: Sat, 4 Oct 2003 21:48:58 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> But I'm still waiting for California ISPs to start posting billions in
> profits now that spam has been banned there. Billions have been removed
> from their expenses, so where are the profits from that? I digress... Have
> a good weekend.
>
> --Dean
California has made spam illegal. What do they define spam? That should
really free up bandwidth.

    Bill





From owner-ietf@ietf.org  Sat Oct  4 22:36:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22034
	for <ietf-web-archive@odin.ietf.org>; Sat, 4 Oct 2003 22:36:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A5ygT-00048n-JU
	for ietf-list@asgard.ietf.org; Sat, 04 Oct 2003 22:31:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5yfp-00046M-Nh
	for ietf@asgard.ietf.org; Sat, 04 Oct 2003 22:31:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21906
	for <ietf@ietf.org>; Sat, 4 Oct 2003 22:30:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5yfn-0005Rq-00
	for ietf@ietf.org; Sat, 04 Oct 2003 22:31:03 -0400
Received: from ns1.vrx.net ([199.166.27.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5yfn-0005Rn-00
	for ietf@ietf.org; Sat, 04 Oct 2003 22:31:03 -0400
Received: from [192.168.1.14] (lsanca1-ar47-4-33-129-133.lsanca1.dsl-verizon.net [4.33.129.133])
	by ns1.vrx.net (Postfix) with ESMTP id 20AA5D445
	for <ietf@ietf.org>; Sat,  4 Oct 2003 22:30:58 -0400 (EDT)
Mime-Version: 1.0
X-Sender: stef@ns1.vrx.net
Message-Id: <v0422083abba5325d783a@[192.168.1.14]>
In-Reply-To: <000601c38ae2$d8a2dd60$b4082b45@a>
References: <Pine.LNX.4.44.0310041802260.12154-100000@vista.av8.net>
 <000601c38ae2$d8a2dd60$b4082b45@a>
Date: Sat, 4 Oct 2003 19:30:47 -0700
To: ietf@ietf.org
From: Einar Stefferud <Stef@nma.com>
Subject: Re: Out of Office Reply & junkmail
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

Yeah!  I can just hear those spammers quaking in the boots!...\Stef

At 21:48 -0400 10/4/03, Bill Cunningham wrote:
> > But I'm still waiting for California ISPs to start posting billions in
> > profits now that spam has been banned there. Billions have been removed
> > from their expenses, so where are the profits from that? I digress... Have
> > a good weekend.
> >
> > --Dean
>California has made spam illegal. What do they define spam? That should
>really free up bandwidth.
>
>    Bill




From owner-ietf@ietf.org  Sun Oct  5 06:59:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12592
	for <ietf-web-archive@odin.ietf.org>; Sun, 5 Oct 2003 06:59:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A66RO-000863-MB
	for ietf-list@asgard.ietf.org; Sun, 05 Oct 2003 06:48:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A66Qx-00084O-D3
	for ietf@asgard.ietf.org; Sun, 05 Oct 2003 06:48:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12344
	for <ietf@ietf.org>; Sun, 5 Oct 2003 06:48:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A66Qu-0000rA-00
	for ietf@ietf.org; Sun, 05 Oct 2003 06:48:12 -0400
Received: from web80601.mail.yahoo.com ([66.218.79.90])
	by ietf-mx with smtp (Exim 4.12)
	id 1A66Qt-0000qr-00
	for ietf@ietf.org; Sun, 05 Oct 2003 06:48:11 -0400
Message-ID: <20031005104742.33781.qmail@web80601.mail.yahoo.com>
Received: from [213.147.67.206] by web80601.mail.yahoo.com via HTTP; Sun, 05 Oct 2003 03:47:42 PDT
Date: Sun, 5 Oct 2003 03:47:42 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Re: IETF Storage Solution 
To: Valdis.Kletnieks@vt.edu, ietf@ietf.org
In-Reply-To: <200310031325.h93DPCqd015622@turing-police.cc.vt.edu>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-6381229-1065350862=:33023"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-6381229-1065350862=:33023
Content-Type: text/plain; charset=us-ascii

Ha Gotcha! Your knowledge of computers is wanting.  Magnetic harddisks can be scanned with laser for surface patterns arrangements,  I think your attacks on me are least professional.
 
Nyagudi Musandu

Valdis.Kletnieks@vt.edu wrote:
On Thu, 02 Oct 2003 22:40:46 PDT, NM Research said:

> Have the old hard disks read with use of laser and copied into new larger capacity hard disks.

> CAUTION: New hard disks must have the same hardware characteristics as the old ones to prevent OS malfunction ( special tailor-made hard disks ?? ).

This is totally nonsensical. You can't have the "same hardware characteristics"
and "larger capacity" at the same time.

> How do you think governments read stolen laptops?? With laser ofcourse!

Actually, if you've stolen a laptop, it's usually easier to just take the disk and
plug it into another machine and read it with the normal mechanisms.

And if you're doing data recovery because you were silly enough to steal a laptop
that had a physically broken disk drive, the usual hardware is magnetic-based
rather than laser-based.

This is even less IETF-relevant than your previous postings. Please read
the following two documents before posting to this list again:

http://www.ietf.org/tao.html (Also known as RFC3060)
http://www.ietf.org/internet-drafts/draft-mrose-ietf-posting-03.txt


> ATTACHMENT part 2 application/pgp-signature 


---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
--0-6381229-1065350862=:33023
Content-Type: text/html; charset=us-ascii

<DIV>Ha Gotcha! Your knowledge of computers is wanting.&nbsp; Magnetic harddisks can be scanned with laser for surface patterns arrangements,&nbsp; I think your attacks on me are least professional.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi Musandu<BR><BR><B><I>Valdis.Kletnieks@vt.edu</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">On Thu, 02 Oct 2003 22:40:46 PDT, NM Research <NM_RESEARCH@YAHOO.COM>said:<BR><BR>&gt; Have the old hard disks read with use of laser and copied into new larger capacity hard disks.<BR><BR>&gt; CAUTION: New hard disks must have the same hardware characteristics as the old ones to prevent OS malfunction ( special tailor-made hard disks ?? ).<BR><BR>This is totally nonsensical. You can't have the "same hardware characteristics"<BR>and "larger capacity" at the same time.<BR><BR>&gt; How do you think governments read stolen laptops?? With laser ofcourse!<BR><BR>Actually, if you've stolen a laptop, it's usually easier to just take the disk and<BR>plug it into another machine and read it with the normal mechanisms.<BR><BR>And if you're doing data recovery because you were silly enough to steal a laptop<BR>that had a physically broken disk drive, the usual hardware is
 magnetic-based<BR>rather than laser-based.<BR><BR>This is even less IETF-relevant than your previous postings. Please read<BR>the following two documents before posting to this list again:<BR><BR>http://www.ietf.org/tao.html (Also known as RFC3060)<BR>http://www.ietf.org/internet-drafts/draft-mrose-ietf-posting-03.txt<BR><BR><BR>&gt; ATTACHMENT part 2 application/pgp-signature <BR></BLOCKQUOTE><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://shopping.yahoo.com/?__yltc=s%3A150000443%2Cd%3A22708228%2Cslk%3Atext%2Csec%3Amail">The New Yahoo! Shopping</a> - with improved product search
--0-6381229-1065350862=:33023--



From owner-ietf@ietf.org  Sun Oct  5 06:59:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12605
	for <ietf-web-archive@odin.ietf.org>; Sun, 5 Oct 2003 06:59:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A66RO-00085x-A2
	for ietf-list@asgard.ietf.org; Sun, 05 Oct 2003 06:48:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A66QW-00084H-Ba
	for ietf@asgard.ietf.org; Sun, 05 Oct 2003 06:47:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12322
	for <ietf@ietf.org>; Sun, 5 Oct 2003 06:47:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A66QT-0000qw-00
	for ietf@ietf.org; Sun, 05 Oct 2003 06:47:45 -0400
Received: from web80601.mail.yahoo.com ([66.218.79.90])
	by ietf-mx with smtp (Exim 4.12)
	id 1A66QT-0000qk-00
	for ietf@ietf.org; Sun, 05 Oct 2003 06:47:45 -0400
Message-ID: <20031005104716.33680.qmail@web80601.mail.yahoo.com>
Received: from [213.147.67.206] by web80601.mail.yahoo.com via HTTP; Sun, 05 Oct 2003 03:47:16 PDT
Date: Sun, 5 Oct 2003 03:47:16 -0700 (PDT)
From: NM Research <nm_research@yahoo.com>
Subject: Re: IETF Storage Solution 
To: Valdis.Kletnieks@vt.edu, ietf@ietf.org
In-Reply-To: <200310031325.h93DPCqd015622@turing-police.cc.vt.edu>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-281181733-1065350836=:28010"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-281181733-1065350836=:28010
Content-Type: text/plain; charset=us-ascii

Ha Gotcha! Your knowledge of computers is wanting.  Magnetic harddisks can be scanned with laser for surface patterns arrangements,  I think your attacks on me are least professional.
 
Nyagudi Musandu

Valdis.Kletnieks@vt.edu wrote:
On Thu, 02 Oct 2003 22:40:46 PDT, NM Research said:

> Have the old hard disks read with use of laser and copied into new larger capacity hard disks.

> CAUTION: New hard disks must have the same hardware characteristics as the old ones to prevent OS malfunction ( special tailor-made hard disks ?? ).

This is totally nonsensical. You can't have the "same hardware characteristics"
and "larger capacity" at the same time.

> How do you think governments read stolen laptops?? With laser ofcourse!

Actually, if you've stolen a laptop, it's usually easier to just take the disk and
plug it into another machine and read it with the normal mechanisms.

And if you're doing data recovery because you were silly enough to steal a laptop
that had a physically broken disk drive, the usual hardware is magnetic-based
rather than laser-based.

This is even less IETF-relevant than your previous postings. Please read
the following two documents before posting to this list again:

http://www.ietf.org/tao.html (Also known as RFC3060)
http://www.ietf.org/internet-drafts/draft-mrose-ietf-posting-03.txt


> ATTACHMENT part 2 application/pgp-signature 


---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
--0-281181733-1065350836=:28010
Content-Type: text/html; charset=us-ascii

<DIV>Ha Gotcha! Your knowledge of computers is wanting.&nbsp; Magnetic harddisks can be scanned with laser for surface patterns arrangements,&nbsp; I think your attacks on me are least professional.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Nyagudi Musandu<BR><BR><B><I>Valdis.Kletnieks@vt.edu</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">On Thu, 02 Oct 2003 22:40:46 PDT, NM Research <NM_RESEARCH@YAHOO.COM>said:<BR><BR>&gt; Have the old hard disks read with use of laser and copied into new larger capacity hard disks.<BR><BR>&gt; CAUTION: New hard disks must have the same hardware characteristics as the old ones to prevent OS malfunction ( special tailor-made hard disks ?? ).<BR><BR>This is totally nonsensical. You can't have the "same hardware characteristics"<BR>and "larger capacity" at the same time.<BR><BR>&gt; How do you think governments read stolen laptops?? With laser ofcourse!<BR><BR>Actually, if you've stolen a laptop, it's usually easier to just take the disk and<BR>plug it into another machine and read it with the normal mechanisms.<BR><BR>And if you're doing data recovery because you were silly enough to steal a laptop<BR>that had a physically broken disk drive, the usual hardware is
 magnetic-based<BR>rather than laser-based.<BR><BR>This is even less IETF-relevant than your previous postings. Please read<BR>the following two documents before posting to this list again:<BR><BR>http://www.ietf.org/tao.html (Also known as RFC3060)<BR>http://www.ietf.org/internet-drafts/draft-mrose-ietf-posting-03.txt<BR><BR><BR>&gt; ATTACHMENT part 2 application/pgp-signature <BR></BLOCKQUOTE><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://shopping.yahoo.com/?__yltc=s%3A150000443%2Cd%3A22708228%2Cslk%3Atext%2Csec%3Amail">The New Yahoo! Shopping</a> - with improved product search
--0-281181733-1065350836=:28010--



From owner-ietf@ietf.org  Mon Oct  6 10:42:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04068
	for <ietf-web-archive@odin.ietf.org>; Mon, 6 Oct 2003 10:42:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A6WCx-00065x-KU
	for ietf-list@asgard.ietf.org; Mon, 06 Oct 2003 10:19:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A6WC6-00065e-Tg
	for ietf@asgard.ietf.org; Mon, 06 Oct 2003 10:18:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03096
	for <ietf@ietf.org>; Mon, 6 Oct 2003 10:18:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6WC5-0005yK-00
	for ietf@ietf.org; Mon, 06 Oct 2003 10:18:37 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6WC4-0005xr-00
	for ietf@ietf.org; Mon, 06 Oct 2003 10:18:37 -0400
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 8098261C0A; Mon,  6 Oct 2003 16:17:56 +0200 (CEST)
Date: Mon, 06 Oct 2003 00:20:26 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Meng Wang <mwang3@unity.ncsu.edu>, ietf@ietf.org
Subject: Re: About intrusion detection
Message-ID: <9043353.1065399626@localhost>
In-Reply-To: <Pine.GSO.4.58.0310030022430.15687@uni00du.unity.ncsu.edu>
References:  <Pine.GSO.4.58.0310030022430.15687@uni00du.unity.ncsu.edu>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

you might want to investigate the IDWG working group, which has been 
working on standardizing exchange formats for intrusion detection reports.

              Harald

--On 3. oktober 2003 00:23 -0400 Meng Wang <mwang3@unity.ncsu.edu> wrote:

> Hi,
>
>   Anyone can provide useful info such as URLs on intrusion detection?
> Is there any definition/description or summary on different kinds of
> intrusions?
>
>   Thanks.
> meng
>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which
> is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on
> what to pass are made solely by Raffaele D'Albenzio.
>
>







From owner-ietf@ietf.org  Mon Oct  6 12:32:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10406
	for <ietf-web-archive@odin.ietf.org>; Mon, 6 Oct 2003 12:32:14 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A6YCY-0003U8-RI
	for ietf-list@asgard.ietf.org; Mon, 06 Oct 2003 12:27:14 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A6YAy-0003Sb-I1
	for ietf@asgard.ietf.org; Mon, 06 Oct 2003 12:25:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10119
	for <ietf@ietf.org>; Mon, 6 Oct 2003 12:25:26 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6YAx-0000OQ-00
	for ietf@ietf.org; Mon, 06 Oct 2003 12:25:35 -0400
Received: from h80ad2558.async.vt.edu ([128.173.37.88] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6YAw-0000ON-00
	for ietf@ietf.org; Mon, 06 Oct 2003 12:25:34 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h96GPTCE024969;
	Mon, 6 Oct 2003 12:25:29 -0400
Message-Id: <200310061625.h96GPTCE024969@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: NM Research <nm_research@yahoo.com>
Cc: ietf@ietf.org
Subject: Re: IETF Storage Solution 
In-Reply-To: Your message of "Sun, 05 Oct 2003 03:47:16 PDT."
             <20031005104716.33680.qmail@web80601.mail.yahoo.com> 
References: <20031005104716.33680.qmail@web80601.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_94455250P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 06 Oct 2003 12:25:26 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sun, 05 Oct 2003 03:47:16 PDT, you said:

> Ha Gotcha! Your knowledge of computers is wanting.  Magnetic harddisks can be
> scanned with laser for surface patterns arrangements,  I think your attacks on
> me are least professional.

OK. Perhaps they *can* be scanned with lasers.  However, as far as I can tell,
most companies actually recovering data from magnetic media are using some
variant on a magnetic sensor, not a laser.

http://www.boulder.nist.gov/div816/2001/MagneticRecordingMeasurements/

See the section "New Technique for Recovering Data":

"Termed "second-harmonic magnetoresistive microscopy" (SH-MRM), this technique
makes use of high-resolution magnetic sensors developed for modern computer
hard-disk drives."

So as of 2 years ago, the research in the field was still using magnetic based
techniques, and of course the companies doing it for a living will be lagging
somewhat behind that.

Perhaps your confusion is based on a misunderstanding of the process:

http://www.usbyte.com/common/AFM_storage.htm

Yes, a small laser is used - to measure the deflection of a sensor by a magnetic field.

And I'm sorry that you find it unprofessional to be asked what your postings
have of interest *TO THE IETF*.  The 'I' stands for 'Internet'. Not nuclear
weapon, not nanotech, not disk storage, but *INTERNET*.  Unless you can show
how nuclear weapons, nanotech, disk storage, or whatever your next missive is
about is related *TO THE INTERNET*, it's off-topic for *THIS* list.


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

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

iD8DBQE/gZd2cC3lWbTT17ARAlxmAKDFhGICDUQ5+AuMGieMlTd+UgWjqgCeN8e3
FDunD0uEQfpdjdxawHytnbg=
=naAj
-----END PGP SIGNATURE-----

--==_Exmh_94455250P--



From owner-ietf@ietf.org  Mon Oct  6 12:47:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11322
	for <ietf-web-archive@odin.ietf.org>; Mon, 6 Oct 2003 12:47:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A6YQM-0004yX-UQ
	for ietf-list@asgard.ietf.org; Mon, 06 Oct 2003 12:41:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A6YQ2-0004xT-Is
	for ietf@asgard.ietf.org; Mon, 06 Oct 2003 12:41:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11083
	for <ietf@ietf.org>; Mon, 6 Oct 2003 12:41:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6YQ1-0000ek-00
	for ietf@ietf.org; Mon, 06 Oct 2003 12:41:09 -0400
Received: from adsl-66-137-237-100.dsl.rcsntx.swbell.net
	([66.137.237.100] helo=mail.frascone.com ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6YQ0-0000eg-00
	for ietf@ietf.org; Mon, 06 Oct 2003 12:41:08 -0400
Received: from localhost (wolverine [127.0.0.1])
	by mail.frascone.com (Postfix) with ESMTP
	id 1422458001A; Mon,  6 Oct 2003 11:41:08 -0500 (CDT)
Received: by mail.frascone.com (Postfix, from userid 500)
	id 21A5D58001C; Mon,  6 Oct 2003 11:41:07 -0500 (CDT)
Date: Mon, 6 Oct 2003 11:41:07 -0500
From: David Frascone <dave@frascone.com>
To: Valdis.Kletnieks@vt.edu
Cc: NM Research <nm_research@yahoo.com>, ietf@ietf.org
Subject: Re: IETF Storage Solution
Message-ID: <20031006164107.GE31520@frascone.com>
References: <20031005104716.33680.qmail@web80601.mail.yahoo.com> <200310061625.h96GPTCE024969@turing-police.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200310061625.h96GPTCE024969@turing-police.cc.vt.edu>
User-Agent: Mutt/1.3.28i
X-Virus-Scanned: by AMaViS 0.3.12 (frascone.com)
Sender: owner-ietf@ietf.org
Precedence: bulk

I've noticed that the diet commonly preferred by trolls includes made-up
jargon, insults, and paradoxes.  Responding with reason or legitimate
information leaves them craving more.

-Dave

On Monday, 06 Oct 2003, Valdis.Kletnieks@vt.edu wrote:
> On Sun, 05 Oct 2003 03:47:16 PDT, you said:
> 
> > Ha Gotcha! Your knowledge of computers is wanting.  Magnetic harddisks can be
> > scanned with laser for surface patterns arrangements,  I think your attacks on
> > me are least professional.
> 
> OK. Perhaps they *can* be scanned with lasers.  However, as far as I can tell,
> most companies actually recovering data from magnetic media are using some
> variant on a magnetic sensor, not a laser.
> 
> http://www.boulder.nist.gov/div816/2001/MagneticRecordingMeasurements/
> 
> See the section "New Technique for Recovering Data":
> 
> "Termed "second-harmonic magnetoresistive microscopy" (SH-MRM), this technique
> makes use of high-resolution magnetic sensors developed for modern computer
> hard-disk drives."
> 
> So as of 2 years ago, the research in the field was still using magnetic based
> techniques, and of course the companies doing it for a living will be lagging
> somewhat behind that.
> 
> Perhaps your confusion is based on a misunderstanding of the process:
> 
> http://www.usbyte.com/common/AFM_storage.htm
> 
> Yes, a small laser is used - to measure the deflection of a sensor by a magnetic field.
> 
> And I'm sorry that you find it unprofessional to be asked what your postings
> have of interest *TO THE IETF*.  The 'I' stands for 'Internet'. Not nuclear
> weapon, not nanotech, not disk storage, but *INTERNET*.  Unless you can show
> how nuclear weapons, nanotech, disk storage, or whatever your next missive is
> about is related *TO THE INTERNET*, it's off-topic for *THIS* list.
> 



-- 
David Frascone

                  Plan to be more spontaneous.



From owner-ietf@ietf.org  Tue Oct  7 16:06:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20237
	for <ietf-web-archive@odin.ietf.org>; Tue, 7 Oct 2003 16:06:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A6xsa-0000u1-7n
	for ietf-list@asgard.ietf.org; Tue, 07 Oct 2003 15:52:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A5z3D-0005UE-RE
	for ietf@asgard.ietf.org; Sat, 04 Oct 2003 22:55:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22452
	for <ietf@ietf.org>; Sat, 4 Oct 2003 22:55:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5z3B-0005et-00
	for ietf@ietf.org; Sat, 04 Oct 2003 22:55:13 -0400
Received: from smtp.sprintpcs.com ([63.167.114.16] helo=dedicated60-bos.wh.sprintip.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5z3B-0005eM-00
	for ietf@ietf.org; Sat, 04 Oct 2003 22:55:13 -0400
Received: from solidmatrix.com ([68.27.136.24])
 by dedicated60-bos.wh.sprintip.net
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTPA id <0HM9005FYK1GZC@dedicated60-bos.wh.sprintip.net> for
 ietf@ietf.org; Sun, 05 Oct 2003 02:53:44 +0000 (GMT)
Date: Sat, 04 Oct 2003 22:53:38 -0400
From: Yakov Shafranovich <research@solidmatrix.com>
Subject: [Fwd: [Asrg] 0. General - Verisign has suspended SiteFinder (fwd)]
To: ietf@ietf.org
Message-id: <3F7F87B2.20103@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4)
 Gecko/20030624
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

Below is an official notice from Verisign on when exactly
SiteFinder will be shut off (from the NANOG list). As of now, it appears
to have been killed.


-------- Original Message --------
Subject: [Asrg] 0. General - Verisign has suspended SiteFinder (fwd)
Date: Sat, 04 Oct 2003 21:26:59 -0400
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
To: ASRG list <asrg@ietf.org>

Below is the relevant list message from the NANOG mailing list:

> Date: Fri, 3 Oct 2003 17:50:02 -0400
> From: Matt Larson [address]
> To: nanog@nanog.org
> Subject: Removal of wildcard A records from .com and .net zones
> 
> VeriSign was directed by ICANN to suspend the Site Finder service by 0100 UTC on Sunday, October 5. We requested an extension from ICANN to give more notice to the community but were denied. We will be removing the wildcard A records from the .com and .net zones beginning at 2300 UTC on Saturday, October 4. The former behavior for these zones (returning Name Error/RCODE=3 in response to queries for nonexistent domain names) will be in place by 0100 UTC on Sunday, October. 
> 
> Matt
> --
> Matt Larson [address]
> VeriSign Naming and Directory Services



_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg










From owner-ietf@ietf.org  Thu Oct  9 18:46:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15423
	for <ietf-web-archive@odin.ietf.org>; Thu, 9 Oct 2003 18:46:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A7jGQ-000138-VQ
	for ietf-list@asgard.ietf.org; Thu, 09 Oct 2003 18:28:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7jGB-00011s-KQ
	for ietf@asgard.ietf.org; Thu, 09 Oct 2003 18:27:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14890
	for <ietf@ietf.org>; Thu, 9 Oct 2003 18:27:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7jG9-0005TO-00
	for ietf@ietf.org; Thu, 09 Oct 2003 18:27:49 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7jG8-0005Su-00
	for ietf@ietf.org; Thu, 09 Oct 2003 18:27:49 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h99MWtf23654;
	Thu, 9 Oct 2003 15:32:55 -0700
Date: Thu, 9 Oct 2003 15:27:13 -0700
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v2.00.22)
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <17261234170.20031009152713@brandenburg.com>
To: iesg@ietf.orgor.cnri.reston.va.us
CC: ietf@ietf.org
Subject: Comments on draft-irtf-nsrg-report-10.txt Last Call
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: base64

Rm9sa3MsDQoNCkFzIHRoZSBkaXNjdXNzaW9uIGFib3V0IGlkZW50aWZpZXJzIGhlYXRzIHVw
IGFyb3VuZCB0aGUgSUVURiwgSSd2ZSBiZWVuDQpmaW5kaW5nIHRoZSBOU1JHIGRyYWZ0IHZl
cnkgaGVscGZ1bC4gSXQncyBqb3VybmV5IHRocm91Z2ggdGhlIGlzc3VlcyBtYWtlcyBpdA0K
bW9yZSBkaWZmaWN1bHQgZm9yIHRoZSByZWFkZXIgdG8gbWlzcyBjb25jZXJucyB0aGF0IG5l
ZWQgdG8gYmUgdmlzaXRlZCBhbG9uZw0KdGhlIHdheS4gR2l2ZW4gdGhlIHJlbWFya2FibGUg
bnVtYmVyIG9mIElFVEYgZWZmb3J0cyB0aGF0IGN1cnJlbnRseSB0b3VjaCB0aGlzDQp0b3Bp
YywgaXQgc2hvdWxkIGJlIG5vIHNtYWxsIGJlbmVmaXQgdG8gaGF2ZSBhIGRvY3VtZW50IGxp
a2UgdGhpcywgdG8gYWRkIHNvbWUNCmRpc2NpcGxpbmUgdG8gdGhlIGRpc2N1c3Npb24uDQoN
CkkgdGhpbmsgaXQgaXMganVzdCBmaW5lIHRoYXQgdGhlIHBhcGVyIG1vc3RseSBkb2VzIG5v
dCBwcm9wb3NlIG9yICJ2b3RlIGZvciINCnNwZWNpZmljIHNvbHV0aW9ucy4gSG93ZXZlciwg
SSBzdWdnZXN0IHRoYXQgc29tZSBkZXRhaWwgYW5kIGRlcHRoIGJlIGFkZGVkIHRvDQpzb21l
IG9mIHRoZSBvcGluaW9ucyBvZmZlcmVkLCBwYXJ0aWN1bGFybHkgaW4gbGlnaHQgb2YgdGhl
IHJlY2VudCBldm9sdXRpb24gdG8NCmxvY2F0aW9uL2lkZW50aXR5IGFuZCBtdWx0aWFkZHJl
c3NpbmcgKG1vYmlsaXR5IGFuZCBtdWx0aWhvbWluZykgZGlzY3Vzc2lvbnMNCmluIHRoZSBJ
RVRGLg0KDQpJbiBnZW5lcmFsLCBhbnl0aW1lIHRoZSBkb2N1bWVudCBvZmZlcnMgYW4gb3Bp
bmlvbiwgaXQgc2hvdWxkIHRyeSB0byBleHBsYWluDQp0aGluZ3Mgc3VmZmljaWVudGx5IHNv
IHRoYXQgX3Vuc3ltcGF0aGV0aWNfIHJlYWRlcnMgYW5kIHJlYWRlcnMgdW5mYW1pbGlhcg0K
d2l0aCB0aGUgdG9waWMgY2FuIHNlZSB0aGUgc29saWQgYmFzaXMgZm9yIHRoZSBvcGluaW9u
LiBUaGUgZXh0cmEgcGVkYWdvZ3kNCndpbGwgYmUgZXh0cmVtZWx5IHVzZWZ1bC4NCg0KDQpT
cGVjaWZpYyBjb21tZW50czoNCg0KDQogICAgICAgIDEuMSBTZWN1cml0eSBDb25zaWRlcmF0
aW9ucw0KDQogICAgICAgIC4uLmJlY2F1c2UgYm90aCB0aGUgRE5TIGVudHJ5IGFuZCB0aGUg
SVAgYWRkcmVzcyBjYW4gY2hhbmdlLg0KDQpUaGVyZSBpcyBubyBzdWNoIHRoaW5nIGFzIHBl
cm1hbmVudC4gRXZlbiB0aGluZ3MgbGlrZSBNQUMgaWQncyBjYW4gYmUgc29mdC4gQnkNCm1v
c3QgSW50ZXJuZXQgbWVhc3VyZXMsIEROUyBlbnRyaWVzIGFyZSB2ZXJ5IGxvbmctbGl2ZWQu
IFNvIHRoZSBjb25jZXJuIHRoYXQgYQ0KRE5TIGVudHJ5IGNhbiBjaGFuZ2UgbmVlZHMgdG8g
YmUgZGlzY3Vzc2VkIGluIHRlcm1zIG9mIHByYWN0aWNhbCBhbHRlcm5hdGl2ZXMuDQooTXkg
Y29uY2VybiBpcyBub3QgYSBtYXR0ZXIgb2YgcHVyaXR5LiAgSSB0cnVseSBkbyBub3Qga25v
dyB3aGF0IHRoZSBkcmFmdA0KbWVhbnMuKQ0KDQpJZiB0aGUgTlNSRyBmb2xrcyB0aGluayB0
aGF0IHNvbWV0aGluZyBiZXR0ZXIgaXMgcG9zc2libGUsIHRoZWlyIGRvY3VtZW50DQpzaG91
bGQgZGVzY3JpYmUgdGhhdCBhbHRlcm5hdGl2ZSBjb25jcmV0ZWx5LiBQZXJzb25hbGx5LCBJ
IGNhbid0IGd1ZXNzIHdoYXQNCnRoYXQgd291bGQgYmUuIEFuZCBzaW5jZSBJJ3ZlIGJlY29t
ZSBhbiBhZHZvY2F0ZSBvZiB1c2luZyBkb21haW4gbmFtZXMgYXMNCmlkZW50aWZpZXJzLCBJ
J20gcGFydGljdWxhcmx5IGludGVyZXN0ZWQgaW4gaGVhcmluZyB0aGUgZGV0YWlscyBvZiB3
aGF0IHRoZQ0KTlNSRyBoYXMgaW4gbWluZC4NCg0KT25seSB0aGVuIGNhbiB0aGUgcmVhZGVy
IGV2YWx1YXRlIHRoYXQgYnJvYWQgY2xhaW0gaW4gdGhlIGRvY3VtZW50IHRoYXQgdGhlDQpJ
bnRlcm5ldCdzIGFyY2hpdGVjdHVyZSBoYXMgYSBzaG9ydGNvbWluZyBieSBub3QgaGF2aW5n
ICJwZXJzaXN0ZW50IiBuYW1lcy4NCg0KDQogICAgICAgICAgLi4uY29ubmVjdGlvbiBiZWlu
ZyBoaWphY2tlZC4uLg0KDQpQZWtrYSBOaWthbmRlciBoYXMgY2l0ZWQgYm90aCBoaWphY2tp
bmcgYW5kIGZsb29kaW5nIGFzIGV4cG9zdXJlcy4gTXkgc3VtbWFyeQ0Kb2YgaGlzIHBvaW50
IGlzOg0KDQogICAgICAgICAgSGlqYWNraW5nIGlzIGRpcmVjdGluZyB0cmFmZmljIHRvIG9u
ZXNlbGYuIEZsb29kaW5nIGlzIGRpcmVjdGluZw0KICAgICAgICAgIHRyYWZmaWMgdG8gc29t
ZW9uZSBlbHNlLiBPbmUgaXMgdG8gaW50ZXJjZXB0IGRhdGEgYW5kIHRoZSBvdGhlciBpcw0K
ICAgICAgICAgIHRvIG92ZXJsb2FkIGEgdmljdGltLiBCb3RoIHByb2JsZW1zIGFyZSBjcmVh
dGVkIGJ5IGJlaW5nIGFibGUgdG8gLi4uDQogICAgICAgICAgcmVkaXJlY3QgdHJhZmZpYyB0
byBhIG5ldyBhZGRyZXNzLg0KDQpJdCdzIGhlbHBmdWwgdG8gbWFrZSB0aGUgZGlzdGluY3Rp
b24gYmV0d2VlbiB0aGUgdHdvLg0KDQoNCiAgICAgICAgICAyLiBSZWxhdGVkIFdvcmsNCg0K
UGxlYXNlIGFkZCBkaXNjdXNzaW9uIGFib3V0IHRoZSBuZXcgYWx0ZXJuYXRpdmVzIHRoYXQg
aGF2ZSBwb3BwZWQgdXAuIFRDUC1NSCwNCk1BU1QgYW5kIExJTjYgYXJlIHRoZSB0aHJlZSBJ
IGNhbiB0aGluayBvZi4gIERDQ1AncyB0ZW50YXRpdmUgbXVsdGlob21pbmcNCnByb3Bvc2Fs
IHByb2JhYmx5IHF1YWxpZmllcyBpdCBmb3IgY29uc2lkZXJhdGlvbiwgdG9vLg0KDQpUbyB0
aGUgZXh0ZW50IHRoYXQgdGhlIE5TUkcgZmluZHMgaXQgaGVscGZ1bCwgdGhleSBtaWdodCB3
YW50IHRvIHRha2UgYSBsb29rIGF0Og0KDQogIDxodHRwOi8vd3d3LmlldGYub3JnL2ludGVy
bmV0LWRyYWZ0cy9kcmFmdC1jcm9ja2VyLW1hc3QtYW5hbHlzaXMtMDAudHh0Pg0KDQpJIHNw
bGl0IGl0IG9mZiBmcm9tIHRoZSBNQVNUIHByb3Bvc2FsLiBJdCBkaXNjdXNzZXMgYWxsIG9m
IHRoZSBhbHRlcm5hdGl2ZQ0Kc3BlY2lmaWNhdGlvbnMuIEkgYW0gYWxzbyB3b3JraW5nIG9u
IHNvbWUgdGFibGVzIHRoYXQgY29tcGFyZSB0aGUgZGlmZmVyZW50DQpwcm9wb3NhbHMsIGJ1
dCBwcm9ncmVzcyBvbiBpdCBpcyBzbG93Lg0KDQoNCiAgICAgICAgICAgMi4zIEhJUA0KDQog
ICAgICAgICAgIC4uLnJlZHVjZWQgYWRtaW5pc3RyYXRpb24uIEEgdHlwaWNhbCBhY2Nlc3Mg
bGlzdCB1c2VkIG9uIHRoZQ0KICAgICAgICAgICBJbnRlcm5ldC4uLg0KDQpUaGUgcGFwZXIg
aXMgZW50aXJlbHkgdG9vIGNhc3VhbCBhYm91dCBjaXRpbmcgYWNjZXNzIGNvbnRyb2wgbGlz
dCBhZ2dyZWdhdGlvbi4NCkl0IGltcGxpZXMgdGhhdCB0aGlzIGlzIG1lcmVseSBhbiBlbmNv
ZGluZyBpc3N1ZSB0aGF0IGlzIGh1cnQgYnkgSElQJ3MgdXNlIG9mDQphIGhhc2guDQoNCkhv
d2V2ZXIgdGhlIGVudGlyZSBjb25jZXB0IG9mIHNlZWtpbmcgYWdncmVnYXRpb24gaGluZ2Vz
IG9uIHRoZSBuYXR1cmUgb2YgdGhlDQpzdHJpbmcgYWRtaW5pc3RyYXRpb24uIEluZGVwZW5k
ZW50IG9mIHRoZSAic3ludGFjdGljIiBpc3N1ZSB0aGF0IGlzIGRlZmVhdGVkDQpieSBzb21l
dGhpbmcgbGlrZSBoYXNoaW5nLCBpdCBpcyBvbmx5IHVzZWZ1bCB0byBhZ2dyZWdhdGUgYSBj
b250cm9sIGxpc3QgaWYNCnRoZSB0aGluZ3MgYmVpbmcgYWdncmVnYXRlZCBoYXZlIHRoZSBy
aWdodCBwcm9wZXJ0aWVzIGluIGNvbW1vbiBBTkQgdGhlDQpwcm9wZXJ0aWVzIGFyZSByZWZs
ZWN0ZWQgaW4gdGhlIG5hbWUuIFNvLCBmb3IgZXhhbXBsZSwgYWdncmVnYXRpbmcNCnRvcG9s
b2dpY2FsbHktcmVsYXRlZCBuYW1lcyBtYWtlcyBzZW5zZSwgaWYgdG9wb2xvZ3kgaXMgdGhl
IGNvbmNlcm4uIEZvcg0KZG9tYWluIG5hbWVzLCB0aGUgcHJvcGVydHkgaW4gY29tbW9uIGlz
IGFkbWluaXN0cmF0aXZlIGF1dGhvcml0eS4gSXMgdGhhdCB0aGUNCnJpZ2h0IHByb3BlcnR5
IGZvciBhbiBhY2Nlc3MgbGlzdCB0byBhZ2dyZWdhdGUgb24/IE9mIGNvdXJzZSwgdGhlIGFu
c3dlciBpcw0KdGhhdCBpdCBkZXBlbmRzLiBBbmQgdGhlIHBhcGVyIHNob3VsZCBjaXRlIHRo
aXMuDQoNCkFsc28gdGhpcyBpc3N1ZSBvZiBsaXN0IGFnZ3JlZ2F0aW9uIGlzIG9mIGdlbmVy
YWwgaW50ZXJlc3QgYW5kIHNob3VsZCBub3QgYmUNCmJ1cmllZCBpbiB0aGUgZGlzY3Vzc2lv
biBvZiBhIHBhcnRpY3VsYXIgYWx0ZXJuYXRpdmUuDQoNCg0KICAgICAgICAgICAzLiBEaXNj
dXNzaW9uDQoNCiAgICAgICAgICAgLi4uRXhhbXBsZXMgb2YgYW4gZW50aXR5IGluY2x1ZGUu
Li4NCg0KSG93IGlzIGEgInNlcnZpY2UiIGRpZmZlcmVudCBmcm9tIGEgImNvbW11bmljYXRp
bmcgZW50aXR5Ij8gUGVyaGFwcyBJJ20gbm90DQp1bmRlcnN0YW5kaW5nIHdoYXQgdGhlIE5T
UkcgbWVhbnMgYnkgInNlcnZpY2UiLg0KDQpJbiBhbnkgZXZlbnQsIGxldCBtZSBzdWdnZXN0
IHRoYXQgYW4gYXJjaGl0ZWN0dXJhbCBkaXNjdXNzaW9uIGxpa2UgdGhpcyBzaG91bGQNCm5v
dCBqdXN0IG9mZmVyIGV4YW1wbGVzLCBidXQgc2hvdWxkIGV4cGxpY2l0bHkgbGlzdCB0aGUg
ZnVsbCBzZXQgb2YNCmFsdGVybmF0aXZlcy4gVGhpcyBuZWVkcyB0byBpbmNsdWRlIGludGVy
ZmFjZXMsIGZvciBleGFtcGxlLiAoSWYgdGhlIE5TUkcNCm1lYW50ICJzdGFjayIgdG8gY292
ZXIgaW50ZXJmYWNlcywgYXMgd2VsbCBhcyBsb2dpY2FsIHByb3RvY29sIHN0YWNrcywgdGhl
bg0KdGhleSBuZWVkIHRvIG1ha2UgdGhpcyBjbGVhci4gSG93ZXZlciwgYXJlIHNob3VsZCBh
IHN0YWNrIGJlIGFibGUgdG8gaGF2ZSBvbmx5DQpvbmUgaW50ZXJmYWNlPykNCg0KSSBiZWxp
ZXZlIG11Y2ggb2YgdGhlIGRlYmF0ZSBvbiBjaG9vc2luZyBhIHR5cGUgb2YgaWRlbnRpZmll
ciBoaW5nZXMgb24gaXRzDQphcmNoaXRlY3R1cmFsIHBsYWNlbWVudC4gU28sIGl0J3MgcXVp
dGUgbmljZSB0aGF0IHRoZSBOU1JHIHBhcGVyIGhhcyB0aGlzIERpc2N1c3Npb24NCnNlY3Rp
b24sIGJ1dCBJIHRoaW5rIGl0IG5lZWRzIHRvIGJlIG1vcmUgcGVkYW50aWMgLS0gb3IsIHJh
dGhlciwgcGVkYWdvZ2ljYWwgLS0NCmFib3V0IGxpc3RpbmcgYW5kIGNvbnNpZGVyaW5nIHRo
ZSBjaG9pY2VzLg0KDQoNCiAgICAgICAgICAzLjEgUmVxdWlyZW1lbnRzDQoNCiAgICAgICAg
ICAiU3RhY2sgbmFtZXMgYXJlIGRlZmluZWQgdG8gYmUgYSBuZXcgbmFtaW5nIHN0cnVjdHVy
ZS4uLiINCg0KSXQgaXMgYSBiaXQgc3RyYW5nZSB0byBoYXZlIHRoZSB0ZXJtICJzdGFjayIg
ZGVmaW5lZCBjb25zaWRlcmFibHkgYWZ0ZXIgaXQgaGFzDQpiZWVuIHVzZWQuDQoNCk1vcmUg
aW1wb3J0YW50bHksIGl0IGNhbGxzIGZvciBhIG5ldyBzdHJpbmcgYW5kIGF1dG9tYXRpY2Fs
bHkgZXhjbHVkZXMgYW55DQpleGlzdGluZyBjaG9pY2VzLiBJZiB0aGF0J3Mgbm90IHdoYXQg
dGhlIE5TUkcgbWVhbnQsIHRoZXkgbWlnaHQgd2FudCB0byB1c2UgcGhyYXNpbmcNCmRpZmZl
cmVudCBmcm9tICJuZXcgbmFtaW5nIHN0cnVjdHVyZSIuIFBlcmhhcHMgIm5ldyBuYW1pbmcg
Y29uc3RydWN0IiB3aXRoIGFuDQpleHBsaWNpdCBub3RlIHRoYXQgaXQgaW5jbHVkZXMgZXhp
c3RpbmcgbmFtZXMsIHN1Y2ggYXMgSVAgYWRkcmVzc2VzIGFuZCBkb21haW4NCm5hbWVzPyBF
eGlzdGluZyBjaG9pY2VzIG1pZ2h0IHdlbGwgYmUgc3VmZmljaWVudCwgaWYgdGhleSBjb3Zl
ciB0aGUgcmlnaHQNCnBsYWNlIGluIHRoZSBzdGFjayBhbmQgaGF2ZSB0aGUgbmVjZXNzYXJ5
IG90aGVyIHByb3BlcnRpZXMuIFNvIHRoZSB0ZXh0IHNob3VsZA0Kbm90IGltcGx5IHRoYXQg
YSBuZXcgc3RyaW5nIGlzIHJlcXVpcmVkLg0KDQpJZiwgb24gdGhlIG90aGVyIGhhbmQsIHRo
ZSBOU1JHIHJlYWxseSBkaWQgbWVhbiB0byBpbnNpc3QgdGhhdCBhIG5ldyBzdHJpbmcgaXMN
CnJlcXVpcmVkLCB0aGVuIHRoZSBwYXBlciBpcyB0YWtpbmcgYSBwb3NpdGlvbiBmb3Igd2hp
Y2ggdGhlcmUgaXMgaW5zdWZmaWNpZW50DQpyZXF1aXJlbWVudHMgc3VwcG9ydC4gQXQgdGhl
IGxlYXN0LCB0aGUgTlNSRyBuZWVkcyB0byBkbyBhIG11Y2ggbW9yZSB0aG9yb3VnaA0Kam9i
IG9mIGV4cGxhaW5pbmcgd2h5IGV4aXN0aW5nIGNob2ljZXMgYXJlIGFic29sdXRlbHkgdW5h
Y2NlcHRhYmxlLg0KDQpNeSBvd24gZWZmb3J0cyB0byBnZXQganVzdCB0aGlzIHNvcnQgb2Yg
ZXhwbGFuYXRpb24sIG9uIHNldmVyYWwgbWFpbGluZyBsaXN0cywNCmhhcyBiZWVuIG9kZGx5
IHVucHJvZHVjdGl2ZSwgYWx0aG91Z2ggc29tZSBvZmZsaW5lIGRpc2N1c3Npb25zIGFyZSBt
YWtpbmcNCnByb2dyZXNzLiBJIGdldCB0aGUgc2Vuc2Ugb2YgdW5kZXJseWluZyByZWxpZ2lv
biBkcml2aW5nIHRoaW5ncyBtb3JlIHRoYW4NCmZ1bmN0aW9uYWwgcmVxdWlyZW1lbnRzLCBv
ciBhdCBsZWFzdCBvZiBmdW5jdGlvbmFsIHJlcXVpcmVtZW50cyB0aGF0IGFyZSBzbw0KYWJz
dHJhY3QsIGZvbGtzIGRvIG5vdCBoYXZlIGEgc3VmZmljaWVudGx5IGNvbmNyZXRlIHNlbnNl
IG9mIHVzYWdlLiBTbyBteQ0KcmVxdWVzdCB0byBmb3IgdGhlc2UgZW5oYW5jZW1lbnRzIHRv
IHRoZSBOU1JHIHBhcGVyIHJlYWxseSBpcyBhIHBsZWEuDQoNCkJ5IHRoZSB3YXksIHRoZSBi
dWxsZXRlZCBsaXN0IGF0IHRoZSBlbmQgb2YgdGhlIHNlY3Rpb24gaXMgYSBnb29kIHN1bW1h
cnkgb2YNCnRoZSBjb25jZXB0dWFsIGNvbmNlcm5zLg0KDQoNCiAgICAgICAgICAgMy4yLjIg
U3RhdGlzdGljYWwNCg0KVGhpcyBzZWN0aW9uIDMuMiBpcyBhbiBleGNlbGxlbnQgZ3VpZGUg
dG8gbmFtZSBhcmNoaXRlY3RzLg0KDQoNCiAgICAgICAgICAgLi4uc3VjaCBkZWxlZ2F0aW9u
IGludHJvZHVjZXMgb3ZlcmhlYWQuLi4NCg0KVGhpcyBzZWN0aW9uIGFwcGxpZXMgdG8gSVAg
YWRkcmVzc2VzLCBhcyB3ZWxsIGFzIGRvbWFpbiBuYW1lcywgc28gdGhlDQpkaXNjdXNzaW9u
IG5lZWRzIHRvIGJlIG11Y2ggbW9yZSBjb25zdHJhaW5lZCBpbiBsaXN0aW5nIHByb2JsZW1z
LiBGb3IgZXhhbXBsZSwNCnNvbHV0aW9ucyB0aGF0IGhhdmUgbm8gbGluZ3Vpc3RpYy9zZW1h
bnRpYyBxdWFsaXR5IHRvIHRoZW0gYXJlIG5vdCBsaWtlbHkgdG8NCnJ1biBpbnRvIHNlcmlv
dXMgdHJhZGVtYXJrIGNvbmNlcm5zLg0KDQpGcmFua2x5IEkgdGhpbmsgdGhlIHJlZmVyZW5j
ZSB0byBkb21haW4gc3F1YXR0aW5nIGlzIGJvZ3VzLiAgRG9tYWluIHNxdWF0dGluZw0KaXMg
YSBoYXNzbGUsIGJ1dCBkb2VzIG5vdCBzZWVtIHRvIGJlIGEgbWFqb3IgaXNzdWUgaW4gdGhl
IHVzZSBvZiBkb21haW4gbmFtZXMsDQp0aGVzZSBkYXlzLg0KDQoNCiAgICAgICAgICAzLjIu
MyBNYXBwaW5nDQoNCiAgICAgICAgICBBIG5hbWUgb24gaXRzIG93biBpcyBvZiB2ZXJ5IGxp
bWl0ZWQgdmFsdWUuDQoNCk9uIHRoZSBjb250cmFyeSwgdGhlIHNpbXBsZSBmYWN0IG9mIGEg
c3RyaW5nJ3MgdW5pcXVlbmVzcyBjYW4gYmUgZXh0cmVtZWx5DQpoZWxwZnVsLCBpbiBhIHN1
ZmZpY2llbnRseSBjb25zdHJhaW5lZCBjb250ZXh0LCBldmVuIHdoZW4gdGhlcmUgaXMgbm8g
bWFwcGluZy4NClRoZSBjb250ZXh0IG5vbmNlIGxhYmVscyB0aGF0IGFyZSB1c2VkIGluIFBQ
SywgU0NUUCBhbmQgTUFTVCBkbyBub3QgcmVhbGx5DQpoYXZlIGFueSAibWFwcGluZyIgb3Ro
ZXIgdGhhbiBiZWluZyB1bmlxdWUuDQoNCg0KICAgICAgICAgIFVzYWdlDQoNClRoaXMgaXMg
YSBkaXNjdXNzaW9uIHRoYXQgc2VlbXMgdG8gYmUgbWlzc2luZyBmcm9tIHRoZSBzZWN0aW9u
LCB5ZXQgZXZlcnl0aGluZw0KaGluZ2VzIG9uIGl0LiBIb3cgd2lsbCBhIG5hbWUgZ2V0IHVz
ZWQ/IEZvciBleGFtcGxlIGFzIHRoZSBwYXBlciBub3Rlcywgb25lDQppbXBvcnRhbnQgcXVl
c3Rpb24gaXMgd2hldGhlciB0aGUgbmFtZSBuZWVkcyB0byBiZSBpbiBldmVyeSBwYWNrZXQ/
DQoNClRoaXMgb25lIHBvaW50IGhhcyBtYXNzaXZlIGltcGFjdCBvbiB0aGUgZGVzaWduIGNo
b2ljZSwgb2YgY291cnNlLg0KDQpJIGJlbGlldmUgYSBmYWlsaW5nIGluIHRoZSBjb21tdW5p
dHkgZGlzY3Vzc2lvbiBhYm91dCBpZGVudGlmaWVycyBpcyB0aGF0IGl0DQppcyBjb25kdWN0
ZWQgdG9vIG11Y2ggaW4gdGhlIGFic3RyYWN0IHdpdGggdG9vIGxpdHRsZSBjb25zaWRlcmF0
aW9uIG9mIHRoZQ0KYWN0dWFsIHVzYWdlIHJlcXVpcmVtZW50cy4gQ29uc2VxdWVudGx5IHBl
b3BsZSBhcmUgbm90IHRoaW5raW5nIHZlcnkgaGFyZA0KYWJvdXQgdHJhZGUtb2ZmcyBhbW9u
ZyB0aGUgYWx0ZXJuYXRpdmVzLg0KDQpUaGUgcGFwZXIgcHJlc2VudHMgaXNzdWVzIGluIHRl
cm1zIG9mIGEga2luZCBvZiB0YXhvbm9teS4gVGhpcyBpcyBxdWl0ZQ0KdXNlZnVsLCBidXQg
b25seSBhZnRlciB0aGVyZSBpcyBhIGJyb2FkZXIgY29udGV4dCBmb3IgZGlzY3Vzc2luZyB1
c2FnZSwgc2luY2UNCml0IGlzIHRoZSB1c2FnZSB0aGF0IGRyaXZlcyB0aGUgcmVxdWlyZW1l
bnRzLiBPbmx5IHdoZW4gdGhlIHJlcXVpcmVtZW50cyBhcmUNCm1vcmUgY2xlYXIgY2FuIHRo
ZSBkZXNpZ24gY2hvaWNlcyBiZSBtYWRlIGZyb20gdGhlIHRheG9ub21pYyBtZW51IHRoYXQg
eW91DQpwcmVzZW50Lg0KDQoNCiAgICAgICAgSW5mcmFzdHJ1Y3R1cmUNCg0KVGhpcyBpcyBh
bm90aGVyIGRpc2N1c3Npb24gdGhhdCB3b3VsZCBiZSBoZWxwZnVsIHRvIGFkZC4gVGhlIHBh
cGVyIHRvdWNoZXMgb24NCml0IGluIG1hbnkgcGxhY2VzLCBhbmQgY2VydGFpbmx5IHRoZSBw
YXBlciBpbXBsaWVzIGl0cyBpbXBvcnRhbmNlLCBidXQgSSB0aGluaw0KdGhhdCBpdCBpcyBu
b3QgcHJlc2VudGVkIGFzIGEgY29oZXJlbnQgZGVzaWduIHBvaW50Lg0KDQpUaGUgcXVlc3Rp
b24gaXMgd2hhdCBhZG1pbmlzdHJhdGl2ZSBhbmQgb3BlcmF0aW9uYWwgaW5mcmFzdHJ1Y3R1
cmVzIGFyZSBuZWVkZWQNCmZvciB0aGUgaWRlbnRpZmllcj8gKEFuZCwgb2YgY291cnNlLCB3
aHk/KSBBZ2FpbiwgbXkgc2Vuc2l0aXZpdHkgYWJvdXQgdGhpcw0KY29tZXMgZnJvbSBzZWVp
bmcgYSBsYWNrIG9mIGNvbnNpZGVyYXRpb24gZm9yIGl0IGluIHRoZSBjb21tdW5pdHkgZGlz
Y3Vzc2lvbnMuDQoNCg0KICAgICAgICAzLjUgSXMgYW4gYXJjaGl0ZWN0dXJhbCBjaGFuZ2Ug
bmVlZGVkDQoNCiAgICAgICAgLi4uIE1vYmlsZSBJUCB3aWxsIGNvdmVyIGFueSBwZXJjZWl2
ZWQgbmVlZC4uLg0KDQpUaGlzIHN0YXRlbWVudCBpcyBhIGdvb2QgZXhhbXBsZSBvZiBtaXNz
aW5nIHRoZSBpbmZyYXN0cnVjdHVyZSBmYWN0b3IuIE1vYmlsZQ0KSVAgdGFrZXMgYSBzaWdu
aWZpY2FudCBpbmZyYXN0cnVjdHVyZSBoaXQuIE5vdGUsIGZvciBleGFtcGxlIHRoYXQgdGhl
IE1JUA0KZWZmb3J0IGhhcyBiZWVuIHVuZGVyd2F5IGZvciBhIHZlcnkgbG9uZyB0aW1lIGFu
ZCBoYXMsIHNvIGZhciwgYWNoaWV2ZWQNCmVzc2VudGlhbGx5IG5vIG1hcmtldCBwZW5ldHJh
dGlvbi4NCg0KRnVydGhlciwgYXBwcm9hY2hlcyBsaWtlIFRDUC1NSCBhbmQgU0NUUCBzaG93
IHRoYXQgc2ltaWxhciBmdW5jdGlvbmFsaXR5IGNhbg0KYmUgYWNoaWV2ZWQgdGhyb3VnaCBh
IHZlcnkgZGlmZmVyZW50IGFwcHJvYWNoIHRoYXQgaGFzIG5vIGluZnJhc3RydWN0dXJlDQpv
dmVyaGVhZC4gTm8sIG5vdCB0aGUgc2FtZSBhcyBNSVAuIFRhcmdldCAoaWUsIFNlcnZlcikg
TW9iaWxpdHkgcmVxdWlyZXMgc29tZQ0Kc29ydCBvZiAzcmQgcGFydHkgcmVmZXJlbmNlIHNl
cnZpY2UuIEhvd2V2ZXIgSW5pdGlhdG9yIChpZSwgQ2xpZW50KSBNb2JpbGl0eQ0KZG9lcyBu
b3QuDQoNCkkgc3Ryb25nbHkgZW5jb3VyYWdlIHRoYXQgdGhlIHBhcGVyIGF2b2lkIHRha2lu
ZyBNSVAgYXMgYSBnaXZlbi4NCg0KVG8gY29uY2x1ZGUsIEknbGwgcmVwZWF0IG15IHRoYW5r
cyBmb3IgdGhlIE5TUkcgcGFwZXIuIEFsdGhvdWdoIEkgaGF2ZSBteSBvd24NCmJpYXNlcyBh
Ym91dCB0aGUgcmlnaHQgY2hvaWNlcyBmb3IgdGhpcyB0b3BpYywgSSBhbSBtb3JlIGNvbmNl
cm5lZCB0aGF0DQpkaXNjdXNzaW9uIGFib3V0IGNob2ljZXMgYmUgY2FyZWZ1bGx5IHJlYXNv
bmVkIGFuZCBhcHByb3ByaWF0ZWx5IGNvbmNyZXRlLg0KRnJvbSB3aGF0IEkgaGF2ZSBzZWVu
LCB0aGlzIGhhcyBub3QgYmVlbiBoYXBwZW5pbmcuIHRoZSBOU1JHIHBhcGVyIGNhbiBiZQ0K
ZXh0cmVtZWx5IGhlbHBmdWwgaW4gZm9jdXNpbmcgZGlzY3Vzc2lvbiB0byBiZSBsZXNzIHJl
bGlnaW91cyBhbmQgbW9yZQ0KZnVuY3Rpb25hbC4NCg0KZC8NCi0tDQogRGF2ZSBDcm9ja2Vy
IDxkY3JvY2tlci1hdC1icmFuZGVuYnVyZy1kb3QtY29tPg0KIEJyYW5kZW5idXJnIEludGVy
bmV0V29ya2luZyA8d3d3LmJyYW5kZW5idXJnLmNvbT4NCiBTdW5ueXZhbGUsIENBICBVU0Eg
PHRlbDorMS40MDguMjQ2LjgyNTM+DQoNCg==




From owner-ietf@ietf.org  Thu Oct  9 22:14:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21055
	for <ietf-web-archive@odin.ietf.org>; Thu, 9 Oct 2003 22:14:22 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A7mYZ-0007BG-Mf
	for ietf-list@asgard.ietf.org; Thu, 09 Oct 2003 21:59:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7mY5-00079t-Pw
	for ietf@asgard.ietf.org; Thu, 09 Oct 2003 21:58:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20627;
	Thu, 9 Oct 2003 21:58:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7mY3-0007bi-00; Thu, 09 Oct 2003 21:58:31 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7mY3-0007al-00; Thu, 09 Oct 2003 21:58:31 -0400
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 4393E61BA7; Fri, 10 Oct 2003 03:57:57 +0200 (CEST)
Date: Fri, 10 Oct 2003 03:54:08 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Tony Hain <alh-ietf@tndh.net>, IAB <iab@iab.org>
Cc: The IESG <iesg@ietf.org>, ipv6@ietf.org, IETF <ietf@ietf.org>
Subject: Re: Appeal to the IAB on the site-local issue
Message-ID: <53402438.1065758048@localhost>
In-Reply-To: <IKEDILMOGFKPCDJAMFKKKEAOCMAA.alh-ietf@tndh.net>
References:  <IKEDILMOGFKPCDJAMFKKKEAOCMAA.alh-ietf@tndh.net>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony,

speaking only for myself:

I am saddened to see the length to which you are willing to go in 
attempting to use process mechanisms to overturn a technical WG decision to 
which you do not agree.

After reviewing the video, I personally concluded that *no matter what the 
merits of the case*, the WG had clearly made a decision. My judgment of the 
the form of the discussion was that it was an informed one; my judgment of 
the arguments raised was that it was a correct one.

But there's absolutely no doubt in my mind that the WG made a decision, and 
that the chairs were procedurally correct in recording that decision as the 
outcome of the meeting.

That is, after all, what you claimed to be appealing.

                            Harald


--On 9. oktober 2003 16:59 -0700 Tony Hain <alh-ietf@tndh.net> wrote:

> I am saddened that it has come to this, but the IESG action has simply
> prolonged the process. The only clarity in their '...somewhere to the
> left...' justification is their willingness to let personal technical
> biases blind them to the process failure. As such, please consider this
> note to be an appeal to the IAB against the IESG decision to reject my
> appeal.







From owner-ietf@ietf.org  Thu Oct  9 22:22:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21493
	for <ietf-web-archive@odin.ietf.org>; Thu, 9 Oct 2003 22:22:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A7mo3-0007dp-GB
	for ietf-list@asgard.ietf.org; Thu, 09 Oct 2003 22:15:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7mnc-0007aI-UK
	for ietf@asgard.ietf.org; Thu, 09 Oct 2003 22:14:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21075;
	Thu, 9 Oct 2003 22:14:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7mna-0007kv-00; Thu, 09 Oct 2003 22:14:34 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7mna-0007kW-00; Thu, 09 Oct 2003 22:14:34 -0400
Subject: RE: Appeal to the IAB on the site-local issue
Date: Thu, 9 Oct 2003 19:14:02 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C604@server2003.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Appeal to the IAB on the site-local issue
thread-index: AcOO0oAdTcnqwDyrQWqgZCxFUMDlWQAAMnfg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        "Tony Hain" <alh-ietf@tndh.net>, "IAB" <iab@iab.org>
Cc: "The IESG" <iesg@ietf.org>, <ipv6@ietf.org>, "IETF" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Harald,

> Harald Tveit Alvestrand
> But there's absolutely no doubt in my mind that the WG made a
> decision, and that the chairs were procedurally correct in
> recording that decision as the outcome of the meeting.

There many people, including some that actually _wrote_ the procedures,
that disagree with you. As of myself, I am not completely happy with the
way Tony has worded his appeal (although I do agree with it), which is
why I will file one on different grounds as soon as this one as been
ruled. Since it appears that there is a waiting list to file an appeal
on this matter, I am sure that we will be entertained for the next two
or three years to come.

Michel.




From owner-ietf@ietf.org  Fri Oct 10 01:28:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26554
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 01:28:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A7paJ-0004RG-7q
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 01:13:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7pZY-0004Pm-LC
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 01:12:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25856;
	Fri, 10 Oct 2003 01:12:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7pZV-0001gj-00; Fri, 10 Oct 2003 01:12:13 -0400
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7pZV-0001gH-00; Fri, 10 Oct 2003 01:12:13 -0400
Received: from inet-vrs-04.redmond.corp.microsoft.com ([157.54.8.149]) by mail4.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 9 Oct 2003 22:11:42 -0700
Received: from 157.54.8.109 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 09 Oct 2003 22:11:42 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 9 Oct 2003 22:11:42 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 9 Oct 2003 22:11:40 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Thu, 9 Oct 2003 22:11:40 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Appeal to the IAB on the site-local issue
Date: Thu, 9 Oct 2003 22:11:40 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA05947B69@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Appeal to the IAB on the site-local issue
thread-index: AcOO0oAdTcnqwDyrQWqgZCxFUMDlWQAAMnfgAAXCpnA=
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>,
        "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        "Tony Hain" <alh-ietf@tndh.net>, "IAB" <iab@iab.org>
Cc: "The IESG" <iesg@ietf.org>, <ipv6@ietf.org>, "IETF" <ietf@ietf.org>
X-OriginalArrivalTime: 10 Oct 2003 05:11:40.0522 (UTC) FILETIME=[FD09F4A0:01C38EEC]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> > Harald Tveit Alvestrand
> > But there's absolutely no doubt in my mind that the WG made a
> > decision, and that the chairs were procedurally correct in
> > recording that decision as the outcome of the meeting.
>=20
> There many people, including some that actually _wrote_ the
procedures,
> that disagree with you.=20

Please explain or retract. I was the note-taker during that particular
session, and I don't recall ever stating that the chair's decision did
not reflect the result of the meeting.=20

-- Christian Huitema




From owner-ietf@ietf.org  Fri Oct 10 01:30:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26628
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 01:30:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A7pn3-0004jn-PK
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 01:26:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7pjw-0004fU-Ct
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 01:23:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26355;
	Fri, 10 Oct 2003 01:22:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7pjt-0001sG-00; Fri, 10 Oct 2003 01:22:57 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7pjq-0001s1-00; Fri, 10 Oct 2003 01:22:54 -0400
Subject: RE: Appeal to the IAB on the site-local issue
Date: Thu, 9 Oct 2003 22:22:24 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C607@server2003.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Appeal to the IAB on the site-local issue
thread-index: AcOO0oAdTcnqwDyrQWqgZCxFUMDlWQAAMnfgAAXCpnAAALDl0A==
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Christian Huitema" <huitema@windows.microsoft.com>,
        "Harald Tveit Alvestrand" <harald@alvestrand.no>, "IAB" <iab@iab.org>
Cc: "The IESG" <iesg@ietf.org>, <ipv6@ietf.org>, "IETF" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Christian,

>> Michel Py wrote:=20
>> There many people, including some that actually _wrote_
>> the procedures, that disagree with you.=20

> Christian Huitema wrote:
> Please explain or retract. I was the note-taker during that
> particular session, and I don't recall ever stating that the
> chair's decision did not reflect the result of the meeting.

Neither do I. I was not referring to you. By "_wrote_ the procedures", I
did not mean "wrote the proceedings".

As an example, I was referring to Scott Bradner's posts the; relation
with the procedure being that Scott is the editor of RFC2026; I do
acknowledge that Scott might not have been speaking as the editor of
RFC2026; nevertheless I consider (as many other people do) Scott as an
expert in terms of procedure.

Michel.




From owner-ietf@ietf.org  Fri Oct 10 03:13:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11505
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 03:13:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A7rFp-0006FZ-Vh
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 03:00:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7rCW-0006AW-KM
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 02:56:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11120
	for <ietf@ietf.org>; Fri, 10 Oct 2003 02:56:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7rCU-0002rh-00
	for ietf@ietf.org; Fri, 10 Oct 2003 02:56:34 -0400
Received: from smtp-out4.blueyonder.co.uk ([195.188.213.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7rCT-0002re-00
	for ietf@ietf.org; Fri, 10 Oct 2003 02:56:33 -0400
Received: from cluster1 ([172.23.146.42]) by smtp-out4.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.5600);
	 Fri, 10 Oct 2003 07:56:33 +0100
Received: from mail pickup service by cluster1 with Microsoft SMTPSVC;
	 Fri, 10 Oct 2003 07:56:33 +0100
Received: from smtp-in1.blueyonder.co.uk ([172.23.146.12]) by cluster1 with Microsoft SMTPSVC(5.0.2195.5329);
	 Sat, 20 Sep 2003 20:15:08 +0100
Received: from exim14.blueyonder.co.uk ([195.188.213.49]) by smtp-in1.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.5600);
	 Sat, 20 Sep 2003 17:46:06 +0100
Received: from [132.151.6.40] (helo=asgard.ietf.org)
	by exim14.blueyonder.co.uk with esmtp (Exim 4.14)
	id 1A0ks2-0007CY-HL
	for a-i@blueyonder.co.uk; Sat, 20 Sep 2003 17:46:06 +0100
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A0kVQ-00071M-Rh
	for ietf-list@asgard.ietf.org; Sat, 20 Sep 2003 12:22:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A0kHP-0006wQ-PS
	for ietf@asgard.ietf.org; Sat, 20 Sep 2003 12:08:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14641
	for <ietf@ietf.org>; Sat, 20 Sep 2003 12:08:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0kHO-00062W-00
	for ietf@ietf.org; Sat, 20 Sep 2003 12:08:14 -0400
Received: from ns.cnri.reston.va.us ([132.151.1.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0kHJ-00062T-00
	for ietf@ietf.org; Sat, 20 Sep 2003 12:08:09 -0400
Received: from [132.151.7.39] (helo=mailbox.cnri.reston.va.us)
	by ns.cnri.reston.va.us with esmtp (Exim 4.20)
	id 1A0kHJ-00059v-Aa
	for ietf@ietf.org; Sat, 20 Sep 2003 12:08:09 -0400
Date: Sat, 20 Sep 2003 12:08:09 -0400 (EDT)
From: Stanley Weilnau <sweilnau@foretec.com>
X-X-Sender:  <sweilnau@mailbox.cnri.reston.va.us>
To: <ietf@ietf.org>
Message-ID: <Pine.GSO.4.31.0309201200560.8581-100000@mailbox.cnri.reston.va.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sent-To: a-i@blueyonder.co.uk
X-OriginalArrivalTime: 20 Sep 2003 16:46:07.0004 (UTC) FILETIME=[AFEF8DC0:01C37F96]
Sender: owner-ietf@ietf.org
Precedence: bulk


As you probably have already noticed, email delievery from ietf.org has
been reinstated.

If you notice any issues, please email ietf-action@ietf.org.

Thank you,
Stanley Weilnau





From owner-ietf@ietf.org  Fri Oct 10 08:01:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22455
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 08:01:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A7vhb-00027q-B5
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 07:44:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7vhL-00027S-QY
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 07:44:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21535;
	Fri, 10 Oct 2003 07:44:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7vhK-0001LS-00; Fri, 10 Oct 2003 07:44:42 -0400
Received: from teldanex.hiit.fi ([212.68.5.99] helo=n97.nomadiclab.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7vhJ-0001LC-00; Fri, 10 Oct 2003 07:44:42 -0400
Received: from nomadiclab.com (teldanex.local.nikander.com [192.168.0.194])
	by n97.nomadiclab.com (Postfix) with ESMTP
	id D5C341C; Fri, 10 Oct 2003 14:57:26 +0300 (EEST)
Message-ID: <3F869B8F.3020508@nomadiclab.com>
Date: Fri, 10 Oct 2003 14:44:15 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20030925
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IESG <iesg@ietf.org>
Cc: IETF Discuss <ietf@ietf.org>
Subject: Detail comments wrt. HIP on draft-irtf-nsrg-report-10.txt Last Call
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I have both more general comments on the draft, and a
number of detail comments with regard to the HIP section,
Section 2.3 in the draft.  This message contains only
the detail, HIP related comments.  I will raise my
more general comments separately.

Section 2.3 of the draft describes HIP.  While the description
is mostly accurate, it does not quite reflect the most recent
work on HIP.  To make the section more up to date with the
current work, I am providing a number of comments and making
some suggestions.  Please note that these comments or suggestions
do not present critisism against the draft; their sole purpose
is to update the HIP related parts of the draft up to date
with the more recent work.

Page 8, second last paragraph, last line:

   Current text:

     HIP attempts to address this [security threat] through
     the use of public key verification.

   Suggested new text:

     HIP attempts to address this through the use of public
     key verification and a Return Routability (RR) test, similar
     to the RR test used in Mobile IPv6 Route Optimization.

   A reference to the MIPv6 RO Security backgrounder,
   draft-nikander-mobileip-v6-ro-sec-01.txt, would probably
   be in place.  That draft explains the reasoning behind the
   MIPv6 RO RR test.

Page 8, last paragraph, last line, continuing to the next page:

   Current text:

     Because the value of a HIT is a hash in part, and only
     the administratively assigned value can be aggregated, ...

   Comment:

     The current HIP specifications contain detailed
     specifications only for HITs that are just the hash,
     and do not contain an administratively assigned part.
     In that respect the currently suggested HIT usage in
     HIP is closer to PBK than earlier.  However, the architecture
     still contains the provisioning for HITs that are different
     in structure, and may contain and administratively assigned
     part.

   Suggested new text:

     Because the value of a HIT may is a hash in part or in whole, the
     possibilities of controlling large numbers of HITs with a
     single administrative configuration entry may be reduced when
     compared to the curent situation with IP addresses.  On the
     other hand, since the HITs refer to public keys and since the
     signatures are sent in clear text in HIP control messages, future
     firewalls may verify the signatures and have more secure control
     over the traffic.

Page 9, second paragraph, starting with "On the other hand, there is..."

   Comment:

     It looks like there is something missing from the paragraph.
     As it currently stands, the paragraph does not make much sense.

Page 9, third paragraph:

   Comment:

     Even with a careful reading of the HIP architecture draft version
     -02 (the referred one) or -04 (the current one), I could not
     find explicit discussion of how to use domain names.  If this
     paragraph refers to Section 5.3 of the -02 version of the HIP
     archi draft, on Host Assigning Authority (HAA) field, then I
     would suggest a much more careful wording on the paragraph.
     Furthermore, the refernence to the old version of the draft has
     to be retained, since the current version of the HIP architecture
     draft does not explicitly discuss the HAA field any more.

     Unfortunately I do not fully understand the message that the
     paragraph is trying to convey, and therefore I cannot provide
     a suggestion for new text.  Maybe the paragraph should just be
     removed.

Page 9, fourth paragraph:

   Comment:

     The new version (-04) of the HIP architecture draft explicitly
     discusses the concept of a HIP rendezvous server.  The rendezvous
     provides a service similar to the Mobile IP home agent to fast
     moving HIP hosts.  HIP hosts that change their IP address only
     occasionally may not need the services from a rendezvous server,
     and use Dynamic DNS instead.

   Suggested new text:

     A key concern with HIP is whether or not it will work in a mobile
     world.  The HIP architecture proposes a new infrastructure
     component, called the HIP rendezvous service, which provides
     services similar to the Mobile IP home agent for fast moving HIP
     hosts.  Since the rendezvous server needs to pass only a few
     packets, until HIP peers can communicate directly, the expected
     load on a rendezvous server is verly light.

     Compared to Mobile IP, there is an important difference.  That is,
     even a fast moving HIP host is not dependent on the rendezvous
     server; a host can have several rendezvous servers at the
     same time, or change them in the fly.  The life of existing
     connections is in no way bound to the rendezvous servers.

Page 22, reference 21:

   Comment:

     The currentversion of the HIP architecture draft is -04.  There
     will be a -05 version before Minneapolis deadline.  It may also
     be appropriate to refer also to the actual protocol specification,
     which is currently draft-moskowitz-hip-07.txt.  A new version -08
     will be released before the Minneapolis deadline.

     Depending on the above comment about the HAA field, it may also
     be necessary to retain a reference to the old -02 version of the
     architecture draft.

--Pekka Nikander




From owner-ietf@ietf.org  Fri Oct 10 08:05:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22767
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 08:05:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A7vw7-0002JD-MC
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 07:59:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7vvT-0002IQ-EX
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 07:59:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22339;
	Fri, 10 Oct 2003 07:59:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7vvS-0001ff-00; Fri, 10 Oct 2003 07:59:18 -0400
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7vvR-0001eX-00; Fri, 10 Oct 2003 07:59:17 -0400
Received: from dfnjgl21 (12-237-229-250.client.attbi.com[12.237.229.250])
          by comcast.net (rwcrmhc11) with SMTP
          id <2003101011583901300qn25oe>
          (Authid: sdawkins@comcast.net);
          Fri, 10 Oct 2003 11:58:39 +0000
Message-ID: <088701c38f25$dd017cd0$0400a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>,
        "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        "Tony Hain" <alh-ietf@tndh.net>, "IAB" <iab@iab.org>
Cc: "The IESG" <iesg@ietf.org>, <ipv6@ietf.org>, "IETF" <ietf@ietf.org>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C604@server2003.arneill-py.sacramento.ca.us>
Subject: Re: Appeal to the IAB on the site-local issue
Date: Fri, 10 Oct 2003 06:58:46 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Speaking as an outsider on this particular topic...

Is there any reason why these appeals should be single-threaded?

As much fun as it might be to continue to rotate this topic on a spit,
we've been discussing whether we actually made this decision or not
for six months. Continuing to discuss it for another two or three
years is just pathological. If it was the WRONG decision, deciding
that we made the decision, and letting the wrongness blossom/fester
and become evident to all, would be an improvement.

Spencer

----- Original Message ----- 
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>


> Harald,
>
> > Harald Tveit Alvestrand
> > But there's absolutely no doubt in my mind that the WG made a
> > decision, and that the chairs were procedurally correct in
> > recording that decision as the outcome of the meeting.
>
> There many people, including some that actually _wrote_ the
procedures,
> that disagree with you. As of myself, I am not completely happy with
the
> way Tony has worded his appeal (although I do agree with it), which
is
> why I will file one on different grounds as soon as this one as been
> ruled. Since it appears that there is a waiting list to file an
appeal
> on this matter, I am sure that we will be entertained for the next
two
> or three years to come.
>
> Michel.
>
>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it,
which is a sublist of ietf@ietf.org. Not all messages are passed.
Decisions on what to pass are made solely by IETF_CENSORED ML
Administrator (ietf_admin@ngnet.it).




From owner-ietf@ietf.org  Fri Oct 10 08:32:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24417
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 08:32:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A7wKJ-0003XB-IT
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 08:24:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7wJy-0003WK-La
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 08:24:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24024;
	Fri, 10 Oct 2003 08:24:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7wJx-0002G6-00; Fri, 10 Oct 2003 08:24:37 -0400
Received: from teldanex.hiit.fi ([212.68.5.99] helo=n97.nomadiclab.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7wJw-0002Fc-00; Fri, 10 Oct 2003 08:24:36 -0400
Received: from nomadiclab.com (teldanex.local.nikander.com [192.168.0.194])
	by n97.nomadiclab.com (Postfix) with ESMTP
	id 616A31C; Fri, 10 Oct 2003 15:37:20 +0300 (EEST)
Message-ID: <3F86A4E8.7040106@nomadiclab.com>
Date: Fri, 10 Oct 2003 15:24:08 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20030925
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: iesg@ietf.org, ietf@ietf.org
Subject: Re: Comments on draft-irtf-nsrg-report-10.txt Last Call
References: <17261234170.20031009152713@brandenburg.com>
In-Reply-To: <17261234170.20031009152713@brandenburg.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave and others,

Thanks for these your valuable comments, Dave.  As I mentioned in
my other message wrt. the draft, I have also some concerns.
Since they mostly align with your concerns, it looks best
to use your message as a starting point, and mostly add to it.
On the other hand, in a couple of points I do disagree with you,
or just have a different point-of-view.  I also indicate these
below.

Before going to the specifics, I also want to express my please
on the draft.  I think that it is very important that the IETF
conveys this kind of discussion, and that the draft is published
in a timely manner as an RFC.  I also hope that the IAB soon
will create the architectural discussion mailing list that they
promised at the IAB open meeting in Vienna.

I am only referring to those sections of your (Dave's) comments
that are relevant to my concerns or where I clearly disagree.

> 1.1 Security Considerations
> 
> ...connection being hijacked...
> 
> Pekka Nikander has cited both hijacking and flooding as exposures. My
> summary of his point is:
> 
> Hijacking is directing traffic to oneself. Flooding is directing 
> traffic to someone else. One is to intercept data and the other is to
> overload a victim. Both problems are created by being able to ... 
> redirect traffic to a new address.
> 
> It's helpful to make the distinction between the two.

I completely agree and second this comment.  As far as I know,
still today the best document explaining the attacks is the Mobile
IPv6 Route Optimization background document,
draft-nikander-mobileip-v6-ro-sec-01.txt.  The document is somewhat
lengthy and MIPv6 specific, but it does explain the dangers.
The current intention is to publish the document as an informational
RFC.  Gabriel Montenegro is the document editor.

> 2.3 HIP
> 
> ...reduced administration. A typical access list used on the 
> Internet...
> 
> The paper is entirely too casual about citing access control list
> aggregation. It implies that this is merely an encoding issue that is
> hurt by HIP's use of a hash.
...
> Also this issue of list aggregation is of general interest and should
> not be buried in the discussion of a particular alternative.

I concur.  Especially now when HIP is more similar to PBK in the
sense that HIP keys are mostly created by the hosts themselves
and not administratively assigned in any way, I would suggest
moving this discussion to a completely separate section.  On the
other hand, we have to remember that HIP is still very much a moving
target, and may change considerably in the future.

The issue of using HIP Host Identifiers in firewalls and ACLs is more
complicated that the text suggests.  While it is true that managing
strings that do not have any aggretable structure may be harder, it
is also true that the public key nature of the HIP host identifiers
make it possible to build much stronger firewalls and ACL protection
than the current IP address based mechanisms allow.

> Usage  [of names]
> 
> This is a discussion that seems to be missing from the section, yet
> everything hinges on it. How will a name get used? For example as the
> paper notes, one important question is whether the name needs to be
> in every packet?
> 
> This one point has massive impact on the design choice, of course.

I think that it is very important to try to clarify the role of
any potential new identifiers or stack names.

The off-line discussions that Dave, me and a few other folks have
been having seem to indicate towards a direction where we have at
least two very different design choices:

   1. The new names could be used mostly for (combound) connection
      identifiers, allowing end-points involved in connections
      to change their IP addresses during the lifetime of the
      connections.  At the same time, IP addresses would continue
      to be used for opening new connections.  There are many
      subtleties in this design, especially security wise, but I do
      not want to use excess space to explain them here.

   2. The new names could be used more like genuine end-point
      identifiers, both naming existing connections and being used
      as contact points for new connections.

While this usage semantics dimension definitely needs to be
explored much more, I don't know whether the NSRG draft is the
right place to do so.  Maybe the NSRG draft could merely
explicitly mention the problem relate to usage semantics, and
the deep relations to any future design and architecture.

> I believe a failing in the community discussion about identifiers is
> that it is conducted too much in the abstract with too little
> consideration of the actual usage requirements. Consequently people
> are not thinking very hard about trade-offs among the alternatives.

I pretty much agree.

> Infrastructure
> 
> The question is what administrative and operational infrastructures
> are needed for the identifier? (And, of course, why?) Again, my
> sensitivity about this comes from seeing a lack of consideration for
> it in the community discussions.

I tend to believe that it is too early to discuss the question of
required infrastructure in detail.  Only when we have some kind
of understanding of the usage scenarios can we do so.  From my
point of view, the current touches on infrastructure are quite
enough for the NSRG report.

> 3.5 Is an architectural change needed
> 
> ... Mobile IP will cover any perceived need...
> 
> This statement is a good example of missing the infrastructure
> factor. Mobile IP takes a significant infrastructure hit. Note, for
> example that the MIP effort has been underway for a very long time
> and has, so far, achieved essentially no market penetration.
> 
> Further, approaches like TCP-MH and SCTP show that similar
> functionality can be achieved through a very different approach that
> has no infrastructure overhead. No, not the same as MIP. Target (ie,
> Server) Mobility requires some sort of 3rd party reference service.
> However Initiator (ie, Client) Mobility does not.
> 
> I strongly encourage that the paper avoid taking MIP as a given.

Dave, with all respect, I think that you are partially missing the
context here.  My reading of the draft here is that it simply tries
to explain the two schools of thought.  From my perspective, many
people seem to believe (or at least hope) that Mobile IP will solve
the problems, and that it provides a reasonable bases for much
future functionality, multi-address based multi-homing included.
Quite a few people seem to share that point-of-view.  Whether that
point-of-view is foolish or technically unsound is a completely
separate question.

My suggestion is to simply make the section more clear in presenting
the two different schools of thought.  At minimum, I think that the
first paragraph needs to be split before the words "Here there are ...".

----

Most probably I don't share many of the larger concerns that Dave
has, given his much longer experience at the IETF and in the industry
than I have.  However, I do believe that this question of name spaces
is of immerce importance to the future of the Internet.

I do believe that the NSRG report contains many pieces of good
information and advice, and that it should be published as soon
as possible.  On the other hand, I also think that is is just yet
another starting point for a discussion.  As of today, we still lack
the proper forum for that discussion.  Therefore I urge the IESG and
the IAB to make sure that the forum will be formed in a timely fashion.

--Pekka Nikander





From owner-ietf@ietf.org  Fri Oct 10 10:32:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00406
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 10:32:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A7y4h-0002vD-4B
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 10:16:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7y4Z-0002uf-S5
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 10:16:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29868;
	Fri, 10 Oct 2003 10:16:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7y4Y-0003yP-00; Fri, 10 Oct 2003 10:16:50 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7y4X-0003yL-00; Fri, 10 Oct 2003 10:16:49 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.9/8.12.2) with ESMTP id h9AEGg6U001916;
	Fri, 10 Oct 2003 10:16:42 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.9/8.12.2/Submit) id h9AEGgOV001915;
	Fri, 10 Oct 2003 10:16:42 -0400 (EDT)
Date: Fri, 10 Oct 2003 10:16:42 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200310101416.h9AEGgOV001915@newdev.harvard.edu>
To: iab@iab.org
Subject: re: Appeal to the IAB on the site-local issue
Cc: iesg@ietf.org, ietf@ietf.org, ipv6@ietf.org
Sender: owner-ietf@ietf.org
Precedence: bulk

IAB,

Please consider this input for the IAB discussion on Tony's appeal of the
site local decision.  This should not be considered a separate appeal.
(Which I would think would have to start at the beginning with the working
group chairs.)

I do not have an opinion on the particulars of Tony's appeal since I was
not at the meeting in question and only followed the discussion on the
mailing list.  Nor is this an opinion based on the technical question under
discussion.  (Although I think some of the cures proposed to the site-local
disease are quite a bit worse than the disease itself.)

I would like to reiterate the concern I expressed on the mailing list back
in July - I think there may been a violation of the IETF consensus process 
in this case.

It is my opinion that there is a difference between a working group
deciding to adopt a technology and a working group deciding to delete a
technology from an existing IETF specification.  It is my opinion that the
second case should require a stronger demonstration of consensus to
change since the decision effects existing implementations, documentation,
text books etc.

But even without any need to show any extra level of consensus I did not
see that even a minimal level of rough consensus was demonstrated to remove
site local addresses.

The claim was made on the list that there was not consensus to keep site
local addresses, I think that is the wrong question to ask - the proposal
was to change a specification after its publication there should have been
a rough consensus to remove the feature.

I did not see rough consensus to do so based on my monitoring the list.

Scott

(this is the letter I sent back in July on the topic)

From sob Mon Jul 28 15:11:01 2003
To: Erik.Nordmark@Sun.COM
Subject: Re: state-of-art SLs
Cc: ipng@sunroof.eng.sun.com
In-Reply-To: <Roam.SIMC.2.0.6.1059396655.12753.nordmark@bebop.france>


> The chairs have read all of the messages on the list, and based on your
> considerable input, we have determined that the IPv6 WG does have rough
> consensus to deprecate the usage of IPv6 site-local unicast addressing AND
> to investigate alternative mechanisms for local addressing and local access
. control.

humm - it is not all that often that we have said that 2/3 is rough
consensus in the IETF - in my exterience if 1/3 is not in support
then I would not claim consensus (even 6 grit) - 3/4 would be very
rough indeed, 5/6 would be the mininum I would say was "rough consensus"


just when does "rough consensus" faid out in this model?

Scott




From owner-ietf@ietf.org  Fri Oct 10 11:07:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02399
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 11:07:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A7ylH-0004Ff-IH
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 11:00:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7ykO-0004Eo-IC
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 11:00:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02098;
	Fri, 10 Oct 2003 10:59:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7ykM-0004e3-00; Fri, 10 Oct 2003 11:00:02 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7ykM-0004dz-00; Fri, 10 Oct 2003 11:00:02 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 0B1D913FD8; Fri, 10 Oct 2003 10:59:58 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 05558-03; Fri, 10 Oct 2003 10:59:56 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 59F6914108; Fri, 10 Oct 2003 10:59:55 -0400 (EDT)
Date: Fri, 10 Oct 2003 10:56:33 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Scott Bradner <sob@harvard.edu>
Cc: moore@cs.utk.edu, iab@iab.org, iesg@ietf.org, ietf@ietf.org, ipv6@ietf.org
Subject: Re: Appeal to the IAB on the site-local issue
Message-Id: <20031010105633.33615cf3.moore@cs.utk.edu>
In-Reply-To: <200310101416.h9AEGgOV001915@newdev.harvard.edu>
References: <200310101416.h9AEGgOV001915@newdev.harvard.edu>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


- I don't see anything in our documented processes that requires a 
  greater degree of consensus to change an existing specification.
  Rather I see an expectation built into our process that undesirable 
  or unworkable features will be removed as a standard progresses from
  proposed to draft to full standard.

- I can understand a belief that 3/4 majority is on the rough edge of rough
  consensus.  But even assuming that rough consensus requires a greater
  plurality, there was certainly a sufficient demonstration of opinion
  that any revision to existing specifications that did include site local
  was unlikely to gain consensus and that trying to fix site-local was
  not a useful expenditure of the WG's energy.  And there was also growing
  evidence that we had not found a workable way to use site local, which would
  by itself be sufficient to bar site-local from advancing in grade along 
  with the rest of IPv6.  So even accepting that there was something less than
  consensus in the WG's decision, in some sense it's a moot point.  Site-local 
  was a dead end anyway, both politically and technically.



From owner-ietf@ietf.org  Fri Oct 10 11:14:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02884
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 11:14:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A7yty-0004eY-Kq
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 11:09:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7yta-0004as-U7
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 11:09:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02607;
	Fri, 10 Oct 2003 11:09:26 -0400 (EDT)
From: Margaret.Wasserman@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7ytZ-0004nG-00; Fri, 10 Oct 2003 11:09:33 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7ytY-0004n7-00; Fri, 10 Oct 2003 11:09:33 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9AF9SR15340;
	Fri, 10 Oct 2003 18:09:28 +0300 (EET DST)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6533991516ac158f23077@esvir03nok.nokia.com>;
 Fri, 10 Oct 2003 18:09:27 +0300
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 10 Oct 2003 10:09:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Appeal to the IAB on the site-local issue
Date: Fri, 10 Oct 2003 11:09:22 -0400
Message-ID: <E320A8529CF07E4C967ECC2F380B0CF902335083@bsebe001.americas.nokia.com>
Thread-Topic: Appeal to the IAB on the site-local issue
Thread-Index: AcOPOTTKussVoZEJS8Ken2C8SzLXCQAAmaog
To: <sob@harvard.edu>, <iab@iab.org>
Cc: <iesg@ietf.org>, <ietf@ietf.org>, <ipv6@ietf.org>
X-OriginalArrivalTime: 10 Oct 2003 15:09:25.0486 (UTC) FILETIME=[7E3928E0:01C38F40]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable



Hi Scott,

Speaking only for myself, I would like to address a couple of the=20
points that you have made.
=20
> It is my opinion that there is a difference between a working group
> deciding to adopt a technology and a working group deciding=20
> to delete a technology from an existing IETF specification.  It is my=20
> opinion that the second case should require a stronger demonstration=20
> of consensus to change since the decision effects existing =
implementations,=20
> documentation, text books etc.

First, I disagree with your basic premise.  We don't make any=20
distinction between these cases, but if we did, all other things
being equal, I think it should be harder to add a new feature to a=20
specification than to take one out.  Removing a feature from a=20
specification doesn't even prevent people from using it, whereas
adding a feature requires people to implement new code to be compliant
with the specification.

But, regardless of our differing opinions on this theoretical point, I=20
am not sure how it applies to this situation.  Although a prefix for=20
site-local addressing was set aside in the IPv6 Address Architecture=20
(a PS RFC), the entire specification for the concept of site-local=20
addressing, including how you would actually use these addresses, was=20
only ever documented in the IPv6 Scoped Addressing Architecture I-D.  At =

the time that this decision was made by the WG, the latest version of=20
that I-D had expired.  Various versions of the I-D had been considered
by the WG for years, but we had never reached rough consensus to send=20
this I-D to the IESG for publication.

> The claim was made on the list that there was not consensus=20
> to keep site local addresses, I think that is the wrong question=20
> to ask -  the proposal was to change a specification after its=20
> publication there should have been a rough consensus to remove the=20
> feature.

I'm not sure where this is coming from.  You quoted the consensus=20
finding later in your message:

> > The chairs have read all of the messages on the list, and=20
> > based on your considerable input, we have determined that=20
> > the IPv6 WG does have rough consensus to deprecate the usage=20
> > of IPv6 site-local unicast addressing AND to investigate=20
> > alternative mechanisms for local addressing and local access
> > control.

In other words, we found that there was consensus to deprecate AND
replace site-locals, not that there was a lack of consensus to keep
them.

In response to your appended letter:

> humm - it is not all that often that we have said that 2/3 is rough
> consensus in the IETF - in my exterience if 1/3 is not in support
> then I would not claim consensus (even 6 grit) - 3/4 would be very
> rough indeed, 5/6 would be the mininum I would say was "rough=20
> consensus"

The actual ratio of YES to NO responses to this poll was closer
to 3/4.

Also, the poll was not the only tool that the WG chairs (I was
one of them at the time) used to determine the consensus of the=20
WG.  There was considerable discussion regarding this issue -- in
the WG meeting and on the list.  This included a fairly large number
of people who gave conditional replies on the list, or who clarified
their meeting postion on the list along the lines of:  (1) I do not
think we should deprecate site-local unless/until we replace them,
or (2) Although I think that we should deprecate site-locals, I also
think that we need a replacement.  The chairs consensus call was
based on lengthy and careful consideration of all of the information
contributed by the WG, not just on the results of the opinion poll.

It is still my personal opinion that we correctly judged the=20
consensus of the WG regarding this matter.

Margaret=20



From owner-ietf@ietf.org  Fri Oct 10 12:30:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06022
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 12:30:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A7zrx-0006Yv-Jr
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 12:11:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7zrN-0006YC-Sd
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 12:11:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05075;
	Fri, 10 Oct 2003 12:11:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7zrM-0005dk-00; Fri, 10 Oct 2003 12:11:20 -0400
Received: from e1.ny.us.ibm.com ([32.97.182.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7zrL-0005cU-00; Fri, 10 Oct 2003 12:11:19 -0400
Received: from northrelay04.pok.ibm.com (northrelay04.pok.ibm.com [9.56.224.206])
	by e1.ny.us.ibm.com (8.12.10/NS PXFA) with ESMTP id h9AG0bHe394900;
	Fri, 10 Oct 2003 12:00:37 -0400
Received: from rotala.raleigh.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by northrelay04.pok.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h9AG0Ybk192338;
	Fri, 10 Oct 2003 12:00:34 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by rotala.raleigh.ibm.com (8.12.8/8.12.5) with ESMTP id h9AFxcGB005192;
	Fri, 10 Oct 2003 11:59:44 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost)
	by rotala.raleigh.ibm.com (8.12.8/8.12.8/Submit) with ESMTP id h9AFxcQR005188;
	Fri, 10 Oct 2003 11:59:38 -0400
Message-Id: <200310101559.h9AFxcQR005188@rotala.raleigh.ibm.com>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        "Tony Hain" <alh-ietf@tndh.net>, "IAB" <iab@iab.org>,
        "The IESG" <iesg@ietf.org>, ipv6@ietf.org, "IETF" <ietf@ietf.org>
Subject: Re: Appeal to the IAB on the site-local issue 
In-Reply-To: Message from michel@arneill-py.sacramento.ca.us
   of "Thu, 09 Oct 2003 19:14:02 PDT." <DD7FE473A8C3C245ADA2A2FE1709D90B06C604@server2003.arneill-py.sacramento.ca.us> 
Date: Fri, 10 Oct 2003 11:59:37 -0400
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

Michel,

> There many people, including some that actually _wrote_ the procedures,
> that disagree with you.

This is FUD. If there are people that agree with Tony's appeal, let
them speak for themselves. In all the email on this thread (and the
many conversations I have had with folk), I have had a _very_ hard
time seeing anyone truly supporting Tony's appeal (with the exception
of kre, who posted specifically in support of it). Scott Bradner has
already posted separately clarifying his views.

And let's be very clear. Disagreeing with the decision to deprecate is
not the same thing as agreeing with Tony's appeal. His appeal is very
specific and focuses on a process question. One can disagree with the
the decision to deprecate and simultaneously disagree with the
appeal. Not to beat an obvious point, one can't just appeal a decision
because one doesn't like it, one has to have specific reasons (as
listed in 2026). 

> As of myself, I am not completely happy with the
> way Tony has worded his appeal (although I do agree with it), which is
> why I will file one on different grounds as soon as this one as been
> ruled. Since it appears that there is a waiting list to file an appeal
> on this matter, I am sure that we will be entertained for the next two
> or three years to come.

You might want to consult RFC 2026. There is a statute of limitations
with regards to appeals:

>    All appeals must be initiated within two months of the public
>    knowledge of the action or decision to be challenged.

If you are waiting to see the results of the current appeal before
filing yet another one, you'd better have grounds other than issues
with the original actions some months ago. A statute of limitations is
apparently a necessary thing (unfortunately), precisely to prevent
issues from dragging out over "the next two or three years to come".

Popping up a level, there's a more basic thing that I fail to
understand about this appeal. If the decision to deprecate was so
wrong and flawed, how does one explain that the community seems to
support it? From some of Tony's notes, one would think that process
ran amok in this case with a horrible end result that goes against the
will of the WG. But I don't see the community agreeing with that view.
E.g., see a recent note from the IPv6 chairs on the subject
(appended).  From it, it is clear that there is strong community
support to deprecate SLs. Thus, the idea that the consensus call was
fatally flawed, that the community doesn't support the decision and
that we consequently somehow need to reset the clock and pretend that
the last 6 months didn't happen and that we must start the entire
conversation over about what to do with SLs just doesn't make any
sense to me.

Thomas

From: Bob Hinden & Brian Haberman <hinden@iprg.nokia.com>
To: ipv6@ietf.org
Cc: hinden@iprg.nokia.com, Brian Haberman <brian@innovationslab.net>
Date: Tue, 16 Sep 2003 10:55:33 -0700
Subject: Results of Poll

The results of the poll (appended below) started by the chairs in early 
August to get more feed back from the working about how to deprecate 
site-local are as follows:

    Preference A   32     45%
    Preference B   31     44%
    Preference C    8     11%
    --------------------------
    Total Votes    71    100%

The raw votes are available at:

     http://people.nokia.net/~hinden/ipv6-choices.html

If we missed your preference or got it wrong, please let us know.

There are a few conclusions that can be seen in this poll.

Only 11% of the people responding wanted to defer the deprecation of 
site-local until an alternative was deployed.  89% wanted to deprecate 
prior to an alternative being standardized or at the same time an 
alternative was standardized.

There was not a consensus about tieing the deprecation of site-local to 
defining an alternative or do the deprecation before defining an 
alternative.  The working group is closely split on this.  Even combing 
preferences B & C (i.e., 55%) does not form a consensus.

Based on this, the chairs will plan to move the deprecation document and 
the local addressing specification forward at approximately the same time, 
but will not do anything to officially tie them together.

Bob Hinden / Brian Haberman
IPv6 w.g. chairs



>Date: Mon, 04 Aug 2003 11:06:55 -0700
>To: ipng@sunroof.eng.sun.com
>From: Bob Hinden <hinden@IPRG.nokia.com>
>Subject: Moving forward on Site-Local and Local Addressing
>Cc: hinden@iprg.nokia.com
>
>[IPv6 working group chair hat on]
>
>I think the working group has been making good progress on replacing 
>site-local addresses and wanted to get feed back from the working group on 
>how we should move forward.  This is not intended to directly relate to 
>the ongoing appeal of the working groups decision to deprecate the usage 
>site-local addresses, but to get feedback on how to proceed.  I think it 
>is very important that we move forward on this issue and not rehash what 
>has happened in the past.
>
>We now have a combined local addressing requirements document 
><draft-hain-templin-ipv6-limitedrange-00.txt>, a specific alternative to 
>site-local addresses draft <draft-hinden-ipv6-global-local-addr-02.txt> 
>(accepted as a working group item at the Vienna IETF), and will soon have 
>a draft describing why site-local addresses are being deprecated and doing 
>the formal deprecation (authors identified and outline discussed at the 
>Vienna IETF).  Note that all of these documents will proceed through the 
>normal working group and IETF processes of last calls and review.
>
>I think legitimate questions have been raised about how the working group 
>should go about deprecating site-local addresses given their maturity in 
>the current specifications and use in deployed products.  Specifically 
>should they be deprecated independently from having an alternative 
>solution available, at the same time an alternative is available, or 
>sometime after an alternative is available.  A forth alternative is to not 
>replace site-local addresses in any form, but I think the working group 
>has made it clear that this is not a reasonable alternative.
>
>I would like to hear from the working group on how we should proceed.  I 
>think the choices are:
>
>A) Deprecate Site-Local addresses independently from having an alternative 
>solution available.  This would mean that the working group should treat 
>the deprecation, and requirements and solution documents outlined above 
>independently from each other.  If there was no consensus on an 
>alternative a replacement would not happen.
>
>B) Deprecate Site-Local addresses at the same time as a alternative 
>solution is agreed to.  This would mean advancing both documents at the 
>same time and making them include normative references to each other to 
>insure that they were published at the same time.  This would result in 
>the deprecation only happening if a consensus was reached on an alternative.
>
>C) Deprecate Site-Local addresses after an alternative is defined, 
>standardized, and in operational practice.  This would mean not advancing 
>a deprecation document until there was operational evidence that the 
>alternative was working and shown to be an improvement over Site-Local 
>addresses.
>
>Note:  In the above choices "Deprecate Site-Local addresses" means 
>publishing an RFC that does the formal deprecation.
>
>Please respond to the list with your preference, or if there is an 
>alternative approach that is an improvement from the ones I outlined.  I 
>hope that many of you will respond.
>
>Thanks,
>Bob




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From owner-ietf@ietf.org  Fri Oct 10 14:44:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11552
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 14:44:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A820X-0001Gz-94
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 14:28:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8203-0001GE-GY
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 14:28:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10991;
	Fri, 10 Oct 2003 14:28:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8201-0007Kw-00; Fri, 10 Oct 2003 14:28:25 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8200-0007Kp-00; Fri, 10 Oct 2003 14:28:24 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.9/8.12.2) with ESMTP id h9AIId6U002823;
	Fri, 10 Oct 2003 14:18:39 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.9/8.12.2/Submit) id h9AIIdLF002822;
	Fri, 10 Oct 2003 14:18:39 -0400 (EDT)
Date: Fri, 10 Oct 2003 14:18:39 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200310101818.h9AIIdLF002822@newdev.harvard.edu>
To: michel@arneill-py.sacramento.ca.us, narten@us.ibm.com
Subject: Re: Appeal to the IAB on the site-local issue
Cc: alh-ietf@tndh.net, harald@alvestrand.no, iab@iab.org, iesg@ietf.org,
        ietf@ietf.org, ipv6@ietf.org
In-Reply-To: <200310101559.h9AFxcQR005188@rotala.raleigh.ibm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

note that this survey was done *after* the decision was announced
as a done deal - I, for one, took that into account when I responded

----
From: Bob Hinden & Brian Haberman <hinden@iprg.nokia.com>
To: ipv6@ietf.org
Cc: hinden@iprg.nokia.com, Brian Haberman <brian@innovationslab.net>
Date: Tue, 16 Sep 2003 10:55:33 -0700
Subject: Results of Poll

The results of the poll (appended below) started by the chairs in early 
August to get more feed back from the working about how to deprecate 
site-local are as follows:

    Preference A   32     45%
    Preference B   31     44%
    Preference C    8     11%
    --------------------------
    Total Votes    71    100%

The raw votes are available at:

     http://people.nokia.net/~hinden/ipv6-choices.html

If we missed your preference or got it wrong, please let us know.




From owner-ietf@ietf.org  Fri Oct 10 14:44:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11568
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 14:44:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A829E-0001Oy-L4
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 14:37:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A827d-0001Na-Hi
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 14:36:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11235;
	Fri, 10 Oct 2003 14:36:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A827b-0007Mi-00; Fri, 10 Oct 2003 14:36:16 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A827b-0007Me-00; Fri, 10 Oct 2003 14:36:15 -0400
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h9AIZacb005067;
	Fri, 10 Oct 2003 11:35:38 -0700 (PDT)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AMK37233;
	Fri, 10 Oct 2003 11:31:17 -0700 (PDT)
Message-Id: <6.0.0.22.2.20031010111733.041e6000@mira-sjc5-b.cisco.com>
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Fri, 10 Oct 2003 11:34:04 -0700
To: Margaret.Wasserman@nokia.com
From: Fred Baker <fred@cisco.com>
Subject: Removing features
Cc: <sob@harvard.edu>, <iab@iab.org>, <iesg@ietf.org>, <ietf@ietf.org>,
        <ipv6@ietf.org>
In-Reply-To: <E320A8529CF07E4C967ECC2F380B0CF902335083@bsebe001.americas
 .nokia.com>
References: <E320A8529CF07E4C967ECC2F380B0CF902335083@bsebe001.americas.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 08:09 AM 10/10/2003, Margaret.Wasserman@nokia.com wrote:
>Removing a feature from a specification doesn't even prevent people from 
>using it

I'm changing the thread subject. While this is relevant to the subject of 
Tony's appeal, it is also a general debate orthogonal to Tony's appeal. It 
is a side note that may prove relevant. While your assertion may generally 
be true, this particular change does prevent people from using it, and I'm 
not sure the assertion is true as worded.

The site-local proposal says that there is an assurance that a particular 
block of addresses is available to a network administration to use in 
whatever way it chooses within the confines of its own network, on the 
proviso that it neither advertise those addresses outside its network in 
routing nor trust announcements of the block by others, and presumably also 
ingress filters for the address prefix. Removing the concept removes that 
capability. YMMV as to whether you want the capability, but you cannot 
accurately say that the capability still exists once it has been removed.

Your assertion is also dangerous in protocols. If a capability is 
deprecated (remains defined but its implementation/use is discouraged, as 
for example true of TOS routing in OSPF, cf RFCs 1583, 2178, and 2328), 
then an implementation that contains the capability can accurately say it 
is using a superset of the specification. If the capability is simply 
removed, one has to presume that at some time in the future the bits will 
be reused with different semantics, making the implementation that 
yesterday was using a superset of the specification an active hazard today, 
and causing operational networks that were using the capability to have to 
make some potentially hard choices.

So in the general case I don't see a problem with deprecating things under 
the right circumstances, but I do have a problem with removing them 
outright. Deprecation doesn't prevent people from using them, but outright 
removal can be dangerous. And in this case, the assertion that one can 
still use the address prefix in a local manner is simply incorrect; it can 
be assigned at the whim of IANA, and network administrations need to plan 
accordingly. 




From owner-ietf@ietf.org  Fri Oct 10 14:52:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12208
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 14:52:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A82Gz-00021s-PR
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 14:45:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A82G7-0001vw-1I
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 14:45:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11620;
	Fri, 10 Oct 2003 14:44:55 -0400 (EDT)
From: Margaret.Wasserman@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A82G5-0007Tw-00; Fri, 10 Oct 2003 14:45:01 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A82G4-0007To-00; Fri, 10 Oct 2003 14:45:00 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9AIiwv26172;
	Fri, 10 Oct 2003 21:44:58 +0300 (EET DST)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65345e60cbac158f24077@esvir04nok.ntc.nokia.com>;
 Fri, 10 Oct 2003 21:44:57 +0300
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 10 Oct 2003 11:43:52 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Removing features
Date: Fri, 10 Oct 2003 14:43:49 -0400
Message-ID: <E320A8529CF07E4C967ECC2F380B0CF902335089@bsebe001.americas.nokia.com>
Thread-Topic: Removing features
Thread-Index: AcOPXYGny6eNvc5IT4axQxuM6Avu+gAADypw
To: <fred@cisco.com>
Cc: <sob@harvard.edu>, <iab@iab.org>, <iesg@ietf.org>, <ietf@ietf.org>,
        <ipv6@ietf.org>
X-OriginalArrivalTime: 10 Oct 2003 18:43:52.0986 (UTC) FILETIME=[73D9D7A0:01C38F5E]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


Hi Fred,

> So in the general case I don't see a problem with deprecating=20
> things under the right circumstances, but I do have a problem with=20
> removing them outright. Deprecation doesn't prevent people from using=20
> them, but outright removal can be dangerous. And in this case, the=20
> assertion that one can still use the address prefix in a local manner=20
> is simply incorrect; it can be assigned at the whim of IANA, and=20
> network administrations need to plan accordingly.=20

Actually, we are being very careful about this in the deprecation
of IPv6 site-local addressing.  Christian Huitema and Brian Carpenter=20
have co-authored a very carefully written deprecation document that=20
makes it clear how these addresses should be treated to avoid problems=20
with existing site-local implementations.  And, we are planning to=20
instruct IANA not to return these addresses to the regular allocation=20
pool.

Margaret



From owner-ietf@ietf.org  Fri Oct 10 15:43:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16239
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 15:43:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A831U-0004Ni-3m
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 15:34:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A830D-0004KK-TN
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 15:32:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15310;
	Fri, 10 Oct 2003 15:32:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A830B-0000SP-00; Fri, 10 Oct 2003 15:32:39 -0400
Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A830A-0000SH-00; Fri, 10 Oct 2003 15:32:38 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h9ALUuR22076;
	Fri, 10 Oct 2003 23:30:57 +0200
Message-ID: <3F87250F.7050700@it.su.se>
Date: Fri, 10 Oct 2003 23:30:55 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: "Eugene M. Kim" <gene@nttmcl.com>
CC: Tony Hain <alh-ietf@tndh.net>, IETF IPv6 Working Group <ipv6@ietf.org>,
        The Internet Engineering Task Force <ietf@ietf.org>,
        The Internet Engineering Steering Group <iesg@ietf.org>,
        The Internet Architecture Board <iab@iab.org>
Subject: Re: Appeal to the IAB on the site-local issue
References: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net> <3F86FFD5.4050706@nttmcl.com>
In-Reply-To: <3F86FFD5.4050706@nttmcl.com>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

Eugene M. Kim wrote:


<snip>

|
| With all due respect, it seems that it would be beneficial for both
| camps (for and against SL) to hear, even now, the real concerns directly
| from the operation people and to let them participate in the decision
| themselves. ... <snip>

Been there. Done that. Didn't work. This vast Moral Majority of the
Site-Locals either don't exist or live entierly behind NATs or other
boxes which prevent them from receiving the call to arms to participate
in the debate. ;-)

	Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/hyUP8Jx8FtbMZncRAjBrAJ9mn99C+vUGrNifGl+moqvMz31qPgCfavjp
ZpDTz3E6/Z54/T4qRpL8W3o=
=LQPP
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Fri Oct 10 16:11:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19474
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 16:11:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A83HW-0006vX-51
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 15:50:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A83BP-0005AQ-BY
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 15:44:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16542;
	Fri, 10 Oct 2003 15:44:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A83BK-0000iq-00; Fri, 10 Oct 2003 15:44:10 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A83BJ-0000il-00; Fri, 10 Oct 2003 15:44:09 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id DD891141B4; Fri, 10 Oct 2003 15:44:08 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 13876-04; Fri, 10 Oct 2003 15:44:07 -0400 (EDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 1A3D71412A; Fri, 10 Oct 2003 15:44:07 -0400 (EDT)
Date: Fri, 10 Oct 2003 15:40:11 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Fred Baker <fred@cisco.com>
Cc: moore@cs.utk.edu, Margaret.Wasserman@nokia.com, sob@harvard.edu,
        iab@iab.org, iesg@ietf.org, ietf@ietf.org, ipv6@ietf.org
Subject: Re: Removing features
Message-Id: <20031010154011.17ee6634.moore@cs.utk.edu>
In-Reply-To: <6.0.0.22.2.20031010111733.041e6000@mira-sjc5-b.cisco.com>
References: <E320A8529CF07E4C967ECC2F380B0CF902335083@bsebe001.americas.nokia.com>
	<6.0.0.22.2.20031010111733.041e6000@mira-sjc5-b.cisco.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> At 08:09 AM 10/10/2003, Margaret.Wasserman@nokia.com wrote:
> >Removing a feature from a specification doesn't even prevent people
> >from using it
> 
> I'm changing the thread subject. While this is relevant to the subject
> of Tony's appeal, it is also a general debate orthogonal to Tony's
> appeal. It is a side note that may prove relevant. While your
> assertion may generally be true, this particular change does prevent
> people from using it, and I'm not sure the assertion is true as
> worded.

Given that the objections to site local were based on the realization
that using it actually causes harm to applications and to the network,
then I agree with you.  Most of us realize that we cannot prevent
harmful behavior, especially on a private network.  But the intent of
deprecating site-local was at the very minimum to strongly discourage
its use.

> The site-local proposal says that there is an assurance that a
> particular block of addresses is available to a network administration
> to use in whatever way it chooses within the confines of its own
> network, on the proviso that it neither advertise those addresses
> outside its network in routing nor trust announcements of the block by
> others, and presumably also ingress filters for the address prefix.

It turns out that those usage constraints are not sufficient to avoid
harm to the network as a whole, and after numerous attempts we have 
not been able to define a set of constraints that still allow use of
site-local while avoiding that harm.

> Your assertion is also dangerous in protocols. If a capability is 
> deprecated (remains defined but its implementation/use is discouraged,
> as for example true of TOS routing in OSPF, cf RFCs 1583, 2178, and
> 2328), then an implementation that contains the capability can
> accurately say it is using a superset of the specification. 

The terms you are using are biased.  A vendor could define a "superset"
of IP that had the "capability" of routing addresses to destinations
other than those intended by the source, or modifying the contents of
messages sent by the source, or masquerading as the destination and 
issuing responses that appear to come from the destination.  A DNS
server could add the "capability" of misrepresenting the status of a
name given in a query.  Indeed, all of these "capabilities" exist in
some product or another.  It also turns out that all of these
"capabilities" cause harm to applications.

It's a fallacy to believe, and disingeneous to pretend, that 
providing new "capabilities" or a "superset" of a protocol is at worst
a benign activity.  There exist "capabilities" that do harm.  In the 
case of site-locals, it happens that this "capability" was part of an
IETF specification.  So once we realized that site-locals were harmful,
it became our responsibility to fix them.  I agree, as do most of us,
that we should make considerable effort to avoid disruptive changes to
published specifications.  However it was only after investigating
several proposals for less disruptive fixes, and finding all of them
insufficient, that there emerged a consensus to deprecate site-locals.

> If the
> capability is simply removed, one has to presume that at some time in
> the future the bits will be reused with different semantics, making
> the implementation that yesterday was using a superset of the
> specification an active hazard today, and causing operational networks
> that were using the capability to have to make some potentially hard
> choices.

We can promise to not re-assign them, and we can keep our promise.

But if site administrators decide to move away from site-locals, this is
a good thing, as it will minimize the harm done by having them in the wild.

Keith





From owner-ietf@ietf.org  Fri Oct 10 16:21:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20404
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 16:21:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A83Ko-000833-Vf
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 15:53:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A83Ew-00067K-MI
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 15:47:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17074;
	Fri, 10 Oct 2003 15:47:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A83Eu-0000sT-00; Fri, 10 Oct 2003 15:47:52 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A83Et-0000sK-00; Fri, 10 Oct 2003 15:47:51 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id EE7AB14129; Fri, 10 Oct 2003 15:47:51 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 14254-06; Fri, 10 Oct 2003 15:47:51 -0400 (EDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id B5CC014196; Fri, 10 Oct 2003 15:47:50 -0400 (EDT)
Date: Fri, 10 Oct 2003 15:43:55 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Tony Hain" <alh-ietf@tndh.net>
Cc: moore@cs.utk.edu, narten@us.ibm.com, michel@arneill-py.sacramento.ca.us,
        harald@alvestrand.no, alh-ietf@tndh.net, iab@iab.org, iesg@ietf.org,
        ipv6@ietf.org, ietf@ietf.org
Subject: Re: Appeal to the IAB on the site-local issue
Message-Id: <20031010154355.11275d3e.moore@cs.utk.edu>
In-Reply-To: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net>
References: <200310101559.h9AFxcQR005188@rotala.raleigh.ibm.com>
	<IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> You are listening to a very limited subset of the 'community'. I have had
> several questions from fortune 500 network managers as to 'what now?' They
> plan to roll out IPv6 with addresses that are in either the FEC0 range
> anyway, or are trusting that the proposed replacement FC00 will be finalized
> soon.

maybe those people are being fed bad information.  the question is, by whom?



From owner-ietf@ietf.org  Fri Oct 10 16:25:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20681
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 16:25:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A83kq-0007QO-NS
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 16:20:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A83M9-0008Ur-Ie
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 15:55:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17905;
	Fri, 10 Oct 2003 15:55:13 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A83M7-00018A-00; Fri, 10 Oct 2003 15:55:19 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A83M7-000180-00; Fri, 10 Oct 2003 15:55:19 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9AJt6RX003398;
	Fri, 10 Oct 2003 15:55:06 -0400
Message-Id: <200310101955.h9AJt6RX003398@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Fred Baker <fred@cisco.com>
Cc: iab@iab.org, iesg@ietf.org, ietf@ietf.org, ipv6@ietf.org
Subject: Re: Removing features 
In-Reply-To: Your message of "Fri, 10 Oct 2003 11:34:04 PDT."
             <6.0.0.22.2.20031010111733.041e6000@mira-sjc5-b.cisco.com> 
References: <E320A8529CF07E4C967ECC2F380B0CF902335083@bsebe001.americas.nokia.com>
            <6.0.0.22.2.20031010111733.041e6000@mira-sjc5-b.cisco.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-616238898P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 10 Oct 2003 15:55:06 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-616238898P
Content-Type: text/plain; charset=us-ascii

On Fri, 10 Oct 2003 11:34:04 PDT, Fred Baker said:

> The site-local proposal says that there is an assurance that a particular 
> block of addresses is available to a network administration to use in 
> whatever way it chooses within the confines of its own network, on the 
> proviso that it neither advertise those addresses outside its network in 
> routing nor trust announcements of the block by others, and presumably also 
> ingress filters for the address prefix. Removing the concept removes that 
> capability. YMMV as to whether you want the capability, but you cannot 
> accurately say that the capability still exists once it has been removed.

On the flip side, the biggest basis for removing the feature is the fact that
RFC1918 contains essentially the same provision for IPv4, and 1918 addresses
are continually leaking like sieves, and nobody (to my knowledge) was able to
point at magic router filter dust that would prevent it from happening on IPv6.

So the basic concept is (in my opinion) broken and needs to be euthanized.

> outright. Deprecation doesn't prevent people from using them, but outright 
> removal can be dangerous. And in this case, the assertion that one can 
> still use the address prefix in a local manner is simply incorrect; it can 
> be assigned at the whim of IANA, and network administrations need to plan 
> accordingly. 

And in fact, we've seen this effect in operation recently, when the 69/8 address
space was allocated but often unreachable due to bogon filters....

All in all, however, I think outright removal, although short-term more painful,
will be less troublesome than many years of debugging problems caused by
1918-style leakage of addresses for a "deprecated" feature.




--==_Exmh_-616238898P
Content-Type: application/pgp-signature

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

iD8DBQE/hw6acC3lWbTT17ARAkKHAKC9AnIs9ADnIlVNJNob6L/Yu+khUACfdZ7h
jYoBYJJed2s3k68TNYUEQu8=
=VMnG
-----END PGP SIGNATURE-----

--==_Exmh_-616238898P--



From owner-ietf@ietf.org  Fri Oct 10 16:40:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21750
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 16:40:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A83wd-0000sz-8O
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 16:33:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A83p3-0000Aa-MT
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 16:25:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20663;
	Fri, 10 Oct 2003 16:25:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A83p1-000231-00; Fri, 10 Oct 2003 16:25:12 -0400
Received: from ns2.sea.interquest.net ([66.135.144.2] helo=ns2.sea)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A83p1-00022y-00; Fri, 10 Oct 2003 16:25:11 -0400
Received: from ssprunk (ip135.post-vineyard.dfw.interquest.net [66.135.181.135])
	by ns2.sea (8.12.10/8.12.5) with SMTP id h9AKP5fa005942;
	Fri, 10 Oct 2003 13:25:06 -0700
Message-ID: <011f01c38f6c$99c12dc0$6401a8c0@ssprunk>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Leif Johansson" <leifj@it.su.se>, "Eugene M. Kim" <gene@nttmcl.com>
Cc: "Tony Hain" <alh-ietf@tndh.net>, "IETF IPv6 Working Group" <ipv6@ietf.org>,
        "The Internet Engineering Task Force" <ietf@ietf.org>,
        "The Internet Engineering Steering Group" <iesg@ietf.org>,
        "The Internet Architecture Board" <iab@iab.org>
References: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net> <3F86FFD5.4050706@nttmcl.com> <3F87250F.7050700@it.su.se>
Subject: Re: Appeal to the IAB on the site-local issue
Date: Fri, 10 Oct 2003 15:23:55 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thus spake "Leif Johansson" <leifj@it.su.se>
> Been there. Done that. Didn't work. This vast Moral Majority of the
> Site-Locals either don't exist or live entierly behind NATs or other
> boxes which prevent them from receiving the call to arms to participate
> in the debate. ;-)

Or we all just got sick of the bickering and accepted defeat (unlike Tony).

For the record, I can't support deprecating site locals until we have
something else approved to replace them -- at which point I say good
riddance.  There are several drafts in the WG to that end which haven't
gained any momentum thus far.

S

Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking




From owner-ietf@ietf.org  Fri Oct 10 17:18:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23292
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 17:18:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A84Lt-0002cO-8e
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 16:59:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A845a-0001YP-G3
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 16:42:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21929;
	Fri, 10 Oct 2003 16:42:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A845Y-0002Od-00; Fri, 10 Oct 2003 16:42:16 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A845Y-0002NA-00; Fri, 10 Oct 2003 16:42:16 -0400
Received: from cisco.com (171.68.223.137)
  by sj-iport-3.cisco.com with ESMTP; 10 Oct 2003 13:49:46 -0700
Received: from cisco.com (rtp-vpn2-432.cisco.com [10.82.241.176])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h9AKecYb007313;
	Fri, 10 Oct 2003 13:40:39 -0700 (PDT)
Message-ID: <3F871946.400@cisco.com>
Date: Fri, 10 Oct 2003 13:40:38 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stephen Sprunk <stephen@sprunk.org>
CC: Leif Johansson <leifj@it.su.se>, "Eugene M. Kim" <gene@nttmcl.com>,
        Tony Hain <alh-ietf@tndh.net>, IETF IPv6 Working Group <ipv6@ietf.org>,
        The Internet Engineering Task Force <ietf@ietf.org>,
        The Internet Engineering Steering Group <iesg@ietf.org>,
        The Internet Architecture Board <iab@iab.org>
Subject: Re: Appeal to the IAB on the site-local issue
References: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net> <3F86FFD5.4050706@nttmcl.com> <3F87250F.7050700@it.su.se> <011f01c38f6c$99c12dc0$6401a8c0@ssprunk>
In-Reply-To: <011f01c38f6c$99c12dc0$6401a8c0@ssprunk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Stephen Sprunk wrote:
> Or we all just got sick of the bickering and accepted defeat (unlike Tony).
> 
> For the record, I can't support deprecating site locals until we have
> something else approved to replace them -- at which point I say good
> riddance.  There are several drafts in the WG to that end which haven't
> gained any momentum thus far.

And this is why the appeal is in my opinion untimely.  The working group 
has not yet been given a chance to provide any documentation on that 
"What next?" question Tony asked.  For the IESG or the IAB to interfere 
at this stage would be micromanagement.

But here we are.  Tony has decided to push an appeal of a "vote", and 
not even one that generated a document.  That the appeal has even gotten 
this far seems is a flaw in the process.

Had the IESG been able to disallow the appeal, simply on this basis, 
then perhaps the working group could actually provide documents about 
which we could argue over technical merit.  As it stands, I predict yet 
another round of appeals once IETF last call closes, and the document is 
reviewed by the IESG.

Welcome to Court TV, IETF style.

Eliot





From owner-ietf@ietf.org  Fri Oct 10 17:34:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23894
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 17:34:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A84lE-00047m-IP
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 17:25:20 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A84jm-00041U-SA
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 17:23:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23546;
	Fri, 10 Oct 2003 17:23:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A84jk-0002vP-00; Fri, 10 Oct 2003 17:23:48 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A84jk-0002vL-00; Fri, 10 Oct 2003 17:23:48 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 78CF314020; Fri, 10 Oct 2003 17:23:48 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 27824-04; Fri, 10 Oct 2003 17:23:47 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id A3F8913FE5; Fri, 10 Oct 2003 17:23:45 -0400 (EDT)
Date: Fri, 10 Oct 2003 17:20:25 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Stephen Sprunk" <stephen@sprunk.org>
Cc: moore@cs.utk.edu, leifj@it.su.se, gene@nttmcl.com, alh-ietf@tndh.net,
        ipv6@ietf.org, ietf@ietf.org, iesg@ietf.org, iab@iab.org
Subject: Re: Appeal to the IAB on the site-local issue
Message-Id: <20031010172025.704837be.moore@cs.utk.edu>
In-Reply-To: <011f01c38f6c$99c12dc0$6401a8c0@ssprunk>
References: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net>
	<3F86FFD5.4050706@nttmcl.com>
	<3F87250F.7050700@it.su.se>
	<011f01c38f6c$99c12dc0$6401a8c0@ssprunk>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> For the record, I can't support deprecating site locals until we have
> something else approved to replace them 

replace them for what purpose?   different people wanted site locals for
different purposes.  some of those purposes are dubious.  others inherently
cause harm.

we're not going to find a single solution that satisfies all of the
purposes for which people thought site-locals were a good idea.
and that is a good thing.




From owner-ietf@ietf.org  Fri Oct 10 17:58:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24746
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 17:58:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A85BI-0005o0-W4
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 17:52:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8546-0005TP-N1
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 17:44:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24386;
	Fri, 10 Oct 2003 17:44:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8544-0003Cx-00; Fri, 10 Oct 2003 17:44:48 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8543-0003Cu-00; Fri, 10 Oct 2003 17:44:48 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h9ALhted010164;
	Fri, 10 Oct 2003 23:43:58 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Fri, 10 Oct 2003 23:43:20 +0200
Subject: Re: Removing features 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: iab@iab.org, iesg@ietf.org, ietf@ietf.org, ipv6@ietf.org
To: Valdis.Kletnieks@vt.edu
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200310101955.h9AJt6RX003398@turing-police.cc.vt.edu>
Message-Id: <C4319890-FB6A-11D7-B291-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On vrijdag, okt 10, 2003, at 21:55 Europe/Amsterdam, 
Valdis.Kletnieks@vt.edu wrote:

> the biggest basis for removing the feature is the fact that
> RFC1918 contains essentially the same provision for IPv4, and 1918 
> addresses
> are continually leaking like sieves, and nobody (to my knowledge) was 
> able to
> point at magic router filter dust that would prevent it from happening 
> on IPv6.

> So the basic concept is (in my opinion) broken and needs to be 
> euthanized.

This is based on the assumption that leaking RFC 1918 routing 
information or packets with RFC 1918 source or destination addresses is 
actually harmful in and of itself. This is a broken assumption. If 
people are going to send bogus routes or packets, then having RFC 1918 
addresses in them is the least harmful way to do it. Now obviously 
people shouldn't send out bogus routes or packets, but this is a 
problem that is completely unrelated to private addressing issues. It's 
just that private addresses make this problem much more visible. 
Removing that which is clearly wrong only helps to make sure the 
wrongness that remains is less visible.

And if you're unable to figure out how to filter private addresses in 
routing updates or IP traffic, there are numerous non-magical books out 
there that will tell you how to do this.

>> outright. Deprecation doesn't prevent people from using them, but 
>> outright
>> removal can be dangerous. And in this case, the assertion that one can
>> still use the address prefix in a local manner is simply incorrect; 
>> it can
>> be assigned at the whim of IANA, and network administrations need to 
>> plan
>> accordingly.

> And in fact, we've seen this effect in operation recently, when the 
> 69/8 address
> space was allocated but often unreachable due to bogon filters....

> All in all, however, I think outright removal, although short-term 
> more painful,
> will be less troublesome than many years of debugging problems caused 
> by
> 1918-style leakage of addresses for a "deprecated" feature.

Your argument is self-defeating. If we were to recycle FEC0::/10 this 
would be the 69.0.0.0/8 but ten times worse. Everybody knew that 
69.0.0.0/8 would be assigned at some point, so the people filtering 
this range knew what they were doing (or at least, they should have). 
FEC0::/10 on the other hand has been in the specification as a fixed 
special purpose range for a lot of years, and presumably people have 
implemented their networks accordingly. Pulling the rug from under them 
by removing this address range from the spefication and (at least 
theoretically) allowing it to be reassigned for a different purpose is 
insane.

And that's not even considering the lack of alternatives at this point 
in time. We may not be able to come up with a reasonable way for 
networks that implement site local addressing and interconnect with 
other networks that do the same, but there is still a very real need 
for addresses that can be used in disconnected IPv6 networks. I believe 
that forcing people who just want to interconnect a few boxes to do 
some testing to obtain globally routable IPv6 unicast space is a very 
bad idea. As long as there aren't any alternatives, FEC0::/10 should be 
used for this. And even after we have alternatives, FEC0::/10 should 
forever be set aside to avoid problems.

> <mime-attachment>

Huh?

Iljitsch van Beijnum




From owner-ietf@ietf.org  Fri Oct 10 18:10:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25904
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 18:10:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A85Oj-00026h-Ed
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 18:06:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A85MK-000178-Iq
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 18:03:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25188;
	Fri, 10 Oct 2003 18:03:31 -0400 (EDT)
From: Margaret.Wasserman@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A85MI-0003Ua-00; Fri, 10 Oct 2003 18:03:38 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A85MH-0003UT-00; Fri, 10 Oct 2003 18:03:37 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9AM3ZZ04816;
	Sat, 11 Oct 2003 01:03:35 +0300 (EET DST)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6535143bc9ac158f25186@esvir05nok.ntc.nokia.com>;
 Sat, 11 Oct 2003 01:03:35 +0300
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 10 Oct 2003 17:03:33 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Removing features 
Date: Fri, 10 Oct 2003 18:03:31 -0400
Message-ID: <E320A8529CF07E4C967ECC2F380B0CF90233508D@bsebe001.americas.nokia.com>
Thread-Topic: Removing features 
Thread-Index: AcOPd1/+YXk8uCDNSGq4vJ5C4Xuh1gAAZMNA
To: <fred@cisco.com>, <Valdis.Kletnieks@vt.edu>
Cc: <iab@iab.org>, <iesg@ietf.org>, <ietf@ietf.org>, <ipv6@ietf.org>
X-OriginalArrivalTime: 10 Oct 2003 22:03:33.0656 (UTC) FILETIME=[58E30180:01C38F7A]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


=20
> The second is the side point I raised with Margaret: in the=20
> general case of "things in specifications", removing something=20
> from a  specification does not mean that someone can still use=20
> it. Deprecation protects such a usage, but removal does not.

Scott's posting made a distinction between adding and removing
features, lumping site-local deprecation into the "removing
features" category.  I echoed his terminology.

I agree with you that there is a difference between simply
removing a feature (which might cause serious backwards
compatibility concerns, and could be quite irresponsible in
some cases) and carefully deprecating a feature (while considering
the affects on current implementations and preserving  backwards=20
compatibility).  In the IPv6 site-local case, the decision was made=20
to deprecate site-local addresses, and that is what we are working=20
to do.  The proposals currently on the table reserve the current=20
site-local prefix, so that it will not be reallocated by IANA.

Fred, I hope that this resolves your technical concern about
this particular case, and I apologize for not making this
distinction clear in my response to Scott. =20

> That is actually not the=20
> subject of either appeal, and should not enter into the discussion of=20
> either appeal,...

As far as I know, there is only one appeal currently open
regarding this subject.

Margaret



From owner-ietf@ietf.org  Fri Oct 10 18:25:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27066
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 18:25:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A85YB-0005JA-LW
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 18:15:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A85Te-0003jd-Ip
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 18:11:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25974;
	Fri, 10 Oct 2003 18:11:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A85Tc-0003ZT-00; Fri, 10 Oct 2003 18:11:12 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A85Tb-0003Yj-00; Fri, 10 Oct 2003 18:11:11 -0400
Received: from cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 10 Oct 2003 15:18:30 -0700
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h9AM9k7E028188;
	Fri, 10 Oct 2003 15:09:46 -0700 (PDT)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AMK60803;
	Fri, 10 Oct 2003 15:05:23 -0700 (PDT)
Message-Id: <6.0.0.22.2.20031010143040.04624358@mira-sjc5-b.cisco.com>
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Fri, 10 Oct 2003 14:55:04 -0700
To: Leif Johansson <leifj@it.su.se>
From: Fred Baker <fred@cisco.com>
Subject: Re: Appeal to the IAB on the site-local issue
Cc: IETF IPv6 Working Group <ipv6@ietf.org>,
        The Internet Engineering Task Force <ietf@ietf.org>,
        The Internet Engineering Steering Group <iesg@ietf.org>,
        The Internet Architecture Board <iab@iab.org>
In-Reply-To: <3F87250F.7050700@it.su.se>
References: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net>
 <3F86FFD5.4050706@nttmcl.com>
 <3F87250F.7050700@it.su.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 02:30 PM 10/10/2003, Leif Johansson wrote:
>>With all due respect, it seems that it would be beneficial for both camps 
>>(for and against SL) to hear, even now, the real concerns directly from 
>>the operation people and to let them participate in the decision 
>>themselves. ... <snip>
>
>Been there. Done that. Didn't work. This vast Moral Majority of the 
>Site-Locals either don't exist or live entierly behind NATs or other boxes 
>which prevent them from receiving the call to arms to participate in the 
>debate. ;-)

Let's at least try to be fair and realistic. There is a fairly large and 
vocal camp from tier 1 and tier 2 operators in the IETF which presumes that 
the needs of a backbone service provider are the only needs that are 
relevant in any network and go around blasting anything they don't need as 
"clueless". But not all tier 1/2 operators are represented or choose to 
speak publicly, and not all networks are tier 1/2 networks. I have a fairly 
long history of sitting in the room with people from certain tier 1/2 
operators who will tell me at dinner or in the hallway what they think 
about this or that, but are precluded from speaking for themselves publicly 
by the policy or culture of their employers. I'm not naming names, because 
that would be inappropriate (if they can't/won't speak for themselves 
because their employer doesn't want to tip a business hand, who am I to tip 
it for them?). But I guarantee you that they are present, and they don't 
necessarily agree with the vocal operators.

When it comes to tertiary operators and enterprises, let's face it. They're 
vastly under-represented, and perhaps not at all represented. If they were 
represented as completely as the Tier 1/2 operators are, we would routinely 
have meetings with multiples of 10K attendees. They don't come to IETF 
meetings. They read about them in Network World and Computer Week, they 
tell their vendors what they are willing to buy, and their vendors come 
talk about the features smaller operators and enterprises are asking for. 
The vendors take a beating from the operational elite, who tell us

  - we have no clue how to run a network
  - we have no idea what features a network needs
  - there is no deployed (pick your protocol that is perhaps inappropriate in
    a Tier 1 backbone) in the whole wide world
  - Specifically, there is no operational deployment of the diffserv
    architecture (having heard this extensively from the gentleman from 
Telstra,
    I wonder if he ever talks to the gentleman from Comindico that I spoke 
with
    last week; they seem to live on different planets)
  - That everything we produce and talk about is what we want to sell, not
    what the tier 1/2 operators or anybody else wants to buy.
  - That whatever we say is inherently invalid because we are vendors.

Interesting. Do we do these things for our health? Do we go generate 
features and then try to sell them to people? Do we keep beat our heads 
against the wall for a decade or more while there is no market and all 
problems are trivially solved using other technologies?

Are we that idiotic?

You know, I'd like to see a little more respect for people, and for the 
reports they make. Yes, it would be much better if operational staff from 
each of the Fortune 500 companies and larger tertiary operators came to the 
IETF and spoke for themselves. They don't, and that doesn't make their 
opinions or requirements irrelevant. 




From owner-ietf@ietf.org  Fri Oct 10 18:46:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24749
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 17:58:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A851T-0005Lb-L1
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 17:42:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A850p-0005B3-2U
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 17:41:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24157;
	Fri, 10 Oct 2003 17:41:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A850n-00038F-00; Fri, 10 Oct 2003 17:41:25 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A850m-00037z-00; Fri, 10 Oct 2003 17:41:24 -0400
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h9ALdgUt023299;
	Fri, 10 Oct 2003 14:39:42 -0700 (PDT)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AMK57713;
	Fri, 10 Oct 2003 14:35:23 -0700 (PDT)
Message-Id: <6.0.0.22.2.20031010142000.04624670@mira-sjc5-b.cisco.com>
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Fri, 10 Oct 2003 14:29:24 -0700
To: Valdis.Kletnieks@vt.edu
From: Fred Baker <fred@cisco.com>
Subject: Re: Removing features 
Cc: iab@iab.org, iesg@ietf.org, ietf@ietf.org, ipv6@ietf.org
In-Reply-To: <200310101955.h9AJt6RX003398@turing-police.cc.vt.edu>
References: <E320A8529CF07E4C967ECC2F380B0CF902335083@bsebe001.americas.nokia.com>
 <6.0.0.22.2.20031010111733.041e6000@mira-sjc5-b.cisco.com>
 <200310101955.h9AJt6RX003398@turing-police.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:55 PM 10/10/2003, Valdis.Kletnieks@vt.edu wrote:
>All in all, however, I think outright removal, although short-term more 
>painful, will be less troublesome than many years of debugging problems 
>caused by 1918-style leakage of addresses for a "deprecated" feature.

That may be so. It is a third discussion, and is appropriate to the IPv6 list.

The first discussion is Tony's appeal, which is a procedural discussion and 
should not be debated on the basis of whether one agrees or disagrees with 
the particular feature (site-local addresses) but on the basis of whether 
the right consensus development and recognition procedures were followed. 
The Author/Editor of the procedural description has commented that it 
looked problematic to him.

The second is the side point I raised with Margaret: in the general case of 
"things in specifications", removing something from a specification does 
not mean that someone can still use it. Deprecation protects such a usage, 
but removal does not.

The third point, the one you address, is where all this started out, which 
is whether or not one should entertain site-local addresses at all. It is 
relevant to neither the procedural discussion nor the general discussion 
about removing features. But it is clearly something that the IPv6 working 
group needs to have a consensus opinion on. That is actually not the 
subject of either appeal, and should not enter into the discussion of 
either appeal, as it has no bearing on the thing appealed - which is the 
procedural issue. Using the wrong procedure to accomplish the right result 
(if one assumes that this is what happened) is just as bad as using the 
right procedure to produce the wrong result. One wants to use the right 
procedure *and* produce the right result.

When I changed the topic, I changed the subject line... Let's not confuse 
issues. 




From owner-ietf@ietf.org  Fri Oct 10 18:59:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28183
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 18:59:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A864A-0000JX-V3
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 18:48:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A85uc-0008R4-GK
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 18:39:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27670
	for <ietf@ietf.org>; Fri, 10 Oct 2003 18:38:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A85ua-0003vm-00
	for ietf@ietf.org; Fri, 10 Oct 2003 18:39:04 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A85uZ-0003uF-00
	for ietf@ietf.org; Fri, 10 Oct 2003 18:39:04 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9AMi9f13994;
	Fri, 10 Oct 2003 15:44:09 -0700
Date: Fri, 10 Oct 2003 15:38:27 -0700
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v2.00.22)
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <312461970.20031010153827@brandenburg.com>
To: Fred Baker <fred@cisco.com>
CC: The Internet Engineering Task Force <ietf@ietf.org>
Subject: Representative input
In-Reply-To: <6.0.0.22.2.20031010143040.04624358@mira-sjc5-b.cisco.com>
References: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net>
 <3F86FFD5.4050706@nttmcl.com> <3F87250F.7050700@it.su.se>
 <6.0.0.22.2.20031010143040.04624358@mira-sjc5-b.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Fred,

FB> You know, I'd like to see a little more respect for people, and for the 
FB> reports they make. Yes, it would be much better if operational staff from 
FB> each of the Fortune 500 companies and larger tertiary operators came to the 
FB> IETF and spoke for themselves. They don't, and that doesn't make their 
FB> opinions or requirements irrelevant.


You are right.  The problem is with taking input that purports to represent
others, when we have no way to validate that input.

Personally, my technical comments are really on behalf of God, and it is
rather irritating that so many folks keep rejecting His input (that I offer),
but the IETF way of doing things is to take first-person input. I've learned
to live with it, no matter how misguided are all the folks who do not see the
correctness of my comments.

The problem with trying to deal with the problem you present is that it leads
to the one that I've just demonstrated.

What I do not understand is why it is not enough to have some folks say "I
want this thing and I will build it" and to have others say "I want this thing
and I will operate  it" and to consider both sufficient?

Unless and until we have a way of simply, reliably, and validly calculating
the "fan out" a particular bit of input represents, we simply cannot add more
fuzziness to our work by taking some claimed representative input but not
others.

A different problem, of course, is having one group claim that another doesn't
know what it is talking about. For example, the idea that an operator could
claim that a vendor to operators has no understanding of operations, is a bit
strange.  To the extent that the operators are correct, there is a gaping
market opportunity waiting to be filled.

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Fri Oct 10 19:09:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28805
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 19:09:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A86KK-0001mg-Nd
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 19:05:40 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A86Ff-0001RM-1u
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 19:00:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28304;
	Fri, 10 Oct 2003 19:00:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A86Fc-00049b-00; Fri, 10 Oct 2003 19:00:48 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A86Fb-00049P-00; Fri, 10 Oct 2003 19:00:47 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id AC1BE141D8; Fri, 10 Oct 2003 19:00:46 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 06500-02; Fri, 10 Oct 2003 19:00:46 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 345BC14114; Fri, 10 Oct 2003 19:00:45 -0400 (EDT)
Date: Fri, 10 Oct 2003 18:57:24 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: moore@cs.utk.edu, Valdis.Kletnieks@vt.edu, iab@iab.org, iesg@ietf.org,
        ietf@ietf.org, ipv6@ietf.org
Subject: Re: Removing features
Message-Id: <20031010185724.0525853b.moore@cs.utk.edu>
In-Reply-To: <C4319890-FB6A-11D7-B291-00039388672E@muada.com>
References: <200310101955.h9AJt6RX003398@turing-police.cc.vt.edu>
	<C4319890-FB6A-11D7-B291-00039388672E@muada.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > So the basic concept is (in my opinion) broken and needs to be 
> > euthanized.
> 
> This is based on the assumption that leaking RFC 1918 routing 
> information or packets with RFC 1918 source or destination addresses is 
> actually harmful in and of itself.

no, it's based on (among other things) first-hand experience that applications
are expected to be able to use whatever addresses are given to them, regardless
of whether or not those applications employ hosts that are outside of site
boundaries.

> And if you're unable to figure out how to filter private addresses in 
> routing updates or IP traffic, there are numerous non-magical books out 
> there that will tell you how to do this.

attempts to filter such traffic just makes the breakage worse.



From owner-ietf@ietf.org  Fri Oct 10 19:12:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28993
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 19:12:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A86NU-0002Fe-09
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 19:08:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A86MW-00027f-Hd
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 19:07:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28669
	for <ietf@ietf.org>; Fri, 10 Oct 2003 19:07:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A86MU-0004Gv-00
	for ietf@ietf.org; Fri, 10 Oct 2003 19:07:54 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A86MU-0004GW-00
	for ietf@ietf.org; Fri, 10 Oct 2003 19:07:54 -0400
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h9AN6v7E006969;
	Fri, 10 Oct 2003 16:06:57 -0700 (PDT)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AMK67304;
	Fri, 10 Oct 2003 16:02:38 -0700 (PDT)
Message-Id: <6.0.0.22.2.20031010160010.044d2570@mira-sjc5-b.cisco.com>
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Fri, 10 Oct 2003 16:06:17 -0700
To: Dave Crocker <dcrocker@brandenburg.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: Representative input
Cc: The Internet Engineering Task Force <ietf@ietf.org>
In-Reply-To: <312461970.20031010153827@brandenburg.com>
References: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net>
 <3F86FFD5.4050706@nttmcl.com>
 <3F87250F.7050700@it.su.se>
 <6.0.0.22.2.20031010143040.04624358@mira-sjc5-b.cisco.com>
 <312461970.20031010153827@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 03:38 PM 10/10/2003, Dave Crocker wrote:
>A different problem, of course, is having one group claim that another 
>doesn't know what it is talking about. For example, the idea that an 
>operator could claim that a vendor to operators has no understanding of 
>operations, is a bit strange.

Actually, this problem is fundamental, at least at present. We have people 
walking into working groups and throwing up presentations entitled "reality 
check, nobody in this room but us knows what they're talking about" and 
making similar statements in very public and very private fora, when the 
vendors know for certain what they have just spent or are spending a huge 
amount of effort developing at very specific customer requests - in some 
cases, the very networks whose employees are making those presentations - 
and have deployed in customer networks that they aren't allowed to talk about.

I have no problem with not being able to name my customers and yet doing 
for them what they tell me they want done. I do have a problem being basted 
as clueless because my customer isn't standing at the mike asking for it. I 
have a big problem with the level of disrespect being pushed around here. 




From owner-ietf@ietf.org  Fri Oct 10 19:19:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29317
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 19:19:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A86NU-0002Fk-Ay
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 19:08:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A86MX-00027p-Oa
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 19:07:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28673;
	Fri, 10 Oct 2003 19:07:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A86MV-0004H5-00; Fri, 10 Oct 2003 19:07:55 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A86MU-0004GY-00; Fri, 10 Oct 2003 19:07:54 -0400
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h9AN6u7E006958;
	Fri, 10 Oct 2003 16:06:56 -0700 (PDT)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AMK67302;
	Fri, 10 Oct 2003 16:02:37 -0700 (PDT)
Message-Id: <6.0.0.22.2.20031010154931.04532fc0@mira-sjc5-b.cisco.com>
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Fri, 10 Oct 2003 15:50:47 -0700
To: <Margaret.Wasserman@nokia.com>
From: Fred Baker <fred@cisco.com>
Subject: RE: Removing features 
Cc: <Valdis.Kletnieks@vt.edu>, <iab@iab.org>, <iesg@ietf.org>, <ietf@ietf.org>,
        <ipv6@ietf.org>
In-Reply-To: <E320A8529CF07E4C967ECC2F380B0CF90233508D@bsebe001.americas
 .nokia.com>
References: <E320A8529CF07E4C967ECC2F380B0CF90233508D@bsebe001.americas.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 03:03 PM 10/10/2003, Margaret.Wasserman@nokia.com wrote:
>Fred, I hope that this resolves your technical concern about
>this particular case, and I apologize for not making this
>distinction clear in my response to Scott.

yes, it does.

In this case, I was responding to an increase in the complexity of the 
debate. Whether or not you like site locals, the process of the decision 
and such needs to be correct, so bringing up the technical merits or 
demerits of site local actively doesn't help. 




From owner-ietf@ietf.org  Fri Oct 10 19:26:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29727
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 19:26:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A86XA-0003QG-Do
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 19:18:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A86RQ-0002yF-99
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 19:13:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29087;
	Fri, 10 Oct 2003 19:12:50 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A86RO-0004PM-00; Fri, 10 Oct 2003 19:12:58 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A86RN-0004PI-00; Fri, 10 Oct 2003 19:12:57 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9ANCtRX009416;
	Fri, 10 Oct 2003 19:12:55 -0400
Message-Id: <200310102312.h9ANCtRX009416@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: iab@iab.org, iesg@ietf.org, ietf@ietf.org, ipv6@ietf.org
Subject: Re: Removing features 
In-Reply-To: Your message of "Fri, 10 Oct 2003 23:43:20 +0200."
             <C4319890-FB6A-11D7-B291-00039388672E@muada.com> 
References: <C4319890-FB6A-11D7-B291-00039388672E@muada.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-557933910P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 10 Oct 2003 19:12:55 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-557933910P
Content-Type: text/plain; charset=us-ascii

On Fri, 10 Oct 2003 23:43:20 +0200, Iljitsch van Beijnum said:

> And if you're unable to figure out how to filter private addresses in 
> routing updates or IP traffic, there are numerous non-magical books out 
> there that will tell you how to do this.

The problem is that usually, the offending site isn't the one feeling the pain.

We've been doing bogon filtering of 1918 addresses for a LONG time.

The *real* fun is collateral damage - we filter inbound 1918 source
addresses.  A certain clueless Tier-1 numbers their point-to-points
out of 1918 space.  If one of those links tosses an ICMP error,
it gets dropped at our border router.

Does wonders for PMTU discovery when the frag-needed packet gets tossed.

How many sites have to Get It Wrong before 30% of all the packets seen
at the root nameservers are from 1918 space?

> Your argument is self-defeating. If we were to recycle FEC0::/10 this 
> would be the 69.0.0.0/8 but ten times worse. Everybody knew that 
> 69.0.0.0/8 would be assigned at some point, so the people filtering 
> this range knew what they were doing (or at least, they should have). 
> FEC0::/10 on the other hand has been in the specification as a fixed 
> special purpose range for a lot of years, and presumably people have 
> implemented their networks accordingly. Pulling the rug from under them 
> by removing this address range from the spefication and (at least 
> theoretically) allowing it to be reassigned for a different purpose is 
> insane.

Agreed.  On the other hand, if we don't, we're stuck looking at
having inbound FEC0::/10 packets for eternity.

> And that's not even considering the lack of alternatives at this point 
> in time. We may not be able to come up with a reasonable way for 
> networks that implement site local addressing and interconnect with 
> other networks that do the same, but there is still a very real need 
> for addresses that can be used in disconnected IPv6 networks. I believe 
> that forcing people who just want to interconnect a few boxes to do 
> some testing to obtain globally routable IPv6 unicast space is a very 
> bad idea. As long as there aren't any alternatives, FEC0::/10 should be 
> used for this. And even after we have alternatives, FEC0::/10 should 
> forever be set aside to avoid problems.

Well.. OK... *disconnected* networks, I can see the point.  Unfortunately,
unless you make a rule that an IPv6 host will categorically refuse to
accept traffic to/from a FEC0::/10 host if it knows *ANY* other non-link-local
prefixes, it will end up leaking.  Yes, that means if you connect and learn
other prefixes, you need to renumber the site-locals.  It also means that
if you have a router talking to the outside world, you aren't allowed to do
NAT-style games - the router has to pretend your FEC0:/10 hosts don't exist.

> > <mime-attachment>
> 
> Huh?

RFC2440 - OpenPGP Message Format. J. Callas, L. Donnerhacke, H. Finney, R.
     Thayer. November 1998. (Format: TXT=141371 bytes) (Status: PROPOSED
     STANDARD)


--==_Exmh_-557933910P
Content-Type: application/pgp-signature

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

iD8DBQE/hzz2cC3lWbTT17ARAuPzAJ9q6G28lqHCnviJqvvK8OwCz6scFwCgonxZ
m/XVJACnYGYd6D2DLFv4CCc=
=VBOm
-----END PGP SIGNATURE-----

--==_Exmh_-557933910P--



From owner-ietf@ietf.org  Fri Oct 10 20:02:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00832
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 20:02:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A876x-00061n-F3
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 19:55:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A870K-0005jZ-BB
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 19:49:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00417
	for <ietf@ietf.org>; Fri, 10 Oct 2003 19:48:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A870I-0004vy-00
	for ietf@ietf.org; Fri, 10 Oct 2003 19:49:02 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A870H-0004vv-00
	for ietf@ietf.org; Fri, 10 Oct 2003 19:49:01 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id D1826141D5; Fri, 10 Oct 2003 19:49:00 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 10856-05; Fri, 10 Oct 2003 19:48:59 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id E56D11427A; Fri, 10 Oct 2003 19:48:58 -0400 (EDT)
Date: Fri, 10 Oct 2003 19:45:37 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Fred Baker <fred@cisco.com>
Cc: moore@cs.utk.edu, dcrocker@brandenburg.com, ietf@ietf.org
Subject: accusations of cluelessness
Message-Id: <20031010194537.2b8d9318.moore@cs.utk.edu>
In-Reply-To: <6.0.0.22.2.20031010160010.044d2570@mira-sjc5-b.cisco.com>
References: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net>
	<3F86FFD5.4050706@nttmcl.com>
	<3F87250F.7050700@it.su.se>
	<6.0.0.22.2.20031010143040.04624358@mira-sjc5-b.cisco.com>
	<312461970.20031010153827@brandenburg.com>
	<6.0.0.22.2.20031010160010.044d2570@mira-sjc5-b.cisco.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Actually, this problem is fundamental, at least at present. We have people 
> walking into working groups and throwing up presentations entitled "reality 
> check, nobody in this room but us knows what they're talking about" and 
> making similar statements in very public and very private fora, when the 
> vendors know for certain what they have just spent or are spending a huge 
> amount of effort developing at very specific customer requests - in some 
> cases, the very networks whose employees are making those presentations - 
> and have deployed in customer networks that they aren't allowed to talk
> about.

And guess what?  Sometimes those people with the presentations are right
and the customers are wrong.  Sometimes the customers are right and the
folks with the presentations are wrong.  Sometimes they're both right, and
there's a fundamental (perhaps unresolvable) conflict of legitimate needs. 
Sometimes they're both wrong.

There's no way we can hope to sort these things out unless we know the actual 
requirements.  And those aren't always the same thing as what your customer
thinks its requirements are.

But this might explain a lot of the problems we've been having over the past
few years, and so I thank you for this explanation.

> I have no problem with not being able to name my customers and yet doing 
> for them what they tell me they want done. I do have a problem being basted 
> as clueless because my customer isn't standing at the mike asking for it. I 
> have a big problem with the level of disrespect being pushed around here. 

Well, one fairly good indicator of a clueless person is when they insist that
things have to be a certain way, but seem unwilling or unable to explain why.
In a sense, a person that exhibits such behavior *is* clueless, or at least
acting that way, because they aren't able to provide any insight (i.e. clue)
into the discussion.

Perhaps the person being so accused should simply say "my customer insists
on this.  I can't tell you who he is, and I can't amplify on his reasons for
insisting on this."

To which the reply should be "then your customer needs to represent his own
needs here.  Because the solution your customer insists on causes problems, 
and without actually having some insight into your customer's real
requirements, we have no basis on which to try to build a compromise."

Keith



From owner-ietf@ietf.org  Fri Oct 10 20:33:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02332
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 20:33:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A87LT-0007EC-KE
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 20:10:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A87Gz-0006pN-S9
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 20:06:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01107
	for <ietf@ietf.org>; Fri, 10 Oct 2003 20:06:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A87Gy-0005B5-00
	for ietf@ietf.org; Fri, 10 Oct 2003 20:06:16 -0400
Received: from dsl092-066-067.bos1.dsl.speakeasy.net ([66.92.66.67] helo=thrintun.hactrn.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A87Gx-0005Ai-00
	for ietf@ietf.org; Fri, 10 Oct 2003 20:06:15 -0400
Received: from thrintun.hactrn.net (localhost [::1])
	by thrintun.hactrn.net (Postfix) with ESMTP id 375BD18E2
	for <ietf@ietf.org>; Fri, 10 Oct 2003 20:05:45 -0400 (EDT)
Date: Fri, 10 Oct 2003 20:05:45 -0400
From: Rob Austein <sra+ietf@hactrn.net>
To: ietf@ietf.org
Subject: Re: Removing features 
In-Reply-To: <200310102312.h9ANCtRX009416@turing-police.cc.vt.edu>
References: <C4319890-FB6A-11D7-B291-00039388672E@muada.com>
	<200310102312.h9ANCtRX009416@turing-police.cc.vt.edu>
User-Agent: Wanderlust/2.10.0 (Venus) Emacs/20.7 Mule/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20031011000545.375BD18E2@thrintun.hactrn.net>
Sender: owner-ietf@ietf.org
Precedence: bulk

No offense, folks, but if you really must have yet another round of
this interminable discussion, could you please trim the cc: list?
Four copies of each message is a bit much.  Thanks.



From owner-ietf@ietf.org  Fri Oct 10 21:22:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03578
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 21:22:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A88LC-0003g8-2s
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 21:14:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A88C4-0003Q0-4e
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 21:05:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03206
	for <ietf@ietf.org>; Fri, 10 Oct 2003 21:05:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A88C2-0005w2-00
	for ietf@ietf.org; Fri, 10 Oct 2003 21:05:14 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A88C1-0005vv-00
	for ietf@ietf.org; Fri, 10 Oct 2003 21:05:13 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id h9B15BbQ016798
	for ietf@ietf.org env-from <vjs>;
	Fri, 10 Oct 2003 19:05:11 -0600 (MDT)
Date: Fri, 10 Oct 2003 19:05:11 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200310110105.h9B15BbQ016798@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: accusations of cluelessness
References: <20031010194537.2b8d9318.moore@cs.utk.edu
Sender: owner-ietf@ietf.org
Precedence: bulk

> Well, one fairly good indicator of a clueless person is when they insist that
> things have to be a certain way, but seem unwilling or unable to explain why.
> ...

That's all fine, except that it would be more accurate without the words
starting with "but..."  People who absolutely positively know they are
right never are.  Being certain you right is the second best defense
against being penetrated by clues.  (The best defense is being dead.)



> Perhaps the person being so accused should simply say "my customer insists
> on this.  I can't tell you who he is, and I can't amplify on his reasons for
> insisting on this."
>
> To which the reply should be "then your customer needs to represent his own
> needs here.  Because the solution your customer insists on causes problems, 
> and without actually having some insight into your customer's real
> requirements, we have no basis on which to try to build a compromise."

Once upon a time there was an ad hoc group that hashed out interoperable
network protocols based on consensus, but generally did not try to impose
its view of right or wrong.  The group was filled with sentiments along
the lines of "let the market decide."  The group had many academic ties,
but knew better than to try to require any tha participant disclose
anything secret.   This was partly because the incumbant official
standards condemned as completely wrong, unworkable, and heretical
everything the ad hoc group was doing, and it would have been silly for
the ad hoc group to dictate anything.  Then the group became powerful
and infected with delusions of grandeur, omnipotence, and provincialism.
Forever after, or until the next ad hoc group with incomplete pretensions,
it grew increasingly insane and like the older organizations it used to
decry for reasons other than turf wars.

In other words, what happened to the old IETF that would have said
"Site local addresses are utterly stupid and wrong; how large a
block did you say you wanted?"  Where are the old IETF vendors and
other outfits that if told "No, we will not let you have site local
addresses" would have said "Ok, give us a block and by the way, if
I were you, I'd filter routes and packets carrying those addresses."
Isn't that only a slighty bent picture of how the SAP addresses
used for IP on 802 networks came about?

What happened is that they all turned into a bunch of provincial amateur
lawyers, each utterly convinced of omniscience, and with no designing,
implementing, or debugging to do, since otherwise they'd be doing it
instead of spending time writing legalistic appeals and decisions.

This is all utterly silly.  If some outfit decides it must have site
local addresses for any notion of the phrase, it will get them.  The
most you can do is brand sight local anathema and reasonably expect
that pointy haired "IT" bosses will not use them until there is a real
need that overcomes the political risks of violating an oh fish all
fur shure standard.

Just for my own ignorance, how are you going to outlaw the use of
::ffff:10.0.0.0/104 in the bright new IPv6 world?  Why won't 
existing uses of site local addresses be grandfathered?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri Oct 10 22:12:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04577
	for <ietf-web-archive@odin.ietf.org>; Fri, 10 Oct 2003 22:12:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8974-0006eo-0v
	for ietf-list@asgard.ietf.org; Fri, 10 Oct 2003 22:04:10 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A88yG-0006Pf-PF
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 21:55:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04229
	for <ietf@ietf.org>; Fri, 10 Oct 2003 21:54:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A88yE-0006MX-00
	for ietf@ietf.org; Fri, 10 Oct 2003 21:55:02 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A88yE-0006MU-00
	for ietf@ietf.org; Fri, 10 Oct 2003 21:55:02 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 29607141D1; Fri, 10 Oct 2003 21:55:03 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 21196-10; Fri, 10 Oct 2003 21:55:02 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id E6EA81410D; Fri, 10 Oct 2003 21:55:01 -0400 (EDT)
Date: Fri, 10 Oct 2003 21:51:41 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031010215141.38169f40.moore@cs.utk.edu>
In-Reply-To: <200310110105.h9B15BbQ016798@calcite.rhyolite.com>
References: <200310110105.h9B15BbQ016798@calcite.rhyolite.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> In other words, what happened to the old IETF that would have said
> "Site local addresses are utterly stupid and wrong; how large a
> block did you say you wanted?"  

It went away with the old Internet that was mostly an experiment and research
tool used by a relatively small, elite group with largely common interests,
and a fairly high overall clue level (as compared to today), to support a 
relatively small set of apps.

> If some outfit decides it must have site
> local addresses for any notion of the phrase, it will get them. 

well, if they expect apps to actually work with those things, they're 
seriously deluded.  and no amount of money will stop the tide.

> Why won't existing uses of site local addresses be grandfathered?

people can be deluded if they want to.  vendors can encourage those delusions,
and try to sell them products based on those delusions.   the question is 
only whether IETF should lend support to those delusions.






From owner-ietf@ietf.org  Sat Oct 11 00:28:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07798
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 00:28:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8B9r-0004q5-Oa
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 00:15:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Aw2-0004SQ-TA
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 00:00:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06909
	for <ietf@ietf.org>; Sat, 11 Oct 2003 00:00:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Avz-0007KV-00
	for ietf@ietf.org; Sat, 11 Oct 2003 00:00:51 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Avz-0007KS-00
	for ietf@ietf.org; Sat, 11 Oct 2003 00:00:51 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1A8Avy-00008Y-00; Fri, 10 Oct 2003 23:00:50 -0500
Date: Sat, 11 Oct 2003 00:00:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@cs.utk.edu>, Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-ID: <268494564.1065830450@scan.jck.com>
In-Reply-To: <20031010215141.38169f40.moore@cs.utk.edu>
References: <200310110105.h9B15BbQ016798@calcite.rhyolite.com>
 <20031010215141.38169f40.moore@cs.utk.edu>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Friday, 10 October, 2003 21:51 -0400 Keith Moore 
<moore@cs.utk.edu> wrote:

>> In other words, what happened to the old IETF that would have
>> said "Site local addresses are utterly stupid and wrong; how
>> large a block did you say you wanted?"
>
> It went away with the old Internet that was mostly an
> experiment and research tool used by a relatively small, elite
> group with largely common interests, and a fairly high overall
> clue level (as compared to today), to support a  relatively
> small set of apps.

Keith, I don't understand what you are saying here.   As I read 
his note, Vernon isn't saying "make all the applications 
recognize a particular address range and do something special". 
He is saying "ok, we don't think this is useful, but, if it 
would help you to have an address range to do your own thing in 
your own way, addresses are just not that scarce".

I'd love to stamp out all of the wrong-headedness and stupidity 
in the world, but I would not expect to succeed and have largely 
given up trying except for isolated local cases.  Efforts 
through the centuries to make and enforce laws against stupidity 
and  stupid behavior have not been very successful.   I'm not as 
convinced as you are that, to use Vernon's description, "Site 
local addresses are utterly stupid and wrong", but, even if I 
were, I'd be having some trouble convincing myself that taking 
the relevant address range out of the allocation pool and 
leaving it out would be seriously harmful to the network and to 
interoperability.

     john




From owner-ietf@ietf.org  Sat Oct 11 00:38:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08146
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 00:38:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8BS2-0006Md-HF
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 00:33:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8BRN-0006JR-Ij
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 00:33:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08042
	for <ietf@ietf.org>; Sat, 11 Oct 2003 00:33:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8BRK-0007cR-00
	for ietf@ietf.org; Sat, 11 Oct 2003 00:33:14 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8BRK-0007cO-00
	for ietf@ietf.org; Sat, 11 Oct 2003 00:33:14 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 5B282141D6; Sat, 11 Oct 2003 00:33:15 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 27102-05; Sat, 11 Oct 2003 00:33:14 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 02543140BE; Sat, 11 Oct 2003 00:33:14 -0400 (EDT)
Date: Sat, 11 Oct 2003 00:29:52 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <john-ietf@jck.com>
Cc: moore@cs.utk.edu, vjs@calcite.rhyolite.com, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031011002952.6de17a0f.moore@cs.utk.edu>
In-Reply-To: <268494564.1065830450@scan.jck.com>
References: <200310110105.h9B15BbQ016798@calcite.rhyolite.com>
	<20031010215141.38169f40.moore@cs.utk.edu>
	<268494564.1065830450@scan.jck.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Keith, I don't understand what you are saying here.   As I read 
> his note, Vernon isn't saying "make all the applications 
> recognize a particular address range and do something special". 
> He is saying "ok, we don't think this is useful, but, if it 
> would help you to have an address range to do your own thing in 
> your own way, addresses are just not that scarce".

scarcity isn't the problem.  just because something is plentiful
doesn't mean you want to pollute the water supply with it.  and no,
it's not okay to say "you can pollute your own water supply if you
want to", because that stuff flows downstream to everybody else.

> I'd love to stamp out all of the wrong-headedness and stupidity 
> in the world, but I would not expect to succeed and have largely 
> given up trying except for isolated local cases.  Efforts 
> through the centuries to make and enforce laws against stupidity 
> and  stupid behavior have not been very successful.  

nobody is proposing we make or enforce laws against stupidity.
what is being proposed is that we take a practice that is now widely
acknowledged to be stupid, or at least harmful, and say "oops,
sorry, this turns out to have been a bad idea.  please don't do this"

maybe we can't outlaw stupidity, but that doesn't mean we have to
encourage it, or even be silent about it.

> I'm not as 
> convinced as you are that, to use Vernon's description, "Site 
> local addresses are utterly stupid and wrong", but, even if I 
> were, I'd be having some trouble convincing myself that taking 
> the relevant address range out of the allocation pool and 
> leaving it out would be seriously harmful to the network and to 
> interoperability.

well, so would I, and as I understand it, that's just what is being
proposed.

I don't have any problem with IETF/IANA saying "the addresses formerly 
allocated to site-local will never be re-assigned".  I do have 
a problem with IETF giving any support to the notion that it's
reasonable to use site-local addresses.



From owner-ietf@ietf.org  Sat Oct 11 02:20:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22496
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 02:20:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8D0i-0006ml-SD
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 02:13:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Czm-0006VG-OY
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 02:12:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21745;
	Sat, 11 Oct 2003 02:12:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Czj-0000a3-00; Sat, 11 Oct 2003 02:12:51 -0400
Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Czi-0000Zw-00; Sat, 11 Oct 2003 02:12:50 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h9B6Cbd23325;
	Sat, 11 Oct 2003 08:12:40 +0200
Message-ID: <3F879F55.6070009@it.su.se>
Date: Sat, 11 Oct 2003 08:12:37 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
CC: IETF IPv6 Working Group <ipv6@ietf.org>,
        The Internet Engineering Task Force <ietf@ietf.org>,
        The Internet Engineering Steering Group <iesg@ietf.org>,
        The Internet Architecture Board <iab@iab.org>
Subject: Re: Appeal to the IAB on the site-local issue
References: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net> <3F86FFD5.4050706@nttmcl.com> <3F87250F.7050700@it.su.se> <6.0.0.22.2.20031010143040.04624358@mira-sjc5-b.cisco.com>
In-Reply-To: <6.0.0.22.2.20031010143040.04624358@mira-sjc5-b.cisco.com>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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


| You know, I'd like to see a little more respect for people, and for the
| reports they make. Yes, it would be much better if operational staff
| from each of the Fortune 500 companies and larger tertiary operators
| came to the IETF and spoke for themselves. They don't, and that doesn't
| make their opinions or requirements irrelevant.

I do (sort of) apologize for the tone of my email but I simply don't
understand how the debate in the IETF will survive the trend to replace
technical argument with "My Fortune 500 customers tell me foo and thus
foo it must be.". Please tell me how that is fundamentally different
from voting based on (in some way) market share.

Don't take me wrong, I am not an air-headed academic who fails to
understand the importance of beeing able to sell the solutions to
people who are willing to pay for them.

	Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/h59V8Jx8FtbMZncRAscCAKCDb6j3shAQ5ImB1Z0P/j9X75sBMgCgq1iG
k3AN8B/NTdZuE4Vtn8wrdG0=
=NsYR
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Sat Oct 11 02:51:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23528
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 02:51:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8DXc-00032c-L6
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 02:47:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8DX1-0002zH-U5
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 02:47:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23390;
	Sat, 11 Oct 2003 02:47:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8DWz-00013Q-00; Sat, 11 Oct 2003 02:47:13 -0400
Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8DWy-00013N-00; Sat, 11 Oct 2003 02:47:12 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h9B6k4d23374;
	Sat, 11 Oct 2003 08:46:06 +0200
Message-ID: <3F87A72C.5050700@it.su.se>
Date: Sat, 11 Oct 2003 08:46:04 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
CC: Valdis.Kletnieks@vt.edu, iab@iab.org, iesg@ietf.org, ietf@ietf.org,
        ipv6@ietf.org
Subject: Re: Removing features
References: <C4319890-FB6A-11D7-B291-00039388672E@muada.com>
In-Reply-To: <C4319890-FB6A-11D7-B291-00039388672E@muada.com>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

Iljitsch van Beijnum wrote:
<snip>

|
| This is based on the assumption that leaking RFC 1918 routing
| information or packets with RFC 1918 source or destination addresses is
| actually harmful in and of itself. This is a broken assumption. If

Tell that to the root zone operators and brace for the reaction.

	Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/h6cs8Jx8FtbMZncRAunXAJ9zQz+YXtdH6kjZy5BZL5CCYxU/JwCcCYjn
BD6+OpZS7L5Itcg1WfoPzGg=
=BRx5
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Sat Oct 11 03:10:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24185
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 03:10:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8Dq0-0004Zz-Cx
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 03:06:52 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8DjP-00041E-8o
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 03:00:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23934;
	Sat, 11 Oct 2003 02:59:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8DjL-0001GV-00; Sat, 11 Oct 2003 02:59:59 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8DjK-0001GG-00; Sat, 11 Oct 2003 02:59:59 -0400
Subject: RE: Removing features
MIME-Version: 1.0
Date: Fri, 10 Oct 2003 23:59:24 -0700
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C60E@server2003.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Removing features
thread-index: AcOPxEeLrxkiYRECSlaDbzRi1BP3ZwAANPkw
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Leif Johansson" <leifj@it.su.se>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>
Cc: <Valdis.Kletnieks@vt.edu>, <iab@iab.org>, <iesg@ietf.org>, <ietf@ietf.org>,
        <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Leif Johansson wrote:
> Tell that to the root zone operators and brace for the reaction.

Root zone operators, meaning like Verisign?

Michel.




From owner-ietf@ietf.org  Sat Oct 11 03:41:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23531
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 02:51:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8DUj-0002sA-0W
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 02:44:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8DU5-0002oI-7z
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 02:44:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23298;
	Sat, 11 Oct 2003 02:44:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8DU2-00011X-00; Sat, 11 Oct 2003 02:44:10 -0400
Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8DU1-00011U-00; Sat, 11 Oct 2003 02:44:09 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h9B6hvd23366;
	Sat, 11 Oct 2003 08:43:58 +0200
Message-ID: <3F87A6AD.7020308@it.su.se>
Date: Sat, 11 Oct 2003 08:43:57 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Leif Johansson <leifj@it.su.se>
CC: Fred Baker <fred@cisco.com>, IETF IPv6 Working Group <ipv6@ietf.org>,
        The Internet Engineering Task Force <ietf@ietf.org>,
        The Internet Engineering Steering Group <iesg@ietf.org>,
        The Internet Architecture Board <iab@iab.org>
Subject: Re: Appeal to the IAB on the site-local issue
References: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net> <3F86FFD5.4050706@nttmcl.com> <3F87250F.7050700@it.su.se> <6.0.0.22.2.20031010143040.04624358@mira-sjc5-b.cisco.com> <3F879F55.6070009@it.su.se>
In-Reply-To: <3F879F55.6070009@it.su.se>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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


|
| Don't take me wrong, I am not an air-headed academic who fails to
| understand the importance of beeing able to sell the solutions to
| people who are willing to pay for them.

Just to be very clear on this: I don't believe I have seen anyone
in the SL debate who presented an 'academic' argument without insight
into the commercial realities facing vendors. Even the most die-hard
opponents of SL I believe understand this. The failure to accept the
Furtune-500 argument is not the same as not understanding it.

	Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/h6at8Jx8FtbMZncRAqftAJ930kLekkwbg1LzbQJwnkCJdOZXsQCgg2ou
PNGLq07cMTfH94OX8cEJ44M=
=v36K
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Sat Oct 11 04:01:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25330
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 04:01:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8EaO-0006xv-I3
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 03:54:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8ERA-0006eG-6l
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 03:45:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25003
	for <ietf@ietf.org>; Sat, 11 Oct 2003 03:45:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8ER7-0001h0-00
	for ietf@ietf.org; Sat, 11 Oct 2003 03:45:13 -0400
Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8ER6-0001gx-00
	for ietf@ietf.org; Sat, 11 Oct 2003 03:45:13 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h9B7e5d23530;
	Sat, 11 Oct 2003 09:40:05 +0200
Message-ID: <3F87B3D4.1060706@it.su.se>
Date: Sat, 11 Oct 2003 09:40:04 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Michel Py <michel@arneill-py.sacramento.ca.us>
CC: Iljitsch van Beijnum <iljitsch@muada.com>, Valdis.Kletnieks@vt.edu,
        ietf@ietf.org
Subject: Impact from rfc1918 leaks
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C60E@server2003.arneill-py.sacramento.ca.us>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C60E@server2003.arneill-py.sacramento.ca.us>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

Michel Py wrote:
|>Leif Johansson wrote:
|>Tell that to the root zone operators and brace for the reaction.
|
|
| Root zone operators, meaning like Verisign?
|
| Michel.
|

Yes. I recently sat in on a presentation from the operators of
I.root-servers.net. Currently 8-10% of queries are from rfc1918
addrs and 3.6% of queries are for rfc1918 .in-addr.arpa records.
That is not an insignifficant number of queries.

	Cheers Leif

PS I changed the subject and trimmed the cc. It is sometimes
difficult to keep up when you are in a different timezone. I
appologize for the email you replied to which spilled over to
a thread where it did not belong. DS
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/h7PU8Jx8FtbMZncRAuNJAKCt/PyruJz7aLTIjxBSQvueGU3CwgCgokjc
9+0BukBcd0ySLugClYA/QqA=
=5JAc
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Sat Oct 11 05:04:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26353
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 05:04:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8FXT-00025C-SL
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 04:55:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8FWk-000223-VU
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 04:55:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26231
	for <ietf@ietf.org>; Sat, 11 Oct 2003 04:54:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8FWi-0002A7-00
	for ietf@ietf.org; Sat, 11 Oct 2003 04:55:04 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8FWh-0002A4-00
	for ietf@ietf.org; Sat, 11 Oct 2003 04:55:03 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h9B8kTed020112;
	Sat, 11 Oct 2003 10:46:29 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Sat, 11 Oct 2003 10:46:27 +0200
Subject: Re: Impact from rfc1918 leaks
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, Valdis.Kletnieks@vt.edu,
        ietf@ietf.org
To: Leif Johansson <leifj@it.su.se>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <3F87B3D4.1060706@it.su.se>
Message-Id: <66DFB5FC-FBC7-11D7-B291-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On zaterdag, okt 11, 2003, at 09:40 Europe/Amsterdam, Leif Johansson 
wrote:

> |>Tell that to the root zone operators and brace for the reaction.

> | Root zone operators, meaning like Verisign?

> Yes. I recently sat in on a presentation from the operators of
> I.root-servers.net. Currently 8-10% of queries are from rfc1918
> addrs and 3.6% of queries are for rfc1918 .in-addr.arpa records.
> That is not an insignifficant number of queries.

My argument was (is) that having RFC 1918 routes or packets escape 
doesn't add additional problems on top of the fundamental problem that 
routes or packets with the wrong addresses get out. Letting out wrong 
(non-RFC 1918) addresses hurts the legitimate holder of those 
addresses. With RFC 1918 addresses this isn't a problem.

I don't think another 10% load on the root nameservers is a huge deal, 
so I wouldn't use the word "harmful" but I guess this is a special case 
as a resolving nameserver that uses an RFC 1918 address isn't going to 
receive a reply for its queries to the root, so it will keep repeating 
those queries over and over again.

I read a report that only 2% of the hits on the root servers is both 
legitimate and useful anyway.




From owner-ietf@ietf.org  Sat Oct 11 05:37:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27117
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 05:37:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8G7H-0004FF-Qo
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 05:32:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8G4w-000461-U2
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 05:30:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26925
	for <ietf@ietf.org>; Sat, 11 Oct 2003 05:30:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8G4u-0002QP-00
	for ietf@ietf.org; Sat, 11 Oct 2003 05:30:24 -0400
Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8G4t-0002QG-00
	for ietf@ietf.org; Sat, 11 Oct 2003 05:30:23 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h9B9OPd06205;
	Sat, 11 Oct 2003 11:24:25 +0200
Message-ID: <3F87CC48.1000408@it.su.se>
Date: Sat, 11 Oct 2003 11:24:24 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
CC: Michel Py <michel@arneill-py.sacramento.ca.us>, Valdis.Kletnieks@vt.edu,
        ietf@ietf.org
Subject: Re: Impact from rfc1918 leaks
References: <66DFB5FC-FBC7-11D7-B291-00039388672E@muada.com>
In-Reply-To: <66DFB5FC-FBC7-11D7-B291-00039388672E@muada.com>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by klapautius.it.su.se id h9B9OPd06205
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

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

Iljitsch van Beijnum wrote:

<snip>

|
| My argument was (is) that having RFC 1918 routes or packets escape
| doesn't add additional problems on top of the fundamental problem that
| routes or packets with the wrong addresses get out. Letting out wrong
| (non-RFC 1918) addresses hurts the legitimate holder of those addresses.
| With RFC 1918 addresses this isn't a problem.

In the DNS case this is incorrect. What happens is that you get a udp
packet with a return addr of 10.0.0.1 and not only don't you know what
to do with it so you have to throw it away but you can be sure of
getting the *same* query again, and again, and again, presumably from
the *same* client who can't figure out why the reply isn't coming back.

This happens in many protocols which are (contrary to popular belief)
deployed on the Internet today.

|
| I don't think another 10% load on the root nameservers is a huge deal,
| so I wouldn't use the word "harmful" but I guess this is a special case

Again. You'll have to ask the operators of the root-zone if they
consider 11-14% a big deal. Maybe some of them are listening....


| I read a report that only 2% of the hits on the root servers is both
| legitimate and useful anyway.

~From the presentation I refer to which unfortunately is in Swedish but
you can probably read the numbers anyway... :

http://www.iis.se/Internetdagarna/2003/23-robust-dns/id03-23-lars-johanli=
man.pdf

this is clearly not the case. The rfc1918-queries consistute the bulk
of bad queries ("DUMMA fr=E5gor" on page 4 of the presentation). I must
however confess ignorance as to what queries are 'useful'. Presumably
even the rfc1918-queries were deemed useful for someone since they
were sent in the first place.

	Cheers Leif



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/h8xI8Jx8FtbMZncRAmLHAJ9gRWRPZ+oJRRG/Xr+EeLQLRM1FBwCgixT/
sf5v+ALitXYAaXHDGp8PCuM=3D
=3DKMeC
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Sat Oct 11 08:36:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01061
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 08:36:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8Iog-0006Y0-C9
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 08:25:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Inm-0006S5-01
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 08:24:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00906
	for <ietf@ietf.org>; Sat, 11 Oct 2003 08:24:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Inl-0003xL-00
	for ietf@ietf.org; Sat, 11 Oct 2003 08:24:53 -0400
Received: from dhcp4.se.kurtis.pp.se ([195.43.225.73] helo=laptop2.kurtis.autonomica.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Ink-0003xI-00
	for ietf@ietf.org; Sat, 11 Oct 2003 08:24:52 -0400
Received: from kurtis.pp.se (localhost [127.0.0.1])
	by laptop2.kurtis.autonomica.se (8.12.9/8.10.2) with ESMTP id h9BCEgwr001384;
	Sat, 11 Oct 2003 14:14:47 +0200 (CEST)
Date: Sat, 11 Oct 2003 14:14:36 +0200
Subject: Re: Impact from rfc1918 leaks
Content-Type: text/plain; delsp=yes; charset=ISO-8859-1; format=fixed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Iljitsch van Beijnum <iljitsch@muada.com>,
        Michel Py <michel@arneill-py.sacramento.ca.us>,
        Valdis.Kletnieks@vt.edu, ietf@ietf.org
To: Leif Johansson <leifj@it.su.se>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <3F87CC48.1000408@it.su.se>
Message-Id: <7ACBF00A-FBE4-11D7-A99B-000A9598A184@kurtis.pp.se>
Content-Transfer-Encoding: quoted-printable
X-Pgp-Rfc2646-Fix: 1
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

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

> | I don't think another 10% load on the root nameservers is a huge =20
> deal,
> | so I wouldn't use the word "harmful" but I guess this is a special =20=

> case
>
> Again. You'll have to ask the operators of the root-zone if they
> consider 11-14% a big deal. Maybe some of them are listening....

Well we as root-server operator will have to take the costs of =20
upgrading to handle the total query volume....10-15% is then quite a =20
lot.

>
>
> | I read a report that only 2% of the hits on the root servers is both
> | legitimate and useful anyway.
>
> ~=46rom the presentation I refer to which unfortunately is in Swedish =
but
> you can probably read the numbers anyway... :
>
> http://www.iis.se/Internetdagarna/2003/23-robust-dns/id03-23-lars-=20
> johanliman.pdf
>
> this is clearly not the case. The rfc1918-queries consistute the bulk
> of bad queries ("DUMMA fr=E5gor" on page 4 of the presentation). I =
must
> however confess ignorance as to what queries are 'useful'. Presumably
> even the rfc1918-queries were deemed useful for someone since they
> were sent in the first place.

The 2% figure I think was from an analysis of f.root-servers.net. =20
i.root-servers.net seems to be seeing more "valid" queries than f. I =20
guess these figures are different from each server. I think Liman said =20=

that we where seeing 25% garbage in total. I think queries from and =20
about RFC1918 addresses was around 20% of those. It would be fun to see =20=

what percentage of the Ipv6 related queries that are for site-local =20
addresses...

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.2

iQA/AwUBP4f0L6arNKXTPFCVEQLr0wCfQ98s0IuFlle09q5Ceu41dzxY0ncAoMde
WOPfR47J5gKXQbD85232h5YK
=3DuMUn
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Sat Oct 11 10:59:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04656
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 10:59:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8L25-0003G3-Dw
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 10:47:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8KyN-00036P-D6
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 10:43:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04434
	for <ietf@ietf.org>; Sat, 11 Oct 2003 10:43:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8KyM-0004vI-00
	for ietf@ietf.org; Sat, 11 Oct 2003 10:43:58 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8KyL-0004vF-00
	for ietf@ietf.org; Sat, 11 Oct 2003 10:43:57 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id h9BEhrbi008300
	for ietf@ietf.org env-from <vjs>;
	Sat, 11 Oct 2003 08:43:53 -0600 (MDT)
Date: Sat, 11 Oct 2003 08:43:53 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200310111443.h9BEhrbi008300@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: accusations of cluelessness
References: <20031011002952.6de17a0f.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> ...
> I don't have any problem with IETF/IANA saying "the addresses formerly 
> allocated to site-local will never be re-assigned".  I do have 
> a problem with IETF giving any support to the notion that it's
> reasonable to use site-local addresses.

In the real world among adults and outside the delusions of those
who think standards committees are Powerful and In Charge, having
the IETF/IANA say "the addresses formerly allocated to site-local
will never be re-assigned" is indistinguishable from having the
IETF/IANA say "here are some site-local addresses; have fun."

The talk about the evils of site local addresses (and NAT) and the errors
of those who want them may be accurate (I'm inclined to agree), but it
is also functionally indistinguishable from the talk about IPv8 and the
foolisness of those someone likes to call "legacy internet engineers."

Neither side is doing anything to help get IPv6 deployed, but just
the opposite.  Partisans on either side who wanted to see IPv6 in use
by the end of the century would conceded the point just to get on to
something worth doing....well, unless they don't have any designs to
complete, protocols to implement, code to debug, applications to teach
about IPv6, IPv6 networks to get running, or anything else worth doing.

Don't the IESG and IAB have anything better to do than hearing appeals,
counter-appeals, and counter-counter-appeals from people with nothing
better to do than prove their analytic and political powers by arguing
this issue?  Letting the IESG and IAB spend time on this issue is as
bad as letting them decide between IPv8 and IPv16.

Instead of playing childish lawyer games, why not write successors to
RFC 1627 and RFC 1597 or an equivalents to RFC 3027 and let the market
decide?  The market will decide no matter what the IETF says or many
zillion times it says it.

I suppose the next pressing network standards issue the IETF and this
mailing list will consider is the wrongheaded evilness of phrases like
"IP network bandwidth" and whether to use "band-size" or "frequespan"
after "bandwidth" is declared anathema. (See
http://www.postel.org/pipermail/end2end-interest/2003-October/date.html )


Vernon Schryver    vjs@rhyolite.com

P.S. I meant my question about ::FFFF:10.0.0.0/104 seriously.  Are
  those IPv6 site local addresses that are already available and
  impossible to retract or even deprecate?  If so, how can anyone
  justify arguing (not to mention appealing) this issue?



From owner-ietf@ietf.org  Sat Oct 11 13:22:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06732
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 13:22:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8NFU-0001Hs-JS
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 13:09:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8N8h-00017S-8T
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 13:02:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06513
	for <ietf@ietf.org>; Sat, 11 Oct 2003 13:02:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8N8f-0005iX-00
	for ietf@ietf.org; Sat, 11 Oct 2003 13:02:46 -0400
Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8N8e-0005iU-00
	for ietf@ietf.org; Sat, 11 Oct 2003 13:02:45 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h9BH2Vd06703;
	Sat, 11 Oct 2003 19:02:31 +0200
Message-ID: <3F8837A7.6040709@it.su.se>
Date: Sat, 11 Oct 2003 19:02:31 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: ietf@ietf.org
Subject: Re: accusations of cluelessness
References: <20031011002952.6de17a0f.moore@cs.utk.edu> <200310111443.h9BEhrbi008300@calcite.rhyolite.com>
In-Reply-To: <200310111443.h9BEhrbi008300@calcite.rhyolite.com>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

Vernon Schryver wrote:
|>From: Keith Moore <moore@cs.utk.edu>
|

<snip>

| is also functionally indistinguishable from the talk about IPv8 and the
| foolisness of those someone likes to call "legacy internet engineers."

That is a bit below the belt isn't it? It's one thing to step up to
the mike and claim to channel Keith Moore but to be accused of beeing
functionally equivalent to a troll is a different kettle of fish
altogether.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/iDem8Jx8FtbMZncRAtw+AKC9GMvYXWHm2fT/awNnQX93Hjbj6gCfdSG9
H8zjjJ3KMlXbnMlF+CWlOuY=
=Lb2i
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Sat Oct 11 14:34:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08024
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 14:34:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8OR2-0005if-AT
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 14:25:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8OQh-0005fc-Sc
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 14:25:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07837
	for <ietf@ietf.org>; Sat, 11 Oct 2003 14:25:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8OQg-0006FX-00
	for ietf@ietf.org; Sat, 11 Oct 2003 14:25:26 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8OQf-0006FU-00
	for ietf@ietf.org; Sat, 11 Oct 2003 14:25:25 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 284DB140EA; Sat, 11 Oct 2003 14:25:26 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 17637-01; Sat, 11 Oct 2003 14:25:24 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id DCE74141F9; Sat, 11 Oct 2003 14:25:23 -0400 (EDT)
Date: Sat, 11 Oct 2003 14:21:59 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031011142159.2134c09c.moore@cs.utk.edu>
In-Reply-To: <200310111443.h9BEhrbi008300@calcite.rhyolite.com>
References: <20031011002952.6de17a0f.moore@cs.utk.edu>
	<200310111443.h9BEhrbi008300@calcite.rhyolite.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > I don't have any problem with IETF/IANA saying "the addresses formerly 
> > allocated to site-local will never be re-assigned".  I do have 
> > a problem with IETF giving any support to the notion that it's
> > reasonable to use site-local addresses.
> 
> In the real world among adults and outside the delusions of those
> who think standards committees are Powerful and In Charge, having
> the IETF/IANA say "the addresses formerly allocated to site-local
> will never be re-assigned" is indistinguishable from having the
> IETF/IANA say "here are some site-local addresses; have fun."

some people can't read.  I'm not sure what we can do about that.
things that we write can only benefit people who are capable of
reading.  fortunately, some people can read, so writing can have
a useful effect.

> The talk about the evils of site local addresses (and NAT) and the errors
> of those who want them may be accurate (I'm inclined to agree), but it
> is also functionally indistinguishable from the talk about IPv8 and the
> foolisness of those someone likes to call "legacy internet engineers."

some people lack the background to understand technical arguments.
I'm not sure what we can do about that either.  fortunately, some people
do have such a background, and those people do have some influence.
it might not be as much as we'd like, but it's not zero.

> Neither side is doing anything to help get IPv6 deployed, but just
> the opposite.  

further deployment of IPv6 with site-local might be worse than not deploying
it.  ultimately the goal isn't to get IPv6 deployed; it's to get a usable
Internet deployed and make sure it works well.  saying that we should just
go ahead and deploy IPv6 without bothering to make sure that everything works
is what got us into this mess.

> Don't the IESG and IAB have anything better to do than hearing appeals,
> counter-appeals, and counter-counter-appeals from people with nothing
> better to do than prove their analytic and political powers by arguing
> this issue? 

absolutely they do.  but I'm not the one trying to waste their time on a 
senseless appeal.

> Instead of playing childish lawyer games, why not write successors to
> RFC 1627 and RFC 1597 or an equivalents to RFC 3027 and let the market
> decide?  The market will decide no matter what the IETF says or many
> zillion times it says it.

the market has demonstrated that it's not capable of making technically
sound decisions.  letting the market decide is no substitute for good
design.  do we let the market decide whether a plane will crash or a bridge
will stay up?
 
> P.S. I meant my question about ::FFFF:10.0.0.0/104 seriously.  Are
>   those IPv6 site local addresses that are already available and
>   impossible to retract or even deprecate?  If so, how can anyone
>   justify arguing (not to mention appealing) this issue?

of course they're not going to be reallocated for other purposes.  but
it makes perfect sense to say "don't use these; they will cause various
kinds of problems and will cause various kinds of failures"





From owner-ietf@ietf.org  Sat Oct 11 14:53:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08424
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 14:53:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8OnS-0000lb-Lg
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 14:48:58 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8OcY-0006SB-4H
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 14:37:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08186
	for <ietf@ietf.org>; Sat, 11 Oct 2003 14:37:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8OcW-0006MP-00
	for ietf@ietf.org; Sat, 11 Oct 2003 14:37:40 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8OcV-0006MK-00
	for ietf@ietf.org; Sat, 11 Oct 2003 14:37:40 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id h9BIbcap025299
	for ietf@ietf.org env-from <vjs>;
	Sat, 11 Oct 2003 12:37:38 -0600 (MDT)
Date: Sat, 11 Oct 2003 12:37:38 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200310111837.h9BIbcap025299@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: accusations of cluelessness
References: <3F8837A7.6040709@it.su.se>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Leif Johansson <leifj@it.su.se>

> | is also functionally indistinguishable from the talk about IPv8 and the
> | foolisness of those someone likes to call "legacy internet engineers."
>
> That is a bit below the belt isn't it? It's one thing to step up to
> the mike and claim to channel Keith Moore but to be accused of beeing
> functionally equivalent to a troll is a different kettle of fish
> altogether.


At this point, what other purpose is there in repeating the discussion
in this list or by the appeal to the IESG?  Unless the IETF repudiates
BCP 5, aren't we stuck site local addresses forever?  Even if the IETF
did move RFC 1918 to "Historic" and publish a new BCP saying that the
evils of site locals are unnecessary in an IPv6 Internet, wouldn't we
still be stuck with site local addresses forever?

Why doesn't the advice given the IPv8 inventor apply in this case?
Why isn't the next step writing RFCs proving the evils or virues
of site local addresses instead of yet another series of ever more
irrelevant polemics for and against?

The statements about bogus queries of the DNS roots from RFC 1918
addresses or for PTR RRs for RFC 1918 addresses are examples of
irrelevant arguments.  How would deprecating or outlawing IPv6 site
local addresses affect that problem now or ever?  Why will the network
operators who leak such noise change anything if the IETF says they
shouldn't use IPv6 site local addresses?  There are things that could be
done that would control that DNS noise problem, but those actions do
not include rehashing the evils and virtues of IPv6 site locals here.

15 years ago a defining difference between the IETF and the ISO was
that the IETF cared about what happens in practice and the ISO cared
about what happens in theory.  As far as I can tell, the IPv6 site
local discussion on both sides is only about moot theories.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sat Oct 11 15:28:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10172
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 15:28:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8PJD-0002Zh-FB
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 15:21:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8PGR-0002PH-S7
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 15:18:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10041
	for <ietf@ietf.org>; Sat, 11 Oct 2003 15:18:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8PGQ-0006ed-00
	for ietf@ietf.org; Sat, 11 Oct 2003 15:18:54 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8PGQ-0006eW-00
	for ietf@ietf.org; Sat, 11 Oct 2003 15:18:54 -0400
Received: from cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 11 Oct 2003 12:27:13 -0700
Received: from cisco.com (sjc-vpn1-387.cisco.com [10.21.97.131])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h9BJIL5R011417;
	Sat, 11 Oct 2003 12:18:22 -0700 (PDT)
Message-ID: <3F88577D.70504@cisco.com>
Date: Sat, 11 Oct 2003 12:18:21 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: ietf@ietf.org
Subject: Re: accusations of cluelessness
References: <3F8837A7.6040709@it.su.se> <200310111837.h9BIbcap025299@calcite.rhyolite.com>
In-Reply-To: <200310111837.h9BIbcap025299@calcite.rhyolite.com>
X-Enigmail-Version: 0.76.7.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Vernon Schryver wrote:
> 15 years ago a defining difference between the IETF and the ISO was
> that the IETF cared about what happens in practice and the ISO cared
> about what happens in theory.  As far as I can tell, the IPv6 site
> local discussion on both sides is only about moot theories.

Without getting into the other points of this argument, let me suggest 
that Vernon is correct on this point, and in as much as we think 
site-locals are bad we must provide a better alternative.  In order to 
do that we must address the underlying needs for site-locals.  Many have 
written at length on this subject, but it all seems to boil down to this:

    We need a way for sites to be internally stable even when their
    relationship to the world around them changes for whatever reason.

This goes to the heart of identity and service location.  In as much as 
we can address this problem we would do much to nullify the arguments 
for site-locals.  IMHO this is where the IETF, IRTF, and other bodies 
should put our efforts.

Eliot





From owner-ietf@ietf.org  Sat Oct 11 15:28:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10184
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 15:28:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8PM8-0002m9-Gz
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 15:24:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8PM3-0002jD-MF
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 15:24:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10104
	for <ietf@ietf.org>; Sat, 11 Oct 2003 15:24:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8PM2-0006gE-00
	for ietf@ietf.org; Sat, 11 Oct 2003 15:24:42 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8PM1-0006gB-00
	for ietf@ietf.org; Sat, 11 Oct 2003 15:24:42 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 50F9114242; Sat, 11 Oct 2003 15:24:42 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 21717-13; Sat, 11 Oct 2003 15:24:41 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 2A158141FA; Sat, 11 Oct 2003 15:24:41 -0400 (EDT)
Date: Sat, 11 Oct 2003 15:21:17 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031011152117.5c664316.moore@cs.utk.edu>
In-Reply-To: <200310111837.h9BIbcap025299@calcite.rhyolite.com>
References: <3F8837A7.6040709@it.su.se>
	<200310111837.h9BIbcap025299@calcite.rhyolite.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> As far as I can tell, the IPv6 site
> local discussion on both sides is only about moot theories.

That's because you aren't trying to write apps that operate across addressing
realm boundaries, and you're apparently not willing to listen to those who
are.  OTOH, you're quite willing to make abusive statements about things that
you don't  understand.

I used to live in a building that had dumbwaiters and garbage chutes.  Both 
were found to be dangerous.  So they told people to stop using them.  They
didn't try to outlaw them or to make them go away or pretend that they never
existed. And occasionally someone did try to use them.  Fortunately, merely
discouraging their use was sufficient to eliminate most of the danger.

Keith



From owner-ietf@ietf.org  Sat Oct 11 15:57:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11046
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 15:57:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8PmF-00058c-Pw
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 15:51:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8PlO-00052y-Nj
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 15:50:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10877
	for <ietf@ietf.org>; Sat, 11 Oct 2003 15:50:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8PlN-0006xy-00
	for ietf@ietf.org; Sat, 11 Oct 2003 15:50:53 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8PlM-0006xv-00
	for ietf@ietf.org; Sat, 11 Oct 2003 15:50:52 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 58E20141F6; Sat, 11 Oct 2003 15:50:52 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 24810-01; Sat, 11 Oct 2003 15:50:51 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 75925141F2; Sat, 11 Oct 2003 15:50:50 -0400 (EDT)
Date: Sat, 11 Oct 2003 15:47:26 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Eliot Lear <lear@cisco.com>
Cc: moore@cs.utk.edu, vjs@calcite.rhyolite.com, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031011154726.2bdfd652.moore@cs.utk.edu>
In-Reply-To: <3F88577D.70504@cisco.com>
References: <3F8837A7.6040709@it.su.se>
	<200310111837.h9BIbcap025299@calcite.rhyolite.com>
	<3F88577D.70504@cisco.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > and in as much as we think 
> > site-locals are bad we must provide a better alternative.

this kind of thinking is a dead end.   we must not accept all of the
proposed uses of site-locals without question, because some of those
uses are the very source of the problem.

>     We need a way for sites to be internally stable even when their
>     relationship to the world around them changes for whatever reason.

see draft-moore-ipv6-prefix-substitution-aa-00.txt for one attempt to solve
this particular problem within a site.  though I don't think it's sufficient 
to solve it only "within" a site.

Keith




From owner-ietf@ietf.org  Sat Oct 11 15:58:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11141
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 15:58:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8Pq7-0005Oa-I7
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 15:55:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8PpG-0005KZ-44
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 15:54:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11002
	for <ietf@ietf.org>; Sat, 11 Oct 2003 15:54:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8PpE-00070R-00
	for ietf@ietf.org; Sat, 11 Oct 2003 15:54:52 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8PpE-00070O-00
	for ietf@ietf.org; Sat, 11 Oct 2003 15:54:52 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id h9BJslI2009306
	for ietf@ietf.org env-from <vjs>;
	Sat, 11 Oct 2003 13:54:47 -0600 (MDT)
Date: Sat, 11 Oct 2003 13:54:47 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200310111954.h9BJslI2009306@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: accusations of cluelessness
References: <20031011152117.5c664316.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> > As far as I can tell, the IPv6 site
> > local discussion on both sides is only about moot theories.
>
> That's because you aren't trying to write apps that operate across addressing
> realm boundaries, and you're apparently not willing to listen to those who
> are.  

I am working on an application that works accross addressing realm
bondaries.  It involves a global network of thousands clients and
servers on the public Internet talking to each other through NAT boxes,
firewalls, and all sorts of other nasty stuff to the tune of more than
51 million operations the day before yesterday.  There is IPv6 support
in the code that seems to work in the sense of IPv6-only systems
talking to IPv4-only systems indirectly through servers that do both
IPv6 and IPv4.

That nasty stuff causes all kinds of real world trouble as opposed to
academic ivory tower empty talk and chest thumping.  I and others
waste plenty of time every week trying to get people running clients
and servers for that application to fix their NAT boxes and firewalls.
A common firewall error regularly causes Mega-packet/day/site wastes
of bandwidth.


>    OTOH, you're quite willing to make abusive statements about things that 
> you don't  understand.

I understand all to well what's going on here.

> I used to live in a building that had dumbwaiters and garbage chutes.  Both 
> were found to be dangerous.  So they told people to stop using them.  They
> didn't try to outlaw them or to make them go away or pretend that they never
> existed. And occasionally someone did try to use them.  Fortunately, merely
> discouraging their use was sufficient to eliminate most of the danger.

So why are you only repeating what you've said many times before instead
of writing an RFC that will repudiate and replace BCP 5?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sat Oct 11 16:18:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11740
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 16:18:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8Q8W-0007Bo-UI
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 16:14:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Q8H-00075Z-CD
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 16:14:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11694
	for <ietf@ietf.org>; Sat, 11 Oct 2003 16:14:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Q8G-0007FO-00
	for ietf@ietf.org; Sat, 11 Oct 2003 16:14:32 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Q8F-0007FL-00
	for ietf@ietf.org; Sat, 11 Oct 2003 16:14:31 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 38BFD141F6; Sat, 11 Oct 2003 16:14:32 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 26693-06; Sat, 11 Oct 2003 16:14:31 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 0E29514074; Sat, 11 Oct 2003 16:14:31 -0400 (EDT)
Date: Sat, 11 Oct 2003 16:11:07 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031011161107.3da4715e.moore@cs.utk.edu>
In-Reply-To: <200310111954.h9BJslI2009306@calcite.rhyolite.com>
References: <20031011152117.5c664316.moore@cs.utk.edu>
	<200310111954.h9BJslI2009306@calcite.rhyolite.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > > As far as I can tell, the IPv6 site
> > > local discussion on both sides is only about moot theories.
> >
> > That's because you aren't trying to write apps that operate across
> > addressing realm boundaries, and you're apparently not willing to listen
> > to those who are.  
> 
> I am working on an application that works accross addressing realm
> bondaries. 
[...] 
> That nasty stuff causes all kinds of real world trouble 

just a couple of messages ago you were claiming that the discussion was about
moot theories and now you're claiming that it causes real world trouble.
which is it?

> So why are you only repeating what you've said many times before instead
> of writing an RFC that will repudiate and replace BCP 5?

the reason I repeat these things once in awhile is because a significant
fraction of people still don't get it, and they're hindering progress.

the reason I don't try to repudiate BCP 5 is that it's clear that for IPv4
we're out of addresses, and you can't really solve the problem in IPv4 
any other way except to move to another address space. 



From owner-ietf@ietf.org  Sat Oct 11 16:54:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12472
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 16:54:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8Qgi-0000qO-DG
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 16:50:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8QVE-0000Sa-I4
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 16:38:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12284
	for <ietf@ietf.org>; Sat, 11 Oct 2003 16:38:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8QVD-0007Rj-00
	for ietf@ietf.org; Sat, 11 Oct 2003 16:38:15 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8QVC-0007Rg-00
	for ietf@ietf.org; Sat, 11 Oct 2003 16:38:14 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.9/8.12.2) with ESMTP id h9BKc86U011904
	for <ietf@ietf.org>; Sat, 11 Oct 2003 16:38:08 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.9/8.12.2/Submit) id h9BKc7AI011903
	for ietf@ietf.org; Sat, 11 Oct 2003 16:38:07 -0400 (EDT)
Date: Sat, 11 Oct 2003 16:38:07 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200310112038.h9BKc7AI011903@newdev.harvard.edu>
To: ietf@ietf.org
Subject: Re: accusations of cluelessness
Sender: owner-ietf@ietf.org
Precedence: bulk


> the reason I don't try to repudiate BCP 5 is that it's clear that for IPv4
> we're out of addresses,

total BS

http://www.iana.org/assignments/ipv4-address-space



From owner-ietf@ietf.org  Sat Oct 11 17:30:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13404
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 17:30:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8RDI-0002eU-Ru
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 17:23:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8R7K-0002L7-F2
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 17:17:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13273
	for <ietf@ietf.org>; Sat, 11 Oct 2003 17:17:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8R7J-000019-00
	for ietf@ietf.org; Sat, 11 Oct 2003 17:17:37 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8R7G-000015-00
	for ietf@ietf.org; Sat, 11 Oct 2003 17:17:35 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id h9BLHWC4025574
	for ietf@ietf.org env-from <vjs>;
	Sat, 11 Oct 2003 15:17:32 -0600 (MDT)
Date: Sat, 11 Oct 2003 15:17:32 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200310112117.h9BLHWC4025574@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: accusations of cluelessness
References: <20031011161107.3da4715e.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> ...
> > I am working on an application that works accross addressing realm
> > bondaries. 
> [...] 
> > That nasty stuff causes all kinds of real world trouble 
>
> just a couple of messages ago you were claiming that the discussion was about
> moot theories and now you're claiming that it causes real world trouble.
> which is it?

It's not a moot theory that NAT/site local addressing causes real world
problems.  The academic (in the bad sense of the word), ISO style moot
theorizing is the repeated haranguing about the evils of NAT and site
local addresses and the implication that the IETF could issue an edict
and prevent their use in (or near) an IPv6 Internet.


> > So why are you only repeating what you've said many times before instead
> > of writing an RFC that will repudiate and replace BCP 5?
>
> the reason I repeat these things once in awhile is because a significant
> fraction of people still don't get it, and they're hindering progress.

Here progress is measured only by published RFCs.  Repetitions of your
inflammatory litanies of the evils of NAT and site local addresses
prevent progress.  Every replay resets things to the start of the
"we gotta have them; no we don't; you're ignorant and wrong; no you
are; you're so clueless that you use Windows; no you are and your
mother too" groove.  I doubt there is anything that can be done about
NAT and site locals, but one thing is clear.  Your repetitions prevent
progress as much as the manipulations of the IETF's bureaucratic
machinery by your moot debate opponents....no, "debate" is wrong.
When I was an academic debator, the judges allowed only a fixed number
of fairly short opportunities to speak.

You claim that you do the IETF a service by replaying your old position
statements because people are ignorant, stupid, illiterate, and didn't
understand before.  Do you really think that makes sense?


> the reason I don't try to repudiate BCP 5 is that it's clear that for IPv4
> we're out of addresses, and you can't really solve the problem in IPv4 
> any other way except to move to another address space. 

Let's assume that's true.  Where is your I-D for a BCP against site
local addresses for IPv6?

I dislike NAT and site local addresses in theory and practice.  I'm
not volunteering to work on an anti-site-local BCP because I have no
hope that it could affect the real world, and because I don't have a
good enough alternative for site local addresses.  That application
of mine and every other real world application will have to deal with
NAT and site local addresses forever.  Life Sucks, but I've not found
an alternative I prefer.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sat Oct 11 17:47:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13756
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 17:47:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8RTj-0004Vl-IL
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 17:40:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8RTD-0004Qd-JH
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 17:40:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13661
	for <ietf@ietf.org>; Sat, 11 Oct 2003 17:40:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8RTC-0000Al-00
	for ietf@ietf.org; Sat, 11 Oct 2003 17:40:14 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8RTB-0000Ai-00
	for ietf@ietf.org; Sat, 11 Oct 2003 17:40:13 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 4F53014268; Sat, 11 Oct 2003 17:40:14 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 01976-11; Sat, 11 Oct 2003 17:40:13 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 312AF1425D; Sat, 11 Oct 2003 17:40:13 -0400 (EDT)
Date: Sat, 11 Oct 2003 17:36:49 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Scott Bradner <sob@harvard.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031011173649.6231161b.moore@cs.utk.edu>
In-Reply-To: <200310112038.h9BKc7AI011903@newdev.harvard.edu>
References: <200310112038.h9BKc7AI011903@newdev.harvard.edu>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > the reason I don't try to repudiate BCP 5 is that it's clear that for IPv4
> > we're out of addresses,
> 
> total BS

okay, let me state it in more detail:  to the best of my understanding, even
if people were willing to stop using RFC 1918 address space, there aren't
enough global address blocks to accomodate all of the networks now using
private addresses. 



From owner-ietf@ietf.org  Sat Oct 11 17:55:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14043
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 17:55:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8Reb-0005Kr-QP
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 17:52:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8RZd-0004py-79
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 17:46:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13741
	for <ietf@ietf.org>; Sat, 11 Oct 2003 17:46:43 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8RZb-0000D3-00
	for ietf@ietf.org; Sat, 11 Oct 2003 17:46:51 -0400
Received: from h80ad24a2.async.vt.edu ([128.173.36.162] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8RZa-0000Cz-00
	for ietf@ietf.org; Sat, 11 Oct 2003 17:46:51 -0400
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9BLkg6s002849;
	Sat, 11 Oct 2003 17:46:42 -0400
Message-Id: <200310112146.h9BLkg6s002849@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org
Subject: Re: accusations of cluelessness 
In-Reply-To: Your message of "Sat, 11 Oct 2003 16:11:07 EDT."
             <20031011161107.3da4715e.moore@cs.utk.edu> 
References: <20031011152117.5c664316.moore@cs.utk.edu> <200310111954.h9BJslI2009306@calcite.rhyolite.com>
            <20031011161107.3da4715e.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1157173088P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sat, 11 Oct 2003 17:46:40 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sat, 11 Oct 2003 16:11:07 EDT, Keith Moore said:

> the reason I don't try to repudiate BCP 5 is that it's clear that for IPv4
> we're out of addresses, and you can't really solve the problem in IPv4 
> any other way except to move to another address space. 

IANA gave out 61/8 in April 97. 69/8 was August 2002. Except for 3 /8s given to
RIPE, there's NOTHING all the way to 126/8.  56 /8s at a burn rate of 2 /8s per
year gives us some 28 more years.  There's also a big chunk up around 173-190/8
for another few years worth...

There's also reason to suspect that for at least 10-15 years, we've reached
somewhat of a plateau in address consumption - the dot-bomb bubble bursting
released a lot of address space allocated to since-departed end users, and the
relatively flat performance by both Microsoft and PC manufacturers indicates
that in the US/Europe area and most of the more advanced parts of the Pacific
Rim, the majority of people who want to be online already are.  There's high
percentage growth in South America/ Africa/Asia, but quite frankly, there's
some major infrastructure issues those areas have to deal with first.

On the other hand, a /28 and a /16 both flap just as hard....


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

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

iD8DBQE/iHpAcC3lWbTT17ARAvNXAJ0YhuJRxUUz5LW4Rpbp/b20QUvY2gCg8Rka
VEiuMnfyk7pOS3/JCTyLNco=
=MDXx
-----END PGP SIGNATURE-----

--==_Exmh_1157173088P--



From owner-ietf@ietf.org  Sat Oct 11 18:05:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14593
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 18:05:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8Ro3-0007EO-UN
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 18:01:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Rlm-00062m-VA
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 17:59:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14228
	for <ietf@ietf.org>; Sat, 11 Oct 2003 17:59:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Rll-0000OW-00
	for ietf@ietf.org; Sat, 11 Oct 2003 17:59:25 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Rlk-0000OP-00
	for ietf@ietf.org; Sat, 11 Oct 2003 17:59:25 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 8279014261; Sat, 11 Oct 2003 17:59:25 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 04774-01; Sat, 11 Oct 2003 17:59:24 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 70F421415B; Sat, 11 Oct 2003 17:59:24 -0400 (EDT)
Date: Sat, 11 Oct 2003 17:56:00 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031011175600.28b0d8f8.moore@cs.utk.edu>
In-Reply-To: <200310112117.h9BLHWC4025574@calcite.rhyolite.com>
References: <20031011161107.3da4715e.moore@cs.utk.edu>
	<200310112117.h9BLHWC4025574@calcite.rhyolite.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

as much as I feel compelled to respond to personal attacks, I don't think it's
relevant to the IETF discussion list any more.  so I'll respond in private.

Keith



From owner-ietf@ietf.org  Sat Oct 11 18:18:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15826
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 18:18:55 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8S0d-0004Su-1d
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 18:14:47 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8RzK-00040E-Mg
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 18:13:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15424
	for <ietf@ietf.org>; Sat, 11 Oct 2003 18:13:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8RzJ-0000WL-00
	for ietf@ietf.org; Sat, 11 Oct 2003 18:13:25 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8RzI-0000WI-00
	for ietf@ietf.org; Sat, 11 Oct 2003 18:13:24 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 4FCA9141F8; Sat, 11 Oct 2003 18:13:25 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 05383-06; Sat, 11 Oct 2003 18:13:24 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 190C9140CA; Sat, 11 Oct 2003 18:13:24 -0400 (EDT)
Date: Sat, 11 Oct 2003 18:10:00 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Valdis.Kletnieks@vt.edu
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031011181000.00c992ed.moore@cs.utk.edu>
In-Reply-To: <200310112146.h9BLkg6s002849@turing-police.cc.vt.edu>
References: <20031011152117.5c664316.moore@cs.utk.edu>
	<200310111954.h9BJslI2009306@calcite.rhyolite.com>
	<20031011161107.3da4715e.moore@cs.utk.edu>
	<200310112146.h9BLkg6s002849@turing-police.cc.vt.edu>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tell you what.  If you can convince the RIRs that it's feasible to relax the
allocation criteria for IPv4 blocks, and you can convince the ISPs to make
address blocks available to their customers at reasonable prices, I'll happily
co-author one or more drafts that explain:

- why in hindsight RFC 1918 was a bad idea 
- why new sites should use global addresses rather than private addresses
- why sites currently using private addresses should consider migrating 
  to global addresses
- techniques for minimizing the pain of renumbering in IPv4, and
- alternate techniques for providing a similar degree of security to 
  that obtained with private addresses

(I say "co-author" because this is a LOT of ground to cover.  Even if I could
write it all myself, I doubt that I could defend it all against the various 
attacks it would draw from many quarters.)

But last I knew, there were several technical hurdles associated with doing
this - a perceived scarcity of addresses, route flapping, widespread use of
IP addresses in various kinds of configuration files (making renumbering more
difficult), and widespread "conventional wisdom" (supported by marketing BS)
that NATs and private addresses are a Good Thing.  

Keith




From owner-ietf@ietf.org  Sat Oct 11 19:37:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17078
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 19:37:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8T4S-0001zw-Ge
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 19:22:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8T4N-0001vh-GQ
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 19:22:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16854
	for <ietf@ietf.org>; Sat, 11 Oct 2003 19:22:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8T4L-0000sk-00
	for ietf@ietf.org; Sat, 11 Oct 2003 19:22:41 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8T4L-0000sh-00
	for ietf@ietf.org; Sat, 11 Oct 2003 19:22:41 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h9BNMaed029273;
	Sun, 12 Oct 2003 01:22:36 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Sun, 12 Oct 2003 01:22:34 +0200
Subject: Re: accusations of cluelessness 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Valdis.Kletnieks@vt.edu
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200310112146.h9BLkg6s002849@turing-police.cc.vt.edu>
Message-Id: <CB37B61D-FC41-11D7-B291-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On zaterdag, okt 11, 2003, at 23:46 Europe/Amsterdam, 
Valdis.Kletnieks@vt.edu wrote:

>> it's clear that for IPv4 we're out of addresses

> IANA gave out 61/8 in April 97. 69/8 was August 2002. Except for 3 /8s 
> given to
> RIPE, there's NOTHING all the way to 126/8.  56 /8s at a burn rate of 
> 2 /8s per
> year gives us some 28 more years.  There's also a big chunk up around 
> 173-190/8
> for another few years worth...

Have a look at Geoff Huston's latest work in this area: 
http://www.potaroo.net/papers.html

> There's also reason to suspect that for at least 10-15 years, we've 
> reached
> somewhat of a plateau in address consumption - the dot-bomb bubble 
> bursting
> released a lot of address space allocated to since-departed end users,

I don't buy this.

> and the
> relatively flat performance by both Microsoft and PC manufacturers 
> indicates
> that in the US/Europe area and most of the more advanced parts of the 
> Pacific
> Rim, the majority of people who want to be online already are.

Maybe there is something to this, but there is also a significant 
possibility that there isn't. There is still a large move from dial-up 
to "always on" types of access (cable, DSL) going on. It's likely the 
same will happen for mobile: today you dial in and use an address for a 
few minutes, in the future you're going to occupy an address 24/7 with 
your IP-enabled cell phone.

It looks like the growth in address usage is linear. Since there are 
significant factors driving this growth down (use of private addressing 
with or without NAT, addressless virtual servers, denser packing of 
subnets) the actual need for addresses must still be going up pretty 
fast.

But at some point the subnets are as dense as they're going to get, and 
everything that can be virtualized or NATed is. At this point life is 
going to become much more interesting.

I guess it all depends on how you look at it: either the glass is half 
empty (still 1.5 billion addresses still free) or it's 97% full (31 
bits down, one to go).

Iljitsch van Beijnum




From owner-ietf@ietf.org  Sat Oct 11 19:56:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17640
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 19:56:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8TVY-0003V9-0I
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 19:50:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8TKG-000329-BH
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 19:39:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17160
	for <ietf@ietf.org>; Sat, 11 Oct 2003 19:38:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8TKB-00010i-00
	for ietf@ietf.org; Sat, 11 Oct 2003 19:39:03 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8TKA-00010a-00
	for ietf@ietf.org; Sat, 11 Oct 2003 19:39:02 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id h9BNd2i2017216
	for ietf@ietf.org env-from <vjs>;
	Sat, 11 Oct 2003 17:39:02 -0600 (MDT)
Date: Sat, 11 Oct 2003 17:39:02 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200310112339.h9BNd2i2017216@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: accusations of cluelessness
References: <20031011175600.28b0d8f8.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

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

> as much as I feel compelled to respond to personal attacks, I don't think it's
> relevant to the IETF discussion list any more.  so I'll respond in private.

If I'd known you were going to switch from public+"courtesy copy" to
private lectures on how much I don't know and what am not doing, I
would have put your address back into my mail defenses.  As it is,
I'm almost but not quite moved to publish the private epistle that
arrived before I got my defenses repaired.

Your closing words in that private message are a motto you might consider
acting on.   In case you've forgotten, they were "Get over it."


What kind of pathology would lead someone to reason that private
flames would be more welcome or effective than public flames? 
Am I supposed to be more readily convince in private that I'm
ignorant and foolish?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Sat Oct 11 20:10:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18063
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 20:10:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8Tj6-0005CP-FK
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 20:04:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Tip-00058I-9s
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 20:04:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17976
	for <ietf@ietf.org>; Sat, 11 Oct 2003 20:04:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Tin-0001HO-00
	for ietf@ietf.org; Sat, 11 Oct 2003 20:04:29 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Tin-0001HL-00
	for ietf@ietf.org; Sat, 11 Oct 2003 20:04:29 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.9/8.12.2) with ESMTP id h9C04O6U012385
	for <ietf@ietf.org>; Sat, 11 Oct 2003 20:04:24 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.9/8.12.2/Submit) id h9C04OSN012384
	for ietf@ietf.org; Sat, 11 Oct 2003 20:04:24 -0400 (EDT)
Date: Sat, 11 Oct 2003 20:04:24 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200310120004.h9C04OSN012384@newdev.harvard.edu>
To: ietf@ietf.org
Subject: Re: accusations of cluelessness
Sender: owner-ietf@ietf.org
Precedence: bulk


> If you can convince the RIRs that it's feasible to relax the
> allocation criteria for IPv4 blocks,

Keith

Just what would you suggest in the way of relaxing?

The basic rule is now - if you (the requester) can show you are going to 
use the space you can get it.

Relaxing from that would seem to indicate that the RIR should provide
more space than the requester thinks they can use.

That does not seem like a real good idea.

Scott



From owner-ietf@ietf.org  Sat Oct 11 21:31:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19644
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 21:31:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8V0D-0002Gn-6k
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 21:26:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Uxp-000277-DK
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 21:24:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19495
	for <ietf@ietf.org>; Sat, 11 Oct 2003 21:23:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Uxn-0001m4-00
	for ietf@ietf.org; Sat, 11 Oct 2003 21:24:03 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Uxn-0001m1-00
	for ietf@ietf.org; Sat, 11 Oct 2003 21:24:03 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.9/8.12.2) with ESMTP id h9C1Nx6U012508
	for <ietf@ietf.org>; Sat, 11 Oct 2003 21:23:59 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.9/8.12.2/Submit) id h9C1NxsL012507
	for ietf@ietf.org; Sat, 11 Oct 2003 21:23:59 -0400 (EDT)
Date: Sat, 11 Oct 2003 21:23:59 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200310120123.h9C1NxsL012507@newdev.harvard.edu>
To: ietf@ietf.org
Subject: Re: accusations of cluelessness
Sender: owner-ietf@ietf.org
Precedence: bulk


> If you have $2500 to ante up for the allocation.

you might take a look at the RIR web pages - it does not cost
an ISP $2500 to get additional address space allocated  - the
additional fee for additional space for large ISPs is generally zero.

end site allocations are a different story but there are a few routing
table issues with doing many of those

Scott



From owner-ietf@ietf.org  Sat Oct 11 22:16:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19642
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 21:31:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8Uth-00020n-A9
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 21:19:49 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8UtL-0001wi-Cu
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 21:19:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19406
	for <ietf@ietf.org>; Sat, 11 Oct 2003 21:19:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8UtJ-0001kL-00
	for ietf@ietf.org; Sat, 11 Oct 2003 21:19:25 -0400
Received: from 143.230.33.65.cfl.rr.com ([65.33.230.143] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8UtF-0001kI-00
	for ietf@ietf.org; Sat, 11 Oct 2003 21:19:25 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1A88rr-0005Aw-00; Fri, 10 Oct 2003 21:48:27 -0400
Date: Fri, 10 Oct 2003 21:48:23 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Scott  Bradner <sob@harvard.edu>
cc: ietf@ietf.org
Subject: Re: accusations of cluelessness
In-Reply-To: <200310120004.h9C04OSN012384@newdev.harvard.edu>
Message-ID: <Pine.LNX.4.44.0310102147480.19887-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 11 Oct 2003, Scott  Bradner wrote:

>
> > If you can convince the RIRs that it's feasible to relax the
> > allocation criteria for IPv4 blocks,
>
> Keith
>
> Just what would you suggest in the way of relaxing?
>
> The basic rule is now - if you (the requester) can show you are going to
> use the space you can get it.

If you have $2500 to ante up for the allocation.


>
> Relaxing from that would seem to indicate that the RIR should provide
> more space than the requester thinks they can use.
>
> That does not seem like a real good idea.
>
> Scott
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81/




From owner-ietf@ietf.org  Sat Oct 11 22:22:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20774
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 22:22:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8Vmo-0006R9-Sa
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 22:16:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Vey-00064o-Qe
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 22:08:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20401
	for <ietf@ietf.org>; Sat, 11 Oct 2003 22:08:31 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Vew-00026b-00
	for ietf@ietf.org; Sat, 11 Oct 2003 22:08:38 -0400
Received: from h80ad24a5.async.vt.edu ([128.173.36.165] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Vev-00026Y-00
	for ietf@ietf.org; Sat, 11 Oct 2003 22:08:37 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9C28U6s010850;
	Sat, 11 Oct 2003 22:08:30 -0400
Message-Id: <200310120208.h9C28U6s010850@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: shogunx <shogunx@sleekfreak.ath.cx>
Cc: ietf@ietf.org
Subject: Re: accusations of cluelessness 
In-Reply-To: Your message of "Fri, 10 Oct 2003 21:48:23 EDT."
             <Pine.LNX.4.44.0310102147480.19887-100000@sleekfreak.ath.cx> 
References: <Pine.LNX.4.44.0310102147480.19887-100000@sleekfreak.ath.cx>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1286225154P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sat, 11 Oct 2003 22:08:29 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Fri, 10 Oct 2003 21:48:23 EDT, shogunx said:

> If you have $2500 to ante up for the allocation.

If the $2,500 is a stumbling block, you're probably WAY undercapitalized for
the project in the first place....

Why do you need your own allocation?  Either because you're getting pretty
big, or you want to multihome a /26 or some such tiny allocation.

Let's say you're getting big enough to want your own /19 - even if you're in a /
20 and growing, that's still 4,000 machines (either your own or customers)..
plus admin salaries, rent, etc, you're a fairly good sized business.  That $2500
shouldn't be a breaking cost - if it is, you're close to failing already and need to be
thinking about consolidating, not expanding...

If you're tiny and trying to multihome, and can't afford $2500, you're probably
not going to be able to afford the router and 2 or more leased lines, and the
expertise to do it - you probably should be looking at a colo instead.


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

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

iD8DBQE/iLedcC3lWbTT17ARAiMNAJ9GqXXzI4jvwFikfQibF68IVcxNxQCg8tWn
NhoNQuWvFgkoPpkThpQC8g4=
=55ZW
-----END PGP SIGNATURE-----

--==_Exmh_1286225154P--



From owner-ietf@ietf.org  Sat Oct 11 23:39:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22954
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 23:39:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8WvS-00034S-Gw
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 23:29:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Wqk-0002u6-HP
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 23:24:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22464
	for <ietf@ietf.org>; Sat, 11 Oct 2003 23:24:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Wqi-0002r0-00
	for ietf@ietf.org; Sat, 11 Oct 2003 23:24:52 -0400
Received: from 143.230.33.65.cfl.rr.com ([65.33.230.143] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Wqe-0002ql-00
	for ietf@ietf.org; Sat, 11 Oct 2003 23:24:51 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1A8AdH-0005Ef-00; Fri, 10 Oct 2003 23:41:31 -0400
Date: Fri, 10 Oct 2003 23:41:03 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Scott  Bradner <sob@harvard.edu>
cc: ietf@ietf.org
Subject: Re: accusations of cluelessness
In-Reply-To: <200310120123.h9C1NxsL012507@newdev.harvard.edu>
Message-ID: <Pine.LNX.4.44.0310102339420.20128-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 11 Oct 2003, Scott  Bradner wrote:

>
> > If you have $2500 to ante up for the allocation.
>
> you might take a look at the RIR web pages - it does not cost
> an ISP $2500 to get additional address space allocated  - the
> additional fee for additional space for large ISPs is generally zero.

ahhh.  additional address space.  i was referring to initial address
space.  from IANA anyway.


>
> end site allocations are a different story but there are a few routing
> table issues with doing many of those
>
> Scott
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81/




From owner-ietf@ietf.org  Sat Oct 11 23:45:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23323
	for <ietf-web-archive@odin.ietf.org>; Sat, 11 Oct 2003 23:45:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8X74-0004qM-OS
	for ietf-list@asgard.ietf.org; Sat, 11 Oct 2003 23:41:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8X6W-0004h2-He
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 23:41:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23056
	for <ietf@ietf.org>; Sat, 11 Oct 2003 23:41:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8X6U-00037O-00
	for ietf@ietf.org; Sat, 11 Oct 2003 23:41:10 -0400
Received: from 143.230.33.65.cfl.rr.com ([65.33.230.143] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8X6R-00036o-00
	for ietf@ietf.org; Sat, 11 Oct 2003 23:41:10 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1A8As3-0005Ez-00; Fri, 10 Oct 2003 23:56:47 -0400
Date: Fri, 10 Oct 2003 23:56:22 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Valdis.Kletnieks@vt.edu
cc: ietf@ietf.org
Subject: Re: accusations of cluelessness 
In-Reply-To: <200310120208.h9C28U6s010850@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0310102344480.20128-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Vladis,


> On Fri, 10 Oct 2003 21:48:23 EDT, shogunx said:
>
> > If you have $2500 to ante up for the allocation.
>
> If the $2,500 is a stumbling block, you're probably WAY undercapitalized for
> the project in the first place....
>

A situation I'm used to.

> Why do you need your own allocation?  Either because you're getting pretty
> big, or you want to multihome a /26 or some such tiny allocation.

Or you are building new infrastructure.

>
> Let's say you're getting big enough to want your own /19 - even if you're in a /
> 20 and growing, that's still 4,000 machines (either your own or customers)..
> plus admin salaries, rent, etc, you're a fairly good sized business.  That $2500
> shouldn't be a breaking cost - if it is, you're close to failing already and need to be
> thinking about consolidating, not expanding...
>

Actually just starting to do thing this way.  In the past I have found it
expedient to simply bypass any security measures and connect a machine
wherever necessary.  And the point is, who decided that IP addresses are a
commodity item anyway?

> If you're tiny and trying to multihome, and can't afford $2500, you're probably
> not going to be able to afford the router and 2 or more leased lines, and the
> expertise to do it - you probably should be looking at a colo instead.
>

No need to multihome.  In fact, for this PARTICULAR application, I can
probably use a free v6 /24 from a tunnel broker routed over a private
address network, although the users will probably notice the packet
latency from their terminal to the tunnel broker, and its a nasty kludge.

Router?  I can build that if necessary.

Colo?  Why when I have access to a Tier 1 NOC with backbone running
through it, though that is 600 miles away.


Scott
>

sleekfreak pirate broadcast
world tour 2002-3
live from the pirate hideout
http://sleekfreak.ath.cx:81/




From owner-ietf@ietf.org  Sun Oct 12 00:41:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24471
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 00:41:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8XvO-00006I-K6
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 00:33:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Xu7-0008PS-95
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 00:32:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24352
	for <ietf@ietf.org>; Sun, 12 Oct 2003 00:32:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Xu5-0003bj-00
	for ietf@ietf.org; Sun, 12 Oct 2003 00:32:25 -0400
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Xu4-0003bP-00
	for ietf@ietf.org; Sun, 12 Oct 2003 00:32:24 -0400
Received: from INET-VRS-02.redmond.corp.microsoft.com ([157.54.8.110]) by mail2.microsoft.com with Microsoft SMTPSVC(6.0.3790.1041);
	 Sat, 11 Oct 2003 21:31:55 -0700
Received: from 157.54.6.197 by INET-VRS-02.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Sat, 11 Oct 2003 21:31:53 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by INET-HUB-06.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Sat, 11 Oct 2003 21:31:41 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 11 Oct 2003 21:28:15 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Sat, 11 Oct 2003 21:31:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: accusations of cluelessness
Date: Sat, 11 Oct 2003 21:31:53 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA0594857B@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: accusations of cluelessness
thread-index: AcOQCQWUfdXzryMQRKSIPzQV6Z6AMAAIoylQ
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Vernon Schryver" <vjs@calcite.rhyolite.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 12 Oct 2003 04:31:54.0079 (UTC) FILETIME=[C36F26F0:01C39079]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


> > I don't have any problem with IETF/IANA saying "the addresses
formerly
> > allocated to site-local will never be re-assigned".  I do have
> > a problem with IETF giving any support to the notion that it's
> > reasonable to use site-local addresses.
>=20
> In the real world among adults and outside the delusions of those
> who think standards committees are Powerful and In Charge, having
> the IETF/IANA say "the addresses formerly allocated to site-local
> will never be re-assigned" is indistinguishable from having the
> IETF/IANA say "here are some site-local addresses; have fun."

I think Vernon hits the nail on the head. A lot of the IETF's energy
appears to be now devoted to shutting down someone else's ideas, on the
basis that we, the clueful, must protect the Internet against the
attacks of greedy and incompetent amateurs. In short, I see a lot of
negative energy floating around.

It is perfectly fine to review a specification, understand the intent of
the original designer, and suggest ways to better achieve the same
result. That is exactly what working groups are supposed to do. It is
also perfectly fine, if the original designer won't change their design,
to publish an alternative design that hopefully works better, and then
rely on market forces to sort it out. But it is not fine to try to
prevent the original designer from actually shipping products, either by
preventing publication of the specification or by trying to prevent
deployment.

The publication game can be played in the working group, but the best
tricks are used by the IESG. The two delaying tactics that I have seen
so far are to request complete consensus on a "requirement document"
before any progress can be made on a system design, or by simply sitting
on a document submitted by the working group and let it rot in the IESG
queue. The requirement trick is probably the most efficient: in
practice, it can delay any work by two or three years. However, in the
days of the web, the IESG can only control publication as an RFC; the
unloved specification most often ends up published elsewhere. There is a
lot of damage done to the IETF, but the ideas, good or bad, get
documented. To really exercise power, one has to prevent deployment.

The practical way to prevent deployment is to control the assignment of
a resource required for the unloved design. The normal loop is through
requiring IANA that some numbers can only be allocated following
publication of an RFC. For example, a new MIME type can only be
registered that way. Very often, this control is only nominal. Fore
example, nothing prevents consenting software implementations to use
unregistered MIME types. One of the remaining strongholds of the IESG,
however, is the assignment of a range of addresses for a specific
purpose. Today, the IANA will not do that without IESG approval, hence
all the hoopla about site local addresses.=20

I wish the attitude would change, but I am not too hopeful. So, maybe a
solution is to as much as possible remove blocking powers from the IETF
process. In particular, we should do something about the control of
address ranges assignment. OK, for IPv4 that will be hard, but IPv6 has
more resource. But maybe we should have a specific registry that assigns
ranges of addresses to specific purposes, and have that registry managed
in much the same way as the current registry of port numbers.

-- Christian Huitema




From owner-ietf@ietf.org  Sun Oct 12 01:15:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25295
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 01:15:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8YTG-0003Ej-Fk
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 01:08:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8YST-00039i-PB
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 01:07:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25113
	for <ietf@ietf.org>; Sun, 12 Oct 2003 01:07:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8YSR-0003u8-00
	for ietf@ietf.org; Sun, 12 Oct 2003 01:07:55 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8YSR-0003u5-00
	for ietf@ietf.org; Sun, 12 Oct 2003 01:07:55 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id D337414120; Sun, 12 Oct 2003 01:07:55 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 00375-11; Sun, 12 Oct 2003 01:07:55 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id C16B714036; Sun, 12 Oct 2003 01:07:54 -0400 (EDT)
Date: Sun, 12 Oct 2003 01:04:29 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031012010429.0059263c.moore@cs.utk.edu>
In-Reply-To: <200310112339.h9BNd2i2017216@calcite.rhyolite.com>
References: <20031011175600.28b0d8f8.moore@cs.utk.edu>
	<200310112339.h9BNd2i2017216@calcite.rhyolite.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> What kind of pathology would lead someone to reason that private
> flames would be more welcome or effective than public flames? 

you deserved what you got in private email.  the list didn't.



From owner-ietf@ietf.org  Sun Oct 12 01:35:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25724
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 01:35:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8YpY-0004Zg-HB
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 01:31:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Ymm-0004PO-LY
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 01:28:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25629
	for <ietf@ietf.org>; Sun, 12 Oct 2003 01:28:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Ymk-00048Q-00
	for ietf@ietf.org; Sun, 12 Oct 2003 01:28:54 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Ymk-00048N-00
	for ietf@ietf.org; Sun, 12 Oct 2003 01:28:54 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 752C31424A; Sun, 12 Oct 2003 01:28:55 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 03107-03; Sun, 12 Oct 2003 01:28:54 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id E18D5141A7; Sun, 12 Oct 2003 01:28:53 -0400 (EDT)
Date: Sun, 12 Oct 2003 01:25:28 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Scott Bradner <sob@harvard.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031012012528.41dd0367.moore@cs.utk.edu>
In-Reply-To: <200310120004.h9C04OSN012384@newdev.harvard.edu>
References: <200310120004.h9C04OSN012384@newdev.harvard.edu>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Just what would you suggest in the way of relaxing?

since I view this as a hypothetical situation anyway (and one that isn't
likely to happen in the real world) I don't think it's necessary to pin down
exactly how they'd go about relaxing the criteria - only to realize that it is
possible to relax those criteria.they could ask for less money, or less
supporting evidence, or they could give out bigger blocks.  whatever.  

note that I didn't say it was a good idea to do this.  but if, as some people
assert, the v4 address shortage is a myth - then I'd be happy to try to work
on getting people to move away from NAT.  personally I still believe there's
some substance to the address shortage.  but I'd love to find out that this
isn't the case.




From owner-ietf@ietf.org  Sun Oct 12 01:35:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25727
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 01:35:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8YpY-0004ZQ-4K
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 01:31:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Yff-0004N3-JV
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 01:21:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25552
	for <ietf@ietf.org>; Sun, 12 Oct 2003 01:21:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Yfd-000464-00
	for ietf@ietf.org; Sun, 12 Oct 2003 01:21:33 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Yfc-000461-00
	for ietf@ietf.org; Sun, 12 Oct 2003 01:21:32 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 150F4141A7; Sun, 12 Oct 2003 01:21:34 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 02158-06; Sun, 12 Oct 2003 01:21:33 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 33C9C14189; Sun, 12 Oct 2003 01:21:31 -0400 (EDT)
Date: Sun, 12 Oct 2003 01:18:05 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Christian Huitema" <huitema@windows.microsoft.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031012011805.67ac834e.moore@cs.utk.edu>
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA0594857B@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References: <DAC3FCB50E31C54987CD10797DA511BA0594857B@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> It is perfectly fine to review a specification, understand the intent of
> the original designer, and suggest ways to better achieve the same
> result. That is exactly what working groups are supposed to do. It is
> also perfectly fine, if the original designer won't change their design,
> to publish an alternative design that hopefully works better, and then
> rely on market forces to sort it out. But it is not fine to try to
> prevent the original designer from actually shipping products, either by
> preventing publication of the specification or by trying to prevent
> deployment.

On the contrary, it is our duty to do all of these things.

What is not fine is for participants to expect IETF to lend its support to bad
designs.



From owner-ietf@ietf.org  Sun Oct 12 02:06:07 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02572
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 02:06:07 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8ZGc-0007b1-4B
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 01:59:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8ZGV-0007Wd-8W
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 01:59:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26346
	for <ietf@ietf.org>; Sun, 12 Oct 2003 01:59:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8ZGT-0004Pu-00
	for ietf@ietf.org; Sun, 12 Oct 2003 01:59:37 -0400
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8ZGS-0004Pk-00
	for ietf@ietf.org; Sun, 12 Oct 2003 01:59:36 -0400
Received: from inet-vrs-04.redmond.corp.microsoft.com ([157.54.8.149]) by mail4.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 11 Oct 2003 22:59:07 -0700
Received: from 157.54.8.109 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Sat, 11 Oct 2003 22:58:57 -0700
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-hub-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 11 Oct 2003 22:58:57 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Sat, 11 Oct 2003 22:59:08 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Sat, 11 Oct 2003 22:58:56 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: accusations of cluelessness
Date: Sat, 11 Oct 2003 22:58:55 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA0594858C@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: accusations of cluelessness
thread-index: AcOQgLTT0AzWhtflSvODeevhIXnmhwAAECpA
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <ietf@ietf.org>
X-OriginalArrivalTime: 12 Oct 2003 05:58:56.0144 (UTC) FILETIME=[EC070900:01C39085]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> > It is perfectly fine to review a specification, understand the
intent of
> > the original designer, and suggest ways to better achieve the same
> > result. That is exactly what working groups are supposed to do. It
is
> > also perfectly fine, if the original designer won't change their
design,
> > to publish an alternative design that hopefully works better, and
then
> > rely on market forces to sort it out. But it is not fine to try to
> > prevent the original designer from actually shipping products,
either by
> > preventing publication of the specification or by trying to prevent
> > deployment.
>=20
> On the contrary, it is our duty to do all of these things.
>=20
> What is not fine is for participants to expect IETF to lend its
support to
> bad designs.

Well, who made us kings? It is one thing to work and publish designs
that hopefully will be good. It is quite another to judge someone else's
design and brand it bad. It is far better to let the market be judge.

-- Christian Huitema




From owner-ietf@ietf.org  Sun Oct 12 03:35:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10888
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 03:35:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8acn-0004Ry-Hp
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 03:26:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8aaw-0004De-8v
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 03:24:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10748
	for <ietf@ietf.org>; Sun, 12 Oct 2003 03:24:41 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8aat-0005HA-00
	for ietf@ietf.org; Sun, 12 Oct 2003 03:24:47 -0400
Received: from h80ad2695.async.vt.edu ([128.173.38.149] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8aas-0005H7-00
	for ietf@ietf.org; Sun, 12 Oct 2003 03:24:46 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9C7Oc6s018972;
	Sun, 12 Oct 2003 03:24:39 -0400
Message-Id: <200310120724.h9C7Oc6s018972@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Christian Huitema <huitema@windows.microsoft.com>
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: accusations of cluelessness 
In-Reply-To: Your message of "Sat, 11 Oct 2003 22:58:55 PDT."
             <DAC3FCB50E31C54987CD10797DA511BA0594858C@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com> 
References: <DAC3FCB50E31C54987CD10797DA511BA0594858C@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-714780876P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sun, 12 Oct 2003 03:24:37 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-714780876P
Content-Type: text/plain; charset=us-ascii

On Sat, 11 Oct 2003 22:58:55 PDT, Christian Huitema said:
> Well, who made us kings? It is one thing to work and publish designs
> that hopefully will be good. It is quite another to judge someone else's
> design and brand it bad. 

On the other hand, the same skills that allow us to evaluate our own
designs as workable should also be able to evaluate other's designs for
workability.  And if we find fatal flaws in a design, it is our responsibility
to say so, rather than let it be deployed in the real world.

This applies whether we are civil engineers, aeronautic designers, or
software creators.

>                    It is far better to let the market be judge.

If letting the market be judge is a good idea, why is such a large percentage
of my bandwidth chewed up by emails bearing viruses?

--==_Exmh_-714780876P
Content-Type: application/pgp-signature

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

iD8DBQE/iQGzcC3lWbTT17ARAg9eAKCSGlIYH8PFzd+YFcYe0FtrKkg8jgCgz27C
01O6swA+zGRYq6GgYrr6TGQ=
=CXCJ
-----END PGP SIGNATURE-----

--==_Exmh_-714780876P--



From owner-ietf@ietf.org  Sun Oct 12 03:52:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11304
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 03:52:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8ay5-00068O-OK
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 03:48:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8axV-0005xa-Pi
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 03:48:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11177
	for <ietf@ietf.org>; Sun, 12 Oct 2003 03:48:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8axT-0005Qh-00
	for ietf@ietf.org; Sun, 12 Oct 2003 03:48:07 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8axS-0005Qe-00
	for ietf@ietf.org; Sun, 12 Oct 2003 03:48:06 -0400
Received: from muada.com (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h9C7m6ed034767;
	Sun, 12 Oct 2003 09:48:06 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Date: Sun, 12 Oct 2003 09:48:05 +0200
Subject: Re: accusations of cluelessness
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org
To: Scott  Bradner <sob@harvard.edu>
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <200310120123.h9C1NxsL012507@newdev.harvard.edu>
Message-Id: <69E6CA81-FC88-11D7-B291-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On zondag, okt 12, 2003, at 03:23 Europe/Amsterdam, Scott Bradner wrote:

>> If you have $2500 to ante up for the allocation.

> you might take a look at the RIR web pages - it does not cost
> an ISP $2500 to get additional address space allocated  - the
> additional fee for additional space for large ISPs is generally zero.

Yes, really fair. Let the newcomers pay for a resource but not the 
people using up most of it.

> end site allocations are a different story but there are a few routing
> table issues with doing many of those

The problem is that the RIRs require the use of at least a /22 (I think 
even a full /20 for ARIN) before they allocate a PA block. This makes 
it hard for newcomers to get their own block. In theory this policy 
helps keep down the size of the routing table. But in practice it 
doesn't, because:

1. many people take a smaller block from their ISP and announce that
2. large networks keep getting /20s and /19s that they announce 
individually

Where is the routing table police when you need them?




From owner-ietf@ietf.org  Sun Oct 12 05:30:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13120
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 05:30:48 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8cSz-0007N9-LJ
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 05:24:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8cSx-0007Ig-2V
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 05:24:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13021
	for <ietf@ietf.org>; Sun, 12 Oct 2003 05:24:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8cSu-00065d-00
	for ietf@ietf.org; Sun, 12 Oct 2003 05:24:40 -0400
Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8cSt-00065a-00
	for ietf@ietf.org; Sun, 12 Oct 2003 05:24:39 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h9C9OWd12567;
	Sun, 12 Oct 2003 11:24:32 +0200
Message-ID: <3F891DD0.3050500@it.su.se>
Date: Sun, 12 Oct 2003 11:24:32 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Christian Huitema <huitema@windows.microsoft.com>
CC: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: accusations of cluelessness
References: <DAC3FCB50E31C54987CD10797DA511BA0594858C@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA0594858C@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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


|
| Well, who made us kings? It is one thing to work and publish designs
| that hopefully will be good. It is quite another to judge someone else's
| design and brand it bad. It is far better to let the market be judge.
|

I agree. But should we not as a community try to produce results
which attempt to be consistent? If a feature in the network layer
break assumptions in the application layer then (setting aside the
discussion of whose fault the inconsistency is) if we want to be
consistent one has to give. I put it to you that the difference
between 'keeping' and 'removing' in this case is just in our heads.

Eg. keeping SL in the original form (I agree this is a hypothetical
situation) would have implied removing features from several protocols.
Did we remove SL or did we keep those protocols intact?

	Cheers Leif

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/iR3Q8Jx8FtbMZncRAjjaAJ96ayKHER/PH/pZjXeeMHEqRR/cTgCdHE1p
1B77cE8kUFURCAO3DoUlMhk=
=Ofi4
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Sun Oct 12 07:07:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14665
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 07:07:13 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8dwv-0005wV-CI
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 06:59:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8dwL-0005hO-B2
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 06:59:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14515
	for <ietf@ietf.org>; Sun, 12 Oct 2003 06:58:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8dw2-0006cd-00
	for ietf@ietf.org; Sun, 12 Oct 2003 06:58:50 -0400
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8dw1-0006cG-00
	for ietf@ietf.org; Sun, 12 Oct 2003 06:58:50 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id UAA718932;
	Sun, 12 Oct 2003 20:58:12 +1000 (EST)
Message-ID: <3F8933C4.8F193FC2@swin.edu.au>
Date: Sun, 12 Oct 2003 20:58:12 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: accusations of cluelessness
References: <DAC3FCB50E31C54987CD10797DA511BA0594858C@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Christian Huitema wrote:
	[..]
> Well, who made us kings?

a track record of being decent engineers. which is why most of
us are ignored when we offer legal advice, and some of us are
acknowledged when we offer clues on networking. (true, others of
us are merely princes, pages or court jesters, but still...)

> It is one thing to work and publish designs
> that hopefully will be good.

that's a good way to be crowned a king, yes.

> It is quite another to judge someone else's
> design and brand it bad.

it is called critique. even vendors go through internal processes
designed to weed out bad product ideas, poorly thought out features,
nasty implementation trade-offs....

(academics have a similar, imperfect process called peer review.
nothing new here.)

> It is far better to let the market be judge.

who blessed "the market" with engineering insight?

the market has sight. market analysts have hind-sight.
engineering is about fore-sight. therein lies a world of
difference in roles and responsibilities.

cheers,
gja
-- 
Grenville Armitage
http://caia.swin.edu.au
I come from a LAN downunder.



From owner-ietf@ietf.org  Sun Oct 12 07:49:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15441
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 07:49:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8efR-00024E-LT
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 07:45:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8efN-0001z8-IJ
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 07:45:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15310
	for <ietf@ietf.org>; Sun, 12 Oct 2003 07:45:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8efM-0006tr-00
	for ietf@ietf.org; Sun, 12 Oct 2003 07:45:40 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8efM-0006to-00
	for ietf@ietf.org; Sun, 12 Oct 2003 07:45:40 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 0DF0F1410C; Sun, 12 Oct 2003 07:45:40 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 22692-01; Sun, 12 Oct 2003 07:45:39 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id B406613FD3; Sun, 12 Oct 2003 07:45:38 -0400 (EDT)
Date: Sun, 12 Oct 2003 07:42:12 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Christian Huitema" <huitema@windows.microsoft.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031012074212.2c235d8c.moore@cs.utk.edu>
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA0594858C@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References: <DAC3FCB50E31C54987CD10797DA511BA0594858C@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> Well, who made us kings? It is one thing to work and publish designs
> that hopefully will be good. It is quite another to judge someone else's
> design and brand it bad. It is far better to let the market be judge.

You're not insisting that the market be judge; you're insisting that
IETF lend its support to bad designs in order to help mislead the market.

Also, you're simply wrong that it's better to let the market judge things -
that is, if you want things to actually work.  

When vendors insist on a level playing field - what they mean is that they
want things slanted in a way that gives them an advantage. 



From owner-ietf@ietf.org  Sun Oct 12 10:21:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19096
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 10:21:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8gwj-0001Sl-Ap
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 10:11:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8guc-0000jf-OY
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 10:09:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18398
	for <ietf@ietf.org>; Sun, 12 Oct 2003 10:09:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8gub-0007mP-00
	for ietf@ietf.org; Sun, 12 Oct 2003 10:09:33 -0400
Received: from smtp2.arin.net ([192.149.252.32])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8gub-0007mH-00
	for ietf@ietf.org; Sun, 12 Oct 2003 10:09:33 -0400
Received: by smtp2.arin.net (Postfix, from userid 5003)
	id 79D82719; Sun, 12 Oct 2003 10:09:03 -0400 (EDT)
Received: from ops.arin.net (ops [192.149.252.141])
	by smtp2.arin.net (Postfix) with ESMTP id 1068032B
	for <ietf@ietf.org>; Sun, 12 Oct 2003 10:09:03 -0400 (EDT)
Received: from ano2 ([192.136.136.85])
	by ops.arin.net (8.9.0/8.9.0) with ESMTP id KAA17542
	for <ietf@ietf.org>; Sun, 12 Oct 2003 10:08:58 -0400 (EDT)
From: "Ray Plzak" <plzak@arin.net>
To: <ietf@ietf.org>
Subject: RE: accusations of cluelessness
Date: Sun, 12 Oct 2003 10:08:53 -0400
Message-ID: <000801c390ca$635d0560$558888c0@arin.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <20031012012528.41dd0367.moore@cs.utk.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-Spam-Status: No, hits=-0.8 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43-arin1
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On 
> Behalf Of Keith Moore
> Sent: Sunday, October 12, 2003 1:25 AM
> To: Scott Bradner
> Cc: moore@cs.utk.edu; ietf@ietf.org
> Subject: Re: accusations of cluelessness
> 
> 
> > Just what would you suggest in the way of relaxing?
> 
> since I view this as a hypothetical situation anyway (and one 
> that isn't
> likely to happen in the real world) I don't think it's 
> necessary to pin down
> exactly how they'd go about relaxing the criteria - only to 
> realize that it is
> possible to relax those criteria

There are currently several discussions in the ARIN region regarding
IPv4 allocations both in regard to minimum size and criteria.
Discussions about IPv4 policy and IPv6 policy are of a contiuous nature
in all of the RIRs reflecting changes in the operational community.

Ray  





From owner-ietf@ietf.org  Sun Oct 12 11:15:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20409
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 11:15:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8hrp-00085D-Cc
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 11:10:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8hjZ-0007sT-5G
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 11:02:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20200
	for <ietf@ietf.org>; Sun, 12 Oct 2003 11:02:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8hjY-0000Q2-00
	for ietf@ietf.org; Sun, 12 Oct 2003 11:02:12 -0400
Received: from web13507.mail.yahoo.com ([216.136.175.86])
	by ietf-mx with smtp (Exim 4.12)
	id 1A8hjX-0000Pz-00
	for ietf@ietf.org; Sun, 12 Oct 2003 11:02:11 -0400
Message-ID: <20031012150209.74661.qmail@web13507.mail.yahoo.com>
Received: from [68.118.70.100] by web13507.mail.yahoo.com via HTTP; Sun, 12 Oct 2003 08:02:09 PDT
Date: Sun, 12 Oct 2003 08:02:09 -0700 (PDT)
From: Mark Seery <m_seery@yahoo.com>
Subject: Let the market be judge (Re: accusations of cluelessness)
To: grenville armitage <garmitage@swin.edu.au>, ietf@ietf.org
In-Reply-To: <3F8933C4.8F193FC2@swin.edu.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk


--- grenville armitage <garmitage@swin.edu.au> wrote:
<snip>
> the market has sight. market analysts have hind-sight.
> engineering is about fore-sight. therein lies a world of
> difference in roles and responsibilities.

The fore-sight of any role is constrained by assumptions. An engineer who
designs a building to withstand a collision with a 707 suddenly has a lot more
hindsight (than fore-sight) when it is hit with a 767. So let's acknowledge
there is no such thing as perfect fore-sight for any role, only better or worse
given a set of assumptions.

The ethos of running code is all about establishing a proof that something
works. Challenging design assumptions is worthwhile, especially if you can see
the 767 coming, but this institution appears to give weight to running "code".
So in the context of running code, the market can be the judge.

--- Valdis.Kletnieks@vt.edu wrote:
<snip>
> If letting the market be judge is a good idea, why is such a large percentage
of my bandwidth chewed up by emails bearing viruses? <

A large percentage of your bandwidth is chewed up because there is no market -
no cost associated with sending an email. A large percentage of those emails
have viruses because a) viruses are to cyber-assets what WMD are to physical
assets - i.e. widespread damage from one device b) the crimial justice system
has not kept pace with technological change and c) there is resitance to
allowing the crimial justice system to keep pace (which may or may not be good
thing depending on your view). Put another way, if the criminal justice system
had the same level of effectiveness at protecting physical assets, I wonder
whether civilization as we know it would exist.




From owner-ietf@ietf.org  Sun Oct 12 11:50:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21241
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 11:50:23 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8iOi-0003nd-Ho
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 11:44:44 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8iO0-0003ZS-30
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 11:44:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21170
	for <ietf@ietf.org>; Sun, 12 Oct 2003 11:43:50 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8iNz-0000kP-00
	for ietf@ietf.org; Sun, 12 Oct 2003 11:43:59 -0400
Received: from h80ad2602.async.vt.edu ([128.173.38.2] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8iNx-0000kM-00
	for ietf@ietf.org; Sun, 12 Oct 2003 11:43:58 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9CFhseb010107;
	Sun, 12 Oct 2003 11:43:54 -0400
Message-Id: <200310121543.h9CFhseb010107@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Mark Seery <m_seery@yahoo.com>
Cc: grenville armitage <garmitage@swin.edu.au>, ietf@ietf.org
Subject: Re: Let the market be judge (Re: accusations of cluelessness) 
In-Reply-To: Your message of "Sun, 12 Oct 2003 08:02:09 PDT."
             <20031012150209.74661.qmail@web13507.mail.yahoo.com> 
References: <20031012150209.74661.qmail@web13507.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_313734677P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Sun, 12 Oct 2003 11:43:53 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Sun, 12 Oct 2003 08:02:09 PDT, Mark Seery <m_seery@yahoo.com>  said:

> thing depending on your view). Put another way, if the criminal justice system
> had the same level of effectiveness at protecting physical assets, I wonder
> whether civilization as we know it would exist.

If you want to take it in that direction, we have a case where "the market" decided
that locks weren't needed on doors in a high-crime area of town.  OK, so maybe
the crime rate was still low when the door was installed - there's been a lot of
delay and negligence in installing said locks.


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

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

iD8DBQE/iXa5cC3lWbTT17ARAjtNAKD967Em6DEidWYpkF286i47NwhVMwCfXBm8
NSj0bberGPt1yPh5QPbuOHE=
=Lp1Q
-----END PGP SIGNATURE-----

--==_Exmh_313734677P--



From owner-ietf@ietf.org  Sun Oct 12 12:14:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21886
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 12:14:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8inu-0005h3-Dj
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 12:10:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8ibE-00053w-Sr
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 11:57:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21545
	for <ietf@ietf.org>; Sun, 12 Oct 2003 11:57:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8ibD-0000tg-00
	for ietf@ietf.org; Sun, 12 Oct 2003 11:57:39 -0400
Received: from smtp013.mail.yahoo.com ([216.136.173.57])
	by ietf-mx with smtp (Exim 4.12)
	id 1A8ibD-0000td-00
	for ietf@ietf.org; Sun, 12 Oct 2003 11:57:39 -0400
Received: from ts46-01-qdr3166.mrgnhll.ca.charter.com (HELO yahoo.com) (m?seery@68.118.70.100 with plain)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 12 Oct 2003 15:57:38 -0000
Message-ID: <3F897A02.4030209@yahoo.com>
Date: Sun, 12 Oct 2003 08:57:54 -0700
From: mark seery <m_seery@yahoo.com>
Reply-To: m_seery@yahoo.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: ietf@ietf.org
Subject: Re: Let the market be judge (Re: accusations of cluelessness)
References: <20031012150209.74661.qmail@web13507.mail.yahoo.com> <200310121543.h9CFhseb010107@turing-police.cc.vt.edu>
In-Reply-To: <200310121543.h9CFhseb010107@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

That is a fair point, but I would observe that there are plenty of more 
cases where locks were not sufficient.

If there are no tradeoffs to actions/feedback loops, then agents in a 
system can not make optimization/fitness decisions and evolution does 
not occur.

Valdis.Kletnieks@vt.edu wrote:

>On Sun, 12 Oct 2003 08:02:09 PDT, Mark Seery <m_seery@yahoo.com>  said:
>
>  
>
>>thing depending on your view). Put another way, if the criminal justice system
>>had the same level of effectiveness at protecting physical assets, I wonder
>>whether civilization as we know it would exist.
>>    
>>
>
>If you want to take it in that direction, we have a case where "the market" decided
>that locks weren't needed on doors in a high-crime area of town.  OK, so maybe
>the crime rate was still low when the door was installed - there's been a lot of
>delay and negligence in installing said locks.
>
>  
>





From owner-ietf@ietf.org  Sun Oct 12 12:29:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22331
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 12:29:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8j1S-00088R-Gy
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 12:24:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8j0e-00082o-SZ
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 12:23:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22270
	for <ietf@ietf.org>; Sun, 12 Oct 2003 12:23:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8j0d-00018X-00
	for ietf@ietf.org; Sun, 12 Oct 2003 12:23:55 -0400
Received: from ns.execdsl.net ([208.184.15.238] helo=EXECDSL.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8j0d-00018U-00
	for ietf@ietf.org; Sun, 12 Oct 2003 12:23:55 -0400
Received: from [66.95.38.74] (HELO JLaptop.stevecrocker.com)
  by EXECDSL.COM (CommuniGate Pro SMTP 3.3)
  with ESMTP id 5601645 for ietf@ietf.org; Sun, 12 Oct 2003 12:23:55 -0400
Message-Id: <5.1.0.14.0.20031012121807.02394068@mail.stevecrocker.com>
X-Sender: joel@stevecrocker.com@mail.stevecrocker.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 12 Oct 2003 12:23:29 -0400
To: IETF <ietf@ietf.org>
From: "Joel M. Halpern" <joel@stevecrocker.com>
Subject: RE: accusations of cluelessness
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA0594858C@WIN-MSG-10.wingro
 up.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

Nobody made us kings.  In fact, we are not kings.
On the other hand, we are not a publication house.  Someone having an idea 
and writing it up does not require us to publish it as an IETF 
standard.  Even if it is a good idea.
If someone wants to have the IETF work on something and produce a standard 
for a problem, then one dimension of that is agreeing to accept IETF review 
and modification of the idea and solution.

We can not stop someone from doing their own thing.  For example, if you 
want to use a new header call X-CHRISTIAN-TYPE and define content type 
values as you please, as long as you do not request IETF agreement that it 
is a good idea we can not stop you.  In that regard, the market can still 
choose.

It is true that the market attaches value to the IETF standardization.  To 
that degree, the market has made us judges and asked us to judge.

Yours,
Joel M. Halpern

At 10:58 PM 10/11/2003 -0700, Christian Huitema wrote:
>Well, who made us kings? It is one thing to work and publish designs
>that hopefully will be good. It is quite another to judge someone else's
>design and brand it bad. It is far better to let the market be judge.





From owner-ietf@ietf.org  Sun Oct 12 12:42:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22674
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 12:42:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8jEz-0001A0-0L
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 12:38:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8jB4-0000LA-9N
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 12:34:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22571
	for <ietf@ietf.org>; Sun, 12 Oct 2003 12:34:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8jB3-0001EV-00
	for ietf@ietf.org; Sun, 12 Oct 2003 12:34:41 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8jB2-0001ES-00
	for ietf@ietf.org; Sun, 12 Oct 2003 12:34:40 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id DF2DC14094; Sun, 12 Oct 2003 12:34:40 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 12353-12; Sun, 12 Oct 2003 12:34:40 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 853CC14047; Sun, 12 Oct 2003 12:34:39 -0400 (EDT)
Date: Sun, 12 Oct 2003 12:31:12 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Mark Seery <m_seery@yahoo.com>
Cc: moore@cs.utk.edu, garmitage@swin.edu.au, ietf@ietf.org
Subject: Re: Let the market be judge (Re: accusations of cluelessness)
Message-Id: <20031012123112.3fdae47b.moore@cs.utk.edu>
In-Reply-To: <20031012150209.74661.qmail@web13507.mail.yahoo.com>
References: <3F8933C4.8F193FC2@swin.edu.au>
	<20031012150209.74661.qmail@web13507.mail.yahoo.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> <snip>
> > the market has sight. market analysts have hind-sight.
> > engineering is about fore-sight. therein lies a world of
> > difference in roles and responsibilities.
> 
> The fore-sight of any role is constrained by assumptions. An engineer who
> designs a building to withstand a collision with a 707 suddenly has a lot
> more hindsight (than fore-sight) when it is hit with a 767. So let's
> acknowledge there is no such thing as perfect fore-sight for any role, only
> better or worse given a set of assumptions.

there is no perfect foresight.  there is no perfect hindsight either.
nor is the market either efficient or reliable at choosing good solutions.

but we are probably better off using some combination of foresight,
hindsight, and market forces than by excluding any of these or 
relying on any of these exclusively.



From owner-ietf@ietf.org  Sun Oct 12 18:08:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01303
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 18:08:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8o8r-0001hF-BI
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 17:52:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8o8m-0001dB-Ps
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 17:52:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00558
	for <ietf@ietf.org>; Sun, 12 Oct 2003 17:52:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8o8g-0003Vl-00
	for ietf@ietf.org; Sun, 12 Oct 2003 17:52:34 -0400
Received: from smtp2.arin.net ([192.149.252.32])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8o8g-0003VX-00
	for ietf@ietf.org; Sun, 12 Oct 2003 17:52:34 -0400
Received: by smtp2.arin.net (Postfix, from userid 5003)
	id 1B522941; Sun, 12 Oct 2003 17:52:04 -0400 (EDT)
Received: from ops.arin.net (ops [192.149.252.141])
	by smtp2.arin.net (Postfix) with ESMTP id 9769C940
	for <ietf@ietf.org>; Sun, 12 Oct 2003 17:52:03 -0400 (EDT)
Received: from ano2 ([192.136.136.39])
	by ops.arin.net (8.9.0/8.9.0) with ESMTP id RAA22404
	for <ietf@ietf.org>; Sun, 12 Oct 2003 17:52:02 -0400 (EDT)
From: "Ray Plzak" <plzak@arin.net>
To: <ietf@ietf.org>
Subject: RE: accusations of cluelessness
Date: Sun, 12 Oct 2003 17:52:00 -0400
Message-ID: <003701c3910b$11d6bf60$278888c0@arin.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <000801c390ca$635d0560$558888c0@arin.net>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Status: No, hits=-0.8 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43-arin1
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

For those who wish to become involved in the policy process or view the
archives:

	http://www.apnic.net/community/lists/index.html

	http://www.arin.net/mailing_lists/index.html

	http://lacnic.net/en/discussion_boards.html

	http://www.ripe.net/ripe/about/maillists.html

Ray

> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On 
> Behalf Of Ray Plzak
> Sent: Sunday, October 12, 2003 10:09 AM
> To: ietf@ietf.org
> Subject: RE: accusations of cluelessness
> 
> 
> 
> 
> > -----Original Message-----
> > From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On 
> > Behalf Of Keith Moore
> > Sent: Sunday, October 12, 2003 1:25 AM
> > To: Scott Bradner
> > Cc: moore@cs.utk.edu; ietf@ietf.org
> > Subject: Re: accusations of cluelessness
> > 
> > 
> > > Just what would you suggest in the way of relaxing?
> > 
> > since I view this as a hypothetical situation anyway (and one 
> > that isn't
> > likely to happen in the real world) I don't think it's 
> > necessary to pin down
> > exactly how they'd go about relaxing the criteria - only to 
> > realize that it is
> > possible to relax those criteria
> 
> There are currently several discussions in the ARIN region regarding
> IPv4 allocations both in regard to minimum size and criteria.
> Discussions about IPv4 policy and IPv6 policy are of a 
> contiuous nature
> in all of the RIRs reflecting changes in the operational community.
> 
> Ray  
> 
> 




From owner-ietf@ietf.org  Sun Oct 12 21:50:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05611
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 21:50:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8rda-0003o1-3v
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 21:36:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8rcg-0003kp-Dz
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 21:35:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05419
	for <ietf@ietf.org>; Sun, 12 Oct 2003 21:35:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8rce-0004sA-00
	for ietf@ietf.org; Sun, 12 Oct 2003 21:35:44 -0400
Received: from smtp101.mail.sc5.yahoo.com ([216.136.174.139])
	by ietf-mx with smtp (Exim 4.12)
	id 1A8rce-0004s7-00
	for ietf@ietf.org; Sun, 12 Oct 2003 21:35:44 -0400
Received: from ts46-01-qdr3166.mrgnhll.ca.charter.com (HELO yahoo.com) (m?seery@68.118.70.100 with plain)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 13 Oct 2003 01:35:44 -0000
Message-ID: <3F8A017F.5050806@yahoo.com>
Date: Sun, 12 Oct 2003 18:35:59 -0700
From: mark seery <m_seery@yahoo.com>
Reply-To: m_seery@yahoo.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: ietf@ietf.org
Subject: Re: Let the market be judge (Re: accusations of cluelessness)
References: <3F8933C4.8F193FC2@swin.edu.au>	<20031012150209.74661.qmail@web13507.mail.yahoo.com> <20031012123112.3fdae47b.moore@cs.utk.edu>
In-Reply-To: <20031012123112.3fdae47b.moore@cs.utk.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:

>><snip>
>>    
>>
>>>the market has sight. market analysts have hind-sight.
>>>engineering is about fore-sight. therein lies a world of
>>>difference in roles and responsibilities.
>>>      
>>>
>>The fore-sight of any role is constrained by assumptions. An engineer who
>>designs a building to withstand a collision with a 707 suddenly has a lot
>>more hindsight (than fore-sight) when it is hit with a 767. So let's
>>acknowledge there is no such thing as perfect fore-sight for any role, only
>>better or worse given a set of assumptions.
>>    
>>
>
>there is no perfect foresight.  there is no perfect hindsight either.
>nor is the market either efficient or reliable at choosing good solutions.
>
It appears the word "market" is overloaded with lots of social/political 
ideology so rather than go down that road, let me redirect the point by 
simply observing that running code allows the designer(s) to get 
feedback about a design and its implementation implications, which is 
the point about "letting the market decide". Many can imagine a "better" 
design for some problem space, according to some fitness bias we have, 
but imagining a "better" design doesn't help unless it can be run and 
produce results, against the fitness bias the consumers of a solution have.

There is nothing wrong with basing an implementation on previous 
experience and foresight, but there are many things which are more 
complex than what we can readily understand and therefore our foresight 
is limited - our implementation experience helps here. This is the age 
old debate about waterfall vs iteration - probably another dead end 
discussion point.

>
>but we are probably better off using some combination of foresight,
>hindsight, and market forces than by excluding any of these or 
>relying on any of these exclusively.
>  
>
ack. so as usual, there are no absolutes and a fair amount of subjective 
judgement, which I guess is the reason why discussion occurs.




From owner-ietf@ietf.org  Sun Oct 12 22:11:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06212
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 22:11:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8s5e-0005j3-Ad
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 22:05:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8s57-0005fl-R9
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 22:05:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06128
	for <ietf@ietf.org>; Sun, 12 Oct 2003 22:05:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8s55-00058B-00
	for ietf@ietf.org; Sun, 12 Oct 2003 22:05:08 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8s55-000588-00
	for ietf@ietf.org; Sun, 12 Oct 2003 22:05:07 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 21FA91418D; Sun, 12 Oct 2003 22:05:07 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 31032-10; Sun, 12 Oct 2003 22:05:06 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id D598E140EA; Sun, 12 Oct 2003 22:05:05 -0400 (EDT)
Date: Sun, 12 Oct 2003 22:01:37 -0400
From: Keith Moore <moore@cs.utk.edu>
To: m_seery@yahoo.com
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Let the market be judge (Re: accusations of cluelessness)
Message-Id: <20031012220137.7ab7474e.moore@cs.utk.edu>
In-Reply-To: <3F8A017F.5050806@yahoo.com>
References: <3F8933C4.8F193FC2@swin.edu.au>
	<20031012150209.74661.qmail@web13507.mail.yahoo.com>
	<20031012123112.3fdae47b.moore@cs.utk.edu>
	<3F8A017F.5050806@yahoo.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> >there is no perfect foresight.  there is no perfect hindsight either.
> >nor is the market either efficient or reliable at choosing good solutions.
> >
> It appears the word "market" is overloaded with lots of social/political 
> ideology so rather than go down that road, let me redirect the point by 
> simply observing that running code allows the designer(s) to get 
> feedback about a design and its implementation implications, which is 
> the point about "letting the market decide". 

Within IETF, "running code" has usually meant interoperability tests of
multiple implementations of a single protocol.  These days we find we need
to be more concerned about the interaction between protocols than we used to
be.  The notion that protocols can be examined in isolation no longer holds. 
So for instance: we expect non-TCP-based protocols to share bandwidth fairly
with TCP-based protocols; and we expect all protocols to be reasonably secure
because when even a single protocol is compromised it can disrupt operation of
the network, other protocols, and hosts that weren't directly compromised.

The "market" is not in a good position to evaluate these characteristics
because many of these effects do not become visible to the "market" until
the "market" has already substantially invested in a particular path.
Indeed, the very discipline of "engineering" exists to minimize such
catastrophes. If you make design decisions based on guesswork, that's
guesswork; if you make design decisions based on analysis of how well a
solution meets well-defined criteria, that's engineering.

These days, a lot of people seem to be arguing that IETF shouldn't do
engineering.




From owner-ietf@ietf.org  Sun Oct 12 22:30:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06670
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 22:30:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8sP0-0006sR-2L
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 22:25:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8sOW-0006j0-Jx
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 22:25:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06582
	for <ietf@ietf.org>; Sun, 12 Oct 2003 22:25:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8sOU-0005JE-00
	for ietf@ietf.org; Sun, 12 Oct 2003 22:25:10 -0400
Received: from smtp101.mail.sc5.yahoo.com ([216.136.174.139])
	by ietf-mx with smtp (Exim 4.12)
	id 1A8sOT-0005JB-00
	for ietf@ietf.org; Sun, 12 Oct 2003 22:25:10 -0400
Received: from ts46-01-qdr3166.mrgnhll.ca.charter.com (HELO yahoo.com) (m?seery@68.118.70.100 with plain)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 13 Oct 2003 02:25:09 -0000
Message-ID: <3F8A0D15.8070202@yahoo.com>
Date: Sun, 12 Oct 2003 19:25:25 -0700
From: mark seery <m_seery@yahoo.com>
Reply-To: m_seery@yahoo.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: ietf@ietf.org
Subject: Re: Let the market be judge (Re: accusations of cluelessness)
References: <3F8933C4.8F193FC2@swin.edu.au>	<20031012150209.74661.qmail@web13507.mail.yahoo.com>	<20031012123112.3fdae47b.moore@cs.utk.edu>	<3F8A017F.5050806@yahoo.com> <20031012220137.7ab7474e.moore@cs.utk.edu>
In-Reply-To: <20031012220137.7ab7474e.moore@cs.utk.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Keith Moore wrote:

><snip>
>
>These days, a lot of people seem to be arguing that IETF shouldn't do
>engineering.
>  
>
Hopefully not - not I for sure, I mean that would require a name change 
;-) What I think exists is a difference of opinion about what the 
definition of engineering is. Another well-known institution seems also 
to be stuggling with this same question:

"....*where numbers count for everything and hunches are scorned...."

*http://www.cnn.com/2003/TECH/space/10/12/nasa.reformers.ap/index.html

>  
>





From owner-ietf@ietf.org  Sun Oct 12 23:08:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08144
	for <ietf-web-archive@odin.ietf.org>; Sun, 12 Oct 2003 23:08:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8svu-0001BG-Du
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 22:59:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8svP-00017o-0W
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 22:59:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07914
	for <ietf@ietf.org>; Sun, 12 Oct 2003 22:59:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8svN-0005ok-00
	for ietf@ietf.org; Sun, 12 Oct 2003 22:59:09 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8svM-0005oh-00
	for ietf@ietf.org; Sun, 12 Oct 2003 22:59:08 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 24B7814322; Sun, 12 Oct 2003 22:59:09 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 04543-03; Sun, 12 Oct 2003 22:59:07 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 69C4114271; Sun, 12 Oct 2003 22:59:07 -0400 (EDT)
Date: Sun, 12 Oct 2003 22:55:38 -0400
From: Keith Moore <moore@cs.utk.edu>
To: m_seery@yahoo.com
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Let the market be judge (Re: accusations of cluelessness)
Message-Id: <20031012225538.1644fb6e.moore@cs.utk.edu>
In-Reply-To: <3F8A0D15.8070202@yahoo.com>
References: <3F8933C4.8F193FC2@swin.edu.au>
	<20031012150209.74661.qmail@web13507.mail.yahoo.com>
	<20031012123112.3fdae47b.moore@cs.utk.edu>
	<3F8A017F.5050806@yahoo.com>
	<20031012220137.7ab7474e.moore@cs.utk.edu>
	<3F8A0D15.8070202@yahoo.com>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> >These days, a lot of people seem to be arguing that IETF shouldn't do
> >engineering.
> 
> What I think exists is a difference of opinion about what the 
> definition of engineering is. 

another way to put it is - after ~17 years of IETF, we need to start
defining what "Internet Engineering" means.

> Another well-known institution seems also to be stuggling with this same
> question:
> 
> "....*where numbers count for everything and hunches are scorned...."

ignoring hunches didn't cause the demise of Challenger and Columbia.
ignoring hard data did.  of course, paying attention to intuition might
be useful in those inevitable (hopefully rare) cases where you do ignore
hard data.



From owner-ietf@ietf.org  Mon Oct 13 09:18:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03095
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 09:18:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A92LO-0000u5-Kz
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 09:02:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A92K7-0000t7-2T
	for ietf@asgard.ietf.org; Mon, 13 Oct 2003 09:01:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02648
	for <ietf@ietf.org>; Mon, 13 Oct 2003 09:01:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A92K6-0002C2-00
	for ietf@ietf.org; Mon, 13 Oct 2003 09:01:18 -0400
Received: from aragorn.bbn.com ([128.33.0.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A92K5-0002Br-00
	for ietf@ietf.org; Mon, 13 Oct 2003 09:01:17 -0400
Received: from arsenaultd2 (col-dhcp33-244-172.bbn.com [128.33.244.172])
	by aragorn.bbn.com (8.12.7/8.12.7) with SMTP id h9DD0iTW022222;
	Mon, 13 Oct 2003 09:00:45 -0400 (EDT)
From: "Al Arsenault" <aarsenau@bbn.com>
To: "Christian Huitema" <huitema@windows.microsoft.com>,
        "Keith Moore" <moore@cs.utk.edu>
Cc: <ietf@ietf.org>
Subject: RE: accusations of cluelessness
Date: Mon, 13 Oct 2003 08:57:57 -0400
Message-ID: <GBEOIAAPLLBIMLPDGHDHGEMOCEAA.aarsenau@bbn.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 IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA0594858C@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I have a feeling I'm gonna regret getting involved in this rat-hole, but
here goes anyway...

I mostly agree with the "let the market decide" philosophy, but there have
to be some limits. Following this strictly leads to pathological cases.  To
point out incidents from the IETF PKIX group over the years that demonstrate
what can happen:

	1 - a gentleman (I'll be polite and call him that) asked PKIX to adopt as a
work item a time-stamping technology he developed.  This gentleman was given
an opportunity (at Adelaide and I believe at one other meeting, as well as
on the list) to present his material to the working group. In the end, PKIX
didn't pick up his work as a work item because it didn't fall under the
charter of the WG. A total of only about 3 people even thought it was
interesting, and they weren't sure it was within the working group's
purview.

	This gentleman has devoted much energy since then to disparaging the IETF,
PKIX, and the PKIX WG chair personally, for this.  His view, stated in
public numerous times, is that the way the IETF should work is that any item
which is properly formatted must be published as an RFC.  That is, any
individual or group can create a document.  If it meets the formatting
requirements, it must be published as an RFC.  It is not the job of the WG,
the IESG, IAB or any other group to approve/disapprove, evaluate, analyze or
otherwise pass judgement on the technical contents of the document.

	Furthermore, all RFCs must be given the same status. It is not appropriate
for the IETF to favor one RFC or the technology contained in it over any
other RFC or technology.

	Any other strategy constitutes restraint of trade, interference in the
market place, and basically a violation of all that a "standards group"
should do.

	Now, fortunately, not too many people agree with this gentleman, but it
does represent a pathological case of "let the market decide".

	2 - the PKIX WG published two competing, non-interoperable protocols for
the same function. One is referred to as CMP; it's in RFC 2510.  The other
is referred to as CMC; it's specified in RFC 2797.  There are a lot of
reasons why we did this; but it boiled down to a schism.  One of the two
largest PKI players at that time preferred CMP, and its allies refused to
yield.  The other of the two largest players preferred CMC, and its allies
refused to yield.  This was because those protocols represented what their
products did, and nobody wanted to change his product.  So, to prevent
bogging down and making no progress at all, the WG decided to progress both
protocols and "let the market decide".  Most people now agree that this was
a mistake.  The strategy of publishing both protocols as "equals" did not
lead to interworking in the Internet; it arguably did the opposite.  It was
also horribly misunderstood by those not in the know; it was believed in
some quarters that one protocol was the interim strategy and the other was
the long-range target. (The supporters of each side did nothing to
discourage this misunderstanding.)

 	While this is not the biggest factor in the failure of PKI to become
ubiquitous, it didn't help.

	My bottom line on this: while I'm not a strong believer in having the
cognoscenti dictate to the unwashed masses the "one true way to do things",
it helps a lot if the Internet Engineering Task Force actually does some
"Internet Engineering".

				Al Arsenault

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org]On Behalf Of
Christian Huitema
Sent: Sunday, October 12, 2003 1:59 AM
To: Keith Moore
Cc: ietf@ietf.org
Subject: RE: accusations of cluelessness


> > It is perfectly fine to review a specification, understand the
intent of
> > the original designer, and suggest ways to better achieve the same
> > result. That is exactly what working groups are supposed to do. It
is
> > also perfectly fine, if the original designer won't change their
design,
> > to publish an alternative design that hopefully works better, and
then
> > rely on market forces to sort it out. But it is not fine to try to
> > prevent the original designer from actually shipping products,
either by
> > preventing publication of the specification or by trying to prevent
> > deployment.
>
> On the contrary, it is our duty to do all of these things.
>
> What is not fine is for participants to expect IETF to lend its
support to
> bad designs.

Well, who made us kings? It is one thing to work and publish designs
that hopefully will be good. It is quite another to judge someone else's
design and brand it bad. It is far better to let the market be judge.

-- Christian Huitema




From owner-ietf@ietf.org  Mon Oct 13 10:28:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07679
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 10:28:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A93Xu-0000JJ-8Q
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 10:19:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A93XW-0000Ip-7k
	for ietf@asgard.ietf.org; Mon, 13 Oct 2003 10:19:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07363
	for <ietf@ietf.org>; Mon, 13 Oct 2003 10:19:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A93XV-0003Cc-00
	for ietf@ietf.org; Mon, 13 Oct 2003 10:19:13 -0400
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A93XU-0003C9-00
	for ietf@ietf.org; Mon, 13 Oct 2003 10:19:12 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id AAA855418;
	Tue, 14 Oct 2003 00:18:39 +1000 (EST)
Message-ID: <3F8AB43E.6536D809@swin.edu.au>
Date: Tue, 14 Oct 2003 00:18:38 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Let the market be judge (Re: accusations of cluelessness)
References: <20031012150209.74661.qmail@web13507.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Mark Seery wrote:
	[..]
> The ethos of running code is all about establishing a proof that something
> works.

I never said otherwise. "Running code" has been a useful means for reducing the
solution space from which the IETF publishes. It has never been a hard and fast
metric of good design. (Indeed, if anything the IETF's history has shown a number
of protocol designs that were running code and yet still only waypoints towards
better designs in the future.)

But that's really not the point here. The role of an _engineering_ taskforce
is to act like engineers, not a vanity press. Our output should be educated
guidance to the wider community - created with diligence and offered with humility.
We can do no more and should do no less.

(Arguments that the IETF prevents deployment by preventing publication are a
red-herring and should be discarded as such. The "market" has shown a remarkable
affinity, at times, to protocols that have either never been fully published or
published outside the IETF.)

cheers,
gja
-- 
Grenville Armitage
http://caia.swin.edu.au
I come from a LAN downunder.



From owner-ietf@ietf.org  Mon Oct 13 10:36:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08168
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 10:36:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A93jV-0000j8-SU
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 10:31:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A7kh9-0004Pr-Ho
	for ietf@asgard.ietf.org; Thu, 09 Oct 2003 19:59:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17839
	for <ietf@ietf.org>; Thu, 9 Oct 2003 19:59:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7kh7-0006Vk-00
	for ietf@ietf.org; Thu, 09 Oct 2003 19:59:45 -0400
Received: from evrtwa1-ar8-4-65-016-099.evrtwa1.dsl-verizon.net ([4.65.16.99] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7kh5-0006VV-00
	for ietf@ietf.org; Thu, 09 Oct 2003 19:59:44 -0400
Received: from eaglet (127.0.0.1:4693)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S35D01> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 09 Oct 2003 16:59:48 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "IAB" <iab@iab.org>
Cc: "The IESG" <iesg@ietf.org>, <ipv6@ietf.org>, "IETF" <ietf@ietf.org>
Subject: Appeal to the IAB on the site-local issue
Date: Thu, 9 Oct 2003 16:59:38 -0700
Message-ID: <IKEDILMOGFKPCDJAMFKKKEAOCMAA.alh-ietf@tndh.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 IMO, Build 9.0.6604 (9.0.2911.0)
In-reply-to: <200309301844.OAA06854@ietf.org>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I am saddened that it has come to this, but the IESG action has simply
prolonged the process. The only clarity in their '...somewhere to the
left...' justification is their willingness to let personal technical biases
blind them to the process failure. As such, please consider this note to be
an appeal to the IAB against the IESG decision to reject my appeal.

Contrary to their claim, the full spectrum of choices was not presented at
the SF meeting. Then, if it weren't for the seriousness of the issue, their
inability to do a quick check of the Atlanta minutes (which shows that 125
attendees were against complete removal, not the limited model) would be
humorous. In response to the overwhelming rejection of her preferred path,
in Atlanta the chair declared 'The wg has agreed we don't want to remove
them completely ...' so there was no documentation developed discussing the
impacts of complete removal. Therefore there could be no substantive
presentation of that position. As noted in my original 4/10/2003 appeal to
the chairs, the mail list claims that the RFC 3513 Site-Local addresses
'have issues that outweigh the benefits', or 'does not meet the
requirements' are invalid because there was no document listing the
requirements, therefore no way to conduct an evaluation which would justify
those positions.

This lack of documentation became acute when the participants from the
applications area were invited to join in the discussion. While I
acknowledge that cross area participation helps refine the specifications
(and had personally been lobbying the Apps Area to participate), that
refinement only happens through extended discussion and informed debate. An
hour and twenty minutes of inciting the mob does not constitute informed
discussion. In fact 10 minutes before the question, Dave Thaler pointed out
there was no draft about elimination, but that detail was ignored by the
chair. Shortly after that, Brian Carpenter pointed out that he couldn't vote
for keeping SL unless he knew the details of that outcome, to which the
chair eventually countered we don't have any details about what it means to
remove them either and 'we may have to wave our hands around a little bit'.
The chair chose to conduct the vote with no clear outcome for either
position, leaving the result that the chair could later tell the working
group what it had decided.

The further comment by the IESG that the action has resulted in working
group activity to address the issues is equally flawed. There were attempts
to disambiguate the FEC0 space prior to the SF fiasco, but those were
consistently savaged by those who want nothing more than to declare the
routing space to be globally flat by IETF fiat. Those same people are
working to prevent a different form of local prefix from being defined, and
now are feeling emboldened as it appears that this current work is an
addition to the architecture rather than a refinement. Which returns us to
the ambiguity of the original question, was this a vote about removing
ambiguity from the site-local prefix, or removing limited routing scope from
the architecture? People expressed opinions about each of those as the basis
of their yes vote, but the scope of routing is an operational decision of
network managers, therefore not something the IETF gets to decide. Since the
votes were mixed as a common Yes, the vote must be invalidated.

At every step, this exercise has exposed failures in how the IETF conducts
its business. It is now up to the IAB to recommend that the IESG go back,
*seriously* set aside their technical biases, and reconsider the process
breakdowns. Anything less and we set the precedent that it really doesn't
matter how badly a chair abuses the process as long as the IESG agrees with
the outcome.

Tony

FYI: video of the SF session:
ftp://limestone.uoregon.edu/pub/videolab/video/ietf56/ietf56


> The IESG has reviewed the appeal by Tony Hain of the IPv6 Working Group
> chairs' declaration of consensus on the issue of site local addresses in
> the IPv6 address architecture.
>
> Tony's appeal requests that the declaration of consensus be
> overturned due
> to the ambiguity of the question asked.
>
> As is to be expected of a technical discussion where there are many
> opinions, the discussion of the site-local issue at the San
> Francisco IETF
> meeting went all over the map, with many unanswered questions.
> However, the question asked by the chairs, with clarification from
> the AD, was clear.  "Does the group want to go away from site-local
> addressing, deprecate it, work out how to get it out, [or] does
> the group want to keep it and figure out what the right usage model
> is for it?"  The clarifying statement was "Deprecate [...] means
> somewhere to the left of the 'limited use' model?"  The spectrum
> of choices, including the 'limited use' model, had been presented
> during that same meeting.  Although the group had decided to
> rule out the 'limited use' model (and presumably anything to the
> left of it as well) in Atlanta, nothing precludes new information
> from prompting a review of old decisions.
>
> The question posed on the list was more concise, simply "Should we
> deprecate IPv6 site-local unicast addressing?"  This question is
> not ambiguous.
>
> The deprecation of site-local addresses in their current form has
> served a useful role in forcing the working group to recognize the
> problems that the original definition had and work to address them.
> The IESG finds nothing unusual about how the question was asked or
> how the working group has proceeded.
>
> There is strong consensus in the IESG that deprecation is the
> correct technical decision, but we have done our best to separate
> our technical preferences from the process issue in considering
> this appeal.
>
> In summary, the IESG upholds the chairs' and INT ADs' decisions.
>
> The IESG
>






From owner-ietf@ietf.org  Mon Oct 13 10:37:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08307
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 10:37:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A93mP-0000qi-RW
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 10:34:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A81YQ-0000lM-01
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 13:59:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09828
	for <ietf@ietf.org>; Fri, 10 Oct 2003 13:59:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81YL-0006z1-00
	for ietf@ietf.org; Fri, 10 Oct 2003 13:59:49 -0400
Received: from evrtwa1-ar8-4-65-016-099.evrtwa1.dsl-verizon.net ([4.65.16.99] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81YK-0006yp-00
	for ietf@ietf.org; Fri, 10 Oct 2003 13:59:48 -0400
Received: from eaglet (127.0.0.1:3236)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S35E85> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 10 Oct 2003 10:59:54 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: <iab@iab.org>
Cc: <iesg@ietf.org>, <ietf@ietf.org>, <ipv6@ietf.org>
Subject: RE: Appeal to the IAB on the site-local issue
Date: Fri, 10 Oct 2003 10:59:45 -0700
Message-ID: <IKEDILMOGFKPCDJAMFKKAEDOCMAA.alh-ietf@tndh.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 IMO, Build 9.0.6604 (9.0.2911.0)
In-reply-to: <E320A8529CF07E4C967ECC2F380B0CF902335083@bsebe001.americas.nokia.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Additional input for your consideration.

Margaret.Wasserman@nokia.com wrote:
> ...
> In other words, we found that there was consensus to deprecate AND
> replace site-locals, ...
Witness the situation where the chair is after the fact defining what the
working group agreed to. There was nothing about 'replacement' in the
question that was asked.

Coupling this with her earlier comment:
> I think it should be harder to add a new feature to a specification
> than to take one out.
shows that, now as AD, the bar for a disambiguated local range will be
higher if the pronouncement is allowed to stand, than what is necessary to
fix the existing specification.

Tony







From owner-ietf@ietf.org  Mon Oct 13 10:38:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08446
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 10:38:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A93mQ-0000rJ-2o
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 10:34:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A81dJ-0000qb-Lu
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 14:04:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10046
	for <ietf@ietf.org>; Fri, 10 Oct 2003 14:04:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81dH-00072x-00
	for ietf@ietf.org; Fri, 10 Oct 2003 14:04:55 -0400
Received: from evrtwa1-ar8-4-65-016-099.evrtwa1.dsl-verizon.net ([4.65.16.99] helo=tndh.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81dF-00072p-00
	for ietf@ietf.org; Fri, 10 Oct 2003 14:04:54 -0400
Received: from eaglet (127.0.0.1:3440)
	by tndh.net with [XMail 1.16 (Win32/Ix86) ESMTP Server]
	id <S35E87> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 10 Oct 2003 11:05:00 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "Thomas Narten" <narten@us.ibm.com>,
        "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        "Tony Hain" <alh-ietf@tndh.net>, "IAB" <iab@iab.org>,
        "The IESG" <iesg@ietf.org>, <ipv6@ietf.org>, "IETF" <ietf@ietf.org>
Subject: RE: Appeal to the IAB on the site-local issue 
Date: Fri, 10 Oct 2003 11:04:50 -0700
Message-ID: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.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 IMO, Build 9.0.6604 (9.0.2911.0)
In-reply-to: <200310101559.h9AFxcQR005188@rotala.raleigh.ibm.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thomas Narten wrote:
> ...
> Popping up a level, there's a more basic thing that I fail to
> understand about this appeal. If the decision to deprecate was so
> wrong and flawed, how does one explain that the community seems to
> support it?

You are listening to a very limited subset of the 'community'. I have had
several questions from fortune 500 network managers as to 'what now?' They
plan to roll out IPv6 with addresses that are in either the FEC0 range
anyway, or are trusting that the proposed replacement FC00 will be finalized
soon.

> From some of Tony's notes, one would think that process
> ran amok in this case with a horrible end result that goes against the
> will of the WG. But I don't see the community agreeing with that view.
> E.g., see a recent note from the IPv6 chairs on the subject
> (appended).  From it, it is clear that there is strong community
> support to deprecate SLs.

Take the biased questions in context, all choices started with 'Deprecate
Site-Local ...' You can get any answer you want as long as you get to frame
the question and later define what the answer means.

Tony

>  Thus, the idea that the consensus call was
> fatally flawed, that the community doesn't support the decision and
> that we consequently somehow need to reset the clock and pretend that
> the last 6 months didn't happen and that we must start the entire
> conversation over about what to do with SLs just doesn't make any
> sense to me.
>
> Thomas
>
> From: Bob Hinden & Brian Haberman <hinden@iprg.nokia.com>
> To: ipv6@ietf.org
> Cc: hinden@iprg.nokia.com, Brian Haberman <brian@innovationslab.net>
> Date: Tue, 16 Sep 2003 10:55:33 -0700
> Subject: Results of Poll
>
> The results of the poll (appended below) started by the chairs in early
> August to get more feed back from the working about how to deprecate
> site-local are as follows:
>
>     Preference A   32     45%
>     Preference B   31     44%
>     Preference C    8     11%
>     --------------------------
>     Total Votes    71    100%
>
> The raw votes are available at:
>
>      http://people.nokia.net/~hinden/ipv6-choices.html
>
> If we missed your preference or got it wrong, please let us know.
>
> There are a few conclusions that can be seen in this poll.
>
> Only 11% of the people responding wanted to defer the deprecation of
> site-local until an alternative was deployed.  89% wanted to deprecate
> prior to an alternative being standardized or at the same time an
> alternative was standardized.
>
> There was not a consensus about tieing the deprecation of site-local to
> defining an alternative or do the deprecation before defining an
> alternative.  The working group is closely split on this.  Even combing
> preferences B & C (i.e., 55%) does not form a consensus.
>
> Based on this, the chairs will plan to move the deprecation document and
> the local addressing specification forward at approximately the
> same time,
> but will not do anything to officially tie them together.
>
> Bob Hinden / Brian Haberman
> IPv6 w.g. chairs
>
>
>
> >Date: Mon, 04 Aug 2003 11:06:55 -0700
> >To: ipng@sunroof.eng.sun.com
> >From: Bob Hinden <hinden@IPRG.nokia.com>
> >Subject: Moving forward on Site-Local and Local Addressing
> >Cc: hinden@iprg.nokia.com
> >
> >[IPv6 working group chair hat on]
> >
> >I think the working group has been making good progress on replacing
> >site-local addresses and wanted to get feed back from the
> working group on
> >how we should move forward.  This is not intended to directly relate to
> >the ongoing appeal of the working groups decision to deprecate the usage
> >site-local addresses, but to get feedback on how to proceed.  I think it
> >is very important that we move forward on this issue and not rehash what
> >has happened in the past.
> >
> >We now have a combined local addressing requirements document
> ><draft-hain-templin-ipv6-limitedrange-00.txt>, a specific alternative to
> >site-local addresses draft <draft-hinden-ipv6-global-local-addr-02.txt>
> >(accepted as a working group item at the Vienna IETF), and will
> soon have
> >a draft describing why site-local addresses are being deprecated
> and doing
> >the formal deprecation (authors identified and outline discussed at the
> >Vienna IETF).  Note that all of these documents will proceed through the
> >normal working group and IETF processes of last calls and review.
> >
> >I think legitimate questions have been raised about how the
> working group
> >should go about deprecating site-local addresses given their maturity in
> >the current specifications and use in deployed products.  Specifically
> >should they be deprecated independently from having an alternative
> >solution available, at the same time an alternative is available, or
> >sometime after an alternative is available.  A forth alternative
> is to not
> >replace site-local addresses in any form, but I think the working group
> >has made it clear that this is not a reasonable alternative.
> >
> >I would like to hear from the working group on how we should proceed.  I
> >think the choices are:
> >
> >A) Deprecate Site-Local addresses independently from having an
> alternative
> >solution available.  This would mean that the working group should treat
> >the deprecation, and requirements and solution documents outlined above
> >independently from each other.  If there was no consensus on an
> >alternative a replacement would not happen.
> >
> >B) Deprecate Site-Local addresses at the same time as a alternative
> >solution is agreed to.  This would mean advancing both documents at the
> >same time and making them include normative references to each other to
> >insure that they were published at the same time.  This would result in
> >the deprecation only happening if a consensus was reached on an
> alternative.
> >
> >C) Deprecate Site-Local addresses after an alternative is defined,
> >standardized, and in operational practice.  This would mean not
> advancing
> >a deprecation document until there was operational evidence that the
> >alternative was working and shown to be an improvement over Site-Local
> >addresses.
> >
> >Note:  In the above choices "Deprecate Site-Local addresses" means
> >publishing an RFC that does the formal deprecation.
> >
> >Please respond to the list with your preference, or if there is an
> >alternative approach that is an improvement from the ones I outlined.  I
> >hope that many of you will respond.
> >
> >Thanks,
> >Bob
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------






From owner-ietf@ietf.org  Mon Oct 13 10:39:36 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08570
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 10:39:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A93mQ-0000rU-AP
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 10:34:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A82Ns-0002h9-QW
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 14:53:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12292;
	Fri, 10 Oct 2003 14:52:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A82Nq-0007gj-00; Fri, 10 Oct 2003 14:53:03 -0400
Received: from alicia.nttmcl.com ([216.69.69.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A82Np-0007e9-00; Fri, 10 Oct 2003 14:53:02 -0400
Received: from nttmcl.com (daal.nttmcl.com [216.69.69.11])
	by alicia.nttmcl.com (8.12.9/8.12.5) with ESMTP id h9AIqMHB029432;
	Fri, 10 Oct 2003 11:52:23 -0700 (PDT)
	(envelope-from gene@nttmcl.com)
Message-ID: <3F86FFD5.4050706@nttmcl.com>
Date: Fri, 10 Oct 2003 11:52:05 -0700
From: "Eugene M. Kim" <gene@nttmcl.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20030925
X-Accept-Language: en-us, en, ko-kr, ko
MIME-Version: 1.0
To: Tony Hain <alh-ietf@tndh.net>
CC: IETF IPv6 Working Group <ipv6@ietf.org>,
        The Internet Engineering Task Force <ietf@ietf.org>,
        The Internet Engineering Steering Group <iesg@ietf.org>,
        The Internet Architecture Board <iab@iab.org>
Subject: Re: Appeal to the IAB on the site-local issue
References: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net>
In-Reply-To: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tony Hain wrote:

>You are listening to a very limited subset of the 'community'. I have had
>several questions from fortune 500 network managers as to 'what now?' They
>plan to roll out IPv6 with addresses that are in either the FEC0 range
>anyway, or are trusting that the proposed replacement FC00 will be finalized
>soon.
>  
>

With all due respect, it seems that it would be beneficial for both 
camps (for and against SL) to hear, even now, the real concerns directly 
from the operation people and to let them participate in the decision 
themselves.  I'm afraid isn't particularly effective nor or appealing 
just to claim `There are many people who are silent now but have their 
stake in SL and would be jeopardized by this decision,' when the 
discussion and decision processes have been open to the public.  I'm 
sure that the IAB and the IESG would also be happy to hear opinions 
directly from them, because that will give a clearer and broader view.

It'd be a totally different story though, if you officially represented 
a group of operation people when you opposed SL deprecation.  I 
apologize if this was indeed the case.

Regards,
Eugene






From owner-ietf@ietf.org  Mon Oct 13 10:42:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08952
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 10:42:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A93qI-0001JW-59
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 10:38:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8REv-0002q3-1F
	for ietf@asgard.ietf.org; Sat, 11 Oct 2003 17:25:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13329
	for <ietf@ietf.org>; Sat, 11 Oct 2003 17:25:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8REt-00002d-00
	for ietf@ietf.org; Sat, 11 Oct 2003 17:25:27 -0400
Received: from web13506.mail.yahoo.com ([216.136.175.85])
	by ietf-mx with smtp (Exim 4.12)
	id 1A8REt-00002Y-00
	for ietf@ietf.org; Sat, 11 Oct 2003 17:25:27 -0400
Message-ID: <20031011212527.93140.qmail@web13506.mail.yahoo.com>
Received: from [68.118.70.100] by web13506.mail.yahoo.com via HTTP; Sat, 11 Oct 2003 14:25:27 PDT
Date: Sat, 11 Oct 2003 14:25:27 -0700 (PDT)
From: Mark Seery <mark@mseery.com>
Subject: Re: accusations of cluelessness
To: ietf@ietf.org
Cc: Scott Bradner <sob@harvard.edu>
In-Reply-To: <200310112038.h9BKc7AI011903@newdev.harvard.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Scott's data point gives a better view of what is reserved/not allocated, but
another data point is that only 30%-32% of the IPv4 address space is currently
being advertised (according to RIB dumps at routeviews.org).

-mark

--- Scott  Bradner <sob@harvard.edu> wrote:
> 
> > the reason I don't try to repudiate BCP 5 is that it's clear that for IPv4
> > we're out of addresses,
> 
> total BS
> 
> http://www.iana.org/assignments/ipv4-address-space
> 






From owner-ietf@ietf.org  Mon Oct 13 10:42:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08984
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 10:42:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A93qH-0001Iz-Qa
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 10:38:37 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Alb-0003h0-Kp
	for ietf@asgard.ietf.org; Fri, 10 Oct 2003 23:50:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06621
	for <ietf@ietf.org>; Fri, 10 Oct 2003 23:49:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8AlZ-0007FP-00
	for ietf@ietf.org; Fri, 10 Oct 2003 23:50:05 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8AlY-0007FM-00
	for ietf@ietf.org; Fri, 10 Oct 2003 23:50:04 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1A8AlT-00003y-00; Fri, 10 Oct 2003 22:49:59 -0500
Date: Fri, 10 Oct 2003 23:49:59 -0400
From: John C Klensin <john@jck.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: ietf@ietf.org
Subject: Re: Removing features
Message-ID: <267843758.1065829799@scan.jck.com>
In-Reply-To: <C4319890-FB6A-11D7-B291-00039388672E@muada.com>
References:  <C4319890-FB6A-11D7-B291-00039388672E@muada.com>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I am about to embarrass myself by asking two stupid and naive 
questions.  But it feels like time for one of us who is not 
strongly involved emotionally with one side or the other of this 
issue to do so.   It seems to me that "site local" is actually 
two different things:

	(1) A set of semantics and expectations about, e.g.,
	applications behavior, otherwise known as "the feature".
	
	(2) An address range.

Is that correct, or is that controversial too?

Now part of the justification for IPv6 is to have "enough" 
address space.  We may be moving toward that being the only 
justification, but that is another discussion.   "Enough" 
presumably includes sufficient headroom that we can make a 
mistake about allocation strategies and deal with it by simply 
retiring the block.  One would not want to do that often, 
especially with large blocks, but we ought to be able to survive 
more than "never".

Given that, and given the argument that some important and 
hard-to-reverse decisions have been made that use that address 
range, is it plausible to:

	(1) Remove, deprecate, or otherwise dispose of, the
	feature.
	
	(2) Permanently retire the address range so it is never
	allocated and identify it in the relevant records as
	"retired".

Now, we have pretty strong statements around to the effect that, 
if an address range isn't allocated, one is not supposed to use 
it and certainly isn't supposed to let it leak.  One could even 
reinforce that with a statement/ standard/ BCP encouraging 
filtering the range, which would bring us more or less back to 
the 1918 situation (reserved space, no semantics).  But an 
enterprise that thought it needed local space could presumably 
use that range, with appropriate filters, etc., but without 
assuming that, e.g., applications would treat it in a special 
way.

I don't expect this suggestion to make anyone on either side 
happy, but is it possibly a way out of the "you can't really 
deprecate that without causing worse damage" part of this mess?

       john






From owner-ietf@ietf.org  Mon Oct 13 10:45:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09309
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 10:45:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A93tC-00023U-Fe
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 10:41:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8zdI-0005SO-9R
	for ietf@asgard.ietf.org; Mon, 13 Oct 2003 06:08:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28899;
	Mon, 13 Oct 2003 06:08:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8zdF-00015U-00; Mon, 13 Oct 2003 06:08:53 -0400
Received: from d12lmsgate-5.de.ibm.com ([194.196.100.238] helo=d12lmsgate.de.ibm.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8zdE-00015H-00; Mon, 13 Oct 2003 06:08:52 -0400
Received: from d12relay01.megacenter.de.ibm.com (d12relay01.megacenter.de.ibm.com [9.149.165.180])
	by d12lmsgate.de.ibm.com (8.12.10/8.12.8) with ESMTP id h9DA8LNb112166;
	Mon, 13 Oct 2003 12:08:21 +0200
Received: from ochsehorn.zurich.ibm.com (ochsehorn.zurich.ibm.com [9.4.16.140])
	by d12relay01.megacenter.de.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h9DA8EuB251724;
	Mon, 13 Oct 2003 12:08:15 +0200
Received: from zurich.ibm.com (sig-9-145-226-186.de.ibm.com [9.145.226.186])
	by ochsehorn.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id MAA33196;
	Mon, 13 Oct 2003 12:08:12 +0200
Message-ID: <3F8A7972.AF55E365@zurich.ibm.com>
Date: Mon, 13 Oct 2003 12:07:46 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,fr,de
MIME-Version: 1.0
To: ipv6@ietf.org
CC: iab@iab.org, iesg@ietf.org, ietf@ietf.org
Subject: Re: Removing features
References: <E320A8529CF07E4C967ECC2F380B0CF902335089@bsebe001.americas.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The word "deprecating" has a quite precise meaning in standards writing,
which is not the same as "removing". Rather than debating this cross-posted
on several lists, why don't people watch out for 
draft-ietf-ipv6-deprecate-site-local-01.txt which will appear in a few days,
and see if they agree with the way it's written? And then debate it on
the relevant list?

   Brian

Margaret.Wasserman@nokia.com wrote:
> 
> Hi Fred,
> 
> > So in the general case I don't see a problem with deprecating
> > things under the right circumstances, but I do have a problem with
> > removing them outright. Deprecation doesn't prevent people from using
> > them, but outright removal can be dangerous. And in this case, the
> > assertion that one can still use the address prefix in a local manner
> > is simply incorrect; it can be assigned at the whim of IANA, and
> > network administrations need to plan accordingly.
> 
> Actually, we are being very careful about this in the deprecation
> of IPv6 site-local addressing.  Christian Huitema and Brian Carpenter
> have co-authored a very carefully written deprecation document that
> makes it clear how these addresses should be treated to avoid problems
> with existing site-local implementations.  And, we are planning to
> instruct IANA not to return these addresses to the regular allocation
> pool.
> 
> Margaret
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Brian E Carpenter 
Distinguished Engineer, Internet Standards & Technology, IBM 

NEW ADDRESS <brc@zurich.ibm.com> PLEASE UPDATE ADDRESS BOOK





From owner-ietf@ietf.org  Mon Oct 13 10:46:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09482
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 10:46:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A93tC-00023u-MD
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 10:41:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8zuJ-0005du-CU
	for ietf@asgard.ietf.org; Mon, 13 Oct 2003 06:26:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29260;
	Mon, 13 Oct 2003 06:26:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8zuG-0001Dq-00; Mon, 13 Oct 2003 06:26:28 -0400
Received: from d12lmsgate-5.de.ibm.com ([194.196.100.238] helo=d12lmsgate.de.ibm.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8zuA-0001DW-00; Mon, 13 Oct 2003 06:26:27 -0400
Received: from d12relay02.megacenter.de.ibm.com (d12relay02.megacenter.de.ibm.com [9.149.165.196])
	by d12lmsgate.de.ibm.com (8.12.10/8.12.8) with ESMTP id h9DAP7Nb012936;
	Mon, 13 Oct 2003 12:25:22 +0200
Received: from ochsehorn.zurich.ibm.com (ochsehorn.zurich.ibm.com [9.4.16.140])
	by d12relay02.megacenter.de.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h9DAOlA2080264;
	Mon, 13 Oct 2003 12:24:47 +0200
Received: from zurich.ibm.com (sig-9-145-226-186.de.ibm.com [9.145.226.186])
	by ochsehorn.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id MAA35940;
	Mon, 13 Oct 2003 12:24:45 +0200
Message-ID: <3F8A7D53.8BA9138F@zurich.ibm.com>
Date: Mon, 13 Oct 2003 12:24:19 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,fr,de
MIME-Version: 1.0
To: The Internet Architecture Board <iab@iab.org>
CC: Tony Hain <alh-ietf@tndh.net>, IETF IPv6 Working Group <ipv6@ietf.org>,
        The Internet Engineering Task Force <ietf@ietf.org>,
        The Internet Engineering Steering Group <iesg@ietf.org>
Subject: Re: Appeal to the IAB on the site-local issue
References: <IKEDILMOGFKPCDJAMFKKEEDOCMAA.alh-ietf@tndh.net> <3F86FFD5.4050706@nttmcl.com> <3F87250F.7050700@it.su.se> <011f01c38f6c$99c12dc0$6401a8c0@ssprunk> <3F871946.400@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I believe that the best outcome for the IETF, and for its constituency,
including enterprise network operators, is for the IPv6 WG to get on with
what it's doing (documenting the deprecation of site-local, and developing
alternatives). I believe the worst outcome for the IETF would be to waste the 
time of busy people (and I'm sadly aware that this message will go to several
thousand people) over a consensus call that was not even about a document
but just a decision in principle. Personally I see no abuse of process in
either the face to face consensus call or the subsequent email poll; the
fact that the questions asked had some degree of ambiguity is simply a result
of the complexity involved. I recommend that the IAB deals with this appeal
as quickly as possible, and avoids future time wasting by constructing a
response that makes further appeals on the same topic pointless.

Personally, this is my last message on this thread and I won't be reading
it again either. I have work to do.

   Brian

Eliot Lear wrote:
> 
> Stephen Sprunk wrote:
> > Or we all just got sick of the bickering and accepted defeat (unlike Tony).
> >
> > For the record, I can't support deprecating site locals until we have
> > something else approved to replace them -- at which point I say good
> > riddance.  There are several drafts in the WG to that end which haven't
> > gained any momentum thus far.
> 
> And this is why the appeal is in my opinion untimely.  The working group
> has not yet been given a chance to provide any documentation on that
> "What next?" question Tony asked.  For the IESG or the IAB to interfere
> at this stage would be micromanagement.
> 
> But here we are.  Tony has decided to push an appeal of a "vote", and
> not even one that generated a document.  That the appeal has even gotten
> this far seems is a flaw in the process.
> 
> Had the IESG been able to disallow the appeal, simply on this basis,
> then perhaps the working group could actually provide documents about
> which we could argue over technical merit.  As it stands, I predict yet
> another round of appeals once IETF last call closes, and the document is
> reviewed by the IESG.
> 
> Welcome to Court TV, IETF style.
> 
> Eliot
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Brian E Carpenter 
Distinguished Engineer, Internet Standards & Technology, IBM 

NEW ADDRESS <brc@zurich.ibm.com> PLEASE UPDATE ADDRESS BOOK





From owner-ietf@ietf.org  Mon Oct 13 12:35:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14341
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 12:35:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A95Vy-0007wR-GV
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 12:25:46 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A95QE-0007qX-QH
	for ietf@asgard.ietf.org; Mon, 13 Oct 2003 12:19:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13732
	for <ietf@ietf.org>; Mon, 13 Oct 2003 12:19:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A95QD-0004zw-00
	for ietf@ietf.org; Mon, 13 Oct 2003 12:19:49 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A95QD-0004zn-00
	for ietf@ietf.org; Mon, 13 Oct 2003 12:19:49 -0400
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id h9DGJjS02735;
	Mon, 13 Oct 2003 09:19:45 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.9.3/8.8.6) id JAA00277;
	Mon, 13 Oct 2003 09:19:45 -0700 (PDT)
Date: Mon, 13 Oct 2003 09:19:45 -0700 (PDT)
Message-Id: <200310131619.JAA00277@gra.isi.edu>
To: ietf@ietf.org, garmitage@swin.edu.au
Subject: Re: Let the market be judge (Re: accusations of cluelessness)
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

  *> 
  *> But that's really not the point here. The role of an _engineering_ taskforce
  *> is to act like engineers, not a vanity press. Our output should be educated
  *> guidance to the wider community - created with diligence and offered with humility.
  *> We can do no more and should do no less.


Grenville,

Nicely said!!  I would like to see your motto inscribed over the
IETF portals... "We create with diligence and offer with humility".

Bob Braden





From owner-ietf@ietf.org  Mon Oct 13 12:39:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14551
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 12:39:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A95fn-0008If-G8
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 12:35:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A95Z4-00085h-UF
	for ietf@asgard.ietf.org; Mon, 13 Oct 2003 12:28:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14090;
	Mon, 13 Oct 2003 12:28:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A95Z1-00055Q-00; Mon, 13 Oct 2003 12:28:55 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A95Z1-00055G-00; Mon, 13 Oct 2003 12:28:55 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.9/8.12.2) with ESMTP id h9DGSn6U028870;
	Mon, 13 Oct 2003 12:28:49 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.9/8.12.2/Submit) id h9DGSnDO028869;
	Mon, 13 Oct 2003 12:28:49 -0400 (EDT)
Date: Mon, 13 Oct 2003 12:28:49 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200310131628.h9DGSnDO028869@newdev.harvard.edu>
To: iab@ietf.org
Subject: Re: Appeal to the IAB on the site-local issue
Cc: iesg@ietf.org, ietf@ietf.org
Sender: owner-ietf@ietf.org
Precedence: bulk



In private email I was asked to review the "tape" of the IPv6 discussion in
San Francisco.

ftp://limestone.uoregon.edu/pub/videolab/video/ietf56/ietf56%20-%2003202003%20-%20INT%20ipv6.rm

The SL discussion starts at 1:02 into the session.

The chairs first presented a set of slides talking about various SL related
options. The presentation was interrupted with questions from the floor
quite a few times during the discussion of the "exclusive" model (wherein a
v6 node would be a SL node of a global addressing node) - it was clear to
me that there was quite a bit of confusion about this model.  There were
few interruptions during the discussions about the other models.

The chairs opened the floor for general discussion at 1:39 into the
session.  The discussion was careful and extensive.  After a while it
became clear, as noted by Thomas, that more people were arguing for
eliminating SL than had been the case in the past and few people were
arguing for SL addressing. Those that were arguing in favor of SL mostly
said that SL and v6 NATs were going to happen anyway but no one seemed all
that concerned that the IETF define such addresses (e.g. Deno pointed out
that people would just pick their own if the IETF did not.)

At 2:07 into the session the chairs conferred and said that they would ask
a simple yes or no question (in reality they asked two questions) about
deprecating IPv6 SL addresses.  (Not eliminate them in that the sense that
the prefix would not be reassigned for other uses.)  Margaret noted that
the simple questions covered a lot of details that were not called out.

After 10 minutes of discussion to clarify the intent of the questions
Margaret asked for a show of hands for:
	1/ how many people want to deprecate the use of IPv6 SL addresses?
	2/ how many people do not want to deprecate the use of IPv6 SL
	  addresses?

She asked the first question twice so they could get a count of hands the
second time.  The result was 102 hands in favor of deprecating and 20
opposed.  The chairs declared that there was rough consensus in the session
to deprecate the use of IPv6 SL addressing but that this consensus would
now be taken to the list to verify.

After my review of the tape I have come to the following conclusions:

	1/ there was a lot of confusion over the details of at least the
	   exclusive model for the use of SL

	2/ it was a clear sense of the people who chose to express their
	   opinion in favor of deprecating IPv6 addresses (I have no 
	   way of knowing what fraction of the room chose to express 
	   an opinion because the IETF web site says that no meeting 
	   report was received so I have no way to know how many people 
	   were in the room.)

RFC 2418 says:
   ... Decisions reached during a face-to-face meeting about
   topics or issues which have not been discussed on the mailing list,
   or are significantly different from previously arrived mailing list 
   consensus MUST be reviewed on the mailing list.

   and

   In the case where a consensus which has been reached during a face-
   to-face meeting is being verified on a mailing list the people who
   were in the meeting and expressed agreement must be taken into
   account.  If there were 100 people in a meeting and only a few people
   on the mailing list disagree with the consensus of the meeting then
   the consensus should be seen as being verified. 

I followed the discussion on the mailing list.  In my opinion, there was
considerable less clarity of view on the list than in the meeting.

I know of no way to figure out what overlap there was between the people
expressing their opinions on the list and those who expressed their opinion
during the face-to-face session but it seems likely that the ratio of
opinion is somewhere between 3/4 (the ratio reported by Margaret about the
mailing list discussion) and 4/5 (the ration in the meeting).  

While I would rather see rough consensus not wind up with 20 or more
percent of the IETF community (or at least the part of the community that
expressed an opinion) disagreeing with a decision. (That many people may
have input that the rest of the community dismisses at its peril.) I have
to support the working group chair's assertion that rough consensus was
found in this case.

I will follow up this note with two others later today but I wanted to
limit this note to the specific topic of the level of consensus and
confusion.

Scott




From owner-ietf@ietf.org  Mon Oct 13 13:07:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15550
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 13:07:19 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A964k-0001Ov-DE
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 13:01:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A960b-0001Ch-1P
	for ietf@asgard.ietf.org; Mon, 13 Oct 2003 12:57:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15192
	for <ietf@ietf.org>; Mon, 13 Oct 2003 12:57:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A960Z-0005RS-00
	for ietf@ietf.org; Mon, 13 Oct 2003 12:57:23 -0400
Received: from smtp102.mail.sc5.yahoo.com ([216.136.174.140])
	by ietf-mx with smtp (Exim 4.12)
	id 1A960Y-0005RP-00
	for ietf@ietf.org; Mon, 13 Oct 2003 12:57:23 -0400
Received: from ts46-01-qdr3166.mrgnhll.ca.charter.com (HELO yahoo.com) (m?seery@68.118.70.100 with plain)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 13 Oct 2003 16:57:21 -0000
Message-ID: <3F8AD981.1020208@yahoo.com>
Date: Mon, 13 Oct 2003 09:57:37 -0700
From: mark seery <m_seery@yahoo.com>
Reply-To: m_seery@yahoo.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bob Braden <braden@ISI.EDU>
CC: ietf@ietf.org, garmitage@swin.edu.au
Subject: Re: Let the market be judge (Re: accusations of cluelessness)
References: <200310131619.JAA00277@gra.isi.edu>
In-Reply-To: <200310131619.JAA00277@gra.isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bob Braden wrote:

>  *> 
>  *> But that's really not the point here. The role of an _engineering_ taskforce
>  *> is to act like engineers, not a vanity press. Our output should be educated
>  *> guidance to the wider community - created with diligence and offered with humility.
>  *> We can do no more and should do no less.
>
>
>Grenville,
>
>Nicely said!!  I would like to see your motto inscribed over the
>IETF portals... "We create with diligence and offer with humility".
>
>Bob Braden
>
>
>
>  
>
Bob, I agree this is a good ethos, which I support, and in general, the 
IETF is trending back in this direction, the discussion over the last 
~year of meatier meetings being one example of the trend in this 
direction; yours, Keith's and Grenville's expressions being others. The 
specific issue though in this case, IMO, was whether engineering was 
conflicting with pragmatics (WRT existing deployments) - happily, the OT 
thread appears to be flushing this out and moving on. Obviously, the 
long-lived tension will always be between under-engineering a solution 
and over-engineering a solution. As this subthread shows, discussing the 
philosophy  doesn't advance the ball on any one particular technical 
issue very much, only skilled engineers arguing opposing views (a good 
thing) can do that.

Best....




From owner-ietf@ietf.org  Mon Oct 13 13:07:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15566
	for <ietf-web-archive@odin.ietf.org>; Mon, 13 Oct 2003 13:07:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A964l-0001PC-D6
	for ietf-list@asgard.ietf.org; Mon, 13 Oct 2003 13:01:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9627-0001EI-Dw
	for ietf@asgard.ietf.org; Mon, 13 Oct 2003 12:58:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15235
	for <ietf@ietf.org>; Mon, 13 Oct 2003 12:58:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9626-0005SY-00
	for ietf@ietf.org; Mon, 13 Oct 2003 12:58:58 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9625-0005S0-00
	for ietf@ietf.org; Mon, 13 Oct 2003 12:58:57 -0400
Subject: RE: Removing features
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 13 Oct 2003 09:58:17 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C612@server2003.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Removing features
thread-index: AcORmTBPwi0Lo1oYSVyZ6MBva/VxxQADEWkA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "John C Klensin" <john@jck.com>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>
Cc: <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

John,


> John C Klensin wrote:
> (1) A set of semantics and expectations about,
> e.g., applications behavior, otherwise known
> as "the feature".
> (2) An address range.
> Is that correct, or is that controversial too?

It looks correct to me although I will detail the feature part below.


> Now part of the justification for IPv6 is to
> have "enough" address space.  We may be moving
> toward that being the only justification, but
> that is another discussion. "Enough" presumably
> includes sufficient headroom that we can make a
> mistake about allocation strategies and deal
> with it by simply retiring the block. One would
> not want to do that often, especially with large
> blocks, but we ought to be able to survive more
> than "never".

Correct. There are 1,024 possible /10s, for example. Screwing up with
three or four is not such a big deal. I'm not saying it's good, but if
the resolution of the issue is that we have to iterate three times on a
solution and end up wasting three times a /10, be it.


> But an enterprise that thought it needed local
> space could presumably use that range, with
> appropriate filters, etc., but without assuming
> that, e.g., applications would treat it in a
> special way.
> I don't expect this suggestion to make anyone
> on either side happy, but is it possibly a way
> out of the "you can't really deprecate that
> without causing worse damage" part of this mess?

The feedback I am getting from enterprise operators is that they
generally don't care about any special application behavior. At the
application level, for all practical purposes there is no need to
differentiate site-locals from other addresses.

The arguments I have heard from app developers indicate that there are
trying to fix issues that are none of their concern. If I design a
network that makes apps break, it's my problem, not theirs.
Specifically, enterprise operators generally:

- Are inclined not to use the multi-address capability of IPv6. Inside
  the enterprise network, it brings complications that are not worth
  the advantages, _especially_ for parts of the network that are
  earmarked as private.

- Do not flood root servers with reverse lookup queries for private
  addresses (I want my traceroutes to work on the inside of the network
  too, so I long ago configured reverse lookup for private addresses on
  my internal DNS servers).

- Deal with ambiguity when there is a collision like when sites merge.
  Besides, IPv6 ambiguity for private addresses could be resolved.

What enterprise operators care about is router behavior, so something
along the lines of scoping will have to be delivered at some point. This
point does not need to be right away as it could be accommodated with
manual filters that will remain in place anyway for defense in depth
considerations.

Michel.




From owner-ietf@ietf.org  Tue Oct 14 10:40:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12538
	for <ietf-web-archive@odin.ietf.org>; Tue, 14 Oct 2003 10:40:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9Q5E-0000hh-5X
	for ietf-list@asgard.ietf.org; Tue, 14 Oct 2003 10:23:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9Q4J-0000gY-Iw
	for ietf@asgard.ietf.org; Tue, 14 Oct 2003 10:22:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11765
	for <ietf@ietf.org>; Tue, 14 Oct 2003 10:22:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Q4H-0003BB-00
	for ietf@ietf.org; Tue, 14 Oct 2003 10:22:33 -0400
Received: from [193.247.235.157] (helo=laptop2.kurtis.autonomica.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Q4G-0003Ay-00
	for ietf@ietf.org; Tue, 14 Oct 2003 10:22:32 -0400
Received: from kurtis.pp.se (localhost [127.0.0.1])
	by laptop2.kurtis.autonomica.se (8.12.9/8.10.2) with ESMTP id h9EELcwr002678;
	Tue, 14 Oct 2003 16:21:39 +0200 (CEST)
Date: Tue, 14 Oct 2003 16:21:32 +0200
Subject: Re: Removing features
Content-Type: text/plain; charset=ISO-8859-1; format=fixed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "John C Klensin" <john@jck.com>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>, <ietf@ietf.org>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C612@server2003.arneill-py.sacramento.ca.us>
Message-Id: <B5CA3518-FE51-11D7-BF24-000A9598A184@kurtis.pp.se>
Content-Transfer-Encoding: quoted-printable
X-Pgp-Rfc2646-Fix: 1
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

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


On m=E5ndag, okt 13, 2003, at 18:58 Europe/Stockholm, Michel Py wrote:

>
> - Do not flood root servers with reverse lookup queries for private
>   addresses (I want my traceroutes to work on the inside of the =
network
>   too, so I long ago configured reverse lookup for private addresses =
on
>   my internal DNS servers).
>
Say again?

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.2

iQA/AwUBP4wGcKarNKXTPFCVEQIoYQCg1L8Xn3TCLI9OpL79Rl0A7+fiz1cAniBW
mN/Mkht8hIilgKGa2mKKq6gt
=3Dlqp9
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Tue Oct 14 11:12:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14056
	for <ietf-web-archive@odin.ietf.org>; Tue, 14 Oct 2003 11:12:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9Qkp-0002fv-SL
	for ietf-list@asgard.ietf.org; Tue, 14 Oct 2003 11:06:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9Qko-0002eQ-2F
	for ietf@asgard.ietf.org; Tue, 14 Oct 2003 11:06:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13837
	for <ietf@ietf.org>; Tue, 14 Oct 2003 11:06:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Qkn-0003tV-00
	for ietf@ietf.org; Tue, 14 Oct 2003 11:06:29 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Qkm-0003t6-00
	for ietf@ietf.org; Tue, 14 Oct 2003 11:06:28 -0400
Subject: RE: Removing features
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 14 Oct 2003 08:05:56 -0700
Content-class: urn:content-classes:message
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C62F@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Removing features
thread-index: AcOSXoIHneToUDQ2T0q6v/yu9Q3VOgAAkThA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Kurt Erik Lindqvist" <kurtis@kurtis.pp.se>
Cc: "John C Klensin" <john@jck.com>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Kurtis,

>> Michel Py wrote:
>> - Do not flood root servers with reverse lookup queries for
>> private addresses (I want my traceroutes to work on the
>> inside of the network too, so I long ago configured reverse
>> lookup for private addresses on my internal DNS servers).

> Kurt Erik Lindqvist wrote:
> Say again?

Where are all these bogus requests to reverse lookup an RFC1918 address
coming from? From hosts with a RFC1918 address that do a traceroute.
Even if the target of the traceroute is outside, the first hop is
inevitably inside. The traceroute does a reverse lookup on each hop for
display purposes; this reverse lookup fails on the local DNS server and
might end up in one of the roots.

However, if a reverse lookup zone (1.168.192.in-addr.arpa in this case)
is configured in the DNS server that the host doing the traceroute is
using, and if the correct PTR is configured (1.1.168.192.in-addr.arpa
PTR cisco.arneill-py.sacrament.ca.us) the traceroute correctly
reverse-lookups the first hop and that request never ends up in a root
server. Also, it's faster because it does not waste 5 seconds timing out
on the request.

tracert www.ietf.org
  1     1 ms     1 ms     1 ms  cisco.arneill-py.sacrament.ca.us
[192.168.1.1]
  2    12 ms    12 ms    61 ms
adsl-209-233-126-254.dsl.scrm01.pacbell.net [209.233.126.254]

Michel.




From owner-ietf@ietf.org  Tue Oct 14 11:24:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14586
	for <ietf-web-archive@odin.ietf.org>; Tue, 14 Oct 2003 11:24:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9QwS-0003N7-27
	for ietf-list@asgard.ietf.org; Tue, 14 Oct 2003 11:18:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9Qvo-0003L9-Pl
	for ietf@asgard.ietf.org; Tue, 14 Oct 2003 11:17:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14288;
	Tue, 14 Oct 2003 11:17:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Qvn-00041j-00; Tue, 14 Oct 2003 11:17:51 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Qvm-00041g-00; Tue, 14 Oct 2003 11:17:51 -0400
Received: from newdev.harvard.edu (localhost [127.0.0.1])
	by newdev.harvard.edu (8.12.9/8.12.2) with ESMTP id h9EFHi6U008636;
	Tue, 14 Oct 2003 11:17:44 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.12.9/8.12.2/Submit) id h9EFHiPF008635;
	Tue, 14 Oct 2003 11:17:44 -0400 (EDT)
Date: Tue, 14 Oct 2003 11:17:44 -0400 (EDT)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200310141517.h9EFHiPF008635@newdev.harvard.edu>
To: iab@ietf.org
Subject: RE: Appeal to the IAB on the site-local issue
Cc: iesg@ietf.org, ietf@ietf.org
Sender: owner-ietf@ietf.org
Precedence: bulk

Yesterday I posted a message that said that I agreed with the IPv6 working
group chairs that rough consensus was reached to deprecate IPv6 site local
addresses.  That said, I do have an issue on the discussion that led up to
that consensus decision.  I do not think there was much of an actual
discussion on the topic.

The working group chair's presentation on the site local options listed
five options for the working group moving forward in regards to the site
local question.  These options ranged from eliminating site local addresses
to fully embracing the concept and working out all the details of how to
use them.  But they only discussed the middle three options.  They reported
that the consensus in the Atlanta meeting was to not support outright
elimination or full embrace so those options were not included in the
chair's presentation of the advantages and disadvantages of the various
options.

The discussion during the chair's presentation basically did not touch on
the pros and cons of having site local addresses per se - a few 'they
should just go away' statements were made but no exploration of the issues.

The open discussion after the presentation also did not explore the issues
but there were a greater number of people who felt that SL addresses should
be eliminated from IPv6.

As I mentioned in yesterday's note - Thomas and others noticed the
sentiment  against SL and the chairs wound up asking the question they did
(about deprecating SL) as a result.

But, for what it's worth, I do not think that there was sufficient
discussion of the option of deprecating SL addresses before the consensus
check was made.  So, in a way, I think the consensus was wrongly reached,
even if I agree that consensus was reached.

At this point I do not know what to suggest be done. As I will explain in
another note, I am in the minority on this topic but even so I'm not sure
that much good would come from readdressing the issue.  It may be best to
stick with the consensus for now and only look at the issue again if it
becomes clear that the future usefulness of IPv6 depends on the IETF
understanding the use of private addressing in IPv6, and that may never
happen. 




From owner-ietf@ietf.org  Tue Oct 14 11:52:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16030
	for <ietf-web-archive@odin.ietf.org>; Tue, 14 Oct 2003 11:52:12 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9RKz-0004gM-Fc
	for ietf-list@asgard.ietf.org; Tue, 14 Oct 2003 11:43:53 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9RJ2-0004ZL-9e
	for ietf@asgard.ietf.org; Tue, 14 Oct 2003 11:41:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15402;
	Tue, 14 Oct 2003 11:41:41 -0400 (EDT)
From: Margaret.Wasserman@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9RJ0-0004Ir-00; Tue, 14 Oct 2003 11:41:50 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9RIz-0004Io-00; Tue, 14 Oct 2003 11:41:49 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9EFfld11774;
	Tue, 14 Oct 2003 18:41:47 +0300 (EET DST)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6548501a96ac158f25461@esvir05nok.ntc.nokia.com>;
 Tue, 14 Oct 2003 18:41:46 +0300
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 14 Oct 2003 08:41:42 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Appeal to the IAB on the site-local issue
Date: Tue, 14 Oct 2003 11:41:41 -0400
Message-ID: <E320A8529CF07E4C967ECC2F380B0CF902335099@bsebe001.americas.nokia.com>
Thread-Topic: Appeal to the IAB on the site-local issue
Thread-Index: AcOSZmxnZPr1ylXURy2brL1Ua+upAwAAIvDw
To: <sob@harvard.edu>, <iab@ietf.org>
Cc: <iesg@ietf.org>, <ietf@ietf.org>
X-OriginalArrivalTime: 14 Oct 2003 15:41:42.0704 (UTC) FILETIME=[AA8C2B00:01C39269]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


Hi Scott,

> But, for what it's worth, I do not think that there was sufficient
> discussion of the option of deprecating SL addresses before=20
> the consensus check was made.  So, in a way, I think the consensus=20
> was wrongly reached, even if I agree that consensus was reached.

If the San Francisco meeting was the only time/place that the IPv6
WG had discussed the topic of what to do regarding IPv6 site-local=20
addressing, then I might agree with you.

However, this had been the most hotly debated and analyzed topic
in the IPv6 WG for the previous two years.  We had exchanged literally=20
thousands of e-mail messages on this topic on the IPv6 list, and we
had held lengthy discussions on this topic at several IETF meetings.

In particular, Brian Haberman and Rob Austein presented information
regarding site-locals in Atlanta:

http://www.ietf.org/proceedings/02nov/slides/ipv6-5.pdf
http://www.ietf.org/proceedings/02nov/slides/ipv6-6.pdf

I also posted a lengthy draft on this topic in December 2002, entitled=20
"The Impact of Site-Local Addressing in IPv6".  This draft has since
expired, but the lastest version can still be found at:

http://www.ietf.org/internet-drafts/draft-wasserman-ipv6-sl-impact-02.txt=


So, the discussion during the San Francisco IETF meeting was not the=20
only information available to IPv6 particpants regarding this topic. =20
Any active IPv6 participant should already have been reasonably=20
well-informed regarding this topic before arriving in San Francisco.

Margaret=20



From owner-ietf@ietf.org  Tue Oct 14 12:00:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16766
	for <ietf-web-archive@odin.ietf.org>; Tue, 14 Oct 2003 12:00:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9RRQ-0004vs-R7
	for ietf-list@asgard.ietf.org; Tue, 14 Oct 2003 11:50:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9RQN-0004n9-8H
	for ietf@asgard.ietf.org; Tue, 14 Oct 2003 11:49:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15796;
	Tue, 14 Oct 2003 11:49:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9RQL-0004QS-00; Tue, 14 Oct 2003 11:49:26 -0400
Received: from h-135-207-24-32.research.att.com ([135.207.24.32] helo=mailman.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9RQL-0004Q0-00; Tue, 14 Oct 2003 11:49:25 -0400
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mailman.research.att.com (8.12.8/8.12.8) with ESMTP id h9EFio84011279;
	Tue, 14 Oct 2003 11:44:50 -0400
Received: from berkshire.research.att.com (raptor.research.att.com [135.207.23.32])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h9EFmoZ13696;
	Tue, 14 Oct 2003 11:48:50 -0400 (EDT)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id D3A4E7B43; Tue, 14 Oct 2003 11:48:49 -0400 (EDT)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: Margaret.Wasserman@nokia.com
Cc: sob@harvard.edu, iab@ietf.org, iesg@ietf.org, ietf@ietf.org
Subject: Re: Appeal to the IAB on the site-local issue 
In-Reply-To: Your message of "Tue, 14 Oct 2003 11:41:41 EDT."
             <E320A8529CF07E4C967ECC2F380B0CF902335099@bsebe001.americas.nokia.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 14 Oct 2003 11:48:49 -0400
Message-Id: <20031014154849.D3A4E7B43@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <E320A8529CF07E4C967ECC2F380B0CF902335099@bsebe001.americas.nokia.co
m>, Margaret.Wasserman@nokia.com writes:
>
>Hi Scott,
>
>> But, for what it's worth, I do not think that there was sufficient
>> discussion of the option of deprecating SL addresses before 
>> the consensus check was made.  So, in a way, I think the consensus 
>> was wrongly reached, even if I agree that consensus was reached.
>
>If the San Francisco meeting was the only time/place that the IPv6
>WG had discussed the topic of what to do regarding IPv6 site-local 
>addressing, then I might agree with you.

What Margaret said.  This is hardly the first time the issue has come 
up; it's been debated for years.

		--Steve Bellovin, http://www.research.att.com/~smb





From owner-ietf@ietf.org  Tue Oct 14 12:07:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17218
	for <ietf-web-archive@odin.ietf.org>; Tue, 14 Oct 2003 12:07:08 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9Ra7-0005x7-W1
	for ietf-list@asgard.ietf.org; Tue, 14 Oct 2003 11:59:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9Fwt-0006FR-4B
	for ietf@asgard.ietf.org; Mon, 13 Oct 2003 23:34:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11657;
	Mon, 13 Oct 2003 23:34:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Fwq-0005G3-00; Mon, 13 Oct 2003 23:34:12 -0400
Received: from zmamail05.zma.compaq.com ([161.114.64.105])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Fwo-0005Ft-00; Mon, 13 Oct 2003 23:34:11 -0400
Received: from tayexg12.americas.cpqcorp.net (tayexg12.americas.cpqcorp.net [16.103.130.103])
	by zmamail05.zma.compaq.com (Postfix) with ESMTP
	id 1D073BAD1; Mon, 13 Oct 2003 23:33:49 -0400 (EDT)
Received: from tayexc13.americas.cpqcorp.net ([16.103.130.26]) by tayexg12.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 13 Oct 2003 23:33:48 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Appeal to the IAB on the site-local issue
Date: Mon, 13 Oct 2003 23:33:48 -0400
Message-ID: <9C422444DE99BC46B3AD3C6EAFC9711B047CA107@tayexc13.americas.cpqcorp.net>
Thread-Topic: Appeal to the IAB on the site-local issue
Thread-Index: AcOPSaYyBNicFkTzQ+yTuDCkgopc2QCtlkBA
From: "Bound, Jim" <jim.bound@hp.com>
To: "Scott Bradner" <sob@harvard.edu>, <iab@iab.org>
Cc: <iesg@ietf.org>, <ietf@ietf.org>, <ipv6@ietf.org>
X-OriginalArrivalTime: 14 Oct 2003 03:33:48.0745 (UTC) FILETIME=[FAD6E390:01C39203]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Scott,

I agree with your caution about "removal" 100% and that it requires a
much stronger consenus and test to execute removal, and do not want it
done in anyway but from a serious analysis of those consequences. I also
agree the issue has nothing to do with which side of the fence one sits
on the issue.  It is a process issue and removal is a very serious
decision.

But I read all the discussions that lead up to the March 2003 meeting,
and was in that March 2003 meeting. It was one of the strongest
consensus moments I have seen that happened that day in that room in
that working group and was IMO over 3/4 of the attendees.  And then the
follow up email to the meeting did not overturn that consenus or the
view of the Chairs, ADs, and no one jumped over the fence, who supported
the decision to my knowledge.

Hence, I agree with the bar you articulate for this case, but I for one
truly believe the IETF process was met to proceed with the
recommendation of the Chairs on this issue and is supported by strong
cosensus of the IETF direct participants.

Also the draft below URL provides a good initial discussion and
framework of the issue and also a means to reduce any pain caused by
this removal.  It is not my endorsement of the draft at this time as a
qualification.

http://www.ietf.org/internet-drafts/draft-ietf-ipv6-deprecate-site-local
-01.txt

Other questions not related to this specific issue you articulated so
well are as follows for the future as input to you who knows far more
about this than I and I realize that completely:

1.  Why did the WG agree to this consensus?  An important question?  I
will not comment on this in public.

2.  Did the implementors who agreed understand the ramifications to code
base and were they participants?  The answer is yes.

3.  Were the needs of the market considered in the decision?  I don't
think by all but do we ever use this bar?  As I said to you once when
you were on the IESG consistency is imperative.  The market is
reprsented by our participants.  If participants are not here to support
the IETF they do not get heard.  We have no way to trust one or a few to
represent an entire market other than present their individual view.
That may or may not influence the WG, it depends on the respect the
individual has with their peers I guess?

I will stop there.

Thanks for doing this and documenting the importance of "removal"
publicly it is a very important understanding we must know well before
we ever do removals.  I do "feel" we had consenus as a note.
/jim

**************************************
"if it looks good, you'll see it;
if it sounds good, you'll hear it,
if it's marketed right, you'll buy it;
 but...if it's real, you'll feel it."
Kid Rock
**************************************






> -----Original Message-----
> From: Scott Bradner [mailto:sob@harvard.edu]=20
> Sent: Friday, October 10, 2003 10:17 AM
> To: iab@iab.org
> Cc: iesg@ietf.org; ietf@ietf.org; ipv6@ietf.org
> Subject: re: Appeal to the IAB on the site-local issue
>=20
>=20
> IAB,
>=20
> Please consider this input for the IAB discussion on Tony's=20
> appeal of the site local decision.  This should not be=20
> considered a separate appeal. (Which I would think would have=20
> to start at the beginning with the working group chairs.)
>=20
> I do not have an opinion on the particulars of Tony's appeal=20
> since I was not at the meeting in question and only followed=20
> the discussion on the mailing list.  Nor is this an opinion=20
> based on the technical question under discussion.  (Although=20
> I think some of the cures proposed to the site-local disease=20
> are quite a bit worse than the disease itself.)
>=20
> I would like to reiterate the concern I expressed on the=20
> mailing list back in July - I think there may been a=20
> violation of the IETF consensus process=20
> in this case.
>=20
> It is my opinion that there is a difference between a working=20
> group deciding to adopt a technology and a working group=20
> deciding to delete a technology from an existing IETF=20
> specification.  It is my opinion that the second case should=20
> require a stronger demonstration of consensus to change since=20
> the decision effects existing implementations, documentation,=20
> text books etc.
>=20
> But even without any need to show any extra level of=20
> consensus I did not see that even a minimal level of rough=20
> consensus was demonstrated to remove site local addresses.
>=20
> The claim was made on the list that there was not consensus=20
> to keep site local addresses, I think that is the wrong=20
> question to ask - the proposal was to change a specification=20
> after its publication there should have been a rough=20
> consensus to remove the feature.
>=20
> I did not see rough consensus to do so based on my monitoring=20
> the list.
>=20
> Scott
>=20
> (this is the letter I sent back in July on the topic)
>=20
> From sob Mon Jul 28 15:11:01 2003
> To: Erik.Nordmark@Sun.COM
> Subject: Re: state-of-art SLs
> Cc: ipng@sunroof.eng.sun.com
> In-Reply-To: <Roam.SIMC.2.0.6.1059396655.12753.nordmark@bebop.france>
>=20
>=20
> > The chairs have read all of the messages on the list, and based on=20
> > your considerable input, we have determined that the IPv6=20
> WG does have=20
> > rough consensus to deprecate the usage of IPv6 site-local unicast=20
> > addressing AND to investigate alternative mechanisms for local=20
> > addressing and local access
> . control.
>=20
> humm - it is not all that often that we have said that 2/3 is=20
> rough consensus in the IETF - in my exterience if 1/3 is not=20
> in support then I would not claim consensus (even 6 grit) -=20
> 3/4 would be very rough indeed, 5/6 would be the mininum I=20
> would say was "rough consensus"
>=20
>=20
> just when does "rough consensus" faid out in this model?
>=20
> Scott
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20





From owner-ietf@ietf.org  Tue Oct 14 17:38:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03777
	for <ietf-web-archive@odin.ietf.org>; Tue, 14 Oct 2003 17:38:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9WmZ-0001Dh-PB
	for ietf-list@asgard.ietf.org; Tue, 14 Oct 2003 17:32:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9Wle-00016H-Ne
	for ietf@asgard.ietf.org; Tue, 14 Oct 2003 17:31:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03538;
	Tue, 14 Oct 2003 17:31:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Wlc-0001b2-00; Tue, 14 Oct 2003 17:31:44 -0400
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Wlb-0001aU-00; Tue, 14 Oct 2003 17:31:44 -0400
Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57])
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id h9EL9i126502;
	Tue, 14 Oct 2003 17:09:44 -0400
From: "bill" <bill@strahm.net>
To: "'Steven M. Bellovin'" <smb@research.att.com>,
        <Margaret.Wasserman@nokia.com>
Cc: <sob@harvard.edu>, <iab@ietf.org>, <iesg@ietf.org>, <ietf@ietf.org>
Subject: RE: Appeal to the IAB on the site-local issue 
Date: Tue, 14 Oct 2003 14:30:55 -0700
Message-ID: <008d01c3929a$7499c800$70d912c0@mobilebill>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <20031014154849.D3A4E7B43@berkshire.research.att.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I'd like to ask an interesting question that might help the IETF, but
not this debate unfortunately.

The meta question is how did we get into a state where some people have
very conflicting views on how well this topic was adjusted (discussed
for years vs. an hour at a IETF meeting in SF), and what can we do in
the future to not allow this process failure to happen again.

Without laying blame anywhere outside of a process failure - I detect
two opinions
1) The WG chairs feel this issue had drug on too long - and finally
reached consensus in SF
2) Some members of the WG feel that an uninformed decision was made in
SF because there wasn't enough time for debate

To be honest - I don't have a personal opinion, and frankly don't know
enough of the details to make a technical choice on which way this
debate should go.  However what appears to be happening is there is an
accusation against our open philosophy inside the IETF.

So from participants, chairs, IESG - are there any lessons to be learned
here that should apply to other WG so that other WG don't have process
failures like this one ?

Bill
In message
<E320A8529CF07E4C967ECC2F380B0CF902335099@bsebe001.americas.nokia.co
m>, Margaret.Wasserman@nokia.com writes:
>
>Hi Scott,
>
>> But, for what it's worth, I do not think that there was sufficient 
>> discussion of the option of deprecating SL addresses before the 
>> consensus check was made.  So, in a way, I think the consensus was 
>> wrongly reached, even if I agree that consensus was reached.
>
>If the San Francisco meeting was the only time/place that the IPv6 WG 
>had discussed the topic of what to do regarding IPv6 site-local 
>addressing, then I might agree with you.

What Margaret said.  This is hardly the first time the issue has come 
up; it's been debated for years.







From owner-ietf@ietf.org  Tue Oct 14 18:06:27 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05254
	for <ietf-web-archive@odin.ietf.org>; Tue, 14 Oct 2003 18:06:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9XCW-00035W-Oy
	for ietf-list@asgard.ietf.org; Tue, 14 Oct 2003 17:59:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9XA9-0002rD-6j
	for ietf@asgard.ietf.org; Tue, 14 Oct 2003 17:57:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04524;
	Tue, 14 Oct 2003 17:56:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9XA7-00023u-00; Tue, 14 Oct 2003 17:57:03 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9XA6-00023r-00; Tue, 14 Oct 2003 17:57:02 -0400
Received: from cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 14 Oct 2003 15:06:05 -0700
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h9ELuTeH029850;
	Tue, 14 Oct 2003 14:56:30 -0700 (PDT)
Received: from cisco.com (stealth-10-32-241-46.cisco.com [10.32.241.46])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AND27889;
	Tue, 14 Oct 2003 14:56:28 -0700 (PDT)
Date: Tue, 14 Oct 2003 17:56:26 -0400
Subject: Re: Appeal to the IAB on the site-local issue 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <iab@ietf.org>, <iesg@ietf.org>, <ietf@ietf.org>
To: "bill" <bill@strahm.net>
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <008d01c3929a$7499c800$70d912c0@mobilebill>
Message-Id: <42485F8F-FE91-11D7-B68A-000A95E35274@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Tuesday, October 14, 2003, at 05:30 PM, bill wrote:
> So from participants, chairs, IESG - are there any lessons to be 
> learned
> here that should apply to other WG so that other WG don't have process
> failures like this one ?

There's a veritable process failure epidemic going on.  It
seems to me that this specific sort of problem is inevitable
from time to time and that it's not sufficiently pervasive
to think that this (where "this" refers to a difference of
opinion as to whether or not an agreement has been reached)
is not a spot problem.  We do tend to have a problem with
people who simply will not accept "no" for an answer but
I don't think this is one of those cases.

Although, come to think of it, to the extent that this represents
a broad category of process failure it would be around our
inability to do consensus well, whether it's as simple as
learning how to ask questions better or publishing the decisions
that have been reached, or as subtle as how we identify
decisions (this aging hippie looks at "80% of the people in
the room said 'yes' so we've got rough consensus" and thinks
"oy vey") and actively try to create consensus.  These issues
are under discussion, etc., elsewhere (the problem working
group) and approaches to solving them are, as well (the "solutions"
mailing list), and it may be worthwhile to take a look at the
documents and mailing list archives to see if you feel there's
more we could be doing around this specific problem area.

Melinda




From owner-ietf@ietf.org  Tue Oct 14 18:06:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05330
	for <ietf-web-archive@odin.ietf.org>; Tue, 14 Oct 2003 18:06:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9XCW-00034D-2r
	for ietf-list@asgard.ietf.org; Tue, 14 Oct 2003 17:59:32 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9X2M-0002dR-5o
	for ietf@asgard.ietf.org; Tue, 14 Oct 2003 17:49:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04320
	for <ietf@ietf.org>; Tue, 14 Oct 2003 17:48:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9X2K-0001zf-00
	for ietf@ietf.org; Tue, 14 Oct 2003 17:49:00 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9X2J-0001zB-00
	for ietf@ietf.org; Tue, 14 Oct 2003 17:48:59 -0400
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 015B661C15; Tue, 14 Oct 2003 23:48:29 +0200 (CEST)
Date: Tue, 14 Oct 2003 23:48:10 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org, problem-statement@alvestrand.no
Subject: IESG proposed statement on the IETF mission
Message-ID: <157547561.1066175290@localhost>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="==========FE903CE760CF831D098F=========="
Sender: owner-ietf@ietf.org
Precedence: bulk

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

Greetings,

As part of the discussions about change process within
the IETF, the IESG has come to believe that a somewhat longer statement of 
the IETF's mission and social dynamics might provide useful context for the 
community's discussion.  As part of that, we'd like to put the following 
document out for feedback.

It incorporates lots of ideas and some text from existing RFCs
and IETF web pages, but is more focused on change than those have
been.  We hope it captures a sense of the context of the work of
improving the IETF, by capturing some of the social dynamics which
have been an implicit part of the IETF's work and style over the years.

We also hope that by making some of those implicit elements more
explicit, we may find it easier to understand how to make changes
that will "go with the grain" of the IETF's history and culture.

We'd be happy to have feedback on it, either sent to the IETF list
for public discussion or to the IESG.  This is an informal piece of work, 
and may never be published in RFC form, but may rather appear on the IETF 
web pages somewhere.

Your comments are welcome!

		Harald Alvestrand
		For the IESG


--==========FE903CE760CF831D098F==========
Content-Type: text/plain; charset=us-ascii; name="social-contract.txt"
Content-Disposition: attachment; filename="social-contract.txt"; size=10544
Content-Transfer-Encoding: 7bit


		The IETF Mission and Social Contract


Introduction
------------

The Internet Engineering Task Force (IETF) is a large open
international community of network engineers concerned with the
evolution of the Internet architecture and facilitating the
operation of the Internet.  In the seventeen years since thirty-odd
engineers first met in a single room, the Internet and the IETF
have grown considerably; the IETF is attempting to adapt to these
changes.

Most of the basic processes and the social contracts by which the
IETF works, both formal and informal, were developed when it was a
community of fifty to two hundred engineers.  Much of its internal
communication depended on long-term personal relationships and an
implicit understanding of shared goals and culture.  This has
worked well for many years and much growth.  The IETF has been and
is a very successful organization, and has produced much serious
work which has both furthered its own goals of Internet evolution
and had a notable effect on global human society.

The processes and social contracts that worked for fifty engineers
have managed to sustain the IETF in dealing with a community of
thousands of engineers and a greatly expanded technology and market
space.  However, while Dave Clark's famous saying

  "We do not believe in kings, presidents, or voting.
   We believe only in rough consensus and running code,"

is still a touchstone of the IETF culture, the rapid growth of
participation in the IETF, the growth of the Internet itself,
and the rapid integration of Internet technology in  real-world markets
and society in general are seriously straining the IETF's traditional 
understated and informal communication and methods.

Though the process of organizational change has actually been going
on continuously for a long time, it would be useful to state more
formally many previously implicit understandings and to make
explicit some previously informal processes.  This note tries to
lay the social foundation for that continuing journey.


The IETF Mission
----------------

The IETF's mission has historically been embedded in a shared
understanding that making engineering choices based on the long
term interest of the Internet as a whole produces better long-term
results for each participant than making choices based on short term
considerations, because the value of those advantages is ultimately
derived from the health of the whole.  The long term interest of the
Internet includes the premise that "the Internet is for everyone".

Two years ago, the IESG felt that making the mission of the IETF
more explicit was needed.  The following terse statement has since
been promulgated, first by IESG members and then by others:

   "The purpose of the IETF is to create high quality, relevant,
    and timely standards for the Internet."

Note that this clearly positions the IETF primarily as a standards
development organization.  There are other activities in the IETF;
but if the IETF does not do its core mission, all else will quickly
fade.  This is intended to be an ordered list of characteristics. 
Timely standards of low quality or that are irrelevant will not 
serve the Internet's or the IETF's needs.

This leaves open the very interesting and difficult questions of
how to measure quality, relevance, and timeliness.  The IETF
has identified interoperability, security, and scalability as essential,
but without attaching measurements to those characteristics.

It is important that this is "For the Internet,"  and does not include 
everything that happens to use IP.  IP is being used in a myriad of 
real-world applications, such as controlling street lights, but the 
IETF does not standardize those applications.


Supporting Missions
-------------------

Historically, the IETF has also been a place for experimentation,
both with protocols and with operational practices.  Testbeds such
as the mbone, 6bone, etc., have been born, coordinated within, 
and run in association with the IETF.  Such efforts have been very
useful in developing high quality relevant standards.

The IETF has also had a strong operational component, with a tight
bond, and hence coordination, between protocol developers and
network operators, and has had many participants who did both.
This has provided valuable feedback to allow correction of
misguided standardization efforts, and has provided feedback to
sort out which standards were actually needed.  As the field has
grown explosively, specialization has set in, and market pressures
have risen, there has been less and less operator participation in
the IETF.


Social Dynamics
---------------

Growth has stressed many parts of the IETF's social and procedural
fabric, and it may be useful to consider some fundamental forces
that are causing these stresses.  As they are neither good nor bad,
it is not appropriate to call them "problems;" rather think of them
as social forces and dynamics.

Scaling - Increased Participation

The IETF is a semi-formal community of individual engineers, not of
organizations, expert in and dedicated to the growth and technical
development of the Internet.  With the popularity and explosive
growth of the Internet, the number and diversity of people wanting
or needing to participate in the IETF has grown a hundredfold.
Many of these have had experience in other standards orgizations
with different operating procedures and focus.  As good engineers,
these new participants have opinions, want to contribute, need to
find a place in the complex social and technology fabric, and, in
general, want to join the jostle of a now large organization.  As
the size and scope of the IETF have increased, the informal
mechanisms for incorporating new participants have been strained,
often creating the appearance of opaque barriers to entry.

Scaling - More Complex Technical Interactions

The number and span of interacting technologies has made the IETF a
far more complex work space, both technically and socially.  A
culture that worked for layers three and four and 50-300 engineers
is being severely stretched working at layers one through nine.
Furthermore, many new participants now come from a far wider set of
disciplines, making integration more difficult.

Scaling - More External Interactions

As the Internet has become widely popular, it has become a serious
marketplace and is being seen as the communication infrastructure
of the future.  This has drawn serious attention from external
forces such as vendors, press, regulators, politicians, and other
standards organizations, whose traditional work now interacts with
that of the IETF.  Often, the relationship turns out to be
tangential, but it takes a long time to get all parties to see
this.  The resultant need for quality interaction with these
external forces places new needs and stresses on the IETF's view of
how it represents itself.

Quality and Architectural Review

With the increase in complexity, it has become increasingly
difficult to maintain the high quality that the IETF has always
demanded.  A bit of engineering in one space can and usually does
interact with many other components of the Internet, and thus
requires deep multi-area review and consensus.  This has been most
easily seen with security and operational scaling considerations,
but actually happens across the board.

As the number of engineers and work areas increases, the number of
documents increases, and the resulting importance of and
interactions needed for inter-area quality coordination and review
grows as a product of these forces.

Replacing Personalities with Process

As the IETF grows and evolves, leaders come and go.  Hence, the
organization needs processes to both ensure continuity as leaders
succeed each other, and to ensure that the organization remains
open and fair, and can continue to interact successfully with the
more complex environment in which the IETF now operates.

But Not Too Much Process

On the other hand, the IETF culture has always been to have formal
processes grow only as needed, and it has resisted unneeded formal
structures as impeding timeliness and driving out key players.
There is deep cultural distrust of 'professional standards goers',
for Dave Clark's kings and presidents, and for institutional
authority.

Tension Among the Dynamics

Many of the above dynamics are in tension with each other; the IETF
can not always have its cake and eat it too.  One of the most
critical tensions is the increase in the number of documents and
the need for cross-technology review.  The number of articulate
engineers who have wide technological span and can and will review
a lot of documents is not growing as fast as the document count.


Changing What We Can Change
---------------------------------------------

These social dynamics can be seen as underlying drivers of many of
the problems identified by those attempting to improve the IETF.  As
part of the effort to diagnose those problems, identifying which of
the underlying forces are or are not within the control of the IETF is an
important aspect of targeting change.  For those within the control of
the IETF, a relatively small but fundamental change may engender
substantial improvements in a number of areas.  For those outside of
the control of the IETF, changes may need to focus on ameliorating symptoms
of the underlying problem or on enabling the community to work within
the identified constraints.  

As part of the ongoing effort to improve the IETF, there will always
be a number of specific proposals coming forward for discussion.  Some
may ask the community to consider changes to existing assumptions or
structures; others may be intended to provide specific solutions to
problems which require them.  As those proposals emerge, the first
step must be to recognize that the IETF will change over time, both as
the community's membership changes and as the work it does evolves.
In adapting the mechanisms by which the IETF operates, we are simply
recognizing that reality.  

No matter what type of change is proposed, however, it is essential to
make sure that the IETF continues to serve its basic mission well.
That mission not only supports an industry and enables a technology;
it makes the IETF as a community more than the sum of its parts.


--==========FE903CE760CF831D098F==========--




From owner-ietf@ietf.org  Tue Oct 14 18:29:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07569
	for <ietf-web-archive@odin.ietf.org>; Tue, 14 Oct 2003 18:29:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9XYl-0003SJ-KU
	for ietf-list@asgard.ietf.org; Tue, 14 Oct 2003 18:22:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9XXg-00035J-Iu
	for ietf@asgard.ietf.org; Tue, 14 Oct 2003 18:21:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07267;
	Tue, 14 Oct 2003 18:21:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9XXe-0002fE-00; Tue, 14 Oct 2003 18:21:22 -0400
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9XXd-0002er-00; Tue, 14 Oct 2003 18:21:22 -0400
Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57])
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id h9ELxS126822;
	Tue, 14 Oct 2003 17:59:28 -0400
From: "bill" <bill@strahm.net>
To: "'Melinda Shore'" <mshore@cisco.com>
Cc: <iab@ietf.org>, <iesg@ietf.org>, <ietf@ietf.org>
Subject: RE: Appeal to the IAB on the site-local issue 
Date: Tue, 14 Oct 2003 15:20:39 -0700
Message-ID: <000101c392a1$6690a010$70d912c0@mobilebill>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <42485F8F-FE91-11D7-B68A-000A95E35274@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I do not think there is anything approaching an epidemic going on.  It
is always good to look at what MIGHT be a process failure - understand
if it IS a failure (be more self critical before someone else points out
your failings) and if it is, see what can be learned and applied in the
future.

I really wish I personally had more time to look into the
problem/process WGs, but unfortunately - I have my other priorities.
And frankly - I trust the people that are there to do the right thing.  

Bill
On Tuesday, October 14, 2003, at 05:30 PM, bill wrote:
> So from participants, chairs, IESG - are there any lessons to be
> learned
> here that should apply to other WG so that other WG don't have process
> failures like this one ?

There's a veritable process failure epidemic going on.  It seems to me
that this specific sort of problem is inevitable from time to time and
that it's not sufficiently pervasive to think that this (where "this"
refers to a difference of opinion as to whether or not an agreement has
been reached) is not a spot problem.  We do tend to have a problem with
people who simply will not accept "no" for an answer but I don't think
this is one of those cases.

Although, come to think of it, to the extent that this represents a
broad category of process failure it would be around our inability to do
consensus well, whether it's as simple as learning how to ask questions
better or publishing the decisions that have been reached, or as subtle
as how we identify decisions (this aging hippie looks at "80% of the
people in the room said 'yes' so we've got rough consensus" and thinks
"oy vey") and actively try to create consensus.  These issues are under
discussion, etc., elsewhere (the problem working
group) and approaches to solving them are, as well (the "solutions"
mailing list), and it may be worthwhile to take a look at the documents
and mailing list archives to see if you feel there's more we could be
doing around this specific problem area.

Melinda





From owner-ietf@ietf.org  Tue Oct 14 18:29:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07572
	for <ietf-web-archive@odin.ietf.org>; Tue, 14 Oct 2003 18:29:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9XSN-0002AH-DJ
	for ietf-list@asgard.ietf.org; Tue, 14 Oct 2003 18:15:55 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9XMF-0008IN-Qq
	for ietf@asgard.ietf.org; Tue, 14 Oct 2003 18:09:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05827;
	Tue, 14 Oct 2003 18:09:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9XMD-0002My-00; Tue, 14 Oct 2003 18:09:34 -0400
Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9XMD-0002Mn-00; Tue, 14 Oct 2003 18:09:33 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h9F079w21495;
	Wed, 15 Oct 2003 02:07:09 +0200
Message-ID: <3F8C8FAD.7000400@it.su.se>
Date: Wed, 15 Oct 2003 02:07:09 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: bill <bill@strahm.net>
CC: "'Steven M. Bellovin'" <smb@research.att.com>,
        Margaret.Wasserman@nokia.com, sob@harvard.edu, iab@ietf.org,
        iesg@ietf.org, ietf@ietf.org
Subject: Re: Appeal to the IAB on the site-local issue
References: <008d01c3929a$7499c800$70d912c0@mobilebill>
In-Reply-To: <008d01c3929a$7499c800$70d912c0@mobilebill>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

bill wrote:
| I'd like to ask an interesting question that might help the IETF, but
| not this debate unfortunately.
|
| The meta question is how did we get into a state where some people have
| very conflicting views on how well this topic was adjusted (discussed

A contributing factor might be that starting with Yokohama and certainly
by SF the issue had attracted attention by people who don't normaly pay
close tabs to ipv6. Why that is is a separate discussion. That is why
(imo) we saw the confusion - suddenly the all the people in the room
and on the list were not speaking the same language or driven by the
same motivation (for good and/or bad).

	Cheers leifj
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/jI+s8Jx8FtbMZncRAgfKAKCsOPca/T2ozbxnaWJAbPF0tmBlpgCgkEgM
+SD0INMitSQ0LOtqlKY9vDs=
=ziFz
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Tue Oct 14 21:58:37 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13329
	for <ietf-web-archive@odin.ietf.org>; Tue, 14 Oct 2003 21:58:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9aiE-0001sy-JR
	for ietf-list@asgard.ietf.org; Tue, 14 Oct 2003 21:44:30 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9ahK-0001nu-Gm
	for ietf@asgard.ietf.org; Tue, 14 Oct 2003 21:43:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13038;
	Tue, 14 Oct 2003 21:43:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ahH-0004oU-00; Tue, 14 Oct 2003 21:43:31 -0400
Received: from coconut.itojun.org ([219.101.47.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ahG-0004oR-00; Tue, 14 Oct 2003 21:43:31 -0400
Received: from itojun.org (localhost [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP
	id 308B890; Wed, 15 Oct 2003 10:43:22 +0900 (JST)
To: hinden@iprg.nokia.com
Cc: Radia Perlman <radia.perlman@sun.com>,
        Mukesh Gupta <Mukesh.Gupta@nokia.com>
Cc: vrrp@ietf.org
Cc: ietf@ietf.org
Subject: draft-ietf-vrrp-ipv6-spec-05.txt lacks IPR clause
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
From: itojun@iijlab.net
Date: Wed, 15 Oct 2003 10:43:18 +0900
Message-Id: <20031015014322.308B890@coconut.itojun.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

	draft-ietf-vrrp-ipv6-spec-05.txt does not have IPR clause on it,
	even though cisco claims to have patent related to it.
	http://www.ietf.org/ietf/IPR/cisco-ipr-draft-ietf-vrrp-ipv6-spec.txt

itojun



From owner-ietf@ietf.org  Wed Oct 15 02:35:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15117
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 02:35:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9f5B-0002w2-I7
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 02:24:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9f56-0002u9-Ni
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 02:24:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07210
	for <ietf@ietf.org>; Wed, 15 Oct 2003 02:24:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9f53-0007Fx-00
	for ietf@ietf.org; Wed, 15 Oct 2003 02:24:21 -0400
Received: from laptop2.kurtis.autonomica.se ([192.71.80.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9f52-0007Fu-00
	for ietf@ietf.org; Wed, 15 Oct 2003 02:24:21 -0400
Received: from kurtis.pp.se (localhost [127.0.0.1])
	by laptop2.kurtis.autonomica.se (8.12.9/8.10.2) with ESMTP id h9F5QDwr002864;
	Wed, 15 Oct 2003 07:26:14 +0200 (CEST)
Date: Wed, 15 Oct 2003 07:26:10 +0200
Subject: Re: Removing features
Content-Type: text/plain; charset=US-ASCII; format=fixed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "John C Klensin" <john@jck.com>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>, <ietf@ietf.org>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C62F@server2003.arneill-py.sacramento.ca.us>
Message-Id: <15E51B5C-FED0-11D7-8B4F-000A9598A184@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
X-Pgp-Rfc2646-Fix: 1
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

>>> - Do not flood root servers with reverse lookup queries for
>>> private addresses (I want my traceroutes to work on the
>>> inside of the network too, so I long ago configured reverse
>>> lookup for private addresses on my internal DNS servers).
>
>> Kurt Erik Lindqvist wrote:
>> Say again?
>
> Where are all these bogus requests to reverse lookup an RFC1918 address
> coming from?


There are a hell of a lot traceroutes going on then...

Also note that at least at i.root there are a lot  more queries with 
src addresses being RFC1918. This is the same for f.root as far as I 
can remember.

> display purposes; this reverse lookup fails on the local DNS server and
> might end up in one of the roots.

Well, as for the reverse lookup it should end up with one of the AS112 
servers as the in-addr.arpa zones have been delegated.

> However, if a reverse lookup zone (1.168.192.in-addr.arpa in this case)
> is configured in the DNS server that the host doing the traceroute is
> using, and if the correct PTR is configured (1.1.168.192.in-addr.arpa
> PTR cisco.arneill-py.sacrament.ca.us) the traceroute correctly
> reverse-lookups the first hop and that request never ends up in a root
> server. Also, it's faster because it does not waste 5 seconds timing 
> out
> on the request.

I won't argue against you. Now, why don't people do this?

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.2

iQA/AwUBP4zadKarNKXTPFCVEQIk1gCg9wbLn6KW3um4Lg+BbyaBM3WO73QAn1AW
BnQMQ5eVfo1zHoprDRQkwFjG
=h//K
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Wed Oct 15 03:18:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18188
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 03:18:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9fqb-0007BY-Ef
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 03:13:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9fpd-00078w-3y
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 03:12:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17975
	for <ietf@ietf.org>; Wed, 15 Oct 2003 03:12:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9fpa-0000Im-00
	for ietf@ietf.org; Wed, 15 Oct 2003 03:12:26 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9fpa-0000Ij-00
	for ietf@ietf.org; Wed, 15 Oct 2003 03:12:26 -0400
Subject: RE: Removing features
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 15 Oct 2003 00:11:56 -0700
Content-class: urn:content-classes:message
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C640@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Removing features
thread-index: AcOS6GSWdAGjXCTrQluHVqxQrbQtVAAApz2g
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Kurt Erik Lindqvist" <kurtis@kurtis.pp.se>
Cc: "John C Klensin" <john@jck.com>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Kurtis,

> Kurt Erik Lindqvist wrote:
> There are a hell of a lot traceroutes going on then...

As pointed out by Keith privately, traceroutes are not the only culprit.
Telnet to a host from a private IP, it does a reverse lookup on your IP,
etc. Basically everything that triggers a reverse lookup adds to the
pain, but if reverse lookup is configured correctly on the local DNS
server it removes the pain for all apps as well.


> Now, why don't people do this?

Ask George Carlin.

Michel.




From owner-ietf@ietf.org  Wed Oct 15 10:49:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02882
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 10:49:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9mfU-0006Pv-Em
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 10:30:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9mf1-0006N2-No
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 10:29:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02212
	for <ietf@ietf.org>; Wed, 15 Oct 2003 10:29:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9mez-00052H-00
	for ietf@ietf.org; Wed, 15 Oct 2003 10:29:57 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9mez-00052E-00
	for ietf@ietf.org; Wed, 15 Oct 2003 10:29:57 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 2F61A14008; Wed, 15 Oct 2003 10:29:56 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 21222-03; Wed, 15 Oct 2003 10:29:55 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id CC45E13FD4; Wed, 15 Oct 2003 10:29:54 -0400 (EDT)
Date: Wed, 15 Oct 2003 10:26:17 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: moore@cs.utk.edu, kurtis@kurtis.pp.se, john@jck.com, iljitsch@muada.com,
        ietf@ietf.org
Subject: Re: Removing features
Message-Id: <20031015102617.29bf5762.moore@cs.utk.edu>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C640@server2003.arneill-py.sacramento.ca.us>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C640@server2003.arneill-py.sacramento.ca.us>
X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wed, 15 Oct 2003 00:11:56 -0700
"Michel Py" <michel@arneill-py.sacramento.ca.us> wrote:

> Kurtis,
> 
> > Kurt Erik Lindqvist wrote:
> > There are a hell of a lot traceroutes going on then...
> 
> As pointed out by Keith privately, traceroutes are not the only culprit.
> Telnet to a host from a private IP, it does a reverse lookup on your IP,
> etc. Basically everything that triggers a reverse lookup adds to the
> pain, but if reverse lookup is configured correctly on the local DNS
> server it removes the pain for all apps as well.

great.  now we'll have NAT boxes intercepting outgoing DNS traffic also.



From owner-ietf@ietf.org  Wed Oct 15 11:07:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03529
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 11:07:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9nA2-00023b-J1
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 11:02:02 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9n9L-00021L-OC
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 11:01:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03410
	for <ietf@ietf.org>; Wed, 15 Oct 2003 11:01:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9n9K-0005UW-00
	for ietf@ietf.org; Wed, 15 Oct 2003 11:01:18 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9n9K-0005UR-00
	for ietf@ietf.org; Wed, 15 Oct 2003 11:01:18 -0400
Subject: RE: Removing features
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 15 Oct 2003 08:00:46 -0700
Content-class: urn:content-classes:message
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C642@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Removing features
thread-index: AcOTKM6KzbxunPA8SUWAkBEAR1GsJwABAhwA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: "Kurt Erik Lindqvist" <kurtis@kurtis.pp.se>, <john@jck.com>,
        "Iljitsch van Beijnum" <iljitsch@muada.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> Keith Moore wrote:
> great.  now we'll have NAT boxes intercepting
> outgoing DNS traffic also.

That was not my point. My point was to have a DNS server in the inside
configured for reverse lookup of private IPs. What you mention would
help though.

Michel.




From owner-ietf@ietf.org  Wed Oct 15 11:14:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03868
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 11:14:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9nHF-0002ZN-Rg
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 11:09:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9nFI-0002HB-F6
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 11:07:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03489
	for <ietf@ietf.org>; Wed, 15 Oct 2003 11:07:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9nFH-0005Wc-00
	for ietf@ietf.org; Wed, 15 Oct 2003 11:07:27 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9nFG-0005WI-00
	for ietf@ietf.org; Wed, 15 Oct 2003 11:07:26 -0400
Received: from cisco.com (171.71.177.254)
  by sj-iport-2.cisco.com with ESMTP; 15 Oct 2003 08:03:39 -0700
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h9FF6reH018252;
	Wed, 15 Oct 2003 08:06:54 -0700 (PDT)
Received: from cisco.com (stealth-10-32-241-46.cisco.com [10.32.241.46])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AND87838;
	Wed, 15 Oct 2003 08:06:52 -0700 (PDT)
Date: Wed, 15 Oct 2003 11:06:49 -0400
Subject: Re: IESG proposed statement on the IETF mission
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: ietf@ietf.org, problem-statement@alvestrand.no
To: Harald Tveit Alvestrand <harald@alvestrand.no>
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <157547561.1066175290@localhost>
Message-Id: <33D8F6AA-FF21-11D7-B68A-000A95E35274@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

It's an interesting document, but it looks to me a bit much
like a problem description and I'm not sure how it relates
to other existing work (the problem description document in
the problem working group, most obviously).  I particularly
liked the discussion of the IETF mission - it could provide
the basis for tackling one problem that's been raised on
a number of occasions, which is that the organization doesn't
have a clear sense of mission or vision.  Even though in the
first paragraph of the "Social Dynamics" section you say that
"As they are neither good nor bad, it is not appropriate to
call them "problems;" rather think of them as social forces
and dynamics" a number of them really are framed as problems.
Indeed, it would be hard to define some way in which statements like
"making integration more difficult" are not problem statements.

I'd really like to see the document, which I think has good
fundamentals, refocused on mission and goals.

Melinda




From owner-ietf@ietf.org  Wed Oct 15 11:57:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06064
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 11:57:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9np5-0004AZ-F3
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 11:44:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9nnC-00047R-CU
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 11:42:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05349
	for <ietf@ietf.org>; Wed, 15 Oct 2003 11:42:21 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9nnB-00069r-00
	for ietf@ietf.org; Wed, 15 Oct 2003 11:42:29 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9nnA-00069o-00
	for ietf@ietf.org; Wed, 15 Oct 2003 11:42:28 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9FFgO5H006879;
	Wed, 15 Oct 2003 11:42:24 -0400
Message-Id: <200310151542.h9FFgO5H006879@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org
Subject: Re: Removing features 
In-Reply-To: Your message of "Wed, 15 Oct 2003 10:26:17 EDT."
             <20031015102617.29bf5762.moore@cs.utk.edu> 
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C640@server2003.arneill-py.sacramento.ca.us>
            <20031015102617.29bf5762.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1639971088P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 15 Oct 2003 11:42:24 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1639971088P
Content-Type: text/plain; charset=us-ascii

On Wed, 15 Oct 2003 10:26:17 EDT, Keith Moore said:

> great.  now we'll have NAT boxes intercepting outgoing DNS traffic also.

The really bad part is that they'll on the average do as good a job of intercepting
DNS traffic as they do of filtering outbound 1918-sourced packets in general. After
all, the root DNS boxes shouldn't ever see a 1918 packet unless (a) some site isn't
egress filtering properly *and* (b) their ISP isn't ingress filtering at the edge.

Egress *and* ingress filtering.  Belt and suspenders design.  Too bad there's so
many sites that still manage to leave their fly open anyhow.....

--==_Exmh_-1639971088P
Content-Type: application/pgp-signature

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

iD8DBQE/jWrgcC3lWbTT17ARAjY0AKDDFEJ4HUHYIJhaMPd0E4Ec7lGaYACfUX8R
kdg3rWVXheEAdiCWKIGGfvE=
=mAbz
-----END PGP SIGNATURE-----

--==_Exmh_-1639971088P--



From owner-ietf@ietf.org  Wed Oct 15 11:57:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06061
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 11:57:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9np5-0004Af-Vl
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 11:44:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9nne-00047w-FO
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 11:42:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05353
	for <ietf@ietf.org>; Wed, 15 Oct 2003 11:42:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9nnd-0006A7-00
	for ietf@ietf.org; Wed, 15 Oct 2003 11:42:57 -0400
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9nnc-0006A4-00
	for ietf@ietf.org; Wed, 15 Oct 2003 11:42:57 -0400
Received: from limbo (limbo.unfix.org [3ffe:8114:2000:240:200:39ff:fe77:1f3f])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP id 0C0B18311;
	Wed, 15 Oct 2003 17:42:53 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Michel Py'" <michel@arneill-py.sacramento.ca.us>,
        "'Keith Moore'" <moore@cs.utk.edu>
Cc: "'Kurt Erik Lindqvist'" <kurtis@kurtis.pp.se>, <john@jck.com>,
        "'Iljitsch van Beijnum'" <iljitsch@muada.com>, <ietf@ietf.org>
Subject: RE: Removing features
Date: Wed, 15 Oct 2003 17:42:54 +0200
Organization: Unfix
Message-ID: <007e01c39333$0057b8f0$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C642@server2003.arneill-py.sacramento.ca.us>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

Michel Py wrote:

> > Keith Moore wrote:
> > great.  now we'll have NAT boxes intercepting
> > outgoing DNS traffic also.
> 
> That was not my point. My point was to have a DNS server in the inside
> configured for reverse lookup of private IPs. What you mention would
> help though.

Which most people already have when configuring their local network
as they setup a local DNS server. Usually NAT boxes also include
a DNS server btw. Even my Alcatel Speedtouch *adsl modem* has one.
But I gladly use a much easier to configure bind ofcourse ;)

People not configuring these DNS servers usually use their ISP's
DNS servers and these should comply to AS112 standards, aka
serve empty versions of the rfc1918 zones and make themselves authoritive.
Afaik the latest bind distributions include at least setup examples
for rfc1918 addresses.

Shouldn't there be a BCP for such cases? Aka that ISP's should
have rfc1918/localhost/169.254.x.x zones in the DNS servers that
face their customers?

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / jeroen@unfix.org / http://unfix.org/~jeroen/

iQA/AwUBP41q/imqKFIzPnwjEQLEcACfWqTKtP0UAkAyRmEOYdDmRGyiE6UAoIF0
cn2z6DmYbo/tBDivtyMKHBdp
=1pV8
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Wed Oct 15 12:11:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06974
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 12:11:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9o8S-0005Zu-0i
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 12:04:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9o7j-0005Sg-6Y
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 12:03:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06552
	for <ietf@ietf.org>; Wed, 15 Oct 2003 12:03:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9o7h-0006Yr-00
	for ietf@ietf.org; Wed, 15 Oct 2003 12:03:41 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9o7X-0006Ye-00
	for ietf@ietf.org; Wed, 15 Oct 2003 12:03:32 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 4119314034; Wed, 15 Oct 2003 12:03:31 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 01785-07; Wed, 15 Oct 2003 12:03:30 -0400 (EDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 6ABCC14022; Wed, 15 Oct 2003 12:03:30 -0400 (EDT)
Date: Wed, 15 Oct 2003 11:58:24 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: moore@cs.utk.edu, kurtis@kurtis.pp.se, john@jck.com, iljitsch@muada.com,
        ietf@ietf.org
Subject: Re: Removing features
Message-Id: <20031015115824.403e88ab.moore@cs.utk.edu>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C642@server2003.arneill-py.sacramento.ca.us>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C642@server2003.arneill-py.sacramento.ca.us>
X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > Keith Moore wrote:
> > great.  now we'll have NAT boxes intercepting
> > outgoing DNS traffic also.
> 
> That was not my point. My point was to have a DNS server in the inside
> configured for reverse lookup of private IPs. 

one of the most-frequently cited justifications for NAT is plug-and-play.
expecting people to set up their own DNS servers sort of nullifies that.



From owner-ietf@ietf.org  Wed Oct 15 12:11:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06994
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 12:11:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9oBP-0005e8-IQ
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 12:07:31 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9o9M-0005as-QP
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 12:05:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06610
	for <ietf@ietf.org>; Wed, 15 Oct 2003 12:05:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9o9L-0006aH-00
	for ietf@ietf.org; Wed, 15 Oct 2003 12:05:23 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9o9K-0006Zn-00
	for ietf@ietf.org; Wed, 15 Oct 2003 12:05:23 -0400
Received: from cisco.com (sjc-vpn3-678.cisco.com [10.21.66.166])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with SMTP id h9FG4mH7015688;
	Wed, 15 Oct 2003 09:04:49 -0700 (PDT)
Received: by cisco.com (sSMTP sendmail emulation); Wed, 15 Oct 2003 12:04:45 -0400
Date: Wed, 15 Oct 2003 12:04:45 -0400
From: Scott W Brim <swb@employees.org>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org, problem-statement@alvestrand.no
Subject: Re: IESG proposed statement on the IETF mission
Message-ID: <20031015120445.O2320@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <swb@employees.org>,
	Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org,
	problem-statement@alvestrand.no
References: <157547561.1066175290@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <157547561.1066175290@localhost>; from harald@alvestrand.no on Tue, Oct 14, 2003 at 11:48:10PM +0200
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, Oct 14, 2003 11:48:10PM +0200, Harald Tveit Alvestrand allegedly wrote:
> As part of the discussions about change process within
> the IETF, the IESG has come to believe that a somewhat longer statement of 
> the IETF's mission and social dynamics might provide useful context for the 
> community's discussion.  As part of that, we'd like to put the following 
> document out for feedback.
> 
> It incorporates lots of ideas and some text from existing RFCs
> and IETF web pages, but is more focused on change than those have
> been.  We hope it captures a sense of the context of the work of
> improving the IETF, by capturing some of the social dynamics which
> have been an implicit part of the IETF's work and style over the years.

OK, but first, it doesn't clarify the mission, or the social contract.
At most it makes a couple vague statements after describing some general
problems.  It looks like the IESG has some sense of where the
problem-statement/solutions process is going, and wants to run with it.
That's okay -- but please say explicitly that's what's happening, if it
is.

> We also hope that by making some of those implicit elements more
> explicit, we may find it easier to understand how to make changes
> that will "go with the grain" of the IETF's history and culture.

What I want is a renewed, clear statement of the fundamental principles
of the IETF which must not be violated or weakened during the
problem/solution process.  It's important that the leadership of the
IETF keep clear themselves on what the fundamental principles are, and
to reiterate them when necessary (like now).  That's part of the social
contract itself.  There are principles which are at the heart of the
organization and which the (pseudo-)consensus process doesn't get to
touch.

> The IETF Mission
> ----------------
> 
> The IETF's mission has historically been embedded in a shared
> understanding that making engineering choices based on the long
> term interest of the Internet as a whole produces better long-term
> results for each participant than making choices based on short term
> considerations, because the value of those advantages is ultimately
> derived from the health of the whole.  The long term interest of the
> Internet includes the premise that "the Internet is for everyone".
> 
> Two years ago, the IESG felt that making the mission of the IETF
> more explicit was needed.  The following terse statement has since
> been promulgated, first by IESG members and then by others:
> 
>    "The purpose of the IETF is to create high quality, relevant,
>     and timely standards for the Internet."

The purpose of the IETF has always been to make the Internet work
better, in measurable operational terms.  All else descends from that.
We do standards because we have to, for now and for the future.  Why do
we care about network operators being in the room if our prime mission
is to make standards?  Why do we care if there are two interoperable
implementations?  The operations work of the IETF is important unless it
is being taken care of elsewhere.  It isn't frosting on a standards body
cake, it's just as important as standards.  

Beyond that, yes, the IETF is primarily an SDO, because many operational
issues and agreement on deployment BCPs are being taken care of by other
means, and also because standards is our main measurable output in the
eyes of the outside world.  The above statement applies, but it is not a
basic principle.  It derives from our fundamental responsibility, to
have an Internet that works well today and is robust and flexible enough
to work well in the future.

> It is important that this is "For the Internet,"  and does not include 
> everything that happens to use IP.  IP is being used in a myriad of 
> real-world applications, such as controlling street lights, but the 
> IETF does not standardize those applications.

A very poor distinction.  Everything runs on the Internet eventually,
regardless of what private area it was meant for to start with.
Experience is that everyone wins if there are Internet-compatible ways
of doing things from the beginning.  I fully expect street light control
to run as a secure service along with many other services over a generic
IP network.  However, it's okay to say that priority will be given to
work on the public Internet.

> The IETF has also had a strong operational component, with a tight
> bond, and hence coordination, between protocol developers and
> network operators, and has had many participants who did both.
> This has provided valuable feedback to allow correction of
> misguided standardization efforts, and has provided feedback to
> sort out which standards were actually needed.  As the field has
> grown explosively, specialization has set in, and market pressures
> have risen, there has been less and less operator participation in
> the IETF.

This has nothing to do with either mission or social contract.  Are you
saying "therefore we need to change our mission"?

Similarly for almost all of the rest.  What's the point?  Are you
reiterating the problem-statement work?  They're doing all right,
although perhaps you could help push the work to completion.  It would
be much more useful for you to reaffirm the fundamental principles that
are not on the auction block.

Have a good time at the meeting, I won't make it this time.

See you ... Scott





From owner-ietf@ietf.org  Wed Oct 15 13:04:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09519
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 13:04:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9oup-0007s6-8b
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 12:54:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9ouB-0007pB-Tv
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 12:53:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08937
	for <ietf@ietf.org>; Wed, 15 Oct 2003 12:53:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ouA-0007MY-00
	for ietf@ietf.org; Wed, 15 Oct 2003 12:53:46 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ouA-0007MV-00
	for ietf@ietf.org; Wed, 15 Oct 2003 12:53:46 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id DBCC21409F; Wed, 15 Oct 2003 12:53:45 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 08711-05; Wed, 15 Oct 2003 12:53:44 -0400 (EDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 4C2B71410F; Wed, 15 Oct 2003 12:53:44 -0400 (EDT)
Date: Wed, 15 Oct 2003 12:48:37 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: moore@cs.utk.edu, ietf@ietf.org, problem-statement@alvestrand.no
Subject: Re: IESG proposed statement on the IETF mission
Message-Id: <20031015124837.79dbcd11.moore@cs.utk.edu>
In-Reply-To: <157547561.1066175290@localhost>
References: <157547561.1066175290@localhost>
X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

overall, I like the document.  some comments:


> However, while Dave Clark's famous saying
> 
>   "We do not believe in kings, presidents, or voting.
>    We believe only in rough consensus and running code,"

is this an accurate quote?  I've usually seen it written

	We reject kings, presidents, and voting. 
	We believe in rough consensus and running code.

I agree with this form, but not with the way you've stated it.
I certainly don't believe "only" in rough consensus and running code -
I also believe in explicit definition of goals and requirements,
careful design by knowledgable experts, analysis, iterative
specification, wide public review, etc.

>    "The purpose of the IETF is to create high quality, relevant,
>     and timely standards for the Internet."

I actually believe IETF has a somewhat wider purpose than that.  What
I usually say is "we're trying to help the Internet work better".
We do this partially by authoring and maintaining protocol standards, 
but we use other mechanisms also.  In addition to standards, we produce 
informational and experimental documents and BCPs.   We provide formal 
and informal advice and feedback to various parties about operational
practices,  implementation practices, efforts by other SDOs, proposed
regulations, etc.  All of these are relevant to, and consistent with,
the purpose of helping the Internet to work better.

We *ought* to provide more architectural direction or advice - our
failure to resolve architectural issues in advance of deployment of
products with conflicting views of the architecture (or in some 
cases, a simple lack of care or foresight on those vendors' parts) has
caused a number of conflicts and operational problems, and has impaired
the ability of the Internet to support diverse applications.

I also believe that some amount of experimentation (perhaps not all
that is being done under IETF's purview) is part of the process of
"trying to make the Internet work better"

> The IETF
> has identified interoperability, security, and scalability as
> essential, but without attaching measurements to those
> characteristics.

that's a start.  there are a lot more characteristics than these that
should be considered in a design, that we haven't articulated yet,
but we need to.

> It is important that this is "For the Internet,"  and does not include
> everything that happens to use IP.  IP is being used in a myriad of 
> real-world applications, such as controlling street lights, but the 
> IETF does not standardize those applications.

I disagree with the sentiment as I understand it.  I don't think it's
realistic anymore to take the view that what people run entirely on 
private networks is their own business and outside of IETF's purview. 
NATs, private addresses, and DHCP with short lease times have all had
devistating effects on the Internet's ability to support applications. 
Insecure applications can facilitate the breeding of viruses that affect
the entire network even if their intended interactions are only between
a local client and server.

We do have to limit our scope.  We don't have the ability to scale to
the point where we could standardize everything that uses IP, and it
would be silly of us to try to claim authority to do so.  But it might
be reasonable for us to define standards for how local networks work
(to provide applications with a predictable environment), or to define
standards which all applications should adhere to (to minimize security
issues) which can be incorporated by reference into other protocol
specifications.

regarding the section on "Quality and Architectural Review".  what strikes
me about this section is the (implicit) assumption that architecture is
done after the fact.  rather than looking ahead to minimize and resolve
conflicts well before they acquire the inertia of wide deployment, we 
try to fix things after the fact.






From owner-ietf@ietf.org  Wed Oct 15 13:05:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09674
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 13:05:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9ozo-0007zs-9T
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 12:59:36 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9owG-0007uA-Co
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 12:55:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09075;
	Wed, 15 Oct 2003 12:55:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9owF-0007PB-00; Wed, 15 Oct 2003 12:55:55 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9owE-0007OT-00; Wed, 15 Oct 2003 12:55:54 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h9FGtHk23013;
	Wed, 15 Oct 2003 09:55:17 -0700
X-mProtect: <200310151655> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.9.199, claiming to be "spruce.iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdSWFExf; Wed, 15 Oct 2003 09:55:16 PDT
Message-Id: <4.3.2.7.2.20031015094435.02488eb8@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 15 Oct 2003 09:52:18 -0700
To: itojun@iijlab.net
From: Bob Hinden <hinden@iprg.nokia.com>
Subject: Re: draft-ietf-vrrp-ipv6-spec-05.txt lacks IPR clause
Cc: hinden@iprg.nokia.com, Radia Perlman <radia.perlman@sun.com>,
        Mukesh Gupta <Mukesh.Gupta@nokia.com>, vrrp@ietf.org, ietf@ietf.org
In-Reply-To: <20031015014322.308B890@coconut.itojun.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

Itojun,

At 06:43 PM 10/14/2003, itojun@iijlab.net wrote:
>         draft-ietf-vrrp-ipv6-spec-05.txt does not have IPR clause on it,
>         even though cisco claims to have patent related to it.
>         http://www.ietf.org/ietf/IPR/cisco-ipr-draft-ietf-vrrp-ipv6-spec.txt

I wasn't aware of this claim on VRRP for IPv6 when the current draft was 
submitted.  I will add an IPR clause in the next version.

Thanks,
Bob




From owner-ietf@ietf.org  Wed Oct 15 13:06:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09782
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 13:06:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9p0t-00082G-JD
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 13:00:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9oy3-0007wY-Um
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 12:57:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09146
	for <ietf@ietf.org>; Wed, 15 Oct 2003 12:57:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oy2-0007RD-00
	for ietf@ietf.org; Wed, 15 Oct 2003 12:57:46 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oy2-0007Qw-00
	for ietf@ietf.org; Wed, 15 Oct 2003 12:57:46 -0400
Received: from cisco.com (64.102.124.13)
  by sj-iport-5.cisco.com with ESMTP; 15 Oct 2003 09:57:39 -0700
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h9FGvBlb000917;
	Wed, 15 Oct 2003 12:57:12 -0400 (EDT)
Message-Id: <200310151657.h9FGvBlb000917@rtp-core-2.cisco.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org, problem-statement@alvestrand.no
Subject: Re: IESG proposed statement on the IETF mission 
In-reply-to: Your message of Tue, 14 Oct 2003 23:48:10 +0200.
             <157547561.1066175290@localhost> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 15 Oct 2003 12:57:11 -0400
From: Eric Rosen <erosen@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


> "The purpose of  the IETF is to create high  quality, relevant, and timely
> standards for the Internet." 

> It is important that this is "For the Internet," and does not include 
> everything that happens to use IP.  IP is being used in a myriad of 
> real-world applications, such as controlling street lights, but the 
> IETF does not standardize those applications. 

Well, let's test this assertion.  Suppose a consortium of electric companies
develops a UDP-based protocol  for monitoring and controlling street lights.
It turns  out that  this protocol generates  an unbounded amount  of traffic
(say,  proportional to  the square  of the  number of  street lights  in the
world), has no  congestion control, and no security, but  is expected to run
over the Internet. 

According to you, this has nothing to  do with the IETF.  It might result in
the congestive collapse of the Internet,  but who cares, the IETF doesn't do
street  lights.  I would  like  to see  the  criteria  which determine  that
telephones belong on the Internet but street lights don't!

Another problem  with your  formulation is that  the Internet is  a growing,
changing, entity,  so "for the Internet"  often means "for what  I think the
Internet  should  be  in  a  few  years", and  this  is  then  a  completely
unobjective criterion.  One  would hope instead that the  IETF would want to
encourage competition between different  views of Internet evolution, as the
competition of ideas is the way to make progress. 

I also do not understand whether "for the Internet" means something different
than "for IP networking" or not.  

I think  it should  also be part  of the  mission to produce  standards that
facilitate the migration to IP  of applications and infrastructures that use
legacy networking  technologies.  Such  migration seems to  be good  for the
Internet, but I don't know if it is "for the Internet" or not. 




From owner-ietf@ietf.org  Wed Oct 15 13:08:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10211
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 13:08:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9p5U-0008M9-E5
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 13:05:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9p3X-0008B3-8k
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 13:03:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09426
	for <ietf@ietf.org>; Wed, 15 Oct 2003 13:03:18 -0400 (EDT)
From: Margaret.Wasserman@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9p3W-0007Vz-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:03:26 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9p3V-0007Vw-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:03:25 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9FH3OX14459
	for <ietf@ietf.org>; Wed, 15 Oct 2003 20:03:24 +0300 (EET DST)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T654dc1358cac158f23076@esvir03nok.nokia.com>;
 Wed, 15 Oct 2003 20:03:24 +0300
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 15 Oct 2003 10:02:50 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: IESG proposed statement on the IETF mission
Date: Wed, 15 Oct 2003 13:01:53 -0400
Message-ID: <E320A8529CF07E4C967ECC2F380B0CF902332FCC@bsebe001.americas.nokia.com>
Thread-Topic: IESG proposed statement on the IETF mission
Thread-Index: AcOTNkIQ3jR8xoGcQk6oVsjGtGIIFgAB6bXQ
To: <swb@employees.org>, <harald@alvestrand.no>
Cc: <problem-statement@alvestrand.no>, <ietf@ietf.org>
X-OriginalArrivalTime: 15 Oct 2003 17:02:50.0899 (UTC) FILETIME=[2AA18630:01C3933E]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


Hi Scott,

> Similarly for almost all of the rest.  What's the point?  Are you
> reiterating the problem-statement work?  They're doing all right,
> although perhaps you could help push the work to completion.  It would
> be much more useful for you to reaffirm the fundamental=20
> principles that are not on the auction block.

From your perspective, what are those fundamental principles?

Margaret




From owner-ietf@ietf.org  Wed Oct 15 13:11:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10553
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 13:11:32 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9p5U-0008MI-Pd
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 13:05:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9p3d-0008B5-7c
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 13:03:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09431
	for <ietf@ietf.org>; Wed, 15 Oct 2003 13:03:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9p3c-0007W7-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:03:32 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9p3b-0007W4-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:03:31 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id CF82313FAF; Wed, 15 Oct 2003 13:03:31 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 09603-11; Wed, 15 Oct 2003 13:03:30 -0400 (EDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 82DCF1409F; Wed, 15 Oct 2003 13:03:30 -0400 (EDT)
Date: Wed, 15 Oct 2003 12:58:24 -0400
From: Keith Moore <moore@cs.utk.edu>
To: erosen@cisco.com
Cc: moore@cs.utk.edu, harald@alvestrand.no, problem-statement@alvestrand.no,
        ietf@ietf.org
Subject: Re: IESG proposed statement on the IETF mission
Message-Id: <20031015125824.3c865835.moore@cs.utk.edu>
In-Reply-To: <200310151657.h9FGvBlb000917@rtp-core-2.cisco.com>
References: <157547561.1066175290@localhost>
	<200310151657.h9FGvBlb000917@rtp-core-2.cisco.com>
X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> One  would hope instead that the  IETF would want to
> encourage competition between different  views of Internet evolution, as the
> competition of ideas is the way to make progress. 

what I would say instead is that the IETF should encourage this competition 
within the sphere of architectural discussion - well in advance of development
of specific standards or deployment of specific products.



From owner-ietf@ietf.org  Wed Oct 15 13:22:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11267
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 13:22:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9pI4-0002FP-FP
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 13:18:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9pH9-0002A1-RM
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 13:17:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11039
	for <ietf@ietf.org>; Wed, 15 Oct 2003 13:17:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9pH8-0000FR-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:17:30 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9pH8-0000Ee-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:17:30 -0400
Received: from employees.org (171.68.223.138)
  by sj-iport-5.cisco.com with ESMTP; 15 Oct 2003 10:17:24 -0700
Received: from cisco.com (sjc-vpn3-678.cisco.com [10.21.66.166])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with SMTP id h9FHGtH7010500;
	Wed, 15 Oct 2003 10:16:56 -0700 (PDT)
Received: by cisco.com (sSMTP sendmail emulation); Wed, 15 Oct 2003 13:16:52 -0400
Date: Wed, 15 Oct 2003 13:16:52 -0400
From: Scott W Brim <swb@employees.org>
To: Margaret.Wasserman@nokia.com
Cc: harald@alvestrand.no, problem-statement@alvestrand.no, ietf@ietf.org
Subject: Re: IESG proposed statement on the IETF mission
Message-ID: <20031015131652.P2320@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <swb@employees.org>,
	Margaret.Wasserman@nokia.com, harald@alvestrand.no,
	problem-statement@alvestrand.no, ietf@ietf.org
References: <E320A8529CF07E4C967ECC2F380B0CF902332FCC@bsebe001.americas.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <E320A8529CF07E4C967ECC2F380B0CF902332FCC@bsebe001.americas.nokia.com>; from Margaret.Wasserman@nokia.com on Wed, Oct 15, 2003 at 01:01:53PM -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Oct 15, 2003 01:01:53PM -0400, Margaret.Wasserman@nokia.com allegedly wrote:
> 
> Hi Scott,
> 
> > Similarly for almost all of the rest.  What's the point?  Are you
> > reiterating the problem-statement work?  They're doing all right,
> > although perhaps you could help push the work to completion.  It would
> > be much more useful for you to reaffirm the fundamental 
> > principles that are not on the auction block.
> 
> >From your perspective, what are those fundamental principles?

I can't do that today, but will reply soon.



From owner-ietf@ietf.org  Wed Oct 15 13:24:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11538
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 13:24:33 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9pKx-0002Mo-Bg
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 13:21:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9pKk-0002Kc-Tr
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 13:21:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11206
	for <ietf@ietf.org>; Wed, 15 Oct 2003 13:21:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9pKj-0000Hp-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:21:13 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9pKj-0000Hh-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:21:13 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1A9pKd-000PIE-00; Wed, 15 Oct 2003 12:21:07 -0500
Date: Wed, 15 Oct 2003 13:21:07 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@cs.utk.edu>
cc: ietf@ietf.org
Subject: Re: Removing features
Message-ID: <9957878.1066224067@scan.jck.com>
In-Reply-To: <20031015115824.403e88ab.moore@cs.utk.edu>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C642@server2003.arn
 eill-py.sacramento.ca.us>
 <20031015115824.403e88ab.moore@cs.utk.edu>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Wednesday, 15 October, 2003 11:58 -0400 Keith Moore 
<moore@cs.utk.edu> wrote:

>> > Keith Moore wrote:
>> > great.  now we'll have NAT boxes intercepting
>> > outgoing DNS traffic also.
>>
>> That was not my point. My point was to have a DNS server in
>> the inside configured for reverse lookup of private IPs.
>
> one of the most-frequently cited justifications for NAT is
> plug-and-play. expecting people to set up their own DNS
> servers sort of nullifies that.

Keith, two observations...

(1) Yes, I think, and think we are in agreement, that this sort 
of thing digs the NAT hole even deeper.

(2) But the typical plug-and-play NAT, at least the ones I have 
run across, is preconfigured with the addresses to be used on 
the "inside" and contains (or is intimately paired with) a DHCP 
server that gives out those addresses.  Installing a DNS filter 
in the thing that would intercept PTR queries for that address 
range, or any 1918 address range, and respond to them in some 
"canned" way while passing other DNS queries out to the network 
as intended is not rocket science and certainly doesn't violate 
any plug-and-play arguments.

Now, whether that interception and diversion of DNS queries is a 
moral activity is a different question.    But, if you believe 
strongly enough that having a NAT in the first place puts one 
into a serious state of sin, then the marginal sin of 
intercepting DNS queries for private addresses, to prevent the 
sort of problems those queries cause, seems to me to be fairly 
small.

"where are we going and what are we doing in this handbasket?"

   john




From owner-ietf@ietf.org  Wed Oct 15 13:38:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12289
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 13:38:54 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9pRl-0003no-Ny
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 13:28:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9pPA-0003GO-V3
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 13:25:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11664
	for <ietf@ietf.org>; Wed, 15 Oct 2003 13:25:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9pP9-0000RS-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:25:47 -0400
Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9pP8-0000RK-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:25:47 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h9FA3Sw22961;
	Wed, 15 Oct 2003 12:03:28 +0200
Message-ID: <3F8D1B70.7090501@it.su.se>
Date: Wed, 15 Oct 2003 12:03:28 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Michel Py <michel@arneill-py.sacramento.ca.us>
CC: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>, John C Klensin <john@jck.com>,
        Iljitsch van Beijnum <iljitsch@muada.com>, ietf@ietf.org
Subject: rfc1918 impact
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C640@server2003.arneill-py.sacramento.ca.us>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C640@server2003.arneill-py.sacramento.ca.us>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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


We should keep nice and descriptive subject-lines...

Michel Py wrote:

<snip>

| etc. Basically everything that triggers a reverse lookup adds to the
| pain, but if reverse lookup is configured correctly on the local DNS

A lot of the arguments seem to contain the phrase "If <foo> is
configured correctly then ...". Now what does that teach us?

	Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/jRtv8Jx8FtbMZncRAg8eAJsEhg6/LOQgaZW3FtSkdiffbp2TvwCgx+x1
dpuw7nwHC2Z8BlAx+qoKyBc=
=7TZn
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Wed Oct 15 14:08:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13518
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 14:08:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9prr-0000Hy-G7
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 13:55:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9pn7-00008D-2x
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 13:50:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12799
	for <ietf@ietf.org>; Wed, 15 Oct 2003 13:50:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9pn5-0000qT-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:50:32 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9pn5-0000qQ-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:50:31 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 4695D14233; Wed, 15 Oct 2003 13:50:31 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 17219-02; Wed, 15 Oct 2003 13:50:30 -0400 (EDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 4D72D141CC; Wed, 15 Oct 2003 13:50:30 -0400 (EDT)
Date: Wed, 15 Oct 2003 13:45:23 -0400
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <john-ietf@jck.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Removing features
Message-Id: <20031015134523.2b53dcb8.moore@cs.utk.edu>
In-Reply-To: <9957878.1066224067@scan.jck.com>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C642@server2003.arn
 eill-py.sacramento.ca.us>
	<20031015115824.403e88ab.moore@cs.utk.edu>
	<9957878.1066224067@scan.jck.com>
X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Now, whether that interception and diversion of DNS queries is a 
> moral activity is a different question.    But, if you believe 
> strongly enough that having a NAT in the first place puts one 
> into a serious state of sin, then the marginal sin of 
> intercepting DNS queries for private addresses, to prevent the 
> sort of problems those queries cause, seems to me to be fairly 
> small.

I probably agree.  But I guess my question is "where does it end?"

That is, how many things do we change elsewhere in the network in order
to minimize the operational problems that crop up with NATs?  What is
the cost of those changes, and how much do they impair the ability of
the network to support applications?




From owner-ietf@ietf.org  Wed Oct 15 14:11:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11264
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 13:22:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9pHC-0002Bz-La
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 13:17:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9pFw-00027V-CI
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 13:16:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10948
	for <ietf@ietf.org>; Wed, 15 Oct 2003 13:16:07 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9pFv-0000EE-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:16:15 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9pFu-0000EA-00
	for ietf@ietf.org; Wed, 15 Oct 2003 13:16:14 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9FHG95H009885;
	Wed, 15 Oct 2003 13:16:09 -0400
Message-Id: <200310151716.h9FHG95H009885@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org
Subject: Re: IESG proposed statement on the IETF mission 
In-Reply-To: Your message of "Wed, 15 Oct 2003 12:48:37 EDT."
             <20031015124837.79dbcd11.moore@cs.utk.edu> 
References: <157547561.1066175290@localhost>
            <20031015124837.79dbcd11.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1597395223P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 15 Oct 2003 13:16:09 -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1597395223P
Content-Type: text/plain; charset=us-ascii

On Wed, 15 Oct 2003 12:48:37 EDT, Keith Moore said:
>
> I certainly don't believe "only" in rough consensus and running code -
> I also believe in explicit definition of goals and requirements,
> careful design by knowledgable experts, analysis, iterative
> specification, wide public review, etc.

Of course, proper design and development techniques increase the likelyhood of
running code - and "proof by example running code" is always a good way to
achieve a consensus. 


--==_Exmh_-1597395223P
Content-Type: application/pgp-signature

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

iD8DBQE/jYDZcC3lWbTT17ARAvJHAKC2aaIR2IzwlbsB6HkmfIhyBYh+2ACeJMru
0+fy2UoOftf/Ep5P98E09eM=
=w4v/
-----END PGP SIGNATURE-----

--==_Exmh_-1597395223P--



From owner-ietf@ietf.org  Wed Oct 15 14:15:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13952
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 14:15:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9q6P-00015I-Kx
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 14:10:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9q62-0000zb-Nb
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 14:10:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13659
	for <ietf@ietf.org>; Wed, 15 Oct 2003 14:09:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9q61-000163-00
	for ietf@ietf.org; Wed, 15 Oct 2003 14:10:05 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9q60-00015y-00
	for ietf@ietf.org; Wed, 15 Oct 2003 14:10:05 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1A9q60-000Pep-00; Wed, 15 Oct 2003 13:10:04 -0500
Date: Wed, 15 Oct 2003 14:10:04 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@cs.utk.edu>
cc: ietf@ietf.org
Subject: Re: Removing features
Message-ID: <12894751.1066227004@scan.jck.com>
In-Reply-To: <20031015134523.2b53dcb8.moore@cs.utk.edu>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C642@server2003.arn
  eill-py.sacramento.ca.us>
 	<20031015115824.403e88ab.moore@cs.utk.edu>
 	<9957878.1066224067@scan.jck.com>
 <20031015134523.2b53dcb8.moore@cs.utk.edu>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Wednesday, 15 October, 2003 13:45 -0400 Keith Moore 
<moore@cs.utk.edu> wrote:

>> Now, whether that interception and diversion of DNS queries
>> is a  moral activity is a different question.    But, if you
>> believe  strongly enough that having a NAT in the first place
>> puts one  into a serious state of sin, then the marginal sin
>> of  intercepting DNS queries for private addresses, to
>> prevent the  sort of problems those queries cause, seems to
>> me to be fairly  small.
>
> I probably agree.  But I guess my question is "where does it
> end?"
>
> That is, how many things do we change elsewhere in the network
> in order to minimize the operational problems that crop up
> with NATs?  What is the cost of those changes, and how much do
> they impair the ability of the network to support applications?

That, it seems to me, is a pragmatic way to state the key 
architectural question.  A different version of it, borrowed 
from a different debate, is how much a particular new capability 
is permitted to force deployed systems or applications code to 
change the way they are doing things in the interest of the 
innovation contained in that new capability.

     john







From owner-ietf@ietf.org  Wed Oct 15 14:19:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14167
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 14:19:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9q8K-0001Lg-UZ
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 14:12:28 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9q7w-0001GB-1K
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 14:12:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13822
	for <ietf@ietf.org>; Wed, 15 Oct 2003 14:11:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9q7u-00018q-00
	for ietf@ietf.org; Wed, 15 Oct 2003 14:12:02 -0400
Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9q7t-00018n-00
	for ietf@ietf.org; Wed, 15 Oct 2003 14:12:02 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h9FKAYw24963;
	Wed, 15 Oct 2003 22:10:34 +0200
Message-ID: <3F8DA9B9.5020804@it.su.se>
Date: Wed, 15 Oct 2003 22:10:33 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
CC: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: rfc1918 impact
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C642@server2003.arn eill-py.sacramento.ca.us> <20031015115824.403e88ab.moore@cs.utk.edu> <9957878.1066224067@scan.jck.com>
In-Reply-To: <9957878.1066224067@scan.jck.com>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

<snip>

|
| (2) But the typical plug-and-play NAT, at least the ones I have run
| across, is preconfigured with the addresses to be used on the "inside"
| and contains (or is intimately paired with) a DHCP server that gives out
| those addresses.  Installing a DNS filter in the thing that would
| intercept PTR queries for that address range, or any 1918 address range,
| and respond to them in some "canned" way while passing other DNS queries
| out to the network as intended is not rocket science and certainly
| doesn't violate any plug-and-play arguments.

So where is the the leak coming from? If what people claim is true and
if not all, but most NAT-boxes are configured with inside DNS, filtering
and extra cheese, where, I ask you do all of those root-zone requests
and other rfc1918 leaks come from?

	Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/jam58Jx8FtbMZncRAu9rAJ9V/vdGmY0UHYRs25IOf333NlSZDwCgohWV
LukIl7zvBBohV0dtG9hVUHs=
=/YAT
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Wed Oct 15 14:23:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14484
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 14:23:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9qF7-000221-0o
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 14:19:29 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9qEx-0001xW-9g
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 14:19:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14163
	for <ietf@ietf.org>; Wed, 15 Oct 2003 14:19:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9qEw-0001Ga-00
	for ietf@ietf.org; Wed, 15 Oct 2003 14:19:18 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9qEv-0001GX-00
	for ietf@ietf.org; Wed, 15 Oct 2003 14:19:17 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1A9qEu-000PmO-00; Wed, 15 Oct 2003 13:19:16 -0500
Date: Wed, 15 Oct 2003 14:19:16 -0400
From: John C Klensin <john-ietf@jck.com>
To: Leif Johansson <leifj@it.su.se>
cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: rfc1918 impact
Message-ID: <13446164.1066227556@scan.jck.com>
In-Reply-To: <3F8DA9B9.5020804@it.su.se>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C642@server2003.arn
  eill-py.sacramento.ca.us>
 <20031015115824.403e88ab.moore@cs.utk.edu>
 <9957878.1066224067@scan.jck.com> <3F8DA9B9.5020804@it.su.se>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Wednesday, 15 October, 2003 22:10 +0200 Leif Johansson 
<leifj@it.su.se> wrote:

>| (2) But the typical plug-and-play NAT, at least the ones I
>| have run across, is preconfigured with the addresses to be
>| used on the "inside" and contains (or is intimately paired
>| with) a DHCP server that gives out those addresses.
>| Installing a DNS filter in the thing that would intercept PTR
>| queries for that address range, or any 1918 address range,
>| and respond to them in some "canned" way while passing other
>| DNS queries out to the network as intended is not rocket
>| science and certainly doesn't violate any plug-and-play
>| arguments.
>
> So where is the the leak coming from? If what people claim is
> true and
> if not all, but most NAT-boxes are configured with inside DNS,
> filtering
> and extra cheese, where, I ask you do all of those root-zone
> requests
> and other rfc1918 leaks come from?

Leif,

I was speaking to the architectural issue, not the deployment 
one.  None of the three plug and play boxes I have here with NAT 
capability has any inside DNS capability (either enabled by 
default or available to be turned on).

It does sound like a recommendation to the effect of "if you are 
going to use NAT, or construct a NAT box, then an 'inside DNS' 
mechanism" would be a reasonable idea.  And I would assume it 
would be an even better one if it made clear what the preferred 
way was to do an "inside DNS" -- I think there might be a couple 
of different ways to do it, and some might be less reprehensible 
than the others.

    john




From owner-ietf@ietf.org  Wed Oct 15 15:24:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17486
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 15:24:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9r6Z-0002z3-5S
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 15:14:43 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9r0X-0001NA-EN
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 15:08:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16240
	for <ietf@ietf.org>; Wed, 15 Oct 2003 15:08:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9r0W-0001oz-00
	for ietf@ietf.org; Wed, 15 Oct 2003 15:08:28 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9r0V-0001ow-00
	for ietf@ietf.org; Wed, 15 Oct 2003 15:08:27 -0400
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h9FJ8Ned089490;
	Wed, 15 Oct 2003 21:08:23 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20031015134523.2b53dcb8.moore@cs.utk.edu>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C642@server2003.arn eill-py.sacramento.ca.us> <20031015115824.403e88ab.moore@cs.utk.edu> <9957878.1066224067@scan.jck.com> <20031015134523.2b53dcb8.moore@cs.utk.edu>
Mime-Version: 1.0 (Apple Message framework v604)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F351C6E7-FF42-11D7-9D65-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Removing features
Date: Wed, 15 Oct 2003 21:08:24 +0200
To: Keith Moore <moore@cs.utk.edu>
X-Mailer: Apple Mail (2.604)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 15 okt 2003, at 19:45, Keith Moore wrote:

>> the marginal sin of
>> intercepting DNS queries for private addresses, to prevent the
>> sort of problems those queries cause, seems to me to be fairly
>> small.

> I probably agree.  But I guess my question is "where does it end?"

It ends when IPv4 ends. That is, if we can keep NAT out of IPv6.

> That is, how many things do we change elsewhere in the network in order
> to minimize the operational problems that crop up with NATs?  What is
> the cost of those changes, and how much do they impair the ability of
> the network to support applications?

There is no answer for these questions. Everyone can unilaterally 
decide to run stuff like NATs. That's actually a strength of our 
archictecture. Also, anyone can unilaterally decide to send traffic. 
That's a big issue with our architecture. Fixing the latter (so, 
amongst other things, root nameservers aren't forced to receive traffic 
from RFC 1918 sources) without getting in the way of the former isn't 
going to be easy.




From owner-ietf@ietf.org  Wed Oct 15 15:24:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17483
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 15:24:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9r6t-00033F-CJ
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 15:15:03 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9r3O-0002IX-7U
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 15:11:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16540
	for <ietf@ietf.org>; Wed, 15 Oct 2003 15:11:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9r3M-0001qp-00
	for ietf@ietf.org; Wed, 15 Oct 2003 15:11:24 -0400
Received: from as13-3-2.rny.s.bonet.se ([217.215.166.49] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9r3L-0001qm-00
	for ietf@ietf.org; Wed, 15 Oct 2003 15:11:24 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id h9FL9uw25065;
	Wed, 15 Oct 2003 23:09:56 +0200
Message-ID: <3F8DB7A4.4010108@it.su.se>
Date: Wed, 15 Oct 2003 23:09:56 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
CC: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: rfc1918 impact
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C642@server2003.arn  eill-py.sacramento.ca.us> <20031015115824.403e88ab.moore@cs.utk.edu> <9957878.1066224067@scan.jck.com> <3F8DA9B9.5020804@it.su.se> <13446164.1066227556@scan.jck.com>
In-Reply-To: <13446164.1066227556@scan.jck.com>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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


<snip>

|
| Leif,
|
| I was speaking to the architectural issue, not the deployment one.  None
| of the three plug and play boxes I have here with NAT capability has any
| inside DNS capability (either enabled by default or available to be
| turned on).

Exactly! Now why is that?

| It does sound like a recommendation to the effect of "if you are going
| to use NAT, or construct a NAT box, then an 'inside DNS' mechanism"
| would be a reasonable idea.  And I would assume it would be an even
| better one if it made clear what the preferred way was to do an "inside
| DNS" -- I think there might be a couple of different ways to do it, and
| some might be less reprehensible than the others.
|

Of course (I am beeing intentionally obtuse) but isn't it quite unlikely
that any recommendation the we make at this point will have any impact
on how v4 NAT is deployed - we are after all talking about kazillions of
adsl modems, SOHO-routers etc etc? Do you believe that things will be
different with v6 NAT, I.e what are the interoperability problems a NAT
vendor will have unless they implement NAT 'correctly'?

	Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/jbek8Jx8FtbMZncRArnHAKCYL6ofsHt7AQHefjm7wx1XpD1dWwCgiMtZ
6HnYUNLxyduWc0MLHSB/OGw=
=wMD6
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Wed Oct 15 16:57:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23276
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 16:57:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9sai-0002vP-TI
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 16:49:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9sSj-0002bG-Nq
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 16:41:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22730
	for <ietf@ietf.org>; Wed, 15 Oct 2003 16:41:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9sSi-0003UH-00
	for ietf@ietf.org; Wed, 15 Oct 2003 16:41:40 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9sSh-0003UB-00
	for ietf@ietf.org; Wed, 15 Oct 2003 16:41:39 -0400
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h9FKfbed090590;
	Wed, 15 Oct 2003 22:41:38 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <3F8DB7A4.4010108@it.su.se>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C642@server2003.arn  eill-py.sacramento.ca.us> <20031015115824.403e88ab.moore@cs.utk.edu> <9957878.1066224067@scan.jck.com> <3F8DA9B9.5020804@it.su.se> <13446164.1066227556@scan.jck.com> <3F8DB7A4.4010108@it.su.se>
Mime-Version: 1.0 (Apple Message framework v604)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F9CA7E36-FF4F-11D7-9D65-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: rfc1918 impact
Date: Wed, 15 Oct 2003 22:41:38 +0200
To: Leif Johansson <leifj@it.su.se>
X-Mailer: Apple Mail (2.604)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 15 okt 2003, at 23:09, Leif Johansson wrote:

> Of course (I am beeing intentionally obtuse) but isn't it quite 
> unlikely
> that any recommendation the we make at this point will have any impact

RFC 2827 provides exactly these recommendations. Unfortunately many 
operators still can't be bothered or use prehistoric equipment that 
can't handle the filtering.




From owner-ietf@ietf.org  Wed Oct 15 17:32:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24713
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 17:32:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9t95-0005Dg-Ct
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 17:25:27 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9t8t-00059S-8C
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 17:25:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24463
	for <ietf@ietf.org>; Wed, 15 Oct 2003 17:25:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9t8r-00043B-00
	for ietf@ietf.org; Wed, 15 Oct 2003 17:25:13 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9t8r-000437-00
	for ietf@ietf.org; Wed, 15 Oct 2003 17:25:13 -0400
Subject: RE: rfc1918 impact
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 15 Oct 2003 14:24:37 -0700
Content-class: urn:content-classes:message
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C64C@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: rfc1918 impact
thread-index: AcOTXxw+jnOjorwCS3GQfamiLhwK6gAAaVzg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>,
        "Leif Johansson" <leifj@it.su.se>
Cc: <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Leif / Iljitsch,


>>> It does sound like a recommendation to the effect of "if you are
going=20
>>> to use NAT, or construct a NAT box, then an 'inside DNS' mechanism"
>>> would be a reasonable idea.  And I would assume it would be an even=20
>>> better one if it made clear what the preferred way was to do an=20
>>> "inside DNS" -- I think there might be a couple of different ways to

>>> do it, and some might be less reprehensible than the others.

>> Leif Johansson wrote:
>> Of course (I am beeing intentionally obtuse) but isn't it
>> quite unlikely that any recommendation the we make at this
>> point will have any impact

Keith will not like it, but NAT vendors will take suggestions that will
make NAT better. In this case, having in the NAT box a DNS proxy that
forwards reverse lookups for public addresses to the ISP's DNS servers
and replies a blanket reply for RFC1918 addresses does not look to much
work. That box could also accept dynamic address registration that is
default in the latest MS products. Even if _we_ have a DNS server at
home Joe-Six-Pack does not, therefore the place for that animal is in
the NAT box indeed. You want to convince NAT box vendors to implement
it? Tell them that if they do, Keith will stop beating the crap out of
them :-)

> Iljitsch van Beijnum wrote:
> RFC 2827 provides exactly these recommendations.

Does it? We are not talking about blocking RFC1918 traffic here; what we
are talking is blocking traffic where both SA(after NAT) and DA are
public that contains a DNS request for a PRT like 8191CFR.in-addr.arpa,
which requires to decapsulate the packet to inspect its content. It's
not that simple.

Michel.




From owner-ietf@ietf.org  Wed Oct 15 18:04:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25947
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 18:04:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9tfy-000083-HQ
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 17:59:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9tbP-0008Gx-2q
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 17:54:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25563
	for <ietf@ietf.org>; Wed, 15 Oct 2003 17:54:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9tbL-0004L2-00
	for ietf@ietf.org; Wed, 15 Oct 2003 17:54:39 -0400
Received: from sequoia.muada.com ([213.156.1.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9tbL-0004Kz-00
	for ietf@ietf.org; Wed, 15 Oct 2003 17:54:39 -0400
Received: from [127.0.0.1] (sequoia.muada.com [213.156.1.123])
	by sequoia.muada.com (8.12.8p1/8.12.8) with ESMTP id h9FLk2ed091317;
	Wed, 15 Oct 2003 23:46:02 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C64C@server2003.arneill-py.sacramento.ca.us>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C64C@server2003.arneill-py.sacramento.ca.us>
Mime-Version: 1.0 (Apple Message framework v604)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F94CE900-FF58-11D7-9D65-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: rfc1918 impact
Date: Wed, 15 Oct 2003 23:46:03 +0200
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.604)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On 15 okt 2003, at 23:24, Michel Py wrote:

>> RFC 2827 provides exactly these recommendations.

[FYI: RFC 2827 is about ingress filtering to stop source address 
spoofing]

> Does it? We are not talking about blocking RFC1918 traffic here;

I was.

> what we
> are talking is blocking traffic where both SA(after NAT) and DA are
> public that contains a DNS request for a PRT like 8191CFR.in-addr.arpa,
> which requires to decapsulate the packet to inspect its content. It's
> not that simple.

I don't feel that a lookup for <something>.10.in-addr.arpa is all that 
wrong. This can be handled in many very reasonable ways, and the usual 
caching applies. Requests with unroutable sources are wrong because 
they break the protocol.

Iljitsch




From owner-ietf@ietf.org  Wed Oct 15 18:04:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25968
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 18:04:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9tZ1-0007Wm-Tp
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 17:52:15 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9tUG-0006zR-97
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 17:47:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25121
	for <ietf@ietf.org>; Wed, 15 Oct 2003 17:47:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9tUE-0004I2-00
	for ietf@ietf.org; Wed, 15 Oct 2003 17:47:18 -0400
Received: from parsley.amaranth.net ([208.254.46.23])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9tUE-0004Hy-00
	for ietf@ietf.org; Wed, 15 Oct 2003 17:47:18 -0400
Received: from Willow.senie.com (amaranth.ne.client2.attbi.com [24.34.18.226])
	(authenticated bits=0)
	by parsley.amaranth.net (8.12.8/8.12.8) with ESMTP id h9FLlAJl006547
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Wed, 15 Oct 2003 17:47:11 -0400
Message-Id: <6.0.0.22.2.20031015173745.024dbca0@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Wed, 15 Oct 2003 17:45:41 -0400
To: ietf@ietf.org
From: Daniel Senie <dts@senie.com>
Subject: RE: rfc1918 impact
Cc: <ietf@ietf.org>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C64C@server2003.arneill-
 py.sacramento.ca.us>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C64C@server2003.arneill-py.sacramento.ca.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 05:24 PM 10/15/2003, Michel Py wrote:
>Leif / Iljitsch,
>
>
> >>> It does sound like a recommendation to the effect of "if you are
>going
> >>> to use NAT, or construct a NAT box, then an 'inside DNS' mechanism"
> >>> would be a reasonable idea.  And I would assume it would be an even
> >>> better one if it made clear what the preferred way was to do an
> >>> "inside DNS" -- I think there might be a couple of different ways to
>
> >>> do it, and some might be less reprehensible than the others.
>
> >> Leif Johansson wrote:
> >> Of course (I am beeing intentionally obtuse) but isn't it
> >> quite unlikely that any recommendation the we make at this
> >> point will have any impact
>
>Keith will not like it, but NAT vendors will take suggestions that will
>make NAT better. In this case, having in the NAT box a DNS proxy that
>forwards reverse lookups for public addresses to the ISP's DNS servers
>and replies a blanket reply for RFC1918 addresses does not look to much
>work.

It also may be ill-advised, unless a switch is present for disabling it.

While we can argue ISPs should not use RFC 1918 space, there are many using 
it, including some who use it because their equipment vendors force them to 
do so (Cisco in the CMTS routing space comes to mind. Do a traceroute out 
from behind a cable modem, and the head-end router responds with a 10/8 
address. Nice job folks).

>  That box could also accept dynamic address registration that is
>default in the latest MS products.

accept, or INTERCEPT? Intercepting the traffic would be nice. After all, 
NAT boxes usually (not always, so a disabling switch would be a good idea) 
are at an administrative border (i.e. gateway to home or office). Those DNS 
updates should not be travelling beyond administrative boundaries in most 
cases.

>  Even if _we_ have a DNS server at
>home Joe-Six-Pack does not, therefore the place for that animal is in
>the NAT box indeed. You want to convince NAT box vendors to implement
>it? Tell them that if they do, Keith will stop beating the crap out of
>them :-)

Heh. Router vendors would likely be interested because it's a good thing to 
do. As for the part about Keith...


> > Iljitsch van Beijnum wrote:
> > RFC 2827 provides exactly these recommendations.
>
>Does it? We are not talking about blocking RFC1918 traffic here; what we
>are talking is blocking traffic where both SA(after NAT) and DA are
>public that contains a DNS request for a PRT like 8191CFR.in-addr.arpa,
>which requires to decapsulate the packet to inspect its content. It's
>not that simple.

Agree. RFC 2827 only discusses filtering packets whose source address is 
inappropriate for crossing a border. When NAT is used, it's rare (if the 
implementation is any good) to have a problem with bogus source addressed 
packets leaving the private network.




From owner-ietf@ietf.org  Wed Oct 15 18:49:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28594
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 18:49:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9uLa-00022K-EU
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 18:42:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9uLI-0001yC-KM
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 18:42:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28364
	for <ietf@ietf.org>; Wed, 15 Oct 2003 18:41:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9uLG-0004so-00
	for ietf@ietf.org; Wed, 15 Oct 2003 18:42:06 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9uLG-0004sl-00
	for ietf@ietf.org; Wed, 15 Oct 2003 18:42:06 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id F17E914248; Wed, 15 Oct 2003 18:42:06 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 25835-03; Wed, 15 Oct 2003 18:42:06 -0400 (EDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id CF30A14244; Wed, 15 Oct 2003 18:42:05 -0400 (EDT)
Date: Wed, 15 Oct 2003 18:36:55 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: moore@cs.utk.edu, iljitsch@muada.com, leifj@it.su.se, ietf@ietf.org
Subject: Re: rfc1918 impact
Message-Id: <20031015183655.0287e9ef.moore@cs.utk.edu>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C64C@server2003.arneill-py.sacramento.ca.us>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C64C@server2003.arneill-py.sacramento.ca.us>
X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Keith will not like it, but NAT vendors will take suggestions that
> will make NAT better.

I'd be happy for them to take suggestions from me, or IETF.  But there's
a big difference between saying "if you must do NAT, please do it this
way" and "NATs are good if they are implemented this way"
 



From owner-ietf@ietf.org  Wed Oct 15 22:02:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02920
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 22:02:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9xDc-0005kf-Qz
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 21:46:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9xCg-0005iJ-Ho
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 21:45:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02516
	for <ietf@ietf.org>; Wed, 15 Oct 2003 21:45:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9xCe-0006Qf-00
	for ietf@ietf.org; Wed, 15 Oct 2003 21:45:24 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9xCd-0006Qb-00
	for ietf@ietf.org; Wed, 15 Oct 2003 21:45:24 -0400
Subject: RE: rfc1918 impact
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 15 Oct 2003 18:44:53 -0700
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C650@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: rfc1918 impact
thread-index: AcOTaJFyKLTZ5HH5SB249TdyUJA9tgAGlf6w
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Daniel Senie" <dts@senie.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Daniel / Iljitsch,

> Daniel Senie wrote:
> [NAT box acting as a DNS server]
> It also may be ill-advised, unless a switch is present for disabling
it.

Of course.


> While we can argue ISPs should not use RFC 1918 space, there are
> many using it, including some who use it because their equipment
> vendors force them to do so (Cisco in the CMTS routing space
> comes to mind. Do a traceroute out from behind a cable modem,
> and the head-end router responds with a 10/8 address. Nice job
> folks).

Indeed. However, one should consider the trade-off between having
blanket reverse resolution for RFC1918 hops vs. flooding the roots with
bogus requests. Besides, for what I have seen these ISPs that use
RFC1918 space for links do not provide reverse lookup for them anyway
:-(


>> Michel Py wrote:
>> That box could also accept dynamic address registration that is
>> default in the latest MS products.

> Daniel Senie wrote:
> accept, or INTERCEPT? Intercepting the traffic would be nice.
> After all, NAT boxes usually (not always, so a disabling switch
> would be a good idea) are at an administrative border (i.e.
> gateway to home or office). Those DNS updates should not be
> travelling beyond administrative boundaries in most cases.

Both accept and intercept are needed.

For accept, what we are looking at is as follows: The NAT box is also
the DHCP server and gives its own address for the DNS server. Then MS
hosts register with it, making it possible not only to return something
for an RFC1918 reverse lookup and not flood the roots, but also to
return the actual host name instead of a blanket name. If using DHCP,
the MS host on the inside could try to register with a DNS server
outside: it does not know its address and registration to a broadcast
address would not be forwarded.

Intercept would be nice in the following situations:
- When Joe Blow has configured a static IP and static DNS servers that
point to the ISP's DNS servers instead of the NAT box.
- When the NAT box is not the DNS server and there is no other DNS
server.
I both cases, intercept would discard the packets of clients trying to
register with the ISP's DNS servers. This would require a comprehensive
implementation: the box should intercept dynamic DNS registration
packets and reverse lookups with an RFC1918 target, but allow other
requests.


>>> Iljitsch van Beijnum wrote:
>>> RFC 2827 provides exactly these recommendations.

>> Michel Py wrote:
>> Does it? We are not talking about blocking RFC1918 traffic here;
>> what we are talking is blocking traffic where both SA(after NAT)
>> and DA are public that contains a DNS request for a PRT like
>> 8191CFR.in-addr.arpa, which requires to decapsulate the packet=20
>> to inspect its content. It's not that simple.

> Daniel Senie wrote:
> Agree. RFC 2827 only discusses filtering packets whose source address
> is inappropriate for crossing a border. When NAT is used, it's rare
> (if the implementation is any good) to have a problem with bogus
> source addressed packets leaving the private network.

Rare indeed, because if the source address is private it is unlikely
that the reply would ever get back to the requester, and NAT
implementations that break DNS do not make it to the market.

Michel.




From owner-ietf@ietf.org  Wed Oct 15 22:33:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03818
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 22:33:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9xqK-0007kH-U7
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 22:26:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9xpO-0007hV-OR
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 22:25:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03640
	for <ietf@ietf.org>; Wed, 15 Oct 2003 22:25:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9xpL-0006sO-00
	for ietf@ietf.org; Wed, 15 Oct 2003 22:25:23 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9xpL-0006s3-00
	for ietf@ietf.org; Wed, 15 Oct 2003 22:25:23 -0400
Received: from vista.av8.net (vista.av8.net [130.105.36.10])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id WAA05190;
	Wed, 15 Oct 2003 22:18:42 -0400
Date: Wed, 15 Oct 2003 22:14:13 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: Leif Johansson <leifj@it.su.se>
cc: Michel Py <michel@arneill-py.sacramento.ca.us>,
        Kurt Erik Lindqvist <kurtis@kurtis.pp.se>,
        John C Klensin <john@jck.com>,
        Iljitsch van Beijnum <iljitsch@muada.com>, <ietf@ietf.org>
Subject: Re: rfc1918 impact
In-Reply-To: <3F8D1B70.7090501@it.su.se>
Message-ID: <Pine.LNX.4.44.0310152140360.7036-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Remember that Reverse lookups are optional. Many people who start of
saying "if reverse dns is configured correctly..." don't seem to
understand that reverse DNS is also properly configured when it is turned
off.

The abuse, and the numerous security vulnerabilities which have been
introduced by the improper use, as well as the difficulties in IPv6 (both
technical and administrative) has prompted discussion on both DNS working
groups to consider removing Reverse DNS altogether.  As it stands, Reverse
DNS is probably not going to be working or widely used in IPV6, which has
an alternate ICMP host information query so that reverse DNS is not
necessary for the most useful purpose of reverse DNS: traceroute.

The good news is that all this nonsense ends with IPv6.

		--Dean

On Wed, 15 Oct 2003, Leif Johansson wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> We should keep nice and descriptive subject-lines...
>
> Michel Py wrote:
>
> <snip>
>
> | etc. Basically everything that triggers a reverse lookup adds to the
> | pain, but if reverse lookup is configured correctly on the local DNS
>
> A lot of the arguments seem to contain the phrase "If <foo> is
> configured correctly then ...". Now what does that teach us?
>
> 	Cheers Leif
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQE/jRtv8Jx8FtbMZncRAg8eAJsEhg6/LOQgaZW3FtSkdiffbp2TvwCgx+x1
> dpuw7nwHC2Z8BlAx+qoKyBc=
> =7TZn
> -----END PGP SIGNATURE-----
>
>
>





From owner-ietf@ietf.org  Wed Oct 15 22:36:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03956
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 22:36:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9xw8-0007uy-DI
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 22:32:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9xr6-0007kJ-4z
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 22:27:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03670
	for <ietf@ietf.org>; Wed, 15 Oct 2003 22:27:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9xr4-0006tA-00
	for ietf@ietf.org; Wed, 15 Oct 2003 22:27:10 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9xr3-0006t7-00
	for ietf@ietf.org; Wed, 15 Oct 2003 22:27:09 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id C58C814198; Wed, 15 Oct 2003 22:27:10 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 19723-12; Wed, 15 Oct 2003 22:27:10 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 9C7FF13FC9; Wed, 15 Oct 2003 22:27:09 -0400 (EDT)
Date: Wed, 15 Oct 2003 22:23:30 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: moore@cs.utk.edu, dts@senie.com, ietf@ietf.org
Subject: Re: rfc1918 impact
Message-Id: <20031015222330.76183926.moore@cs.utk.edu>
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B06C650@server2003.arneill-py.sacramento.ca.us>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B06C650@server2003.arneill-py.sacramento.ca.us>
X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Intercept would be nice in the following situations:
> - When Joe Blow has configured a static IP and static DNS servers that
> point to the ISP's DNS servers instead of the NAT box.

so the next time Joe Blow is trying to figure out why a particular DNS server
isn't responding correctly by explicitly sending it queries, the NAT box
will intercept the queries, forge replies, and mask the problem.


Keith



From owner-ietf@ietf.org  Wed Oct 15 22:37:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04045
	for <ietf-web-archive@odin.ietf.org>; Wed, 15 Oct 2003 22:37:27 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A9xw8-0007vP-Pi
	for ietf-list@asgard.ietf.org; Wed, 15 Oct 2003 22:32:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A9xtz-0007q4-MG
	for ietf@asgard.ietf.org; Wed, 15 Oct 2003 22:30:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03732
	for <ietf@ietf.org>; Wed, 15 Oct 2003 22:30:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9xtx-0006uZ-00
	for ietf@ietf.org; Wed, 15 Oct 2003 22:30:09 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9xtx-0006uI-00
	for ietf@ietf.org; Wed, 15 Oct 2003 22:30:09 -0400
Subject: RE: rfc1918 impact
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 15 Oct 2003 19:29:39 -0700
Content-class: urn:content-classes:message
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C652@server2003.arneill-py.sacramento.ca.us>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: rfc1918 impact
thread-index: AcOTjQEdXcp+3BKaQ+CU9ciZuBNAgQAACVoQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <dts@senie.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

>> Intercept would be nice in the following situations:
>> - When Joe Blow has configured a static IP and static DNS servers
that
>> point to the ISP's DNS servers instead of the NAT box.

> Keith Moore wrote:
> so the next time Joe Blow is trying to figure out why a particular
> DNS server isn't responding correctly by explicitly sending it
> queries, the NAT box will intercept the queries, forge replies,
> and mask the problem.

No. Read the text again: what we are talking about is intercepting the
MS client trying to register dynamic DNS with the ISP's DNS server, not
queries.

Michel.




From owner-ietf@ietf.org  Thu Oct 16 03:29:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22864
	for <ietf-web-archive@odin.ietf.org>; Thu, 16 Oct 2003 03:29:17 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AA2J4-0001Md-0H
	for ietf-list@asgard.ietf.org; Thu, 16 Oct 2003 03:12:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AA2I6-0001Ka-94
	for ietf@asgard.ietf.org; Thu, 16 Oct 2003 03:11:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22396
	for <ietf@ietf.org>; Thu, 16 Oct 2003 03:11:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA2I3-0001P1-00
	for ietf@ietf.org; Thu, 16 Oct 2003 03:11:19 -0400
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA2I2-0001Oy-00
	for ietf@ietf.org; Thu, 16 Oct 2003 03:11:18 -0400
Received: from limbo (limbo.unfix.org [3ffe:8114:2000:240:200:39ff:fe77:1f3f])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP id 17A568311;
	Thu, 16 Oct 2003 09:11:16 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Dean Anderson'" <dean@av8.com>
Cc: <ietf@ietf.org>
Subject: RE: rfc1918 impact
Date: Thu, 16 Oct 2003 09:11:16 +0200
Organization: Unfix
Message-ID: <002801c393b4$b1aa4bf0$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <Pine.LNX.4.44.0310152140360.7036-100000@vista.av8.net>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

Dean Anderson wrote:

> Reverse DNS is probably not going to be working or widely used in 
> IPV6, which has
> an alternate ICMP host information query so that reverse DNS is not
> necessary for the most useful purpose of reverse DNS: traceroute.

I think you underestimate the 'power' of Reverse DNS.
The primary reason that tunnelbrokers are so popular, with even
the non-technical folks, is simply because of Reverse DNS :
  - Reverse DNS gives a nice host on IRC -

Ofcourse ICMP host information could solve that.
But afaik there is no 'secure icmp host information' packet yet.
And we are going to get at dnssec one day.

Next to the vanity host usage of reverse dns there is also
the usage for reverse dns in logs, reverse in 'who' output
and probably many other reasons. Loganalyzing tools are
another popular example of reverse dns usage. Ofcourse
that can be solved too with icmp's, but icmp's don't work
when the host in question is offline, ofcourse one is to
wonder if the host is offline if the dns is not offline
or that the IP is in use by another host etc...
Next to that reverse usually matched forwards, if reverse
is split from forward lookups there is going to be a difference.

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / jeroen@unfix.org / http://unfix.org/~jeroen/

iQA/AwUBP45ElCmqKFIzPnwjEQKe7gCfT5/MWZ9pkkz9U+pnTYnUWKfuADcAn2wW
YeRsiz6r6NDRD7X44km5KBko
=t5WN
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Thu Oct 16 05:52:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26208
	for <ietf-web-archive@odin.ietf.org>; Thu, 16 Oct 2003 05:52:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AA4aM-0007Va-3O
	for ietf-list@asgard.ietf.org; Thu, 16 Oct 2003 05:38:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AA4Zy-0007SP-5A
	for ietf@asgard.ietf.org; Thu, 16 Oct 2003 05:37:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25783
	for <ietf@ietf.org>; Thu, 16 Oct 2003 05:37:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA4Zv-0002X0-00
	for ietf@ietf.org; Thu, 16 Oct 2003 05:37:55 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA4Zu-0002WM-00
	for ietf@ietf.org; Thu, 16 Oct 2003 05:37:55 -0400
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 9ACA561C22; Thu, 16 Oct 2003 11:37:25 +0200 (CEST)
Date: Thu, 16 Oct 2003 11:04:32 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: erosen@cisco.com
Cc: ietf@ietf.org, problem-statement@alvestrand.no
Subject: IETF mission boundaries (Re: IESG proposed statement on the IETF
 mission )
Message-ID: <11016450.1066302272@localhost>
In-Reply-To: <200310151657.h9FGvBlb000917@rtp-core-2.cisco.com>
References:  <200310151657.h9FGvBlb000917@rtp-core-2.cisco.com>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric,

--On 15. oktober 2003 12:57 -0400 Eric Rosen <erosen@cisco.com> wrote:

> Well, let's test this assertion.  Suppose a consortium of electric
> companies develops a UDP-based protocol  for monitoring and controlling
> street lights. It turns  out that  this protocol generates  an unbounded
> amount  of traffic (say,  proportional to  the square  of the  number of
> street lights  in the world), has no  congestion control, and no
> security, but  is expected to run over the Internet.
>
> According to you, this has nothing to  do with the IETF.  It might result
> in the congestive collapse of the Internet,  but who cares, the IETF
> doesn't do street  lights.  I would  like  to see  the  criteria  which
> determine  that telephones belong on the Internet but street lights don't!

thanks for making the most concise statement of the conflict here in the 
discussion so far!
I think this point is one of the critical causes of conflict when talking 
about the IETF mission - and unless we lance the boil, actually talk about 
it, and attempt to *resolve* the issue, we will go on revisiting the issue 
forever, with nothing but wasted energy to show for it.

In the discussions leading up to this document, we actually had 3 different 
other levels of "inclusivity" up for consideration:

- "Everything that runs over the Internet is appropriate for IETF 
standardization". Obviously, that might cause some reactions from 
organizations like the W3C, OMG, ISO, ITU, the power grid standardizers, 
the bank transaction standardizers and others.... even if the IETF were 
able to gather the required competence, it's hard to see how we could build 
a management structure that could handle "everything".

- "Everything that needs open, documented interoperability and runs over 
the Internet is appropriate for IETF standardization". A bit smaller, but 
still huge, and hard to draw boundaries around. Advantage: Everything we 
currently work on is unquestionably part of the IETF's scope.

- "Everything that builds infrastructures on the Internet that needs to be 
open and interoperable is appropriate for IETF standardization". This would 
place SMTP, DNS and LDAP (in the original vision) inside the IETF's sphere, 
but would leave the traffic lights (and the current way LDAP is used) 
outside it.

- "Everything that can seriously impact the Internet is appropriate for 
IETF standardization". Argues for keeping HTTP and DNS, would include your 
hypothetical traffic lights, but would probably leave POP/IMAP out, and 
leaves people arguing about both SIP and L3VPN.

- "For the Internet" - only the stuff that is directly involved in making 
the Internet work is included in the IETF's scope.

It's far from clear in my mind what the right thing is, or what the 
appropriate path forward is if the IETF regards its purpose as being one or 
the other - we might, for instance, decide that we standardize stuff that 
needs to be open and interoperable, but have different evaluation criteria 
for those things than for those things that "make the Internet work", and 
will dispose our resources accordingly - I don't know. And if we decide 
that certain things we currently do are outside our scope, we've got a 
responsibility to make sure the work effort is handled in a responsible 
fashion.

But it's relatively clear to my mind that continuing to have both sides of 
a discussion argue based on "the mission of the IETF", with conflicting 
definitions, is not the best thing for the Internet.

So - rather than stating something completely vague, we put out a proposal. 
If it's the wrong proposal, it should be changed. But please be specific 
about what you think it should be changed to.

makes sense?

                  Harald






From owner-ietf@ietf.org  Thu Oct 16 12:19:05 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08742
	for <ietf-web-archive@odin.ietf.org>; Thu, 16 Oct 2003 12:19:05 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAASA-0000rK-Oe
	for ietf-list@asgard.ietf.org; Thu, 16 Oct 2003 11:54:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAARV-0000oi-BN
	for ietf@asgard.ietf.org; Thu, 16 Oct 2003 11:53:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07837
	for <ietf@ietf.org>; Thu, 16 Oct 2003 11:53:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAARU-00069D-00
	for ietf@ietf.org; Thu, 16 Oct 2003 11:53:36 -0400
Received: from smtp015.mail.yahoo.com ([216.136.173.59])
	by ietf-mx with smtp (Exim 4.12)
	id 1AAARS-000699-00
	for ietf@ietf.org; Thu, 16 Oct 2003 11:53:35 -0400
Received: from ts46-01-qdr3166.mrgnhll.ca.charter.com (HELO yahoo.com) (m?seery@68.118.70.100 with plain)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 16 Oct 2003 15:53:32 -0000
Message-ID: <3F8EBF0C.10505@yahoo.com>
Date: Thu, 16 Oct 2003 08:53:48 -0700
From: mark seery <m_seery@yahoo.com>
Reply-To: m_seery@yahoo.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IESG proposed statement on the IETF mission
References: <157547561.1066175290@localhost>            <20031015124837.79dbcd11.moore@cs.utk.edu> <200310151716.h9FHG95H009885@turing-police.cc.vt.edu>
In-Reply-To: <200310151716.h9FHG95H009885@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald.

Interesting, important, thanks.....

Internet usage
==========

One of the large dynamics not explicitly mentioned is the increased 
commercial usage/value of the Internet and how that drives the community 
in new directions.

Trust model
=========

Inherent in Eric's problem statement is the notion that end systems have 
the ability to impact the experience other Internet users have. Whether 
this is the result of an historical trust model, where people using the 
Internet were assumed to a) have clue and b) be acting in the best 
interests of the community, or whether this is the result of other 
community values, this diserves comment/debate, IMHO.

The basic dynamic of course that needs to be balanced is the rights of 
Internet users, the role and obligations of operators, and the creative 
abuse of the network that could lead to unforseen new value and 
applications.

Discusion of trust models will inevitably also lead us down the road of 
discussing hairy issues such as (D)DOS - but isn't that one of the more 
pressing issues today?

Network Architecture & layers 1-9
=========================

Firstly, seems there are four basic functions that need addressing in 
the building of internets (remembering the network of networks value, 
there is not one "I"nternet):

-Transport of packets from one edge of an internet to the other edge 
 (PE if u like, but...).
-Transport of packets from end system to end system over one of more 
internets
-Management and operation of internets
-Applications that make use of the above infrastructure

Based on the inclusivity problem statement positions you have 
considered, and other comments WRT how much the IETF can do, it would 
appear that over time the last bullet point above might become disjoint 
from the first three. Not arguing that application development should be 
done at the IETF, but I think that some recognition needs to be made of 
the vastly different skill sets and interests of end-system operators 
and engineers and infrastructure operators and engineers. Perhaps the 
"area" concept needs another super-layer, especially given the vast 
difference in communities of liasion.

Lastly, some discussion of layer 1-to-9 should take place. Seems to me 
the IETF works very well when focused at layers 3 to 4; has of course 
established many important application layer standards; but experiences 
challenging liasion when focusing below layer three (data/user plane) - 
PPP not withstanding. In the spirit of "we can not do everything", this 
is deserving of discussion if for no other reason than to clear the air 
as we move forward.

Perhaps one of the most important areas of focus is the connection of 
end systems and internets to other internets. This is an area that must 
allow for creative abuse of the network through both freedom of higher 
layer protocols and also the facilitation and participation of as many 
systems vendors as possible addressing cable, wireless, wireline,....... 
This area should especially be supported by standards, implementation 
agreeements, and interoperability efforts.

The immutable vs the mutable
=====================

Seems like it would be useful to separate the immutable from the mutable.

Examples of immutable might be (not a prescription just examples):

-rough consensus
-running code
-Chairs that operate in the best interests of the community
-the UNIX-like adherence to development of small building blocks (also 
present in biology BTW).
-network of networks

Examples of the mutable might be:

-over the next 5 years we are going to focus on (D)DOS

Lancing the boil
============

There is nothing nice, pleasant, or enjoyable about lancing boils, but 
if we are to do so, then the starting point should be the encouragement 
of the identification of the largest boils.




From owner-ietf@ietf.org  Thu Oct 16 12:21:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08843
	for <ietf-web-archive@odin.ietf.org>; Thu, 16 Oct 2003 12:21:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAAmU-000270-EJ
	for ietf-list@asgard.ietf.org; Thu, 16 Oct 2003 12:15:18 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAAlt-00024j-KO
	for ietf@asgard.ietf.org; Thu, 16 Oct 2003 12:14:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08522
	for <ietf@ietf.org>; Thu, 16 Oct 2003 12:14:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAAls-0006KA-00
	for ietf@ietf.org; Thu, 16 Oct 2003 12:14:40 -0400
Received: from [202.99.160.4] (helo=mail1)
	by ietf-mx with smtp (Exim 4.12)
	id 1AAAlq-0006Jx-00
	for ietf@ietf.org; Thu, 16 Oct 2003 12:14:39 -0400
Received: from asgard.ietf.org([132.151.6.40]) by www.heinfo.net(AIMC 2.9.5.2)
	with SMTP id jm03f892cb8; Sun, 12 Oct 2003 13:22:44 +0800
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1A8YpY-0004Zg-HB
	for ietf-list@asgard.ietf.org; Sun, 12 Oct 2003 01:31:48 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1A8Ymm-0004PO-LY
	for ietf@asgard.ietf.org; Sun, 12 Oct 2003 01:28:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25629
	for <ietf@ietf.org>; Sun, 12 Oct 2003 01:28:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Ymk-00048Q-00
	for ietf@ietf.org; Sun, 12 Oct 2003 01:28:54 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8Ymk-00048N-00
	for ietf@ietf.org; Sun, 12 Oct 2003 01:28:54 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 752C31424A; Sun, 12 Oct 2003 01:28:55 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 03107-03; Sun, 12 Oct 2003 01:28:54 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id E18D5141A7; Sun, 12 Oct 2003 01:28:53 -0400 (EDT)
Date: Sun, 12 Oct 2003 01:25:28 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Scott Bradner <sob@harvard.edu>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: accusations of cluelessness
Message-Id: <20031012012528.41dd0367.moore@cs.utk.edu>
In-Reply-To: <200310120004.h9C04OSN012384@newdev.harvard.edu>
References: <200310120004.h9C04OSN012384@newdev.harvard.edu>
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Just what would you suggest in the way of relaxing?

since I view this as a hypothetical situation anyway (and one that isn't
likely to happen in the real world) I don't think it's necessary to pin down
exactly how they'd go about relaxing the criteria - only to realize that it is
possible to relax those criteria.they could ask for less money, or less
supporting evidence, or they could give out bigger blocks.  whatever.  

note that I didn't say it was a good idea to do this.  but if, as some people
assert, the v4 address shortage is a myth - then I'd be happy to try to work
on getting people to move away from NAT.  personally I still believe there's
some substance to the address shortage.  but I'd love to find out that this
isn't the case.





From owner-ietf@ietf.org  Thu Oct 16 12:48:10 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10556
	for <ietf-web-archive@odin.ietf.org>; Thu, 16 Oct 2003 12:48:10 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AABD3-0004Ix-Qp
	for ietf-list@asgard.ietf.org; Thu, 16 Oct 2003 12:42:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AABC3-0004Gp-TP
	for ietf@asgard.ietf.org; Thu, 16 Oct 2003 12:41:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10240
	for <ietf@ietf.org>; Thu, 16 Oct 2003 12:41:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AABC2-0006pW-00
	for ietf@ietf.org; Thu, 16 Oct 2003 12:41:42 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AABC1-0006pT-00
	for ietf@ietf.org; Thu, 16 Oct 2003 12:41:42 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id h9GGfZe28863;
	Thu, 16 Oct 2003 09:41:35 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200310161641.h9GGfZe28863@boreas.isi.edu>
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the IETF mission )
In-Reply-To: <11016450.1066302272@localhost> from Harald Tveit Alvestrand at "Oct 16, 3 11:04:32 am"
To: harald@alvestrand.no (Harald Tveit Alvestrand)
Date: Thu, 16 Oct 2003 09:41:35 -0700 (PDT)
Cc: erosen@cisco.com, ietf@ietf.org, problem-statement@alvestrand.no
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

% --On 15. oktober 2003 12:57 -0400 Eric Rosen <erosen@cisco.com> wrote:
% 
% > Well, let's test this assertion.  Suppose a consortium of electric
% > companies develops a UDP-based protocol  for monitoring and controlling
% > street lights. It turns  out that  this protocol generates  an unbounded
% > amount  of traffic (say,  proportional to  the square  of the  number of
% > street lights  in the world), has no  congestion control, and no
% > security, but  is expected to run over the Internet.
% >
% > According to you, this has nothing to  do with the IETF.  It might result
% > in the congestive collapse of the Internet,  but who cares, the IETF
% > doesn't do street  lights.  I would  like  to see  the  criteria  which
% > determine  that telephones belong on the Internet but street lights don't!
% 
% thanks for making the most concise statement of the conflict here in the 
% discussion so far!
% I think this point is one of the critical causes of conflict when talking 
% about the IETF mission - and unless we lance the boil, actually talk about 
% it, and attempt to *resolve* the issue, we will go on revisiting the issue 
% forever, with nothing but wasted energy to show for it.
% 
% In the discussions leading up to this document, we actually had 3 different 
% other levels of "inclusivity" up for consideration:
% 
% - "Everything that runs over the Internet is appropriate for IETF 
% 
% - "Everything that needs open, documented interoperability and runs over 
% the Internet is appropriate for IETF 
% 
% - "Everything that builds infrastructures on the Internet that needs to be 
% open and interoperable is appropriate for IETF standardization". 
% 
% - "Everything that can seriously impact the Internet is appropriate for 
% IETF standardization". 

% - "For the Internet" - only the stuff that is directly involved in making 
% the Internet work is included in the IETF's scope.
% 
% a discussion argue based on "the mission of the IETF", with conflicting 
% definitions, is not the best thing for the Internet.
% 
%                   Harald

	I guess for me, I always thought that the IETF and its
	precursors were interested in developing engineering 
	solutions / designing protocols that would allow "end2end or
	any2any" communications, regardless of underlying transport
	media, be it seismic wave, avian carrier, radio waves or
	the PSTN.  - At no time did I ever truly beleive that 
	the systems that used these protocols/solutions would always
	be on and fully connected.  Infrastructures that use IETF
	products have nearly always been only partially connected
	and many systems are not always on.
	
	So while a design goal might have been to support always 
	on/fully connected state, the reality is that infrastructres
	have nearly always been disjoint/unconnected and endpoints
	come and go.  But when they are connectable, they should 
	function in a seamless, e2e fashion, at least IMHO.

	And then you neglect an unstated presumption in the last 
	two bullet points:  As perceived by who?  


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



From owner-ietf@ietf.org  Thu Oct 16 13:26:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12096
	for <ietf-web-archive@odin.ietf.org>; Thu, 16 Oct 2003 13:26:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AABjq-0005yO-Fm
	for ietf-list@asgard.ietf.org; Thu, 16 Oct 2003 13:16:38 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AABis-0005wx-Qm
	for ietf@asgard.ietf.org; Thu, 16 Oct 2003 13:15:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11559
	for <ietf@ietf.org>; Thu, 16 Oct 2003 13:15:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AABir-0007Fw-00
	for ietf@ietf.org; Thu, 16 Oct 2003 13:15:37 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AABir-0007Fs-00
	for ietf@ietf.org; Thu, 16 Oct 2003 13:15:37 -0400
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h9GHF2FQ026610;
	Thu, 16 Oct 2003 13:15:02 -0400 (EDT)
Message-Id: <200310161715.h9GHF2FQ026610@rtp-core-2.cisco.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org, problem-statement@alvestrand.no
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the IETF mission ) 
In-reply-to: Your message of Thu, 16 Oct 2003 11:04:32 +0200.
             <11016450.1066302272@localhost> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 16 Oct 2003 13:15:02 -0400
From: Eric Rosen <erosen@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


> - "For the Internet" - only the stuff that is directly involved in making 
> the Internet work is included in the IETF's scope. 

In other words, routing,  DNS, and Internet operations/management.  Adopting
this as  the IETF's mission  would be a  very radical change  indeed!  While
this particular  mission statement does seem  to reflect the  interests of a
certain notorious IESG member, let's not pretend that this has ever been the
limit of the IETF's mission.  The IETF has always been concerned with things
that make the Internet more useful,  and with things that expand the utility
of the IP protocol suite.  There's never been a time when "for the Internet"
was an accurate representation of the IETF's concerns.

You are  of course welcome  to propose such  a radical change to  the IETF's
mission.  But  if you are  going to circulate  a document under  the subject
line "IESG proposed statement on the IETF mission", you should make it clear
that the  IESG is proposing to make  a complete change in  the IETF mission.
Instead,  you  give  the impression  that  the  IESG  thinks that  "for  the
Internet" is and has always been the IETF's mission. 

The  formulation   I  like  is  "Everything  that   needs  open,  documented
interoperability  and  runs  over  the  Internet  is  appropriate  for  IETF
standardization".  This is  much truer to the IETF's  current and historical
practice.  

That doesn't  necessarily mean that  the IETF has to  standardize everything
that falls within  its mission.  For instance, a  particular area might fall
within the mission, but the IETF  might not have the expertise to tackle it.
A WG  in that area  could then be  rejected on the grounds  of "insufficient
expertise".  Such decisions  would have to be made  on a case-by-case basis.
Again, this is the way such decisions have always been made in the IETF.










From owner-ietf@ietf.org  Thu Oct 16 13:42:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12895
	for <ietf-web-archive@odin.ietf.org>; Thu, 16 Oct 2003 13:42:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAC4T-000744-Ou
	for ietf-list@asgard.ietf.org; Thu, 16 Oct 2003 13:37:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAC2l-0006ym-G2
	for ietf@asgard.ietf.org; Thu, 16 Oct 2003 13:36:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12465
	for <ietf@ietf.org>; Thu, 16 Oct 2003 13:36:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAC2k-0007Tz-00
	for ietf@ietf.org; Thu, 16 Oct 2003 13:36:10 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAC2i-0007Tw-00
	for ietf@ietf.org; Thu, 16 Oct 2003 13:36:09 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id h9GHa5OC014152
	for ietf@ietf.org env-from <vjs>;
	Thu, 16 Oct 2003 11:36:05 -0600 (MDT)
Date: Thu, 16 Oct 2003 11:36:05 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200310161736.h9GHa5OC014152@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the IETF mission )
References: <200310161715.h9GHF2FQ026610@rtp-core-2.cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Eric Rosen <erosen@cisco.com>

> > - "For the Internet" - only the stuff that is directly involved in making 
> > the Internet work is included in the IETF's scope. 
>
> In other words, routing,  DNS, and Internet operations/management.  Adopting
> this as  the IETF's mission  would be a  very radical change  indeed!  While
> this particular  mission statement does seem  to reflect the  interests of a
> certain notorious IESG member, let's not pretend that this has ever been the
> limit of the IETF's mission.  The IETF has always been concerned with things
> that make the Internet more useful,  and with things that expand the utility
> of the IP protocol suite.  There's never been a time when "for the Internet"
> was an accurate representation of the IETF's concerns.

That is wrong or at least a gross overstatement.

> ...
> The  formulation   I  like  is  "Everything  that   needs  open,  documented
> interoperability  and  runs  over  the  Internet  is  appropriate  for  IETF
> standardization".  This is  much truer to the IETF's  current and historical
> practice.  

That is also wrong or at least a gross overstatement.  There have been
many things that the IETF has chosen to step away from but that ran
and run over the Internet.  Some graphics standards come immediately
to my mind.

> That doesn't  necessarily mean that  the IETF has to  standardize everything
> that falls within  its mission.  For instance, a  particular area might fall
> within the mission, but the IETF  might not have the expertise to tackle it.
> A WG  in that area  could then be  rejected on the grounds  of "insufficient
> expertise".  Such decisions  would have to be made  on a case-by-case basis.
> Again, this is the way such decisions have always been made in the IETF.

No committee is ever able to limit itself on grounds of insufficient
expertise.  The people who join committees are predisposed to think
that they're sufficiently expert to deal with the subject matter.

Those graphics standards were kept out of the IETF not because the
working groups involved thought they didn't think they were experts,
but because the subject was out of scope for the IETF.  That most of
participants had no clues about computer graphics was incomprehensible
to most of the participants, and unfortunately irrelevant.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Thu Oct 16 14:39:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15491
	for <ietf-web-archive@odin.ietf.org>; Thu, 16 Oct 2003 14:39:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AACqD-0000ky-Hq
	for ietf-list@asgard.ietf.org; Thu, 16 Oct 2003 14:27:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AACpU-0000iD-Ve
	for ietf@asgard.ietf.org; Thu, 16 Oct 2003 14:26:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14965
	for <ietf@ietf.org>; Thu, 16 Oct 2003 14:26:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AACpT-0000IH-00
	for ietf@ietf.org; Thu, 16 Oct 2003 14:26:31 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AACpS-0000Hs-00
	for ietf@ietf.org; Thu, 16 Oct 2003 14:26:31 -0400
Received: from cisco.com (64.102.124.12)
  by sj-iport-5.cisco.com with ESMTP; 16 Oct 2003 11:26:43 -0700
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h9GIPvFH024826;
	Thu, 16 Oct 2003 14:25:58 -0400 (EDT)
Message-Id: <200310161825.h9GIPvFH024826@rtp-core-1.cisco.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the IETF mission ) 
In-reply-to: Your message of Thu, 16 Oct 2003 11:36:05 -0600.
             <200310161736.h9GHa5OC014152@calcite.rhyolite.com> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 16 Oct 2003 14:25:57 -0400
From: Eric Rosen <erosen@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


> That is wrong or at least a gross overstatement. 

If  that's  what  you think,  I  invite  you  to  make  a list  of  all  the
IETF-standardized protocols and explain how  they are all (or even more than
50% of them) needed to make the Internet work.

> There have been many things that the IETF has chosen to step away from but
> that  ran  and  run  over  the Internet.   Some  graphics  standards  come
> immediately to my  mind ... Those graphics standards were  kept out of the
> IETF not  because the  working groups involved  thought they  didn't think
> they were experts, but because the subject was out of scope for the IETF." 

I'm not  familiar with this particular  case, but I don't  see why protocols
for distributing graphics would be thought  to fall outside the scope of the
IETF, any more  than protocols for distributing voice  or video.  Of course,
graphics standards  that have nothing  do with distribution of  the graphics
over IP would be out of scope.

> No committee is ever able to limit itself on grounds of insufficient
> expertise.  

Now, there  is a  gross overstatement!  For  everyone who  proclaims himself
(rightly or  wrongly) to be  an expert on  some topic, there are  always two
other people who claim  that he is clueless.  It's not uncommon  for a WG to
refuse  to  pick up  a  topic  because the  consensus  is  that the  topic's
proponents are clueless.  











From owner-ietf@ietf.org  Thu Oct 16 16:49:53 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24031
	for <ietf-web-archive@odin.ietf.org>; Thu, 16 Oct 2003 16:49:53 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAE0p-0003CG-6H
	for ietf-list@asgard.ietf.org; Thu, 16 Oct 2003 15:42:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AADzP-000351-PG
	for ietf@asgard.ietf.org; Thu, 16 Oct 2003 15:40:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19644
	for <ietf@ietf.org>; Thu, 16 Oct 2003 15:40:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADzO-0001Ag-00
	for ietf@ietf.org; Thu, 16 Oct 2003 15:40:50 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADzN-0001Ad-00
	for ietf@ietf.org; Thu, 16 Oct 2003 15:40:49 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id h9GJegQn010296
	for ietf@ietf.org env-from <vjs>;
	Thu, 16 Oct 2003 13:40:42 -0600 (MDT)
Date: Thu, 16 Oct 2003 13:40:42 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200310161940.h9GJegQn010296@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the IETF mission )
References: <200310161825.h9GIPvFH024826@rtp-core-1.cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Eric Rosen <erosen@cisco.com>

> > That is wrong or at least a gross overstatement. 
>
> If  that's  what  you think,  I  invite  you  to  make  a list  of  all  the
> IETF-standardized protocols and explain how  they are all (or even more than
> 50% of them) needed to make the Internet work.

There's a progression here:
  1. ad hoc network interoperability group forms.
  2. it has some success and gains some fame.
  3. it is besieged by people eager to borrow its printing press
  4. it is besieged by people who know everything about everything and
    have a duty to write or at least control all standards on
    everything including what people perversions do in the privacy
    of their own networks.

I've been complaining about #3 for many years.  Examples of #4 include
some of the more vigorous combatants in the IPv6 site local arena
and the notion that notion that nothing is out of scope.


> > There have been many things that the IETF has chosen to step away from but
> > that  ran  and  run  over  the Internet.   Some  graphics  standards  come
> > immediately to my  mind ... Those graphics standards were  kept out of the
> > IETF not  because the  working groups involved  thought they  didn't think
> > they were experts, but because the subject was out of scope for the IETF." 
>
> I'm not  familiar with this particular  case, but I don't  see why protocols
> for distributing graphics would be thought  to fall outside the scope of the
> IETF, any more  than protocols for distributing voice  or video.  Of course,
> graphics standards  that have nothing  do with distribution of  the graphics
> over IP would be out of scope.

The example I'm thinking about involved predecessors to OpenGL.
People who know about network stuff know enough to stuff bits into
wires, but that's the earier part of things like OpenGL, Microsoft's
alternative whose name eludes me, JPEG, MPEG, and so forth.


> > No committee is ever able to limit itself on grounds of insufficient
> > expertise.  
>
> Now, there  is a  gross overstatement!  For  everyone who  proclaims himself
> (rightly or  wrongly) to be  an expert on  some topic, there are  always two
> other people who claim  that he is clueless. 

The other two base their claims on their own greater expertise and
wouldn't dream of suggesting that they are not well suited for
standardizing whatever it is.

>                                           It's not uncommon  for a WG to
> refuse  to  pick up  a  topic  because the  consensus  is  that the  topic's
> proponents are clueless.  

Please name an example of such a case.  I have seen WG chairs and
others use brute force and out-of-scope arguments to halt nonsense,
but I've never seen "we don't know enough" work.  Often the brutal WG
chairs say they don't think the WG knows enough, but it's the scope
arguments that carry the day.


Sheesh!--next you'll be telling us that you never heard the phrase
"out of scope" before last week.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri Oct 17 02:57:24 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21361
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 02:57:24 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAO8m-0007WB-KH
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 02:31:12 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAO7u-0007UM-W5
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 02:30:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20887
	for <ietf@ietf.org>; Fri, 17 Oct 2003 02:30:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAO7s-0007HO-00
	for ietf@ietf.org; Fri, 17 Oct 2003 02:30:16 -0400
Received: from tomts31.bellnexxia.net ([209.226.175.105] helo=tomts31-srv.bellnexxia.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAO7s-0007HL-00
	for ietf@ietf.org; Fri, 17 Oct 2003 02:30:16 -0400
Received: from yahoo.com ([65.93.181.155]) by tomts31-srv.bellnexxia.net
          (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP
          id <20031017063012.NOTJ20110.tomts31-srv.bellnexxia.net@yahoo.com>;
          Fri, 17 Oct 2003 02:30:12 -0400
Date: Fri, 17 Oct 2003 02:30:10 -0400
Subject: Re: IESG proposed statement on the IETF mission 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: problem-statement@alvestrand.no, ietf@ietf.org,
        Harald Tveit Alvestrand <harald@alvestrand.no>
To: erosen@cisco.com
From: Simon Woodside <sbwoodside@yahoo.com>
In-Reply-To: <200310151657.h9FGvBlb000917@rtp-core-2.cisco.com>
Message-Id: <5BC4BFD8-006B-11D8-B366-000A9573F104@yahoo.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Wednesday, October 15, 2003, at 12:57  PM, Eric Rosen wrote:

>
>> "The purpose of  the IETF is to create high  quality, relevant, and 
>> timely
>> standards for the Internet."
>
>> It is important that this is "For the Internet," and does not include
>> everything that happens to use IP.  IP is being used in a myriad of
>> real-world applications, such as controlling street lights, but the
>> IETF does not standardize those applications.

Yes, and towards a possibly more contentious application, see Voice 
over IP. Lots of VoIP work is being done without involving the internet 
at all. Used by telecoms for telecoms applications, where "best effort" 
isn't good enough because it needs to keep working when the power goes 
out. IP, yes, Internet, no.

Against that you have "voice over internet" which is AKA "voice chat" 
and already abounds in true internet p2p apps like iChat, GnomeMeeting, 
and some programs on that other OS. These run on the public internet 
and benefit from the IETF design paradigms like edge-to-edge (aka 
end2end) and best effort but also have to accept the relevant drawbacks.

simon

> Well, let's test this assertion.  Suppose a consortium of electric 
> companies
> develops a UDP-based protocol  for monitoring and controlling street 
> lights.
> It turns  out that  this protocol generates  an unbounded amount  of 
> traffic
> (say,  proportional to  the square  of the  number of  street lights  
> in the
> world), has no  congestion control, and no security, but  is expected 
> to run
> over the Internet.
>
> According to you, this has nothing to  do with the IETF.  It might 
> result in
> the congestive collapse of the Internet,  but who cares, the IETF 
> doesn't do
> street  lights.  I would  like  to see  the  criteria  which determine 
>  that
> telephones belong on the Internet but street lights don't!
>
> Another problem  with your  formulation is that  the Internet is  a 
> growing,
> changing, entity,  so "for the Internet"  often means "for what  I 
> think the
> Internet  should  be  in  a  few  years", and  this  is  then  a  
> completely
> unobjective criterion.  One  would hope instead that the  IETF would 
> want to
> encourage competition between different  views of Internet evolution, 
> as the
> competition of ideas is the way to make progress.
>
> I also do not understand whether "for the Internet" means something 
> different
> than "for IP networking" or not.
>
> I think  it should  also be part  of the  mission to produce  
> standards that
> facilitate the migration to IP  of applications and infrastructures 
> that use
> legacy networking  technologies.  Such  migration seems to  be good  
> for the
> Internet, but I don't know if it is "for the Internet" or not.
>
>

--
www.simonwoodside.com :: www.openict.net :: www.semacode.org
                     99% Devil, 1% Angel




From owner-ietf@ietf.org  Fri Oct 17 03:49:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22847
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 03:49:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAPFT-0000cW-Q5
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 03:42:11 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAPFP-0000bM-6B
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 03:42:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22701
	for <ietf@ietf.org>; Fri, 17 Oct 2003 03:41:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAPFM-00006E-00
	for ietf@ietf.org; Fri, 17 Oct 2003 03:42:04 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1AAPFL-00006B-00
	for ietf@ietf.org; Fri, 17 Oct 2003 03:42:03 -0400
Received: (qmail 50454 invoked from network); 17 Oct 2003 07:41:29 -0000
Received: from vaio.hpcl.titech.ac.jp (HELO necom830.hpcl.titech.ac.jp) (131.112.32.134)
  by necom830.hpcl.titech.ac.jp with SMTP; 17 Oct 2003 07:41:29 -0000
Message-ID: <3F8F9D82.80602@necom830.hpcl.titech.ac.jp>
Date: Fri, 17 Oct 2003 16:42:58 +0900
From: masataka ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Simon Woodside <sbwoodside@yahoo.com>
CC: erosen@cisco.com, problem-statement@alvestrand.no, ietf@ietf.org,
        Harald Tveit Alvestrand <harald@alvestrand.no>
Subject: Re: IESG proposed statement on the IETF mission
References: <5BC4BFD8-006B-11D8-B366-000A9573F104@yahoo.com>
In-Reply-To: <5BC4BFD8-006B-11D8-B366-000A9573F104@yahoo.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Simon Woodside;

> Yes, and towards a possibly more contentious application, see Voice over 
> IP. Lots of VoIP work is being done without involving the internet at 
> all. Used by telecoms for telecoms applications, where "best effort" 
> isn't good enough because it needs to keep working when the power goes 
> out. IP, yes, Internet, no.

Why, do you think, the Internet may stop working when the power
goes out?

It should not, which is required to certain ISPs by regulation at
least in Japan.

> Against that you have "voice over internet" which is AKA "voice chat" 
> and already abounds in true internet p2p apps like iChat, GnomeMeeting, 
> and some programs on that other OS. These run on the public internet and 
> benefit from the IETF design paradigms like edge-to-edge (aka end2end) 
> and best effort but also have to accept the relevant drawbacks.

"voice chat"? Are you assuming PCs?

POTS telephone devices and terminal adaptors is the natural way
of "voice over the Internet".

Note that end to end architecture means ultimate availability of
fate sharing.

						Masataka Ohta

PS

According to the end to end principle, end user equipments should
have their own power backup, of course, which is also the case with
ISDN TA or cellular phone devices. Then, with multihoming, your
connection is a lot more robust than that of a single telephone
company. 




From owner-ietf@ietf.org  Fri Oct 17 11:25:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06213
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 11:25:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAWGu-0006u9-Q5
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 11:12:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAWG4-0006tH-Bq
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 11:11:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05748
	for <ietf@ietf.org>; Fri, 17 Oct 2003 11:11:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWG3-0004Gf-00
	for ietf@ietf.org; Fri, 17 Oct 2003 11:11:15 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWG2-0004GE-00
	for ietf@ietf.org; Fri, 17 Oct 2003 11:11:14 -0400
Received: from cisco.com (64.102.124.12)
  by sj-iport-5.cisco.com with ESMTP; 17 Oct 2003 08:10:53 -0700
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h9HFAdFH022387;
	Fri, 17 Oct 2003 11:10:40 -0400 (EDT)
Message-Id: <200310171510.h9HFAdFH022387@rtp-core-1.cisco.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the IETF mission ) 
In-reply-to: Your message of Thu, 16 Oct 2003 13:40:42 -0600.
             <200310161940.h9GJegQn010296@calcite.rhyolite.com> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Fri, 17 Oct 2003 11:10:35 -0400
From: Eric Rosen <erosen@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


> Sheesh!--next you'll be telling us that you never heard the phrase
> "out of scope" before last week. 

Sure I have.  There's  hardly a piece of work done by  the IETF that someone
hasn't claimed to  be out of scope.   It's just that the phrase  is not used
consistently.  If  we look at the  historical facts about the  work that the
IETF has traditionally taken on, it's hard to draw any conclusion other than
that anything  is in  scope which  promotes and facilitates  the use  of the
Internet and of IP infrastructure.  And I think that's exactly what the IETF
should be doing.

> The example I'm thinking about involved predecessors to OpenGL. 

As this example  doesn't even involve communication over  a network, I would
agree that it  is out of scope.   But that's a rather extreme  case, most of
the contentious areas do involve communications over an IP infrastructure.

> Often the brutal  WG chairs say they don't think the  WG knows enough, but
> it's the scope arguments that carry the day. 

I've never had  much luck myself with scope arguments,  unless they could be
backed up with an argument either that the center of expertise is elsewhere,
or that the topic has no bearing on IP.  Of course, people will sometimes be
willing  to  agree  that  the  center  of  expertise  is  elsewhere  without
necessarily agreeing that they themselves aren't experts ;-) Sometimes scope
arguments are merely  face-saving ways of saying "we don't  know what we are
doing".  Other times, scope arguments are merely "polite" ways of saying "we
don't think  you know what  you are doing".   You almost never  hear someone
saying "that sounds like a really  good idea, but unfortunately it is out of
scope". 







From owner-ietf@ietf.org  Fri Oct 17 11:25:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06234
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 11:25:38 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAWPc-00074J-GE
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 11:21:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAWP3-00073K-NB
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 11:20:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06019
	for <ietf@ietf.org>; Fri, 17 Oct 2003 11:20:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWP0-0004Lu-00
	for ietf@ietf.org; Fri, 17 Oct 2003 11:20:30 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWP0-0004Ld-00
	for ietf@ietf.org; Fri, 17 Oct 2003 11:20:30 -0400
Received: from cisco.com (64.102.124.13)
  by sj-iport-5.cisco.com with ESMTP; 17 Oct 2003 08:20:07 -0700
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h9HFJuFQ008370;
	Fri, 17 Oct 2003 11:19:56 -0400 (EDT)
Message-Id: <200310171519.h9HFJuFQ008370@rtp-core-2.cisco.com>
To: "Christian Huitema" <huitema@windows.microsoft.com>
cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>, ietf@ietf.org,
        problem-statement@alvestrand.no
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the IETF mission ) 
In-reply-to: Your message of Thu, 16 Oct 2003 15:15:56 -0700.
             <DAC3FCB50E31C54987CD10797DA511BA05B3E96D@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Fri, 17 Oct 2003 11:19:55 -0400
From: Eric Rosen <erosen@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk


> The gist of this comment is that someone developing a network
> application protocol ought to somehow get a blessing from the IETF. 
> Reality check. Who got the IETF approval to deploy ICQ, Kazaa, or for
> that matter HTTP? 

The fact  that someone  did something without  the IETF's approval  does not
imply that  what they did is  outside the scope of  the IETF, or  that it is
beyond the IETF's mission. 







From owner-ietf@ietf.org  Fri Oct 17 11:41:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07304
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 11:41:51 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAWe8-00088x-EF
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 11:36:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAWdT-00086p-Ux
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 11:35:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07011
	for <ietf@ietf.org>; Fri, 17 Oct 2003 11:35:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWdS-0004fP-00
	for ietf@ietf.org; Fri, 17 Oct 2003 11:35:26 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWdP-0004es-00
	for ietf@ietf.org; Fri, 17 Oct 2003 11:35:24 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id h9HFZI6P005321
	for ietf@ietf.org env-from <vjs>;
	Fri, 17 Oct 2003 09:35:18 -0600 (MDT)
Date: Fri, 17 Oct 2003 09:35:18 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200310171535.h9HFZI6P005321@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the IETF mission )
References: <200310171510.h9HFAdFH022387@rtp-core-1.cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Eric Rosen <erosen@cisco.com>

> ...
> > Sheesh!--next you'll be telling us that you never heard the phrase
> > "out of scope" before last week. 
>
> Sure I have.  There's  hardly a piece of work done by  the IETF that someone
> hasn't claimed to  be out of scope.   It's just that the phrase  is not used
> consistently.  

That's true.

>                If  we look at the  historical facts about the  work that the
> IETF has traditionally taken on, it's hard to draw any conclusion other than
> that anything  is in  scope which  promotes and facilitates  the use  of the
> Internet and of IP infrastructure.  And I think that's exactly what the IETF
> should be doing.

That's wrong.  At best it's meaningless.  For example it supports
lobbying Congress.


> > The example I'm thinking about involved predecessors to OpenGL. 
>
> As this example  doesn't even involve communication over  a network, I would
> agree that it is out of scope.   ...

It was out of scope, but not because it did not involve putting graphics
stuff over UDP or TCP, because it did.  My fellow employees in SGI's
network group and I breathed a sigh of releaf when Ron returned from
an IETF meeting to report that "out of scope" had carried the day
against other IETF participants who thought that knowing people who
knew about Nagle and congestion control and avoidance was enough to
design graphics remote procedure calls or similar.  It's not that
other examples such as X couldn't have used more network knowledge to
avoid problems (e.g. the mouse stuff), but that the network stuff is
the tail of that and many other dogs.  Because of my employement
history, I may know a little more about how to do graphics in general
or over IP networks than many IETF participants, but I know that I'm
abjectly completely utterly incompetent for doing exactly what the
IETF started to do in that case.


> > Often the brutal  WG chairs say they don't think the  WG knows enough, but
> > it's the scope arguments that carry the day. 
>
> I've never had  much luck myself with scope arguments,  unless they could be
> backed up with an argument either that the center of expertise is elsewhere,
> or that the topic has no bearing on IP.  Of course, people will sometimes be
> willing  to  agree  that  the  center  of  expertise  is  elsewhere  without
> necessarily agreeing that they themselves aren't experts ;-) Sometimes scope
> arguments are merely  face-saving ways of saying "we don't  know what we are
> doing".  Other times, scope arguments are merely "polite" ways of saying "we
> don't think  you know what  you are doing".   You almost never  hear someone
> saying "that sounds like a really  good idea, but unfortunately it is out of
> scope". 

Yes, with the proviso that you mean you usually don't hear people really
meaning that last sentence.  You certainly hear those words a lot.

If "out of scope" were removed as an acceptable reason to not do things,
then you would never squelch bad efforts.

I suspect the whole effort of defining IETF charters or missions is
a very bad idea.  It's often better to not spell things out, but to
rely on the good judgement of the people running the show.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri Oct 17 12:11:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08539
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 12:11:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAX4G-0000xm-9W
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 12:03:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAX48-0000w9-Md
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 12:03:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08276
	for <ietf@ietf.org>; Fri, 17 Oct 2003 12:02:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAX47-00053V-00
	for ietf@ietf.org; Fri, 17 Oct 2003 12:02:59 -0400
Received: from smtp015.mail.yahoo.com ([216.136.173.59])
	by ietf-mx with smtp (Exim 4.12)
	id 1AAX46-00053S-00
	for ietf@ietf.org; Fri, 17 Oct 2003 12:02:58 -0400
Received: from ts46-01-qdr3166.mrgnhll.ca.charter.com (HELO yahoo.com) (m?seery@68.118.70.100 with plain)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 17 Oct 2003 16:02:56 -0000
Message-ID: <3F9012C2.4020102@yahoo.com>
Date: Fri, 17 Oct 2003 09:03:14 -0700
From: mark seery <m_seery@yahoo.com>
Reply-To: m_seery@yahoo.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the IETF
 mission )
References: <200310171510.h9HFAdFH022387@rtp-core-1.cisco.com> <200310171535.h9HFZI6P005321@calcite.rhyolite.com>
In-Reply-To: <200310171535.h9HFZI6P005321@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Scoping is certainly used successfully as an argument at the WG level, 
through the more common pronnouncement "....that would require a change 
to the charter.." Scoping aids WGs in being able to move the ball 
forward in the direction of predfined goals, and hence is a process aid. 
This is scoping at a micro level. I would think that the role of mission 
is to provide scoping at a macro level, the kind of scoping that 
determines whether a WG is established in the first place or not.

More importantly I would suggest, the simple requirement for making 
binary decisions about whether something is in scope or not is necessary 
but not sufficient. An institution surely needs some way to guide its 
priorities as well. So one could for example agree with Eric's 
definition of what the IETF's mission is, but once that is done, what 
then guides the priorities of the IETF? I think you will find this to be 
at the heart of the debate:

scoping=>smaller workload=>focused differentiation in the standards 
marketplace+better quality output.

Every entity must decide what it is going to do uniquly better than any 
other entity. This is the purpose of mission. Generic catchall missions 
do not help entities keep the eye on that particular ball.




From owner-ietf@ietf.org  Fri Oct 17 13:29:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11594
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 13:29:46 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAYFo-0004i4-7L
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 13:19:08 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAYFj-0004h3-OA
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 13:19:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11176
	for <ietf@ietf.org>; Fri, 17 Oct 2003 13:18:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYFi-0005sf-00
	for ietf@ietf.org; Fri, 17 Oct 2003 13:19:02 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYFi-0005sV-00
	for ietf@ietf.org; Fri, 17 Oct 2003 13:19:02 -0400
Received: from cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 17 Oct 2003 10:28:38 -0700
Received: from cisco.com (sjc-vpn3-461.cisco.com [10.21.65.205])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h9HHISQY002764;
	Fri, 17 Oct 2003 10:18:29 -0700 (PDT)
Message-ID: <3F902464.6070506@cisco.com>
Date: Fri, 17 Oct 2003 10:18:28 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: ietf@ietf.org
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the IETF
 mission )
References: <200310171510.h9HFAdFH022387@rtp-core-1.cisco.com> <200310171535.h9HFZI6P005321@calcite.rhyolite.com>
In-Reply-To: <200310171535.h9HFZI6P005321@calcite.rhyolite.com>
X-Enigmail-Version: 0.76.7.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


>>>The example I'm thinking about involved predecessors to OpenGL. 
>>
>>As this example  doesn't even involve communication over  a network, I would
>>agree that it is out of scope.   ...
> 
> [OpenGL example]
> It's not that other examples such as X couldn't have used more network knowledge to
> avoid problems (e.g. the mouse stuff), but that the network stuff is
> the tail of that and many other dogs.  Because of my employement
> history, I may know a little more about how to do graphics in general
> or over IP networks than many IETF participants, but I know that I'm
> abjectly completely utterly incompetent for doing exactly what the
> IETF started to do in that case.

Great scope example.  The issue for OpenGL, however, demonstrates a gap 
in as much as the developers would probably have liked something like 
dccp so that they could use a library to get Nagle, backoff, etc.  While 
we're a wire protocol sort of a group, we all should realize the 
importance of generality and good library support ;-)


> If "out of scope" were removed as an acceptable reason to not do things,
> then you would never squelch bad efforts.

An effort isn't bad because it's out of scope.  An effort is bad because 
it's bad, and we invest our faith in the IESG that they will use good 
judgment to catch bad efforts.

If anyone on the IESG does not feel empowered to say "no" they should 
not be on the IESG.  WG chairs need to vet their own group's work first, 
of course.  And we could certainly do a better job on that.

Eliot





From owner-ietf@ietf.org  Fri Oct 17 13:57:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13331
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 13:57:26 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAYku-00057G-BK
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 13:51:16 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAYkd-00054U-1H
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 13:50:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12841
	for <ietf@ietf.org>; Fri, 17 Oct 2003 13:50:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYkb-0006LL-00
	for ietf@ietf.org; Fri, 17 Oct 2003 13:50:57 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYkZ-0006LI-00
	for ietf@ietf.org; Fri, 17 Oct 2003 13:50:56 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id h9HHolFg008804
	for ietf@ietf.org env-from <vjs>;
	Fri, 17 Oct 2003 11:50:47 -0600 (MDT)
Date: Fri, 17 Oct 2003 11:50:47 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200310171750.h9HHolFg008804@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: IETF mission boundaries 
References: <3F902464.6070506@cisco.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Eliot Lear <lear@cisco.com>

> ...
> > If "out of scope" were removed as an acceptable reason to not do things,
> > then you would never squelch bad efforts.
>
> An effort isn't bad because it's out of scope.  An effort is bad because 
> it's bad, and we invest our faith in the IESG that they will use good 
> judgment to catch bad efforts.
>
> If anyone on the IESG does not feel empowered to say "no" they should 
> not be on the IESG.  WG chairs need to vet their own group's work first, 
> of course.  And we could certainly do a better job on that.

There's a difference between feeling empowered to say "no" and having
the power to say no and make it stick or even just not be forced to
waste time in bureaucratic appeals.

What's the purpose of this "IETF mission statement" effort?  If it
involved better specifications of what the IETF doesn't do, I'd be
happy.  Instead it seems to involve replacing reasons to say "no"
with content-free blanket authorizations like "for the kids."

One might have hoped that "mission statement" would be a red flag to
more participants.  When was the last time you heard of an effort to
write a "mission statement" that wasn't fodder for "Dilbert"?  It's
good decide what you're trying to do and even better if you figure it
out befre you start, but "mission statement" seems to inevitably
produce worse than useless statements like "promote and facilitate
the use  of the Internet and of IP infrastructure."

That a IETF "mission statement" is being crafted at this late date
is a very bad sign about the likely result of that crafting and the
state of the IETF.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Fri Oct 17 14:19:18 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14328
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 14:19:18 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAZ73-0000Rg-Lp
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 14:14:09 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAZ5Y-0000OA-FC
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 14:12:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14048
	for <ietf@ietf.org>; Fri, 17 Oct 2003 14:12:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAZ5X-0006go-00
	for ietf@ietf.org; Fri, 17 Oct 2003 14:12:35 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAZ5W-0006gS-00
	for ietf@ietf.org; Fri, 17 Oct 2003 14:12:34 -0400
Received: from cisco.com (171.71.177.254)
  by sj-iport-5.cisco.com with ESMTP; 17 Oct 2003 11:12:17 -0700
Received: from cisco.com (sjc-vpn3-461.cisco.com [10.21.65.205])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h9HIC2eA021810;
	Fri, 17 Oct 2003 11:12:02 -0700 (PDT)
Message-ID: <3F9030F1.2000308@cisco.com>
Date: Fri, 17 Oct 2003 11:12:01 -0700
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: ietf@ietf.org
Subject: Re: IETF mission boundaries
References: <3F902464.6070506@cisco.com> <200310171750.h9HHolFg008804@calcite.rhyolite.com>
In-Reply-To: <200310171750.h9HHolFg008804@calcite.rhyolite.com>
X-Enigmail-Version: 0.76.7.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Vernon,

I'm not much for mission statements either.  But it's easy to fall into 
a "Dilbert" view of the world, even when such things might actually help.

I think the intent is to derive from some community consensus on goals 
how to evolve the organization.  And we are at a crossroads.  Either we 
pretty much limit our scope to a more confined area, or we need to grow. 
  And growing is painful.  It involves changing of responsibilities, 
delegation, and the like.  If a mission statement serves as a point of 
consensus from which the IETF management can march, I'm all for it, in 
principle.

Of course, it has to have sufficient substance that one can in fact 
derive a direction for management of the organization.

Eliot





From owner-ietf@ietf.org  Fri Oct 17 15:38:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18864
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 15:38:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAaFf-0000fJ-3L
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 15:27:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AASSf-0004eW-Rh
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 07:08:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27503
	for <ietf@ietf.org>; Fri, 17 Oct 2003 07:07:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AASSd-0002B4-00
	for ietf@ietf.org; Fri, 17 Oct 2003 07:07:59 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AASSc-0002Az-00
	for ietf@ietf.org; Fri, 17 Oct 2003 07:07:58 -0400
Received: from [147.28.0.62] (helo=acm.org)
	by psg.com with esmtp (Exim 4.24; FreeBSD 4.9)
	id 1AASSc-0001Mh-Qa
	for ietf@ietf.org; Fri, 17 Oct 2003 11:07:59 +0000
Date: Fri, 17 Oct 2003 20:08:11 +0900
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: Sunday training classes at IETF58
From: Avri Doria <avri@acm.org>
To: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <326F44A1-0092-11D8-897E-000393CC2112@acm.org>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In addition to the Newcomer's training and the security tutorial, the 
IETF sunday training schedule for Minneapolis will include two new 
sessions.

The first covers the editor's role in working with the WG and in 
producing RFCs.  This is a completely new course.  The session is open 
to both current editors and folks who think they may be interested in 
taking on an editorship, or co-editorship, at some point in the future.

The second is the WG chairs training course.  This is an extension of 
the course that has been given during  lunch sessions for WG chairs.  
This session is open to both current WG chairs and to anyone who thinks 
they may be interested in  chairing a WG.

The schedule for the courses is listed below.  There is no need to 
pre-register, just show up.

Thanks
a.


Sunday, November 10, 2003
=========================

1330-1430  Newcomers Training -- Salon B  (Scott Bradner)

     An introduction to the IETF for anyone who wants to know
     more about the IETF, specifically recommended for all new
     or recent IETF attendees. The session covers the IETF
     history, structure, and standards process. It also
     provides tips for success in the IETF environment.

1330-1500  Editor's Training -- Conrad C  (Avri Doria)

     Training for current or aspiring IETF document
     editors.  Covers the roles and responsibilities
     of a document editor, and includes advice on
     producing a high-quality IETF specification.

1330-1500  Intro WG Chairs Training -- Conrad B  (Margaret Wasserman)

     Introductory training for new or aspiring WG chairs.
     Covers the role and responsibilities of the WG chair,
     and includes advice on how to run a WG that is fair,
     open and productive.

1500-1700  Security Tutorial -- Salon B  (Radia Perlman)

     All IETF attendees need to be aware of the security
     implications of our design choices.  This session
     offers a basic primer in protocol security, as well
     as advice on how to write the Security Considerations
     sections required for all IETF documents.






From owner-ietf@ietf.org  Fri Oct 17 16:27:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18861
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 15:38:35 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAaFe-0000f7-Tq
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 15:27:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAGQ0-0003T8-U0
	for ietf@asgard.ietf.org; Thu, 16 Oct 2003 18:16:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28358
	for <ietf@ietf.org>; Thu, 16 Oct 2003 18:16:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAGPz-0003YQ-00
	for ietf@ietf.org; Thu, 16 Oct 2003 18:16:27 -0400
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAGPy-0003Y6-00
	for ietf@ietf.org; Thu, 16 Oct 2003 18:16:26 -0400
Received: from INET-VRS-03.redmond.corp.microsoft.com ([157.54.5.27]) by mail3.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 16 Oct 2003 15:15:52 -0700
Received: from 157.54.8.109 by INET-VRS-03.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 16 Oct 2003 15:15:51 -0700
Received: from RED-IMC-04.redmond.corp.microsoft.com ([157.54.2.168]) by inet-hub-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 16 Oct 2003 15:15:51 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by RED-IMC-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 16 Oct 2003 15:15:50 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Thu, 16 Oct 2003 15:15:50 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7097.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: IETF mission boundaries (Re: IESG proposed statement on the IETF mission )
Date: Thu, 16 Oct 2003 15:15:56 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA05B3E96D@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: IETF mission boundaries (Re: IESG proposed statement on the IETF mission )
thread-index: AcOTzBbAi1IaJVfhQ0yRRlka+N83eQAZNxhg
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>, <erosen@cisco.com>
Cc: <ietf@ietf.org>, <problem-statement@alvestrand.no>
X-OriginalArrivalTime: 16 Oct 2003 22:15:50.0414 (UTC) FILETIME=[0E81DAE0:01C39433]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


> > According to you, this has nothing to  do with the IETF.  It might
> result
> > in the congestive collapse of the Internet,  but who cares, the IETF
> > doesn't do street  lights.  I would  like  to see  the  criteria
which
> > determine  that telephones belong on the Internet but street lights
> don't!
>=20
> thanks for making the most concise statement of the conflict here in
the
> discussion so far!
> I think this point is one of the critical causes of conflict when
talking
> about the IETF mission - and unless we lance the boil, actually talk
about
> it, and attempt to *resolve* the issue, we will go on revisiting the
issue
> forever, with nothing but wasted energy to show for it.

Well, to paraphrase a well known leader, "the IETF, how many divisions?"
The gist of this comment is that someone developing a network
application protocol ought to somehow get a blessing from the IETF.
Reality check. Who got the IETF approval to deploy ICQ, Kazaa, or for
that matter HTTP?

If the Internet is so fragile that a poorly developed application can
break it, then the IETF response should not be to try control each
application. It has to be, design checks that can be implemented by
cooperating hosts and routers so that their neck of the Internet is in
good health!

-- Christian Huitema





From owner-ietf@ietf.org  Fri Oct 17 16:31:21 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22994
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 16:31:21 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAb1H-0003tX-VC
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 16:16:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAaxk-0001jt-Ay
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 16:12:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21990
	for <ietf@ietf.org>; Fri, 17 Oct 2003 16:12:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAaxi-0000kB-00
	for ietf@ietf.org; Fri, 17 Oct 2003 16:12:38 -0400
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAaxi-0000j2-00
	for ietf@ietf.org; Fri, 17 Oct 2003 16:12:38 -0400
Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57])
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id h9HJof109019;
	Fri, 17 Oct 2003 15:50:42 -0400
From: "bill" <bill@strahm.net>
To: "'Avri Doria'" <avri@acm.org>, <ietf@ietf.org>
Subject: RE: Sunday training classes at IETF58
Date: Fri, 17 Oct 2003 13:11:48 -0700
Message-ID: <004c01c394ea$e575da30$70d912c0@mobilebill>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <326F44A1-0092-11D8-897E-000393CC2112@acm.org>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Avri,

Some quick questions - 

Are these RSVP meetings ?

Can I forward this to my WG mailing list and suggest participation to
people that are interested ??? (ie. How big is the room you are
reserving ?)

Bill

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of Avri
Doria
Sent: Friday, October 17, 2003 4:08 AM
To: ietf@ietf.org
Subject: Sunday training classes at IETF58


In addition to the Newcomer's training and the security tutorial, the 
IETF sunday training schedule for Minneapolis will include two new 
sessions.

The first covers the editor's role in working with the WG and in 
producing RFCs.  This is a completely new course.  The session is open 
to both current editors and folks who think they may be interested in 
taking on an editorship, or co-editorship, at some point in the future.

The second is the WG chairs training course.  This is an extension of 
the course that has been given during  lunch sessions for WG chairs.  
This session is open to both current WG chairs and to anyone who thinks 
they may be interested in  chairing a WG.

The schedule for the courses is listed below.  There is no need to 
pre-register, just show up.

Thanks
a.


Sunday, November 10, 2003
=========================

1330-1430  Newcomers Training -- Salon B  (Scott Bradner)

     An introduction to the IETF for anyone who wants to know
     more about the IETF, specifically recommended for all new
     or recent IETF attendees. The session covers the IETF
     history, structure, and standards process. It also
     provides tips for success in the IETF environment.

1330-1500  Editor's Training -- Conrad C  (Avri Doria)

     Training for current or aspiring IETF document
     editors.  Covers the roles and responsibilities
     of a document editor, and includes advice on
     producing a high-quality IETF specification.

1330-1500  Intro WG Chairs Training -- Conrad B  (Margaret Wasserman)

     Introductory training for new or aspiring WG chairs.
     Covers the role and responsibilities of the WG chair,
     and includes advice on how to run a WG that is fair,
     open and productive.

1500-1700  Security Tutorial -- Salon B  (Radia Perlman)

     All IETF attendees need to be aware of the security
     implications of our design choices.  This session
     offers a basic primer in protocol security, as well
     as advice on how to write the Security Considerations
     sections required for all IETF documents.








From owner-ietf@ietf.org  Fri Oct 17 17:10:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24473
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 17:10:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAbZv-0006yo-EL
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 16:52:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAbIW-0006TJ-S8
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 16:34:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23198
	for <ietf@ietf.org>; Fri, 17 Oct 2003 16:33:59 -0400 (EDT)
From: Margaret.Wasserman@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAbIV-00019P-00
	for ietf@ietf.org; Fri, 17 Oct 2003 16:34:07 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAbIU-00019M-00
	for ietf@ietf.org; Fri, 17 Oct 2003 16:34:06 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9HKY6X02366
	for <ietf@ietf.org>; Fri, 17 Oct 2003 23:34:06 +0300 (EET DST)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6558ced2b2ac158f23076@esvir03nok.nokia.com>;
 Fri, 17 Oct 2003 23:34:06 +0300
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 17 Oct 2003 13:34:04 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Sunday training classes at IETF58
Date: Fri, 17 Oct 2003 16:34:03 -0400
Message-ID: <E320A8529CF07E4C967ECC2F380B0CF902443E1F@bsebe001.americas.nokia.com>
Thread-Topic: Sunday training classes at IETF58
Thread-Index: AcOU7bBOmKg2wMTGSqWiIgRu7HwuQgAABalQ
To: <bill@strahm.net>, <avri@acm.org>, <ietf@ietf.org>
X-OriginalArrivalTime: 17 Oct 2003 20:34:04.0816 (UTC) FILETIME=[01B34900:01C394EE]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable



Hi Bill,

> Are these RSVP meetings ?
>=20
> Can I forward this to my WG mailing list and suggest participation to
> people that are interested ??? (ie. How big is the room you are
> reserving ?)

No RSVPs are required.

All of the rooms will hold 100 or more people.  Given previous
attendance at Sunday afternoon classes, we think that this will
be adequate to allow everyone who is interested to attend any
of our courses.

Please feel free to forward this information to anyone who
you think may be interested.

Thanks,
Margaret



From owner-ietf@ietf.org  Fri Oct 17 19:31:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29446
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 19:31:39 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAdw2-0002bh-Fi
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 19:23:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAdvE-0002WR-27
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 19:22:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29285
	for <ietf@ietf.org>; Fri, 17 Oct 2003 19:22:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAdvC-0002oW-00
	for ietf@ietf.org; Fri, 17 Oct 2003 19:22:14 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAdvB-0002o0-00
	for ietf@ietf.org; Fri, 17 Oct 2003 19:22:13 -0400
Received: from vista.av8.net (vista.av8.net [130.105.36.10])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA07474;
	Fri, 17 Oct 2003 19:24:52 -0400
Date: Fri, 17 Oct 2003 19:20:25 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: Jeroen Massar <jeroen@unfix.org>
cc: ietf@ietf.org
Subject: RE: rfc1918 impact
In-Reply-To: <002801c393b4$b1aa4bf0$210d640a@unfix.org>
Message-ID: <Pine.LNX.4.44.0310171835520.12640-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

So far, DNSSEC doesn't solve this problem.  I don't think the reverse DNS
problem is intended to be solved by DNSSEC.

  Quick poll: Does anyone actually think that DNS can be made globably
invulnerable, and positively trusted, yet usable?

DNSSEC won't solve a number of problems of intentional false information.
It only works in cooperative environments, and is limited in many ways.
These limitations still make DNS generally untrustable, which makes in
inappropriate for logs and most other uses.  I don't think the
implementors expect it to be widely deployed, but useful in some special
cases.

Also, logs should definitely NOT be using reverse DNS.  This is one of the
many improper uses of Reverse DNS.  One must always log the IP address. If
you have a lot of extra time, and space in the log, the current value of
the reverse lookup may be interesting, but it it not meaningful.

Implementors are starting to get a clue:  I've noticed that the UTMP on
several platforms only stores the IP address for IPv6.  Many a breakin has
been hard or impossible to trace due to improper use of reverse DNS in
logging. Sometimes it is impossible to detect! How do you know that the
access from the_very_long_host.another_long_zone.some_doma---oops, out of
space for hostname--was unauthorized?  Anonymous Mail Relay abuse was made
possible because the early SMTP implmentors didn't put the IP address in
the Recieved header, but the reverse DNS, which we subsequently found out
to be useless.  Ironically, one of our current DNS chairs, Rob Austein,
argued against putting the IP address in the header in 1986,
unintentionally bringing us this scourge. I guess if you screw something
up bad enough, you get management (Sorry Rob ;-)  The BSD R-command
exploits are due to improper trust in reverse DNS.  The list goes on, and
includes _everthing_ (that I've heard of) except for traceroute, which is
using reverse DNS only for what amounts to transient pretty printing.
Transient, frivolous use, like in traceroute, is the only appopriate use
for reverse DNS.  All other use that I've seen so far is inappropriate,
and leads to a vulnerability of one sort or another.

Anyway, this is getting afield a little for the IETF list, and probably
belongs on one of the DNS lists.

Perhaps all that is important is to remember that "properly configured
Reverse DNS" includes having no reverse DNS at all.

		--Dean

On Thu, 16 Oct 2003, Jeroen Massar wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
>
> Dean Anderson wrote:
>
> > Reverse DNS is probably not going to be working or widely used in
> > IPV6, which has
> > an alternate ICMP host information query so that reverse DNS is not
> > necessary for the most useful purpose of reverse DNS: traceroute.
>
> I think you underestimate the 'power' of Reverse DNS.
> The primary reason that tunnelbrokers are so popular, with even
> the non-technical folks, is simply because of Reverse DNS :
>   - Reverse DNS gives a nice host on IRC -
>
> Ofcourse ICMP host information could solve that.
> But afaik there is no 'secure icmp host information' packet yet.
> And we are going to get at dnssec one day.
>
> Next to the vanity host usage of reverse dns there is also
> the usage for reverse dns in logs, reverse in 'who' output
> and probably many other reasons. Loganalyzing tools are
> another popular example of reverse dns usage. Ofcourse
> that can be solved too with icmp's, but icmp's don't work
> when the host in question is offline, ofcourse one is to
> wonder if the host is offline if the dns is not offline
> or that the IP is in use by another host etc...
> Next to that reverse usually matched forwards, if reverse
> is split from forward lookups there is going to be a difference.
>
> Greets,
>  Jeroen
>
> -----BEGIN PGP SIGNATURE-----
> Version: Unfix PGP for Outlook Alpha 13 Int.
> Comment: Jeroen Massar / jeroen@unfix.org / http://unfix.org/~jeroen/
>
> iQA/AwUBP45ElCmqKFIzPnwjEQKe7gCfT5/MWZ9pkkz9U+pnTYnUWKfuADcAn2wW
> YeRsiz6r6NDRD7X44km5KBko
> =t5WN
> -----END PGP SIGNATURE-----
>
>




From owner-ietf@ietf.org  Fri Oct 17 19:44:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00043
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 19:44:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAeBN-0003ZN-Ad
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 19:38:57 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAe9f-0003M4-Hx
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 19:37:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29788
	for <ietf@ietf.org>; Fri, 17 Oct 2003 19:37:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAe9d-0002zy-00
	for ietf@ietf.org; Fri, 17 Oct 2003 19:37:09 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAe9d-0002zH-00
	for ietf@ietf.org; Fri, 17 Oct 2003 19:37:09 -0400
Received: from vista.av8.net (vista.av8.net [130.105.36.10])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id TAA10675;
	Fri, 17 Oct 2003 19:38:59 -0400
Date: Fri, 17 Oct 2003 19:34:32 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: mark seery <m_seery@yahoo.com>
cc: ietf@ietf.org
Subject: Re: IESG proposed statement on the IETF mission
In-Reply-To: <3F8EBF0C.10505@yahoo.com>
Message-ID: <Pine.LNX.4.44.0310171923240.12640-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Thu, 16 Oct 2003, mark seery wrote:

> Trust model
> =========
>
> Inherent in Eric's problem statement is the notion that end systems have
> the ability to impact the experience other Internet users have. Whether
> this is the result of an historical trust model, where people using the
> Internet were assumed to a) have clue and b) be acting in the best
> interests of the community, or whether this is the result of other
> community values, this diserves comment/debate, IMHO.

I've noticed that the people who claim to have the most clue, frequently
don't, and the people who claim most to be acting in the interests of the
community, aren't.

Clue has to do with being right, and time always reveals who and what is
right.  It is not always immediately apparent who is right. But the one
with the "clue" will be shown to have been right later on.

Community has to do with democratic, common interests. It is always
interesting that the people who are most shrill about "the interests
community" often want to exclude most of the community from the decision.

Therein lies the problem.

		--Dean




From owner-ietf@ietf.org  Fri Oct 17 20:32:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01296
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 20:32:20 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAeuz-0005cZ-Iw
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 20:26:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAeji-0005P1-VF
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 20:14:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00954
	for <ietf@ietf.org>; Fri, 17 Oct 2003 20:14:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAejg-0003N8-00
	for ietf@ietf.org; Fri, 17 Oct 2003 20:14:24 -0400
Received: from coconut.itojun.org ([219.101.47.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAejf-0003N4-00
	for ietf@ietf.org; Fri, 17 Oct 2003 20:14:24 -0400
Received: from itojun.org (localhost [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP id 561C591
	for <ietf@ietf.org>; Sat, 18 Oct 2003 09:14:23 +0900 (JST)
To: ietf@ietf.org
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
From: itojun@iijlab.net
Subject: IAB concerns against permanent deployment of edge-based filtering
Date: Sat, 18 Oct 2003 09:14:22 +0900
Message-Id: <20031018001423.561C591@coconut.itojun.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

IAB concerns against permanent deployment of edge-based filtering


The IAB notes that there ISPs/ASes undertaking permanent deployment of
edge-based protocol number/port number packet filtering on traffic
received from eBGP peers.

As a short term response to security incidents this is a prudent
operational measure that limits the spread of various forms of attack, and
also mitigates some level of risk associated with network vulnerabilities.
For example, many ISPs installed temporary filters in response to a July
2003 security advisory for CISCO routers (
http://www.cert.org/advisories/CA-2003-15.html). In the case of this
incident PIM (protocol # 103) and mobile-ip4 (55) packets could trigger
the vulnerability. The operational community responded with widespread
deployment of filters at AS borders for these protocol numbers.  Because
of this, PIM and mobile-ip4 no longer work across such AS borders.

The IAB is concerned about the practice of the permanent deployment of
such traffic filters, since this could block the operation of certain
applications in current use, as well as limiting the potential for
deployment of future applications. Such filters ultimately limit
extensibility of the Internet protocol as well as the Internet itself.

It is an entirely appropriate and operationally prudent response to filter
at the AS border as a short term mitigation of various network
vulnerabilities. However, filters at AS borders do not provide any more
than a relatively short term mitigation, and certainly do not solve the
real problem of eliminating all forms of exploitation of such
vulnerabilities. Over time knowledge of a vulnerability spreads across
the network and potential exploiters of a vulnerability will be within an
ISP/AS as well as being on the outside. The only stable and appropriate
longer term operational response is to upgrade network equipment to
eliminate the vulnerability, rather than attempting to configure packet
filters intended to prevent externally located third parties from
exploiting it.

While short term traffic filters are deployed, the appropriate recommended
longer term action is to:

- To install filters to detect packets that are directed to the router
   itself to protect the router. (do not filter traffic that goes through
   the routers).

- To update router firmware to a version known to eliminate the
   vulnerability

Regards,

Jun-ichiro itojun Hagino, on behalf of IAB (iab@ietf.org)



From owner-ietf@ietf.org  Fri Oct 17 20:54:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01886
	for <ietf-web-archive@odin.ietf.org>; Fri, 17 Oct 2003 20:54:57 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAfK0-00070H-R9
	for ietf-list@asgard.ietf.org; Fri, 17 Oct 2003 20:51:56 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAfFI-0006p6-LL
	for ietf@asgard.ietf.org; Fri, 17 Oct 2003 20:47:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01788
	for <ietf@ietf.org>; Fri, 17 Oct 2003 20:46:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAfFG-0003f7-00
	for ietf@ietf.org; Fri, 17 Oct 2003 20:47:02 -0400
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAfFG-0003f4-00
	for ietf@ietf.org; Fri, 17 Oct 2003 20:47:02 -0400
Received: from limbo (limbo.unfix.org [3ffe:8114:2000:240:200:39ff:fe77:1f3f])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP id EB55B8311;
	Sat, 18 Oct 2003 02:46:57 +0200 (CEST)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Dean Anderson'" <dean@av8.com>
Cc: <ietf@ietf.org>
Subject: RE: rfc1918 impact
Date: Sat, 18 Oct 2003 02:46:25 +0200
Organization: Unfix
Message-ID: <00a401c39511$42cbeff0$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <Pine.LNX.4.44.0310171835520.12640-100000@vista.av8.net>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

Dean Anderson wrote:

> So far, DNSSEC doesn't solve this problem.  I don't think the 
> reverse DNS problem is intended to be solved by DNSSEC.

IMHO "reverse" is just the same as ordinary domains.
Where DNS is a phonebook for internet name mappings.

>   Quick poll: Does anyone actually think that DNS can be made globably
> invulnerable, and positively trusted, yet usable?

I trust on the word of Miek Gieben and as he says it is so, I
have to go with that it will be trusted and usable.

> DNSSEC won't solve a number of problems of intentional false 
> information.

You won't be able to 'spoof' anymore, which solves the
intentional false information part.

> It only works in cooperative environments, and is limited in 
> many ways.

Everything is based on cooperation, nobody is 'forced' to
implement a specification and people can invent their own etc.
You might want to followup to the dnssec-wg why you think it
is limited btw.

<SNIP>

> Also, logs should definitely NOT be using reverse DNS.  This 
> is one of the many improper uses of Reverse DNS.
> One must always log the IP address. If
> you have a lot of extra time, and space in the log, the 
> current value of the reverse lookup may be interesting,
> but it it not meaningful.
> Implementors are starting to get a clue:  I've noticed that 
> the UTMP on several platforms only stores the IP address for IPv6.
> Many a breakin has been hard or impossible to trace due to improper
> use of reverse DNS in logging.

I realize that all too well, unfortunatly some don't:
http://www.freebsd.org/cgi/query-pr.cgi?pr=22595
(Check the dates btw :)

They should log both the IP and the reverse.

> Sometimes it is impossible to detect! How do you 
> know that the access from 
> the_very_long_host.another_long_zone.some_doma---oops, out of
> space for hostname--was unauthorized?  Anonymous Mail Relay 
> abuse was made possible because the early SMTP implmentors
> didn't put the IP address in the Recieved header, but the
> reverse DNS, which we subsequently found out to be useless.

Reverses should be checked with the forward mapping ofcourse.
If both of these answers come in over DNSSEC then you are 100%
sure that this host has this name. But still one wants to
log the IP because DNS-TTL later the hostname is out of your
cache and possibly out of the entire DNS system.

> and includes _everthing_ (that I've heard of) except for 
> traceroute, which is using reverse DNS only for what amounts
> to transient pretty printing.

Traceroute doesn't check the forward beloning to a reverse
and I have seen an number of jokers using 'nice' hostnames
next to that there are very easy ways of spoofing traceroutes,
rotorouter anyone ?:)

> Anyway, this is getting afield a little for the IETF list, 
> and probably belongs on one of the DNS lists.

Ack.

> Perhaps all that is important is to remember that "properly configured
> Reverse DNS" includes having no reverse DNS at all.

Ack.

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook Alpha 13 Int.
Comment: Jeroen Massar / jeroen@unfix.org / http://unfix.org/~jeroen/

iQA/AwUBP5CNYCmqKFIzPnwjEQJwvACghPgsX8dPkJ6shPG7OGccdp5dDQQAnjpo
HWwqKUUDkL0M3xRa7kyCIO43
=rCiF
-----END PGP SIGNATURE-----




From owner-ietf@ietf.org  Sat Oct 18 00:44:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06956
	for <ietf-web-archive@odin.ietf.org>; Sat, 18 Oct 2003 00:44:00 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAihC-0006Z3-5p
	for ietf-list@asgard.ietf.org; Sat, 18 Oct 2003 00:28:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAigb-0006Uv-UF
	for ietf@asgard.ietf.org; Sat, 18 Oct 2003 00:27:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06398
	for <ietf@ietf.org>; Sat, 18 Oct 2003 00:27:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAigZ-0005MM-00
	for ietf@ietf.org; Sat, 18 Oct 2003 00:27:27 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAigY-0005LN-00
	for ietf@ietf.org; Sat, 18 Oct 2003 00:27:27 -0400
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 46B6E61F4A; Sat, 18 Oct 2003 06:26:56 +0200 (CEST)
Date: Fri, 17 Oct 2003 22:18:41 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org, problem-statement@alvestrand.no
Subject: Re: IESG proposed statement on the IETF mission
Message-ID: <36860662.1066429121@localhost>
In-Reply-To: <20031015124837.79dbcd11.moore@cs.utk.edu>
References: <157547561.1066175290@localhost>
 <20031015124837.79dbcd11.moore@cs.utk.edu>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

since both you and Scott pointed out this one....

--On 15. oktober 2003 12:48 -0400 Keith Moore <moore@cs.utk.edu> wrote:

>>    "The purpose of the IETF is to create high quality, relevant,
>>     and timely standards for the Internet."
>
> I actually believe IETF has a somewhat wider purpose than that.  What
> I usually say is "we're trying to help the Internet work better".

my personal belief is that the purpose of the *Internet technical 
community* is to make the Internet work better. But we have to admit to 
division of labor, and the part that we call the IETF needs to concentrate 
on standards, and the "supporting functions" of fora for experimentation 
and gathering of operational experience.

Others do the work of pulling fiber, designing routers, arresting spammers 
and detecting virii. We, gathered as the IETF, should not (IMHO) attempt to 
take over those functions. Despite the fact that it's what many of us do 
when we're not doing IETF stuff!

                Harald





From owner-ietf@ietf.org  Sat Oct 18 00:44:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06965
	for <ietf-web-archive@odin.ietf.org>; Sat, 18 Oct 2003 00:44:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAihB-0006Ym-OV
	for ietf-list@asgard.ietf.org; Sat, 18 Oct 2003 00:28:05 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAigY-0006Ur-3Q
	for ietf@asgard.ietf.org; Sat, 18 Oct 2003 00:27:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06374
	for <ietf@ietf.org>; Sat, 18 Oct 2003 00:27:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAigV-0005M6-00
	for ietf@ietf.org; Sat, 18 Oct 2003 00:27:23 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAigV-0005LJ-00
	for ietf@ietf.org; Sat, 18 Oct 2003 00:27:23 -0400
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id A6C7B61C20; Sat, 18 Oct 2003 06:26:51 +0200 (CEST)
Date: Fri, 17 Oct 2003 22:09:44 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Christian Huitema <huitema@windows.microsoft.com>
Cc: ietf@ietf.org, problem-statement@alvestrand.no
Subject: RE: IETF mission boundaries (Re: IESG proposed statement on the
 IETF mission )
Message-ID: <36324071.1066428584@localhost>
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA05B3E96D@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References:  <DAC3FCB50E31C54987CD10797DA511BA05B3E96D@WIN-MSG-10.wingroup.wi
 ndeploy.ntdev.microsoft.com>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Christian,

we might be looking through opposite ends of this tunnel.....

--On 16. oktober 2003 15:15 -0700 Christian Huitema 
<huitema@windows.microsoft.com> wrote:

>> I think this point is one of the critical causes of conflict when
> talking
>> about the IETF mission - and unless we lance the boil, actually talk
> about
>> it, and attempt to *resolve* the issue, we will go on revisiting the
> issue
>> forever, with nothing but wasted energy to show for it.
>
> Well, to paraphrase a well known leader, "the IETF, how many divisions?"
> The gist of this comment is that someone developing a network
> application protocol ought to somehow get a blessing from the IETF.
> Reality check. Who got the IETF approval to deploy ICQ, Kazaa, or for
> that matter HTTP?

For application protocols, I view it in the opposite direction - if someone 
comes to the IETF and *asks* for the IETF's advice, blessing or ownership, 
what are the conditions under which we say "yes"? Or "no"?

For those that never ask, and never become important, I say "not my 
problem". The number of application protocols with the oomph to "break" the 
Internet is quite small - offhand, I'd say that HTTP/1.0 probably was the 
closest try.

> If the Internet is so fragile that a poorly developed application can
> break it, then the IETF response should not be to try control each
> application. It has to be, design checks that can be implemented by
> cooperating hosts and routers so that their neck of the Internet is in
> good health!

Now there's an idea..... :-)

The flipside is of course with those things that are *already* under IETF 
control, or critical for our infrastructure, for some reason. The 
abstracted version of the fights over MIME types, URI schemes, SIP 
extension etcetera seems to be "don't extend until you've talked to us 
about what you're doing, and if we don't like it, don't try to pretend that 
we did" (the P-headers, vnd. MIME types and the proposed faceted URI 
schemes); I'm not certain what the abstracted version of the fights over 
COPS, CR-LDP, RSVP-TE and so on are.....

The IETF has got fewer divisions than the Pope, of course. Anyone is free 
to ignore us. And we need to remember that, sometimes.








From owner-ietf@ietf.org  Sat Oct 18 01:32:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06959
	for <ietf-web-archive@odin.ietf.org>; Sat, 18 Oct 2003 00:44:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAihC-0006ZK-Ha
	for ietf-list@asgard.ietf.org; Sat, 18 Oct 2003 00:28:06 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAigg-0006Uy-4D
	for ietf@asgard.ietf.org; Sat, 18 Oct 2003 00:27:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06402
	for <ietf@ietf.org>; Sat, 18 Oct 2003 00:27:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAigd-0005MS-00
	for ietf@ietf.org; Sat, 18 Oct 2003 00:27:31 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAigc-0005LU-00
	for ietf@ietf.org; Sat, 18 Oct 2003 00:27:30 -0400
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 9CBDD621B6; Sat, 18 Oct 2003 06:26:59 +0200 (CEST)
Date: Fri, 17 Oct 2003 22:27:14 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: erosen@cisco.com
Cc: ietf@ietf.org, problem-statement@alvestrand.no
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the
 IETF mission ) 
Message-ID: <37373730.1066429634@localhost>
In-Reply-To: <200310161715.h9GHF2FQ026610@rtp-core-2.cisco.com>
References:  <200310161715.h9GHF2FQ026610@rtp-core-2.cisco.com>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 16. oktober 2003 13:15 -0400 Eric Rosen <erosen@cisco.com> wrote:

>> - "For the Internet" - only the stuff that is directly involved in
>> making  the Internet work is included in the IETF's scope.
>
> In other words, routing,  DNS, and Internet operations/management.
> Adopting this as  the IETF's mission  would be a  very radical change
> indeed!

I erred in describing that category. I should have used something else - it 
was not what the IESG thought it was saying in its proposed mission 
statement, so me recycling the term "for the Internet" in the bulleted list 
I made added confusion rather than clarifying. Sorry!

(I still think it's a valid point on the scale. It leaves us with a much 
smaller IETF. But some people tend to think that's a positive side.)

                   Harald






From owner-ietf@ietf.org  Sat Oct 18 14:14:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04212
	for <ietf-web-archive@odin.ietf.org>; Sat, 18 Oct 2003 14:14:47 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAvED-0005pX-FP
	for ietf-list@asgard.ietf.org; Sat, 18 Oct 2003 13:51:01 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAvDm-0005nf-Lm
	for ietf@asgard.ietf.org; Sat, 18 Oct 2003 13:50:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03601
	for <ietf@ietf.org>; Sat, 18 Oct 2003 13:50:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAvDl-0003m6-00
	for ietf@ietf.org; Sat, 18 Oct 2003 13:50:33 -0400
Received: from smtp011.mail.yahoo.com ([216.136.173.31])
	by ietf-mx with smtp (Exim 4.12)
	id 1AAvDk-0003m2-00
	for ietf@ietf.org; Sat, 18 Oct 2003 13:50:32 -0400
Received: from ts46-01-qdr3166.mrgnhll.ca.charter.com (HELO yahoo.com) (m?seery@68.118.70.100 with plain)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 18 Oct 2003 17:50:31 -0000
Message-ID: <3F917D7A.5090609@yahoo.com>
Date: Sat, 18 Oct 2003 10:50:50 -0700
From: mark seery <m_seery@yahoo.com>
Reply-To: m_seery@yahoo.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: ietf@ietf.org
Subject: Re: IESG proposed statement on the IETF mission
References: <Pine.LNX.4.44.0310171923240.12640-100000@vista.av8.net>
In-Reply-To: <Pine.LNX.4.44.0310171923240.12640-100000@vista.av8.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dean Anderson wrote:

>On Thu, 16 Oct 2003, mark seery wrote:
>
>  
>
>>Trust model
>>=========
>>
>>Inherent in Eric's problem statement is the notion that end systems have
>>the ability to impact the experience other Internet users have. Whether
>>this is the result of an historical trust model, where people using the
>>Internet were assumed to a) have clue and b) be acting in the best
>>interests of the community, or whether this is the result of other
>>community values, this diserves comment/debate, IMHO.
>>    
>>
>
>I've noticed that the people who claim to have the most clue, frequently
>don't,
>
"...most imposters are desperate to prove that they are not what they 
are..." - Katherine Hepburn, Love Story

that said, no one has clue in everything, and in almost any one thing, 
there is almost always some one with more clue, so this too is relative.

>and the people who claim most to be acting in the interests of the
>community, aren't.
>
"Patriotism is the last refuge of a scoundrel."  - Samuel Johnson.

that said there is a lot that is instructive about listening to the 
ghosts from the past. lessons in open processes as an immutable value 
for example.

>
>Clue has to do with being right, and time always reveals who and what is
>right.  It is not always immediately apparent who is right. But the one
>with the "clue" will be shown to have been right later on
>
But the assasination has usually taken place by then. The lesson of 
almost any complex society is dare to be different, and the gods will 
exact their revenge. It takes people of courage, stupidty or independent 
wealth to truly express what they think. That is why secret ballots 
exist in many democracies - it allows a broader range of non-stupid 
people to express their opinion (all beit on a narrow decision criteria).

>Community has to do with democratic, common interests. It is always
>interesting that the people who are most shrill about "the interests
>community" often want to exclude most of the community from the decision.
>
Common interests I agree, which I think is probably the crux of the 
mission discussion. Whether a "statement" or any other single instrument 
is sufficient to cross this bridge is fair game for discussion. But 
undoubtely, IMHO, it is the definition, articulation, and recognition of 
what the common interest is that is the problem at hand. For example, I 
don't think IEEE 802.3 have any problems understanding what their common 
interest is - the propogation of Ethernet technology - with no qualms 
about the commercial realities of that common interest.

What is the common interest of the IETF? Packets to the people? The 
propogation and use of IP (including Eric's expression of migrating 
applications from other technologies)? The refinement and perfection of 
connectionless networking techology? The development/standardization of 
technologies that address as many networking problem spaces as possible 
forming an umbrella under which we can throw many things by calling it 
the "Internet"?

So yes Dean, I think you elude to the central issue - what is the common 
interest, and as the community was propelled almost forceably, and 
inexorably by market forces from a world where as Randy put it 
"operators cooperated" together, in a non-commercial endeavor based on 
very non-commercial values, into a very commercial world, did the 
community ever have a chance to take a big breath, inspect what has 
happened, and where it really wants to go from here.

Given the seeminly overloaded semantics of "mission" perhaps a statement 
of "common interest" would indeed be more beneficial.

As for the democratic bit, I have been giving a lot of thought recently 
to what a democracy is or should be - as such I am not sure what 
democratic is, so I leave that piece as an exercise to the reader.

Best,......





From owner-ietf@ietf.org  Sat Oct 18 16:17:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08288
	for <ietf-web-archive@odin.ietf.org>; Sat, 18 Oct 2003 16:17:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AAxKq-0001kV-SG
	for ietf-list@asgard.ietf.org; Sat, 18 Oct 2003 16:06:00 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AAxJt-0001if-Hv
	for ietf@asgard.ietf.org; Sat, 18 Oct 2003 16:05:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08122
	for <ietf@ietf.org>; Sat, 18 Oct 2003 16:04:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAxJs-0005sh-00
	for ietf@ietf.org; Sat, 18 Oct 2003 16:05:00 -0400
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1AAxJr-0005sd-00
	for ietf@ietf.org; Sat, 18 Oct 2003 16:04:59 -0400
Received: (qmail 52215 invoked by uid 1013); 18 Oct 2003 20:04:58 -0000
Date: Sat, 18 Oct 2003 22:04:58 +0200
From: Markus Stumpf <maex-lists-ietf-general@Space.Net>
To: Dean Anderson <dean@av8.com>
Cc: Jeroen Massar <jeroen@unfix.org>, ietf@ietf.org
Subject: Re: rfc1918 impact
Message-ID: <20031018200458.GG25145@Space.Net>
References: <002801c393b4$b1aa4bf0$210d640a@unfix.org> <Pine.LNX.4.44.0310171835520.12640-100000@vista.av8.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0310171835520.12640-100000@vista.av8.net>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, Oct 17, 2003 at 07:20:25PM -0400, Dean Anderson wrote:
> Perhaps all that is important is to remember that "properly configured
> Reverse DNS" includes having no reverse DNS at all.

Reverse DNS is just a zone in the in-addr.arpa domain. And there is more
to reverse DNS than just a untrustworthy PTR record.

	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"



From owner-ietf@ietf.org  Sun Oct 19 19:25:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22933
	for <ietf-web-archive@odin.ietf.org>; Sun, 19 Oct 2003 19:25:03 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ABMZX-0006YT-8a
	for ietf-list@asgard.ietf.org; Sun, 19 Oct 2003 19:02:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ABMZ6-0006Xy-4r
	for ietf@asgard.ietf.org; Sun, 19 Oct 2003 19:02:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22657
	for <ietf@ietf.org>; Sun, 19 Oct 2003 19:02:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABMZ4-0001B5-00
	for ietf@ietf.org; Sun, 19 Oct 2003 19:02:22 -0400
Received: from [130.105.12.4] (helo=citation.av8.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABMZ4-0001B2-00
	for ietf@ietf.org; Sun, 19 Oct 2003 19:02:22 -0400
Received: from vista.av8.net (vista.av8.net [130.105.36.10])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id SAA01681;
	Sun, 19 Oct 2003 18:57:02 -0400
Date: Sun, 19 Oct 2003 18:52:37 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@vista.av8.net
To: mark seery <m_seery@yahoo.com>
cc: ietf@ietf.org
Subject: Re: IESG proposed statement on the IETF mission
In-Reply-To: <3F917D7A.5090609@yahoo.com>
Message-ID: <Pine.LNX.4.44.0310191747040.21976-100000@vista.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

> So yes Dean, I think you elude to the central issue - what is the common
> interest, and as the community was propelled almost forceably, and
> inexorably by market forces from a world where as Randy put it
> "operators cooperated" together, in a non-commercial endeavor based on
> very non-commercial values, into a very commercial world, did the
> community ever have a chance to take a big breath, inspect what has
> happened, and where it really wants to go from here.

Ok, here is MY opinion on the central issue:

Deployed communications systems are either military or commercial. Pure
research doesn't deploy systems.  OC-192 equipment and millions of miles
of fiber aren't cheap. Those complaining about how great things were when
they were non-commercial were preceeded by people complaining about
working for the military.

The people who don't want to service the commercial sector, and don't want
to service the military sector, really don't realistically have much of a
place in our society outside of pure research, and shouldn't be given
control over the future commercial or military applications of the
internet.

But it comes down to a question of whether science serves public policy or
whether public policy serves science. Which is the tail, and which is the
dog?  There is room for some pure science for nothing other than the sake
of pure science, but most of the research has to be done for productive
commercial or military purposes. I think this is a pretty general
statement that is as true of biotech research as it is of communications
research.  And since the internet is now vastly commercial, and
international, the leaders of the IETF ought to focus research on things
that will be commercially useful.

The present situation, in my opinion, the tail is wagging the dog.  This
should be changed.  The IETF mission should make clear what the
constituencies are, what the goals are, and what the priorities are, so
that the tail does the wagging.

It used to be that engineering and operations within a company "cooperated
together", sharing work and, of course, passwords. In small companies,
this is still be true.  But in many large telecom companies, engineering
is denied access to the production systems, and only the operations staff
can make changes.  This is necessary to ensure commercial stability, since
custom engineering changes don't scale well, and don't lead to widely
stable systems, since the custom changes may not be made on all systems.

Large groups work at arms length, even within a company, with well defined
protocols and policies regarding who can do what. Of course, there are
inevitable disagreements between engineering, operations, sales, etc.
These are resolved civilly, within the organization, and may include
appeals to senior management.  Those that know me, know that I'm usually
working in the engineering group, which means I am sometimes arguing with
the operations group for access to a newly deployed production system. The
first few times, I usually win. But I either have to stop asking or lose
these disgreements, in favor of documented troubleshooting procedures for
the benefit of improved stability. There are good reasons that practices
that might have been nice for small companies are abandoned by big
companies.  The IETF has this same issue.

Clearly, there are going to be even greater problems when many companies
come together to work on the same problems.  It is not reasonable to
expect that a few people can just "cooperate together" and work something
out for a large community.  What worked for the Internet many years ago
isn't going to work again--ever again--anymore than it would work for a
large telecom company to share passwords between engineering and
operations.

		--Dean






From owner-ietf@ietf.org  Sun Oct 19 21:27:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25301
	for <ietf-web-archive@odin.ietf.org>; Sun, 19 Oct 2003 21:27:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ABOgB-0008Gq-Uh
	for ietf-list@asgard.ietf.org; Sun, 19 Oct 2003 21:17:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ABOfq-0008GH-If
	for ietf@asgard.ietf.org; Sun, 19 Oct 2003 21:17:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25010
	for <ietf@ietf.org>; Sun, 19 Oct 2003 21:17:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABOfo-0002DO-00
	for ietf@ietf.org; Sun, 19 Oct 2003 21:17:28 -0400
Received: from 94.180.32.202.ts.2iij.net ([202.32.180.94] helo=mail.64translator.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABOfn-0002DF-00
	for ietf@ietf.org; Sun, 19 Oct 2003 21:17:27 -0400
Received: from bahamas.64translator.com ([10.21.32.3])
	by mail.64translator.com (8.12.6p3/8.12.6) with ESMTP id h9K1GlZo042682
	for <ietf@ietf.org>; Mon, 20 Oct 2003 10:16:48 +0900 (JST)
	(envelope-from Yukiyo.Akisada@jp.yokogawa.com)
Received: from localhost (dhcp154.64translator.com [10.21.32.154])
	by bahamas.64translator.com (8.12.9/8.12.9) with SMTP id h9K1Gf4d012280
	for <ietf@ietf.org>; Mon, 20 Oct 2003 10:16:42 +0900 (JST)
Date: Mon, 20 Oct 2003 10:16:38 +0900
From: Yukiyo Akisada <Yukiyo.Akisada@jp.yokogawa.com>
To: ietf@ietf.org
Subject: 5th TAHI event announcement
Message-Id: <20031020101638.5599ce29.Yukiyo.Akisada@jp.yokogawa.com>
Organization: Yokogawa Electric Corporation
X-Mailer: Sylpheed version 0.8.3 (GTK+ 1.2.10; i386-portbld-freebsd4.7)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi all.

I'm pleased to be able to announce the next TAHI IPv6 test event.

The 5th TAHI IPv6 Interoperability Test Event will be held
19-23 January, 2004 at Makuhari, Chiba, JAPAN.

This time we are focusing on following items.

    * IPv6 Ready Logo Phase-1
    * MIPv6 ID-24
    * SIP (terminal test)
    * IPv6 Core Protocol
    * IPsec
    * Prefix Delegation
    * Default Address Selection
    * Default Router Preference

For more details, please visit our web site.

    * TAHI Project Home Page
        http://www.tahi.org/

    * "5th TAHI IPv6 Interoperability Test Event" announcement.
        http://www.tahi.org/inop/5thinterop.html

# I'm sorry if you have already receive this mail.
 
Thanks.

----
Yukiyo Akisada <Yukiyo.Akisada@jp.yokogawa.com>



From owner-ietf@ietf.org  Sun Oct 19 22:11:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26622
	for <ietf-web-archive@odin.ietf.org>; Sun, 19 Oct 2003 22:11:40 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ABPRb-0001er-RI
	for ietf-list@asgard.ietf.org; Sun, 19 Oct 2003 22:06:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ABPRC-0001eA-SX
	for ietf@asgard.ietf.org; Sun, 19 Oct 2003 22:06:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26499
	for <ietf@ietf.org>; Sun, 19 Oct 2003 22:06:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABPRA-0002hD-00
	for ietf@ietf.org; Sun, 19 Oct 2003 22:06:24 -0400
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABPRA-0002hA-00
	for ietf@ietf.org; Sun, 19 Oct 2003 22:06:24 -0400
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 1B70A14138; Sun, 19 Oct 2003 22:06:25 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 17606-03; Sun, 19 Oct 2003 22:06:24 -0400 (EDT)
Received: from envy.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id DC443140AB; Sun, 19 Oct 2003 22:06:23 -0400 (EDT)
Date: Sun, 19 Oct 2003 22:02:29 -0400
From: Keith Moore <moore@cs.utk.edu>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: moore@cs.utk.edu, huitema@windows.microsoft.com, ietf@ietf.org,
        problem-statement@alvestrand.no
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the
 IETF mission )
Message-Id: <20031019220229.2cdc63dc.moore@cs.utk.edu>
In-Reply-To: <36324071.1066428584@localhost>
References: <DAC3FCB50E31C54987CD10797DA511BA05B3E96D@WIN-MSG-10.wingroup.wi
 ndeploy.ntdev.microsoft.com>
	<36324071.1066428584@localhost>
X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> The number of application protocols with the oomph to "break" the 
> Internet is quite small

however, it's not safe to assume that it's zero.  any new killer app that were
poorly designed could do it.

also, you might be underestimating the damage done by HTTP (1.0 or later).



From owner-ietf@ietf.org  Sun Oct 19 22:51:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27451
	for <ietf-web-archive@odin.ietf.org>; Sun, 19 Oct 2003 22:51:09 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ABQ0Q-0002UG-Rb
	for ietf-list@asgard.ietf.org; Sun, 19 Oct 2003 22:42:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ABPyJ-0002SZ-5X
	for ietf@asgard.ietf.org; Sun, 19 Oct 2003 22:40:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27200
	for <ietf@ietf.org>; Sun, 19 Oct 2003 22:40:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABPyH-0002ww-00
	for ietf@ietf.org; Sun, 19 Oct 2003 22:40:37 -0400
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABPyG-0002wj-00
	for ietf@ietf.org; Sun, 19 Oct 2003 22:40:36 -0400
Received: from dfnjgl21 (12-237-229-250.client.attbi.com[12.237.229.250])
          by comcast.net (rwcrmhc12) with SMTP
          id <200310200240060140072s8ke>
          (Authid: sdawkins@comcast.net);
          Mon, 20 Oct 2003 02:40:06 +0000
Message-ID: <046a01c396b3$7c47d2a0$0400a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf@ietf.org>, <problem-statement@alvestrand.no>
References: <DAC3FCB50E31C54987CD10797DA511BA05B3E96D@WIN-MSG-10.wingroup.wi ndeploy.ntdev.microsoft.com><36324071.1066428584@localhost> <20031019220229.2cdc63dc.moore@cs.utk.edu>
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the IETF mission )
Date: Sun, 19 Oct 2003 21:40:11 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

 > The number of application protocols with the oomph to "break" the
> Internet is quite small

OK, I've gotta ask - how many times do we break the Internet before we
reverse this reasoning? (How many times is "too many"?)

(signed) curious






From owner-ietf@ietf.org  Mon Oct 20 11:56:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01543
	for <ietf-web-archive@odin.ietf.org>; Mon, 20 Oct 2003 11:56:06 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ABcC9-0008SR-Q2
	for ietf-list@asgard.ietf.org; Mon, 20 Oct 2003 11:43:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ABcBD-0008RR-Gi
	for ietf@asgard.ietf.org; Mon, 20 Oct 2003 11:42:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01194
	for <ietf@ietf.org>; Mon, 20 Oct 2003 11:42:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABcBC-0001Wq-00
	for ietf@ietf.org; Mon, 20 Oct 2003 11:42:46 -0400
Received: from mtiwmhc12.worldnet.att.net ([204.127.131.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABcBC-0001Wb-00
	for ietf@ietf.org; Mon, 20 Oct 2003 11:42:46 -0400
Received: from bolaba (117.sanjose-08-09rs16rt.ca.dial-access.att.net[12.81.3.117])
          by worldnet.att.net (mtiwmhc12) with SMTP
          id <2003102015421311200ik72ve>; Mon, 20 Oct 2003 15:42:14 +0000
Message-ID: <001901c39720$21548240$010aff0a@bolaba>
From: "todd glassey" <todd.glassey@worldnet.att.net>
To: "Spencer Dawkins" <spencer@mcsr-labs.org>, <ietf@ietf.org>,
        <problem-statement@alvestrand.no>
References: <DAC3FCB50E31C54987CD10797DA511BA05B3E96D@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com><36324071.1066428584@localhost><20031019220229.2cdc63dc.moore@cs.utk.edu> <046a01c396b3$7c47d2a0$0400a8c0@DFNJGL21>
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on theIETF mission )
Date: Mon, 20 Oct 2003 08:37:51 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Spencer, this is not intended at you personally but rather at the whole IETF
and this WG in particular. So let me ask then - What makes you think *you*
or anyone else here has any say as to what is or is not routed on the
Internet. ***YOU DON'T***  also as to "what breaks the Internet" - You don't
there too. None of us do.

And in fact NO ONE PERSON has any possible say as to the US internet except
the person running DHS and if you doubt this - try arguing with them.

BTW - The biggest thing the IETF can do is to get off the concept of "that
its wares and efforts" only pertain to the Internet. Because they don't -
obviously so too, and this is a key issue. If the IETF's actions only
pertained to the Internet and there was such a quantifiable thing as the
Internet then this might have some meaning - but its a fantasy that the IESG
likes to propagate to justify its existence.

Sorry if the truth hurts - but it is what it is.

Todd

----- Original Message ----- 
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf@ietf.org>; <problem-statement@alvestrand.no>
Sent: Sunday, October 19, 2003 7:40 PM
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on theIETF
mission )


> > The number of application protocols with the oomph to "break" the
> > Internet is quite small
>
> OK, I've gotta ask - how many times do we break the Internet before we
> reverse this reasoning? (How many times is "too many"?)
>
> (signed) curious
>
>
>




From owner-ietf@ietf.org  Mon Oct 20 19:28:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13531
	for <ietf-web-archive@odin.ietf.org>; Mon, 20 Oct 2003 19:28:01 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ABj7N-00031I-Bv
	for ietf-list@asgard.ietf.org; Mon, 20 Oct 2003 19:07:17 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ABimC-0001tw-NT
	for ietf@asgard.ietf.org; Mon, 20 Oct 2003 18:45:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12151
	for <ietf@ietf.org>; Mon, 20 Oct 2003 18:45:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABimA-0002lm-00
	for ietf@ietf.org; Mon, 20 Oct 2003 18:45:22 -0400
Received: from lakehearnglobal.coxinc.com ([206.157.224.254] helo=hatl0ms21.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABimA-0002lb-00
	for ietf@ietf.org; Mon, 20 Oct 2003 18:45:22 -0400
Received: from catl0ms22.corp.cox.com ([10.62.200.101]) by hatl0ms21.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 20 Oct 2003 18:44:52 -0400
Received: from mail pickup service by catl0ms22.corp.cox.com with Microsoft SMTPSVC;
	 Mon, 20 Oct 2003 18:28:33 -0400
Received: from hatl0ms22.CORP.COX.COM ([10.62.201.69]) by catl0ms22.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 20 Oct 2003 12:02:46 -0400
Received: from bastion.cox.com ([10.230.2.65]) by hatl0ms22.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 20 Oct 2003 12:02:46 -0400
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion.cox.com (8.11.7p1+Sun/8.11.6) with SMTP id h9KG2jr07008;
	Mon, 20 Oct 2003 12:02:45 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ABcC9-0008SR-Q2
	for ietf-list@asgard.ietf.org; Mon, 20 Oct 2003 11:43:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ABcBD-0008RR-Gi
	for ietf@asgard.ietf.org; Mon, 20 Oct 2003 11:42:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01194
	for <ietf@ietf.org>; Mon, 20 Oct 2003 11:42:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABcBC-0001Wq-00
	for ietf@ietf.org; Mon, 20 Oct 2003 11:42:46 -0400
Received: from mtiwmhc12.worldnet.att.net ([204.127.131.116])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABcBC-0001Wb-00
	for ietf@ietf.org; Mon, 20 Oct 2003 11:42:46 -0400
Received: from bolaba (117.sanjose-08-09rs16rt.ca.dial-access.att.net[12.81.3.117])
          by worldnet.att.net (mtiwmhc12) with SMTP
          id <2003102015421311200ik72ve>; Mon, 20 Oct 2003 15:42:14 +0000
Message-ID: <001901c39720$21548240$010aff0a@bolaba>
From: "todd glassey" <todd.glassey@worldnet.att.net>
To: "Spencer Dawkins" <spencer@mcsr-labs.org>, <ietf@ietf.org>,
        <problem-statement@alvestrand.no>
References: <DAC3FCB50E31C54987CD10797DA511BA05B3E96D@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com><36324071.1066428584@localhost><20031019220229.2cdc63dc.moore@cs.utk.edu> <046a01c396b3$7c47d2a0$0400a8c0@DFNJGL21>
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on theIETF mission )
Date: Mon, 20 Oct 2003 08:37:51 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Oct 2003 16:02:46.0461 (UTC) FILETIME=[9A48AED0:01C39723]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Spencer, this is not intended at you personally but rather at the whole IETF
and this WG in particular. So let me ask then - What makes you think *you*
or anyone else here has any say as to what is or is not routed on the
Internet. ***YOU DON'T***  also as to "what breaks the Internet" - You don't
there too. None of us do.

And in fact NO ONE PERSON has any possible say as to the US internet except
the person running DHS and if you doubt this - try arguing with them.

BTW - The biggest thing the IETF can do is to get off the concept of "that
its wares and efforts" only pertain to the Internet. Because they don't -
obviously so too, and this is a key issue. If the IETF's actions only
pertained to the Internet and there was such a quantifiable thing as the
Internet then this might have some meaning - but its a fantasy that the IESG
likes to propagate to justify its existence.

Sorry if the truth hurts - but it is what it is.

Todd

----- Original Message ----- 
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf@ietf.org>; <problem-statement@alvestrand.no>
Sent: Sunday, October 19, 2003 7:40 PM
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on theIETF
mission )


> > The number of application protocols with the oomph to "break" the
> > Internet is quite small
>
> OK, I've gotta ask - how many times do we break the Internet before we
> reverse this reasoning? (How many times is "too many"?)
>
> (signed) curious
>
>
>





From owner-ietf@ietf.org  Mon Oct 20 21:18:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17286
	for <ietf-web-archive@odin.ietf.org>; Mon, 20 Oct 2003 21:18:59 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ABkmP-0001jd-H9
	for ietf-list@asgard.ietf.org; Mon, 20 Oct 2003 20:53:45 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ABklb-0001fg-1d
	for ietf@asgard.ietf.org; Mon, 20 Oct 2003 20:52:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16439
	for <ietf@ietf.org>; Mon, 20 Oct 2003 20:52:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABklY-0004li-00
	for ietf@ietf.org; Mon, 20 Oct 2003 20:52:52 -0400
Received: from [206.157.230.254] (helo=hatl0ms22.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABklY-0004l2-00
	for ietf@ietf.org; Mon, 20 Oct 2003 20:52:52 -0400
Received: from catl0ms23.corp.cox.com ([10.64.200.46]) by hatl0ms22.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 20 Oct 2003 20:52:19 -0400
Received: from mail pickup service by catl0ms23.corp.cox.com with Microsoft SMTPSVC;
	 Mon, 20 Oct 2003 20:44:17 -0400
Received: from hatl0ms22.CORP.COX.COM ([10.62.201.69]) by catl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Sun, 19 Oct 2003 22:52:51 -0400
Received: from bastion.cox.com ([10.230.2.65]) by hatl0ms22.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Sun, 19 Oct 2003 22:52:51 -0400
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion.cox.com (8.11.7p1+Sun/8.11.6) with SMTP id h9K2qor07982;
	Sun, 19 Oct 2003 22:52:50 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ABQ0Q-0002UG-Rb
	for ietf-list@asgard.ietf.org; Sun, 19 Oct 2003 22:42:50 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ABPyJ-0002SZ-5X
	for ietf@asgard.ietf.org; Sun, 19 Oct 2003 22:40:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27200
	for <ietf@ietf.org>; Sun, 19 Oct 2003 22:40:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABPyH-0002ww-00
	for ietf@ietf.org; Sun, 19 Oct 2003 22:40:37 -0400
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABPyG-0002wj-00
	for ietf@ietf.org; Sun, 19 Oct 2003 22:40:36 -0400
Received: from dfnjgl21 (12-237-229-250.client.attbi.com[12.237.229.250])
          by comcast.net (rwcrmhc12) with SMTP
          id <200310200240060140072s8ke>
          (Authid: sdawkins@comcast.net);
          Mon, 20 Oct 2003 02:40:06 +0000
Message-ID: <046a01c396b3$7c47d2a0$0400a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf@ietf.org>, <problem-statement@alvestrand.no>
References: <DAC3FCB50E31C54987CD10797DA511BA05B3E96D@WIN-MSG-10.wingroup.wi ndeploy.ntdev.microsoft.com><36324071.1066428584@localhost> <20031019220229.2cdc63dc.moore@cs.utk.edu>
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the IETF mission )
Date: Sun, 19 Oct 2003 21:40:11 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Oct 2003 02:52:51.0455 (UTC) FILETIME=[40A8B0F0:01C396B5]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

 > The number of application protocols with the oomph to "break" the
> Internet is quite small

OK, I've gotta ask - how many times do we break the Internet before we
reverse this reasoning? (How many times is "too many"?)

(signed) curious







From owner-ietf@ietf.org  Tue Oct 21 01:02:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22664
	for <ietf-web-archive@odin.ietf.org>; Tue, 21 Oct 2003 01:02:34 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ABoSk-00083f-A1
	for ietf-list@asgard.ietf.org; Tue, 21 Oct 2003 00:49:42 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ABoS2-00082Q-CK
	for ietf@asgard.ietf.org; Tue, 21 Oct 2003 00:48:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22463
	for <ietf@ietf.org>; Tue, 21 Oct 2003 00:48:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABoS0-0006sA-00
	for ietf@ietf.org; Tue, 21 Oct 2003 00:48:56 -0400
Received: from lakehearnglobal.coxinc.com ([206.157.224.254] helo=hatl0ms21.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABoRz-0006rx-00
	for ietf@ietf.org; Tue, 21 Oct 2003 00:48:55 -0400
Received: from catl0ms23.corp.cox.com ([10.64.200.46]) by hatl0ms21.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 21 Oct 2003 00:48:21 -0400
Received: from mail pickup service by catl0ms23.corp.cox.com with Microsoft SMTPSVC;
	 Tue, 21 Oct 2003 00:31:12 -0400
Received: from hatl0ms22.CORP.COX.COM ([10.62.201.69]) by catl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Sun, 19 Oct 2003 21:29:28 -0400
Received: from bastion.cox.com ([10.230.2.65]) by hatl0ms22.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Sun, 19 Oct 2003 21:29:28 -0400
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion.cox.com (8.11.7p1+Sun/8.11.6) with SMTP id h9K1TSr02784;
	Sun, 19 Oct 2003 21:29:28 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ABOgB-0008Gq-Uh
	for ietf-list@asgard.ietf.org; Sun, 19 Oct 2003 21:17:51 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ABOfq-0008GH-If
	for ietf@asgard.ietf.org; Sun, 19 Oct 2003 21:17:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25010
	for <ietf@ietf.org>; Sun, 19 Oct 2003 21:17:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABOfo-0002DO-00
	for ietf@ietf.org; Sun, 19 Oct 2003 21:17:28 -0400
Received: from 94.180.32.202.ts.2iij.net ([202.32.180.94] helo=mail.64translator.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABOfn-0002DF-00
	for ietf@ietf.org; Sun, 19 Oct 2003 21:17:27 -0400
Received: from bahamas.64translator.com ([10.21.32.3])
	by mail.64translator.com (8.12.6p3/8.12.6) with ESMTP id h9K1GlZo042682
	for <ietf@ietf.org>; Mon, 20 Oct 2003 10:16:48 +0900 (JST)
	(envelope-from Yukiyo.Akisada@jp.yokogawa.com)
Received: from localhost (dhcp154.64translator.com [10.21.32.154])
	by bahamas.64translator.com (8.12.9/8.12.9) with SMTP id h9K1Gf4d012280
	for <ietf@ietf.org>; Mon, 20 Oct 2003 10:16:42 +0900 (JST)
Date: Mon, 20 Oct 2003 10:16:38 +0900
From: Yukiyo Akisada <Yukiyo.Akisada@jp.yokogawa.com>
To: ietf@ietf.org
Subject: 5th TAHI event announcement
Message-Id: <20031020101638.5599ce29.Yukiyo.Akisada@jp.yokogawa.com>
Organization: Yokogawa Electric Corporation
X-Mailer: Sylpheed version 0.8.3 (GTK+ 1.2.10; i386-portbld-freebsd4.7)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Oct 2003 01:29:28.0737 (UTC) FILETIME=[9ACE8110:01C396A9]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi all.

I'm pleased to be able to announce the next TAHI IPv6 test event.

The 5th TAHI IPv6 Interoperability Test Event will be held
19-23 January, 2004 at Makuhari, Chiba, JAPAN.

This time we are focusing on following items.

    * IPv6 Ready Logo Phase-1
    * MIPv6 ID-24
    * SIP (terminal test)
    * IPv6 Core Protocol
    * IPsec
    * Prefix Delegation
    * Default Address Selection
    * Default Router Preference

For more details, please visit our web site.

    * TAHI Project Home Page
        http://www.tahi.org/

    * "5th TAHI IPv6 Interoperability Test Event" announcement.
        http://www.tahi.org/inop/5thinterop.html

# I'm sorry if you have already receive this mail.
 
Thanks.

----
Yukiyo Akisada <Yukiyo.Akisada@jp.yokogawa.com>




From owner-ietf@ietf.org  Tue Oct 21 19:45:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19520
	for <ietf-web-archive@odin.ietf.org>; Tue, 21 Oct 2003 19:45:31 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AC5P6-0007Ok-BE
	for ietf-list@asgard.ietf.org; Tue, 21 Oct 2003 18:55:04 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AC4Ki-0001Rc-7I
	for ietf@asgard.ietf.org; Tue, 21 Oct 2003 17:46:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12212;
	Tue, 21 Oct 2003 17:46:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC4Kg-00036p-00; Tue, 21 Oct 2003 17:46:26 -0400
Received: from coconut.itojun.org ([219.101.47.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC4Ke-00036g-00; Tue, 21 Oct 2003 17:46:25 -0400
Received: by coconut.itojun.org (Postfix, from userid 1001)
	id CDE5D9C; Wed, 22 Oct 2003 06:46:23 +0900 (JST)
To: hinden@iprg.nokia.com
Cc: Radia Perlman <radia.perlman@sun.com>,
        Mukesh Gupta <Mukesh.Gupta@nokia.com>, vrrp@ietf.org, ietf@ietf.org
Subject: Re: draft-ietf-vrrp-ipv6-spec-05.txt lacks IPR clause
X-Mailer: Cue version 0.6 (031002-0709/itojun)
Mime-Version: 1.0
References: <20031015014322.308B890@coconut.itojun.org>
Cc: itojun@itojun.org
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20031021214623.CDE5D9C@coconut.itojun.org>
Date: Wed, 22 Oct 2003 06:46:23 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
Sender: owner-ietf@ietf.org
Precedence: bulk

	btw, KAME have removed VRRP6 implementation from the distribution
	because of the IPR statement (it conflicts with our policy about
	IPR).  there's ongoing work called "carp" which is specifically
	designed to avoid infringing cisco patent on HSRP by avoiding core
	details, so KAME would integrate that eventually.

itojun


--- KAME IPR policy
9. Policy on technology with intellectual property right restriction

There are quite a few IETF documents/whatever which has intellectual property
right (IPR) restriction.  KAME's stance is stated below.

    The goal of KAME is to provide freely redistributable, BSD-licensed,
    implementation of Internet protocol technologies.
    For this purpose, we implement protocols that (1) do not need license
    contract with IPR holder, and (2) are royality-free.
    The reason for (1) is, even if KAME contracts with the IPR holder in
    question, the users of KAME stack (usually implementers of some other
    codebase) would need to make a license contract with the IPR holder.
    it would damage "freely redistributable" status of KAME codebase.

    By doing so KAME is (implicitly) trying to advocate no-license-contract,
    royality-free, release of IPRs.

Note however, as documented in README, we do not guarantee that KAME code
is free of IPR infringement, you MUST check it if you are to integrate
KAME into your product (or whatever):
    READ CAREFULLY: Several countries have legal enforcement for
    export/import/use of cryptographic software.  Check it before playing
    with the kit.  We do not intend to be your legalease clearing house
    (NO WARRANTY).  If you intend to include KAME stack into your product,
    you'll need to check if the licenses on each file fit your situations,
    and/or possible intellectual property right issues.



From owner-ietf@ietf.org  Wed Oct 22 08:46:52 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06268
	for <ietf-web-archive@odin.ietf.org>; Wed, 22 Oct 2003 08:46:52 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ACI6L-0007wm-BU
	for ietf-list@asgard.ietf.org; Wed, 22 Oct 2003 08:28:33 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ACI5w-0007uI-RK
	for ietf@asgard.ietf.org; Wed, 22 Oct 2003 08:28:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05469
	for <ietf@ietf.org>; Wed, 22 Oct 2003 08:27:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACI5w-0004Mh-00
	for ietf@ietf.org; Wed, 22 Oct 2003 08:28:08 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACI5v-0004LF-00
	for ietf@ietf.org; Wed, 22 Oct 2003 08:28:07 -0400
Received: from employees.org (171.68.223.138)
  by sj-iport-5.cisco.com with ESMTP; 22 Oct 2003 05:28:41 -0700
Received: from cisco.com (sjc-vpn2-404.cisco.com [10.21.113.148])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with SMTP id h9MCQebd029997;
	Wed, 22 Oct 2003 05:26:41 -0700 (PDT)
Received: by cisco.com (sSMTP sendmail emulation); Wed, 22 Oct 2003 08:26:28 -0400
Date: Wed, 22 Oct 2003 08:26:28 -0400
From: Scott W Brim <swb@employees.org>
To: Margaret.Wasserman@nokia.com
Cc: harald@alvestrand.no, problem-statement@alvestrand.no, ietf@ietf.org
Subject: Re: IESG proposed statement on the IETF mission
Message-ID: <20031022082628.F2936@sbrim-w2k01>
Mail-Followup-To: Scott W Brim <swb@employees.org>,
	Margaret.Wasserman@nokia.com, harald@alvestrand.no,
	problem-statement@alvestrand.no, ietf@ietf.org
References: <E320A8529CF07E4C967ECC2F380B0CF902332FCC@bsebe001.americas.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <E320A8529CF07E4C967ECC2F380B0CF902332FCC@bsebe001.americas.nokia.com>; from Margaret.Wasserman@nokia.com on Wed, Oct 15, 2003 at 01:01:53PM -0400
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Oct 15, 2003 01:01:53PM -0400, Margaret.Wasserman@nokia.com allegedly wrote:
> 
> Hi Scott,
> 
> > Similarly for almost all of the rest.  What's the point?  Are you
> > reiterating the problem-statement work?  They're doing all right,
> > although perhaps you could help push the work to completion.  It would
> > be much more useful for you to reaffirm the fundamental 
> > principles that are not on the auction block.
> 
> >From your perspective, what are those fundamental principles?

I still haven't replied and I don't know when I'll get to.  I thought I
would have room in the last few days, but we're trying to finish a
document and my wife goes for her (hopefully final) chemotherapy session
on Thursday, which means I turn into a pumpkin for the rest of the week.
Someday.  Sorry.



From owner-ietf@ietf.org  Thu Oct 23 06:07:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11270
	for <ietf-web-archive@odin.ietf.org>; Thu, 23 Oct 2003 06:07:44 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ACc4w-0008Fa-DW
	for ietf-list@asgard.ietf.org; Thu, 23 Oct 2003 05:48:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ACc44-0008E5-Ss
	for ietf@asgard.ietf.org; Thu, 23 Oct 2003 05:47:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10516
	for <ietf@ietf.org>; Thu, 23 Oct 2003 05:47:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACc42-0004Rz-00
	for ietf@ietf.org; Thu, 23 Oct 2003 05:47:30 -0400
Received: from teldanex.hiit.fi ([212.68.5.99] helo=n97.nomadiclab.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACc41-0004Rs-00
	for ietf@ietf.org; Thu, 23 Oct 2003 05:47:29 -0400
Received: from nomadiclab.com (teldanex.local.nikander.com [192.168.0.194])
	by n97.nomadiclab.com (Postfix) with ESMTP
	id A63F41C; Thu, 23 Oct 2003 13:00:13 +0300 (EEST)
Message-ID: <3F97A396.5040300@nomadiclab.com>
Date: Thu, 23 Oct 2003 12:47:02 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF Discuss <ietf@ietf.org>, Multi6 WG <multi6@ops.ietf.org>,
        Mobile IPv6 WG <mipv6@ietf.org>, Mobile IPv4 WG <mipv4@ietf.org>,
        IPsec WG <ipsec@lists.tislabs.com>
Cc: hipsec@honor.trusecure.com, hipsec@honor.trusecure.com
Subject: Host Identity Protocol Architecture and BOF
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

The Host Identity Protocol, first discussed after the the
MALLOC meeting at 43th IETF in Orlando and again at BOFs
during the 50th IETF in Minneapolis and 51st in London, is
surfacing again.

The HIP work has proceeded at the side of the IETF, without any
formal organization, to a level where the HIP Architecture
document is ready to be published as an Informational RFC.
The actual protocol specification is also quite mature, and
there there are at least six implementations, four of which
have been tested for interoperability.  To complete the remaining
work on infrastructure so that it would be possible to experiment
with HIP on a wide scale, we have requested a BOF for the next
IETF in Minneapolis.  While the BOF is still pending formal
approval from the ADs, it does appear at the preliminary agenda.


The architecture specification, draft-moskowitz-hip-arch-05.txt,
is on its way to the archives.  The plan is to submit it directly
to the RFC Editor on Monday, October 27th, following the procedure
of RFC2026 Section 4.2.3.  It would be very valuable if people
would read the draft either before Oct27th or soon afterwards,
allowing possible comments to be considered before publishing the
document.   The comments should be sent either directly to the
authors or to the hipsec mailing list.

Since it may take some time before the draft appears in the
repository, it is currently also available at the following URLs:

http://www.tml.hut.fi/~pnr/HIP/draft-moskowitz-hip-arch-05.txt
http://www.tml.hut.fi/~pnr/HIP/draft-moskowitz-hip-arch-05.html
http://www.tml.hut.fi/~pnr/HIP/draft-moskowitz-hip-arch-05.xml

The corresponding protocol specification, draft-moskowitz-hip-08.txt,
will be heading to the repository later today.  It will also be
available at URLs similar to the ones above.  An announcement
will be sent to the hipsec mailing list.


The BOF is currently scheduled for Thursday, Nov 13, at 1300-1500,
but as the agenda is still much in flux, it may be moved.  The BOF
description is available at http://www.ietf.org/ietf/03nov/hipbof.txt


At this stage I want to thank the large number of people that have
contributed to HIP during these years, allowing it to proceed this
far.  You know who you are.  Without your work it would not have
been possible to get even here.  HIP has been a community effort,
and will continue as such.


This announcement was sent to the Multi6, Mobile IPv4, Mobile IPv6,
and IPsec WGs, in addition to the IETF Discuss mailing lists.  The
reason for this is that HIP, if adopted, may have effects on IPsec
based security, IP layer mobility, and multi-address multi-homing.

The HIP architecture and protocol should be discussed at the hipsec
mailing list; see the BOF description for details on how to subscribe.

--Pekka Nikander





From owner-ietf@ietf.org  Thu Oct 23 14:42:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11702
	for <ietf-web-archive@odin.ietf.org>; Thu, 23 Oct 2003 14:42:42 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ACkF4-0006pr-Bm
	for ietf-list@asgard.ietf.org; Thu, 23 Oct 2003 14:31:26 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ACkEC-0006iy-5M
	for ietf@asgard.ietf.org; Thu, 23 Oct 2003 14:30:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11398
	for <ietf@ietf.org>; Thu, 23 Oct 2003 14:30:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACkEA-0006EL-00
	for ietf@ietf.org; Thu, 23 Oct 2003 14:30:30 -0400
Received: from web11904.mail.yahoo.com ([216.136.172.188])
	by ietf-mx with smtp (Exim 4.12)
	id 1ACkEA-0006EI-00
	for ietf@ietf.org; Thu, 23 Oct 2003 14:30:30 -0400
Message-ID: <20031023183018.2444.qmail@web11904.mail.yahoo.com>
Received: from [203.192.205.194] by web11904.mail.yahoo.com via HTTP; Thu, 23 Oct 2003 11:30:18 PDT
Date: Thu, 23 Oct 2003 11:30:18 -0700 (PDT)
From: Patricia Townstend <patriciatownstend@yahoo.com>
Subject: 11th Parlay Open Meeting Event Announcement
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-526847604-1066933818=:2150"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-526847604-1066933818=:2150
Content-Type: text/plain; charset=us-ascii

Folks,
 
Just for your information; thought it might be relevant to some potential participants on this list. 
 
Details at: http://www.parlay.org/news/events/meeting110403/index.asp
 
-\Patty
 

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

11th Parlay Open Meeting
Rome - Italy
November 4-6, 2003
Pre- Meeting Education Track November 3, 2003
 

   Listen to Industry leaders Korea Telecom, Telecom Italia, tekVizion, and WiPro Technologies speak during the Parlay Plenary session

   Experience "Parlay Live": A Net4Call/Ericsson Interactive Televoting Experience

   Meet Friends & Colleagues at the Parlay Business Networking Reception,  Tuesday evening, November 4th  -- Hosted by Appium Technologies 

   Observe demonstrations from Parlay member companies: Ericsson, Net4Call, IBM, Appium, Telecom Italia, Infitel International, Open API Solutions, AePONA, Marconi, Redknee, Inc, and Hewlett-Packard

   Learn more about Parlay from the Parlay Education Track hosted by Thomas Magedanz, Director, FOKUS, "3G Beyond" and Marc LeClerc, Ericsson, Parlay Marketing Chair, held Monday, November 3rd 

   
Attend the Newly implemented POIG working group geared toward Operators


   View member presentations in our showcase from: Kabira Technologies, Ind TeleSoft, Telcordia, Telenity,  Redknee, Inc., Appium, Net4Call, IBM, Ericsson, Marconi, Hewlett-Packard, Infitel International, Telecom Italia, AePONA, tekVizion

   Participate in Parlay 's new  Technical Direction Discussion Group an extension of the original TAC group

   Contribute to the Parlay 6 Requirements session

   Get Involved with the planning and discussions for the next Interoperability Event in January 2004
 
Learn More & Register Now
 
  
---------------------------------



MEMBERSHIP OPPORTUNITY

There will be a literature table available for member companies to display a limited amount of their company collateral.  If you are interested please plan to bring or ship literature to the meeting for display.  If you have any questions please contact Krista Burgess kburgess@inventures.com



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




OTHER IMPORTANT INFO. & DEADLINES

 

 

HOTEL INFORMATION

 

If you have not made your hotel reservations please do so by Monday, October 20th, after this date the Parlay contracted rate will no longer be guaranteed.  Rooms can be reserved based on availability and the going rate at that time.  Parlay has blocked rooms for the attendees convenience, please take advantage of this opportunity.

 

Hilton Rome Airport

Via Arturo Ferrarin 2

Fiumicino-Roma 00050

Reservation Phone: +39.06.6525(8)

 

GENERAL MEETING REGISTRATION

 

Take a moment now to register for Rome, if you haven't already.  Invite your co-workers, vendors, and customers - EVERYONE'S WELCOME!!!!! There is no cost to attend this meeting.


Registrations need to be submitted by Wednesday, October 22nd

Registration & Further Information

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



The Parlay Group  Member Meeting 
Rome, Italy November 4-6, 2003
 plus Pre-Meeting Education Track: Monday, Nov. 3rd 
 
Look what's new for the Parlay Group in Rome, here are several reasons why you should not miss this opportunity  ... 

   Featuring Korea Telecom, tekVizion, Wipro Technologies as plenary speakers 
    Experience "Parlay Live": A Net4Call/Ericsson Interactive Televoting Experience 
    Attend the OSA/Parlay Interop Planning - Discussions about the upcoming interop event in January 04'    
    Learn about a NEW Parlay Technical Direction Group - Discussions on where Parlay stands now and in the future 
    Join our Host, Appium for an Evening Networking Reception, Tuesday, Nov. 4th from 6-8PM.  The Parlay Group would like to thank Appium for sponsoring this event. 
   View the Attached Meeting Agenda for further details

Come share in this excitement, everyone is welcome to register online.
 

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









---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
--0-526847604-1066933818=:2150
Content-Type: text/html; charset=us-ascii

<DIV>
<DIV>
<DIV><FONT face=Arial>
<DIV align=center><SPAN class=912245222-02052003><FONT size=4><FONT color=#0000ff><FONT face=Arial><SPAN class=827300021-08052003><SPAN class=845424421-09102003>
<DIV align=left><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><FONT face=Arial><SPAN class=912245222-02052003><SPAN class=845424421-09102003></SPAN></SPAN></FONT></SPAN></SPAN></SPAN></SPAN><FONT size=3><FONT color=#000000>Folks,</FONT></FONT></DIV>
<DIV align=left>&nbsp;</DIV>
<DIV align=left><FONT color=#000000 size=3>Just for your information; thought it might be relevant to some potential participants on this list. </FONT></DIV>
<DIV align=left>&nbsp;</DIV>
<DIV align=left><FONT color=#000000 size=3>Details at: <A href="http://www.parlay.org/news/events/meeting110403/index.asp">http://www.parlay.org/news/events/meeting110403/index.asp</A></FONT></DIV>
<DIV align=left>&nbsp;</DIV>
<DIV align=left><FONT color=#000000 size=3>-\Patty</FONT></DIV>
<DIV align=left><FONT face=Arial><STRONG>&nbsp;</STRONG></DIV>
<DIV align=left><STRONG>
<HR>
</STRONG></DIV>
<DIV align=center><STRONG><SPAN class=072004420-15102003><FONT color=#000080 face=Arial>11th Parlay Open Meeting</FONT></SPAN></STRONG></DIV>
<DIV align=center><STRONG><SPAN class=072004420-15102003><FONT color=#000080 face=Arial>Rome - Italy</FONT></SPAN></STRONG></DIV>
<DIV align=center><STRONG><SPAN class=072004420-15102003><FONT color=#000080 face=Arial>November 4-6, 2003</FONT></SPAN></STRONG></DIV>
<DIV align=center><STRONG><SPAN class=072004420-15102003><FONT color=#000080 face=Arial>Pre- Meeting Education Track November 3, 2003</FONT></SPAN></STRONG></DIV>
<DIV align=center><SPAN class=072004420-15102003><FONT color=#000080><FONT color=#000000 face=Arial><SPAN></SPAN></FONT></FONT></SPAN><STRONG>&nbsp;</STRONG></DIV>
<OL>
<LI>
<DIV align=left><STRONG><FONT color=#0000ff><SPAN class=072004420-15102003><FONT face="Arial Black"><SPAN><SPAN class=734080100-16102003><FONT face=Arial><FONT face="Times New Roman">Listen to Industry leaders</FONT> <FONT face="Times New Roman">Korea Telecom, Telecom Italia, tekVizion, and WiPro Technologies</FONT>&nbsp;<FONT face="Times New Roman">speak during the Parlay Plenary session</FONT></FONT></SPAN></SPAN></FONT></SPAN></FONT></STRONG></DIV>
<LI>
<DIV align=left><SPAN class=072004420-15102003><FONT color=#000080><FONT color=#000000 face="Arial Black"><SPAN><SPAN class=734080100-16102003></SPAN></SPAN></FONT></FONT></SPAN><STRONG><SPAN class=072004420-15102003><FONT face="Times New Roman">Experience&nbsp;"Parlay Live": A Net4Call/Ericsson&nbsp;Interactive Televoting Experience</FONT></SPAN></STRONG></DIV>
<LI>
<DIV align=left><STRONG><SPAN class=072004420-15102003><SPAN class=734080100-16102003><FONT face=Arial size=2><FONT face="Times New Roman" size=3>Meet Friends &amp; Colleagues at the&nbsp;Parlay</FONT></FONT></SPAN> <FONT face="Times New Roman">Business Networking Reception</FONT>,&nbsp;<SPAN class=734080100-16102003><FONT face=Arial size=2>&nbsp;<FONT face="Times New Roman" size=3>Tuesday evening,</FONT>&nbsp;</FONT></SPAN><FONT face="Times New Roman">November 4th</FONT>&nbsp;<SPAN class=734080100-16102003><FONT face=Arial size=2>&nbsp;-- <FONT face="Times New Roman" size=3>Hosted by Appium Technologies</FONT>&nbsp;</FONT></SPAN></SPAN></STRONG></DIV>
<LI>
<DIV align=left><SPAN class=072004420-15102003><SPAN class=734080100-16102003></SPAN></SPAN><STRONG><SPAN class=072004420-15102003><FONT face=Arial><FONT face="Times New Roman">Observe demonstrations from Parlay member companies:</FONT> </FONT><FONT face="Times New Roman">Ericsson,&nbsp;Net4Call,&nbsp;IBM, Appium, Telecom Italia, Infitel International, Open API Solutions, AePONA, Marconi, Redknee, Inc, and Hewlett-Packard</FONT></SPAN></STRONG></DIV>
<LI>
<DIV align=left><STRONG><SPAN class=072004420-15102003><FONT face="Times New Roman">Learn more about Parlay from the Parlay Education Track</FONT> <FONT face="Times New Roman"><FONT face="Times New Roman"><SPAN><FONT face="Times New Roman">hosted by </FONT></SPAN><SPAN><FONT face="Times New Roman">Thomas</FONT> </SPAN></FONT><SPAN><FONT face="Times New Roman">Magedanz, Director, FOKUS, "3G</FONT> <FONT face="Times New Roman">Beyond" and Marc LeClerc, Ericsson, Parlay Marketing Chair, held Monday, November 3<SUP>rd </SUP></FONT></SPAN></FONT></SPAN></STRONG></DIV>
<LI>
<DIV align=left><SPAN class=072004420-15102003><FONT face="Times New Roman"><SPAN>
<P class=MsoBodyText><STRONG><SPAN><FONT face="Times New Roman"><SPAN class=072004420-15102003><SPAN class=734080100-16102003><FONT face=Arial size=2><FONT face="Times New Roman" size=3>Attend the</FONT> </FONT></SPAN>N</SPAN>ewly implemented POIG working group gear<SPAN class=072004420-15102003>ed</SPAN> to<SPAN class=241451400-16102003>ward</SPAN> Operators</FONT></SPAN></STRONG></P></SPAN></FONT></SPAN></DIV>
<LI>
<DIV align=left><STRONG><SPAN class=072004420-15102003><FONT face="Times New Roman">View member presentations in our showcase from: Kabira Technologies, Ind TeleSoft, Telcordia, Telenity,&nbsp; Redknee, Inc., Appium, Net4Call,&nbsp;IBM, Ericsson, Marconi, Hewlett-Packard, Infitel International, Telecom Italia, AePONA, tekVizion</FONT></SPAN></STRONG></DIV>
<LI>
<DIV align=left><STRONG><SPAN class=072004420-15102003><FONT face="Times New Roman"><SPAN class=734080100-16102003>Participate in</SPAN> Parlay<SPAN class=734080100-16102003>&nbsp;'s new&nbsp;</SPAN> Technical Direction Discussion Group an extension of the original TAC group</FONT></SPAN></STRONG></DIV>
<LI>
<DIV align=left><STRONG><SPAN class=072004420-15102003><SPAN class=072004420-15102003><SPAN class=241451400-16102003><FONT face="Times New Roman">Contribute to the Parlay 6 Requirements session</FONT></SPAN></SPAN></SPAN></STRONG></DIV>
<LI><STRONG><SPAN class=072004420-15102003><FONT face="Times New Roman"><SPAN class=734080100-16102003>Get Involved with</SPAN> the planning and discussions for the next Interoperability Event in January 2004</FONT></SPAN></STRONG></LI></OL>
<DIV align=left><SPAN class=072004420-15102003></SPAN><STRONG>&nbsp;</STRONG></DIV>
<DIV align=center><SPAN class=072004420-15102003></SPAN><SPAN class=072004420-15102003><FONT face=Arial size=4><A href="http://www.parlay.org/news/events/meeting110403/index.asp" target=_blank><STRONG>Learn More &amp; Register Now</STRONG></A></FONT></SPAN></DIV>
<DIV align=left><SPAN class=072004420-15102003><FONT color=#000080 face=Arial size=4></FONT></SPAN><STRONG>&nbsp;</STRONG></DIV>
<DIV align=left><SPAN class=072004420-15102003><STRONG><SPAN><SPAN><SPAN class=449513615-25042003>&nbsp; 
<HR>
</SPAN></SPAN></SPAN></STRONG>
<P></P>
<P align=center class=MsoNormal><STRONG><FONT color=#000000><SPAN><SPAN><SPAN class=449513615-25042003><FONT color=#008080 size=5><U>MEMBERSHIP OPPORTUNITY</U></FONT></SPAN></SPAN></SPAN></FONT></STRONG></P>
<P align=left class=MsoNormal><FONT color=#000000><SPAN><SPAN><SPAN class=449513615-25042003><STRONG><SPAN class=072004420-15102003>There will be </SPAN>a <FONT color=#ff0000>literature table</FONT> available for member companies to display a limited amount of their company&nbsp;<SPAN class=072004420-15102003>collateral</SPAN>.&nbsp; If you are interested please plan to bring or ship literature to the meeting for display.&nbsp; If you have any questions please contact Krista Burgess </STRONG><A href="http://us.f119.mail.yahoo.com/ym/Compose?To=kburgess@inventures.com" target=_blank><STRONG>kburgess@inventures.com</STRONG></A></SPAN></SPAN></SPAN></FONT></P>
<P align=left class=MsoNormal><FONT color=#000000><SPAN><SPAN><SPAN class=449513615-25042003></P><STRONG>
<HR>
</STRONG></SPAN></SPAN></SPAN></FONT>
<P></P><FONT color=#ff0000 size=5><SPAN class=083570119-17122002>
<DIV align=left><FONT face=Arial></FONT><FONT size=2><FONT color=#000000><SPAN></DIV>
<DIV align=left>
<P align=center><STRONG><FONT face=Arial size=5><SPAN class=083570119-17122002>OTHER IMPORTANT INFO. &amp; DEADLINES</SPAN></FONT></STRONG></P>
<P align=center><FONT color=#00ff00 face=Arial size=5><SPAN class=083570119-17122002><U></U></SPAN></FONT><STRONG>&nbsp;</STRONG></P>
<P align=left><SPAN><SPAN><SPAN class=824161520-01102002><SPAN class=455513623-01102002><FONT face=Arial><SPAN class=003321020-22042003></SPAN></FONT></SPAN></SPAN></SPAN><SPAN><SPAN class=824161520-01102002><FONT color=#000000 size=3><SPAN class=072004420-15102003></SPAN></FONT></SPAN></SPAN></SPAN><STRONG>&nbsp;</STRONG></P>
<P align=left><STRONG><SPAN><SPAN><SPAN class=824161520-01102002><FONT color=#000000 face=Arial size=3><SPAN class=072004420-15102003><U>HOTEL INFORMATION</U></SPAN></FONT></SPAN></SPAN></SPAN></STRONG></P>
<P align=left><SPAN><SPAN><SPAN class=824161520-01102002><FONT color=#000000 face=Arial size=3><SPAN class=072004420-15102003><U></U></SPAN></FONT></SPAN></SPAN></SPAN><STRONG>&nbsp;</STRONG></P><SPAN><SPAN><SPAN class=824161520-01102002><FONT size=+0><SPAN class=072004420-15102003>
<P class=MsoNormal><STRONG><SPAN><SPAN class=072004420-15102003><FONT color=#000000 size=3>If you have not made your hotel reservations please do so by <FONT color=#ff0000><U>Monday, October 20th,</U></FONT><FONT color=#000000> after this date the Parlay contracted rate will no longer be guaranteed.&nbsp; Rooms can be reserved based on availability and the going rate at that time.&nbsp; Parlay has blocked rooms for the attendees convenience, please take advantage of this opportunity.</FONT></FONT></SPAN></SPAN></STRONG></P>
<P class=MsoNormal><SPAN><SPAN class=072004420-15102003><FONT color=#000000 size=3></FONT></SPAN></SPAN><STRONG>&nbsp;</STRONG></P>
<P class=MsoNormal><STRONG><SPAN><FONT color=#000000><FONT size=3>Hilton Rome Airport</FONT></FONT></SPAN></STRONG></P>
<P class=MsoNormal><STRONG><SPAN><FONT color=#000000><FONT size=3>Via Arturo Ferrarin 2</FONT></FONT></SPAN></STRONG></P>
<P class=MsoNormal><STRONG><SPAN><FONT color=#000000><FONT size=3>Fiumicino-Roma 00050</FONT></FONT></SPAN></STRONG></P>
<P class=DefinitionTerm><STRONG><SPAN><FONT color=#000000><FONT size=3><SPAN class=072004420-15102003>Reservation </SPAN>Phone: +39.06.6525<SPAN class=072004420-15102003>(8)</SPAN></FONT></FONT></SPAN></STRONG></P>
<P class=DefinitionTerm><SPAN><FONT color=#000000><FONT size=3><SPAN class=072004420-15102003></SPAN></FONT></FONT></SPAN><STRONG>&nbsp;</STRONG></P>
<P class=DefinitionTerm><STRONG><SPAN><FONT color=#000000><FONT size=3><SPAN class=072004420-15102003><U>GENERAL MEETING REGISTRATION</U></SPAN></FONT></FONT></SPAN></STRONG></P>
<P class=DefinitionTerm><SPAN><FONT color=#000000><FONT size=3><SPAN class=072004420-15102003><U></U></SPAN></FONT></FONT></SPAN><STRONG>&nbsp;</STRONG></P><STRONG>
<P class=DefinitionTerm><SPAN><FONT color=#000000><FONT size=3><SPAN class=072004420-15102003><FONT face=Arial>Take a moment now to register for&nbsp;<SPAN class=083570119-17122002><SPAN class=003321020-22042003>Rome, if you haven't already</SPAN></SPAN><SPAN><SPAN class=040281922-30122002>.&nbsp; Invite your co-workers, vendors, and customers - EVERYONE'S WELCOME!!!!! There is <U>no cost</U> to attend this meeting.</SPAN></SPAN></FONT></SPAN></FONT></FONT></SPAN></SPAN></STRONG></FONT></SPAN></SPAN></SPAN><SPAN><FONT color=#000000></P></DIV>
<DIV align=left>
<P class=MsoNormal><STRONG><FONT face=Arial><FONT size=3><SPAN class=072004420-15102003>R</SPAN>egistrations need to be submitted by&nbsp;<U><FONT color=#ff0000><SPAN class=072004420-15102003>Wednes</SPAN><SPAN>day,&nbsp;<SPAN class=072004420-15102003>October 22nd</SPAN></SPAN></FONT></U></FONT></FONT></STRONG></P>
<P><A href="http://www.parlay.org/news/events/meeting110403/index.asp" target=_blank><STRONG><FONT color=#0000ff><FONT face=Arial><SPAN class=824161520-01102002><FONT size=3>Registration&nbsp;<SPAN class=003321020-22042003>&amp; Further Information</SPAN></FONT></SPAN><U><SPAN><FONT size=2></FONT></SPAN></U></FONT></FONT></STRONG></A></P></FONT></SPAN></SPAN></FONT></FONT></SPAN></FONT></SPAN></FONT><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><FONT color=#000000><FONT size=3><SPAN class=912245222-02052003><SPAN class=845424421-09102003><STRONG>
<HR>
</STRONG></SPAN></SPAN></FONT></FONT></SPAN></SPAN></SPAN></SPAN></DIV></DIV></SPAN></SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV align=center><SPAN class=912245222-02052003><FONT size=4><FONT color=#0000ff><FONT face=Arial><STRONG><SPAN class=827300021-08052003><SPAN class=845424421-09102003>The </SPAN>P</SPAN>arlay&nbsp;</STRONG><SPAN class=845424421-09102003><STRONG>Group</STRONG><SPAN class=199470823-09102003><FONT size=2>&nbsp;<STRONG><FONT size=4> Member Meeting</FONT></STRONG>&nbsp;</FONT></SPAN></SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV align=center><SPAN class=912245222-02052003><STRONG><FONT color=#0000ff><FONT size=4><FONT face=Arial><SPAN class=845424421-09102003>Rome, Italy</SPAN><SPAN class=827300021-08052003>&nbsp;<SPAN class=845424421-09102003>November 4</SPAN>-<SPAN class=845424421-09102003>6</SPAN>, 2003</SPAN></FONT></FONT></FONT></STRONG></SPAN></DIV>
<DIV align=center><FONT color=#0000ff size=2><SPAN class=912245222-02052003><FONT size=4><SPAN class=827300021-08052003><FONT face=Arial><SPAN class=199470823-09102003><FONT size=2><FONT size=4>&nbsp;plus</FONT>&nbsp;</FONT></SPAN>Pre-<SPAN class=845424421-09102003>Meeting&nbsp;</SPAN><SPAN class=845424421-09102003>Education Track</SPAN>:&nbsp;<SPAN class=845424421-09102003>Mon</SPAN>day<SPAN class=845424421-09102003>,</SPAN>&nbsp;<SPAN class=845424421-09102003>Nov.</SPAN> 3<SPAN class=845424421-09102003>rd</SPAN>&nbsp;</FONT></SPAN></FONT></SPAN></DIV>
<DIV align=center><FONT color=#000000><SPAN><SPAN><SPAN class=449513615-25042003><FONT color=#ff0000 face=Arial size=2><SPAN class=000051421-02052003></SPAN></FONT></SPAN></SPAN></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=ltr>
<DIV align=left><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><STRONG><SPAN class=827300021-08052003><FONT color=#000000><FONT size=3><SPAN class=845424421-09102003>L</SPAN>ook what<SPAN class=845424421-09102003>'s new for&nbsp;the Parlay Group&nbsp;in Rome, here are several reasons why you should not miss&nbsp;this opportunity&nbsp;&nbsp;...</SPAN>&nbsp;</FONT></FONT></SPAN></STRONG></SPAN></SPAN></SPAN></SPAN><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><STRONG><FONT color=#000000><FONT size=3><SPAN class=827300021-08052003></SPAN></FONT></FONT></STRONG></SPAN></SPAN></SPAN></SPAN></DIV>
<UL>
<LI><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><STRONG><FONT color=#000000><FONT size=3><SPAN class=827300021-08052003><SPAN class=845424421-09102003><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><STRONG><FONT color=#000000><FONT size=3><SPAN class=827300021-08052003><SPAN class=845424421-09102003>Featuring Korea Telecom, tekVizion, Wipro Technologies as plenary speakers</SPAN></SPAN></FONT></FONT></STRONG></SPAN></SPAN></SPAN></SPAN></SPAN></SPAN></FONT></FONT></STRONG></SPAN></SPAN></SPAN></SPAN><FONT face=Arial> </FONT>
<LI><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><FONT color=#000000><FONT size=3><SPAN class=827300021-08052003><SPAN class=845424421-09102003><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><FONT color=#000000><FONT size=3><SPAN class=827300021-08052003><SPAN class=845424421-09102003><SPAN class=199470823-09102003><FONT color=#0000ff size=2>&nbsp;<FONT color=#000000 size=3><STRONG>Experience</STRONG></FONT>&nbsp;</FONT></SPAN><STRONG>"Parlay Live": A Net4Call/Ericsson&nbsp;Interactive Televoting Experience</STRONG></SPAN></SPAN></FONT></FONT></SPAN></SPAN></SPAN></SPAN></SPAN></SPAN></FONT></FONT></SPAN></SPAN></SPAN></SPAN><FONT face=Arial> </FONT>
<LI><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><FONT color=#000000><FONT size=3><SPAN class=827300021-08052003><SPAN class=845424421-09102003><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><FONT color=#000000><FONT size=3><SPAN class=827300021-08052003><SPAN class=845424421-09102003><SPAN class=199470823-09102003><FONT color=#0000ff size=2>&nbsp;<FONT color=#000000 size=3><STRONG>Attend the</STRONG></FONT>&nbsp;</FONT></SPAN><STRONG>OSA/Parlay Interop Planning - Discussions about the upcoming interop event in January<SPAN class=165082323-09102003> </SPAN>04'&nbsp;&nbsp;&nbsp;</STRONG></SPAN></SPAN></FONT></FONT></SPAN></SPAN></SPAN></SPAN></SPAN></SPAN></FONT></FONT></SPAN></SPAN></SPAN></SPAN><FONT face=Arial> </FONT>
<LI><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><FONT color=#000000><FONT size=3><SPAN class=827300021-08052003><SPAN class=845424421-09102003><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><FONT color=#000000><FONT size=3><SPAN class=827300021-08052003><SPAN class=845424421-09102003><SPAN class=199470823-09102003><FONT color=#0000ff size=2>&nbsp;<FONT color=#000000 size=3><STRONG>Learn about a&nbsp;NEW</STRONG></FONT>&nbsp;</FONT></SPAN><STRONG>Parlay Technical Direction Group - Discussions on where Parlay stands now and in the future</STRONG></SPAN></SPAN></FONT></FONT></SPAN></SPAN></SPAN></SPAN></SPAN></SPAN></FONT></FONT></SPAN></SPAN></SPAN></SPAN><FONT face=Arial> </FONT>
<LI><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><FONT color=#000000><FONT size=3><SPAN class=827300021-08052003><SPAN class=845424421-09102003><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><FONT color=#000000><FONT size=3><SPAN class=827300021-08052003><SPAN class=845424421-09102003><SPAN class=199470823-09102003><FONT color=#0000ff size=2>&nbsp;<FONT color=#000000 size=3><STRONG>Join our Host, Appium for an</STRONG></FONT>&nbsp;</FONT></SPAN><STRONG>Evening Networking&nbsp;Reception, Tuesday, Nov. 4th from 6-8PM.</STRONG></SPAN></SPAN><SPAN class=827300021-08052003><STRONG>&nbsp; The Parlay Group would like to thank&nbsp;<SPAN class=845424421-09102003>Appium </SPAN>for sponsoring this event<SPAN class=845424421-09102003>.</SPAN></STRONG></SPAN></FONT></FONT></SPAN></SPAN></SPAN></SPAN></SPAN></SPAN></FONT></FONT></SPAN></SPAN></SPAN></SPAN><FONT face=Arial> </FONT>
<LI>
<DIV align=left><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><STRONG><FONT size=+0><FONT size=+0><FONT color=#000000 size=3><SPAN class=827300021-08052003>View the Attached Meeting Agenda for further details</SPAN></FONT></FONT></FONT></STRONG></SPAN></SPAN></SPAN></SPAN></DIV></LI></UL>
<DIV align=left><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><STRONG><FONT color=#000000><FONT size=3>Come share in this excitement<SPAN class=912245222-02052003>,&nbsp;<SPAN class=827300021-08052003>everyone is welcome to </SPAN><A href="http://www.parlay.org/news/events/meeting110403/index.asp" target=_blank>register&nbsp;</A><SPAN class=845424421-09102003><A href="http://www.parlay.org/news/events/meeting110403/index.asp" target=_blank>online</A>.</SPAN></SPAN></FONT></FONT></STRONG></SPAN></SPAN></SPAN></SPAN></DIV>
<DIV align=left><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><STRONG><FONT color=#000000><FONT face=Arial size=3><SPAN class=912245222-02052003><SPAN class=845424421-09102003></SPAN></SPAN></FONT></FONT></STRONG></SPAN></SPAN></SPAN></SPAN>&nbsp;</DIV>
<DIV align=left><SPAN><SPAN><SPAN class=449513615-25042003><SPAN class=000051421-02052003><FONT color=#000000><FONT size=3><SPAN class=912245222-02052003><SPAN class=845424421-09102003><STRONG>
<HR>
</STRONG></SPAN></SPAN></FONT></FONT></SPAN></SPAN></SPAN></SPAN></DIV></BLOCKQUOTE></FONT></FONT></DIV>
<P><BR></P></DIV></DIV><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://shopping.yahoo.com/?__yltc=s%3A150000443%2Cd%3A22708228%2Cslk%3Atext%2Csec%3Amail">The New Yahoo! Shopping</a> - with improved product search
--0-526847604-1066933818=:2150--



From owner-ietf@ietf.org  Thu Oct 23 17:03:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18836
	for <ietf-web-archive@odin.ietf.org>; Thu, 23 Oct 2003 17:03:04 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ACmRe-0005NW-93
	for ietf-list@asgard.ietf.org; Thu, 23 Oct 2003 16:52:34 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ACmKI-00052p-7B
	for ietf@asgard.ietf.org; Thu, 23 Oct 2003 16:44:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18067
	for <ietf@ietf.org>; Thu, 23 Oct 2003 16:44:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACmKG-0000Hx-00
	for ietf@ietf.org; Thu, 23 Oct 2003 16:44:56 -0400
Received: from noxmail.sandelman.ottawa.on.ca ([205.150.200.166])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACmKF-0000Hu-00
	for ietf@ietf.org; Thu, 23 Oct 2003 16:44:56 -0400
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca [205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id h9NKln302736
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK);
	Thu, 23 Oct 2003 16:47:54 -0400 (EDT)
Received: from marajade.sandelman.ottawa.on.ca (mcr@marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id h9NKfEmr030114
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 23 Oct 2003 16:41:14 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by marajade.sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id h9NKf88f030091;
	Thu, 23 Oct 2003 16:41:11 -0400
To: ietf@ietf.org, problem-statement@alvestrand.no
Subject: Re: IETF mission boundaries (Re: IESG proposed statement on the IETF mission ) 
In-reply-to: Your message of "Thu, 16 Oct 2003 11:04:32 +0200."
             <11016450.1066302272@localhost> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 23 Oct 2003 16:41:08 -0400
Message-ID: <30090.1066941668@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-ietf@ietf.org
Precedence: bulk

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


>>>>> "Harald" == Harald Tveit Alvestrand <harald@alvestrand.no> writes:
    Harald> In the discussions leading up to this document, we actually had 3
    Harald> different other levels of "inclusivity" up for consideration:

  okay, I very much like these descriptions.

    Harald> - "Everything that runs over the Internet is appropriate for IETF
    Harald> standardization". 

    Harald> - "Everything that needs open, documented interoperability and
    Harald> runs over the Internet is appropriate for IETF
    Harald> standardization". 

    Harald> - "Everything that builds infrastructures on the Internet that
    Harald> needs to be open and interoperable is appropriate for IETF
    Harald> standardization". 

  These are three levels that I understand, and each seems to enclose
the next.

    Harald> - "Everything that can seriously impact the Internet is
    Harald> appropriate for IETF standardization". 

  This is very much more nebulous, because "seriously impact" is a question
of very open judgement.

] Collecting stories about my dad: http://www.sandelman.ca/cjr/ |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian/notebook using, kernel hacking, security guy");  [
  
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys - custom hacks make this fully PGP2 compat

iQCVAwUBP5g84oqHRg3pndX9AQH01AP/ayMZ2WJVxz7xZXVSu9Pbew9U1A+GLUFb
PVgK45qNL/qsL95U4cU1SyV5Tn2YYTjWkSD4j8tVNHAX+HyoqDJPYgWFwevOKblY
HCwUj3N6Y/U43TpIZ8+w8NqcIkV0Z4BPc9kjpSjiUeTOZ4nfY+Pbg3yS+vaUvWcd
ThqgtWgB7Lc=
=p3P3
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Fri Oct 24 00:19:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02379
	for <ietf-web-archive@odin.ietf.org>; Fri, 24 Oct 2003 00:19:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ACtBC-0005gG-Is
	for ietf-list@asgard.ietf.org; Fri, 24 Oct 2003 00:04:02 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ACt9j-0005bx-Dh
	for ietf@asgard.ietf.org; Fri, 24 Oct 2003 00:02:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01980
	for <ietf@ietf.org>; Fri, 24 Oct 2003 00:02:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACt9h-0004vm-00
	for ietf@ietf.org; Fri, 24 Oct 2003 00:02:29 -0400
Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1ACt9g-0004un-00
	for ietf@ietf.org; Fri, 24 Oct 2003 00:02:29 -0400
Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap 
	 id 21739; Fri, 24 Oct 2003 00:10:01 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: 11th Parlay Open Meeting Event Announcement
Date: Fri, 24 Oct 2003 00:02:04 -0400
Message-ID: <4A3384433CE2AB46A63468CB207E209D4F686F@zoe.office.snowshore.com>
Thread-Topic: 11th Parlay Open Meeting Event Announcement
Thread-Index: AcOZlg9X+eRRIwD1ThSJ96q88jHEwAATVpYA
From: "Eric Burger" <eburger@snowshore.com>
To: "Patricia Townstend" <patriciatownstend@yahoo.com>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hmmm.  Java version of Q.2931.  Sounds like something everyone on this =
list is dying to do :-)




From owner-ietf@ietf.org  Fri Oct 24 01:50:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04244
	for <ietf-web-archive@odin.ietf.org>; Fri, 24 Oct 2003 01:50:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ACuhO-0004Gs-3f
	for ietf-list@asgard.ietf.org; Fri, 24 Oct 2003 01:41:22 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ACugl-0004Ch-DL
	for ietf@asgard.ietf.org; Fri, 24 Oct 2003 01:40:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04090
	for <ietf@ietf.org>; Fri, 24 Oct 2003 01:40:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACugj-0005hy-00
	for ietf@ietf.org; Fri, 24 Oct 2003 01:40:41 -0400
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACugi-0005hi-00
	for ietf@ietf.org; Fri, 24 Oct 2003 01:40:40 -0400
Received: from INET-VRS-03.redmond.corp.microsoft.com ([157.54.5.27]) by mail3.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 23 Oct 2003 22:40:11 -0700
Received: from 157.54.5.25 by INET-VRS-03.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 23 Oct 2003 22:40:11 -0700
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-hub-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 23 Oct 2003 22:40:10 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Thu, 23 Oct 2003 22:40:10 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Thu, 23 Oct 2003 22:40:10 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7097.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Proposed statement quotes wrong numbers
Date: Thu, 23 Oct 2003 22:40:15 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA05D51E47@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Proposed statement quotes wrong numbers
thread-index: AcOSoeR8gDOBL1xpRi+gwL537VDkXgHTW/xA
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>, <ietf@ietf.org>,
        <problem-statement@alvestrand.no>
X-OriginalArrivalTime: 24 Oct 2003 05:40:10.0206 (UTC) FILETIME=[49DF87E0:01C399F1]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

The statement that you issued repeatedly mentions that the IETF rules
and social contract were establish at a time when the IETF had 50 to 250
or 50 to 300 members. The obvious implication is that, since the
attendance has grown by an order of magnitude, the rules have to change
significantly.

The problem is that the 50-300 numbers are wrong. The original rules of
the IETF were indeed devised in 1986, when the IETF was just created and
had maybe 30-50 members. However, the current rules were designed in
1992-1993, in large part because the IETF had outgrown the previous
rules. If you look at http://www.ietf.org/meetings/past.meetings.html,
you will see that the attendance then was in the 500-700 range. Dave
Clark's statement was made during the 24th IETF, held July 13-17, 1992
in Cambridge, Massachusetts. There were 677 attendees.

Since then, the IETF has grown, and then shrunk. The current size is
about double the size of 1992. That is significant, but not quite an
order of magnitude.

-- Christian Huitema



From owner-ietf@ietf.org  Fri Oct 24 13:02:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17842
	for <ietf-web-archive@odin.ietf.org>; Fri, 24 Oct 2003 13:02:58 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AD3kX-0007c5-4n
	for ietf-list@asgard.ietf.org; Fri, 24 Oct 2003 11:21:13 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AD3Xf-0004Vz-4M
	for ietf@asgard.ietf.org; Fri, 24 Oct 2003 11:07:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07383
	for <ietf@ietf.org>; Fri, 24 Oct 2003 11:07:44 -0400 (EDT)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AD3Xe-00050o-00
	for ietf@ietf.org; Fri, 24 Oct 2003 11:07:54 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AD3Xd-00050l-00
	for ietf@ietf.org; Fri, 24 Oct 2003 11:07:53 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9OF7pI22005
	for <ietf@ietf.org>; Fri, 24 Oct 2003 18:07:51 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T657bb0a727ac158f21082@esvir01nok.ntc.nokia.com>;
 Fri, 24 Oct 2003 18:07:51 +0300
Received: from esebe007.NOE.Nokia.com ([172.21.138.47]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 24 Oct 2003 18:07:50 +0300
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebe007.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 24 Oct 2003 18:07:50 +0300
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Subject: RE: IESG proposed statement on the IETF mission
Date: Fri, 24 Oct 2003 18:07:49 +0300
Message-ID: <DADF50F5EC506B41A0F375ABEB320636BF6CF4@esebe023.ntc.nokia.com>
Thread-Topic: IESG proposed statement on the IETF mission
Thread-Index: AcOSnRJ0iekjj9LVTOe1EGpNCLmQ1AHg3WRQ
To: <harald@alvestrand.no>, <ietf@ietf.org>, <problem-statement@alvestrand.no>
X-OriginalArrivalTime: 24 Oct 2003 15:07:50.0390 (UTC) FILETIME=[97532960:01C39A40]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hi Harald,

I'm going to pick on one statement, which other have as well.

> It is important that this is "For the Internet,"  and does not include =

> everything that happens to use IP.  IP is being used in a myriad of=20
> real-world applications, such as controlling street lights, but the=20
> IETF does not standardize those applications.

I almost feel that this should just be dropped from the statement.  My
reasons being that I have been told by the IESG about protocol =
extensibility
is that the IETF wants to have a tighter control over protocol=20
extensibility, even for extensions thought to be for limited use
or specific networks (for example, cellular networks).  The reason
being is that once something is out there, it often starts to be used
in ways which were not originally planned or used outside of its=20
original 'limited use' plans.  Therefore, in order to ensure proper
protocol behavior & interoperability, the IESG wants to manage
extensibility.  This has been very true in SIP & Diameter, for example.

On the other hand, we see a protocol like RADIUS, which the IETF
has never done a good job at working with or standardizing, being
developed in 4 or more SDOs, and not in a colaborative manner.  This
makes a big mess with the RADIUS spec, and RADIUS does seem like a
protocol that has a big effect on the Internet.

So, in summary, the IESG has shown not to follow the above paragraph,
sometimes even for good reasons.  I can't think of a way in which=20
modify the paragraph to make it any better - because there will always
be examples of work that the IETF choses to standardize (or not)
which will violate that part of the mission.  Perhaps moving the=20
'for the internet to the previous paragraph is what is needed.

 This leaves open the very interesting and difficult questions of
 how to measure quality, relevance, and timeliness.  The IETF
 has identified interoperability, security, scalability and=20
 'for the Internet' as essential, but without attaching measurements=20
 to those characteristics.

John



From owner-ietf@ietf.org  Fri Oct 24 14:17:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20999
	for <ietf-web-archive@odin.ietf.org>; Fri, 24 Oct 2003 14:17:29 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AD69T-0001LB-Oi
	for ietf-list@asgard.ietf.org; Fri, 24 Oct 2003 13:55:07 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AD612-0000eE-G3
	for ietf@asgard.ietf.org; Fri, 24 Oct 2003 13:46:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19888
	for <ietf@ietf.org>; Fri, 24 Oct 2003 13:46:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AD611-0001b6-00
	for ietf@ietf.org; Fri, 24 Oct 2003 13:46:23 -0400
Received: from web11907.mail.yahoo.com ([216.136.172.191])
	by ietf-mx with smtp (Exim 4.12)
	id 1AD610-0001aw-00
	for ietf@ietf.org; Fri, 24 Oct 2003 13:46:22 -0400
Message-ID: <20031024174617.40313.qmail@web11907.mail.yahoo.com>
Received: from [203.192.205.153] by web11907.mail.yahoo.com via HTTP; Fri, 24 Oct 2003 10:46:17 PDT
Date: Fri, 24 Oct 2003 10:46:17 -0700 (PDT)
From: Patricia Townstend <patriciatownstend@yahoo.com>
Subject: RE: 11th Parlay Open Meeting Event Announcement
To: Eric Burger <eburger@snowshore.com>, ietf@ietf.org
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D4F686F@zoe.office.snowshore.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-773973437-1067017577=:39414"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-773973437-1067017577=:39414
Content-Type: text/plain; charset=us-ascii

eric,
 
*q.2931 is broadband isdn spec (e.g., specifies the procedures/parameters/messages  for session control and mtc fuctions between atm endpoints). 
*JAIN deals with java APIs for ISUP, OAM, MEGACO, Call control (JCC/JCAT) etc.
* parlay is not exactly any of the above. as far as i can remember, parlay/osa is an arch and set of i/f worked on jointly by the parlay group, etsi span 12 and 3GPP tsg cn wg5 ("Joint API Group")
 
given this, i couldnt quite get the humour - do excuse my ignorance/naivete. it'd help if you can throw some light. 
 
though this is not very pertinent to this list, the last word from you would help.
 
-\Patty

Eric Burger <eburger@snowshore.com> wrote:
Hmmm. Java version of Q.2931. Sounds like something everyone on this list is dying to do :-)



---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
--0-773973437-1067017577=:39414
Content-Type: text/html; charset=us-ascii

<DIV>
<DIV>eric,</DIV>
<DIV>&nbsp;</DIV>
<DIV>*q.2931 is broadband isdn spec&nbsp;(e.g., specifies the procedures/parameters/messages&nbsp; for session control and mtc fuctions between atm endpoints). </DIV>
<DIV>*JAIN deals with java APIs for ISUP, OAM, MEGACO, Call control (JCC/JCAT) etc.</DIV>
<DIV>* parlay is not exactly any of the above. as far as i can remember, parlay/osa is&nbsp;an arch and&nbsp;set of i/f worked on jointly by the parlay group, etsi span 12 and 3GPP tsg cn wg5 ("Joint API Group")</DIV>
<DIV>&nbsp;</DIV>
<DIV>given this, i couldnt quite get the humour - do excuse my ignorance/naivete. it'd help if you can throw some light. </DIV>
<DIV>&nbsp;</DIV>
<DIV>though this is not very pertinent to this list, the last word from you would help.</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=#000000 size=3>-\Patty</FONT><BR><BR><B><I>Eric Burger &lt;eburger@snowshore.com&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hmmm. Java version of Q.2931. Sounds like something everyone on this list is dying to do :-)<BR></BLOCKQUOTE></DIV><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://shopping.yahoo.com/?__yltc=s%3A150000443%2Cd%3A22708228%2Cslk%3Atext%2Csec%3Amail">The New Yahoo! Shopping</a> - with improved product search
--0-773973437-1067017577=:39414--



From owner-ietf@ietf.org  Fri Oct 24 14:17:30 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21015
	for <ietf-web-archive@odin.ietf.org>; Fri, 24 Oct 2003 14:17:30 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AD67o-00015I-B7
	for ietf-list@asgard.ietf.org; Fri, 24 Oct 2003 13:53:24 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AD5Z9-0007rm-LZ
	for ietf@asgard.ietf.org; Fri, 24 Oct 2003 13:17:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18733
	for <ietf@ietf.org>; Fri, 24 Oct 2003 13:17:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AD5Z9-0001Bp-00
	for ietf@ietf.org; Fri, 24 Oct 2003 13:17:35 -0400
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AD5Z8-0001Bl-00
	for ietf@ietf.org; Fri, 24 Oct 2003 13:17:34 -0400
Received: from latte (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.12.10/8.12.10) with ESMTP id h9OHHQ1e021955
	for <ietf@ietf.org>; Fri, 24 Oct 2003 19:17:26 +0200
To: ietf@ietf.org
Subject: Re: concerning draft-josefsson-dns-url-08.txt
References: <iluel1fkrdb.fsf@latte.josefsson.org>
	<20030628004726.4EDE2230012@fh.vix.com>
	<20030630161659.GB9368@fysh.org> <iluk7b3gg8w.fsf@latte.josefsson.org>
	<20030701085857.GA15880@fysh.org>
From: Simon Josefsson <jas@extundo.com>
X-Payment: hashcash 1.2 0:031024:ietf@ietf.org:e1ce60def29aa016
X-Hashcash: 0:031024:ietf@ietf.org:e1ce60def29aa016
Date: Fri, 24 Oct 2003 19:17:24 +0200
In-Reply-To: <20030701085857.GA15880@fysh.org> (zefram@fysh.org's message of
 "Tue, 1 Jul 2003 09:58:57 +0100")
Message-ID: <ilu8ynaa72z.fsf@extundo.com>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Zefram <zefram@fysh.org> wrote a few months ago:

> I was referring to RFC2673 bit labels.  Consider also what should be
> done for other EDNS0 extended label types (RFC2671).

After doing some research, I discovered that IESG has reclassified
binary labels from proposed standard to experimental, refer to
<http://www1.ietf.org/mail-archive/ietf-announce/Current/msg19416.html>.
So I came to the conclusion that they are not worth spending more time
on, and added the following under "Interoperability considerations":

   Interaction with Binary Labels [12], or other extended label types,
   has not been analyzed. However, they appear to be infrequently used
   in practice.

I hope this is satisfactory.  If someone wants to use binary labels in
DNS URIs, and have some ideas on how to do it, please let me know.

I intend to submit the following document as -09 soon.  If someone has
additional comments, now would be a good opportunity to send them.
Note that it does not remove the optional "//"dnsauthority"/", as I
and others believe it is useful, and there were only one voice that
wanted to remove it.  With that possible exception, and with this
message to solve the binary label problem, I believe I have addressed
all concerns raised in this thread.

http://josefsson.org/draft-josefsson-dns-url.txt

Thanks for the feedback,
Simon




From owner-ietf@ietf.org  Fri Oct 24 18:14:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03516
	for <ietf-web-archive@odin.ietf.org>; Fri, 24 Oct 2003 18:14:02 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AD9yl-0008TK-Rx
	for ietf-list@asgard.ietf.org; Fri, 24 Oct 2003 18:00:19 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AD9pu-0007xu-Qc
	for ietf@asgard.ietf.org; Fri, 24 Oct 2003 17:51:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01700
	for <ietf@ietf.org>; Fri, 24 Oct 2003 17:51:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AD9pt-00056W-00
	for ietf@ietf.org; Fri, 24 Oct 2003 17:51:09 -0400
Received: from 216-43-25-66.ip.mcleodusa.net ([216.43.25.66] helo=episteme-software.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AD9ps-000560-00
	for ietf@ietf.org; Fri, 24 Oct 2003 17:51:08 -0400
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server X 3.2.3b1) for <ietf@ietf.org>;
 Fri, 24 Oct 2003 16:50:54 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p0610030dbbbf4e22a3fe@[216.43.25.67]>
X-Mailer: Eudora [Macintosh version 6.1a2]
Date: Fri, 24 Oct 2003 16:50:36 -0500
To: IETF <ietf@ietf.org>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Multicast in Minneapolis
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

I may be away from the IETF meeting on Wednesday evening in 
Minneapolis . Will there be multicast for the IESG Plenary Wednesday 
night? If so, where can I find out about software in order to use it, 
and once I have that software, is there some way I can test it so 
that I'm sure all of the multicast config is done on my network 
beforehand?

pr
-- 
Pete Resnick <http://wwww.qualcomm.com/~presnick/>
QUALCOMM Incorporated



From owner-ietf@ietf.org  Sun Oct 26 15:20:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27347
	for <ietf-web-archive@odin.ietf.org>; Sun, 26 Oct 2003 15:20:42 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1ADr06-00025O-3s
	for ietf-list@asgard.ietf.org; Sun, 26 Oct 2003 14:56:34 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1ADqzJ-00024N-J4
	for ietf@asgard.ietf.org; Sun, 26 Oct 2003 14:55:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25682;
	Sun, 26 Oct 2003 14:55:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqzH-0000DX-00; Sun, 26 Oct 2003 14:55:43 -0500
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqzH-0000DE-00; Sun, 26 Oct 2003 14:55:43 -0500
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 26 Oct 2003 20:53:10 +0100
Received: from xbe-ams-312.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h9QJt4l0006339;
	Sun, 26 Oct 2003 20:55:04 +0100 (MET)
Received: from xfe-ams-311.cisco.com ([144.254.228.204]) by xbe-ams-312.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Sun, 26 Oct 2003 20:55:11 +0100
Received: from [127.0.0.1] ([144.254.74.55]) by xfe-ams-311.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Sun, 26 Oct 2003 20:55:10 +0100
Mime-Version: 1.0 (Apple Message framework v606)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
Content-Transfer-Encoding: quoted-printable
Cc: Pete Resnick <presnick@qualcomm.com>, Ted Hardie <hardie@qualcomm.com>,
        Ned Freed <ned.freed@mrochek.com>
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
Subject: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Sun, 26 Oct 2003 20:55:08 +0100
To: ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org
X-Mailer: Apple Mail (2.606)
X-OriginalArrivalTime: 26 Oct 2003 19:55:10.0612 (UTC) FILETIME=[101FC540:01C39BFB]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

At the IETF in Minneapolis, there will be a BOF on Internationalized=20
Email Addresses (IEA).

It is *preliminary* on the agenda on Monday, November 10, 2003 at=20
1530-1730.

Chairs:  Pete Resnick, Patrik F=E4ltstr=F6m
Mailing list:imaa@imc.org (other salient lists include uri@w3.org)
Agenda:

Agenda Bashing (Chairs)                5 min.
Topic Introduction (Chairs)           10 min.
Proposals
   IDNA-Based (Paul Hoffman)           15 min.
   Infrastructure-Based (John Klensin) 15 min.
   IRI-Based (Michel Suignard)         15 min.

Discussion                            60 min.

Topics for discussion:

   Are there other solutions which have been specified?

   The solutions present the problem at different scopes;

      Where should the IETF tackle it?

      Are some short-term, and other long-term?

      Can the solutions be staged or co-exist?

      If staged, how to migrate from one to another?

   What are the next steps for the IETF?


NB:  This BoF is exploratory in nature, and it is not intended that the=20=

IETF will finalize a decision in this venue.  It was proposed to foster=20=

a community discussion, not charter a working group or pick a winner.=20
If further work is required, step one would be identifying individuals=20=

willing to carry that work forward.

Reading material:
   draft-hoffman-imaa-03.txt
   draft-klensin-emailaddr-i18n-01.txt
   draft-duerst-iri-04.txt

Pete and myself hope people will come with a lot of constructive=20
comments and ideas.

         Patrik, co-chair of the bof




From owner-ietf@ietf.org  Mon Oct 27 00:50:32 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13612
	for <ietf-web-archive@odin.ietf.org>; Mon, 27 Oct 2003 00:50:32 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AE03K-0007MS-4r
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 00:36:30 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AE02A-0007Lx-Ul
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 00:35:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13146
	for <ietf@ietf.org>; Mon, 27 Oct 2003 00:35:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE028-0006dB-00
	for ietf@ietf.org; Mon, 27 Oct 2003 00:35:16 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE028-0006cp-00
	for ietf@ietf.org; Mon, 27 Oct 2003 00:35:16 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 6498961BFB; Mon, 27 Oct 2003 06:34:46 +0100 (CET)
Date: Sun, 26 Oct 2003 21:34:45 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Christian Huitema <huitema@windows.microsoft.com>, ietf@ietf.org,
        problem-statement@alvestrand.no
Subject: Re: Proposed statement quotes wrong numbers
Message-ID: <222145117.1067204085@[192.168.1.49]>
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA05D51E47@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References:  <DAC3FCB50E31C54987CD10797DA511BA05D51E47@WIN-MSG-10.wingroup.wi
 ndeploy.ntdev.microsoft.com>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Christian,

thanks for the correction.
We can quibble about the exact dates for a while, but I've made the quip 
quite a few times that the IETF has a fine scalable management structure, 
which will scale all the way to 700 participants...... so I agree that 
"order of magnitude" is a misnomer.

We do, however, have trouble, even at our currently reduced size.

                 Harald

--On 23. oktober 2003 22:40 -0700 Christian Huitema 
<huitema@windows.microsoft.com> wrote:

> The statement that you issued repeatedly mentions that the IETF rules
> and social contract were establish at a time when the IETF had 50 to 250
> or 50 to 300 members. The obvious implication is that, since the
> attendance has grown by an order of magnitude, the rules have to change
> significantly.
>
> The problem is that the 50-300 numbers are wrong. The original rules of
> the IETF were indeed devised in 1986, when the IETF was just created and
> had maybe 30-50 members. However, the current rules were designed in
> 1992-1993, in large part because the IETF had outgrown the previous
> rules. If you look at http://www.ietf.org/meetings/past.meetings.html,
> you will see that the attendance then was in the 500-700 range. Dave
> Clark's statement was made during the 24th IETF, held July 13-17, 1992
> in Cambridge, Massachusetts. There were 677 attendees.
>
> Since then, the IETF has grown, and then shrunk. The current size is
> about double the size of 1992. That is significant, but not quite an
> order of magnitude.
>
> -- Christian Huitema
>







From owner-ietf@ietf.org  Mon Oct 27 00:53:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13737
	for <ietf-web-archive@odin.ietf.org>; Mon, 27 Oct 2003 00:53:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AE0Cz-0007TC-PZ
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 00:46:29 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AE0BM-0007SQ-1J
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 00:44:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13416
	for <ietf@ietf.org>; Mon, 27 Oct 2003 00:44:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE0BJ-0006iW-00
	for ietf@ietf.org; Mon, 27 Oct 2003 00:44:45 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE0BJ-0006h7-00
	for ietf@ietf.org; Mon, 27 Oct 2003 00:44:45 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id ED03C61BFB; Mon, 27 Oct 2003 06:44:14 +0100 (CET)
Date: Sun, 26 Oct 2003 21:44:13 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: john.loughney@nokia.com, ietf@ietf.org, problem-statement@alvestrand.no
Subject: RE: IESG proposed statement on the IETF mission
Message-ID: <222713495.1067204653@[192.168.1.49]>
In-Reply-To: <DADF50F5EC506B41A0F375ABEB320636BF6CF4@esebe023.ntc.nokia.com>
References:  <DADF50F5EC506B41A0F375ABEB320636BF6CF4@esebe023.ntc.nokia.com>
X-Mailer: Mulberry/3.1.0b8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 24. oktober 2003 18:07 +0300 john.loughney@nokia.com wrote:

> Hi Harald,
>
> I'm going to pick on one statement, which other have as well.
>
>> It is important that this is "For the Internet,"  and does not include
>> everything that happens to use IP.  IP is being used in a myriad of
>> real-world applications, such as controlling street lights, but the
>> IETF does not standardize those applications.
>
> I almost feel that this should just be dropped from the statement.  My
> reasons being that I have been told by the IESG about protocol
> extensibility is that the IETF wants to have a tighter control over
> protocol
> extensibility, even for extensions thought to be for limited use
> or specific networks (for example, cellular networks).  The reason
> being is that once something is out there, it often starts to be used
> in ways which were not originally planned or used outside of its
> original 'limited use' plans.  Therefore, in order to ensure proper
> protocol behavior & interoperability, the IESG wants to manage
> extensibility.  This has been very true in SIP & Diameter, for example.

True. Nearly a year ago, we attempted to publish 
draft-iesg-vendor-extensions, to describe these problems in more detail - 
but we failed to get that finished.
>
> On the other hand, we see a protocol like RADIUS, which the IETF
> has never done a good job at working with or standardizing, being
> developed in 4 or more SDOs, and not in a colaborative manner.  This
> makes a big mess with the RADIUS spec, and RADIUS does seem like a
> protocol that has a big effect on the Internet.

You'll have no disagreement from me that RADIUS is a problem!

> So, in summary, the IESG has shown not to follow the above paragraph,
> sometimes even for good reasons.  I can't think of a way in which
> modify the paragraph to make it any better - because there will always
> be examples of work that the IETF choses to standardize (or not)
> which will violate that part of the mission.  Perhaps moving the
> 'for the internet to the previous paragraph is what is needed.

as I've said before - I don't think we can come up with a mission statement 
that retroactively blesses everything we've done well before, or 
retroactively curses everything we've done badly. And we do require 
flexibility to "do what's right". But without the ability to talk about 
what the mission of the IETF ... I think we'll do badly.

                       Harald





From owner-ietf@ietf.org  Mon Oct 27 07:18:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08985
	for <ietf-web-archive@odin.ietf.org>; Mon, 27 Oct 2003 07:18:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AE63r-0002m7-Gq
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 07:01:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AE61P-0002kz-Op
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 06:58:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08252
	for <ietf@ietf.org>; Mon, 27 Oct 2003 06:58:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE61N-0003bI-00
	for ietf@ietf.org; Mon, 27 Oct 2003 06:58:53 -0500
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE61M-0003aL-00
	for ietf@ietf.org; Mon, 27 Oct 2003 06:58:52 -0500
Received: from dfnjgl21 (12-237-229-250.client.attbi.com[12.237.229.250])
          by comcast.net (rwcrmhc12) with SMTP
          id <2003102711582301400nsntde>
          (Authid: sdawkins@comcast.net);
          Mon, 27 Oct 2003 11:58:23 +0000
Message-ID: <08fc01c39c81$a89d2110$0400a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf@ietf.org>, <problem-statement@alvestrand.no>
References: <DADF50F5EC506B41A0F375ABEB320636BF6CF4@esebe023.ntc.nokia.com> <222713495.1067204653@[192.168.1.49]>
Subject: Re: IESG proposed statement on the IETF mission
Date: Mon, 27 Oct 2003 05:58:38 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: "Harald Tveit Alvestrand" <harald@alvestrand.no>
>
> True. Nearly a year ago, we attempted to publish
> draft-iesg-vendor-extensions, to describe these problems in more
detail -
> but we failed to get that finished.

I should probably get out more, but I wasn't familiar with this draft.
I see that version 00 was announced. It looks to have been discussed
in a couple of posts on ccamp (and mpls? but I didn't look), and
revectored onto the main IETF discussion list, where it was the
subject of two posts. The draft says "The initial version of this
document was put together by the IESG", suggesting that they were
asking for input or other forms of help, but that didn't happen.

(In your opinion:) Was this a case of insufficient agreement, or a
case of insufficient cycles? Or something else?

Spencer




From owner-ietf@ietf.org  Mon Oct 27 11:00:44 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21635
	for <ietf-web-archive@odin.ietf.org>; Mon, 27 Oct 2003 11:00:44 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AE9ZZ-0003aq-79
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 10:46:25 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AE9YZ-0003YM-BJ
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 10:45:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20765;
	Mon, 27 Oct 2003 10:45:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE9YY-0006tc-00; Mon, 27 Oct 2003 10:45:22 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE9YX-0006tB-00; Mon, 27 Oct 2003 10:45:21 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9RFokf29900;
	Mon, 27 Oct 2003 07:50:46 -0800
Date: Mon, 27 Oct 2003 07:41:11 -0800
From: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: The Bat! (v2.00.22)
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <12228881609.20031027074111@brandenburg.com>
To: =?ISO-8859-1?B?UGF0cmlrIEbkbHRzdHL2bQ==?= <paf@cisco.com>
CC: ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, <lemonade@ietf.org>, <discuss@apps.ietf.org>,
        <ietf-imapext@imc.org>, <ietf-smtp@imc.org>,
        Pete Resnick <presnick@Qualcomm.Com>, Ted Hardie <hardie@Qualcomm.Com>,
        Ned Freed <ned.freed@mrochek.com>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Patrik,

Thanks for putting this BOF together.


PF>       Where should the IETF tackle it?

I am not sure I understand this question.  Please clarify.


PF>    What are the next steps for the IETF?

Would it help to have a draft charter for the meeting?  (I realize that the
presence of such different specifications makes a charter at least a bit
challenging, but it seems to help to have a draft, to make things concrete.)



d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Mon Oct 27 11:04:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21968
	for <ietf-web-archive@odin.ietf.org>; Mon, 27 Oct 2003 11:04:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AE9jG-0003hj-3l
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 10:56:26 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AE9cQ-0003dw-Dx
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 10:49:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21104
	for <ietf@ietf.org>; Mon, 27 Oct 2003 10:49:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE9cP-0006x6-00
	for ietf@ietf.org; Mon, 27 Oct 2003 10:49:21 -0500
Received: from mtiwmhc13.worldnet.att.net ([204.127.131.117])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE9cO-0006wO-00
	for ietf@ietf.org; Mon, 27 Oct 2003 10:49:21 -0500
Received: from bolaba (34.sanjose-01-02rs16rt.ca.dial-access.att.net[12.81.0.34])
          by worldnet.att.net (mtiwmhc13) with SMTP
          id <2003102715484211300890r3e>; Mon, 27 Oct 2003 15:48:44 +0000
Message-ID: <027e01c39ca1$31452a70$010aff0a@bolaba>
From: "todd glassey" <todd.glassey@worldnet.att.net>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        "Christian Huitema" <huitema@windows.microsoft.com>, <ietf@ietf.org>,
        <problem-statement@alvestrand.no>
References: <DAC3FCB50E31C54987CD10797DA511BA05D51E47@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com> <222145117.1067204085@[192.168.1.49]>
Subject: Re: Proposed statement quotes wrong numbers
Date: Mon, 27 Oct 2003 06:15:43 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald,

----- Original Message ----- 
From: "Harald Tveit Alvestrand" <harald@alvestrand.no>
To: "Christian Huitema" <huitema@windows.microsoft.com>; <ietf@ietf.org>;
<problem-statement@alvestrand.no>
Sent: Sunday, October 26, 2003 9:34 PM
Subject: Re: Proposed statement quotes wrong numbers


> Christian,
>
> thanks for the correction.
> We can quibble about the exact dates for a while, but I've made the quip
> quite a few times that the IETF has a fine scalable management structure,
> which will scale all the way to 700 participants...... so I agree that
> "order of magnitude" is a misnomer.
>
> We do, however, have trouble, even at our currently reduced size.
>
>                  Harald
>
> --On 23. oktober 2003 22:40 -0700 Christian Huitema
> <huitema@windows.microsoft.com> wrote:
>
> > The statement that you issued repeatedly mentions that the IETF rules
> > and social contract were establish at a time when the IETF had 50 to 250
> > or 50 to 300 members. The obvious implication is that, since the
> > attendance has grown by an order of magnitude, the rules have to change
> > significantly.
> >
> > The problem is that the 50-300 numbers are wrong. The original rules of
> > the IETF were indeed devised in 1986, when the IETF was just created and
> > had maybe 30-50 members. However, the current rules were designed in
> > 1992-1993, in large part because the IETF had outgrown the previous
> > rules. If you look at http://www.ietf.org/meetings/past.meetings.html,
> > you will see that the attendance then was in the 500-700 range. Dave
> > Clark's statement was made during the 24th IETF, held July 13-17, 1992
> > in Cambridge, Massachusetts. There were 677 attendees.

What was the attendance of the last meeting then? and also what then is the
sum total of unique EMail Addresses in the Lists then too? I.e. what is the
total size of the Vetting Community Resource that the IETF brings to the
Party as an enterprise/org???

> >
> > Since then, the IETF has grown, and then shrunk. The current size is
> > about double the size of 1992. That is significant, but not quite an
> > order of magnitude.
> >
> > -- Christian Huitema
> >
>
>
>
>




From owner-ietf@ietf.org  Mon Oct 27 11:09:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22504
	for <ietf-web-archive@odin.ietf.org>; Mon, 27 Oct 2003 11:09:57 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AE9jG-0003iH-UT
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 10:56:26 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AE9gm-0003eh-Qj
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 10:53:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21341;
	Mon, 27 Oct 2003 10:53:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE9gl-0006zm-00; Mon, 27 Oct 2003 10:53:51 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE9gl-0006zd-00; Mon, 27 Oct 2003 10:53:51 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 812AC14142; Mon, 27 Oct 2003 10:53:50 -0500 (EST)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 01580-02; Mon, 27 Oct 2003 10:53:49 -0500 (EST)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 7D86C14094; Mon, 27 Oct 2003 10:53:49 -0500 (EST)
Date: Mon, 27 Oct 2003 10:52:22 -0500
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: moore@cs.utk.edu, paf@cisco.com, ietf-imaa@imc.org, idn@ops.ietf.org,
        ietf-822@imc.org, ietf@ietf.org, ietf-pop3ext@imc.org,
        lemonade@ietf.org, discuss@apps.ietf.org, ietf-imapext@imc.org,
        ietf-smtp@imc.org, presnick@qualcomm.com, hardie@qualcomm.com,
        ned.freed@mrochek.com
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-Id: <20031027105222.4eae54fd.moore@cs.utk.edu>
In-Reply-To: <12228881609.20031027074111@brandenburg.com>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
	<12228881609.20031027074111@brandenburg.com>
X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> PF>    What are the next steps for the IETF?
> 
> Would it help to have a draft charter for the meeting?  

let's back up a step further.

what problem are we trying to solve here?

Keith



From owner-ietf@ietf.org  Mon Oct 27 12:07:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25406
	for <ietf-web-archive@odin.ietf.org>; Mon, 27 Oct 2003 12:07:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEAaZ-0005Lz-F8
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 11:51:31 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEANY-0005Fw-Rv
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 11:38:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23957;
	Mon, 27 Oct 2003 11:37:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEANW-00001p-00; Mon, 27 Oct 2003 11:38:02 -0500
Received: from 216-43-25-66.ip.mcleodusa.net ([216.43.25.66] helo=episteme-software.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEANV-00000G-00; Mon, 27 Oct 2003 11:38:01 -0500
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server X 3.2.3b1);
 Mon, 27 Oct 2003 10:37:25 -0600
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p06100300bbc2f94105a7@[216.43.25.67]>
In-Reply-To: <20031027105222.4eae54fd.moore@cs.utk.edu>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 <12228881609.20031027074111@brandenburg.com>
 <20031027105222.4eae54fd.moore@cs.utk.edu>
X-Mailer: Eudora [Macintosh version 6.1a2]
Date: Mon, 27 Oct 2003 10:37:21 -0600
To: Keith Moore <moore@cs.utk.edu>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Cc: Dave Crocker <dcrocker@brandenburg.com>, moore@cs.utk.edu, paf@cisco.com,
        ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org, hardie@qualcomm.com,
        ned.freed@mrochek.com
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

On 10/27/03 at 10:52 AM -0500, Keith Moore wrote:

>>DC: Would it help to have a draft charter for the meeting?

As was mentioned in the draft agenda at 
<http://www.ietf.org/ietf/03nov/iea.txt>, we want to simply start the 
discussion, not immediately attempt to charter a working group.

>let's back up a step further.
>
>what problem are we trying to solve here?

Please have a look at draft-hoffman-imaa, 
draft-klensin-emailaddr-i18n, and draft-duerst-iri. Certainly the 
first two have very explicit descriptions of the problem.

pr
-- 
Pete Resnick <http://wwww.qualcomm.com/~presnick/>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102



From owner-ietf@ietf.org  Mon Oct 27 12:16:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25954
	for <ietf-web-archive@odin.ietf.org>; Mon, 27 Oct 2003 12:16:06 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEAoy-0005VW-ED
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 12:06:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEAjN-0005PN-HB
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 12:00:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25120;
	Mon, 27 Oct 2003 12:00:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEAjM-0000QI-00; Mon, 27 Oct 2003 12:00:36 -0500
Received: from panoramix.hexago.com ([209.71.226.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEAjH-0000QE-00; Mon, 27 Oct 2003 12:00:35 -0500
Received: from localhost (retro.viagenie.qc.ca [IPv6:3ffe:b00:c18:3::22])
	(authenticated bits=0)
	by panoramix.hexago.com (8.12.8/8.12.8) with ESMTP id h9RH0M6r005886;
	Mon, 27 Oct 2003 12:00:22 -0500 (EST)
Date: Mon, 27 Oct 2003 12:00:01 -0500
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
To: Keith Moore <moore@cs.utk.edu>, Dave Crocker <dcrocker@brandenburg.com>
cc: paf@cisco.com, ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org,
        ietf@ietf.org, ietf-pop3ext@imc.org, lemonade@ietf.org,
        discuss@apps.ietf.org, ietf-imapext@imc.org, ietf-smtp@imc.org,
        presnick@qualcomm.com, hardie@qualcomm.com, ned.freed@mrochek.com
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-ID: <575390000.1067274001@classic.viagenie.qc.ca>
In-Reply-To: <20031027105222.4eae54fd.moore@cs.utk.edu>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 	<12228881609.20031027074111@brandenburg.com>
 <20031027105222.4eae54fd.moore@cs.utk.edu>
X-Mailer: Mulberry/3.1.0b8 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



-- Monday, October 27, 2003 10:52:22 -0500 Keith Moore <moore@cs.utk.edu>
wrote/a ecrit:

>> PF>    What are the next steps for the IETF?
>> 
>> Would it help to have a draft charter for the meeting?  
> 
> let's back up a step further.
> 
> what problem are we trying to solve here?

to me, that (problem we are trying to solve) would be part of the
introduction in the charter...

so I guess some initial proposal for:
- what are we trying to solve
- what would be the way to solve it

would be a good starting point together with the "state-of-the-art"
presentations.

Marc.


> 
> Keith



------------------------------------------
Marc Blanchet
Hexago
tel: +1-418-266-5533x225
------------------------------------------
http://www.freenet6.net: IPv6 connectivity
------------------------------------------



From owner-ietf@ietf.org  Mon Oct 27 13:59:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00499
	for <ietf-web-archive@odin.ietf.org>; Mon, 27 Oct 2003 13:59:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AECR3-0007SP-EI
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 13:49:49 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AECN3-0007OV-Bl
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 13:45:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29652;
	Mon, 27 Oct 2003 13:45:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AECMz-0001tJ-00; Mon, 27 Oct 2003 13:45:37 -0500
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AECMy-0001tA-00; Mon, 27 Oct 2003 13:45:36 -0500
Received: from localhost (klutz [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 4F4301401D; Mon, 27 Oct 2003 13:45:34 -0500 (EST)
Received: from klutz.cs.utk.edu ([127.0.0.1])
 by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 25223-11; Mon, 27 Oct 2003 13:45:33 -0500 (EST)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 3AA6C13FEC; Mon, 27 Oct 2003 13:45:33 -0500 (EST)
Date: Mon, 27 Oct 2003 13:44:03 -0500
From: Keith Moore <moore@cs.utk.edu>
To: Mark Crispin <mrc@CAC.Washington.EDU>
Cc: moore@cs.utk.edu, dcrocker@brandenburg.com, paf@cisco.com,
        ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org, presnick@qualcomm.com,
        hardie@qualcomm.com, ned.freed@mrochek.com
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-Id: <20031027134403.5eaaee9e.moore@cs.utk.edu>
In-Reply-To: <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
	<12228881609.20031027074111@brandenburg.com>
	<20031027105222.4eae54fd.moore@cs.utk.edu>
	<Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new and ClamAV at cs.utk.edu
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Mark,

Thanks for taking a stab at a problem statement.  I'd like to drill down
on this just a bit.

What is the source of the "growing need"?  Is it:

a. for users of many languages (particularly those not using Latin alphabets)
   email addresses are difficult to remember
b. for users of many languages (particularly those not using Latin alphabets)
   email addresses are difficult to transcribe or type
c. users want to use their names in email addresses
d. users are confused by apparently arbitrary restrictions on use of 
   characters in email addresses, and this leads to mistakes
e. on computer systems employing non-ASCII names for other purposes (e.g.
   login or account names) these do not map well to ASCII email addresses

or something else that I don't see?

> As presently constituted, email addresses are limited to the 26 Latin
> alphabetics, 10 digits, and a limited number of special characters in
> the ASCII character set.  There is a growing need to use additional
> characters, specifically Latin characters with diacriticals and
> non-Latin characters, in email addresses to better serve the needs of
> the multi-national Internet community.  However, the restrictions of
> ASCII email addresses have served as a "lingua franca" since everybody
> can enter ASCII email addresses, and there is an ongoing need for this
> as well.  The problem to be solved is the resolution of these two
> needs.



From owner-ietf@ietf.org  Mon Oct 27 14:20:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01486
	for <ietf-web-archive@odin.ietf.org>; Mon, 27 Oct 2003 14:20:11 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEChp-0008CG-8C
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 14:07:09 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEAwD-0005v2-G7
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 12:13:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25813;
	Mon, 27 Oct 2003 12:13:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEAwC-0000fv-00; Mon, 27 Oct 2003 12:13:52 -0500
Received: from mxout2.cac.washington.edu ([140.142.33.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEAwB-0000fk-00; Mon, 27 Oct 2003 12:13:51 -0500
Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201])
	by mxout2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9RHDThu011833;
	Mon, 27 Oct 2003 09:13:30 -0800
Received: from localhost (mrc@localhost)
	by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9RHDTew015664;
	Mon, 27 Oct 2003 09:13:29 -0800
Date: Mon, 27 Oct 2003 09:13:29 -0800 (PST)
From: Mark Crispin <mrc@CAC.Washington.EDU>
To: Keith Moore <moore@cs.utk.edu>
cc: Dave Crocker <dcrocker@brandenburg.com>, paf@cisco.com, ietf-imaa@imc.org,
        idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org, presnick@qualcomm.com,
        hardie@qualcomm.com, ned.freed@mrochek.com
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <20031027105222.4eae54fd.moore@cs.utk.edu>
Message-ID: <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 <12228881609.20031027074111@brandenburg.com> <20031027105222.4eae54fd.moore@cs.utk.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 27 Oct 2003, Keith Moore wrote:
> what problem are we trying to solve here?

I agree with Keith.  This isn't to say that I dispute that there is a
problem to be solved -- indeed, I think that the problem is apparent to
all -- but we must have a problem statement that we all agree upon before
we even think about solutions.

I don't think that references to drafts of proposed solutions suffice as a
problem statement.  Leaving aside questions of possible bias (= present a
problem in such a way that this is the obvious best solution), having the
problem statement in a draft (which by its nature is an ephemeral
document) muddies the issues.

The problem statement should consist of a single paragraph (and preferably
in one or two sentences), separate from any proposed solution, and stated
in a charter which is approved by everyone.

Here's a start at such a statement:

As presently constituted, email addresses are limited to the 26 Latin
alphabetics, 10 digits, and a limited number of special characters in the
ASCII character set.  There is a growing need to use additional
characters, specifically Latin characters with diacriticals and non-Latin
characters, in email addresses to better serve the needs of the
multi-national Internet community.  However, the restrictions of ASCII
email addresses have served as a "lingua franca" since everybody can enter
ASCII email addresses, and there is an ongoing need for this as well.  The
problem to be solved is the resolution of these two needs.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.





From owner-ietf@ietf.org  Mon Oct 27 14:24:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01814
	for <ietf-web-archive@odin.ietf.org>; Mon, 27 Oct 2003 14:24:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEChp-0008Cd-Gf
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 14:07:09 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEBCq-0006RA-8j
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 12:31:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26541;
	Mon, 27 Oct 2003 12:30:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEBCp-0000vG-00; Mon, 27 Oct 2003 12:31:03 -0500
Received: from p1.spindry.com ([64.5.41.83] helo=mx.spindry.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEBCo-0000vC-00; Mon, 27 Oct 2003 12:31:02 -0500
Received: from filenet-gw.filenet.com ([198.3.8.1] helo=ATTABOY.carpenter.ORG)
	by mx.spindry.com with smtp (Exim 3.36 #2)
	id 1AEBCg-0005Z8-00; Mon, 27 Oct 2003 12:30:54 -0500
Date: Mon, 27 Oct 2003 09:30:46 -0800
Message-ID: <4027-Mon27Oct2003093046-0800-bill@carpenter.ORG>
X-Mailer: 21.1 (patch 9) "Canyonlands" XEmacs Lucid (via feedmail 11-beta-2 I) wjc loop;
	VM 6.71 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: bill-imc@carpenter.ORG (WJCarpenter)
To: ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
	<12228881609.20031027074111@brandenburg.com>
	<20031027105222.4eae54fd.moore@cs.utk.edu>
	<Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

mc> As presently constituted, email addresses are limited to the 26
mc> Latin alphabetics, 10 digits, and a limited number of special
mc> characters in the ASCII character set.  There is a growing need to

upper and lower case alphabetics
-- 
bill-imc@carpenter.ORG (WJCarpenter)    PGP 0x91865119
38 95 1B 69 C9 C6 3D 25    73 46 32 04 69 D6 ED F3






From owner-ietf@ietf.org  Mon Oct 27 15:03:00 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04076
	for <ietf-web-archive@odin.ietf.org>; Mon, 27 Oct 2003 15:03:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEDPc-0001dY-SX
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 14:52:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AED7t-0001JG-Es
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 14:34:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02665
	for <ietf@ietf.org>; Mon, 27 Oct 2003 14:33:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AED7s-0002qS-00
	for ietf@ietf.org; Mon, 27 Oct 2003 14:34:04 -0500
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AED7r-0002q6-00
	for ietf@ietf.org; Mon, 27 Oct 2003 14:34:04 -0500
Received: by sa.vix.com (Postfix, from userid 716)
	id F2D1013967; Mon, 27 Oct 2003 19:33:31 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Proposed statement quotes wrong numbers
References: <222145117.1067204085@[192.168.1.49]>
From: Paul Vixie <vixie@vix.com>
Date: 27 Oct 2003 19:33:31 +0000
In-Reply-To: <222145117.1067204085@[192.168.1.49]>
Message-ID: <g3he1ucw6s.fsf@sa.vix.com>
Lines: 3
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

> We do, however, have trouble, even at our currently reduced size.

yes.  and if we ever start to succeed again, the size will increase again.



From owner-ietf@ietf.org  Mon Oct 27 15:21:08 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06501
	for <ietf-web-archive@odin.ietf.org>; Mon, 27 Oct 2003 15:21:08 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEDPf-0001fE-OF
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 14:52:27 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEDHb-0001Yk-9N
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 14:44:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03167;
	Mon, 27 Oct 2003 14:43:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEDHZ-0002yw-00; Mon, 27 Oct 2003 14:44:05 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEDHZ-0002yC-00; Mon, 27 Oct 2003 14:44:05 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id 49062164; Mon, 27 Oct 2003 14:42:18 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
Organization: Secure Software -- http://www.securesw.com/
To: bill-imc@carpenter.ORG (WJCarpenter), ietf-imaa@imc.org, idn@ops.ietf.org,
        ietf-822@imc.org, ietf@ietf.org, ietf-pop3ext@imc.org,
        lemonade@ietf.org, discuss@apps.ietf.org, ietf-imapext@imc.org,
        ietf-smtp@imc.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Mon, 27 Oct 2003 14:43:09 -0500
User-Agent: KMail/1.5.2
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com> <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu> <4027-Mon27Oct2003093046-0800-bill@carpenter.ORG>
In-Reply-To: <4027-Mon27Oct2003093046-0800-bill@carpenter.ORG>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310271443.09779.spamtrap.ietf@dja.mailme.org>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Mon October 27 2003 12:30, WJCarpenter wrote:

 > mc> As presently constituted, email addresses are limited to the 26
 > mc> Latin alphabetics, 10 digits, and a limited number of special
 > mc> characters in the ASCII character set.  There is a growing need
 > to
 >
 > upper and lower case alphabetics

Yes, but with either of those two sets (generally) considered equivalent 
to the other, boiling down to effectively 26 choices.

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
Web: http://destined.to/program http://listen.to/davearonson




From owner-ietf@ietf.org  Tue Oct 28 01:47:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16958
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 01:47:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEJq9-0003mu-CF
	for ietf-list@asgard.ietf.org; Mon, 27 Oct 2003 21:44:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEFSm-0005jB-Vy
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 17:03:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18015
	for <ietf@ietf.org>; Mon, 27 Oct 2003 17:03:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEFSl-0006o9-00
	for ietf@ietf.org; Mon, 27 Oct 2003 17:03:47 -0500
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEFSk-0006n0-00
	for ietf@ietf.org; Mon, 27 Oct 2003 17:03:47 -0500
Received: from inet-vrs-04.redmond.corp.microsoft.com ([157.54.8.149]) by mail4.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 27 Oct 2003 14:03:15 -0800
Received: from 157.54.8.155 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 27 Oct 2003 14:03:14 -0800
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 27 Oct 2003 14:03:05 -0800
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 27 Oct 2003 14:03:13 -0800
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Mon, 27 Oct 2003 14:03:04 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7097.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Proposed statement quotes wrong numbers
Date: Mon, 27 Oct 2003 14:00:56 -0800
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA05DCE3DE@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Proposed statement quotes wrong numbers
thread-index: AcOcTAjU4nRN2fz/QF2A/BNNGoUZ4AAiStEg
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>, <ietf@ietf.org>,
        <problem-statement@alvestrand.no>
X-OriginalArrivalTime: 27 Oct 2003 22:03:04.0051 (UTC) FILETIME=[18436430:01C39CD6]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

In fact, if you go back to the archives of the 1992 discussions, it was
perceived then that the previous structure did not scale. For example,
the IAB was in charge of reviewing every RFC before it could be
published, and as the number of WG increased that became a bottleneck. A
lot of the 1992 effort was about designing a structure that would scale
better -- i.e. scale for much more than the 600-700 participants at the
time.

I am not sure that the IETF problems are primarily a scaling issue.

> -----Original Message-----
> From: Harald Tveit Alvestrand [mailto:harald@alvestrand.no]
> Sent: Sunday, October 26, 2003 9:35 PM
> To: Christian Huitema; ietf@ietf.org; problem-statement@alvestrand.no
> Subject: Re: Proposed statement quotes wrong numbers
>=20
> Christian,
>=20
> thanks for the correction.
> We can quibble about the exact dates for a while, but I've made the
quip
> quite a few times that the IETF has a fine scalable management
structure,
> which will scale all the way to 700 participants...... so I agree that
> "order of magnitude" is a misnomer.
>=20
> We do, however, have trouble, even at our currently reduced size.
>=20
>                  Harald
>=20
> --On 23. oktober 2003 22:40 -0700 Christian Huitema
> <huitema@windows.microsoft.com> wrote:
>=20
> > The statement that you issued repeatedly mentions that the IETF
rules
> > and social contract were establish at a time when the IETF had 50 to
250
> > or 50 to 300 members. The obvious implication is that, since the
> > attendance has grown by an order of magnitude, the rules have to
change
> > significantly.
> >
> > The problem is that the 50-300 numbers are wrong. The original rules
of
> > the IETF were indeed devised in 1986, when the IETF was just created
and
> > had maybe 30-50 members. However, the current rules were designed in
> > 1992-1993, in large part because the IETF had outgrown the previous
> > rules. If you look at
http://www.ietf.org/meetings/past.meetings.html,
> > you will see that the attendance then was in the 500-700 range. Dave
> > Clark's statement was made during the 24th IETF, held July 13-17,
1992
> > in Cambridge, Massachusetts. There were 677 attendees.
> >
> > Since then, the IETF has grown, and then shrunk. The current size is
> > about double the size of 1992. That is significant, but not quite an
> > order of magnitude.
> >
> > -- Christian Huitema
> >
>=20
>=20
>=20




From owner-ietf@ietf.org  Tue Oct 28 03:40:09 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08972
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 03:40:09 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEM0m-0001Cz-Gg
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 00:03:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEH1U-0004xw-PC
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 18:43:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28798
	for <ietf@ietf.org>; Mon, 27 Oct 2003 18:43:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEH1S-00023C-00
	for ietf@ietf.org; Mon, 27 Oct 2003 18:43:43 -0500
Received: from sentosa.post1.com ([202.27.17.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1AEH1R-00022V-00
	for ietf@ietf.org; Mon, 27 Oct 2003 18:43:42 -0500
Received: (qmail 5838 invoked from network); 28 Oct 2003 00:01:35 -0000
Received: from rifcd-04p117.ppp.odn.ad.jp (HELO pobox.org.sg) (211.3.24.117)
  by sentosa.post1.com with SMTP; 28 Oct 2003 00:01:35 -0000
Message-ID: <3F9CFC5D.7060509@pobox.org.sg>
Date: Mon, 27 Oct 2003 19:07:09 +0800
From: James Seng <jseng@pobox.org.sg>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en, zh-cn, zh-tw, ja, ko
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
CC: ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org,
        Pete Resnick <presnick@qualcomm.com>, Ted Hardie <hardie@qualcomm.com>,
        Ned Freed <ned.freed@mrochek.com>
Subject: Re: [idn] FYI: BOF on Internationalized Email Addresses (IEA)
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
In-Reply-To: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id SAA28801
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

I seen John and Paul proposal but I have not seen Michel. Is there a=20
draft that I can read up?

ps: I wont be able to join the meeting but I am interested in the subject.

-James Seng

Patrik F=E4ltstr=F6m wrote:

> At the IETF in Minneapolis, there will be a BOF on Internationalized=20
> Email Addresses (IEA).
>=20
> It is *preliminary* on the agenda on Monday, November 10, 2003 at=20
> 1530-1730.
>=20
> Chairs:  Pete Resnick, Patrik F=E4ltstr=F6m
> Mailing list:imaa@imc.org (other salient lists include uri@w3.org)
> Agenda:
>=20
> Agenda Bashing (Chairs)                5 min.
> Topic Introduction (Chairs)           10 min.
> Proposals
>   IDNA-Based (Paul Hoffman)           15 min.
>   Infrastructure-Based (John Klensin) 15 min.
>   IRI-Based (Michel Suignard)         15 min.
>=20
> Discussion                            60 min.
>=20
> Topics for discussion:
>=20
>   Are there other solutions which have been specified?
>=20
>   The solutions present the problem at different scopes;
>=20
>      Where should the IETF tackle it?
>=20
>      Are some short-term, and other long-term?
>=20
>      Can the solutions be staged or co-exist?
>=20
>      If staged, how to migrate from one to another?
>=20
>   What are the next steps for the IETF?
>=20
>=20
> NB:  This BoF is exploratory in nature, and it is not intended that the=
=20
> IETF will finalize a decision in this venue.  It was proposed to foster=
=20
> a community discussion, not charter a working group or pick a winner. I=
f=20
> further work is required, step one would be identifying individuals=20
> willing to carry that work forward.
>=20
> Reading material:
>   draft-hoffman-imaa-03.txt
>   draft-klensin-emailaddr-i18n-01.txt
>   draft-duerst-iri-04.txt
>=20
> Pete and myself hope people will come with a lot of constructive=20
> comments and ideas.
>=20
>         Patrik, co-chair of the bof
>=20
>=20
>=20
>=20
>=20





From owner-ietf@ietf.org  Tue Oct 28 03:46:04 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09256
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 03:46:04 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEN4Q-0002JG-AJ
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 01:11:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEHZw-0005W6-3o
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 19:19:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00315
	for <ietf@ietf.org>; Mon, 27 Oct 2003 19:19:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEHZu-0002dn-00
	for ietf@ietf.org; Mon, 27 Oct 2003 19:19:18 -0500
Received: from mtiwmhc11.worldnet.att.net ([204.127.131.115])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEHZu-0002d9-00
	for ietf@ietf.org; Mon, 27 Oct 2003 19:19:18 -0500
Received: from bolaba (141.sanjose-05-10rs16rt.ca.dial-access.att.net[12.81.6.141])
          by worldnet.att.net (mtiwmhc11) with SMTP
          id <2003102800183611100iehk9e>; Tue, 28 Oct 2003 00:18:38 +0000
Message-ID: <000701c39ce8$6917f7b0$010aff0a@bolaba>
From: "todd glassey" <todd.glassey@worldnet.att.net>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>, <ietf@ietf.org>,
        <problem-statement@alvestrand.no>
References: <DADF50F5EC506B41A0F375ABEB320636BF6CF4@esebe023.ntc.nokia.com> <222713495.1067204653@[192.168.1.49]>
Subject: Re: IESG proposed statement on the IETF mission
Date: Mon, 27 Oct 2003 15:56:34 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald - I would agree that you are right here that the IETF's mission
process and in fact operations have fluttered in the breeze but the breeze
was caused by whoever was chair at the time's running by or away from the
key issue that they as the chair were given the ability because of a very
weak charter and very ambiguous processes (may instead of must everywhere)
create whatever it is they wanted. The issue is that the wants and mandates
of the chair's have changed over the years and so the IETF has changed in
response to that.


What that tends to indicate is that the IETF is responsive to changes in its
management's desires but not in the proletariat's... So then what I suggest
is the answer is a more rigidized standards process and in particular a set
of unambiguous policies and procedures that are at least modeled if not
tested before being released. And that are in and of themselves the same for
all they are applied to or around.

Todd Glassey
----- Original Message ----- 
From: "Harald Tveit Alvestrand" <harald@alvestrand.no>
To: <john.loughney@nokia.com>; <ietf@ietf.org>;
<problem-statement@alvestrand.no>
Sent: Sunday, October 26, 2003 9:44 PM
Subject: RE: IESG proposed statement on the IETF mission


>
>
> --On 24. oktober 2003 18:07 +0300 john.loughney@nokia.com wrote:
>
> > Hi Harald,
> >
> > I'm going to pick on one statement, which other have as well.
> >
> >> It is important that this is "For the Internet,"  and does not include
> >> everything that happens to use IP.  IP is being used in a myriad of
> >> real-world applications, such as controlling street lights, but the
> >> IETF does not standardize those applications.
> >
> > I almost feel that this should just be dropped from the statement.  My
> > reasons being that I have been told by the IESG about protocol
> > extensibility is that the IETF wants to have a tighter control over
> > protocol
> > extensibility, even for extensions thought to be for limited use
> > or specific networks (for example, cellular networks).  The reason
> > being is that once something is out there, it often starts to be used
> > in ways which were not originally planned or used outside of its
> > original 'limited use' plans.  Therefore, in order to ensure proper
> > protocol behavior & interoperability, the IESG wants to manage
> > extensibility.  This has been very true in SIP & Diameter, for example.
>
> True. Nearly a year ago, we attempted to publish
> draft-iesg-vendor-extensions, to describe these problems in more detail -
> but we failed to get that finished.
> >
> > On the other hand, we see a protocol like RADIUS, which the IETF
> > has never done a good job at working with or standardizing, being
> > developed in 4 or more SDOs, and not in a colaborative manner.  This
> > makes a big mess with the RADIUS spec, and RADIUS does seem like a
> > protocol that has a big effect on the Internet.
>
> You'll have no disagreement from me that RADIUS is a problem!
>
> > So, in summary, the IESG has shown not to follow the above paragraph,
> > sometimes even for good reasons.  I can't think of a way in which
> > modify the paragraph to make it any better - because there will always
> > be examples of work that the IETF choses to standardize (or not)
> > which will violate that part of the mission.  Perhaps moving the
> > 'for the internet to the previous paragraph is what is needed.
>
> as I've said before - I don't think we can come up with a mission
statement
> that retroactively blesses everything we've done well before, or
> retroactively curses everything we've done badly. And we do require
> flexibility to "do what's right". But without the ability to talk about
> what the mission of the IETF ... I think we'll do badly.
>
>                        Harald
>
>




From owner-ietf@ietf.org  Tue Oct 28 03:57:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10035
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 03:57:17 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEN4U-0002PU-4R
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 01:11:14 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEILh-0002nM-Ql
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 20:08:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02178;
	Mon, 27 Oct 2003 20:08:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEILf-0003Mo-00; Mon, 27 Oct 2003 20:08:40 -0500
Received: from panoramix.hexago.com ([209.71.226.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEILf-0003Mg-00; Mon, 27 Oct 2003 20:08:39 -0500
Received: from localhost (retro.viagenie.qc.ca [IPv6:3ffe:b00:c18:3::22])
	(authenticated bits=0)
	by panoramix.hexago.com (8.12.8/8.12.8) with ESMTP id h9S18c6r006354;
	Mon, 27 Oct 2003 20:08:39 -0500 (EST)
Date: Mon, 27 Oct 2003 20:08:25 -0500
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
To: Dave Crocker <dcrocker@brandenburg.com>, ietf-imaa@imc.org,
        idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-ID: <839550000.1067303305@classic.viagenie.qc.ca>
In-Reply-To: <355752681.20031027161925@brandenburg.com>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 <12228881609.20031027074111@brandenburg.com>
 <20031027105222.4eae54fd.moore@cs.utk.edu>
 <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
 <355752681.20031027161925@brandenburg.com>
X-Mailer: Mulberry/3.1.0b8 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

- good start!
- timeline seems pretty agressive... will see.
- would probably good to have a requirement document upfront. Might not the
same way that idn requirement ends up, but a narrow-implementable
requirement would help to have a concensus (hopefully) on what needs to be
done. 
- while the idn req went not that good, now that we have experience, I
think we should try to be better and have one.

I know I might start some debate with this, but still think it is the best
way to go...

- would be useful to have some reference to idn (idna) in the charter, as
background work. the developers and users will have to take care of "both"
(ie. idn and imail) in the email infrastructure.

Marc.

-- Monday, October 27, 2003 16:19:25 -0800 Dave Crocker <dhc@dcrocker.net>
wrote/a ecrit:

> Folks,
> 
> On the theory that discussions go better when they have a concrete
> deliverable, here is a proposed charter for a proposed working group.
> 
> The following started with Mark Crispin's text, although it might not
> look it. Besides the usual goals for a charter, the following text
> attempts to specify the problem domain in the narrowest feasible form
> that is valid. If anyone thinks the scope is too narrow, they need to
> explain why.
> 
> 
> 
> DRAFT CHARTER
> 
> Mail Internationalised Local-Part (MILP)
> ---------------------------------
> 
> The <local-part> portion of RFC2822 and <Local-part> portion of RFC2821
> mail addresses are restricted to a subset of ASCII. This poses a
> fundamental barrier for users needing mail addresses to be expressed in a
> richer set of characters, such as Latin characters with diacriticals and
> the many Asian characters. The goal of the current work is to add
> local-part support for these additional characters, while preserving the
> large, installed base of ASCII usage.
> 
> The group will take:
> 
>    draft-hoffman-imaa-03.txt
>    draft-klensin-emailaddr-i18n-01.txt
>    draft-duerst-iri-04.txt
> 
> as input to discussions.
> 
> The group will pay particular attention to barriers to adoption and
> utility, as well as any impact the new scheme might have on the existing
> base of Internet mail usage.
> 
> 
> Milestones
> ----------
> 
> Nov, 03:  BOF
> 
> Dec, 03:  WG chartered
> 
> Feb, 03:  Initial draft of working group specifications.
> 
> Jun, 03:  Specifications submitted for IETF approval
> 
> 
> d/
> --
>  Dave Crocker <dcrocker-at-brandenburg-dot-com>
>  Brandenburg InternetWorking <www.brandenburg.com>
>  Sunnyvale, CA  USA <tel:+1.408.246.8253>
> 



------------------------------------------
Marc Blanchet
Hexago
tel: +1-418-266-5533x225
------------------------------------------
http://www.freenet6.net: IPv6 connectivity
------------------------------------------



From owner-ietf@ietf.org  Tue Oct 28 04:02:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10438
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 04:02:22 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AENFE-0005T7-8N
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 01:22:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEJp2-0003jF-Kw
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 21:43:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04675;
	Mon, 27 Oct 2003 21:42:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEJp0-0004Pu-00; Mon, 27 Oct 2003 21:43:02 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEJoz-0004Pp-00; Mon, 27 Oct 2003 21:43:01 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9S2mVf18218;
	Mon, 27 Oct 2003 18:48:31 -0800
Date: Mon, 27 Oct 2003 18:42:26 -0800
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v2.00.22)
Reply-To: dcrocker@brandenburg.com
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <14814332829.20031027184226@brandenburg.com>
To: Roy Badami <roy@gnomon.org.uk>
CC: ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, <lemonade@ietf.org>, <discuss@apps.ietf.org>,
        <ietf-imapext@imc.org>, <ietf-smtp@imc.org>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <16285.48493.496028.516294@moriarty.gnomon.org.uk>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 <12228881609.20031027074111@brandenburg.com>
 <20031027105222.4eae54fd.moore@cs.utk.edu>
 <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
 <355752681.20031027161925@brandenburg.com>
 <16285.48493.496028.516294@moriarty.gnomon.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Roy,

 >> Mail Internationalised Local-Part (MILP)

RB> Even though, given IDNA now exists as a proposed standard, the main
RB> issues relate to the local part, the issue under discussion is that of
RB> internationalized mail addresses, not just internationalized
RB> local-parts.

Really?  What work needs to be done, except for local part?  IDNA takes care
of the right-hand side.

So what is there to do about "internationalized mail addresses" other than the
local part?

RB> Restricting the disucssion to local-parts runs the risk of excluding
RB> other potentially relevent issues.  For instance, one of the issues
RB> that has been discussed on the IMAA list is whether full-width at
RB> should be recognized in an internationalized mail address.

full-width _where_?  somewhere other than local part?

if yes, then how can that be practical?  if no, then the charter does not
preclude their use.  (if you think otherwise, please explain.)

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Tue Oct 28 04:34:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09257
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 03:46:04 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEN4Q-0002JW-TM
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 01:11:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEHbg-0005Xe-7m
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 19:21:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00363;
	Mon, 27 Oct 2003 19:20:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEHbe-0002f4-00; Mon, 27 Oct 2003 19:21:06 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEHbd-0002ez-00; Mon, 27 Oct 2003 19:21:05 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9S0Qaf09143;
	Mon, 27 Oct 2003 16:26:36 -0800
Date: Mon, 27 Oct 2003 16:19:25 -0800
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v2.00.22)
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <355752681.20031027161925@brandenburg.com>
To: ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, <lemonade@ietf.org>, <discuss@apps.ietf.org>,
        <ietf-imapext@imc.org>, <ietf-smtp@imc.org>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 <12228881609.20031027074111@brandenburg.com>
 <20031027105222.4eae54fd.moore@cs.utk.edu>
 <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

On the theory that discussions go better when they have a concrete
deliverable, here is a proposed charter for a proposed working group.

The following started with Mark Crispin's text, although it might not look it.
Besides the usual goals for a charter, the following text attempts to specify
the problem domain in the narrowest feasible form that is valid. If anyone
thinks the scope is too narrow, they need to explain why.



DRAFT CHARTER

Mail Internationalised Local-Part (MILP)
---------------------------------

The <local-part> portion of RFC2822 and <Local-part> portion of RFC2821 mail
addresses are restricted to a subset of ASCII. This poses a fundamental
barrier for users needing mail addresses to be expressed in a richer set of
characters, such as Latin characters with diacriticals and the many Asian
characters. The goal of the current work is to add local-part support for
these additional characters, while preserving the large, installed base of
ASCII usage.

The group will take:

   draft-hoffman-imaa-03.txt
   draft-klensin-emailaddr-i18n-01.txt
   draft-duerst-iri-04.txt

as input to discussions.

The group will pay particular attention to barriers to adoption and utility,
as well as any impact the new scheme might have on the existing base of
Internet mail usage.


Milestones
----------

Nov, 03:  BOF

Dec, 03:  WG chartered

Feb, 03:  Initial draft of working group specifications.

Jun, 03:  Specifications submitted for IETF approval


d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Tue Oct 28 04:54:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12525
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 04:54:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEPzc-0005KI-1W
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 04:18:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEOAb-00084w-Ne
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 02:21:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02639;
	Tue, 28 Oct 2003 02:21:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEOAZ-0002hD-00; Tue, 28 Oct 2003 02:21:35 -0500
Received: from 216-43-25-66.ip.mcleodusa.net ([216.43.25.66] helo=episteme-software.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEOAY-0002e4-00; Tue, 28 Oct 2003 02:21:34 -0500
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server X 3.2.3b1);
 Tue, 28 Oct 2003 01:21:01 -0600
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p06100309bbc3c83a8871@[216.43.25.67]>
In-Reply-To: <14814332829.20031027184226@brandenburg.com>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 <12228881609.20031027074111@brandenburg.com>
 <20031027105222.4eae54fd.moore@cs.utk.edu>
 <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
 <355752681.20031027161925@brandenburg.com>
 <16285.48493.496028.516294@moriarty.gnomon.org.uk>
 <14814332829.20031027184226@brandenburg.com>
X-Mailer: Eudora [Macintosh version 6.1a2]
Date: Tue, 28 Oct 2003 01:20:58 -0600
To: dcrocker@brandenburg.com
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Cc: Roy Badami <roy@gnomon.org.uk>, ietf-imaa@imc.org, idn@ops.ietf.org,
        ietf-822@imc.org, ietf@ietf.org, ietf-pop3ext@imc.org,
        <lemonade@ietf.org>, <discuss@apps.ietf.org>, <ietf-imapext@imc.org>,
        <ietf-smtp@imc.org>, Dave Crocker <dhc@dcrocker.net>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

On 10/27/03 at 6:42 PM -0800, Dave Crocker wrote:

>RB> Even though, given IDNA now exists as a proposed standard, the main
>RB> issues relate to the local part, the issue under discussion is that of
>RB> internationalized mail addresses, not just internationalized
>RB> local-parts.
>
>Really?  What work needs to be done, except for local part?  IDNA takes care
>of the right-hand side.

Please review John Klensin's draft before making these kinds of assumptions.

>RB> Restricting the disucssion to local-parts runs the risk of excluding
>RB> other potentially relevent issues.

I agree. Limiting discussion at this point to local-part does not 
take into account some of the possibilities.

pr
-- 
Pete Resnick <http://wwww.qualcomm.com/~presnick/>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102



From owner-ietf@ietf.org  Tue Oct 28 04:55:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12588
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 04:55:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEPzt-0005vQ-Pi
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 04:18:41 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEPNm-0000RF-N7
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 03:39:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08937
	for <ietf@ietf.org>; Tue, 28 Oct 2003 03:39:07 -0500 (EST)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEPNj-0005Cg-00
	for ietf@ietf.org; Tue, 28 Oct 2003 03:39:16 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEPNj-0005Cd-00
	for ietf@ietf.org; Tue, 28 Oct 2003 03:39:15 -0500
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9S8dFI20329
	for <ietf@ietf.org>; Tue, 28 Oct 2003 10:39:16 +0200 (EET)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T658eaf5a39ac158f21083@esvir01nok.ntc.nokia.com>;
 Tue, 28 Oct 2003 10:39:13 +0200
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 28 Oct 2003 10:39:13 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: IESG proposed statement on the IETF mission
Date: Tue, 28 Oct 2003 10:39:13 +0200
Message-ID: <DADF50F5EC506B41A0F375ABEB320636A8B7F0@esebe023.ntc.nokia.com>
Thread-Topic: IESG proposed statement on the IETF mission
Thread-Index: AcOcTV6CeIFNyCmlR3+M30EMD6JtkwA4UALA
To: <harald@alvestrand.no>, <ietf@ietf.org>, <problem-statement@alvestrand.no>
X-OriginalArrivalTime: 28 Oct 2003 08:39:13.0374 (UTC) FILETIME=[F6F3DFE0:01C39D2E]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Harald,

>
> > I almost feel that this should just be dropped from the statement.  =
My
> > reasons being that I have been told by the IESG about protocol
> > extensibility is that the IETF wants to have a tighter control over =
protocol
> > extensibility, even for extensions thought to be for limited use
> > or specific networks (for example, cellular networks).  The reason
> > being is that once something is out there, it often starts to be =
used
> > in ways which were not originally planned or used outside of its
> > original 'limited use' plans.  Therefore, in order to ensure proper
> > protocol behavior & interoperability, the IESG wants to manage
> > extensibility.  This has been very true in SIP & Diameter,=20
> > for example.
>=20
> True. Nearly a year ago, we attempted to publish=20
> draft-iesg-vendor-extensions, to describe these problems in more =
detail -=20
> but we failed to get that finished.

So, I think we have to be careful about what we consider part of
the IETF mission, if we cannot get basic agreement upon the implications
of the mission statement.

> > On the other hand, we see a protocol like RADIUS, which the IETF
> > has never done a good job at working with or standardizing, being
> > developed in 4 or more SDOs, and not in a colaborative manner.  This
> > makes a big mess with the RADIUS spec, and RADIUS does seem like a
> > protocol that has a big effect on the Internet.
>=20
> You'll have no disagreement from me that RADIUS is a problem!
>=20
> > So, in summary, the IESG has shown not to follow the above =
paragraph,
> > sometimes even for good reasons.  I can't think of a way in which
> > modify the paragraph to make it any better - because there will =
always
> > be examples of work that the IETF choses to standardize (or not)
> > which will violate that part of the mission.  Perhaps moving the
> > 'for the internet to the previous paragraph is what is needed.
>=20
> as I've said before - I don't think we can come up with a mission =
statement=20
> that retroactively blesses everything we've done well before, or=20
> retroactively curses everything we've done badly. And we do require=20
> flexibility to "do what's right". But without the ability to talk =
about=20
> what the mission of the IETF ... I think we'll do badly.

The past is the past, I don't want to revisit the past.  What I want
to do is to look forward.  We should have flexibility in terms of
how to decide what the IETF can do, what it can't do and what it
should (or shouldn't do).  I think we cannot make a blanket statement
in the mission that covers this.

thanks,
John



From owner-ietf@ietf.org  Tue Oct 28 04:57:48 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12859
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 04:57:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEQ28-00067j-5P
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 04:21:00 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEPYl-00027s-L4
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 03:50:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09686;
	Tue, 28 Oct 2003 03:50:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEPYi-0005Vv-00; Tue, 28 Oct 2003 03:50:36 -0500
Received: from maya20.nic.fr ([192.134.4.152])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEPYh-0005Vs-00; Tue, 28 Oct 2003 03:50:35 -0500
Received: from vespucci.nic.fr (postfix@vespucci.nic.fr [192.134.4.68])
	by maya20.nic.fr (8.12.4/8.12.4) with ESMTP id h9S8oNQW1526872;
	Tue, 28 Oct 2003 09:50:23 +0100 (CET)
Received: by vespucci.nic.fr (Postfix, from userid 1055)
	id 5FF63FF47; Tue, 28 Oct 2003 09:50:23 +0100 (CET)
Date: Tue, 28 Oct 2003 09:50:23 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Mark Davis <mark.davis@jtcsv.com>
Cc: Mark Crispin <MRC@CAC.Washington.EDU>, Keith Moore <moore@cs.utk.edu>,
        dcrocker@brandenburg.com, paf@cisco.com, ietf-imaa@imc.org,
        idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        IMAP Extensions WG <ietf-imapext@imc.org>, ietf-smtp@imc.org,
        presnick@qualcomm.com, hardie@qualcomm.com, ned.freed@mrochek.com
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-ID: <20031028085023.GB6617@nic.fr>
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
X-Operating-System: Debian GNU/Linux testing/unstable
X-Kernel: Linux 2.4.21-3-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, Oct 27, 2003 at 05:39:32PM -0800,
 Mark Davis <mark.davis@jtcsv.com> wrote 
 a message of 76 lines which said:

> We should remember that for a great many people in the world, Latin letters are
> quite unnatural; it'd be a bit like if we had to use Greek letters in all email
> addresses. 

It would be a bit like if we had to use Greek letters in mathematics
:-)




From owner-ietf@ietf.org  Tue Oct 28 05:05:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13241
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 05:05:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEQe7-0000UQ-HM
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 05:00:15 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEQC9-0006Zy-Vm
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 04:31:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11736;
	Tue, 28 Oct 2003 04:31:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEQC7-0006Ig-00; Tue, 28 Oct 2003 04:31:19 -0500
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEQC6-0006IZ-00; Tue, 28 Oct 2003 04:31:18 -0500
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 1AEQC3-0007Da-00; Tue, 28 Oct 2003 09:31:15 +0000
Date: Tue, 28 Oct 2003 09:31:15 +0000
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-ID: <20031028093114.GC20198@fysh.org>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com> <12228881609.20031027074111@brandenburg.com> <20031027105222.4eae54fd.moore@cs.utk.edu> <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu> <355752681.20031027161925@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <355752681.20031027161925@brandenburg.com>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

Dave Crocker wrote:
>                                               This poses a fundamental
>barrier for users needing mail addresses to be expressed in a richer set of
>characters,

I have yet to see this "need" established.  Everyone who has supported
internationalised mail addresses has axiomatically assumed such a need,
and has conspicuously failed to provide any more detail, such as any of
Keith Moore's suggestions.

I think the first task in this area should be to investigate the nature
and degree of desire for non-ASCII local parts.  This desire needs to
be weighed against the benefits we derive from writing all local parts
in a small, fixed alphabet (ASCII printables).

-zefram



From owner-ietf@ietf.org  Tue Oct 28 05:21:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13996
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 05:21:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEQe8-0000VS-7Y
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 05:00:16 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEQKw-0006oh-Ge
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 04:40:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12044;
	Tue, 28 Oct 2003 04:40:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEQKt-0006Or-00; Tue, 28 Oct 2003 04:40:23 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEQKt-0006Ok-00; Tue, 28 Oct 2003 04:40:23 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9S9jrf12762;
	Tue, 28 Oct 2003 01:45:54 -0800
Date: Tue, 28 Oct 2003 01:13:50 -0800
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v2.00.22)
Reply-To: dcrocker@brandenburg.com
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <2337816887.20031028011350@brandenburg.com>
To: Pete Resnick <presnick@qualcomm.com>
CC: ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, <lemonade@ietf.org>, <discuss@apps.ietf.org>,
        <ietf-imapext@imc.org>, <ietf-smtp@imc.org>,
        Dave Crocker <dhc@dcrocker.net>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <p06100309bbc3c83a8871@[216\.43\.25\.67]>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 <12228881609.20031027074111@brandenburg.com>
 <20031027105222.4eae54fd.moore@cs.utk.edu>
 <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
 <355752681.20031027161925@brandenburg.com>
 <16285.48493.496028.516294@moriarty.gnomon.org.uk>
 <14814332829.20031027184226@brandenburg.com>
 <p06100309bbc3c83a8871@[216.43.25.67]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pete,

>>RB> Restricting the disucssion to local-parts runs the risk of excluding
>>RB> other potentially relevent issues.
PR> I agree. Limiting discussion at this point to local-part does not
PR> take into account some of the possibilities.


That was exactly the intent of the text.

We have already seen how nicely the text served to bring into pretty stark
relief one bit of expectation from one of the proposals. It is only fitting to
have it serve the same purpose for another one.

IETF BOF time is pretty lousy for an open-ended chat.  Having specifications
to chat about is only marginally better than not having them.

What makes the real difference is having serious focus to the meeting. If we
go into this meeting without even having a clear sense of the scope of the
problem to be tackled, then the chance of having a productive meeting is
pretty small.

At the moment, it appears that the focus of the meeting is likely to be:
Shall we break existing Internet mail or shall we lay an enhancement on top of
it that preserves the installed base.  (I'm sure that everyone else who was
present at the pre-MIME/ESMTP discussions is really looking forward to
repeating the experience.)

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Tue Oct 28 05:28:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14396
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 05:28:13 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEQfB-0000tz-UM
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 05:01:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEQe2-0000S5-1p
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 05:00:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13040
	for <ietf@ietf.org>; Tue, 28 Oct 2003 04:59:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEQdz-0006og-00
	for ietf@ietf.org; Tue, 28 Oct 2003 05:00:07 -0500
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEQdy-0006oO-00
	for ietf@ietf.org; Tue, 28 Oct 2003 05:00:07 -0500
Received: by postman.ripe.net (Postfix, from userid 8)
	id 7EDC74EF2C; Tue, 28 Oct 2003 10:59:38 +0100 (CET)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP
	id DC5A34EF08; Tue, 28 Oct 2003 10:59:37 +0100 (CET)
Received: from x53.ripe.net (x53.ripe.net [193.0.1.53])
	by birch.ripe.net (8.12.10/8.11.6) with ESMTP id h9S9xbHm017251;
	Tue, 28 Oct 2003 10:59:37 +0100
Date: Tue, 28 Oct 2003 10:59:37 +0100 (CET)
From: Bruce Campbell <bruce.campbell@ripe.net>
X-X-Sender: bc@x53.ripe.net
To: todd glassey <todd.glassey@worldnet.att.net>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>,
        Christian Huitema <huitema@windows.microsoft.com>, ietf@ietf.org,
        problem-statement@alvestrand.no
Subject: Re: Proposed statement quotes wrong numbers
In-Reply-To: <027e01c39ca1$31452a70$010aff0a@bolaba>
Message-ID: <Pine.LNX.4.58.0310281054280.11194@x53.ripe.net>
References: <DAC3FCB50E31C54987CD10797DA511BA05D51E47@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
 <222145117.1067204085@[192.168.1.49]> <027e01c39ca1$31452a70$010aff0a@bolaba>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-RIPE-Spam-Status: N 0.499386
X-RIPE-Signature: 2036598cba69016b7157691c222971af
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 27 Oct 2003, todd glassey wrote:

> What was the attendance of the last meeting then? and also what then is the
> sum total of unique EMail Addresses in the Lists then too? I.e. what is the
> total size of the Vetting Community Resource that the IETF brings to the
> Party as an enterprise/org???

Are you sure that you can count the (large) number of subscribers that are
on the main IETF lists, and the umpteen WG lists, as participants?  There
seem to be a lot of people who are subscribed to various IETF-related
lists who do not seem to participate in the IETF discussions.

( But theres still a lot more than just 700 people who participate in the
  IETF )

--==--
Bruce.



From owner-ietf@ietf.org  Tue Oct 28 09:32:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23691
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 09:32:13 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEUVF-0001AR-0R
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 09:07:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEI4z-0002Wd-Em
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 19:51:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01382
	for <ietf@ietf.org>; Mon, 27 Oct 2003 19:51:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEI4x-00032k-00
	for ietf@ietf.org; Mon, 27 Oct 2003 19:51:23 -0500
Received: from willow.gnomon.org.uk ([69.10.132.76])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEI4w-00032T-00
	for ietf@ietf.org; Mon, 27 Oct 2003 19:51:22 -0500
Received: from moriarty.gnomon.org.uk (cpc4-cmbg2-5-0-cust162.cmbg.cable.ntl.com [81.100.86.162])
	by willow.gnomon.org.uk (8.12.3/8.12.3/Debian-6.6) with ESMTP id h9S0p8RX014082
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK)
	for <ietf@ietf.org>; Tue, 28 Oct 2003 00:51:11 GMT
Received: from moriarty.gnomon.org.uk (roy@localhost [127.0.0.1])
	by moriarty.gnomon.org.uk (8.12.3/8.12.3/Debian-6.6) with ESMTP id h9S0p7Ze008685
	for <ietf@ietf.org>; Tue, 28 Oct 2003 00:51:07 GMT
Received: by moriarty.gnomon.org.uk (tmda-sendmail, from uid 559);
	Tue, 28 Oct 2003 00:50:59 +0000 (GMT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16285.48493.496028.516294@moriarty.gnomon.org.uk>
Date: Tue, 28 Oct 2003 00:50:53 +0000
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, <lemonade@ietf.org>, <discuss@apps.ietf.org>,
        <ietf-imapext@imc.org>, <ietf-smtp@imc.org>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <355752681.20031027161925@brandenburg.com>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
	<12228881609.20031027074111@brandenburg.com>
	<20031027105222.4eae54fd.moore@cs.utk.edu>
	<Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
	<355752681.20031027161925@brandenburg.com>
X-Mailer: VM 7.03 under Emacs 20.7.2
From: Roy Badami <roy@gnomon.org.uk>
X-Delivery-Agent: TMDA/0.81 (Swaps)
X-Primary-Address: roy@gnomon.org.uk
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

 > Mail Internationalised Local-Part (MILP)

Even though, given IDNA now exists as a proposed standard, the main
issues relate to the local part, the issue under discussion is that of
internationalized mail addresses, not just internationalized
local-parts.

Restricting the disucssion to local-parts runs the risk of excluding
other potentially relevent issues.  For instance, one of the issues
that has been discussed on the IMAA list is whether full-width at
should be recognized in an internationalized mail address.  IMHO, the
charter shouldn't be framed in a way that is sufficiently narrow as to
render such questions out of scope.

	-roy






From owner-ietf@ietf.org  Tue Oct 28 09:32:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23700
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 09:32:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEUVE-0001AG-QN
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 09:07:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEHXF-0005Ud-72
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 19:16:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00175
	for <ietf@ietf.org>; Mon, 27 Oct 2003 19:16:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEHXD-0002aa-00
	for ietf@ietf.org; Mon, 27 Oct 2003 19:16:31 -0500
Received: from w1309.hostcentric.net ([66.40.78.254])
	by ietf-mx with smtp (Exim 4.12)
	id 1AEHXC-0002aO-00
	for ietf@ietf.org; Mon, 27 Oct 2003 19:16:30 -0500
Received: (qmail 22319 invoked by alias); 28 Oct 2003 00:16:21 -0000
Received: from unknown (HELO DAVIS1) (129.42.184.35)
  by 0 with SMTP; 28 Oct 2003 00:16:21 -0000
Message-ID: <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1>
From: "Mark Davis" <mark.davis@jtcsv.com>
To: "Mark Crispin" <mrc@CAC.Washington.EDU>, "Keith Moore" <moore@cs.utk.edu>
Cc: <dcrocker@brandenburg.com>, <paf@cisco.com>, <ietf-imaa@imc.org>,
        <idn@ops.ietf.org>, <ietf-822@imc.org>, <ietf@ietf.org>,
        <ietf-pop3ext@imc.org>, <lemonade@ietf.org>, <discuss@apps.ietf.org>,
        <ietf-imapext@imc.org>, <ietf-smtp@imc.org>, <presnick@qualcomm.com>,
        <hardie@qualcomm.com>, <ned.freed@mrochek.com>
References: <E1AEH14-000N0E-GD@psg.com>
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Mon, 27 Oct 2003 16:16:20 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id TAA00180
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

I'm curious: why do you think that everyone would be satisfied with Latin
characters only, and no non-Latin characters?

Mark
__________________________________
http://www.macchiato.com
=E2=96=BA =E0=A4=B6=E0=A4=BF=E0=A4=B7=E0=A5=8D=E0=A4=AF=E0=A4=BE=E0=A4=A6=
=E0=A4=BF=E0=A4=9A=E0=A5=8D=E0=A4=9B=E0=A5=87=E0=A4=A4=E0=A5=8D=E0=A4=AA=E0=
=A4=B0=E0=A4=BE=E0=A4=9C=E0=A4=AF=E0=A4=AE=E0=A5=8D =E2=97=84

----- Original Message -----=20
From: "Mark Crispin" <mrc@CAC.Washington.EDU>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <dcrocker@brandenburg.com>; <paf@cisco.com>; <ietf-imaa@imc.org>;
<idn@ops.ietf.org>; <ietf-822@imc.org>; <ietf@ietf.org>; <ietf-pop3ext@im=
c.org>;
<lemonade@ietf.org>; <discuss@apps.ietf.org>; <ietf-imapext@imc.org>;
<ietf-smtp@imc.org>; <presnick@qualcomm.com>; <hardie@qualcomm.com>;
<ned.freed@mrochek.com>
Sent: Mon, 2003 Oct 27 11:10
Subject: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)


> On Mon, 27 Oct 2003, Keith Moore wrote:
>
>  >> Thanks for taking a stab at a problem statement.  I'd like to drill=
 down
>  >> on this just a bit.
>  >> What is the source of the "growing need"?  Is it:
>  >> [snip]
>
>
> I agree that this needs to be stated, but someone other than me will ha=
ve
> to do it.
>
> I believe that the primary push for this functionality comes from regio=
ns
> which use Latin alphabetics with diacriticals; and that most individual=
s
> in regions which do not use Latin script are accept the use of Latin
> script for multinational interchange.  In many regions where Latin
> diacriticals are used, there is no acceptable transform of a surname to=
 a
> form that does not use diacriticals.  Simply omitting the diacritical
> causes (at least to the inhabitants of those regions) a misspelling.
>
> This set of beliefs naturally biases how I approach the problem.  The
> problem statement must be free of bias, including mine.
>
> -- Mark --
>
> http://staff.washington.edu/mrc
> Science does not emerge from voting, party politics, or public debate.
> Si vis pacem, para bellum.
>
>
>
>
>
>
>
>






From owner-ietf@ietf.org  Tue Oct 28 09:49:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25533
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 09:49:17 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEUVF-0001Ao-A8
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 09:07:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEIpd-0002xY-Cn
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 20:39:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03129
	for <ietf@ietf.org>; Mon, 27 Oct 2003 20:39:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEIpb-0003jO-00
	for ietf@ietf.org; Mon, 27 Oct 2003 20:39:35 -0500
Received: from w1309.hostcentric.net ([66.40.78.254])
	by ietf-mx with smtp (Exim 4.12)
	id 1AEIpa-0003jG-00
	for ietf@ietf.org; Mon, 27 Oct 2003 20:39:34 -0500
Received: (qmail 22048 invoked by alias); 28 Oct 2003 01:39:33 -0000
Received: from unknown (HELO DAVIS1) (129.42.184.35)
  by 0 with SMTP; 28 Oct 2003 01:39:33 -0000
Message-ID: <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
From: "Mark Davis" <mark.davis@jtcsv.com>
To: "Mark Crispin" <MRC@CAC.Washington.EDU>
Cc: "Keith Moore" <moore@cs.utk.edu>, <dcrocker@brandenburg.com>,
        <paf@cisco.com>, <ietf-imaa@imc.org>, <idn@ops.ietf.org>,
        <ietf-822@imc.org>, <ietf@ietf.org>, <ietf-pop3ext@imc.org>,
        <lemonade@ietf.org>, <discuss@apps.ietf.org>,
        "IMAP Extensions WG" <ietf-imapext@imc.org>, <ietf-smtp@imc.org>,
        <presnick@qualcomm.com>, <hardie@qualcomm.com>,
        <ned.freed@mrochek.com>
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU>
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Mon, 27 Oct 2003 17:39:32 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id UAA03132
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Ok, I understand more about the context.

Based on what I've seen, I think it quite likely that people will want em=
ail
addresses in their native script, even if that means that outsiders can't
(easily) use those email address. After all, it is quite easy to have mul=
tiple
email addresses. Mr. Tanaka can have one with Latin letters and one with
Japanese (e.g. =E3=83=A0=E3=83=AB=E3=82=AF@=E3=82=AB=E3=82=AF.=E3=83=AF=E3=
=82=B7=E3=83=B3=E3=82=B0=E3=83=88=E3=83=B3.=E3=82=A8=E3=83=87=E3=82=A5).

We should remember that for a great many people in the world, Latin lette=
rs are
quite unnatural; it'd be a bit like if we had to use Greek letters in all=
 email
addresses. And there are many projects underway in less-developed countri=
es to
bring computers to masses of people that will even less familiarity with =
Latin
letters.

Mark
__________________________________
http://www.macchiato.com
=E2=96=BA =E0=A4=B6=E0=A4=BF=E0=A4=B7=E0=A5=8D=E0=A4=AF=E0=A4=BE=E0=A4=A6=
=E0=A4=BF=E0=A4=9A=E0=A5=8D=E0=A4=9B=E0=A5=87=E0=A4=A4=E0=A5=8D=E0=A4=AA=E0=
=A4=B0=E0=A4=BE=E0=A4=9C=E0=A4=AF=E0=A4=AE=E0=A5=8D =E2=97=84

----- Original Message -----=20
From: "Mark Crispin" <MRC@CAC.Washington.EDU>
To: "Mark Davis" <mark.davis@jtcsv.com>
Cc: "Keith Moore" <moore@cs.utk.edu>; <dcrocker@brandenburg.com>;
<paf@cisco.com>; <ietf-imaa@imc.org>; <idn@ops.ietf.org>; <ietf-822@imc.o=
rg>;
<ietf@ietf.org>; <ietf-pop3ext@imc.org>; <lemonade@ietf.org>;
<discuss@apps.ietf.org>; "IMAP Extensions WG" <ietf-imapext@imc.org>;
<ietf-smtp@imc.org>; <presnick@qualcomm.com>; <hardie@qualcomm.com>;
<ned.freed@mrochek.com>
Sent: Mon, 2003 Oct 27 17:15
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA=
)


> On Mon, 27 Oct 2003, Mark Davis wrote:
> > I'm curious: why do you think that everyone would be satisfied with L=
atin
> > characters only, and no non-Latin characters?
>
> I didn't say that.  I stated my belief that, for reasons of practicalit=
y,
> most individuals in regions which do not use Latin script accept the us=
e
> of Latin script for multinational exchange.
>
> It does not work well for an individual in Japan with surname Tanaka to
> expect the overwhelming majority of non-Japanese individuals worldwide =
to
> know his surname is written with the Han characters for "rice paddy" an=
d
> "middle", or what those characters look like, or how to enter those
> characters on the computer.
>
> It does, however, work for him to expect that the overwhelming majority=
 of
> individuals worldwide to know how to deal with the 6 Latin letters that
> form the romanization "Tanaka".
>
> Nor is it very likely that this situation will change in the future.  I
> doubt that many individuals in the world are literate in all the world'=
s
> active scripts.  Literacy in one's native script and basic Latin script=
 is
> something that most computer users possess today.
>
> For domestic exchange only, that pair of Han characters are probably
> alright.  Within Western Europe, it's probably alright to use Latin
> characters with diacriticals.
>
> Perhaps the main problem that needs to be decided in any IEA effort is =
if
> it is alright to have email addresses that are only usable in limited
> areas of the world; or if not, how to represent internationalized email
> addresses in a usable fashion when (not if) the email address needs to =
be
> represented for a person and/or computer is illiterate in that script.
>
> A likely side issue is whether it is "good enough" to promote Latin
> characters with diacriticals to the same status of "everybody must know
> how to do these" that is required for ASCII.
>
> -- Mark --
>
> http://staff.washington.edu/mrc
> Science does not emerge from voting, party politics, or public debate.
> Si vis pacem, para bellum.
>






From owner-ietf@ietf.org  Tue Oct 28 09:49:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25568
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 09:49:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEUVF-0001Ai-5g
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 09:07:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEISL-0002qc-43
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 20:15:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02380;
	Mon, 27 Oct 2003 20:15:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEISJ-0003TW-00; Mon, 27 Oct 2003 20:15:31 -0500
Received: from mxout1.cac.washington.edu ([140.142.32.134])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEISI-0003TC-00; Mon, 27 Oct 2003 20:15:30 -0500
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9S1EwaZ010323;
	Mon, 27 Oct 2003 17:14:59 -0800
Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9S1Ewx0018732
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Mon, 27 Oct 2003 17:14:58 -0800
Date: Mon, 27 Oct 2003 17:15:00 -0800 (Pacific Standard Time)
From: Mark Crispin <MRC@CAC.Washington.EDU>
To: Mark Davis <mark.davis@jtcsv.com>
cc: Keith Moore <moore@cs.utk.edu>, dcrocker@brandenburg.com, paf@cisco.com,
        ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        IMAP Extensions WG <ietf-imapext@imc.org>, ietf-smtp@imc.org,
        presnick@qualcomm.com, hardie@qualcomm.com, ned.freed@mrochek.com
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1>
Message-ID: <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU>
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 27 Oct 2003, Mark Davis wrote:
> I'm curious: why do you think that everyone would be satisfied with Latin
> characters only, and no non-Latin characters?

I didn't say that.  I stated my belief that, for reasons of practicality,
most individuals in regions which do not use Latin script accept the use
of Latin script for multinational exchange.

It does not work well for an individual in Japan with surname Tanaka to
expect the overwhelming majority of non-Japanese individuals worldwide to
know his surname is written with the Han characters for "rice paddy" and
"middle", or what those characters look like, or how to enter those
characters on the computer.

It does, however, work for him to expect that the overwhelming majority of
individuals worldwide to know how to deal with the 6 Latin letters that
form the romanization "Tanaka".

Nor is it very likely that this situation will change in the future.  I
doubt that many individuals in the world are literate in all the world's
active scripts.  Literacy in one's native script and basic Latin script is
something that most computer users possess today.

For domestic exchange only, that pair of Han characters are probably
alright.  Within Western Europe, it's probably alright to use Latin
characters with diacriticals.

Perhaps the main problem that needs to be decided in any IEA effort is if
it is alright to have email addresses that are only usable in limited
areas of the world; or if not, how to represent internationalized email
addresses in a usable fashion when (not if) the email address needs to be
represented for a person and/or computer is illiterate in that script.

A likely side issue is whether it is "good enough" to promote Latin
characters with diacriticals to the same status of "everybody must know
how to do these" that is required for ASCII.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.





From owner-ietf@ietf.org  Tue Oct 28 09:51:42 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25868
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 09:51:42 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEUVF-0001Au-Eb
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 09:07:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEKfy-0004ag-Uf
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 22:37:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05819;
	Mon, 27 Oct 2003 22:37:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEKfw-0004uv-00; Mon, 27 Oct 2003 22:37:44 -0500
Received: from mxout5.cac.washington.edu ([140.142.32.135])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEKfv-0004ul-00; Mon, 27 Oct 2003 22:37:44 -0500
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9S3baMk024515;
	Mon, 27 Oct 2003 19:37:36 -0800
Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9S3bZSS003692
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Mon, 27 Oct 2003 19:37:35 -0800
Date: Mon, 27 Oct 2003 19:37:37 -0800 (Pacific Standard Time)
From: Mark Crispin <MRC@CAC.Washington.EDU>
To: Mark Davis <mark.davis@jtcsv.com>
cc: Keith Moore <moore@cs.utk.edu>, dcrocker@brandenburg.com, paf@cisco.com,
        ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        IMAP Extensions WG <ietf-imapext@imc.org>, ietf-smtp@imc.org,
        presnick@qualcomm.com, hardie@qualcomm.com, ned.freed@mrochek.com
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
Message-ID: <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU>
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU>
 <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 27 Oct 2003, Mark Davis wrote:
> Based on what I've seen, I think it quite likely that people will want email
> addresses in their native script, even if that means that outsiders can't
> (easily) use those email address.

That may well be the case.

> We should remember that for a great many people in the world, Latin
> letters are quite unnatural; it'd be a bit like if we had to use Greek
> letters in all email addresses. And there are many projects underway in
> less-developed countries to bring computers to masses of people that
> will even less familiarity with Latin letters.

I am not convinced that it is possible to use a computer on the Internet
anywhere in the world without at least a basic acquaintance with Latin
script.

I do not believe many individuals (other than primary school children) are
literate in their native language but are completely illiterate in Latin
script.  This does not mean "being able to read or write the English
language"; rather, this simply means knowing the Latin script alphabet.

Put another way, individuals who are completely illiterate in Latin script
are also likely to be illiterate in their native language script as well.

No other script on the planet has such international recognition.

There is undoubtably a *preference* for one's native script; and that
preference should be respected as much as possible.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.





From owner-ietf@ietf.org  Tue Oct 28 09:51:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25913
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 09:51:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEUVF-0001B0-Iv
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 09:07:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AELNf-00079d-8t
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 23:22:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07113
	for <ietf@ietf.org>; Mon, 27 Oct 2003 23:22:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AELNc-0005QT-00
	for ietf@ietf.org; Mon, 27 Oct 2003 23:22:52 -0500
Received: from miranda.org ([209.58.150.153] ident=qmailr)
	by ietf-mx with smtp (Exim 4.12)
	id 1AELNc-0005QH-00
	for ietf@ietf.org; Mon, 27 Oct 2003 23:22:52 -0500
Received: (qmail 21999 invoked from network); 28 Oct 2003 04:22:45 -0000
Received: from miranda.org (HELO lustre.dyn.wiw.org) (ams@209.58.150.153)
  by miranda.org with SMTP; 28 Oct 2003 04:22:45 -0000
Received: from ams by lustre.dyn.wiw.org with local (Exim 4.20)
	id 1AELNT-0000RV-Fn; Tue, 28 Oct 2003 09:52:43 +0530
Date: Tue, 28 Oct 2003 09:52:43 +0530
From: Abhijit Menon-Sen <ams@wiw.org>
To: Mark Crispin <MRC@CAC.Washington.EDU>
Cc: ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-ID: <20031028095243.A1525@lustre.dyn.wiw.org>
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU>
Sender: owner-ietf@ietf.org
Precedence: bulk

At 2003-10-27 19:37:37 -0800, MRC@CAC.Washington.EDU wrote:
>
> I do not believe many individuals (other than primary school children) are
> literate in their native language but are completely illiterate in Latin
> script.  This does not mean "being able to read or write the English
> language"; rather, this simply means knowing the Latin script alphabet.

Mark,

The number of people in India who can read and write only their native
language, but have no usable knowledge of Latin script, is much larger
than the tiny number who are familiar with both. I'm told that this is
true for many native speakers of Chinese and Arabic as well.

The use of local scripts is much more than just a "preference" for the
numerous localisation efforts in India which focus on making computing
more accessible to poor farmers and people in villages.

(I agree that it's currently nearly impossible to use computers if one
isn't familiar with the Latin script, of course.)

-- ams





From owner-ietf@ietf.org  Tue Oct 28 09:54:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26411
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 09:54:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEUVG-0001Be-8A
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 09:07:22 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEQpO-0001TL-Sa
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 05:11:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13596;
	Tue, 28 Oct 2003 05:11:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEQpL-00070l-00; Tue, 28 Oct 2003 05:11:52 -0500
Received: from melkebalanse.gulbrandsen.priv.no ([217.19.171.131])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEQpL-00070I-00; Tue, 28 Oct 2003 05:11:51 -0500
Message-Id: <MB5TXyMPE3DdvF8zxs0w+g.md5@melkebalanse.gulbrandsen.priv.no>
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Mark Crispin <mrc@CAC.Washington.EDU>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Cc: ietf@ietf.org, lemonade@ietf.org, IETF RFC-822 list <ietf-822@imc.org>,
        IMAA list <ietf-imaa@imc.org>,
        IMAP Extensions WG <ietf-imapext@imc.org>, ietf-pop3ext@imc.org,
        ietf-smtp@imc.org, Abhijit Menon-Sen <ams@wiw.org>,
        discuss@apps.ietf.org, IETF/IDN WG <idn@ops.ietf.org>
References: <E1AEH14-000N0E-GD@psg.com>
 <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU>
 <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU>
 <20031028095243.A1525@lustre.dyn.wiw.org>
 <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>
In-Reply-To: 
 <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>
Content-Type: text/plain; format=flowed
MIME-Version: 1.0
Date: Tue, 28 Oct 2003 11:15:17 +0100
Sender: owner-ietf@ietf.org
Precedence: bulk

Mark Crispin writes:
> On Tue, 28 Oct 2003, Abhijit Menon-Sen wrote:
>> (I agree that it's currently nearly impossible to use computers if 
>> one isn't familiar with the Latin script, of course.)
>
> Which probably makes the rest of this discussion academic, unless 
> we're going to undertake solving *that* problem for Microsoft and the 
> various UNIX/Linux vendors...

You're not appreciating the full complexity of the problem. ;)

Not only should the email standards permit MUAs and MTAs of the year 
2020 to solve the problem Abhijit mentions, but they should even permit 
such future programs to interoperate with latinate ones of the present 
and near future. And if it's too hard for latinate MUAs to implement 
the IEA standard, that won't happen.

--Arnt





From owner-ietf@ietf.org  Tue Oct 28 09:54:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26427
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 09:54:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEUVF-0001BS-PS
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 09:07:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AELgU-0005Ho-1D
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 23:42:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09024;
	Mon, 27 Oct 2003 23:42:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AELgR-00069K-00; Mon, 27 Oct 2003 23:42:19 -0500
Received: from mxout1.cac.washington.edu ([140.142.32.134])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AELgR-00069G-00; Mon, 27 Oct 2003 23:42:19 -0500
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9S4gHaZ024278;
	Mon, 27 Oct 2003 20:42:17 -0800
Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9S4gHx0026302
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Mon, 27 Oct 2003 20:42:17 -0800
Date: Mon, 27 Oct 2003 20:42:19 -0800 (Pacific Standard Time)
From: Mark Crispin <MRC@CAC.Washington.EDU>
To: Abhijit Menon-Sen <ams@wiw.org>
cc: ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <20031028095243.A1525@lustre.dyn.wiw.org>
Message-ID: <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU>
 <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU>
 <20031028095243.A1525@lustre.dyn.wiw.org>
Organization: Networks & Distributed Computing
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 28 Oct 2003, Abhijit Menon-Sen wrote:
> The number of people in India who can read and write only their native
> language, but have no usable knowledge of Latin script, is much larger
> than the tiny number who are familiar with both. I'm told that this is
> true for many native speakers of Chinese and Arabic as well.

I defer to your superior knowledge about India.

I do not believe that this is true for Chinese.  AFAIK, Chinese primary
school kids use Latin script with hanyu-pinyin as a stopgap prior to their
mastery of Han script (which takes many years).

> The use of local scripts is much more than just a "preference" for the
> numerous localisation efforts in India which focus on making computing
> more accessible to poor farmers and people in villages.

A poor farmer or villager in China is more likely to be totally illiterate
than to be literate in Han script but unable to recognize Latin script.

Note that when I say "recognize Latin script", I mean the ability to
determine that "dog" is a three-letter word that has the letters "d", "o",
and "g", each of which the individual recognizes and can name.  This does
not include the ability to recognize that this refers to a domesticated
canine.

> (I agree that it's currently nearly impossible to use computers if one
> isn't familiar with the Latin script, of course.)

Which probably makes the rest of this discussion academic, unless we're
going to undertake solving *that* problem for Microsoft and the various
UNIX/Linux vendors...

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.





From owner-ietf@ietf.org  Tue Oct 28 10:19:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23694
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 09:32:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEUVE-0001AA-Lv
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 09:07:20 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AECls-0008Hm-QP
	for ietf@asgard.ietf.org; Mon, 27 Oct 2003 14:11:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01160;
	Mon, 27 Oct 2003 14:11:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEClr-0002KE-00; Mon, 27 Oct 2003 14:11:19 -0500
Received: from mxout3.cac.washington.edu ([140.142.32.166])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEClr-0002Js-00; Mon, 27 Oct 2003 14:11:19 -0500
Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201])
	by mxout3.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9RJAtC2014056;
	Mon, 27 Oct 2003 11:10:56 -0800
Received: from localhost (mrc@localhost)
	by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9RJAtOx022764;
	Mon, 27 Oct 2003 11:10:55 -0800
Date: Mon, 27 Oct 2003 11:10:55 -0800 (PST)
From: Mark Crispin <mrc@CAC.Washington.EDU>
To: Keith Moore <moore@cs.utk.edu>
cc: dcrocker@brandenburg.com, paf@cisco.com, ietf-imaa@imc.org,
        idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org, presnick@qualcomm.com,
        hardie@qualcomm.com, ned.freed@mrochek.com
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <20031027134403.5eaaee9e.moore@cs.utk.edu>
Message-ID: <Pine.LNX.4.60.0310271059140.20831@shiva1.cac.washington.edu>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 <12228881609.20031027074111@brandenburg.com> <20031027105222.4eae54fd.moore@cs.utk.edu>
 <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
 <20031027134403.5eaaee9e.moore@cs.utk.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 27 Oct 2003, Keith Moore wrote:
> Thanks for taking a stab at a problem statement.  I'd like to drill down
> on this just a bit.
> What is the source of the "growing need"?  Is it:
> [snip]

I agree that this needs to be stated, but someone other than me will have
to do it.

I believe that the primary push for this functionality comes from regions
which use Latin alphabetics with diacriticals; and that most individuals
in regions which do not use Latin script are accept the use of Latin
script for multinational interchange.  In many regions where Latin
diacriticals are used, there is no acceptable transform of a surname to a
form that does not use diacriticals.  Simply omitting the diacritical
causes (at least to the inhabitants of those regions) a misspelling.

This set of beliefs naturally biases how I approach the problem.  The
problem statement must be free of bias, including mine.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.





From owner-ietf@ietf.org  Tue Oct 28 14:56:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19585
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 14:56:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEYul-0002WT-I4
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 13:49:59 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEVX1-0003nm-M2
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 10:13:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28420;
	Tue, 28 Oct 2003 10:13:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEVX0-0005I1-00; Tue, 28 Oct 2003 10:13:14 -0500
Received: from [195.167.170.152] (helo=bowl.fysh.org ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEVWz-0005Hv-00; Tue, 28 Oct 2003 10:13:13 -0500
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
	id 1AEVWs-0000mk-00; Tue, 28 Oct 2003 15:13:06 +0000
Date: Tue, 28 Oct 2003 15:13:06 +0000
To: Mark Crispin <mrc@CAC.Washington.EDU>
Cc: Keith Moore <moore@cs.utk.edu>, dcrocker@brandenburg.com, paf@cisco.com,
        ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org, presnick@qualcomm.com,
        hardie@qualcomm.com, ned.freed@mrochek.com
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-ID: <20031028151306.GA1549@fysh.org>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com> <12228881609.20031027074111@brandenburg.com> <20031027105222.4eae54fd.moore@cs.utk.edu> <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu> <20031027134403.5eaaee9e.moore@cs.utk.edu> <Pine.LNX.4.60.0310271059140.20831@shiva1.cac.washington.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.60.0310271059140.20831@shiva1.cac.washington.edu>
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

Mark Crispin wrote:
>                                       In many regions where Latin
>diacriticals are used, there is no acceptable transform of a surname to a
>form that does not use diacriticals.  Simply omitting the diacritical
>causes (at least to the inhabitants of those regions) a misspelling.

Ah, this one's easy.  Local parts aren't limited to Latin letters,
they can use all the ASCII printables.  Diacriticals are available
there, albeit in characters that are shared with other uses.
<dej`a_vu@foo.example> is a perfectly valid email address already.
It doesn't start to get tricky until we get into the eastern European
languages -- ASCII only intentionally provides western European
diacriticals.

Cue the debate about whether the diacritic should go before or after
the base letter.

-zefram



From owner-ietf@ietf.org  Tue Oct 28 15:08:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20700
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 15:08:50 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEZlG-00045C-1u
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 14:44:14 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEWTM-0002ff-FE
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 11:13:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04547;
	Tue, 28 Oct 2003 11:13:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEWTL-0007Tt-00; Tue, 28 Oct 2003 11:13:31 -0500
Received: from panoramix.hexago.com ([209.71.226.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEWTK-0007TN-00; Tue, 28 Oct 2003 11:13:30 -0500
Received: from localhost (retro.viagenie.qc.ca [IPv6:3ffe:b00:c18:3::22])
	(authenticated bits=0)
	by panoramix.hexago.com (8.12.8/8.12.8) with ESMTP id h9SGD66r006992;
	Tue, 28 Oct 2003 11:13:14 -0500 (EST)
Date: Tue, 28 Oct 2003 11:12:54 -0500
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
To: Mark Davis <mark.davis@jtcsv.com>, Mark Crispin <MRC@CAC.Washington.EDU>,
        Abhijit Menon-Sen <ams@wiw.org>
cc: ietf-imaa@imc.org, idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-ID: <280960000.1067357574@classic.viagenie.qc.ca>
In-Reply-To: <00a001c39d65$b23177f0$7900a8c0@DAVIS1>
References: <E1AEH14-000N0E-GD@psg.com>
 <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU>
 <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU>
 <20031028095243.A1525@lustre.dyn.wiw.org>
 <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>
 <00a001c39d65$b23177f0$7900a8c0@DAVIS1>
X-Mailer: Mulberry/3.1.0b9 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

it appears to me that this thread is not very different from the idn
considerations on usage of idn in the world. So what is really new in this
discussion?

Marc.

-- Tuesday, October 28, 2003 07:10:59 -0800 Mark Davis
<mark.davis@jtcsv.com> wrote/a ecrit:

>> > (I agree that it's currently nearly impossible to use computers if one
>> > isn't familiar with the Latin script, of course.)
>> 
>> Which probably makes the rest of this discussion academic, unless we're
>> going to undertake solving *that* problem for Microsoft and the various
>> UNIX/Linux vendors...
> 
> It is currently impossible to use the Internet without knowing the Latin
> script. However, the goal of most well-designed client software and
> operating systems is to permit the user to work entirely within their
> native language, with a fully localized system. This is reaching to India
> and other countries; Microsoft has introduced fully localized versions of
> Indic Windows just recently, and Linux vendors are hard at work to
> produce fully localized versions of their software.
> 
> Email and Web addresses are the big remaining holdouts for most people.
> People should not be forced to use a script that they are unfamiliar
> with, just to use email addresses and sites in their own countries. Even
> if they are familiar with the Latin script, it is very often a very bad
> match for their languages, making it very difficult to figure out how
> native words would be spelled in it.
> 
> Mark
> 



------------------------------------------
Marc Blanchet
Hexago
tel: +1-418-266-5533x225
------------------------------------------
http://www.freenet6.net: IPv6 connectivity
------------------------------------------



From owner-ietf@ietf.org  Tue Oct 28 15:34:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23908
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 15:34:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEZle-0004TG-2K
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 14:44:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEX6y-0000ni-Ga
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 11:54:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07634;
	Tue, 28 Oct 2003 11:54:16 -0500 (EST)
From: Margaret.Wasserman@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEX6x-0000xX-00; Tue, 28 Oct 2003 11:54:27 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEX6w-0000xK-00; Tue, 28 Oct 2003 11:54:26 -0500
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9SGsPI05937;
	Tue, 28 Oct 2003 18:54:25 +0200 (EET)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T659074b434ac158f21083@esvir01nok.ntc.nokia.com>;
 Tue, 28 Oct 2003 18:54:24 +0200
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 28 Oct 2003 10:54:22 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Tue, 28 Oct 2003 11:54:21 -0500
Message-ID: <E320A8529CF07E4C967ECC2F380B0CF902443EA6@bsebe001.americas.nokia.com>
Thread-Topic: FYI: BOF on Internationalized Email Addresses (IEA)
Thread-Index: AcOdY3TL2xxUnJupRI2uu4njYAvuPgAD/9pQ
To: <idn@ops.ietf.org>, <ietf-822@imc.org>, <ietf@ietf.org>,
        <ietf-pop3ext@imc.org>, <lemonade@ietf.org>, <discuss@apps.ietf.org>,
        <ietf-imapext@imc.org>, <ietf-smtp@imc.org>, <ietf-imaa@imc.org>
X-OriginalArrivalTime: 28 Oct 2003 16:54:22.0543 (UTC) FILETIME=[22FF4DF0:01C39D74]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


Excuse me, but could you please constrain this
conversation to fewer than 9 (nine!) e-mail lists?

The BOF description lists imaa@imc.org as the
discussion list, but this discussion is being
cc:ed to ietf-imaa@imc.org.  I'd suggest that you
move this discussion to whichever of those lists
is actually correct.

Margaret




From owner-ietf@ietf.org  Tue Oct 28 15:36:28 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24186
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 15:36:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEZlm-0004nU-3B
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 14:44:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEXlX-00008u-Kd
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 12:36:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11141;
	Tue, 28 Oct 2003 12:36:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEXlV-0002Hm-00; Tue, 28 Oct 2003 12:36:22 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEXlV-0002Hi-00; Tue, 28 Oct 2003 12:36:21 -0500
Received: from bs.jck.com ([209.187.148.211] helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AEXlK-000NIP-00; Tue, 28 Oct 2003 12:36:11 -0500
Date: Tue, 28 Oct 2003 12:36:07 -0500
From: John C Klensin <klensin@jck.com>
To: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>,
        Mark Davis <mark.davis@jtcsv.com>,
        Mark Crispin <MRC@CAC.Washington.EDU>, Abhijit Menon-Sen <ams@wiw.org>
cc: "ietf-imaa@imc.org" <ietf-imaa@imc.org>,
        "idn@ops.ietf.org" <idn@ops.ietf.org>,
        "ietf-822@imc.org" <ietf-822@imc.org>, "ietf@ietf.org" <ietf@ietf.org>,
        "ietf-pop3ext@imc.org" <ietf-pop3ext@imc.org>,
        "lemonade@ietf.org" <lemonade@ietf.org>,
        "discuss@apps.ietf.org" <discuss@apps.ietf.org>,
        "ietf-imapext@imc.org" <ietf-imapext@imc.org>,
        "ietf-smtp@imc.org" <ietf-smtp@imc.org>
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email
 Addresses (IEA)
Message-ID: <12344770.1067344567@KLENSIN-TP>
In-Reply-To: <280960000.1067357574@classic.viagenie.qc.ca>
References: <E1AEH14-000N0E-GD@psg.com>
 <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU>
 <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU>
  <20031028095243.A1525@lustre.dyn.wiw.org>
 <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>
  <00a001c39d65$b23177f0$7900a8c0@DAVIS1>
 <280960000.1067357574@classic.viagenie.qc.ca>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Tuesday, October 28, 2003 11:12 -0500 Marc Blanchet
<Marc.Blanchet@viagenie.qc.ca> wrote:

> it appears to me that this thread is not very different from
> the idn considerations on usage of idn in the world. So what
> is really new in this discussion?

See the draft.

Quick answer: DNS interfaces really exist at the protocol level,
and a large part of the hypothesis behind IDNA was that it would
be possible, after we had enough implementations, to prevent an
end-user from ever seeing an encoded domain name.  That story
just doesn't hold for a special encoding-based (aka MUA-only)
email local part implementation, and maybe not for email
generally.  For example, under current rules, an MTA is required
to stuff the name it actually sees in HELO/EHLO and the MAIL
command into various headers.  If it is expected to notice that
they have special encodings and decodes them, we've gone rather
far into "the infrastructure is involved", even if the actual
on-the-wire transport is not impacted.  If it doesn't do that,
the encodings --both the IDNA domain parts and the special mail
encoding-- are going to be in the user's face, in the most
literal sense of that term.  

The similarity of that situation to the early IDN discussions is
the importance of the "what problem are you solving" question.
And it is very clear to me that, for email addresses, the answer
has got to "user sees their own characters in their email
addresses and the email addresses of those whose languages they
speak/ recognize.  Users typically don't actually see envelopes.
But seeing, e.g., different forms/codings of an address in the
header "From:" field than appears in "Return-path:" or than
appears in a signature line in the message body, is going to
create real unhappiness.  Similarly as has been pointed out in
another context, seeing an address in different from when it
appears in a header than when it (and that header) are
encapsulated in a message/?? body part is just not going to
amuse any user to whom we've said "ok, now you have i18n
strings, enjoy your new found local language capabilities".  And
I guess that tells you what I think the problem is that we need
to solve.  YMMD.

     john
 



From owner-ietf@ietf.org  Tue Oct 28 16:24:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27237
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 16:24:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEajF-0001VS-2l
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 15:46:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEa7u-00033N-AZ
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 15:07:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20519;
	Tue, 28 Oct 2003 15:07:26 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEa7s-0005if-00; Tue, 28 Oct 2003 15:07:36 -0500
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEa7r-0005iU-00; Tue, 28 Oct 2003 15:07:35 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9SK7J6P004972;
	Tue, 28 Oct 2003 15:07:19 -0500
Message-Id: <200310282007.h9SK7J6P004972@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Mark Davis <mark.davis@jtcsv.com>
Cc: Mark Crispin <MRC@CAC.Washington.EDU>, Keith Moore <moore@cs.utk.edu>,
        dcrocker@brandenburg.com, paf@Cisco.COM, ietf-imaa@imc.org,
        idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        IMAP Extensions WG <ietf-imapext@imc.org>, ietf-smtp@imc.org,
        presnick@qualcomm.com, hardie@qualcomm.com, ned.freed@mrochek.com
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA) 
In-Reply-To: Your message of "Mon, 27 Oct 2003 17:39:32 PST."
             <014c01c39cf4$5675cd60$79d52b09@DAVIS1> 
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU>
            <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1503687178P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 28 Oct 2003 15:07:19 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1503687178P
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, 27 Oct 2003 17:39:32 PST, Mark Davis said:

> email addresses. Mr. Tanaka can have one with Latin letters and one wit=
h
> Japanese (e.g. =E3=83=A0=E3=83=AB=E3=82=AF@=E3=82=AB=E3=82=AF.=E3=83=AF=
=E3=82=B7=E3=83=B3=E3=82=B0=E3=83=88=E3=83=B3.=E3=82=A8=E3=83=87=E3=82=A5=
).

This gets interesting in the context of a "reply all".

Apologies for breaking the UTF-8 in the quote, but it's illustrative - if=
 the
breakage had been in the To/Cc lines, things would have broken even worse=

unless whatever scheme we end up using is ASCII-transparent.

--==_Exmh_-1503687178P
Content-Type: application/pgp-signature

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

iD8DBQE/nsx3cC3lWbTT17ARAlD1AKC74t7EwonvMVVb4YcOTjs6cE9mCwCfX9xR
fx4FhsH1KZDlHM6R8Ip+I+A=
=61XB
-----END PGP SIGNATURE-----

--==_Exmh_-1503687178P--



From owner-ietf@ietf.org  Tue Oct 28 22:10:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17932
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 22:10:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEg5l-0002Zb-MB
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 21:29:49 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEd5C-00048E-Rc
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 18:17:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06316;
	Tue, 28 Oct 2003 18:16:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEd5A-0002ND-00; Tue, 28 Oct 2003 18:17:00 -0500
Received: from lakehearnglobal.coxinc.com ([206.157.224.254] helo=hatl0ms21.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEd59-0002Ma-00; Tue, 28 Oct 2003 18:16:59 -0500
Received: from CATL0MS81.corp.cox.com ([10.62.200.231]) by hatl0ms21.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 18:16:29 -0500
Received: from mail pickup service by CATL0MS81.corp.cox.com with Microsoft SMTPSVC;
	 Tue, 28 Oct 2003 18:16:28 -0500
Received: from hatl0ms23.corp.cox.com ([10.64.200.56]) by catl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 15:52:19 -0500
Received: from bastion2.cox.com ([10.225.2.51]) by hatl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 15:37:56 -0500
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion2.cox.com (8.11.7p1+Sun/8.11.6) with SMTP id h9SKbmv16600;
	Tue, 28 Oct 2003 15:37:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEZlm-0004nU-3B
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 14:44:46 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEXlX-00008u-Kd
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 12:36:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11141;
	Tue, 28 Oct 2003 12:36:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEXlV-0002Hm-00; Tue, 28 Oct 2003 12:36:22 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEXlV-0002Hi-00; Tue, 28 Oct 2003 12:36:21 -0500
Received: from bs.jck.com ([209.187.148.211] helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AEXlK-000NIP-00; Tue, 28 Oct 2003 12:36:11 -0500
Date: Tue, 28 Oct 2003 12:36:07 -0500
From: John C Klensin <klensin@jck.com>
To: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>,
        Mark Davis <mark.davis@jtcsv.com>,
        Mark Crispin <MRC@CAC.Washington.EDU>, Abhijit Menon-Sen <ams@wiw.org>
cc: "ietf-imaa@imc.org" <ietf-imaa@imc.org>,
        "idn@ops.ietf.org" <idn@ops.ietf.org>,
        "ietf-822@imc.org" <ietf-822@imc.org>, "ietf@ietf.org" <ietf@ietf.org>,
        "ietf-pop3ext@imc.org" <ietf-pop3ext@imc.org>,
        "lemonade@ietf.org" <lemonade@ietf.org>,
        "discuss@apps.ietf.org" <discuss@apps.ietf.org>,
        "ietf-imapext@imc.org" <ietf-imapext@imc.org>,
        "ietf-smtp@imc.org" <ietf-smtp@imc.org>
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email
 Addresses (IEA)
Message-ID: <12344770.1067344567@KLENSIN-TP>
In-Reply-To: <280960000.1067357574@classic.viagenie.qc.ca>
References: <E1AEH14-000N0E-GD@psg.com>
 <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU>
 <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU>
  <20031028095243.A1525@lustre.dyn.wiw.org>
 <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>
  <00a001c39d65$b23177f0$7900a8c0@DAVIS1>
 <280960000.1067357574@classic.viagenie.qc.ca>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Oct 2003 20:37:57.0507 (UTC) FILETIME=[5EF05D30:01C39D93]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Tuesday, October 28, 2003 11:12 -0500 Marc Blanchet
<Marc.Blanchet@viagenie.qc.ca> wrote:

> it appears to me that this thread is not very different from
> the idn considerations on usage of idn in the world. So what
> is really new in this discussion?

See the draft.

Quick answer: DNS interfaces really exist at the protocol level,
and a large part of the hypothesis behind IDNA was that it would
be possible, after we had enough implementations, to prevent an
end-user from ever seeing an encoded domain name.  That story
just doesn't hold for a special encoding-based (aka MUA-only)
email local part implementation, and maybe not for email
generally.  For example, under current rules, an MTA is required
to stuff the name it actually sees in HELO/EHLO and the MAIL
command into various headers.  If it is expected to notice that
they have special encodings and decodes them, we've gone rather
far into "the infrastructure is involved", even if the actual
on-the-wire transport is not impacted.  If it doesn't do that,
the encodings --both the IDNA domain parts and the special mail
encoding-- are going to be in the user's face, in the most
literal sense of that term.  

The similarity of that situation to the early IDN discussions is
the importance of the "what problem are you solving" question.
And it is very clear to me that, for email addresses, the answer
has got to "user sees their own characters in their email
addresses and the email addresses of those whose languages they
speak/ recognize.  Users typically don't actually see envelopes.
But seeing, e.g., different forms/codings of an address in the
header "From:" field than appears in "Return-path:" or than
appears in a signature line in the message body, is going to
create real unhappiness.  Similarly as has been pointed out in
another context, seeing an address in different from when it
appears in a header than when it (and that header) are
encapsulated in a message/?? body part is just not going to
amuse any user to whom we've said "ok, now you have i18n
strings, enjoy your new found local language capabilities".  And
I guess that tells you what I think the problem is that we need
to solve.  YMMD.

     john
 




From owner-ietf@ietf.org  Tue Oct 28 22:11:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18230
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 22:11:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEg5s-0002r5-1x
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 21:29:56 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEdtF-0002J8-FT
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 19:08:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09619;
	Tue, 28 Oct 2003 19:08:32 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEdtD-0003Rv-00; Tue, 28 Oct 2003 19:08:43 -0500
Received: from lakehearnglobal.coxinc.com ([206.157.224.254] helo=hatl0ms21.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEdtC-0003RD-00; Tue, 28 Oct 2003 19:08:42 -0500
Received: from catl0ms22.corp.cox.com ([10.62.200.101]) by hatl0ms21.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 19:08:13 -0500
Received: from mail pickup service by catl0ms22.corp.cox.com with Microsoft SMTPSVC;
	 Tue, 28 Oct 2003 18:58:56 -0500
Received: from hatl0ms22.CORP.COX.COM ([10.62.201.69]) by catl0ms22.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 16:35:02 -0500
Received: from bastion2.cox.com ([10.225.2.51]) by hatl0ms22.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 16:28:31 -0500
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion2.cox.com (8.11.7p1+Sun/8.11.6) with SMTP id h9SLSRO10130;
	Tue, 28 Oct 2003 16:28:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEajF-0001VS-2l
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 15:46:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEa7u-00033N-AZ
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 15:07:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20519;
	Tue, 28 Oct 2003 15:07:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEa7s-0005if-00; Tue, 28 Oct 2003 15:07:36 -0500
Received: from turing-police.cc.vt.edu ([128.173.14.107])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEa7r-0005iU-00; Tue, 28 Oct 2003 15:07:35 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9SK7J6P004972;
	Tue, 28 Oct 2003 15:07:19 -0500
Message-Id: <200310282007.h9SK7J6P004972@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Mark Davis <mark.davis@jtcsv.com>
Cc: Mark Crispin <MRC@CAC.Washington.EDU>, Keith Moore <moore@cs.utk.edu>,
        dcrocker@brandenburg.com, paf@Cisco.COM, ietf-imaa@imc.org,
        idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        IMAP Extensions WG <ietf-imapext@imc.org>, ietf-smtp@imc.org,
        presnick@qualcomm.com, hardie@qualcomm.com, ned.freed@mrochek.com
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA) 
In-Reply-To: Your message of "Mon, 27 Oct 2003 17:39:32 PST."
             <014c01c39cf4$5675cd60$79d52b09@DAVIS1> 
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU>
            <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1503687178P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 28 Oct 2003 15:07:19 -0500
X-OriginalArrivalTime: 28 Oct 2003 21:28:31.0955 (UTC) FILETIME=[6F9C6230:01C39D9A]
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1503687178P
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, 27 Oct 2003 17:39:32 PST, Mark Davis said:

> email addresses. Mr. Tanaka can have one with Latin letters and one wit=
h
> Japanese (e.g. =E3=83=A0=E3=83=AB=E3=82=AF@=E3=82=AB=E3=82=AF.=E3=83=AF=
=E3=82=B7=E3=83=B3=E3=82=B0=E3=83=88=E3=83=B3.=E3=82=A8=E3=83=87=E3=82=A5=
).

This gets interesting in the context of a "reply all".

Apologies for breaking the UTF-8 in the quote, but it's illustrative - if=
 the
breakage had been in the To/Cc lines, things would have broken even worse=

unless whatever scheme we end up using is ASCII-transparent.

--==_Exmh_-1503687178P
Content-Type: application/pgp-signature

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

iD8DBQE/nsx3cC3lWbTT17ARAlD1AKC74t7EwonvMVVb4YcOTjs6cE9mCwCfX9xR
fx4FhsH1KZDlHM6R8Ip+I+A=
=61XB
-----END PGP SIGNATURE-----

--==_Exmh_-1503687178P--




From owner-ietf@ietf.org  Tue Oct 28 22:15:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18851
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 22:15:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEg74-0003Fo-Li
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 21:31:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEevW-0004ov-Tj
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 20:15:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14008
	for <ietf@ietf.org>; Tue, 28 Oct 2003 20:15:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEevV-000546-00
	for ietf@ietf.org; Tue, 28 Oct 2003 20:15:09 -0500
Received: from mtiwmhc13.worldnet.att.net ([204.127.131.117])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEevU-00052G-00
	for ietf@ietf.org; Tue, 28 Oct 2003 20:15:08 -0500
Received: from bolaba (209.sanjose-03-04rs16rt.ca.dial-access.att.net[12.81.1.209])
          by worldnet.att.net (mtiwmhc13) with SMTP
          id <20031029011433113008c3tde>; Wed, 29 Oct 2003 01:14:35 +0000
Message-ID: <031a01c39db9$65a9c000$010aff0a@bolaba>
From: "todd glassey" <todd.glassey@worldnet.att.net>
To: "Bruce Campbell" <bruce.campbell@ripe.net>
Cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        "Christian Huitema" <huitema@windows.microsoft.com>, <ietf@ietf.org>,
        <problem-statement@alvestrand.no>
References: <DAC3FCB50E31C54987CD10797DA511BA05D51E47@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com> <222145117.1067204085@[192.168.1.49]> <027e01c39ca1$31452a70$010aff0a@bolaba> <Pine.LNX.4.58.0310281054280.11194@x53.ripe.net>
Subject: Re: Proposed statement quotes wrong numbers
Date: Tue, 28 Oct 2003 17:09:12 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bruce -
----- Original Message ----- 
From: "Bruce Campbell" <bruce.campbell@ripe.net>
To: "todd glassey" <todd.glassey@worldnet.att.net>
Cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>; "Christian Huitema"
<huitema@windows.microsoft.com>; <ietf@ietf.org>;
<problem-statement@alvestrand.no>
Sent: Tuesday, October 28, 2003 1:59 AM
Subject: Re: Proposed statement quotes wrong numbers


> On Mon, 27 Oct 2003, todd glassey wrote:
>
> > What was the attendance of the last meeting then? and also what then is
the
> > sum total of unique EMail Addresses in the Lists then too? I.e. what is
the
> > total size of the Vetting Community Resource that the IETF brings to the
> > Party as an enterprise/org???
>
> Are you sure that you can count the (large) number of subscribers that are
> on the main IETF lists, and the umpteen WG lists, as participants?

participants as far as meetings are concerned? no - obviously not, but this
pool of good email addresses constitute the core value of the IETF, that
being its Vettig Pool. So yes indeed, and also remember that the IETF is a
voluntary particpation standards process and platform, and that the reliable
email addresses for this "Vetting Pool" is what the core of the IETF's ideas
are vetted against. So put on your "organizational leader's" hat and then
ask me the same question -

> There
> seem to be a lot of people who are subscribed to various IETF-related
> lists who do not seem to participate in the IETF discussions.

But the point is that they have the option. Its their choice as to whether
to participate of not.

>
> ( But theres still a lot more than just 700 people who participate in the
>   IETF )

I agree - so lets ask the question again, how many unique names are there in
the lists - what's the total 'verified email addresses' that make up the
total of the vetting pool? - 5000 - 10000 - 50000? what is it? Harald? -
this seems like a number that you as the Chair of the IETF would not only be
proud of, but would also have on the top of your head on a monthly basis...
Any ideas as to the number?

Todd


>
> --==--
> Bruce.




From owner-ietf@ietf.org  Tue Oct 28 22:15:56 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18854
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 22:15:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEg6u-0002wM-0c
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 21:31:00 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEeAo-0004G1-T1
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 19:26:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10743;
	Tue, 28 Oct 2003 19:26:42 -0500 (EST)
From: Margaret.Wasserman@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEeAn-0003pI-00; Tue, 28 Oct 2003 19:26:53 -0500
Received: from lakehearnglobal.coxinc.com ([206.157.224.254] helo=hatl0ms21.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEeAm-0003oo-00; Tue, 28 Oct 2003 19:26:52 -0500
Received: from CATL0MS81.corp.cox.com ([10.62.200.231]) by hatl0ms21.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 19:26:23 -0500
Received: from mail pickup service by CATL0MS81.corp.cox.com with Microsoft SMTPSVC;
	 Tue, 28 Oct 2003 19:26:22 -0500
Received: from hatl0ms23.corp.cox.com ([10.64.200.56]) by catl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 15:49:23 -0500
Received: from bastion2.cox.com ([10.225.2.51]) by hatl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 15:35:41 -0500
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion2.cox.com (8.11.7p1+Sun/8.11.6) with SMTP id h9SKZbv10724;
	Tue, 28 Oct 2003 15:35:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEZle-0004TG-2K
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 14:44:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEX6y-0000ni-Ga
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 11:54:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07634;
	Tue, 28 Oct 2003 11:54:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEX6x-0000xX-00; Tue, 28 Oct 2003 11:54:27 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEX6w-0000xK-00; Tue, 28 Oct 2003 11:54:26 -0500
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9SGsPI05937;
	Tue, 28 Oct 2003 18:54:25 +0200 (EET)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T659074b434ac158f21083@esvir01nok.ntc.nokia.com>;
 Tue, 28 Oct 2003 18:54:24 +0200
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 28 Oct 2003 10:54:22 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Tue, 28 Oct 2003 11:54:21 -0500
Message-ID: <E320A8529CF07E4C967ECC2F380B0CF902443EA6@bsebe001.americas.nokia.com>
Thread-Topic: FYI: BOF on Internationalized Email Addresses (IEA)
Thread-Index: AcOdY3TL2xxUnJupRI2uu4njYAvuPgAD/9pQ
To: <idn@ops.ietf.org>, <ietf-822@imc.org>, <ietf@ietf.org>,
        <ietf-pop3ext@imc.org>, <lemonade@ietf.org>, <discuss@apps.ietf.org>,
        <ietf-imapext@imc.org>, <ietf-smtp@imc.org>, <ietf-imaa@imc.org>
X-OriginalArrivalTime: 28 Oct 2003 16:54:22.0543 (UTC) FILETIME=[22FF4DF0:01C39D74]
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


Excuse me, but could you please constrain this
conversation to fewer than 9 (nine!) e-mail lists?

The BOF description lists imaa@imc.org as the
discussion list, but this discussion is being
cc:ed to ietf-imaa@imc.org.  I'd suggest that you
move this discussion to whichever of those lists
is actually correct.

Margaret





From owner-ietf@ietf.org  Tue Oct 28 22:17:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19147
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 22:17:22 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEg75-0003Gu-A9
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 21:31:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEf2p-0004wG-B4
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 20:22:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14266
	for <ietf@ietf.org>; Tue, 28 Oct 2003 20:22:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEf2n-00059Z-00
	for ietf@ietf.org; Tue, 28 Oct 2003 20:22:41 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEf2n-00059W-00
	for ietf@ietf.org; Tue, 28 Oct 2003 20:22:41 -0500
Received: from bs.jck.com ([209.187.148.211] helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AEf2i-0001OA-00; Tue, 28 Oct 2003 20:22:36 -0500
Date: Tue, 28 Oct 2003 18:03:15 -0500
From: John C Klensin <john-ietf@jck.com>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: ietf-imaa@imc.org, ietf@ietf.org
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email
 Addresses (IEA)
Message-ID: <1694652.1067364195@localhost>
In-Reply-To: <355752681.20031027161925@brandenburg.com>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 <12228881609.20031027074111@brandenburg.com>
 <20031027105222.4eae54fd.moore@cs.utk.edu>
 <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
 <355752681.20031027161925@brandenburg.com>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave,

(distro trimmed to IMAA and IETF lists; I hope we can soon get
rid of the latter too).

One large problem with the charter draft (I'm too tired to know
if there are small ones)...

If one is going to consider internationalization of email
addresses in a way that permits them to move through the mail
protocol in some traditional Unicode encoding  (e.g., UTF-8),
then I believe that we at least need to entertain the notion
that what we are going after is "mailbox", rather than "local
part".  Yes, the hard work lies in the local part.  But, to me,
the goal is to have an I18N presentation form that is also
carried over the protocol.   

That implies that one should be able to have
      local-part-i18n@FQDN-i18n
(UTF-8 on both sides or, if you prefer, throughout the string
(since the coding of "@" in UTF-8 is the same as it is in ASCII) 

rather than, e.g.,
      local-part-i18n@FQDN-IDNA
(UTF-8 on the LHS, but punycode for any domain labels that use
non-ASCII).

Again, the goal is that this should be natural for the user,
using the user's script (or the script of the recipient), both
in protocol transactions and in the case of "My email address is
xx@yy." in the body of a message... where the only parts of that
sentence (appropriately translated) which are a ASCII characters
are the @-sign and _maybe_ the TLD (whether the TLD can be
non-ASCII is presumably an ICANN problem unless the user
interface does something akin to draft-klensin-idn-tld-01.txt). 

If the email address the user sees _looks_ like local script in
the local part, but is forced into ASCII/punycode in the domain
part, I think the users will assume that we have been smoking
something.  And, arguably, they will be right --punycode is a
way of transporting internationalized data so it doesn't foul up
other systems or cause DNS damage.  But, from the user
standpoint, however much users hate, e.g., a string representing
a name transliterated into Roman characters, they will hate
looking at punycode-- which has no mnemonic value at all for
non-Roman scripts-- even more.

So please don't prejudge the question of what happens to the
domain part (right hand side) of an email address in the
charter: this set of issues should at lease be considered very
carefully.

      john



--On Monday, October 27, 2003 16:19 -0800 Dave Crocker
<dhc@dcrocker.net> wrote:

> Folks,
> 
> On the theory that discussions go better when they have a
> concrete deliverable, here is a proposed charter for a
> proposed working group.
> 
> The following started with Mark Crispin's text, although it
> might not look it. Besides the usual goals for a charter, the
> following text attempts to specify the problem domain in the
> narrowest feasible form that is valid. If anyone thinks the
> scope is too narrow, they need to explain why.
> 
> 
> 
> DRAFT CHARTER
> 
> Mail Internationalised Local-Part (MILP)
> ---------------------------------
> 
> The <local-part> portion of RFC2822 and <Local-part> portion
> of RFC2821 mail addresses are restricted to a subset of ASCII.
> This poses a fundamental barrier for users needing mail
> addresses to be expressed in a richer set of characters, such
> as Latin characters with diacriticals and the many Asian
> characters. The goal of the current work is to add local-part
> support for these additional characters, while preserving the
> large, installed base of ASCII usage.
> 
> The group will take:
> 
>    draft-hoffman-imaa-03.txt
>    draft-klensin-emailaddr-i18n-01.txt
>    draft-duerst-iri-04.txt
> 
> as input to discussions.
> 
> The group will pay particular attention to barriers to
> adoption and utility, as well as any impact the new scheme
> might have on the existing base of Internet mail usage.
> 
> 
> Milestones
> ----------
> 
> Nov, 03:  BOF
> 
> Dec, 03:  WG chartered
> 
> Feb, 03:  Initial draft of working group specifications.
> 
> Jun, 03:  Specifications submitted for IETF approval
> 
> 
> d/
> --
>  Dave Crocker <dcrocker-at-brandenburg-dot-com>
>  Brandenburg InternetWorking <www.brandenburg.com>
>  Sunnyvale, CA  USA <tel:+1.408.246.8253>
> 
> 
>  







From owner-ietf@ietf.org  Tue Oct 28 22:18:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19443
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 22:18:57 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEg75-0003H0-Jf
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 21:31:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEf2r-0004wI-4F
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 20:22:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14270
	for <ietf@ietf.org>; Tue, 28 Oct 2003 20:22:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEf2p-00059f-00
	for ietf@ietf.org; Tue, 28 Oct 2003 20:22:43 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEf2o-00059c-00
	for ietf@ietf.org; Tue, 28 Oct 2003 20:22:42 -0500
Received: from bs.jck.com ([209.187.148.211] helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1AEf2o-0001OA-00; Tue, 28 Oct 2003 20:22:42 -0500
Date: Tue, 28 Oct 2003 18:40:03 -0500
From: John C Klensin <john-ietf@jck.com>
To: Mark Crispin <mrc@CAC.Washington.EDU>
cc: ietf-imaa@imc.org, ietf@ietf.org
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email
 Addresses (IEA)
Message-ID: <3903227.1067366403@localhost>
In-Reply-To: <E1AEH14-000N0E-GD@psg.com>
References:  <E1AEH14-000N0E-GD@psg.com>
X-Mailer: Mulberry/3.0.3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Monday, October 27, 2003 11:10 -0800 Mark Crispin
<mrc@CAC.Washington.EDU> wrote:

> On Mon, 27 Oct 2003, Keith Moore wrote:
> 
>  >> Thanks for taking a stab at a problem statement.  I'd like
> to drill down  >> on this just a bit.
>  >> What is the source of the "growing need"?  Is it:
>  >> [snip]
> 
> 
> I agree that this needs to be stated, but someone other than
> me will have to do it.
> 
> I believe that the primary push for this functionality comes
> from regions which use Latin alphabetics with diacriticals;
> and that most individuals in regions which do not use Latin
> script are accept the use of Latin script for multinational
> interchange.  In many regions where Latin diacriticals are
> used, there is no acceptable transform of a surname to a form
> that does not use diacriticals.  Simply omitting the
> diacritical causes (at least to the inhabitants of those
> regions) a misspelling.
>...

Actually, unlike the original push for internationalization of
email message bodies, and some of the push for IDNs, most of the
push I'm seeing for this are coming from folks with distinctly
non-Latin (i.e., not Cyrillic or Greek either) scripts... e.g.,
east Asia, middle east, etc.

I can't speak for the motivations of the others who have thought
and written about the problem.

So these are real "different characters" issues, not the
complexities of dealing with diacriticals on Latin letters and
what their omission might mean.

     john





From owner-ietf@ietf.org  Tue Oct 28 22:21:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19679
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 22:21:21 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEg7J-0003Pb-85
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 21:31:25 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEfKi-0000RU-4F
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 20:41:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15663;
	Tue, 28 Oct 2003 20:41:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEfKf-0005dR-00; Tue, 28 Oct 2003 20:41:09 -0500
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEfKf-0005dN-00; Tue, 28 Oct 2003 20:41:09 -0500
Received: from [63.202.92.152] (adsl-66-125-125-69.dsl.pltn13.pacbell.net [66.125.125.69])
	(authenticated bits=0)
	by above.proper.com (8.12.10/8.12.8) with ESMTP id h9T1f6I8016895;
	Tue, 28 Oct 2003 17:41:06 -0800 (PST)
	(envelope-from phoffman@imc.org)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p06002021bbc4cab20108@[63.202.92.152]>
In-Reply-To: 
 <E320A8529CF07E4C967ECC2F380B0CF902443EA6@bsebe001.americas.nokia.com>
References: 
 <E320A8529CF07E4C967ECC2F380B0CF902443EA6@bsebe001.americas.nokia.com>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Tue, 28 Oct 2003 17:41:55 -0800
To: Margaret.Wasserman@nokia.com, <idn@ops.ietf.org>, <ietf-822@imc.org>,
        <ietf@ietf.org>, <ietf-pop3ext@imc.org>, <lemonade@ietf.org>,
        <discuss@apps.ietf.org>, <ietf-imapext@imc.org>, <ietf-smtp@imc.org>,
        <ietf-imaa@imc.org>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Location of the IMAA list (was: RE: FYI: BOF on Internationalized
 Email Addresses (IEA))
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 11:54 AM -0500 10/28/03, Margaret.Wasserman@nokia.com wrote:
>The BOF description lists imaa@imc.org as the
>discussion list, but this discussion is being
>cc:ed to ietf-imaa@imc.org.  I'd suggest that you
>move this discussion to whichever of those lists
>is actually correct.

It is ietf-imaa@imc.org, although because Patrik sent out the wrong 
address, I have made sure that both addresses work. An archive of the 
list, and links to the current versions of the drafts, can be found 
at <http://www.imc.org/ietf-imaa/>.

No more messages to all lists: that's what the IMAA list is for.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Tue Oct 28 22:58:23 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21986
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 22:58:23 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEh0A-00082l-K1
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 22:28:06 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEgN9-000434-1O
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 21:47:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17255
	for <ietf@ietf.org>; Tue, 28 Oct 2003 21:47:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEgN6-0006MW-00
	for ietf@ietf.org; Tue, 28 Oct 2003 21:47:45 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEgN6-0006ME-00
	for ietf@ietf.org; Tue, 28 Oct 2003 21:47:44 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9T2r4f25793;
	Tue, 28 Oct 2003 18:53:04 -0800
Date: Tue, 28 Oct 2003 18:16:46 -0800
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v2.00.22)
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <1957796741.20031028181646@brandenburg.com>
To: John C Klensin <john-ietf@jck.com>
CC: ietf-imaa@imc.org, ietf@ietf.org
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <1694652.1067364195@localhost>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 <12228881609.20031027074111@brandenburg.com>
 <20031027105222.4eae54fd.moore@cs.utk.edu>
 <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
 <355752681.20031027161925@brandenburg.com> <1694652.1067364195@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

JCK> If one is going to consider internationalization of email
JCK> addresses in a way that permits them to move through the mail
JCK> protocol in some traditional Unicode encoding  (e.g., UTF-8),
JCK> then

...then we get to repeat the mime/esmtp debates all over again.  After all,
why should we even try to learn anything from 10 years of experience.  (And
no, John, I'm not directing my comment at you.)

To be specific: I am not suggesting that pure utf-8 is a bad goal -- although
the fact that utf-8 is, itself, a condensed representation of unicode should
strike folks as a just a tad ironic, with respect to these discussions.

Rather, I suggest that it be a _separate_ goal from near-term support of an
edge-only enhancement for Unicode support, the same as we did for mime and
IDN.

We already have that support for domain names. That only leaves local-part.

It's fine to pursue a separate path for long-term 8-bit purity.  I'm sure we
will achieve it much sooner for addresses than we have for content.


JCK> Again, the goal is that this should be natural for the user,
JCK> using the user's script (or the script of the recipient), both
JCK> in protocol transactions and in the case of "My email address is
JCK> xx@yy."

The business card representation of an email address is the classic example of
IETF work that very much _does_ directly involve the user interface.  However
we already dealt with this issue for non-ascii domain names.  We do not need
to rehash this issue yet again.

As for the protocol, I could have sworn that users do not type protocol data
units directly, or at least that they haven't for roughly 25 years.  (Another
jibe, citing the fact that utf-8 is, itself, a modification to "raw" unicode
is probably worth repeating, here.)



JCK> in the body of a message... where the only parts of that
JCK> sentence (appropriately translated) which are a ASCII characters
JCK> are the @-sign and _maybe_ the TLD (whether the TLD can be
JCK> non-ASCII is presumably an ICANN problem unless the user
JCK> interface does something akin to draft-klensin-idn-tld-01.txt).

Indeed, representation of non-ascii addressing information within a text
segment is an interesting problem.  I'd guess it's identical to the business
card requirement.

And the current issue is no different than we have for IDN.

So perhaps the right thing to do is forget about IDN.  Pretend it never
happen.  Let's start all over.

Or, perhaps we could complete the design approach started by IDN, while
_separately_ pursuing the purist approach of end-to-end 8-bit.


JCK> So please don't prejudge the question of what happens to the
JCK> domain part (right hand side) of an email address in the
JCK> charter: this set of issues should at lease be considered very
JCK> carefully.

Indeed it should, including tidbits like adoption barriers, and the last
several years of IDN work.

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Tue Oct 28 23:27:15 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22933
	for <ietf-web-archive@odin.ietf.org>; Tue, 28 Oct 2003 23:27:15 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEhe7-0002j8-RX
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 23:09:23 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEhId-0001HA-Ki
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 22:47:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21602
	for <ietf@ietf.org>; Tue, 28 Oct 2003 22:47:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEhIb-0000FI-00
	for ietf@ietf.org; Tue, 28 Oct 2003 22:47:09 -0500
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEhIa-0000EW-00
	for ietf@ietf.org; Tue, 28 Oct 2003 22:47:09 -0500
Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57])
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id h9T3Om102527;
	Tue, 28 Oct 2003 22:24:49 -0500
From: "bill" <bill@strahm.net>
To: "'todd glassey'" <todd.glassey@worldnet.att.net>
Cc: <ietf@ietf.org>
Subject: RE: Proposed statement quotes wrong numbers
Date: Tue, 28 Oct 2003 19:46:29 -0800
Message-ID: <000401c39dcf$3cf02cb0$1c02a8c0@mobilebill>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <031a01c39db9$65a9c000$010aff0a@bolaba>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I disagree with your analysis todd.

The strength of the IETF is not in the number of unique e-mail address
on its e-mail lists (define unique - I have subscribed from probably 10
e-mail addresses over the years - many people I know are subscribed with
multiple "unique" addresses - many address in reality point to archiving
services, other reflectors, peoples inboxes that don't look at the
e-mail

So I don't think you can even count the number of unique e-mail
addresses - but if you could -

Peoples technical content/quality very widely, some input is worthless
(or close to it) and many just monitor what is going on... Other e-mail
is critical - either in technical content, providing an alternative
viewpoint etc.

The strength of the IETF is that it is a gathering point for all of
these people.  Not a quantity of e-mail addresses that can be spammed or
something else

Bill

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of todd
glassey
Sent: Tuesday, October 28, 2003 5:09 PM
To: Bruce Campbell
Cc: Harald Tveit Alvestrand; Christian Huitema; ietf@ietf.org;
problem-statement@alvestrand.no
Subject: Re: Proposed statement quotes wrong numbers


Bruce -
----- Original Message ----- 
From: "Bruce Campbell" <bruce.campbell@ripe.net>
To: "todd glassey" <todd.glassey@worldnet.att.net>
Cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>; "Christian
Huitema" <huitema@windows.microsoft.com>; <ietf@ietf.org>;
<problem-statement@alvestrand.no>
Sent: Tuesday, October 28, 2003 1:59 AM
Subject: Re: Proposed statement quotes wrong numbers


> On Mon, 27 Oct 2003, todd glassey wrote:
>
> > What was the attendance of the last meeting then? and also what then

> > is
the
> > sum total of unique EMail Addresses in the Lists then too? I.e. what

> > is
the
> > total size of the Vetting Community Resource that the IETF brings to

> > the Party as an enterprise/org???
>
> Are you sure that you can count the (large) number of subscribers that

> are on the main IETF lists, and the umpteen WG lists, as participants?

participants as far as meetings are concerned? no - obviously not, but
this pool of good email addresses constitute the core value of the IETF,
that being its Vettig Pool. So yes indeed, and also remember that the
IETF is a voluntary particpation standards process and platform, and
that the reliable email addresses for this "Vetting Pool" is what the
core of the IETF's ideas are vetted against. So put on your
"organizational leader's" hat and then ask me the same question -

> There
> seem to be a lot of people who are subscribed to various IETF-related 
> lists who do not seem to participate in the IETF discussions.

But the point is that they have the option. Its their choice as to
whether to participate of not.

>
> ( But theres still a lot more than just 700 people who participate in
the
>   IETF )

I agree - so lets ask the question again, how many unique names are
there in the lists - what's the total 'verified email addresses' that
make up the total of the vetting pool? - 5000 - 10000 - 50000? what is
it? Harald? - this seems like a number that you as the Chair of the IETF
would not only be proud of, but would also have on the top of your head
on a monthly basis... Any ideas as to the number?

Todd


>
> --==--
> Bruce.





From owner-ietf@ietf.org  Wed Oct 29 02:20:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15837
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 02:20:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEkSm-0002tj-LP
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 02:09:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEkMj-0000e2-Gz
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 02:03:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01892
	for <ietf@ietf.org>; Wed, 29 Oct 2003 02:03:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEkMh-0002qg-00
	for ietf@ietf.org; Wed, 29 Oct 2003 02:03:35 -0500
Received: from mtiwmhc11.worldnet.att.net ([204.127.131.115])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEkMg-0002qK-00
	for ietf@ietf.org; Wed, 29 Oct 2003 02:03:34 -0500
Received: from bolaba (209.sanjose-03-04rs16rt.ca.dial-access.att.net[12.81.1.209])
          by worldnet.att.net (mtiwmhc11) with SMTP
          id <2003102907030211100l6sv3e>; Wed, 29 Oct 2003 07:03:03 +0000
Message-ID: <042701c39dea$14749a80$010aff0a@bolaba>
From: "todd glassey" <todd.glassey@worldnet.att.net>
To: "bill" <bill@strahm.net>
Cc: <ietf@ietf.org>
References: <000401c39dcf$3cf02cb0$1c02a8c0@mobilebill>
Subject: Re: Proposed statement quotes wrong numbers
Date: Tue, 28 Oct 2003 21:56:43 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bill - you are missing the picture. The ultimate number of bodies that the
IETF can count on are those unique email addresses. No one said they were
any particular Vetting Initiative but rather the total possible number of
"representative opinions" that any consensus could possibly count on -
assuming an "across the Organizational breadth" as the metric.

The IETF is supposed to be representative of the people of the world and
their representatives to the task of building Internet protocols, right? So
then the unique email addresses are a direct metric on how well the world is
represented. Wouldn't you say?

Todd


----- Original Message ----- 
From: "bill" <bill@strahm.net>
To: "'todd glassey'" <todd.glassey@worldnet.att.net>
Cc: <ietf@ietf.org>
Sent: Tuesday, October 28, 2003 7:46 PM
Subject: RE: Proposed statement quotes wrong numbers


> I disagree with your analysis todd.
>
> The strength of the IETF is not in the number of unique e-mail address
> on its e-mail lists (define unique - I have subscribed from probably 10
> e-mail addresses over the years - many people I know are subscribed with
> multiple "unique" addresses - many address in reality point to archiving
> services, other reflectors, peoples inboxes that don't look at the
> e-mail

Thats a problem with the Registration Process then.

>
> So I don't think you can even count the number of unique e-mail
> addresses - but if you could -
>
> Peoples technical content/quality very widely, some input is worthless
> (or close to it) and many just monitor what is going on... Other e-mail
> is critical - either in technical content, providing an alternative
> viewpoint etc.

What has that to do with how many possible opinions are available herein?

>
> The strength of the IETF is that it is a gathering point for all of
> these people.

You mean the mailing lists right? - so count the members...

>  Not a quantity of e-mail addresses that can be spammed or
> something else

Bill -  you have not discounted or invalidated anything I have said here. My
comment stands.

>
> Bill
>
> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of todd
> glassey
> Sent: Tuesday, October 28, 2003 5:09 PM
> To: Bruce Campbell
> Cc: Harald Tveit Alvestrand; Christian Huitema; ietf@ietf.org;
> problem-statement@alvestrand.no
> Subject: Re: Proposed statement quotes wrong numbers
>
>
> Bruce -
> ----- Original Message ----- 
> From: "Bruce Campbell" <bruce.campbell@ripe.net>
> To: "todd glassey" <todd.glassey@worldnet.att.net>
> Cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>; "Christian
> Huitema" <huitema@windows.microsoft.com>; <ietf@ietf.org>;
> <problem-statement@alvestrand.no>
> Sent: Tuesday, October 28, 2003 1:59 AM
> Subject: Re: Proposed statement quotes wrong numbers
>
>
> > On Mon, 27 Oct 2003, todd glassey wrote:
> >
> > > What was the attendance of the last meeting then? and also what then
>
> > > is
> the
> > > sum total of unique EMail Addresses in the Lists then too? I.e. what
>
> > > is
> the
> > > total size of the Vetting Community Resource that the IETF brings to
>
> > > the Party as an enterprise/org???
> >
> > Are you sure that you can count the (large) number of subscribers that
>
> > are on the main IETF lists, and the umpteen WG lists, as participants?
>
> participants as far as meetings are concerned? no - obviously not, but
> this pool of good email addresses constitute the core value of the IETF,
> that being its Vettig Pool. So yes indeed, and also remember that the
> IETF is a voluntary particpation standards process and platform, and
> that the reliable email addresses for this "Vetting Pool" is what the
> core of the IETF's ideas are vetted against. So put on your
> "organizational leader's" hat and then ask me the same question -
>
> > There
> > seem to be a lot of people who are subscribed to various IETF-related
> > lists who do not seem to participate in the IETF discussions.
>
> But the point is that they have the option. Its their choice as to
> whether to participate of not.
>
> >
> > ( But theres still a lot more than just 700 people who participate in
> the
> >   IETF )
>
> I agree - so lets ask the question again, how many unique names are
> there in the lists - what's the total 'verified email addresses' that
> make up the total of the vetting pool? - 5000 - 10000 - 50000? what is
> it? Harald? - this seems like a number that you as the Chair of the IETF
> would not only be proud of, but would also have on the top of your head
> on a monthly basis... Any ideas as to the number?
>
> Todd
>
>
> >
> > --==--
> > Bruce.
>
>




From owner-ietf@ietf.org  Wed Oct 29 02:31:26 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25887
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 02:31:26 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEkUD-0003Di-Qg
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 02:11:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEkQE-0002Nk-4E
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 02:07:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05501
	for <ietf@ietf.org>; Wed, 29 Oct 2003 02:07:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEkQB-0002u3-00
	for ietf@ietf.org; Wed, 29 Oct 2003 02:07:11 -0500
Received: from coconut.itojun.org ([219.101.47.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEkQB-0002u0-00
	for ietf@ietf.org; Wed, 29 Oct 2003 02:07:11 -0500
Received: from itojun.org (localhost [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP id 2262613
	for <ietf@ietf.org>; Wed, 29 Oct 2003 16:07:11 +0900 (JST)
To: ietf@ietf.org
Subject: mailman switchover: password unknown
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
From: itojun@iijlab.net
Date: Wed, 29 Oct 2003 16:07:11 +0900
Message-Id: <20031029070711.2262613@coconut.itojun.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

	ipv6 and other wg mailing list have switched over to mailman, which
	is good.  however, i don't remember being informed of password to
	be used to control my mailman settings.  am i missing something?

itojun



From owner-ietf@ietf.org  Wed Oct 29 03:20:50 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27843
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 03:20:50 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AElGi-00084Y-IT
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 03:01:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEl7l-0007rZ-Ku
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 02:52:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26967
	for <ietf@ietf.org>; Wed, 29 Oct 2003 02:52:03 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEl7j-0003hL-00
	for ietf@ietf.org; Wed, 29 Oct 2003 02:52:11 -0500
Received: from h80ad24f3.async.vt.edu ([128.173.36.243] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEl7h-0003hD-00
	for ietf@ietf.org; Wed, 29 Oct 2003 02:52:10 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9T7pt43015326;
	Wed, 29 Oct 2003 02:51:55 -0500
Message-Id: <200310290751.h9T7pt43015326@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Zefram <zefram@fysh.org>
Cc: ietf-imaa@imc.org, ietf-822@imc.org, ietf@ietf.org, ietf-smtp@imc.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA) 
In-Reply-To: Your message of "Tue, 28 Oct 2003 15:13:06 GMT."
             <20031028151306.GA1549@fysh.org> 
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com> <12228881609.20031027074111@brandenburg.com> <20031027105222.4eae54fd.moore@cs.utk.edu> <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu> <20031027134403.5eaaee9e.moore@cs.utk.edu> <Pine.LNX.4.60.0310271059140.20831@shiva1.cac.washington.edu>
            <20031028151306.GA1549@fysh.org>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1326845046P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 29 Oct 2003 02:51:55 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1326845046P
Content-Type: text/plain; charset=us-ascii

On Tue, 28 Oct 2003 15:13:06 GMT, Zefram said:

> It doesn't start to get tricky until we get into the eastern European
> languages -- ASCII only intentionally provides western European
> diacriticals.

"Macrons and carons and cedillas, oh my..." :)

Actually, ASCII doesn't intentionally provide any diacriticals. Western
European diacriticals are in the Unicode Latin-1 Supplement, and (as you
correctly note) some of us of the eastern European persuasion need characters
from Latin-A and/or Latin-B to actually do things...
  
> Cue the debate about whether the diacritic should go before or after
> the base letter.

So tell me, does the dot on an 'i' go before or after the base letter?

(OK, so I'm just touchy because nobody on this side of the big puddle
wants to deal with the fact that the 3rd letter of the preferred spelling of
my last name is Unicode codepoint 0113 (Latin small e with macron)).


--==_Exmh_-1326845046P
Content-Type: application/pgp-signature

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

iD8DBQE/n3GbcC3lWbTT17ARAgVWAKCreVssgTRHdU1MG7hgWuD2IblKsgCcCpeg
khVJf7S35LV/zwtFwgFxDwI=
=kYpA
-----END PGP SIGNATURE-----

--==_Exmh_-1326845046P--



From owner-ietf@ietf.org  Wed Oct 29 05:38:20 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02076
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 05:38:20 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEnTI-0002ly-Vf
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 05:22:36 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEnFl-0002bl-Ml
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 05:08:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01407
	for <ietf@ietf.org>; Wed, 29 Oct 2003 05:08:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEnFi-0005UQ-00
	for ietf@ietf.org; Wed, 29 Oct 2003 05:08:34 -0500
Received: from smtp2.arin.net ([192.149.252.32])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEnFi-0005UA-00
	for ietf@ietf.org; Wed, 29 Oct 2003 05:08:34 -0500
Received: by smtp2.arin.net (Postfix, from userid 5003)
	id D4DB06DD; Wed, 29 Oct 2003 05:08:05 -0500 (EST)
Received: from ops.arin.net (ops [192.149.252.141])
	by smtp2.arin.net (Postfix) with ESMTP
	id 6D70F2ED; Wed, 29 Oct 2003 05:08:05 -0500 (EST)
Received: from ano2 ([192.136.136.114])
	by ops.arin.net (8.9.0/8.9.0) with ESMTP id FAA03558;
	Wed, 29 Oct 2003 05:08:02 -0500 (EST)
From: "Ray Plzak" <plzak@arin.net>
To: "'Bruce Campbell'" <bruce.campbell@ripe.net>,
        "'todd glassey'" <todd.glassey@worldnet.att.net>
Cc: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>,
        "'Christian Huitema'" <huitema@windows.microsoft.com>, <ietf@ietf.org>,
        <problem-statement@alvestrand.no>
Subject: RE: Proposed statement quotes wrong numbers
Date: Wed, 29 Oct 2003 05:07:54 -0500
Message-ID: <00e901c39e04$87a633a0$728888c0@arin.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <Pine.LNX.4.58.0310281054280.11194@x53.ripe.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-Spam-Status: No, hits=-0.3 required=5.0
	tests=IN_REP_TO,SPAM_PHRASE_01_02
	version=2.43-arin1
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On 
> Behalf Of Bruce Campbell
> Sent: Tuesday, October 28, 2003 5:00 AM
> To: todd glassey
> Cc: Harald Tveit Alvestrand; Christian Huitema; 
> ietf@ietf.org; problem-statement@alvestrand.no
> Subject: Re: Proposed statement quotes wrong numbers
> 
> 
> ( But theres still a lot more than just 700 people who 
> participate in the
>   IETF )
> 
> --==--
> Bruce.

There are certainly more than 700 who attend.  I don't know if you can
characterize them as all participating.

Ray
 




From owner-ietf@ietf.org  Wed Oct 29 09:01:13 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07678
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 09:01:13 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEqZQ-0006qj-2i
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 08:41:08 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEV5R-0003Tn-Na
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 09:44:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25341
	for <ietf@ietf.org>; Tue, 28 Oct 2003 09:44:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEV5Q-0004Ow-00
	for ietf@ietf.org; Tue, 28 Oct 2003 09:44:44 -0500
Received: from palrel11.hp.com ([156.153.255.246])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEV5P-0004Ol-00
	for ietf@ietf.org; Tue, 28 Oct 2003 09:44:43 -0500
Received: from iconsrv5.india.hp.com (iconsrv5.india.hp.com [15.42.229.13])
	by palrel11.hp.com (Postfix) with ESMTP
	id F11301C0703B; Tue, 28 Oct 2003 06:43:55 -0800 (PST)
Received: from nt23060 (nt23060.india.hp.com [15.42.230.60])
	by iconsrv5.india.hp.com (8.9.3 (PHNE_28810)/8.9.3 SMKit7.02) with ESMTP id UAA23203;
	Tue, 28 Oct 2003 20:12:31 +0530 (IST)
From: "Madan Ganesh Velayudham" <mganesh@india.hp.com>
To: "'Mark Davis'" <mark.davis@jtcsv.com>,
        "'Mark Crispin'" <mrc@cac.washington.edu>,
        "'Keith Moore'" <moore@cs.utk.edu>
Cc: <ietf-imaa@imc.org>, <idn@ops.ietf.org>, <ietf-822@imc.org>,
        <ietf@ietf.org>, <ietf-pop3ext@imc.org>, <ietf-smtp@imc.org>
Subject: RE: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Tue, 28 Oct 2003 20:13:42 +0530
Organization: Hewlett-Packard STSD
Message-ID: <000101c39d61$e38f3e30$3ce62a0f@nt23060>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
In-Reply-To: <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> I'm curious: why do you think that everyone would be=20
> satisfied with Latin characters only, and no non-Latin characters?
>=20
> Mark
> __________________________________
> http://www.macchiato.com
> =E2=96=BA =
=E0=A4=B6=E0=A4=BF=E0=A4=B7=E0=A5=8D=E0=A4=AF=E0=A4=BE=E0=A4=A6=E0=A4=BF=E0=
=A4=9A=E0=A5=8D=E0=A4=9B=E0=A5=87=E0=A4=A4=E0=A5=8D=E0=A4=AA=E0=A4=B0=E0=A4=
=BE=E0=A4=9C=E0=A4=AF=E0=A4=AE=E0=A5=8D =E2=97=84

Yes, I also agree. Especially in India, we have more than 10 Languages ( =
Hindi, Tamil, Telugu, Kannada, Malayalam, etc., )






From owner-ietf@ietf.org  Wed Oct 29 09:01:17 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07696
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 09:01:17 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEqZQ-0006qp-76
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 08:41:08 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEVFE-0005k7-Mw
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 09:54:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26531
	for <ietf@ietf.org>; Tue, 28 Oct 2003 09:54:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEVFC-0004oI-00
	for ietf@ietf.org; Tue, 28 Oct 2003 09:54:50 -0500
Received: from w1309.hostcentric.net ([66.40.78.254])
	by ietf-mx with smtp (Exim 4.12)
	id 1AEVFB-0004nt-00
	for ietf@ietf.org; Tue, 28 Oct 2003 09:54:49 -0500
Received: (qmail 23826 invoked by alias); 28 Oct 2003 14:54:45 -0000
Received: from unknown (HELO DAVIS1) (12.235.201.242)
  by 0 with SMTP; 28 Oct 2003 14:54:45 -0000
Message-ID: <006b01c39d63$6d928d70$7900a8c0@DAVIS1>
From: "Mark Davis" <mark.davis@jtcsv.com>
To: "Stephane Bortzmeyer" <bortzmeyer@nic.fr>
Cc: "Mark Crispin" <MRC@CAC.Washington.EDU>, "Keith Moore" <moore@cs.utk.edu>,
        <dcrocker@brandenburg.com>, <paf@cisco.com>, <ietf-imaa@imc.org>,
        <idn@ops.ietf.org>, <ietf-822@imc.org>, <ietf@ietf.org>,
        <ietf-pop3ext@imc.org>, <lemonade@ietf.org>, <discuss@apps.ietf.org>,
        "IMAP Extensions WG" <ietf-imapext@imc.org>, <ietf-smtp@imc.org>,
        <presnick@qualcomm.com>, <hardie@qualcomm.com>,
        <ned.freed@mrochek.com>
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <20031028085023.GB6617@nic.fr>
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Tue, 28 Oct 2003 06:54:45 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0068_01C39D20.5EDF9090"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0068_01C39D20.5EDF9090
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Sigh. I used "Greek" in an analogy because I was hoping that some of the =
Latin-only folks out there would at least recognize the name of one =
other script. But how comforable would you really be, if =
=D9=8A=D9=8F=D9=8F =D9=88=D9=90=D8=B1=D9=90 =
=D9=81=D9=8F=D8=B1=D8=B3=D9=90=D8=AF =D8=AA=D9=8F =
=D8=B1=D9=8E=D9=90=D8=AF =D9=8E=D9=86 =
=D9=90=D9=86=D8=AA=D9=90=D8=B1=D9=90=D9=84=D9=8A =
=D8=AF=D9=90=D9=81=D9=81=D9=90=D8=B1=D9=90=D9=86=D8=AA =
=D8=B3=D9=83=D8=B1=D9=90=D9=BE=D8=AA=D8=8C =
=D8=B3=D9=90=D9=85=D9=BE=D9=84=D9=8A =D8=AA=D9=8F =
=D9=8F=D9=86=D8=AF=D9=90=D8=B1=D8=B3=D8=AA=D9=8E=D9=86=D8=AF =
=D9=90=D9=85=D9=8E=D9=90=D9=84 =
=D9=8E=D8=AF=D8=AF=D8=B1=D9=90=D8=B3=D8=B3=D9=90=D8=B3=D8=8C =
=D9=8E=D9=86=D8=AF =D9=8E =D8=B3=D9=83=D8=B1=D9=90=D9=BE=D8=AA =
=D8=AA=D9=87=D9=8E=D8=AA =D9=83=D9=8F=D9=8F=D9=84=D8=AF =
=D9=8F=D9=86=D9=84=D9=8A =
=D9=BE=D9=8E=D8=B1=D8=AA=D9=8E=D9=90=D9=84=D9=84=D9=8A =
=D8=B1=D9=90=D9=81=D9=84=D9=90=D9=83=D8=AA =D8=AA=D9=87=D9=90 =
=D8=B1=D9=8E=D9=90=D9=84 =
=D8=B3=D9=BE=D9=90=D9=84=D9=84=D9=90=D9=86=DA=AF =D9=8F=D9=81 =
=D9=8A=D9=8F=D9=8F=D8=B1 =D9=88=D9=8F=D8=B1=D8=AF=D8=B3?

Mark
__________________________________

=20
----- Original Message -----=20
From: "Stephane Bortzmeyer" <bortzmeyer@nic.fr>
To: "Mark Davis" <mark.davis@jtcsv.com>
Cc: "Mark Crispin" <MRC@CAC.Washington.EDU>; "Keith Moore" =
<moore@cs.utk.edu>; <dcrocker@brandenburg.com>; <paf@cisco.com>; =
<ietf-imaa@imc.org>; <idn@ops.ietf.org>; <ietf-822@imc.org>; =
<ietf@ietf.org>; <ietf-pop3ext@imc.org>; <lemonade@ietf.org>; =
<discuss@apps.ietf.org>; "IMAP Extensions WG" <ietf-imapext@imc.org>; =
<ietf-smtp@imc.org>; <presnick@qualcomm.com>; <hardie@qualcomm.com>; =
<ned.freed@mrochek.com>
Sent: Tue, 2003 Oct 28 00:50
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses =
(IEA)


> On Mon, Oct 27, 2003 at 05:39:32PM -0800,
>  Mark Davis <mark.davis@jtcsv.com> wrote=20
>  a message of 76 lines which said:
>=20
> > We should remember that for a great many people in the world, Latin =
letters are
> > quite unnatural; it'd be a bit like if we had to use Greek letters =
in all email
> > addresses.=20
>=20
> It would be a bit like if we had to use Greek letters in mathematics
> :-)
>=20
> 
------=_NextPart_000_0068_01C39D20.5EDF9090
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.2800.1264" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3D"Times New Roman">Sigh. I used "Greek" in an analogy =
because I=20
was hoping that some of the Latin-only folks out there would at least=20
recognize&nbsp;the name of one&nbsp;other script. But how comforable =
would you=20
really be, if =D9=8A=D9=8F=D9=8F =D9=88=D9=90=D8=B1=D9=90 =
=D9=81=D9=8F=D8=B1=D8=B3=D9=90=D8=AF =D8=AA=D9=8F =
=D8=B1=D9=8E=D9=90=D8=AF =D9=8E=D9=86 =
=D9=90=D9=86=D8=AA=D9=90=D8=B1=D9=90=D9=84=D9=8A =
=D8=AF=D9=90=D9=81=D9=81=D9=90=D8=B1=D9=90=D9=86=D8=AA =
=D8=B3=D9=83=D8=B1=D9=90=D9=BE=D8=AA=D8=8C =
=D8=B3=D9=90=D9=85=D9=BE=D9=84=D9=8A =D8=AA=D9=8F=20
=D9=8F=D9=86=D8=AF=D9=90=D8=B1=D8=B3=D8=AA=D9=8E=D9=86=D8=AF =
=D9=90=D9=85=D9=8E=D9=90=D9=84 =
=D9=8E=D8=AF=D8=AF=D8=B1=D9=90=D8=B3=D8=B3=D9=90=D8=B3=D8=8C =
=D9=8E=D9=86=D8=AF =D9=8E =D8=B3=D9=83=D8=B1=D9=90=D9=BE=D8=AA =
=D8=AA=D9=87=D9=8E=D8=AA =D9=83=D9=8F=D9=8F=D9=84=D8=AF =
=D9=8F=D9=86=D9=84=D9=8A =
=D9=BE=D9=8E=D8=B1=D8=AA=D9=8E=D9=90=D9=84=D9=84=D9=8A =
=D8=B1=D9=90=D9=81=D9=84=D9=90=D9=83=D8=AA =D8=AA=D9=87=D9=90=20
=D8=B1=D9=8E=D9=90=D9=84 =
=D8=B3=D9=BE=D9=90=D9=84=D9=84=D9=90=D9=86=DA=AF =D9=8F=D9=81 =
=D9=8A=D9=8F=D9=8F=D8=B1 =D9=88=D9=8F=D8=B1=D8=AF=D8=B3?</FONT></DIV>
<DIV><BR><FONT=20
size=3D2>Mark<BR>__________________________________<BR><BR>&nbsp;</FONT><=
/DIV>
<DIV><FONT size=3D2>----- Original Message ----- </FONT>
<DIV><FONT size=3D2>From: "Stephane Bortzmeyer" &lt;</FONT><A=20
href=3D"mailto:bortzmeyer@nic.fr"><FONT =
size=3D2>bortzmeyer@nic.fr</FONT></A><FONT=20
size=3D2>&gt;</FONT></DIV>
<DIV><FONT size=3D2>To: "Mark Davis" &lt;</FONT><A=20
href=3D"mailto:mark.davis@jtcsv.com"><FONT=20
size=3D2>mark.davis@jtcsv.com</FONT></A><FONT size=3D2>&gt;</FONT></DIV>
<DIV><FONT size=3D2>Cc: "Mark Crispin" &lt;</FONT><A=20
href=3D"mailto:MRC@CAC.Washington.EDU"><FONT=20
size=3D2>MRC@CAC.Washington.EDU</FONT></A><FONT size=3D2>&gt;; "Keith =
Moore"=20
&lt;</FONT><A href=3D"mailto:moore@cs.utk.edu"><FONT=20
size=3D2>moore@cs.utk.edu</FONT></A><FONT size=3D2>&gt;; &lt;</FONT><A=20
href=3D"mailto:dcrocker@brandenburg.com"><FONT=20
size=3D2>dcrocker@brandenburg.com</FONT></A><FONT size=3D2>&gt;; =
&lt;</FONT><A=20
href=3D"mailto:paf@cisco.com"><FONT =
size=3D2>paf@cisco.com</FONT></A><FONT=20
size=3D2>&gt;; &lt;</FONT><A href=3D"mailto:ietf-imaa@imc.org"><FONT=20
size=3D2>ietf-imaa@imc.org</FONT></A><FONT size=3D2>&gt;; &lt;</FONT><A=20
href=3D"mailto:idn@ops.ietf.org"><FONT =
size=3D2>idn@ops.ietf.org</FONT></A><FONT=20
size=3D2>&gt;; &lt;</FONT><A href=3D"mailto:ietf-822@imc.org"><FONT=20
size=3D2>ietf-822@imc.org</FONT></A><FONT size=3D2>&gt;; &lt;</FONT><A=20
href=3D"mailto:ietf@ietf.org"><FONT =
size=3D2>ietf@ietf.org</FONT></A><FONT=20
size=3D2>&gt;; &lt;</FONT><A href=3D"mailto:ietf-pop3ext@imc.org"><FONT=20
size=3D2>ietf-pop3ext@imc.org</FONT></A><FONT size=3D2>&gt;; =
&lt;</FONT><A=20
href=3D"mailto:lemonade@ietf.org"><FONT =
size=3D2>lemonade@ietf.org</FONT></A><FONT=20
size=3D2>&gt;; &lt;</FONT><A href=3D"mailto:discuss@apps.ietf.org"><FONT =

size=3D2>discuss@apps.ietf.org</FONT></A><FONT size=3D2>&gt;; "IMAP =
Extensions WG"=20
&lt;</FONT><A href=3D"mailto:ietf-imapext@imc.org"><FONT=20
size=3D2>ietf-imapext@imc.org</FONT></A><FONT size=3D2>&gt;; =
&lt;</FONT><A=20
href=3D"mailto:ietf-smtp@imc.org"><FONT =
size=3D2>ietf-smtp@imc.org</FONT></A><FONT=20
size=3D2>&gt;; &lt;</FONT><A href=3D"mailto:presnick@qualcomm.com"><FONT =

size=3D2>presnick@qualcomm.com</FONT></A><FONT size=3D2>&gt;; =
&lt;</FONT><A=20
href=3D"mailto:hardie@qualcomm.com"><FONT=20
size=3D2>hardie@qualcomm.com</FONT></A><FONT size=3D2>&gt;; =
&lt;</FONT><A=20
href=3D"mailto:ned.freed@mrochek.com"><FONT=20
size=3D2>ned.freed@mrochek.com</FONT></A><FONT =
size=3D2>&gt;</FONT></DIV>
<DIV><FONT size=3D2>Sent: Tue, 2003 Oct 28 00:50</FONT></DIV>
<DIV><FONT size=3D2>Subject: Re: [idn] Re: FYI: BOF on Internationalized =
Email=20
Addresses (IEA)</FONT></DIV></DIV>
<DIV><FONT size=3D2><BR></FONT></DIV><FONT size=3D2>&gt; On Mon, Oct 27, =
2003 at=20
05:39:32PM -0800,<BR>&gt; &nbsp;Mark Davis &lt;</FONT><A=20
href=3D"mailto:mark.davis@jtcsv.com"><FONT=20
size=3D2>mark.davis@jtcsv.com</FONT></A><FONT size=3D2>&gt; wrote =
<BR>&gt; &nbsp;a=20
message of 76 lines which said:<BR>&gt; <BR>&gt; &gt; We should remember =
that=20
for a great many people in the world, Latin letters are<BR>&gt; &gt; =
quite=20
unnatural; it'd be a bit like if we had to use Greek letters in all=20
email<BR>&gt; &gt; addresses. <BR>&gt; <BR>&gt; It would be a bit like =
if we had=20
to use Greek letters in mathematics<BR>&gt; :-)<BR>&gt; <BR>&gt;=20
</FONT></BODY></HTML>

------=_NextPart_000_0068_01C39D20.5EDF9090--






From owner-ietf@ietf.org  Wed Oct 29 09:08:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08227
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 09:08:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEqnu-00075b-IC
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 08:56:06 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEVUu-00037P-3O
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 10:11:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28194
	for <ietf@ietf.org>; Tue, 28 Oct 2003 10:10:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEVUs-0005F8-00
	for ietf@ietf.org; Tue, 28 Oct 2003 10:11:02 -0500
Received: from w1309.hostcentric.net ([66.40.78.254])
	by ietf-mx with smtp (Exim 4.12)
	id 1AEVUr-0005F2-00
	for ietf@ietf.org; Tue, 28 Oct 2003 10:11:02 -0500
Received: (qmail 31822 invoked by alias); 28 Oct 2003 15:10:59 -0000
Received: from unknown (HELO DAVIS1) (12.235.201.242)
  by 0 with SMTP; 28 Oct 2003 15:10:59 -0000
Message-ID: <00a001c39d65$b23177f0$7900a8c0@DAVIS1>
From: "Mark Davis" <mark.davis@jtcsv.com>
To: "Mark Crispin" <MRC@CAC.Washington.EDU>, "Abhijit Menon-Sen" <ams@wiw.org>
Cc: <ietf-imaa@imc.org>, <idn@ops.ietf.org>, <ietf-822@imc.org>,
        <ietf@ietf.org>, <ietf-pop3ext@imc.org>, <lemonade@ietf.org>,
        <discuss@apps.ietf.org>, <ietf-imapext@imc.org>, <ietf-smtp@imc.org>
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU> <20031028095243.A1525@lustre.dyn.wiw.org> <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Tue, 28 Oct 2003 07:10:59 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > (I agree that it's currently nearly impossible to use computers if one
> > isn't familiar with the Latin script, of course.)
>
> Which probably makes the rest of this discussion academic, unless we're
> going to undertake solving *that* problem for Microsoft and the various
> UNIX/Linux vendors...

It is currently impossible to use the Internet without knowing the Latin script.
However, the goal of most well-designed client software and operating systems is
to permit the user to work entirely within their native language, with a fully
localized system. This is reaching to India and other countries; Microsoft has
introduced fully localized versions of Indic Windows just recently, and Linux
vendors are hard at work to produce fully localized versions of their software.

Email and Web addresses are the big remaining holdouts for most people. People
should not be forced to use a script that they are unfamiliar with, just to use
email addresses and sites in their own countries. Even if they are familiar with
the Latin script, it is very often a very bad match for their languages, making
it very difficult to figure out how native words would be spelled in it.

Mark






From owner-ietf@ietf.org  Wed Oct 29 09:09:16 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08327
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 09:09:16 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEqnu-00075h-MX
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 08:56:06 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEWcG-00036F-3P
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 11:22:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04908
	for <ietf@ietf.org>; Tue, 28 Oct 2003 11:22:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEWcE-0007dr-00
	for ietf@ietf.org; Tue, 28 Oct 2003 11:22:42 -0500
Received: from w1309.hostcentric.net ([66.40.78.254])
	by ietf-mx with smtp (Exim 4.12)
	id 1AEWcD-0007dj-00
	for ietf@ietf.org; Tue, 28 Oct 2003 11:22:41 -0500
Received: (qmail 2789 invoked by alias); 28 Oct 2003 16:22:38 -0000
Received: from unknown (HELO DAVIS1) (12.235.201.242)
  by 0 with SMTP; 28 Oct 2003 16:22:38 -0000
Message-ID: <00fb01c39d6f$b46cdd70$7900a8c0@DAVIS1>
From: "Mark Davis" <mark.davis@jtcsv.com>
To: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>,
        "Mark Crispin" <MRC@CAC.Washington.EDU>,
        "Abhijit Menon-Sen" <ams@wiw.org>
Cc: <ietf-imaa@imc.org>, <idn@ops.ietf.org>, <ietf-822@imc.org>,
        <ietf@ietf.org>, <ietf-pop3ext@imc.org>, <lemonade@ietf.org>,
        <discuss@apps.ietf.org>, <ietf-imapext@imc.org>, <ietf-smtp@imc.org>
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU> <20031028095243.A1525@lustre.dyn.wiw.org> <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU> <00a001c39d65$b23177f0$7900a8c0@DAVIS1> <280960000.1067357574@classic.viagenie.qc.ca>
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Tue, 28 Oct 2003 08:22:37 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA04910
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

I wouldn't have thought so either, but at least some people questioned th=
e need
for non-Latin characters, and went so far as to exclude them from a propo=
sed
problem statement:

> ... There is a growing need to use additional
> characters, specifically Latin characters with diacriticals and non-Lat=
in
> characters, in email addresses to better serve the needs of the
> multi-national Internet community...

Mark
__________________________________
http://www.macchiato.com
=E2=96=BA =E0=A4=B6=E0=A4=BF=E0=A4=B7=E0=A5=8D=E0=A4=AF=E0=A4=BE=E0=A4=A6=
=E0=A4=BF=E0=A4=9A=E0=A5=8D=E0=A4=9B=E0=A5=87=E0=A4=A4=E0=A5=8D=E0=A4=AA=E0=
=A4=B0=E0=A4=BE=E0=A4=9C=E0=A4=AF=E0=A4=AE=E0=A5=8D =E2=97=84

----- Original Message -----=20
From: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
To: "Mark Davis" <mark.davis@jtcsv.com>; "Mark Crispin"
<MRC@CAC.Washington.EDU>; "Abhijit Menon-Sen" <ams@wiw.org>
Cc: <ietf-imaa@imc.org>; <idn@ops.ietf.org>; <ietf-822@imc.org>;
<ietf@ietf.org>; <ietf-pop3ext@imc.org>; <lemonade@ietf.org>;
<discuss@apps.ietf.org>; <ietf-imapext@imc.org>; <ietf-smtp@imc.org>
Sent: Tue, 2003 Oct 28 08:12
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA=
)


>
> it appears to me that this thread is not very different from the idn
> considerations on usage of idn in the world. So what is really new in t=
his
> discussion?
>
> Marc.
>
> -- Tuesday, October 28, 2003 07:10:59 -0800 Mark Davis
> <mark.davis@jtcsv.com> wrote/a ecrit:
>
> >> > (I agree that it's currently nearly impossible to use computers if=
 one
> >> > isn't familiar with the Latin script, of course.)
> >>
> >> Which probably makes the rest of this discussion academic, unless we=
're
> >> going to undertake solving *that* problem for Microsoft and the vari=
ous
> >> UNIX/Linux vendors...
> >
> > It is currently impossible to use the Internet without knowing the La=
tin
> > script. However, the goal of most well-designed client software and
> > operating systems is to permit the user to work entirely within their
> > native language, with a fully localized system. This is reaching to I=
ndia
> > and other countries; Microsoft has introduced fully localized version=
s of
> > Indic Windows just recently, and Linux vendors are hard at work to
> > produce fully localized versions of their software.
> >
> > Email and Web addresses are the big remaining holdouts for most peopl=
e.
> > People should not be forced to use a script that they are unfamiliar
> > with, just to use email addresses and sites in their own countries. E=
ven
> > if they are familiar with the Latin script, it is very often a very b=
ad
> > match for their languages, making it very difficult to figure out how
> > native words would be spelled in it.
> >
> > Mark
> >
>
>
>
> ------------------------------------------
> Marc Blanchet
> Hexago
> tel: +1-418-266-5533x225
> ------------------------------------------
> http://www.freenet6.net: IPv6 connectivity
> ------------------------------------------
>






From owner-ietf@ietf.org  Wed Oct 29 09:19:14 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08781
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 09:19:14 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEqnv-00075r-2j
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 08:56:07 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEqbE-0006r2-3d
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 08:43:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07020
	for <ietf@ietf.org>; Wed, 29 Oct 2003 08:42:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEqbD-0000lX-00
	for ietf@ietf.org; Wed, 29 Oct 2003 08:42:59 -0500
Received: from h-135-207-24-32.research.att.com ([135.207.24.32] helo=mailman.research.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEqbD-0000kt-00
	for ietf@ietf.org; Wed, 29 Oct 2003 08:42:59 -0500
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mailman.research.att.com (8.12.8/8.12.8) with ESMTP id h9TDbMLZ012245;
	Wed, 29 Oct 2003 08:37:22 -0500
Received: from berkshire.research.att.com (guard.research.att.com [135.207.1.20])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h9TDgOZ20830;
	Wed, 29 Oct 2003 08:42:24 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id 6AF7B7B43; Wed, 29 Oct 2003 08:42:23 -0500 (EST)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: itojun@iijlab.net
Cc: ietf@ietf.org
Subject: Re: mailman switchover: password unknown 
In-Reply-To: Your message of "Wed, 29 Oct 2003 16:07:11 +0900."
             <20031029070711.2262613@coconut.itojun.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 29 Oct 2003 08:42:23 -0500
Message-Id: <20031029134223.6AF7B7B43@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <20031029070711.2262613@coconut.itojun.org>, itojun@iijlab.net write
s:
>	ipv6 and other wg mailing list have switched over to mailman, which
>	is good.  however, i don't remember being informed of password to
>	be used to control my mailman settings.  am i missing something?

In general, mailman will email you your password if you click the right 
button.  It's not as obvious as it should be -- in this case, enter 
your email address in the "Edit Options" box at the bottom of the page; 
the next page will have a forgotten password button.


		--Steve Bellovin, http://www.research.att.com/~smb





From owner-ietf@ietf.org  Wed Oct 29 10:07:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10730
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 10:07:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AErcg-0001w5-Oj
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 09:48:34 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AErVm-0001nM-3t
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 09:41:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09516;
	Wed, 29 Oct 2003 09:41:15 -0500 (EST)
From: Margaret.Wasserman@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AErVl-0001mb-00; Wed, 29 Oct 2003 09:41:25 -0500
Received: from [206.157.230.254] (helo=hatl0ms22.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AErVk-0001mH-00; Wed, 29 Oct 2003 09:41:24 -0500
Received: from CATL0MS82.corp.cox.com ([10.62.200.232]) by hatl0ms22.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 09:40:54 -0500
Received: from mail pickup service by CATL0MS82.corp.cox.com with Microsoft SMTPSVC;
	 Wed, 29 Oct 2003 09:14:48 -0500
Received: from hatl0ms23.corp.cox.com ([10.64.200.56]) by catl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 15:49:23 -0500
Received: from bastion2.cox.com ([10.225.2.51]) by hatl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 15:35:41 -0500
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion2.cox.com (8.11.7p1+Sun/8.11.6) with SMTP id h9SKZbv10724;
	Tue, 28 Oct 2003 15:35:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEZle-0004TG-2K
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 14:44:38 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEX6y-0000ni-Ga
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 11:54:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07634;
	Tue, 28 Oct 2003 11:54:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEX6x-0000xX-00; Tue, 28 Oct 2003 11:54:27 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEX6w-0000xK-00; Tue, 28 Oct 2003 11:54:26 -0500
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9SGsPI05937;
	Tue, 28 Oct 2003 18:54:25 +0200 (EET)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T659074b434ac158f21083@esvir01nok.ntc.nokia.com>;
 Tue, 28 Oct 2003 18:54:24 +0200
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 28 Oct 2003 10:54:22 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Tue, 28 Oct 2003 11:54:21 -0500
Message-ID: <E320A8529CF07E4C967ECC2F380B0CF902443EA6@bsebe001.americas.nokia.com>
Thread-Topic: FYI: BOF on Internationalized Email Addresses (IEA)
Thread-Index: AcOdY3TL2xxUnJupRI2uu4njYAvuPgAD/9pQ
To: <idn@ops.ietf.org>, <ietf-822@imc.org>, <ietf@ietf.org>,
        <ietf-pop3ext@imc.org>, <lemonade@ietf.org>, <discuss@apps.ietf.org>,
        <ietf-imapext@imc.org>, <ietf-smtp@imc.org>, <ietf-imaa@imc.org>
X-OriginalArrivalTime: 28 Oct 2003 16:54:22.0543 (UTC) FILETIME=[22FF4DF0:01C39D74]
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


Excuse me, but could you please constrain this
conversation to fewer than 9 (nine!) e-mail lists?

The BOF description lists imaa@imc.org as the
discussion list, but this discussion is being
cc:ed to ietf-imaa@imc.org.  I'd suggest that you
move this discussion to whichever of those lists
is actually correct.

Margaret





From owner-ietf@ietf.org  Wed Oct 29 10:25:01 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13178
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 10:25:00 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEs3K-0002zK-U8
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 10:16:06 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AErzU-0007XC-Lv
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 10:12:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11697
	for <ietf@ietf.org>; Wed, 29 Oct 2003 10:11:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AErzT-0002Jw-00
	for ietf@ietf.org; Wed, 29 Oct 2003 10:12:07 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AErzT-0002JL-00
	for ietf@ietf.org; Wed, 29 Oct 2003 10:12:07 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9TFHdf06477;
	Wed, 29 Oct 2003 07:17:39 -0800
Date: Wed, 29 Oct 2003 07:11:30 -0800
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v2.00.22)
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <11354281242.20031029071130@brandenburg.com>
To: "Mark Davis" <mark.davis@jtcsv.com>
CC: ietf-imaa@imc.org, ietf@ietf.org
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <01eb01c39e2d$a852c720$92d2399d@DAVIS1>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 <12228881609.20031027074111@brandenburg.com>
 <20031027105222.4eae54fd.moore@cs.utk.edu>
 <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
 <355752681.20031027161925@brandenburg.com> <1694652.1067364195@localhost>
 <1957796741.20031028181646@brandenburg.com>
 <01eb01c39e2d$a852c720$92d2399d@DAVIS1>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Mark,

>>   (Another
>> jibe, citing the fact that utf-8 is, itself, a modification to "raw" unicode
>> is probably worth repeating, here.)
MD> When Unicode is expressed as a series of bytes, there are a number of equally
MD> valid sncoding schemes (aka serializations). UTF-8 is one of those schemes, and
MD> is no more or less a "modification", and no more or less "Unicode" than any
MD> other of these schemes.


That's right.  It is an "encoding".  Raw Unicode takes more than 8-bits.  Lots
more.  UTF-8 is a method of encoding those raw bits into a non-raw form.

So is the ACE approach.

My point was that folks tend to talk about UTF-8 as if it were the raw
representation, rather than a derivative encoding.  In fact, UTF-8 is exactly
parallel to the ACE approach.

It might be a more efficient encoding, but it is no more "native" or "direct"
or "raw" than ACE.


d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Wed Oct 29 11:10:03 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16145
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 11:10:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEsjR-0005Jn-C8
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 10:59:37 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEsY8-0004nN-B7
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 10:47:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14896
	for <ietf@ietf.org>; Wed, 29 Oct 2003 10:47:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEsY7-0003MB-00
	for ietf@ietf.org; Wed, 29 Oct 2003 10:47:55 -0500
Received: from [206.157.230.254] (helo=hatl0ms20.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEsY7-0003LM-00
	for ietf@ietf.org; Wed, 29 Oct 2003 10:47:55 -0500
Received: from catl0ms23.corp.cox.com ([10.64.200.46]) by hatl0ms20.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 10:47:24 -0500
Received: from mail pickup service by catl0ms23.corp.cox.com with Microsoft SMTPSVC;
	 Wed, 29 Oct 2003 10:35:44 -0500
Received: from hatl0ms23.corp.cox.com ([10.64.200.56]) by catl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 23:28:39 -0500
Received: from bastion2.cox.com ([10.225.2.51]) by hatl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 28 Oct 2003 23:28:36 -0500
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion2.cox.com (8.11.7p1+Sun/8.11.6) with SMTP id h9T4SYo16665;
	Tue, 28 Oct 2003 23:28:35 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEhe7-0002j8-RX
	for ietf-list@asgard.ietf.org; Tue, 28 Oct 2003 23:09:23 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEhId-0001HA-Ki
	for ietf@asgard.ietf.org; Tue, 28 Oct 2003 22:47:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21602
	for <ietf@ietf.org>; Tue, 28 Oct 2003 22:47:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEhIb-0000FI-00
	for ietf@ietf.org; Tue, 28 Oct 2003 22:47:09 -0500
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEhIa-0000EW-00
	for ietf@ietf.org; Tue, 28 Oct 2003 22:47:09 -0500
Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57])
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id h9T3Om102527;
	Tue, 28 Oct 2003 22:24:49 -0500
From: "bill" <bill@strahm.net>
To: "'todd glassey'" <todd.glassey@worldnet.att.net>
Cc: <ietf@ietf.org>
Subject: RE: Proposed statement quotes wrong numbers
Date: Tue, 28 Oct 2003 19:46:29 -0800
Message-ID: <000401c39dcf$3cf02cb0$1c02a8c0@mobilebill>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <031a01c39db9$65a9c000$010aff0a@bolaba>
Importance: Normal
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Oct 2003 04:28:36.0493 (UTC) FILETIME=[1EAFABD0:01C39DD5]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I disagree with your analysis todd.

The strength of the IETF is not in the number of unique e-mail address
on its e-mail lists (define unique - I have subscribed from probably 10
e-mail addresses over the years - many people I know are subscribed with
multiple "unique" addresses - many address in reality point to archiving
services, other reflectors, peoples inboxes that don't look at the
e-mail

So I don't think you can even count the number of unique e-mail
addresses - but if you could -

Peoples technical content/quality very widely, some input is worthless
(or close to it) and many just monitor what is going on... Other e-mail
is critical - either in technical content, providing an alternative
viewpoint etc.

The strength of the IETF is that it is a gathering point for all of
these people.  Not a quantity of e-mail addresses that can be spammed or
something else

Bill

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of todd
glassey
Sent: Tuesday, October 28, 2003 5:09 PM
To: Bruce Campbell
Cc: Harald Tveit Alvestrand; Christian Huitema; ietf@ietf.org;
problem-statement@alvestrand.no
Subject: Re: Proposed statement quotes wrong numbers


Bruce -
----- Original Message ----- 
From: "Bruce Campbell" <bruce.campbell@ripe.net>
To: "todd glassey" <todd.glassey@worldnet.att.net>
Cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>; "Christian
Huitema" <huitema@windows.microsoft.com>; <ietf@ietf.org>;
<problem-statement@alvestrand.no>
Sent: Tuesday, October 28, 2003 1:59 AM
Subject: Re: Proposed statement quotes wrong numbers


> On Mon, 27 Oct 2003, todd glassey wrote:
>
> > What was the attendance of the last meeting then? and also what then

> > is
the
> > sum total of unique EMail Addresses in the Lists then too? I.e. what

> > is
the
> > total size of the Vetting Community Resource that the IETF brings to

> > the Party as an enterprise/org???
>
> Are you sure that you can count the (large) number of subscribers that

> are on the main IETF lists, and the umpteen WG lists, as participants?

participants as far as meetings are concerned? no - obviously not, but
this pool of good email addresses constitute the core value of the IETF,
that being its Vettig Pool. So yes indeed, and also remember that the
IETF is a voluntary particpation standards process and platform, and
that the reliable email addresses for this "Vetting Pool" is what the
core of the IETF's ideas are vetted against. So put on your
"organizational leader's" hat and then ask me the same question -

> There
> seem to be a lot of people who are subscribed to various IETF-related 
> lists who do not seem to participate in the IETF discussions.

But the point is that they have the option. Its their choice as to
whether to participate of not.

>
> ( But theres still a lot more than just 700 people who participate in
the
>   IETF )

I agree - so lets ask the question again, how many unique names are
there in the lists - what's the total 'verified email addresses' that
make up the total of the vetting pool? - 5000 - 10000 - 50000? what is
it? Harald? - this seems like a number that you as the Chair of the IETF
would not only be proud of, but would also have on the top of your head
on a monthly basis... Any ideas as to the number?

Todd


>
> --==--
> Bruce.






From owner-ietf@ietf.org  Wed Oct 29 11:43:31 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18151
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 11:43:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEtH4-0007Et-V0
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 11:34:22 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEt9n-00071J-5W
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 11:26:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17284
	for <ietf@ietf.org>; Wed, 29 Oct 2003 11:26:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEt9j-0004Jh-00
	for ietf@ietf.org; Wed, 29 Oct 2003 11:26:47 -0500
Received: from sausage.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEt9h-0004HG-00
	for ietf@ietf.org; Wed, 29 Oct 2003 11:26:45 -0500
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by manatick with esmtp (Exim 4.24)
	id 1AEsvp-00012D-Nw
	for ietf@ietf.org; Wed, 29 Oct 2003 11:12:25 -0500
Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57])
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id h9TFo7104758;
	Wed, 29 Oct 2003 10:50:07 -0500
From: "bill" <bill@strahm.net>
To: "'todd glassey'" <todd.glassey@worldnet.att.net>
Cc: <ietf@ietf.org>
Subject: RE: Proposed statement quotes wrong numbers
Date: Wed, 29 Oct 2003 08:11:47 -0800
Message-ID: <002301c39e37$5b6e21c0$1c02a8c0@mobilebill>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
In-Reply-To: <042701c39dea$14749a80$010aff0a@bolaba>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I would agree in as much as the metric for the productivity of a
programmer is KLOC.

I don't think you could define a unique e-mail in any sense of the word
- and even then, know the quality of the technical opinion behind that
e-mail address.

Bill

-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of todd
glassey
Sent: Tuesday, October 28, 2003 9:57 PM
To: bill
Cc: ietf@ietf.org
Subject: Re: Proposed statement quotes wrong numbers


Bill - you are missing the picture. The ultimate number of bodies that
the IETF can count on are those unique email addresses. No one said they
were any particular Vetting Initiative but rather the total possible
number of "representative opinions" that any consensus could possibly
count on - assuming an "across the Organizational breadth" as the
metric.

The IETF is supposed to be representative of the people of the world and
their representatives to the task of building Internet protocols, right?
So then the unique email addresses are a direct metric on how well the
world is represented. Wouldn't you say?

Todd


----- Original Message ----- 
From: "bill" <bill@strahm.net>
To: "'todd glassey'" <todd.glassey@worldnet.att.net>
Cc: <ietf@ietf.org>
Sent: Tuesday, October 28, 2003 7:46 PM
Subject: RE: Proposed statement quotes wrong numbers


> I disagree with your analysis todd.
>
> The strength of the IETF is not in the number of unique e-mail address

> on its e-mail lists (define unique - I have subscribed from probably 
> 10 e-mail addresses over the years - many people I know are subscribed

> with multiple "unique" addresses - many address in reality point to 
> archiving services, other reflectors, peoples inboxes that don't look 
> at the e-mail

Thats a problem with the Registration Process then.

>
> So I don't think you can even count the number of unique e-mail 
> addresses - but if you could -
>
> Peoples technical content/quality very widely, some input is worthless

> (or close to it) and many just monitor what is going on... Other 
> e-mail is critical - either in technical content, providing an 
> alternative viewpoint etc.

What has that to do with how many possible opinions are available
herein?

>
> The strength of the IETF is that it is a gathering point for all of 
> these people.

You mean the mailing lists right? - so count the members...

>  Not a quantity of e-mail addresses that can be spammed or something 
> else

Bill -  you have not discounted or invalidated anything I have said
here. My comment stands.

>
> Bill
>
> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of 
> todd glassey
> Sent: Tuesday, October 28, 2003 5:09 PM
> To: Bruce Campbell
> Cc: Harald Tveit Alvestrand; Christian Huitema; ietf@ietf.org; 
> problem-statement@alvestrand.no
> Subject: Re: Proposed statement quotes wrong numbers
>
>
> Bruce -
> ----- Original Message -----
> From: "Bruce Campbell" <bruce.campbell@ripe.net>
> To: "todd glassey" <todd.glassey@worldnet.att.net>
> Cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>; "Christian
> Huitema" <huitema@windows.microsoft.com>; <ietf@ietf.org>;
> <problem-statement@alvestrand.no>
> Sent: Tuesday, October 28, 2003 1:59 AM
> Subject: Re: Proposed statement quotes wrong numbers
>
>
> > On Mon, 27 Oct 2003, todd glassey wrote:
> >
> > > What was the attendance of the last meeting then? and also what 
> > > then
>
> > > is
> the
> > > sum total of unique EMail Addresses in the Lists then too? I.e. 
> > > what
>
> > > is
> the
> > > total size of the Vetting Community Resource that the IETF brings 
> > > to
>
> > > the Party as an enterprise/org???
> >
> > Are you sure that you can count the (large) number of subscribers 
> > that
>
> > are on the main IETF lists, and the umpteen WG lists, as 
> > participants?
>
> participants as far as meetings are concerned? no - obviously not, but

> this pool of good email addresses constitute the core value of the 
> IETF, that being its Vettig Pool. So yes indeed, and also remember 
> that the IETF is a voluntary particpation standards process and 
> platform, and that the reliable email addresses for this "Vetting 
> Pool" is what the core of the IETF's ideas are vetted against. So put 
> on your "organizational leader's" hat and then ask me the same 
> question -
>
> > There
> > seem to be a lot of people who are subscribed to various 
> > IETF-related lists who do not seem to participate in the IETF 
> > discussions.
>
> But the point is that they have the option. Its their choice as to 
> whether to participate of not.
>
> >
> > ( But theres still a lot more than just 700 people who participate 
> > in
> the
> >   IETF )
>
> I agree - so lets ask the question again, how many unique names are 
> there in the lists - what's the total 'verified email addresses' that 
> make up the total of the vetting pool? - 5000 - 10000 - 50000? what is

> it? Harald? - this seems like a number that you as the Chair of the 
> IETF would not only be proud of, but would also have on the top of 
> your head on a monthly basis... Any ideas as to the number?
>
> Todd
>
>
> >
> > --==--
> > Bruce.
>
>





From owner-ietf@ietf.org  Wed Oct 29 12:13:11 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19720
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 12:13:11 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEtYL-00083I-0v
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 11:52:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEtRj-0007ia-Su
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 11:45:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18297;
	Wed, 29 Oct 2003 11:45:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEtRi-0004gf-00; Wed, 29 Oct 2003 11:45:22 -0500
Received: from relay-6m.club-internet.fr ([194.158.104.45])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEtRi-0004gU-00; Wed, 29 Oct 2003 11:45:22 -0500
Received: from jfc2.club-internet.fr (f02v-21-20.d0.club-internet.fr [212.195.240.20])
	by relay-6m.club-internet.fr (Postfix) with ESMTP
	id A66FC2567A; Wed, 29 Oct 2003 17:45:14 +0100 (CET)
Message-Id: <6.0.0.22.2.20031029163607.04355ba0@mail.club-internet.fr>
X-Sender: jefsey@mail.club-internet.fr
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Wed, 29 Oct 2003 16:50:39 +0100
To: Zefram <zefram@fysh.org>
From: "J-F C. (Jefsey)  Morfin" <jefsey@club-internet.fr>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Cc: Dave Crocker <dcrocker@brandenburg.com>, ietf-imaa@imc.org,
        idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        ietf-imapext@imc.org, ietf-smtp@imc.org
In-Reply-To: <20031028093114.GC20198@fysh.org>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 <12228881609.20031027074111@brandenburg.com>
 <20031027105222.4eae54fd.moore@cs.utk.edu>
 <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
 <355752681.20031027161925@brandenburg.com>
 <20031028093114.GC20198@fysh.org>
Mime-Version: 1.0
Content-Type: text/plain; x-avg-checked=avg-ok-6A73736C; charset=us-ascii; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

On 10:31 28/10/03, Zefram said:
>I think the first task in this area should be to investigate the nature 
>and degree of desire for non-ASCII local parts.  This desire needs to be 
>weighed against the benefits we derive from writing all local parts in a 
>small, fixed alphabet (ASCII printables).

May I ask which part of the world you come from?

This being said only Americans want/are satisfied with "internationalized" 
(sic) names (the artificial extension of the American character set with 
most of the American foreign scripting, within an ascii frame). No one 
really wants multilingual names (a totally internationalized (sic) frame 
supporting languages and therefore some language oriented rules - at least 
ni management and user support). The users need vernacular support, that is 
to be able to freely do in the mail what they use to do elsewhere.

I note that for non-American writers "international names" means names that 
everyone from every nation will understand. It happens to be the ascii 
character set limited to the DNS used names (they were selected for that 
reason).
jfc






From owner-ietf@ietf.org  Wed Oct 29 12:13:12 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19736
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 12:13:12 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEtYK-000824-Da
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 11:52:12 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEtQt-0007ci-29
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 11:44:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18230
	for <ietf@ietf.org>; Wed, 29 Oct 2003 11:44:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEtQs-0004dj-00
	for ietf@ietf.org; Wed, 29 Oct 2003 11:44:30 -0500
Received: from [206.157.230.254] (helo=hatl0ms22.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEtQr-0004d0-00
	for ietf@ietf.org; Wed, 29 Oct 2003 11:44:29 -0500
Received: from catl0ms22.corp.cox.com ([10.62.200.101]) by hatl0ms22.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 11:43:59 -0500
Received: from mail pickup service by catl0ms22.corp.cox.com with Microsoft SMTPSVC;
	 Wed, 29 Oct 2003 11:43:02 -0500
Received: from hatl0ms23.corp.cox.com ([10.64.200.56]) by catl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 02:22:33 -0500
Received: from bastion2.cox.com ([10.225.2.51]) by hatl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 02:22:32 -0500
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion2.cox.com (8.11.7p1+Sun/8.11.6) with SMTP id h9T7MVo18508;
	Wed, 29 Oct 2003 02:22:31 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEkSm-0002tj-LP
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 02:09:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEkMj-0000e2-Gz
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 02:03:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01892
	for <ietf@ietf.org>; Wed, 29 Oct 2003 02:03:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEkMh-0002qg-00
	for ietf@ietf.org; Wed, 29 Oct 2003 02:03:35 -0500
Received: from mtiwmhc11.worldnet.att.net ([204.127.131.115])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEkMg-0002qK-00
	for ietf@ietf.org; Wed, 29 Oct 2003 02:03:34 -0500
Received: from bolaba (209.sanjose-03-04rs16rt.ca.dial-access.att.net[12.81.1.209])
          by worldnet.att.net (mtiwmhc11) with SMTP
          id <2003102907030211100l6sv3e>; Wed, 29 Oct 2003 07:03:03 +0000
Message-ID: <042701c39dea$14749a80$010aff0a@bolaba>
From: "todd glassey" <todd.glassey@worldnet.att.net>
To: "bill" <bill@strahm.net>
Cc: <ietf@ietf.org>
References: <000401c39dcf$3cf02cb0$1c02a8c0@mobilebill>
Subject: Re: Proposed statement quotes wrong numbers
Date: Tue, 28 Oct 2003 21:56:43 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Oct 2003 07:22:33.0056 (UTC) FILETIME=[6B5CCE00:01C39DED]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bill - you are missing the picture. The ultimate number of bodies that the
IETF can count on are those unique email addresses. No one said they were
any particular Vetting Initiative but rather the total possible number of
"representative opinions" that any consensus could possibly count on -
assuming an "across the Organizational breadth" as the metric.

The IETF is supposed to be representative of the people of the world and
their representatives to the task of building Internet protocols, right? So
then the unique email addresses are a direct metric on how well the world is
represented. Wouldn't you say?

Todd


----- Original Message ----- 
From: "bill" <bill@strahm.net>
To: "'todd glassey'" <todd.glassey@worldnet.att.net>
Cc: <ietf@ietf.org>
Sent: Tuesday, October 28, 2003 7:46 PM
Subject: RE: Proposed statement quotes wrong numbers


> I disagree with your analysis todd.
>
> The strength of the IETF is not in the number of unique e-mail address
> on its e-mail lists (define unique - I have subscribed from probably 10
> e-mail addresses over the years - many people I know are subscribed with
> multiple "unique" addresses - many address in reality point to archiving
> services, other reflectors, peoples inboxes that don't look at the
> e-mail

Thats a problem with the Registration Process then.

>
> So I don't think you can even count the number of unique e-mail
> addresses - but if you could -
>
> Peoples technical content/quality very widely, some input is worthless
> (or close to it) and many just monitor what is going on... Other e-mail
> is critical - either in technical content, providing an alternative
> viewpoint etc.

What has that to do with how many possible opinions are available herein?

>
> The strength of the IETF is that it is a gathering point for all of
> these people.

You mean the mailing lists right? - so count the members...

>  Not a quantity of e-mail addresses that can be spammed or
> something else

Bill -  you have not discounted or invalidated anything I have said here. My
comment stands.

>
> Bill
>
> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of todd
> glassey
> Sent: Tuesday, October 28, 2003 5:09 PM
> To: Bruce Campbell
> Cc: Harald Tveit Alvestrand; Christian Huitema; ietf@ietf.org;
> problem-statement@alvestrand.no
> Subject: Re: Proposed statement quotes wrong numbers
>
>
> Bruce -
> ----- Original Message ----- 
> From: "Bruce Campbell" <bruce.campbell@ripe.net>
> To: "todd glassey" <todd.glassey@worldnet.att.net>
> Cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>; "Christian
> Huitema" <huitema@windows.microsoft.com>; <ietf@ietf.org>;
> <problem-statement@alvestrand.no>
> Sent: Tuesday, October 28, 2003 1:59 AM
> Subject: Re: Proposed statement quotes wrong numbers
>
>
> > On Mon, 27 Oct 2003, todd glassey wrote:
> >
> > > What was the attendance of the last meeting then? and also what then
>
> > > is
> the
> > > sum total of unique EMail Addresses in the Lists then too? I.e. what
>
> > > is
> the
> > > total size of the Vetting Community Resource that the IETF brings to
>
> > > the Party as an enterprise/org???
> >
> > Are you sure that you can count the (large) number of subscribers that
>
> > are on the main IETF lists, and the umpteen WG lists, as participants?
>
> participants as far as meetings are concerned? no - obviously not, but
> this pool of good email addresses constitute the core value of the IETF,
> that being its Vettig Pool. So yes indeed, and also remember that the
> IETF is a voluntary particpation standards process and platform, and
> that the reliable email addresses for this "Vetting Pool" is what the
> core of the IETF's ideas are vetted against. So put on your
> "organizational leader's" hat and then ask me the same question -
>
> > There
> > seem to be a lot of people who are subscribed to various IETF-related
> > lists who do not seem to participate in the IETF discussions.
>
> But the point is that they have the option. Its their choice as to
> whether to participate of not.
>
> >
> > ( But theres still a lot more than just 700 people who participate in
> the
> >   IETF )
>
> I agree - so lets ask the question again, how many unique names are
> there in the lists - what's the total 'verified email addresses' that
> make up the total of the vetting pool? - 5000 - 10000 - 50000? what is
> it? Harald? - this seems like a number that you as the Chair of the IETF
> would not only be proud of, but would also have on the top of your head
> on a monthly basis... Any ideas as to the number?
>
> Todd
>
>
> >
> > --==--
> > Bruce.
>
>





From owner-ietf@ietf.org  Wed Oct 29 12:44:25 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22479
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 12:44:25 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEtvU-0000jY-QD
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 12:16:08 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEtuc-0000Oc-UV
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 12:15:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20085
	for <ietf@ietf.org>; Wed, 29 Oct 2003 12:15:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEtuc-0005Ow-00
	for ietf@ietf.org; Wed, 29 Oct 2003 12:15:14 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEtub-0005Mb-00
	for ietf@ietf.org; Wed, 29 Oct 2003 12:15:13 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9THKEf16610;
	Wed, 29 Oct 2003 09:20:14 -0800
Date: Wed, 29 Oct 2003 09:14:04 -0800
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v2.00.22)
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <19761635346.20031029091404@brandenburg.com>
To: John Cowan <jcowan@reutershealth.com>
CC: ietf-imaa@imc.org, ietf@ietf.org
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <20031029162739.GT8048@skunk.reutershealth.com>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com>
 <12228881609.20031027074111@brandenburg.com>
 <20031027105222.4eae54fd.moore@cs.utk.edu>
 <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu>
 <355752681.20031027161925@brandenburg.com> <1694652.1067364195@localhost>
 <1957796741.20031028181646@brandenburg.com>
 <01eb01c39e2d$a852c720$92d2399d@DAVIS1>
 <11354281242.20031029071130@brandenburg.com>
 <20031029162739.GT8048@skunk.reutershealth.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

JC> That's only true if you take the position that there are no native/direct/raw
JC> encodings of Unicode.

Oh?  You mean that Unicode does not fit directly -- ie, with no special
encoding rules -- into 32 bits, or 24 bits, or somesuch.

You mean that Unicode does not need special rules to stuff it into 8 bits, and
another set of rules to stuff it into 16 bits?

Because if the answer is that yes it does -- and the answer _is_ yes it does
-- then my point stands.

That's the difference between native representation, versus "encoding".

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Wed Oct 29 13:04:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23839
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 13:04:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEuL2-0001j4-1Q
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 12:42:32 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEu2i-00015e-VG
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 12:23:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21407
	for <ietf@ietf.org>; Wed, 29 Oct 2003 12:23:25 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEu2h-0005qy-00
	for ietf@ietf.org; Wed, 29 Oct 2003 12:23:36 -0500
Received: from h80ad2574.async.vt.edu ([128.173.37.116] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEu2g-0005qu-00
	for ietf@ietf.org; Wed, 29 Oct 2003 12:23:34 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9THNU43013564;
	Wed, 29 Oct 2003 12:23:30 -0500
Message-Id: <200310291723.h9THNU43013564@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: bill <bill@strahm.net>
Cc: "'todd glassey'" <todd.glassey@worldnet.att.net>, ietf@ietf.org
Subject: Re: Proposed statement quotes wrong numbers 
In-Reply-To: Your message of "Wed, 29 Oct 2003 08:11:47 PST."
             <002301c39e37$5b6e21c0$1c02a8c0@mobilebill> 
References: <002301c39e37$5b6e21c0$1c02a8c0@mobilebill>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1173114196P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 29 Oct 2003 12:23:30 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1173114196P
Content-Type: text/plain; charset=us-ascii

On Wed, 29 Oct 2003 08:11:47 PST, bill said:

> I don't think you could define a unique e-mail in any sense of the word
> - and even then, know the quality of the technical opinion behind that
> e-mail address.

Amen.

We have kooks with one email address, we have kooks with lots of e-mail
addresses, we have very clued people with one address, and we have very clued
people with multiple addresses.

I'm pretty sure I'm one of the four, but not sure which.  I'm not sure how many
e-mail addresses I have, and I'm not even sure what metric to use for "number
of addresses" - due to some purely internal wonkyness in the way we do
business, the number of legitimate e-mail addresses that will result in mail
being dropped in my inbox is somewhere between two and three orders of
magnitude higher than the number of addresses I'm wont to emit from (at one
time it was almost 4 orders of magnitude, but I'm much better now, thank you).

As is standard IETF culture, you get to decide on the kook/clue yourself. ;)


--==_Exmh_-1173114196P
Content-Type: application/pgp-signature

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

iD8DBQE/n/eScC3lWbTT17ARApvzAJ4rClCFUL25DjIbDCC4fOWa5EsZiwCfcdxh
zBQapuudVJGMTch1k/efU1A=
=H589
-----END PGP SIGNATURE-----

--==_Exmh_-1173114196P--



From owner-ietf@ietf.org  Wed Oct 29 13:39:45 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25561
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 13:39:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEuis-0003G2-5a
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 13:07:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEuQE-0002Nt-S4
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 12:47:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22923
	for <ietf@ietf.org>; Wed, 29 Oct 2003 12:47:43 -0500 (EST)
From: itojun@iijlab.net
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEuQD-0006VC-00
	for ietf@ietf.org; Wed, 29 Oct 2003 12:47:54 -0500
Received: from [206.157.230.254] (helo=hatl0ms22.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEuQD-0006TY-00
	for ietf@ietf.org; Wed, 29 Oct 2003 12:47:53 -0500
Received: from CATL0MS81.corp.cox.com ([10.62.200.231]) by hatl0ms22.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 12:47:22 -0500
Received: from mail pickup service by CATL0MS81.corp.cox.com with Microsoft SMTPSVC;
	 Wed, 29 Oct 2003 12:44:53 -0500
Received: from hatl0ms22.CORP.COX.COM ([10.62.201.69]) by catl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 02:32:39 -0500
Received: from bastion.cox.com ([10.230.2.65]) by hatl0ms22.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 02:32:39 -0500
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion.cox.com (8.11.7p1+Sun/8.11.6) with SMTP id h9T7WdP21219;
	Wed, 29 Oct 2003 02:32:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEkUD-0003Di-Qg
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 02:11:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEkQE-0002Nk-4E
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 02:07:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05501
	for <ietf@ietf.org>; Wed, 29 Oct 2003 02:07:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEkQB-0002u3-00
	for ietf@ietf.org; Wed, 29 Oct 2003 02:07:11 -0500
Received: from coconut.itojun.org ([219.101.47.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEkQB-0002u0-00
	for ietf@ietf.org; Wed, 29 Oct 2003 02:07:11 -0500
Received: from itojun.org (localhost [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP id 2262613
	for <ietf@ietf.org>; Wed, 29 Oct 2003 16:07:11 +0900 (JST)
To: ietf@ietf.org
Subject: mailman switchover: password unknown
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Date: Wed, 29 Oct 2003 16:07:11 +0900
Message-Id: <20031029070711.2262613@coconut.itojun.org>
X-OriginalArrivalTime: 29 Oct 2003 07:32:39.0289 (UTC) FILETIME=[D4B49E90:01C39DEE]
Sender: owner-ietf@ietf.org
Precedence: bulk

	ipv6 and other wg mailing list have switched over to mailman, which
	is good.  however, i don't remember being informed of password to
	be used to control my mailman settings.  am i missing something?

itojun




From owner-ietf@ietf.org  Wed Oct 29 13:39:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25576
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 13:39:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEuis-0003IB-WB
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 13:07:10 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEubu-0002oB-JV
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 12:59:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23366
	for <ietf@ietf.org>; Wed, 29 Oct 2003 12:59:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEubt-0006le-00
	for ietf@ietf.org; Wed, 29 Oct 2003 12:59:57 -0500
Received: from mtiwmhc11.worldnet.att.net ([204.127.131.115])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEubt-0006jm-00
	for ietf@ietf.org; Wed, 29 Oct 2003 12:59:57 -0500
Received: from bolaba (106.sanjose-11-12rs16rt.ca.dial-access.att.net[12.81.4.106])
          by worldnet.att.net (mtiwmhc11) with SMTP
          id <2003102917592411100iu8g4e>; Wed, 29 Oct 2003 17:59:26 +0000
Message-ID: <051a01c39e45$c7bd7480$010aff0a@bolaba>
From: "todd glassey" <todd.glassey@worldnet.att.net>
To: "Ray Plzak" <plzak@arin.net>, "'Bruce Campbell'" <bruce.campbell@ripe.net>
Cc: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>,
        "'Christian Huitema'" <huitema@windows.microsoft.com>, <ietf@ietf.org>,
        <problem-statement@alvestrand.no>
References: <00e901c39e04$87a633a0$728888c0@arin.net>
Subject: Re: Proposed statement quotes wrong numbers
Date: Wed, 29 Oct 2003 09:53:36 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ray - the idea is that you don't need to - the purpose of the IETF as a
standards development platform is to provide the "opportunity for
participation" and not the "enforced mandatory participation" - after all
the IETF is not a slave march (or is it :-)

(Damn this is scary Harald - I am defending the IETF - what's wrong with
this picture?)...

Todd
----- Original Message ----- 
From: "Ray Plzak" <plzak@arin.net>
To: "'Bruce Campbell'" <bruce.campbell@ripe.net>; "'todd glassey'"
<todd.glassey@worldnet.att.net>
Cc: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>; "'Christian
Huitema'" <huitema@windows.microsoft.com>; <ietf@ietf.org>;
<problem-statement@alvestrand.no>
Sent: Wednesday, October 29, 2003 2:07 AM
Subject: RE: Proposed statement quotes wrong numbers


>
>
> > -----Original Message-----
> > From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On
> > Behalf Of Bruce Campbell
> > Sent: Tuesday, October 28, 2003 5:00 AM
> > To: todd glassey
> > Cc: Harald Tveit Alvestrand; Christian Huitema;
> > ietf@ietf.org; problem-statement@alvestrand.no
> > Subject: Re: Proposed statement quotes wrong numbers
> >
> >
> > ( But theres still a lot more than just 700 people who
> > participate in the
> >   IETF )
> >
> > --==--
> > Bruce.
>
> There are certainly more than 700 who attend.  I don't know if you can
> characterize them as all participating.
>
> Ray
>
>




From owner-ietf@ietf.org  Wed Oct 29 14:04:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27442
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 14:04:40 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEvIk-0004hU-2D
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 13:44:14 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEurv-0003X6-74
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 13:16:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24406
	for <ietf@ietf.org>; Wed, 29 Oct 2003 13:16:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEuru-0007B7-00
	for ietf@ietf.org; Wed, 29 Oct 2003 13:16:30 -0500
Received: from smtp101.mail.sc5.yahoo.com ([216.136.174.139])
	by ietf-mx with smtp (Exim 4.12)
	id 1AEurt-0007B4-00
	for ietf@ietf.org; Wed, 29 Oct 2003 13:16:29 -0500
Received: from ts46-01-qdr3166.mrgnhll.ca.charter.com (HELO yahoo.com) (m?seery@68.118.70.100 with plain)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 29 Oct 2003 18:16:28 -0000
Message-ID: <3FA003F5.1060006@yahoo.com>
Date: Wed, 29 Oct 2003 10:16:21 -0800
From: mark seery <m_seery@yahoo.com>
Reply-To: m_seery@yahoo.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proposed statement quotes wrong numbers
References: <002301c39e37$5b6e21c0$1c02a8c0@mobilebill>
In-Reply-To: <002301c39e37$5b6e21c0$1c02a8c0@mobilebill>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Attendance/email registration matters from a number of logistical view 
points (conference setup. server resources, potential revenue stream,.....).

 From an actual work process point of view, it would seem the number of 
active work groups and the number of drafts and RFC proposals created 
impact WG and IESG workload the most. If you take the number of drafts / 
RFC proposals and then some how factor in the breadth and depth of the 
problem spaces they are addessing, then you have another view of the 
scaling problem. One particular aspect that interests me is even 
assuming the WG has the expertise to work a problem domain, what are the 
challenges to IESG members to keep pace with wideining and deepening 
problem domans - it would seem that at some point their feedback would 
become administrative; but perhaps they are all extremely talented 
people with the requisite spare time to keep up / or administrative 
feedback is all that is required?

Sometimes friction is caused by truly deeply divergent view points / 
experiences. Sometimes it is caused simply by a lack of bandwidth 
combined with a very low latency expectation / high quality expectation; 
and of course conversely sometimes the best is the enemy of the good.

FYI, anyone read all the drafts exploding our way in prep for the next 
meeting? (rhetorical of course) And if not, are there challenges to IETF 
members maintaining an end-to-end view point, or is it sufficient for 
people to simply specialize in a certain area without an 
evolving/debated architectural/mission framework in which to work?




From owner-ietf@ietf.org  Wed Oct 29 14:04:47 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27468
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 14:04:47 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEvIj-0004gh-KJ
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 13:44:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEuoQ-0003Vk-12
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 13:12:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24266
	for <ietf@ietf.org>; Wed, 29 Oct 2003 13:12:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEuoP-000778-00
	for ietf@ietf.org; Wed, 29 Oct 2003 13:12:53 -0500
Received: from mtiwmhc11.worldnet.att.net ([204.127.131.115])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEuoO-000773-00
	for ietf@ietf.org; Wed, 29 Oct 2003 13:12:52 -0500
Received: from bolaba (106.sanjose-11-12rs16rt.ca.dial-access.att.net[12.81.4.106])
          by worldnet.att.net (mtiwmhc11) with SMTP
          id <2003102918121911100igeghe>; Wed, 29 Oct 2003 18:12:19 +0000
Message-ID: <055101c39e47$94c41190$010aff0a@bolaba>
From: "todd glassey" <todd.glassey@worldnet.att.net>
To: "bill" <bill@strahm.net>
Cc: <ietf@ietf.org>
References: <002301c39e37$5b6e21c0$1c02a8c0@mobilebill>
Subject: Re: Proposed statement quotes wrong numbers
Date: Wed, 29 Oct 2003 10:07:42 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Bill

----- Original Message ----- 
From: "bill" <bill@strahm.net>
To: "'todd glassey'" <todd.glassey@worldnet.att.net>
Cc: <ietf@ietf.org>
Sent: Wednesday, October 29, 2003 8:11 AM
Subject: RE: Proposed statement quotes wrong numbers


> I would agree in as much as the metric for the productivity of a
> programmer is KLOC.
>
> I don't think you could define a unique e-mail in any sense of the word
> - and even then, know the quality of the technical opinion behind that
> e-mail address.

The quality of the person behind the email address  is totally non-sequitor
to the question at hand. The QUALITY of the participants efforts are not
relevent to the question of whether the world at large was allowed to
participate. That is purely a QUANTITY ISSUE and not attached to the
competence or reasonability of any of the suggestions in the hopper.

- Todd

>
> Bill
>
> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of todd
> glassey
> Sent: Tuesday, October 28, 2003 9:57 PM
> To: bill
> Cc: ietf@ietf.org
> Subject: Re: Proposed statement quotes wrong numbers
>
>
> Bill - you are missing the picture. The ultimate number of bodies that
> the IETF can count on are those unique email addresses. No one said they
> were any particular Vetting Initiative but rather the total possible
> number of "representative opinions" that any consensus could possibly
> count on - assuming an "across the Organizational breadth" as the
> metric.
>
> The IETF is supposed to be representative of the people of the world and
> their representatives to the task of building Internet protocols, right?
> So then the unique email addresses are a direct metric on how well the
> world is represented. Wouldn't you say?
>
> Todd
>
>
> ----- Original Message ----- 
> From: "bill" <bill@strahm.net>
> To: "'todd glassey'" <todd.glassey@worldnet.att.net>
> Cc: <ietf@ietf.org>
> Sent: Tuesday, October 28, 2003 7:46 PM
> Subject: RE: Proposed statement quotes wrong numbers
>
>
> > I disagree with your analysis todd.
> >
> > The strength of the IETF is not in the number of unique e-mail address
>
> > on its e-mail lists (define unique - I have subscribed from probably
> > 10 e-mail addresses over the years - many people I know are subscribed
>
> > with multiple "unique" addresses - many address in reality point to
> > archiving services, other reflectors, peoples inboxes that don't look
> > at the e-mail
>
> Thats a problem with the Registration Process then.
>
> >
> > So I don't think you can even count the number of unique e-mail
> > addresses - but if you could -
> >
> > Peoples technical content/quality very widely, some input is worthless
>
> > (or close to it) and many just monitor what is going on... Other
> > e-mail is critical - either in technical content, providing an
> > alternative viewpoint etc.
>
> What has that to do with how many possible opinions are available
> herein?
>
> >
> > The strength of the IETF is that it is a gathering point for all of
> > these people.
>
> You mean the mailing lists right? - so count the members...
>
> >  Not a quantity of e-mail addresses that can be spammed or something
> > else
>
> Bill -  you have not discounted or invalidated anything I have said
> here. My comment stands.
>
> >
> > Bill
> >
> > -----Original Message-----
> > From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of
> > todd glassey
> > Sent: Tuesday, October 28, 2003 5:09 PM
> > To: Bruce Campbell
> > Cc: Harald Tveit Alvestrand; Christian Huitema; ietf@ietf.org;
> > problem-statement@alvestrand.no
> > Subject: Re: Proposed statement quotes wrong numbers
> >
> >
> > Bruce -
> > ----- Original Message -----
> > From: "Bruce Campbell" <bruce.campbell@ripe.net>
> > To: "todd glassey" <todd.glassey@worldnet.att.net>
> > Cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>; "Christian
> > Huitema" <huitema@windows.microsoft.com>; <ietf@ietf.org>;
> > <problem-statement@alvestrand.no>
> > Sent: Tuesday, October 28, 2003 1:59 AM
> > Subject: Re: Proposed statement quotes wrong numbers
> >
> >
> > > On Mon, 27 Oct 2003, todd glassey wrote:
> > >
> > > > What was the attendance of the last meeting then? and also what
> > > > then
> >
> > > > is
> > the
> > > > sum total of unique EMail Addresses in the Lists then too? I.e.
> > > > what
> >
> > > > is
> > the
> > > > total size of the Vetting Community Resource that the IETF brings
> > > > to
> >
> > > > the Party as an enterprise/org???
> > >
> > > Are you sure that you can count the (large) number of subscribers
> > > that
> >
> > > are on the main IETF lists, and the umpteen WG lists, as
> > > participants?
> >
> > participants as far as meetings are concerned? no - obviously not, but
>
> > this pool of good email addresses constitute the core value of the
> > IETF, that being its Vettig Pool. So yes indeed, and also remember
> > that the IETF is a voluntary particpation standards process and
> > platform, and that the reliable email addresses for this "Vetting
> > Pool" is what the core of the IETF's ideas are vetted against. So put
> > on your "organizational leader's" hat and then ask me the same
> > question -
> >
> > > There
> > > seem to be a lot of people who are subscribed to various
> > > IETF-related lists who do not seem to participate in the IETF
> > > discussions.
> >
> > But the point is that they have the option. Its their choice as to
> > whether to participate of not.
> >
> > >
> > > ( But theres still a lot more than just 700 people who participate
> > > in
> > the
> > >   IETF )
> >
> > I agree - so lets ask the question again, how many unique names are
> > there in the lists - what's the total 'verified email addresses' that
> > make up the total of the vetting pool? - 5000 - 10000 - 50000? what is
>
> > it? Harald? - this seems like a number that you as the Chair of the
> > IETF would not only be proud of, but would also have on the top of
> > your head on a monthly basis... Any ideas as to the number?
> >
> > Todd
> >
> >
> > >
> > > --==--
> > > Bruce.
> >
> >
>
>




From owner-ietf@ietf.org  Wed Oct 29 14:08:06 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27869
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 14:08:06 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEvIk-0004i6-D6
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 13:44:14 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEuuK-0003Xh-Dr
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 13:19:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24522
	for <ietf@ietf.org>; Wed, 29 Oct 2003 13:18:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEuuG-0007Dq-00
	for ietf@ietf.org; Wed, 29 Oct 2003 13:18:56 -0500
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEuuF-0007De-00
	for ietf@ietf.org; Wed, 29 Oct 2003 13:18:55 -0500
Content-class: urn:content-classes:message
Subject: RE: mailman switchover: password unknown
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 29 Oct 2003 10:18:25 -0800
x-mimeole: Produced By Microsoft Exchange V6.5.6944.0
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C6F1@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: mailman switchover: password unknown
Thread-Index: AcOd7swB5LXQEPKdTHW3h5T46Ihj0AAWkybA
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <itojun@iijlab.net>, <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

In many cases, the new temporary password is the email address you are
subscribed to. Not guaranteed to work, but worth a shot.

Michel.


-----Original Message-----
From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of
itojun@iijlab.net
Sent: Tuesday, October 28, 2003 11:07 PM
To: ietf@ietf.org
Subject: mailman switchover: password unknown

	ipv6 and other wg mailing list have switched over to mailman,
which
	is good.  however, i don't remember being informed of password
to
	be used to control my mailman settings.  am i missing something?

itojun




From owner-ietf@ietf.org  Wed Oct 29 14:19:41 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28593
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 14:19:41 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEvIu-0004nB-Uw
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 13:44:24 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AErq7-0003db-D7
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 10:02:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10240
	for <ietf@ietf.org>; Wed, 29 Oct 2003 10:02:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AErq6-00023P-00
	for ietf@ietf.org; Wed, 29 Oct 2003 10:02:26 -0500
Received: from w1309.hostcentric.net ([66.40.78.254])
	by ietf-mx with smtp (Exim 4.12)
	id 1AErq5-00023J-00
	for ietf@ietf.org; Wed, 29 Oct 2003 10:02:25 -0500
Received: (qmail 6914 invoked by alias); 29 Oct 2003 15:02:24 -0000
Received: from unknown (HELO DAVIS1) (12.235.201.242)
  by 0 with SMTP; 29 Oct 2003 15:02:24 -0000
Message-ID: <01eb01c39e2d$a852c720$92d2399d@DAVIS1>
From: "Mark Davis" <mark.davis@jtcsv.com>
To: "Dave Crocker" <dcrocker@brandenburg.com>,
        "John C Klensin" <john-ietf@jck.com>
Cc: <ietf-imaa@imc.org>, <ietf@ietf.org>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com> <12228881609.20031027074111@brandenburg.com> <20031027105222.4eae54fd.moore@cs.utk.edu> <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu> <355752681.20031027161925@brandenburg.com> <1694652.1067364195@localhost> <1957796741.20031028181646@brandenburg.com>
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Wed, 29 Oct 2003 07:02:22 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id KAA10241
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> As for the protocol, I could have sworn that users do not type protocol=
 data
> units directly, or at least that they haven't for roughly 25 years.  (A=
nother
> jibe, citing the fact that utf-8 is, itself, a modification to "raw" un=
icode
> is probably worth repeating, here.)

While it doesn't really have a bearing on the rest of your message, this =
is a
common misperception that I'd like to take a moment to correct.

When Unicode is expressed as a series of bytes, there are a number of equ=
ally
valid sncoding schemes (aka serializations). UTF-8 is one of those scheme=
s, and
is no more or less a "modification", and no more or less "Unicode" than a=
ny
other of these schemes. Different encoding schemes may be better for diff=
erent
domains, but the conversion between any of those schemes is fast and loss=
less.
See http://www.unicode.org/versions/Unicode4.0.0/ch02.pdf, Sections 2.4-2=
.6.

(When Unicode started out 15 years ago, the architecture was different; b=
ut it
has long been structured this way.)

Mark
__________________________________
http://www.macchiato.com
=E2=96=BA =E0=A4=B6=E0=A4=BF=E0=A4=B7=E0=A5=8D=E0=A4=AF=E0=A4=BE=E0=A4=A6=
=E0=A4=BF=E0=A4=9A=E0=A5=8D=E0=A4=9B=E0=A5=87=E0=A4=A4=E0=A5=8D=E0=A4=AA=E0=
=A4=B0=E0=A4=BE=E0=A4=9C=E0=A4=AF=E0=A4=AE=E0=A5=8D =E2=97=84






From owner-ietf@ietf.org  Wed Oct 29 14:21:54 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28886
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 14:21:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEvIv-0004nH-2z
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 13:44:25 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEtBu-00078r-9I
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 11:29:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17448
	for <ietf@ietf.org>; Wed, 29 Oct 2003 11:28:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEtBt-0004N7-00
	for ietf@ietf.org; Wed, 29 Oct 2003 11:29:01 -0500
Received: from [65.246.141.36] (helo=mail.reutershealth.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEtBs-0004N4-00
	for ietf@ietf.org; Wed, 29 Oct 2003 11:29:00 -0500
Received: from skunk.reutershealth.com (mail [65.246.141.36])
	by mail.reutershealth.com (Pro-8.9.3/Pro-8.9.3) with SMTP id LAA08068;
	Wed, 29 Oct 2003 11:24:01 -0500 (EST)
Received: by skunk.reutershealth.com (sSMTP sendmail emulation); Wed, 29 Oct 2003 11:27:39 -0500
Date: Wed, 29 Oct 2003 11:27:39 -0500
From: John Cowan <jcowan@reutershealth.com>
To: Dave Crocker <dhc@dcrocker.net>
Cc: Mark Davis <mark.davis@jtcsv.com>, ietf-imaa@imc.org, ietf@ietf.org
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-ID: <20031029162739.GT8048@skunk.reutershealth.com>
References: <4CD48AD0-07EE-11D8-9C47-000A959CF516@cisco.com> <12228881609.20031027074111@brandenburg.com> <20031027105222.4eae54fd.moore@cs.utk.edu> <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu> <355752681.20031027161925@brandenburg.com> <1694652.1067364195@localhost> <1957796741.20031028181646@brandenburg.com> <01eb01c39e2d$a852c720$92d2399d@DAVIS1> <11354281242.20031029071130@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <11354281242.20031029071130@brandenburg.com>
User-Agent: Mutt/1.4.1i
Sender: owner-ietf@ietf.org
Precedence: bulk

Dave Crocker scripsit:

> That's right.  It is an "encoding".  Raw Unicode takes more than 8-bits.  Lots
> more.  UTF-8 is a method of encoding those raw bits into a non-raw form.

[snip]

> It might be a more efficient encoding, but it is no more "native" or "direct"
> or "raw" than ACE.

That's only true if you take the position that there are no native/direct/raw
encodings of Unicode.

-- 
In politics, obedience and support      John Cowan <jcowan@reutershealth.com>
are the same thing.  --Hannah Arendt    http://www.ccil.org/~cowan





From owner-ietf@ietf.org  Wed Oct 29 16:00:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05861
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 16:00:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEwjt-0003IX-Sa
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 15:16:21 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEvao-0005HA-5I
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 14:02:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27401
	for <ietf@ietf.org>; Wed, 29 Oct 2003 14:02:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEvan-0000R0-00
	for ietf@ietf.org; Wed, 29 Oct 2003 14:02:53 -0500
Received: from [65.246.141.36] (helo=mail.reutershealth.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEvam-0000Qx-00
	for ietf@ietf.org; Wed, 29 Oct 2003 14:02:52 -0500
Received: from skunk.reutershealth.com (mail [65.246.141.36])
	by mail.reutershealth.com (Pro-8.9.3/Pro-8.9.3) with SMTP id NAA10319;
	Wed, 29 Oct 2003 13:57:55 -0500 (EST)
Received: by skunk.reutershealth.com (sSMTP sendmail emulation); Wed, 29 Oct 2003 14:01:33 -0500
Date: Wed, 29 Oct 2003 14:01:33 -0500
From: John Cowan <jcowan@reutershealth.com>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: ietf-imaa@imc.org, ietf@ietf.org
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-ID: <20031029190133.GU8048@skunk.reutershealth.com>
References: <12228881609.20031027074111@brandenburg.com> <20031027105222.4eae54fd.moore@cs.utk.edu> <Pine.LNX.4.60.0310270838030.13643@shiva1.cac.washington.edu> <355752681.20031027161925@brandenburg.com> <1694652.1067364195@localhost> <1957796741.20031028181646@brandenburg.com> <01eb01c39e2d$a852c720$92d2399d@DAVIS1> <11354281242.20031029071130@brandenburg.com> <20031029162739.GT8048@skunk.reutershealth.com> <19761635346.20031029091404@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <19761635346.20031029091404@brandenburg.com>
User-Agent: Mutt/1.4.1i
Sender: owner-ietf@ietf.org
Precedence: bulk

Dave Crocker scripsit:

> Oh?  You mean that Unicode does not fit directly -- ie, with no special
> encoding rules -- into 32 bits, or 24 bits, or somesuch.

Nope.  The Unicode character set maps characters to integers.  How the
integers are mapped to bytes is defined by the encoding rules, of which
there are seven standard ones:  UTF-8, UTF-16, UTF-16BE, UTF-16LE,
UTF-32, UTF-32BE, UTF-32LE.  All have equal status.

> That's the difference between native representation, versus "encoding".

There is no native representation in the sense you mean.  All
representations are equal.

-- 
De plichten van een docent zijn divers,         John Cowan
die van het gehoor ook.                         jcowan@reutershealth.com
      --Edsger Dijkstra                         http://www.ccil.org/~cowan





From owner-ietf@ietf.org  Wed Oct 29 16:26:19 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07013
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 16:26:19 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AExKa-0006H4-Cj
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 15:54:16 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEx8V-0004ws-OT
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 15:41:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05038
	for <ietf@ietf.org>; Wed, 29 Oct 2003 15:41:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEx8U-0002wb-00
	for ietf@ietf.org; Wed, 29 Oct 2003 15:41:46 -0500
Received: from [206.157.230.254] (helo=hatl0ms20.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEx8U-0002w7-00
	for ietf@ietf.org; Wed, 29 Oct 2003 15:41:46 -0500
Received: from catl0ms22.corp.cox.com ([10.62.200.101]) by hatl0ms20.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 15:41:14 -0500
Received: from mail pickup service by catl0ms22.corp.cox.com with Microsoft SMTPSVC;
	 Wed, 29 Oct 2003 15:39:45 -0500
Received: from hatl0ms22.CORP.COX.COM ([10.62.201.69]) by catl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 14:06:04 -0500
Received: from bastion.cox.com ([10.230.2.65]) by hatl0ms22.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 14:06:02 -0500
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion.cox.com (8.11.7p1+Sun/8.11.6) with SMTP id h9TJ62P05666;
	Wed, 29 Oct 2003 14:06:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEvIk-0004hU-2D
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 13:44:14 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEurv-0003X6-74
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 13:16:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24406
	for <ietf@ietf.org>; Wed, 29 Oct 2003 13:16:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEuru-0007B7-00
	for ietf@ietf.org; Wed, 29 Oct 2003 13:16:30 -0500
Received: from smtp101.mail.sc5.yahoo.com ([216.136.174.139])
	by ietf-mx with smtp (Exim 4.12)
	id 1AEurt-0007B4-00
	for ietf@ietf.org; Wed, 29 Oct 2003 13:16:29 -0500
Received: from ts46-01-qdr3166.mrgnhll.ca.charter.com (HELO yahoo.com) (m?seery@68.118.70.100 with plain)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 29 Oct 2003 18:16:28 -0000
Message-ID: <3FA003F5.1060006@yahoo.com>
Date: Wed, 29 Oct 2003 10:16:21 -0800
From: mark seery <m_seery@yahoo.com>
Reply-To: m_seery@yahoo.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proposed statement quotes wrong numbers
References: <002301c39e37$5b6e21c0$1c02a8c0@mobilebill>
In-Reply-To: <002301c39e37$5b6e21c0$1c02a8c0@mobilebill>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Oct 2003 19:06:02.0772 (UTC) FILETIME=[B2505540:01C39E4F]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Attendance/email registration matters from a number of logistical view 
points (conference setup. server resources, potential revenue stream,.....).

 From an actual work process point of view, it would seem the number of 
active work groups and the number of drafts and RFC proposals created 
impact WG and IESG workload the most. If you take the number of drafts / 
RFC proposals and then some how factor in the breadth and depth of the 
problem spaces they are addessing, then you have another view of the 
scaling problem. One particular aspect that interests me is even 
assuming the WG has the expertise to work a problem domain, what are the 
challenges to IESG members to keep pace with wideining and deepening 
problem domans - it would seem that at some point their feedback would 
become administrative; but perhaps they are all extremely talented 
people with the requisite spare time to keep up / or administrative 
feedback is all that is required?

Sometimes friction is caused by truly deeply divergent view points / 
experiences. Sometimes it is caused simply by a lack of bandwidth 
combined with a very low latency expectation / high quality expectation; 
and of course conversely sometimes the best is the enemy of the good.

FYI, anyone read all the drafts exploding our way in prep for the next 
meeting? (rhetorical of course) And if not, are there challenges to IETF 
members maintaining an end-to-end view point, or is it sufficient for 
people to simply specialize in a certain area without an 
evolving/debated architectural/mission framework in which to work?





From owner-ietf@ietf.org  Wed Oct 29 17:08:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09569
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 17:08:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AExma-0007TO-AW
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 16:23:12 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AExPA-0006LW-NP
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 15:59:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05798
	for <ietf@ietf.org>; Wed, 29 Oct 2003 15:58:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AExP9-0003Fm-00
	for ietf@ietf.org; Wed, 29 Oct 2003 15:58:59 -0500
Received: from [206.157.230.254] (helo=hatl0ms22.CORP.COX.COM)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AExP8-0003FX-00
	for ietf@ietf.org; Wed, 29 Oct 2003 15:58:58 -0500
Received: from catl0ms22.corp.cox.com ([10.62.200.101]) by hatl0ms22.CORP.COX.COM with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 15:42:00 -0500
Received: from mail pickup service by catl0ms22.corp.cox.com with Microsoft SMTPSVC;
	 Wed, 29 Oct 2003 15:40:15 -0500
Received: from hatl0ms23.corp.cox.com ([10.64.200.56]) by catl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 14:06:11 -0500
Received: from bastion2.cox.com ([10.225.2.51]) by hatl0ms23.corp.cox.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 29 Oct 2003 14:06:11 -0500
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by bastion2.cox.com (8.11.7p1+Sun/8.11.6) with SMTP id h9TJ6Ao29051;
	Wed, 29 Oct 2003 14:06:11 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AEvIj-0004gh-KJ
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 13:44:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEuoQ-0003Vk-12
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 13:12:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24266
	for <ietf@ietf.org>; Wed, 29 Oct 2003 13:12:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEuoP-000778-00
	for ietf@ietf.org; Wed, 29 Oct 2003 13:12:53 -0500
Received: from mtiwmhc11.worldnet.att.net ([204.127.131.115])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEuoO-000773-00
	for ietf@ietf.org; Wed, 29 Oct 2003 13:12:52 -0500
Received: from bolaba (106.sanjose-11-12rs16rt.ca.dial-access.att.net[12.81.4.106])
          by worldnet.att.net (mtiwmhc11) with SMTP
          id <2003102918121911100igeghe>; Wed, 29 Oct 2003 18:12:19 +0000
Message-ID: <055101c39e47$94c41190$010aff0a@bolaba>
From: "todd glassey" <todd.glassey@worldnet.att.net>
To: "bill" <bill@strahm.net>
Cc: <ietf@ietf.org>
References: <002301c39e37$5b6e21c0$1c02a8c0@mobilebill>
Subject: Re: Proposed statement quotes wrong numbers
Date: Wed, 29 Oct 2003 10:07:42 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Oct 2003 19:06:11.0126 (UTC) FILETIME=[B74B0D60:01C39E4F]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Bill

----- Original Message ----- 
From: "bill" <bill@strahm.net>
To: "'todd glassey'" <todd.glassey@worldnet.att.net>
Cc: <ietf@ietf.org>
Sent: Wednesday, October 29, 2003 8:11 AM
Subject: RE: Proposed statement quotes wrong numbers


> I would agree in as much as the metric for the productivity of a
> programmer is KLOC.
>
> I don't think you could define a unique e-mail in any sense of the word
> - and even then, know the quality of the technical opinion behind that
> e-mail address.

The quality of the person behind the email address  is totally non-sequitor
to the question at hand. The QUALITY of the participants efforts are not
relevent to the question of whether the world at large was allowed to
participate. That is purely a QUANTITY ISSUE and not attached to the
competence or reasonability of any of the suggestions in the hopper.

- Todd

>
> Bill
>
> -----Original Message-----
> From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of todd
> glassey
> Sent: Tuesday, October 28, 2003 9:57 PM
> To: bill
> Cc: ietf@ietf.org
> Subject: Re: Proposed statement quotes wrong numbers
>
>
> Bill - you are missing the picture. The ultimate number of bodies that
> the IETF can count on are those unique email addresses. No one said they
> were any particular Vetting Initiative but rather the total possible
> number of "representative opinions" that any consensus could possibly
> count on - assuming an "across the Organizational breadth" as the
> metric.
>
> The IETF is supposed to be representative of the people of the world and
> their representatives to the task of building Internet protocols, right?
> So then the unique email addresses are a direct metric on how well the
> world is represented. Wouldn't you say?
>
> Todd
>
>
> ----- Original Message ----- 
> From: "bill" <bill@strahm.net>
> To: "'todd glassey'" <todd.glassey@worldnet.att.net>
> Cc: <ietf@ietf.org>
> Sent: Tuesday, October 28, 2003 7:46 PM
> Subject: RE: Proposed statement quotes wrong numbers
>
>
> > I disagree with your analysis todd.
> >
> > The strength of the IETF is not in the number of unique e-mail address
>
> > on its e-mail lists (define unique - I have subscribed from probably
> > 10 e-mail addresses over the years - many people I know are subscribed
>
> > with multiple "unique" addresses - many address in reality point to
> > archiving services, other reflectors, peoples inboxes that don't look
> > at the e-mail
>
> Thats a problem with the Registration Process then.
>
> >
> > So I don't think you can even count the number of unique e-mail
> > addresses - but if you could -
> >
> > Peoples technical content/quality very widely, some input is worthless
>
> > (or close to it) and many just monitor what is going on... Other
> > e-mail is critical - either in technical content, providing an
> > alternative viewpoint etc.
>
> What has that to do with how many possible opinions are available
> herein?
>
> >
> > The strength of the IETF is that it is a gathering point for all of
> > these people.
>
> You mean the mailing lists right? - so count the members...
>
> >  Not a quantity of e-mail addresses that can be spammed or something
> > else
>
> Bill -  you have not discounted or invalidated anything I have said
> here. My comment stands.
>
> >
> > Bill
> >
> > -----Original Message-----
> > From: owner-ietf@ietf.org [mailto:owner-ietf@ietf.org] On Behalf Of
> > todd glassey
> > Sent: Tuesday, October 28, 2003 5:09 PM
> > To: Bruce Campbell
> > Cc: Harald Tveit Alvestrand; Christian Huitema; ietf@ietf.org;
> > problem-statement@alvestrand.no
> > Subject: Re: Proposed statement quotes wrong numbers
> >
> >
> > Bruce -
> > ----- Original Message -----
> > From: "Bruce Campbell" <bruce.campbell@ripe.net>
> > To: "todd glassey" <todd.glassey@worldnet.att.net>
> > Cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>; "Christian
> > Huitema" <huitema@windows.microsoft.com>; <ietf@ietf.org>;
> > <problem-statement@alvestrand.no>
> > Sent: Tuesday, October 28, 2003 1:59 AM
> > Subject: Re: Proposed statement quotes wrong numbers
> >
> >
> > > On Mon, 27 Oct 2003, todd glassey wrote:
> > >
> > > > What was the attendance of the last meeting then? and also what
> > > > then
> >
> > > > is
> > the
> > > > sum total of unique EMail Addresses in the Lists then too? I.e.
> > > > what
> >
> > > > is
> > the
> > > > total size of the Vetting Community Resource that the IETF brings
> > > > to
> >
> > > > the Party as an enterprise/org???
> > >
> > > Are you sure that you can count the (large) number of subscribers
> > > that
> >
> > > are on the main IETF lists, and the umpteen WG lists, as
> > > participants?
> >
> > participants as far as meetings are concerned? no - obviously not, but
>
> > this pool of good email addresses constitute the core value of the
> > IETF, that being its Vettig Pool. So yes indeed, and also remember
> > that the IETF is a voluntary particpation standards process and
> > platform, and that the reliable email addresses for this "Vetting
> > Pool" is what the core of the IETF's ideas are vetted against. So put
> > on your "organizational leader's" hat and then ask me the same
> > question -
> >
> > > There
> > > seem to be a lot of people who are subscribed to various
> > > IETF-related lists who do not seem to participate in the IETF
> > > discussions.
> >
> > But the point is that they have the option. Its their choice as to
> > whether to participate of not.
> >
> > >
> > > ( But theres still a lot more than just 700 people who participate
> > > in
> > the
> > >   IETF )
> >
> > I agree - so lets ask the question again, how many unique names are
> > there in the lists - what's the total 'verified email addresses' that
> > make up the total of the vetting pool? - 5000 - 10000 - 50000? what is
>
> > it? Harald? - this seems like a number that you as the Chair of the
> > IETF would not only be proud of, but would also have on the top of
> > your head on a monthly basis... Any ideas as to the number?
> >
> > Todd
> >
> >
> > >
> > > --==--
> > > Bruce.
> >
> >
>
>





From owner-ietf@ietf.org  Wed Oct 29 19:06:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16059
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 19:06:46 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AF06t-0001Im-KD
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 18:52:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEzwr-00015O-1n
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 18:41:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15114
	for <ietf@ietf.org>; Wed, 29 Oct 2003 18:41:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEzwp-0007Lg-00
	for ietf@ietf.org; Wed, 29 Oct 2003 18:41:55 -0500
Received: from sentosa.post1.com ([202.27.17.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1AEzwo-0007Kw-00
	for ietf@ietf.org; Wed, 29 Oct 2003 18:41:54 -0500
Received: (qmail 42705 invoked from network); 29 Oct 2003 23:59:48 -0000
Received: from p5200-ipad75marunouchi.tokyo.ocn.ne.jp (HELO pobox.org.sg) (220.107.220.200)
  by sentosa.post1.com with SMTP; 29 Oct 2003 23:59:48 -0000
Message-ID: <3FA04CA4.6050409@pobox.org.sg>
Date: Thu, 30 Oct 2003 07:26:28 +0800
From: James Seng <jseng@pobox.org.sg>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en, zh-cn, zh-tw, ja, ko
MIME-Version: 1.0
To: Mark Crispin <MRC@CAC.Washington.EDU>
CC: Mark Davis <mark.davis@jtcsv.com>, Keith Moore <moore@cs.utk.edu>,
        dcrocker@brandenburg.com, paf@cisco.com, ietf-imaa@imc.org,
        idn@ops.ietf.org, ietf-822@imc.org, ietf@ietf.org,
        ietf-pop3ext@imc.org, lemonade@ietf.org, discuss@apps.ietf.org,
        IMAP Extensions WG <ietf-imapext@imc.org>, ietf-smtp@imc.org,
        presnick@qualcomm.com, hardie@qualcomm.com, ned.freed@mrochek.com
Subject: Re: [idn] Re: FYI: BOF on Internationalized Email Addresses (IEA)
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU>
In-Reply-To: <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Crispin,

You need to get out of US (or Wsshington) more often.

-James Seng

> I am not convinced that it is possible to use a computer on the Internet
> anywhere in the world without at least a basic acquaintance with Latin
> script.
> 
> I do not believe many individuals (other than primary school children) are
> literate in their native language but are completely illiterate in Latin
> script.  This does not mean "being able to read or write the English
> language"; rather, this simply means knowing the Latin script alphabet.
> 
> Put another way, individuals who are completely illiterate in Latin script
> are also likely to be illiterate in their native language script as well.
> 
> No other script on the planet has such international recognition.
> 
> There is undoubtably a *preference* for one's native script; and that
> preference should be respected as much as possible.
> 
> -- Mark --
> 
> http://staff.washington.edu/mrc
> Science does not emerge from voting, party politics, or public debate.
> Si vis pacem, para bellum.
> 
> 
> 
> 
> 





From owner-ietf@ietf.org  Wed Oct 29 19:08:46 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16190
	for <ietf-web-archive@odin.ietf.org>; Wed, 29 Oct 2003 19:08:45 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AF06t-0001Is-Rw
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 18:52:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEzx8-00015Q-TD
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 18:42:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15130
	for <ietf@ietf.org>; Wed, 29 Oct 2003 18:42:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEzx7-0007MN-00
	for ietf@ietf.org; Wed, 29 Oct 2003 18:42:13 -0500
Received: from sentosa.post1.com ([202.27.17.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1AEzx6-0007LI-00
	for ietf@ietf.org; Wed, 29 Oct 2003 18:42:12 -0500
Received: (qmail 42733 invoked from network); 30 Oct 2003 00:00:08 -0000
Received: from p5200-ipad75marunouchi.tokyo.ocn.ne.jp (HELO pobox.org.sg) (220.107.220.200)
  by sentosa.post1.com with SMTP; 30 Oct 2003 00:00:08 -0000
Message-ID: <3FA04E1E.9070906@pobox.org.sg>
Date: Thu, 30 Oct 2003 07:32:46 +0800
From: James Seng <jseng@pobox.org.sg>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en, zh-cn, zh-tw, ja, ko
MIME-Version: 1.0
To: Mark Crispin <MRC@CAC.Washington.EDU>
CC: Abhijit Menon-Sen <ams@wiw.org>, ietf-imaa@imc.org, idn@ops.ietf.org,
        ietf-822@imc.org, ietf@ietf.org, ietf-pop3ext@imc.org,
        lemonade@ietf.org, discuss@apps.ietf.org, ietf-imapext@imc.org,
        ietf-smtp@imc.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU> <20031028095243.A1525@lustre.dyn.wiw.org> <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>
In-Reply-To: <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I do not believe that this is true for Chinese.  AFAIK, Chinese primary
> school kids use Latin script with hanyu-pinyin as a stopgap prior to their
> mastery of Han script (which takes many years).

Nope. Hanyu Pinyin was designed to replace the Han ideograph but it 
never did.

> Note that when I say "recognize Latin script", I mean the ability to
> determine that "dog" is a three-letter word that has the letters "d", "o",
> and "g", each of which the individual recognizes and can name.  This does
> not include the ability to recognize that this refers to a domesticated
> canine.

Based on your reasonings, I think we should all reverted back to 
numbers, because that is the only universal recongizable set of symbols 
we have.

We have this argument in IDN before and we certainly dont need this 
again. If you feel we should all stick to Latin, yes, you are entitled 
to your opinion but please do so in other place, and not here. The group 
is suppose to work on Internationalization of Email address 
(identifiers), not debate whether we need it or not.

-James Seng





From owner-ietf@ietf.org  Thu Oct 30 00:01:33 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25455
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 00:01:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AF4hA-0000Ul-9H
	for ietf-list@asgard.ietf.org; Wed, 29 Oct 2003 23:46:04 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AF4gA-0000Ss-Tg
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 23:45:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24788
	for <ietf@ietf.org>; Wed, 29 Oct 2003 23:44:51 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF4g8-0004ap-00
	for ietf@ietf.org; Wed, 29 Oct 2003 23:45:00 -0500
Received: from h80ad26bd.async.vt.edu ([128.173.38.189] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF4g7-0004al-00
	for ietf@ietf.org; Wed, 29 Oct 2003 23:45:00 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9U4iu9X016162;
	Wed, 29 Oct 2003 23:44:56 -0500
Message-Id: <200310300444.h9U4iu9X016162@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: James Seng <jseng@pobox.org.sg>
Cc: ietf-imaa@imc.org, ietf-822@imc.org, ietf@ietf.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA) 
In-Reply-To: Your message of "Thu, 30 Oct 2003 07:32:46 +0800."
             <3FA04E1E.9070906@pobox.org.sg> 
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU> <20031028095243.A1525@lustre.dyn.wiw.org> <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>
            <3FA04E1E.9070906@pobox.org.sg>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1782565142P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 29 Oct 2003 23:44:56 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1782565142P
Content-Type: text/plain; charset=us-ascii

On Thu, 30 Oct 2003 07:32:46 +0800, James Seng said:
> to your opinion but please do so in other place, and not here. The group 
> is suppose to work on Internationalization of Email address 
> (identifiers), not debate whether we need it or not.

Any group that addresses "how" and "for which contexts" without having
a good grasp on "why" is inventing solutions in search of problems.

Mark actually *does* have a *very* valid point - on today's internet, if you
cannot recognize and enter the glyphs for at least c, h, m, o p, t, w, ':',
'@', '.', and '/' you are effectively unable to use the internet.  It may not
make any sense to you, but you can at least recognize and enter them (note that
this same issue was one of the biggest arguments against the .biz domain).

So.. having established that if they're currently using the internet, they can at least
recognize and enter the Latin glyphs, this raises a number of *very* important questions:

1) Is there reason to *not* expect said knowledge of Latin glyphs in the future?
If not, what user group(s) will be literate but not know the Latin charset?

2) Is a "community" approach acceptable?  Is usage of Han OK as long as
you're interacting with other Han users, or are the issues of leakage too high?

3) What *are* the issues of leakage? What am I expected to see if I get some Han,
and how am I to interact with it?  Equally important, what does the Han user do
with my leaked Latin-A characters?

4) Here's a somewhat related issue - looking at the U0100.pdf from www.unicode,org,
I had to enlarge page 2 quite a bit before I could see the difference between the glyphs
at 0114/0115 (capital/small e with breve) and 011A/011B (capital/small e with caron).
And I know my way around most of the Latin characters - our hypothetical Han
user is going to be swinging in the breeze if he gets a business card with e-caron on it.

And if you can't safely put e-caron on a business card, why are we bothering?

--==_Exmh_-1782565142P
Content-Type: application/pgp-signature

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

iD8DBQE/oJdHcC3lWbTT17ARApI2AKDk4oBcEkieOgYRCJBtIedEsSrGGACeJNPE
EFv6UMsEZEZlGu4qGL/6tjA=
=ZXEP
-----END PGP SIGNATURE-----

--==_Exmh_-1782565142P--



From owner-ietf@ietf.org  Thu Oct 30 01:37:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28079
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 01:37:58 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AF6J5-0001qu-1l
	for ietf-list@asgard.ietf.org; Thu, 30 Oct 2003 01:29:19 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AF6Ek-0001mU-IT
	for ietf@asgard.ietf.org; Thu, 30 Oct 2003 01:24:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27687
	for <ietf@ietf.org>; Thu, 30 Oct 2003 01:24:41 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF6Ei-0005nh-00
	for ietf@ietf.org; Thu, 30 Oct 2003 01:24:48 -0500
Received: from h80ad26bd.async.vt.edu ([128.173.38.189] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF6Eg-0005ne-00
	for ietf@ietf.org; Thu, 30 Oct 2003 01:24:47 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9U6OX9X018995;
	Thu, 30 Oct 2003 01:24:33 -0500
Message-Id: <200310300624.h9U6OX9X018995@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Tan Tin Wee <tinwee@bic.nus.edu.sg>
Cc: ietf-imaa@imc.org, ietf-822@imc.org, ietf@ietf.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA) 
In-Reply-To: Your message of "Thu, 30 Oct 2003 13:33:31 +0800."
             <3FA0A2AB.1050803@bic.nus.edu.sg> 
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU> <20031028095243.A1525@lustre.dyn.wiw.org> <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU> <3FA04E1E.9070906@pobox.org.sg> <200310300444.h9U4iu9X016162@turing-police.cc.vt.edu>
            <3FA0A2AB.1050803@bic.nus.edu.sg>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-458448288P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 30 Oct 2003 01:24:33 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-458448288P
Content-Type: text/plain; charset=us-ascii

On Thu, 30 Oct 2003 13:33:31 +0800, Tan Tin Wee said:
> And if they need to send email to outsiders, then they would
> send in ASCII email address, as routinely as they would

OK.. I get that part.  Now for the big question:  You're there in this
Mongolian intranet, and find you need to ask me a technical question,
so my address gets entered in ascii. OK so far.  You now decide you
need to cc: somebody on the intranet so they know I've been asked.

1) What does that person do with my ascii-fied address?
2) How do I do a 'reply all' to both of you?

3) How is your From: address encoded so it's usable *BOTH* from where
I am and from where your co-worker is?  

3a) Can you achieve goal (3) while using the same From: as you would use
if you were mailing ONLY to the intranet (so people don't have to maintain
2 differently encoded values for your address for filtering purposes, etc).

If whatever Mongolia was doing was guaranteed to stay in Mongolia, it wouldn't
be an issue.  However, people inside the enclave *will* want to communicate
with outsiders as well - and the instant you allow an e-mail to cross the
border, you have to get all these types of issues sorted out.

Mark Crispin's point was that currently, knowledge of Latin glyphs *is*
assumed, and as far as anybody has evidenced, this hypothetical Mongolian
intranet with many non-Latin-aware users is still hypothetical - and with no
evidence saying there actually IS one in the works someplace.  So Mark quite
reasonably pointed out that it may very well make more *engineering* sense to
simply train the very small number of users who don't know Latin glyphs than to
come up with some very convoluted scheme that annoys everybody else.

The tail has to be a certain size before it's able to wag the dog. 

--==_Exmh_-458448288P
Content-Type: application/pgp-signature

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

iD8DBQE/oK6gcC3lWbTT17ARAtInAJ9M7ERxOW5GNJtOru9SDwejFHw/0QCeORim
W4c7P+zKtSCHYIKSabU/mH0=
=7R8A
-----END PGP SIGNATURE-----

--==_Exmh_-458448288P--



From owner-ietf@ietf.org  Thu Oct 30 02:21:38 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11855
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 02:21:38 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AF6xb-0006FA-EK
	for ietf-list@asgard.ietf.org; Thu, 30 Oct 2003 02:11:11 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AF6vK-0005p8-BI
	for ietf@asgard.ietf.org; Thu, 30 Oct 2003 02:08:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07584
	for <ietf@ietf.org>; Thu, 30 Oct 2003 02:08:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF6vH-0006J8-00
	for ietf@ietf.org; Thu, 30 Oct 2003 02:08:48 -0500
Received: from pmesmtp02.wcom.com ([199.249.20.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF6vH-0006It-00
	for ietf@ietf.org; Thu, 30 Oct 2003 02:08:47 -0500
Received: from pmismtp02.wcomnet.com ([166.38.62.37])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HNK005J96HQSS@firewall.wcom.com> for ietf@ietf.org; Thu,
 30 Oct 2003 07:08:14 +0000 (GMT)
Received: from pmismtp02.wcomnet.com by pmismtp02.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HNK00H016HQWF@pmismtp02.wcomnet.com>; Thu,
 30 Oct 2003 07:08:14 +0000 (GMT)
Received: from vint.mci.com ([166.50.128.35])
 by pmismtp02.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0HNK00G5T6HNMM@pmismtp02.wcomnet.com>; Thu,
 30 Oct 2003 07:08:14 +0000 (GMT)
Date: Thu, 30 Oct 2003 02:08:07 -0500
From: "vinton g. cerf" <vinton.g.cerf@mci.com>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
X-Sender: vcerf@pop.mcilink.com
To: Valdis.Kletnieks@vt.edu, James Seng <jseng@pobox.org.sg>
Cc: ietf-imaa@imc.org, ietf-822@imc.org, ietf@ietf.org
Message-id: <5.2.0.9.2.20031030020424.031dfeb0@pop.mcilink.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Content-type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Valdis,

I think your example underscores the difference between localization
of an interface to make use of local language/script and globalization
that permits interworking among all parties, independent of their local
language and script. 

the confusion between these two (familiar user interfaces vs ability
to communicate with everyone) makes for a good deal of debate. 

I hope can keep in mind both of these desirable aspects but most 
especially our ability to preserve the global communication needed.

The dialing of telephone numbers relies on the ability of every 
party to enter digits while the system does not care much about
what language we speak. One might think of Latin-A as the Internet
equivalent of digits - however, I don't know whether it is a valid
analogy. 

vint

At 11:44 PM 10/29/2003 -0500, Valdis.Kletnieks@vt.edu wrote:


>*** PGP SIGNATURE VERIFICATION ***
>*** Status:   Good Signature from Invalid Key
>*** Alert:    Please verify signer's key before trusting signature.
>*** Signer:   Valdis Kletnieks <valdis.kletnieks@vt.edu> (0xB4D3D7B0)
>*** Signed:   10/29/2003 11:44:55 PM
>*** Verified: 10/30/2003 2:02:59 AM
>*** BEGIN PGP VERIFIED MESSAGE ***
>
>On Thu, 30 Oct 2003 07:32:46 +0800, James Seng said:
>> to your opinion but please do so in other place, and not here. The group 
>> is suppose to work on Internationalization of Email address 
>> (identifiers), not debate whether we need it or not.
>
>Any group that addresses "how" and "for which contexts" without having
>a good grasp on "why" is inventing solutions in search of problems.
>
>Mark actually *does* have a *very* valid point - on today's internet, if you
>cannot recognize and enter the glyphs for at least c, h, m, o p, t, w, ':',
>'@', '.', and '/' you are effectively unable to use the internet.  It may not
>make any sense to you, but you can at least recognize and enter them (note that
>this same issue was one of the biggest arguments against the .biz domain).
>
>So.. having established that if they're currently using the internet, they can at least
>recognize and enter the Latin glyphs, this raises a number of *very* important questions:
>
>1) Is there reason to *not* expect said knowledge of Latin glyphs in the future?
>If not, what user group(s) will be literate but not know the Latin charset?
>
>2) Is a "community" approach acceptable?  Is usage of Han OK as long as
>you're interacting with other Han users, or are the issues of leakage too high?
>
>3) What *are* the issues of leakage? What am I expected to see if I get some Han,
>and how am I to interact with it?  Equally important, what does the Han user do
>with my leaked Latin-A characters?
>
>4) Here's a somewhat related issue - looking at the U0100.pdf from www.unicode,org,
>I had to enlarge page 2 quite a bit before I could see the difference between the glyphs
>at 0114/0115 (capital/small e with breve) and 011A/011B (capital/small e with caron).
>And I know my way around most of the Latin characters - our hypothetical Han
>user is going to be swinging in the breeze if he gets a business card with e-caron on it.
>
>And if you can't safely put e-caron on a business card, why are we bothering?
>
>
>*** END PGP VERIFIED MESSAGE ***

Vint Cerf
SVP Technology Strategy
MCI
22001 Loudoun County Parkway, F2-4115
Ashburn, VA 20147
703 886 1690 (v806 1690)
703 886 0047 fax
vinton.g.cerf@mci.com
www.mci.com/cerfsup 




From owner-ietf@ietf.org  Thu Oct 30 02:23:02 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11997
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 02:23:02 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AF6xc-0006FZ-8W
	for ietf-list@asgard.ietf.org; Thu, 30 Oct 2003 02:11:12 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AF6wU-000624-Kf
	for ietf@asgard.ietf.org; Thu, 30 Oct 2003 02:10:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08817
	for <ietf@ietf.org>; Thu, 30 Oct 2003 02:09:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF6wS-0006Ji-00
	for ietf@ietf.org; Thu, 30 Oct 2003 02:10:00 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF6wR-0006JV-00
	for ietf@ietf.org; Thu, 30 Oct 2003 02:09:59 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9U7FXf10772;
	Wed, 29 Oct 2003 23:15:33 -0800
Date: Wed, 29 Oct 2003 23:09:24 -0800
From: Dave Crocker <dhc@dcrocker.net>
X-Mailer: The Bat! (v2.00.22)
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <87111751500.20031029230924@brandenburg.com>
To: Valdis.Kletnieks@vt.edu
CC: ietf-imaa@imc.org, ietf-822@imc.org, ietf@ietf.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <200310300444.h9U4iu9X016162@turing-police.cc.vt.edu>
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU>
 <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU>
 <20031028095243.A1525@lustre.dyn.wiw.org>
 <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>
 <3FA04E1E.9070906@pobox.org.sg>
 <200310300444.h9U4iu9X016162@turing-police.cc.vt.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Valdis,

VKve> Mark actually *does* have a *very* valid point - on today's internet, if you



1. The goal is to go beyond today's internet. (But then, that is always the
goal of a new standard.)

2. Although the primary focus of IETF work is to make standards for global
interoperability, there are fine and valid needs for making global conventions
to support local interoperability. Permitting local-part to be unicode is one
of those. (And, no, I do not believe this requires changing the global parsing
rules.)

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>




From owner-ietf@ietf.org  Thu Oct 30 08:05:57 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20730
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 08:05:56 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFCGW-0004F7-LR
	for ietf-list@asgard.ietf.org; Thu, 30 Oct 2003 07:51:04 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AFCBf-0004Du-Se
	for ietf@asgard.ietf.org; Thu, 30 Oct 2003 07:46:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20196
	for <ietf@ietf.org>; Thu, 30 Oct 2003 07:45:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFCBf-0002bm-00
	for ietf@ietf.org; Thu, 30 Oct 2003 07:46:03 -0500
Received: from web14207.mail.yahoo.com ([216.136.173.71])
	by ietf-mx with smtp (Exim 4.12)
	id 1AFCBe-0002bQ-00
	for ietf@ietf.org; Thu, 30 Oct 2003 07:46:02 -0500
Message-ID: <20031030124555.66343.qmail@web14207.mail.yahoo.com>
Received: from [203.124.140.107] by web14207.mail.yahoo.com via HTTP; Thu, 30 Oct 2003 04:45:55 PST
Date: Thu, 30 Oct 2003 04:45:55 -0800 (PST)
From: chintan sheth <shethch@yahoo.com>
Subject: Protocol RFC format/syntax/template
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi,

Is there any standard template/syntax/format to be
followed whenever we want to write an RFC for a
particular protocol. While writing SNMP MIB RFC's
there is a particular syntax (SMIv1/v2) followed. Is
there any similar structure followed for protocol's
too. If so, can anyone point me to the syntax rules
that are to be followed for writing a protocol RFC.

Thanks,

Chintan

__________________________________
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
http://launch.yahoo.com/promos/britneyspears/



From owner-ietf@ietf.org  Thu Oct 30 08:05:58 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20746
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 08:05:57 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFCGX-0004FD-19
	for ietf-list@asgard.ietf.org; Thu, 30 Oct 2003 07:51:05 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AFCF0-0004E7-FG
	for ietf@asgard.ietf.org; Thu, 30 Oct 2003 07:49:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20237
	for <ietf@ietf.org>; Thu, 30 Oct 2003 07:49:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFCEz-0002cy-00
	for ietf@ietf.org; Thu, 30 Oct 2003 07:49:29 -0500
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFCEz-0002cl-00
	for ietf@ietf.org; Thu, 30 Oct 2003 07:49:29 -0500
Received: from dfnjgl21 (12-237-229-250.client.attbi.com[12.237.229.250])
          by comcast.net (rwcrmhc11) with SMTP
          id <2003103012485201300gkmv9e>
          (Authid: sdawkins@comcast.net);
          Thu, 30 Oct 2003 12:48:52 +0000
Message-ID: <0c7801c39ee4$39140010$0400a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf-imaa@imc.org>, <ietf-822@imc.org>, <ietf@ietf.org>
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU> <20031028095243.A1525@lustre.dyn.wiw.org> <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU> <3FA04E1E.9070906@pobox.org.sg> <200310300444.h9U4iu9X016162@turing-police.cc.vt.edu> <87111751500.20031029230924@brandenburg.com>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Thu, 30 Oct 2003 06:49:13 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ummm, I'm not a Genius of E-mail, but I have sent a few. :-}

The very-helpful scenario Valdis included a couple of notes back ("if
we punt on common ability to use Latin glyphs") has happened in my
life, at the presentation level - I've been swapping e-mail back and
forth with some very talented people in Korea. So, they have
ascii-fied e-mail addresses that aren't THAT obvious (I think spencer,
or dcrocker, or even vinton.c.cerf, is pretty obvious, but my three
kids are daddys_little_hurl (April), buddha20oz(Daniel), and
gypsycameo(Amy), so you're not going to figure out who's been copied
just by looking at e-mail addresses in the general case), and
presentation names that are localized, so I can't read them. If a
collaborator copies three people who I can't decode from the e-mail
address, and can't read from the presentation name, I can't figure out
if another researcher has been copied or not, without asking.

If I can't read the characters in the local part of the e-mail
address, there's even less chance I'll be able to figure out who's
been copied (and usually, figuring out who hasn't been copied is more
interesting, in my limited experience) - I know I'm going to regret
not reading Korean when I'm at IETF 59, but today, I don't read
Korean. Game over..

I agree with Dave in the general case ("the goal is to go beyond
today's Internet"), but am wondering if that also requires us to go
beyond today's language capability when we start leaking these
addresses between enclaves. I am sensitive to the comments expressed
in this thread, that a heckuva lot of people have to learn two sets of
glyphs, and I'm not one of them - I just don't see how we do it any
other way.

Oh, yeah - the other thing was, discussion about leaking out of a
Mongolian enclave is interesting, but leaking between two non-Latin
enclaves is where the rubber meets the road, and I've worked with too
many smart people from Asia/Pacific and from the Middle East to
believe that we wouldn't have two non-Latin enclaves who would be
collaborating about fifteen minutes after the second enclave starts
up...

Spencer

p.s. Because I'm not a Genius of Internationalization, I apologize for
using country names as if they were character sets in advance - hope
my comment is still somewhat clear.

p.p.s. If we DO discover life on Mars, I'm willing to change my mind.
I know my stepson would love ro have an excuse to learn
Martian/Klingon/etc....




From owner-ietf@ietf.org  Thu Oct 30 08:54:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22178
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 08:54:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFD9j-0005W8-QK
	for ietf-list@asgard.ietf.org; Thu, 30 Oct 2003 08:48:07 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AFD6o-0005Tx-4R
	for ietf@asgard.ietf.org; Thu, 30 Oct 2003 08:45:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21913
	for <ietf@ietf.org>; Thu, 30 Oct 2003 08:44:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFD6n-0003MJ-00
	for ietf@ietf.org; Thu, 30 Oct 2003 08:45:05 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFD6n-0003KR-00
	for ietf@ietf.org; Thu, 30 Oct 2003 08:45:05 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id AC7EB4C; Thu, 30 Oct 2003 08:43:11 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
Organization: Secure Software -- http://www.securesw.com/
To: "Spencer Dawkins" <spencer@mcsr-labs.org>, <ietf-imaa@imc.org>,
        <ietf-822@imc.org>, <ietf@ietf.org>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Thu, 30 Oct 2003 08:44:03 -0500
User-Agent: KMail/1.5.2
References: <E1AEH14-000N0E-GD@psg.com> <87111751500.20031029230924@brandenburg.com> <0c7801c39ee4$39140010$0400a8c0@DFNJGL21>
In-Reply-To: <0c7801c39ee4$39140010$0400a8c0@DFNJGL21>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310300844.03939.spamtrap.ietf@dja.mailme.org>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Thu October 30 2003 07:49, Spencer Dawkins wrote:

 > leaking between two non-Latin
 > enclaves is where the rubber meets the road,

Specifically, two enclaves with *different* non-Latin character sets.  
(Probably what you meant, but....)

 > I've worked with too many smart people from Asia/Pacific and
 > from the Middle East to believe that we wouldn't have two
 > non-Latin enclaves who would be collaborating about fifteen
 > minutes after the second enclave starts up...

Exactly.  The developinging friendship between Israel and India, two 
tech powerhouses using radically different non-Latin character sets, 
should be quite interesting in many ways, including this.

For that matter, even within India, there are several (somewhere in the 
teens, IIRC) languages widely used.  Can someone tell us, how many 
different character sets these languages use?

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
Web: http://destined.to/program http://listen.to/davearonson




From owner-ietf@ietf.org  Thu Oct 30 09:46:29 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23698
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 09:46:29 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFDql-0006b3-2x
	for ietf-list@asgard.ietf.org; Thu, 30 Oct 2003 09:32:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AEzb0-0000HK-DU
	for ietf@asgard.ietf.org; Wed, 29 Oct 2003 18:19:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14282;
	Wed, 29 Oct 2003 18:19:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEzay-0006nb-00; Wed, 29 Oct 2003 18:19:20 -0500
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEzax-0006mT-00; Wed, 29 Oct 2003 18:19:19 -0500
Received: from INET-VRS-03.redmond.corp.microsoft.com ([157.54.5.27]) by mail3.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 29 Oct 2003 15:18:49 -0800
Received: from 157.54.8.109 by INET-VRS-03.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 29 Oct 2003 15:18:49 -0800
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-hub-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 29 Oct 2003 15:18:49 -0800
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Wed, 29 Oct 2003 15:19:48 -0800
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Wed, 29 Oct 2003 15:18:47 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7097.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [idn] FYI: BOF on Internationalized Email Addresses (IEA)
Date: Wed, 29 Oct 2003 15:18:45 -0800
Message-ID: <84DD35E3DD87D5489AC42A59926DABE9046E700D@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: [idn] FYI: BOF on Internationalized Email Addresses (IEA)
thread-index: AcOc5UacENkLjcQgTxGePqP067EdhwBjOJ7A
From: "Michel Suignard" <michelsu@windows.microsoft.com>
To: "James Seng" <jseng@pobox.org.sg>,
        =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
Cc: <ietf-imaa@imc.org>, <idn@ops.ietf.org>, <ietf-822@imc.org>,
        <ietf@ietf.org>, <ietf-pop3ext@imc.org>, <lemonade@ietf.org>,
        <discuss@apps.ietf.org>, <ietf-imapext@imc.org>, <ietf-smtp@imc.org>,
        "Pete Resnick" <presnick@qualcomm.com>,
        "Ted Hardie" <hardie@qualcomm.com>,
        "Ned Freed" <ned.freed@mrochek.com>
X-OriginalArrivalTime: 29 Oct 2003 23:18:47.0668 (UTC) FILETIME=[014BD340:01C39E73]
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

JS>I seen John and Paul proposal but I have not seen Michel. Is there a =
draft that I can read
JS>up?=20

I don't have a proposal. I am listed there as a co-editor of the IRI =
spec which has a peripheral impact on the IEA (such as extending the URI =
mailto scheme). Like many I am listening with interest to the points =
made for or against the two proposals.

Michel Suignard





From owner-ietf@ietf.org  Thu Oct 30 10:41:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27293
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 10:41:22 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFElL-0005sW-P3
	for ietf-list@asgard.ietf.org; Thu, 30 Oct 2003 10:31:03 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AF5RG-0001Ry-Qz
	for ietf@asgard.ietf.org; Thu, 30 Oct 2003 00:33:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26391
	for <ietf@ietf.org>; Thu, 30 Oct 2003 00:33:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF5RE-0005E7-00
	for ietf@ietf.org; Thu, 30 Oct 2003 00:33:40 -0500
Received: from leonis.nus.edu.sg ([137.132.1.18])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF5RD-0005E4-00
	for ietf@ietf.org; Thu, 30 Oct 2003 00:33:40 -0500
Received: from bic.nus.edu.sg (nusnet-121-223.dynip.nus.edu.sg [137.132.121.223])
	by leonis.nus.edu.sg (8.12.9/8.12.9) with ESMTP id h9U5Xco7020847;
	Thu, 30 Oct 2003 13:33:40 +0800 (SGT)
Message-ID: <3FA0A2AB.1050803@bic.nus.edu.sg>
Date: Thu, 30 Oct 2003 13:33:31 +0800
From: Tan Tin Wee <tinwee@bic.nus.edu.sg>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: James Seng <jseng@pobox.org.sg>, ietf-imaa@imc.org, ietf-822@imc.org,
        ietf@ietf.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU> <20031028095243.A1525@lustre.dyn.wiw.org> <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>            <3FA04E1E.9070906@pobox.org.sg> <200310300444.h9U4iu9X016162@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Valdis.Kletnieks@vt.edu wrote:
> On Thu, 30 Oct 2003 07:32:46 +0800, James Seng said:
> 
>>to your opinion but please do so in other place, and not here. The group 
>>is suppose to work on Internationalization of Email address 
>>(identifiers), not debate whether we need it or not.
> 
> 
> Any group that addresses "how" and "for which contexts" without having
> a good grasp on "why" is inventing solutions in search of problems.
[snipped]

> 
> And if you can't safely put e-caron on a business card, why are we bothering?

We're bothering because it has occurred to some of us that
some folks somewhere in the world may wish to send email only to
themselves within an intranet or a large national intranet or
wish to launch their own internal e-government or
e-education system that involves interpersonal
and interdepartmental communications amongst folks that
speak the same language which doesn't not happen to be Latin-based.
And if they need to send email to outsiders, then they would
send in ASCII email address, as routinely as they would
flipping between the reverse and obverse of their
namecards, one side the local language (including their
local IEA address) and the other, the global lingua franca
latin.

Right now, the Mongolian (or whatever) government cannot launch say
their e-Government intranet email system seamlessly with
the Internet without much pain in getting everyone up to
speed on the latin character set. IEA support will definitely
be a boon to such folks.







From owner-ietf@ietf.org  Thu Oct 30 10:50:49 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27766
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 10:50:49 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFElO-0005sl-6m
	for ietf-list@asgard.ietf.org; Thu, 30 Oct 2003 10:31:06 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AF7aG-00021a-03
	for ietf@asgard.ietf.org; Thu, 30 Oct 2003 02:51:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12953
	for <ietf@ietf.org>; Thu, 30 Oct 2003 02:50:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF7a9-000711-00
	for ietf@ietf.org; Thu, 30 Oct 2003 02:51:01 -0500
Received: from [212.18.224.18] (helo=mail.centralnic.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF7a9-00070y-00
	for ietf@ietf.org; Thu, 30 Oct 2003 02:51:01 -0500
Received: from lon-staffgw-1.centralnic.net ([212.18.224.152] helo=Steve.centralnic.com)
	by mail.centralnic.net with esmtp (Exim 4.22)
	id 1AF7Zz-00037t-HK; Thu, 30 Oct 2003 07:50:51 +0000
Message-Id: <5.2.1.1.2.20031030074204.02c91850@212.18.224.19>
X-Sender: steve@212.18.224.19
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 30 Oct 2003 07:58:27 +0000
To: Valdis.Kletnieks@vt.edu, Tan Tin Wee <tinwee@bic.nus.edu.sg>
From: Steve Dyer <steve@uk.com>
Cc: ietf-imaa@imc.org, ietf-822@imc.org, ietf@ietf.org
In-Reply-To: <200310300624.h9U6OX9X018995@turing-police.cc.vt.edu>
References: <Your message of "Thu, 30 Oct 2003 13:33:31 +0800." <3FA0A2AB.1050803@bic.nus.edu.sg>
 <E1AEH14-000N0E-GD@psg.com>
 <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU>
 <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU>
 <20031028095243.A1525@lustre.dyn.wiw.org>
 <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>
 <3FA04E1E.9070906@pobox.org.sg>
 <200310300444.h9U4iu9X016162@turing-police.cc.vt.edu>
 <3FA0A2AB.1050803@bic.nus.edu.sg>
Mime-Version: 1.0
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA) 
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 01:24 30/10/2003 -0500, Valdis.Kletnieks@vt.edu wrote:
>On Thu, 30 Oct 2003 13:33:31 +0800, Tan Tin Wee said:
> >snip
>If whatever Mongolia was doing was guaranteed to stay in Mongolia, it wouldn't
>be an issue.  However, people inside the enclave *will* want to communicate
>with outsiders as well - and the instant you allow an e-mail to cross the
>border, you have to get all these types of issues sorted out.
>
>Mark Crispin's point was that currently, knowledge of Latin glyphs *is*
>assumed, and as far as anybody has evidenced, this hypothetical Mongolian
>intranet with many non-Latin-aware users is still hypothetical - and with no
>evidence saying there actually IS one in the works someplace.  So Mark quite
>reasonably pointed out that it may very well make more *engineering* sense to
>simply train the very small number of users who don't know Latin glyphs 
>than to
>come up with some very convoluted scheme that annoys everybody else.

Hi

The above is a self-fulfilling prophesy. Of course you have to have a 
knowledge of Latin glyphs because the only Internet around is based on it.
The millions of people (including Mongolians) who don't know latin glyphs 
(and may not yet have computers, and may be illiterate) are still the 
future users, possibly the majority of future users, of the Internet and 
this effort is to address their future needs.

My observation is that we are maybe worrying too much about the characters 
being represented and how they are used, We should merely define a 
protocol. In my book that protocol should allow email addresses to carry 
the widest possible eight-bit ASCII payload. (ie. everything except control 
characters) so that existing non-unicode special characters can be carried, 
and can also carry IDN-style unicoded characters.

Sure there will be problems, - there will be anyway. However we need to 
enable local users to communicate in local scripts in the local language.

In this regard Europeans and Americans are maybe too steeped in the 
existing latin/ASCII to address this issue.  We should listen carefully to 
the non-latin world rather than trying to find reasons not to do it.

I often get completely incomprehensible emails which originated in 
non-latin scripts - I just delete them. I know they're not important for me 
because no author who tries to write to me in Chinese is going to get very 
far no matter what communication medium he uses. Why? Because I don't speak 
Chinese.

>The tail has to be a certain size before it's able to wag the dog.

This dog is almost all tail!

Regards

Steve Dyer 






From owner-ietf@ietf.org  Thu Oct 30 13:12:59 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03446
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 13:12:59 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFGwe-0002K1-Um
	for ietf-list@asgard.ietf.org; Thu, 30 Oct 2003 12:50:52 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AFGgC-00021C-Jl
	for ietf@asgard.ietf.org; Thu, 30 Oct 2003 12:33:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01988
	for <ietf@ietf.org>; Thu, 30 Oct 2003 12:33:41 -0500 (EST)
From: niket@mindspring.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFGgB-0006tM-00
	for ietf@ietf.org; Thu, 30 Oct 2003 12:33:51 -0500
Received: from mclean.mail.mindspring.net ([207.69.200.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFGgA-0006tJ-00
	for ietf@ietf.org; Thu, 30 Oct 2003 12:33:50 -0500
Received: from host-66-81-217-217.rev.o1.com ([66.81.217.217] helo=TOSHIBA)
	by mclean.mail.mindspring.net with smtp (Exim 3.33 #1)
	id 1AFGg4-000294-00; Thu, 30 Oct 2003 12:33:44 -0500
Message-ID: <3FA146D3.4B23@mindspring.com>
Date: Thu, 30 Oct 2003 09:13:55 -0800
X-Mailer: Mozilla 3.01 (WinNT; I)
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: Tan Tin Wee <tinwee@bic.nus.edu.sg>, ietf-imaa@imc.org, ietf-822@imc.org,
        ietf@ietf.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU> <20031028095243.A1525@lustre.dyn.wiw.org> <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU> <3FA04E1E.9070906@pobox.org.sg> <200310300444.h9U4iu9X016162@turing-police.cc.vt.edu>
	            <3FA0A2AB.1050803@bic.nus.edu.sg> <200310300624.h9U6OX9X018995@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Forget Mongolian. Think Chinese and Hindi, plus related languages that
use their character sets. Between the two of them you have nearly 3
billion potential users, i.e. half the world's population. Admittedly
not all of them are literate, and many do understand the Latin character
set, but this is still a very large group to disenfranchise.

There is a second thread to your argument which I object to. Just
because many Internet users can understand the Latin character set does
not mean they do not want to send stuff in their native character set,
or be forced to use the Latin character set. Of course so far we have
made it impossible to do so. I do not understand the difficulty in
making the software 8-bit byte clean - it does not need to understand
what the characters are - just that they are different from each other.
It does not even need to know that one character actually takes three
bytes to specify. In fact, there is an encoding, UTF-8, that makes most
program changes unnecessary, since it maps 128 ASCII 1:1. Then let the
users decide what they want to do.

Why place unnecessary restrictions on the Internet just because it
results in messages that you personally can't understand?

Valdis.Kletnieks@vt.edu wrote:
> 
> On Thu, 30 Oct 2003 13:33:31 +0800, Tan Tin Wee said:
> > And if they need to send email to outsiders, then they would
> > send in ASCII email address, as routinely as they would
> 
> OK.. I get that part.  Now for the big question:  You're there in this
> Mongolian intranet, and find you need to ask me a technical question,
> so my address gets entered in ascii. OK so far.  You now decide you
> need to cc: somebody on the intranet so they know I've been asked.
> 
> 1) What does that person do with my ascii-fied address?
> 2) How do I do a 'reply all' to both of you?
> 
> 3) How is your From: address encoded so it's usable *BOTH* from where
> I am and from where your co-worker is?
> 
> 3a) Can you achieve goal (3) while using the same From: as you would use
> if you were mailing ONLY to the intranet (so people don't have to maintain
> 2 differently encoded values for your address for filtering purposes, etc).
> 
> If whatever Mongolia was doing was guaranteed to stay in Mongolia, it wouldn't
> be an issue.  However, people inside the enclave *will* want to communicate
> with outsiders as well - and the instant you allow an e-mail to cross the
> border, you have to get all these types of issues sorted out.
> 
> Mark Crispin's point was that currently, knowledge of Latin glyphs *is*
> assumed, and as far as anybody has evidenced, this hypothetical Mongolian
> intranet with many non-Latin-aware users is still hypothetical - and with no
> evidence saying there actually IS one in the works someplace.  So Mark quite
> reasonably pointed out that it may very well make more *engineering* sense to
> simply train the very small number of users who don't know Latin glyphs than to
> come up with some very convoluted scheme that annoys everybody else.
> 
> The tail has to be a certain size before it's able to wag the dog.
> 
>     ---------------------------------------------------------------
> 
>                Part 1.2   Type: application/pgp-signature







From owner-ietf@ietf.org  Thu Oct 30 16:04:22 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11417
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 16:04:22 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFJhJ-0008I8-Kc
	for ietf-list@asgard.ietf.org; Thu, 30 Oct 2003 15:47:13 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AFJeP-0007kO-DW
	for ietf@asgard.ietf.org; Thu, 30 Oct 2003 15:44:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10704
	for <ietf@ietf.org>; Thu, 30 Oct 2003 15:44:03 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFJeO-0001t8-00
	for ietf@ietf.org; Thu, 30 Oct 2003 15:44:12 -0500
Received: from h80ad25e2.async.vt.edu ([128.173.37.226] helo=turing-police.cc.vt.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFJeM-0001t4-00
	for ietf@ietf.org; Thu, 30 Oct 2003 15:44:11 -0500
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.10/8.12.10) with ESMTP id h9UKi7gU021938;
	Thu, 30 Oct 2003 15:44:07 -0500
Message-Id: <200310302044.h9UKi7gU021938@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: niket@mindspring.com
Cc: ietf-imaa@imc.org, ietf-822@imc.org, ietf@ietf.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA) 
In-Reply-To: Your message of "Thu, 30 Oct 2003 09:13:55 PST."
             <3FA146D3.4B23@mindspring.com> 
References: <E1AEH14-000N0E-GD@psg.com> <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU> <20031028095243.A1525@lustre.dyn.wiw.org> <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU> <3FA04E1E.9070906@pobox.org.sg> <200310300444.h9U4iu9X016162@turing-police.cc.vt.edu> <3FA0A2AB.1050803@bic.nus.edu.sg> <200310300624.h9U6OX9X018995@turing-police.cc.vt.edu>
            <3FA146D3.4B23@mindspring.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1769311138P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 30 Oct 2003 15:44:06 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

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

On Thu, 30 Oct 2003 09:13:55 PST, niket@mindspring.com said:
> Forget Mongolian. Think Chinese and Hindi, plus related languages that
> use their character sets. Between the two of them you have nearly 3
> billion potential users, i.e. half the world's population. Admittedly
> not all of them are literate, and many do understand the Latin character
> set, but this is still a very large group to disenfranchise.

Right.  The yet unanswered question is how many would be disenfranchised
by making them learn the Latin charset, compared to how many would
be disenfranchised by a non-perfect globalization scheme (see my comment
yesterday regarding macrons and carons).

> There is a second thread to your argument which I object to. Just
> because many Internet users can understand the Latin character set does
> not mean they do not want to send stuff in their native character set,
> or be forced to use the Latin character set. Of course so far we have
> made it impossible to do so.

Note that this is discussing *addresses only*.  We've had charset
support for bodyparts and 2047-encoding for other header fields for *years*.

I get at least 5 or 6 emails a day that have addresses of the form
From: "kanji/big5/etc string here" <romanized.name@someplace.pacificrim>
and/or have charset=utf-8 and kanji in them.

> Why place unnecessary restrictions on the Internet just because it
> results in messages that you personally can't understand?

An equally important consideration is that it result in messages that
are *usable* (possibly without comprehension). If whatever scheme we
decide on results in messages that I can't hit "reply" to or otherwise
process, it's not doing anybody any favors.

An often overlooked aspect of the ASCII charset is that it has 52 glyphs
which for the most part are visually distinctive (except for zero/oh, and
one/lower-ell), so even a non-speaker can make a determination "have I
entered the same glyphs as are on the business card?". This is not true
for any of the Asian glyph sets (at least *I* can't tell easily), and I
don't think that the Latin 1/A/B extension has this property either,
once you start dealing with macrons, cedillas, ogonceks, carons, dots,
and other ornamentation....

So my question remains:  are we doing the 3 billion asians a favor by forcing
them to be able to tell the difference between e-caron and e-breve?

Are we doing *anybody* favors if we make them use rfc3490-style xn-- strings
that are totally incomprehensible if they are from outside the local conclave?
Remember - if they don't understand Latin charsets, a 3490-encoded address will
be *painful*, even for the *owner*.  You don't believe me? Take the character
string 'valdis.kletnieks', change the first e to 0113 (small e-macron), punycode it,
and let me know how much mnemonic value it has.

And remember - the string you get there is the sort of thing that all 3 billion
Asians will get to enter (after I get my sysadmin to set up the aliases to get that
punycode to actually drop into *my* mailbox).

Are you sure it's worth the effort?

It's not that I'm unsympathetic to the goals - far from it.  It's just that I
was there during the RFC2047 wars (which are *still* going on in the spam
world, silly spammers sending around untagged 8-bit headers), and a big part
of me wants to say "Oh no, not again....".





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

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

iD8DBQE/oXgWcC3lWbTT17ARAiilAJ0dpFustTwdCERYNa8F6iS2V3HD3gCdFUIc
Wfx617R3KVtkLgQnFnWuFdg=
=uiJ3
-----END PGP SIGNATURE-----

--==_Exmh_1769311138P--



From owner-ietf@ietf.org  Thu Oct 30 17:54:39 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18031
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 17:54:39 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFKjX-0002Lo-9K
	for ietf-list@asgard.ietf.org; Thu, 30 Oct 2003 16:53:35 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AFKRb-0001yf-TS
	for ietf@asgard.ietf.org; Thu, 30 Oct 2003 16:35:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13895
	for <ietf@ietf.org>; Thu, 30 Oct 2003 16:34:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFKRa-0002pD-00
	for ietf@ietf.org; Thu, 30 Oct 2003 16:35:02 -0500
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFKRZ-0002oc-00
	for ietf@ietf.org; Thu, 30 Oct 2003 16:35:01 -0500
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.10/8.12.10) id h9ULYeTk014657 env-from <vjs>;
	Thu, 30 Oct 2003 14:34:40 -0700 (MST)
Date: Thu, 30 Oct 2003 14:34:40 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200310302134.h9ULYeTk014657@calcite.rhyolite.com>
To: ietf-822@imc.org, ietf-imaa@imc.org, ietf@ietf.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
References: <200310302044.h9UKi7gU021938@turing-police.cc.vt.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Valdis.Kletnieks@vt.edu
> To: niket@mindspring.com
> Cc: ietf-imaa@imc.org, ietf-822@imc.org, ietf@ietf.org

> ...
> Are we doing *anybody* favors ...

Contrary to super heated claims about unfairness and disenfranchisement,
the purposes of this approaching train wreck do not include doing any
users any favors.  At best it is about proving the maturity of the
IETF by inventing a scheme that will make x.400 addresses seem clear
and obvious.

The first and most important thing about train wrecks is that you
don't want to be standing close to where they happen.  After waiving
your lantern at the people in the engine cabs, it's best run as fast
as you can.

The second thing is that after the fire, smoke, and noise settles,
you will see armies of people and equipment working on enormous piles
of debris.

The third thing is that although the debris piles and surrounding
encampments will look permanent, they will disappear almost overnight
and leave almost no sign.  In 5 years, everyone except the most laggard
acolytes of trade rag gurus will have forgotten it.  By then there
will be a new runaway internationalization mail address train about
to derail. 

It's not as if we've not been here before.  It's past time to start
running to get out of the way of this train.  Who knows?  Maybe this
time time the internationalized mail address train won't wreck itself
at the bottom of the pass.

In other words, do all three of these mailing lists need this traffic?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Thu Oct 30 18:30:55 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20332
	for <ietf-web-archive@odin.ietf.org>; Thu, 30 Oct 2003 18:30:55 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFLPh-000321-VP
	for ietf-list@asgard.ietf.org; Thu, 30 Oct 2003 17:37:09 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AFLDm-0002tf-Gs
	for ietf@asgard.ietf.org; Thu, 30 Oct 2003 17:24:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17211
	for <ietf@ietf.org>; Thu, 30 Oct 2003 17:24:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFLDl-0003lp-00
	for ietf@ietf.org; Thu, 30 Oct 2003 17:24:49 -0500
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1AFLDk-0003lm-00
	for ietf@ietf.org; Thu, 30 Oct 2003 17:24:48 -0500
Received: (qmail 3473 invoked by uid 1013); 30 Oct 2003 22:24:46 -0000
Date: Thu, 30 Oct 2003 23:24:46 +0100
From: Markus Stumpf <maex-lists-ietf-general@Space.Net>
To: ietf-imaa@imc.org, ietf-822@imc.org, ietf@ietf.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-ID: <20031030222446.GJ82556@Space.Net>
References: <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU> <014c01c39cf4$5675cd60$79d52b09@DAVIS1> <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU> <20031028095243.A1525@lustre.dyn.wiw.org> <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU> <3FA04E1E.9070906@pobox.org.sg> <200310300444.h9U4iu9X016162@turing-police.cc.vt.edu> <87111751500.20031029230924@brandenburg.com> <0c7801c39ee4$39140010$0400a8c0@DFNJGL21>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <0c7801c39ee4$39140010$0400a8c0@DFNJGL21>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id RAA17212
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 30, 2003 at 06:49:13AM -0600, Spencer Dawkins wrote:
> I agree with Dave in the general case ("the goal is to go beyond
> today's Internet"), but am wondering if that also requires us to go
> beyond today's language capability when we start leaking these
> addresses between enclaves. I am sensitive to the comments expressed
> in this thread, that a heckuva lot of people have to learn two sets of
> glyphs, and I'm not one of them - I just don't see how we do it any
> other way.

In Europe we have a lot of character sets. I use 8859-1, a few
kilometers away in Greece they use 8859-7. As with all the math
I at least have an idea about the characters. However neither my
keyboard nor my X server can currently be used for that out of the
box (as it is).

IMHO in all that discussion it is important with the "case studies"
to differentiate if the address has to be keyed in by some human
or if I would only need more sophisticated software to deal with the
problem.

I am not too enthusiastic with all that internationalization, but:

- In Germany the DENIC has announced they will provide internationalized
  domain names probably next year. The run on this names is really big.
  Other NICs surely have similar plans. So with these domain names we
  need a method to transport email there.

- If I want to go to the olypic games in Greece next year and the website
  has an email address with greek characters, will I be able to click on =
it
  type some text, and my MUA/browser will do the right thing? If it will
  work and everyone will be able to recognize "this is the email address"
  that's fine for me. XML for more structure and better browsers will hel=
p
  for the latter some time.

- How long will there be paper business cards? Don't a lot people
  already exchange business cards per handheld/organizer? And those
  companies with international contacts will have accounts in the
  according coding or at least in a coding that is familiar for the
  other party. Software will be able to do the rest. So you will have to
  carry a small bag of different cards with different codings until you
  will have no paper cards any longer, because they are too difficult to
  handle in this area.
  A big fair in Munich had tested kinda electronic cards lately. As you
  buy your ticket you type in your contact data and it is printed on the
  card as a barcode. Exhibitors had barcode readers and special
  software, so if you want to make a contact you hand over your ticket
  and the infos flow ...

There WILL be a lot of problems with internationalized email addresses
but IMHO a lot of them will be solvable by sophisticated software.
Some of them won't as in print media (and also tv. radio, ...) a domain
    =B5.de	(in 8859-1)
and
    =B5.de	(in 8859-7)
looks identical, but isn't as the =B5 sit on different codes. So the
commercials will be fun:
    "visit us in the Internet on www.=B5.de in good old 8859-1 coding."

And despite all these I think it will be a long time until addresses like
    j=FCrgen.gr=F6=DFl@h=FCberbr=E4u.de
will look familiar (even if this is a (for me) local coding).

	\Maex

--=20
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-=
0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-=
299
"The security, stability and reliability of a computer system is reciproc=
ally
 proportional to the amount of vacuity between the ears of the admin"



From owner-ietf@ietf.org  Fri Oct 31 01:20:51 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01227
	for <ietf-web-archive@odin.ietf.org>; Fri, 31 Oct 2003 01:20:51 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFSGq-0005Dy-0M
	for ietf-list@asgard.ietf.org; Fri, 31 Oct 2003 00:56:28 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AFS3P-00055b-83
	for ietf@asgard.ietf.org; Fri, 31 Oct 2003 00:42:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00029
	for <ietf@ietf.org>; Fri, 31 Oct 2003 00:42:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFS3N-0001Jj-00
	for ietf@ietf.org; Fri, 31 Oct 2003 00:42:33 -0500
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFS3M-0001JV-00
	for ietf@ietf.org; Fri, 31 Oct 2003 00:42:32 -0500
Received: from f01v-27-220.d0.club-internet.fr ([212.195.246.220] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1AFS3A-000191-4y; Thu, 30 Oct 2003 21:42:20 -0800
Message-Id: <6.0.0.22.2.20031031030247.04c74580@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Fri, 31 Oct 2003 04:02:22 +0100
To: Markus Stumpf <maex-lists-ietf-general@Space.Net>, ietf-imaa@imc.org,
        ietf-822@imc.org, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
In-Reply-To: <20031030222446.GJ82556@Space.Net>
References: <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271656320.860@Tomobiki-Cho.CAC.Washington.EDU>
 <014c01c39cf4$5675cd60$79d52b09@DAVIS1>
 <Pine.WNT.4.60.0310271846580.3944@Tomobiki-Cho.CAC.Washington.EDU>
 <20031028095243.A1525@lustre.dyn.wiw.org>
 <Pine.WNT.4.60.0310272027210.2428@Tomobiki-Cho.CAC.Washington.EDU>
 <3FA04E1E.9070906@pobox.org.sg>
 <200310300444.h9U4iu9X016162@turing-police.cc.vt.edu>
 <87111751500.20031029230924@brandenburg.com>
 <0c7801c39ee4$39140010$0400a8c0@DFNJGL21>
 <20031030222446.GJ82556@Space.Net>
Mime-Version: 1.0
Content-Type: text/plain; x-avg-checked=avg-ok-3EF02C17; charset=iso-8859-1; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id AAA00030
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

At 23:24 30/10/03, Markus Stumpf wrote:
>A big fair in Munich had tested kinda electronic cards lately. As you
>buy your ticket you type in your contact data and it is printed on the
>card as a barcode. Exhibitors had barcode readers and special
>software, so if you want to make a contact you hand over your ticket
>and the infos flow ...

Markus,
We are here in a typical layer violation we do not see. We think that=20
passing information from layer 7 to a user is a simple task because ascii=
=20
simplifies it to ascii readers. ENS Model puts 2 layers for that.

Your example is a very good common example of this:
- the application layer (7) has an infromation: the visitor carries and=20
delivers his name to the registration system
- the interapplication layer (8) corresponds to the trade show system whi=
ch=20
organizes and manages the bar codes or other systems (magnetic, noise=20
printing, laser, etc.) and the event and the lanes for him to stop at you=
r=20
boot using his feet and not bytes on a wire.
- the assistant layer (9) which is going to read the information for you=20
and/or for your computer.
- until eventually you the user (layer 10) may access to the infromation=20
and possibly disseminate to other layer 10 colleagues or colleges, or to=20
escalate it to other communicating structures (11). For example the visit=
or=20
may be a common client for your trade pavillon and benefit from a discoun=
t.=20
And then you may want to verify his legal ID and hit the societal system=20
layer (12).

All these layers car be executed by people and by machines. The simplest=20
protocol is yes/no. It then increases in complexity through numbers, then=
=20
langages and characters. Basic English and ASCII are one of the most=20
interesting level for naked brainq. But what about computer (software) or=
=20
community assisted (brainware) brains: whre is/are the most interesting=20
levels of equilibrium?

This is why I say the target is not to develop internationalized, nor=20
multilingual names. To please  Hindi vs American (objections stand). But =
a=20
truly fully vernacular support for users and applications. This means eve=
n=20
more than transparent binary, because binary is only to be one occurence =
in=20
it.

We have a default : ascii. We have a first level of complexity : IDNA. Th=
is=20
must continue. This is why I objected to the (xn--) structure. It is to b=
e=20
necessarily the begining of an unlimited vernacularisation. Having entere=
d=20
the xn-- in the left of the name label introduced a cross hierarchical=20
structure in the DNS (levels from right to left and layers within the=20
labels from left to right). With a complex impact on the DNS administrati=
on=20
and evolution - as we start seeing it now. Another exemple is IPv6. I dou=
bt=20
we can continue writing manually db.flles addresses.

Now, several question the need of a change. IMHO they are right and wrong=
=20
as we do not consider the layers. At the user's layer we must have=20
everything in the language and culture of the user. We are not going to s=
ay=20
that cultures are bugs to correct to fit IDNA! But at the old SMTP level =
or=20
DNS do we need that complexity? I think not. Even if we were building a=20
brand nwe DNS.

What Vint suggests is to use ASCII as a 35 or 37 highly readable numberin=
g=20
pad (2 to 9 A to Z and "-", or 0 to 9) to give more capacities to support=
=20
vernacularization on the layer above. Otherwise everything is going to=20
collapse into a too complex system. For example where are you going to=20
introduce the OPES which will read the written chinese in the proper loca=
l=20
way? This is the same problem as for the multilingual TLDs. In a flat mod=
el=20
we saw it was not possible. I do not see a real problem in a properly set=
=20
multi-layer model. One layer can go one way and the next layer the other=20
way. Then you know what you wand to do where.

jfc












>There WILL be a lot of problems with internationalized email addresses
>but IMHO a lot of them will be solvable by sophisticated software.
>Some of them won't as in print media (and also tv. radio, ...) a domain
>     =B5.de        (in 8859-1)
>and
>     =B5.de        (in 8859-7)
>looks identical, but isn't as the =B5 sit on different codes. So the
>commercials will be fun:
>     "visit us in the Internet on www.=B5.de in good old 8859-1 coding."
>
>And despite all these I think it will be a long time until addresses lik=
e
>     j=FCrgen.gr=F6=DFl@h=FCberbr=E4u.de
>will look familiar (even if this is a (for me) local coding).
>
>         \Maex
>
>--
>SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356=
-0
>Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356=
-299
>"The security, stability and reliability of a computer system is recipro=
cally
>  proportional to the amount of vacuity between the ears of the admin"




From owner-ietf@ietf.org  Fri Oct 31 09:40:35 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29808
	for <ietf-web-archive@odin.ietf.org>; Fri, 31 Oct 2003 09:40:35 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFZuJ-0002kH-6X
	for ietf-list@asgard.ietf.org; Fri, 31 Oct 2003 09:05:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AFZpT-0002c6-Mt
	for ietf@asgard.ietf.org; Fri, 31 Oct 2003 09:00:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28582
	for <ietf@ietf.org>; Fri, 31 Oct 2003 09:00:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFZpS-0000P6-00
	for ietf@ietf.org; Fri, 31 Oct 2003 09:00:42 -0500
Received: from mail.securesoftware.com ([206.131.226.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFZpN-0000Oi-00
	for ietf@ietf.org; Fri, 31 Oct 2003 09:00:37 -0500
Received: from 206.131.226.48 (unknown [206.131.226.48])
	by mail.securesoftware.com (Postfix) with ESMTP
	id 633FE2E; Fri, 31 Oct 2003 08:58:35 -0500 (EST)
From: Dave Aronson <spamtrap.ietf@dja.mailme.org>
Organization: Secure Software -- http://www.securesw.com/
To: ietf-imaa@imc.org, ietf-822@imc.org, ietf@ietf.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Date: Fri, 31 Oct 2003 08:59:28 -0500
User-Agent: KMail/1.5.2
References: <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <0c7801c39ee4$39140010$0400a8c0@DFNJGL21> <20031030222446.GJ82556@Space.Net>
In-Reply-To: <20031030222446.GJ82556@Space.Net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310310859.28748.spamtrap.ietf@dja.mailme.org>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Thu October 30 2003 17:24, Markus Stumpf wrote:

 > - How long will there be paper business cards? Don't a lot people
 >   already exchange business cards per handheld/organizer?

IMHO, always, even for ones with email addresses (and URLs and so on) on 
them.  Even those who lug PDAs around everywhere, may occasionally have 
reason to give contact data to someone who doesn't.

Think also of many businesses that cater to the general public, from 
bleeding-edge geeks like us, to those who can barely spell PDA and 
don't know what one is.  Sure, such a business has many clientele who 
wouldn't make use of the email address, URL, etc.  However, that's 
usually not enough to justify leaving them off.

Can we have a show of hands of those people who, when giving or 
receiving contact data in person, do so *only* by transmitting between 
PDAs?  (If you prefer, feel free to reply directly.  I'll announce 
results and comments received.)  I'm guessing that describes far less 
than a single percent of us, never mind the world.

-- 
Dave Aronson, Senior Software Engineer, Secure Software Inc.
(Opinions above NOT those of securesw.com unless so stated!)
Email me at: work (D0T) 2004 (@T) dja (D0T) mailme (D0T) org
Web: http://destined.to/program http://listen.to/davearonson




From owner-ietf@ietf.org  Fri Oct 31 10:29:40 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03408
	for <ietf-web-archive@odin.ietf.org>; Fri, 31 Oct 2003 10:29:40 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFagh-0003nS-9K
	for ietf-list@asgard.ietf.org; Fri, 31 Oct 2003 09:55:43 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AFaeW-0003js-RE
	for ietf@asgard.ietf.org; Fri, 31 Oct 2003 09:53:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00578
	for <ietf@ietf.org>; Fri, 31 Oct 2003 09:53:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFaeV-00017Z-00
	for ietf@ietf.org; Fri, 31 Oct 2003 09:53:28 -0500
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1AFaeV-00016o-00
	for ietf@ietf.org; Fri, 31 Oct 2003 09:53:27 -0500
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centive.com (NAVGW 2.5.2.11) with SMTP id M2003103110072228653
 ; Fri, 31 Oct 2003 10:07:22 -0500
Received: from centive.com ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Fri, 31 Oct 2003 09:50:06 -0500
Message-ID: <3FA2769E.2000909@centive.com>
Date: Fri, 31 Oct 2003 09:50:06 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
CC: ietf-imaa@imc.org, ietf-822@imc.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
References: <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <0c7801c39ee4$39140010$0400a8c0@DFNJGL21> <20031030222446.GJ82556@Space.Net> <200310310859.28748.spamtrap.ietf@dja.mailme.org>
In-Reply-To: <200310310859.28748.spamtrap.ietf@dja.mailme.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Oct 2003 14:50:06.0627 (UTC) FILETIME=[462A0F30:01C39FBE]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave Aronson wrote:

>Think also of many businesses that cater to the general public, from 
>bleeding-edge geeks like us, to those who can barely spell PDA and 
>don't know what one is.
>
I think the only times I've seen anybody use PDAs to exchange contact 
information were at IETF meetings, in the hallways, when people had time 
to kill.  It just takes too long.  Typically, when two companies are 
meeting, and you've got, say, four people on each side, everybody swaps 
business cards in under a minute, and you're done.  Doing the same thing 
via IR would hold the meeting up too long.

-- 
/==========================================\
|John Stracke      |jstracke@centive.com   |
|Principal Engineer|http://www.centive.com |
|Centive           |My opinions are my own.|
|==========================================|
|I have strong opinions about ambivalence. |
\==========================================/





From owner-ietf@ietf.org  Fri Oct 31 11:39:34 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06836
	for <ietf-web-archive@odin.ietf.org>; Fri, 31 Oct 2003 11:39:34 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFc5o-000439-VA
	for ietf-list@asgard.ietf.org; Fri, 31 Oct 2003 11:25:44 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AFc3H-0003fV-L3
	for ietf@asgard.ietf.org; Fri, 31 Oct 2003 11:23:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05727
	for <ietf@ietf.org>; Fri, 31 Oct 2003 11:22:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFc3G-0002aT-00
	for ietf@ietf.org; Fri, 31 Oct 2003 11:23:06 -0500
Received: from herculanum.int-evry.fr ([157.159.11.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFc3F-0002aA-00
	for ietf@ietf.org; Fri, 31 Oct 2003 11:23:05 -0500
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20])
	by herculanum.int-evry.fr (Postfix) with ESMTP id 03EEA33E9F
	for <ietf@ietf.org>; Fri, 31 Oct 2003 17:11:39 +0100 (CET)
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP id 7B5913F4CB
	for <ietf@ietf.org>; Fri, 31 Oct 2003 17:11:38 +0100 (CET)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003103117113831910
 for <ietf@ietf.org>; Fri, 31 Oct 2003 17:11:38 +0100
Received: from localhost (ivan.int-evry.fr [157.159.100.48])
	by sparte.int-evry.fr (Postfix) with ESMTP id 2FFBF3F4C6
	for <ietf@ietf.org>; Fri, 31 Oct 2003 17:11:36 +0100 (CET)
Received: from jjp by localhost with local id 1AFbrs-0006qH-00
	for <ietf@ietf.org>; Fri, 31 Oct 2003 17:11:20 +0100
Date: Fri, 31 Oct 2003 17:11:20 +0100
From: Jean-Jacques Puig <Jean-Jacques.Puig@int-evry.fr>
To: ietf@ietf.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-ID: <20031031161120.GA24335@ivan.int-evry.fr>
Mail-Followup-To: ietf@ietf.org
References: <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <0c7801c39ee4$39140010$0400a8c0@DFNJGL21> <20031030222446.GJ82556@Space.Net> <200310310859.28748.spamtrap.ietf@dja.mailme.org> <3FA2769E.2000909@centive.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3FA2769E.2000909@centive.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, Oct 31, 2003 at 09:50:06AM -0500, John Stracke wrote:
> Dave Aronson wrote:
> 
> >Think also of many businesses that cater to the general public, from 
> >bleeding-edge geeks like us, to those who can barely spell PDA and 
> >don't know what one is.
> >
> I think the only times I've seen anybody use PDAs to exchange contact 
> information were at IETF meetings, in the hallways, when people had time 
> to kill.  It just takes too long.  Typically, when two companies are 
> meeting, and you've got, say, four people on each side, everybody swaps 
> business cards in under a minute, and you're done.  Doing the same thing 
> via IR would hold the meeting up too long.
> 

Agree. Another point is that many firms print contact / support / sales
mail addresses on documents. So may also individuals in some
circumstances (teachers on the hard copy of their teaching doc,
classified advertisements on newspapers, etc.). Though one may conceive
adverts with a bluetooth device broadcasting contact information, I
believe printed material is still a significant way of obtaining email
addresses and will be so for a long.

Regarding the actual issue (IEA), the technical problem of having to
enter an address in an unknown charset may solve itself almost
naturally: people who feel concerned about being reachable by anyone
abroad would create/buy/ask-their-admin-for a  ascii address, while
others would get locale encoded addresses for a local use. A kind of a
social consensus.

-- 
Jean-Jacques Puig

[homepage] http://www-lor.int-evry.fr/~puig/



From owner-ietf@ietf.org  Fri Oct 31 16:39:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21245
	for <ietf-web-archive@odin.ietf.org>; Fri, 31 Oct 2003 16:39:42 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFgdU-0001em-8a
	for ietf-list@asgard.ietf.org; Fri, 31 Oct 2003 16:16:48 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AFgSp-0001XP-Gx
	for ietf@asgard.ietf.org; Fri, 31 Oct 2003 16:05:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20366
	for <ietf@ietf.org>; Fri, 31 Oct 2003 16:05:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFgSn-0007LI-00
	for ietf@ietf.org; Fri, 31 Oct 2003 16:05:45 -0500
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1AFgSn-0007LF-00
	for ietf@ietf.org; Fri, 31 Oct 2003 16:05:45 -0500
Received: (qmail 94378 invoked by uid 1013); 31 Oct 2003 21:05:44 -0000
Date: Fri, 31 Oct 2003 22:05:44 +0100
From: Markus Stumpf <maex-lists-ietf-general@Space.Net>
To: ietf@ietf.org, ietf-imaa@imc.org, ietf-822@imc.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-ID: <20031031210544.GF58697@Space.Net>
References: <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <0c7801c39ee4$39140010$0400a8c0@DFNJGL21> <20031030222446.GJ82556@Space.Net> <200310310859.28748.spamtrap.ietf@dja.mailme.org> <3FA2769E.2000909@centive.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3FA2769E.2000909@centive.com>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, Oct 31, 2003 at 09:50:06AM -0500, John Stracke wrote:
> I think the only times I've seen anybody use PDAs to exchange contact 
> information were at IETF meetings, in the hallways, when people had time 
> to kill.  It just takes too long.  Typically, when two companies are 
> meeting, and you've got, say, four people on each side, everybody swaps 
> business cards in under a minute, and you're done.  Doing the same thing 
> via IR would hold the meeting up too long.

Please keep in mind two things
1) I wrote
     "I am not too enthusiastic with all that internationalization" ;-))
2) I used the example with PDAs mainly for international contacts. Maybe
   our company is to small, but most of the time I have face to face
   contact to people of foreign companies they are from a local
   subsidiary and they have a local domain on their cards. So with most
   of the meetings (for me at least) this would be a non issue.

	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"



From owner-ietf@ietf.org  Fri Oct 31 16:39:43 2003
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21256
	for <ietf-web-archive@odin.ietf.org>; Fri, 31 Oct 2003 16:39:43 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 1AFgdU-0001f5-K0
	for ietf-list@asgard.ietf.org; Fri, 31 Oct 2003 16:16:48 -0500
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 1AFgW2-0001Ya-1e
	for ietf@asgard.ietf.org; Fri, 31 Oct 2003 16:09:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20453
	for <ietf@ietf.org>; Fri, 31 Oct 2003 16:08:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFgW0-0007N5-00
	for ietf@ietf.org; Fri, 31 Oct 2003 16:09:04 -0500
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1AFgW0-0007N2-00
	for ietf@ietf.org; Fri, 31 Oct 2003 16:09:04 -0500
Received: (qmail 94420 invoked by uid 1013); 31 Oct 2003 21:09:03 -0000
Date: Fri, 31 Oct 2003 22:09:03 +0100
From: Markus Stumpf <maex-lists-ietf-general@Space.Net>
To: ietf@ietf.org
Subject: Re: FYI: BOF on Internationalized Email Addresses (IEA)
Message-ID: <20031031210903.GG58697@Space.Net>
References: <00fd01c39ce8$b6f19fe0$79d52b09@DAVIS1> <0c7801c39ee4$39140010$0400a8c0@DFNJGL21> <20031030222446.GJ82556@Space.Net> <200310310859.28748.spamtrap.ietf@dja.mailme.org> <3FA2769E.2000909@centive.com> <20031031161120.GA24335@ivan.int-evry.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031031161120.GA24335@ivan.int-evry.fr>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, Oct 31, 2003 at 05:11:20PM +0100, Jean-Jacques Puig wrote:
> Agree. Another point is that many firms print contact / support / sales
> mail addresses on documents. So may also individuals in some
> circumstances (teachers on the hard copy of their teaching doc,
> classified advertisements on newspapers, etc.).

But this is an issue only in this are "cross contacts" to non local
partners. Local partners have the same charset coding so this would
not be a problem at all.

> naturally: people who feel concerned about being reachable by anyone
> abroad would create/buy/ask-their-admin-for a  ascii address, while
> others would get locale encoded addresses for a local use. A kind of a
> social consensus.

And the "default ASCII coding" may change to a "default chinese coding"
in some years ;-)

	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"



